Read Only Responsibility in Oracle Apps

Read Only Responsibility in Oracle Apps

Standard/Oracle recommended solution:

§ Identify the menu that is attached to the your responsibility just like GL super user and Payable manager. 

§ Identify the form functions that are attached to the respective menu. 

§ Now create new form functions similar to the standard one but with the parameter QUERY_ONLY="YES" like below.

Navigation : System Administrator --> Application --> Function --> Form --> Parameter

Oracle Apps Payable Table Structure

Oracle Apps Payable Table Structure:

Supplier Tables
AP_SUPPLIERS	This table replaces the old PO_VENDORS table.
	It stores information about your supplier level attributes.
AP_SUPPLIER_SITES_ALL	It stores information about your supplier site level attributes.
IBY_EXTERNAL_PAYEES_ALL	stores Payee(supplier) information.
HZ_PARTIES	Party data for the suppliers.
HZ_PARTY_SITES	Party site data for the supplier sites.B4
Supplier Interface tables
ap_suppliers_int	Supplier Interface. Execute Supplier Open Interface Import Program
ap_supplier_sites_int	Supplier site interface. Execute "Supplier Sites Open Interface Import" Program
Invoice
AP_INVOICES_ALL	It contains records for invoices you enter
AP_INVOICE_LINES_ALL	It contains records for invoice lines entered manually, generated automatically or imported from the Open Interface.
AP_INVOICE_DISTRIBUTIONS_ALL	It holds the distribution information that is manually entered or system-generated
Invoice Interface
AP_INVOICES_INTERFACE	Invoice Header Information. Run Payables Open Interface Import concurrent program
AP_INVOICE_LINES_INTERFACE	Invoice Lines and Distributions Information
Payments:
AP_CHECKS_ALL	Check Header Information
AP_INVOICE_PAYMENTS_ALL	Details of Invoice paid by a Check/Payment
AP_PAYMENT_HISTORY_ALL
AP_INV_SELECTION_CRITERIA_ALL
AP_SELECTED_INVOICES_ALL
AP_PAYMENT_DISTRIBUTIONS_ALL
CE_PAYMENT_DOCUMENTS	AP_CHECK_STOCKS_ALL
IBY_PAY_SERVICE_REQUESTS	Payment Process Request information  (11i Terminology is  Payment Batch)
IBY_PAY_INSTRUCTIONS_ALL	Payment Instruction information
IBY_DOC_PAYABLES_ALL	Invoice information stored by IBY for generating payment
IBY_PAYMENTS_ALL	Payment Information
Accounting
XLA_EVENTS	replaces AP_ACOCUNTING_EVENTS_ALL
XLA_AE_HEADERS	replaces AP_AE_HEADERS_ALL
XLA_AE_LINES	replaces AP_AE_LINES_ALL
Bank Accounts
CE_BANK_ACCOUNTS	AP_BANK_ACCOUNTS_ALL
CE_BANK_ACCT_USES_ALL	replaces AP_BANK_ACCOUNT_USES_ALL
Credit Card Transactions Table
AP_EXPENSE_FEED_LINES	Use the Credit Card Transaction Interface Table to load transaction datafrom your credit card issuers into your Payables system. When younsubmit the Credit Card Transaction Validation and Exception Report, for records where the CREATE_DISTRIBUTION_FLAG is Y, Payables
	uses the data in the AP_EXPENSE_FEED_LINES table to create distributions with proper accounts in the AP_EXPENSE_FEED_DISTS
	table

CREATE OR REPLACE PROCEDURE apps.xx_submit_journal_import_prg

AS

   --DECLARE

   v_request_id   VARCHAR2 (100);

BEGIN

   -- First set the environment of the user submitting the request by submitting

   -- fnd_global.apps_initialize().

   -- The procedure requires three parameters

   -- Fnd_Global.apps_initialize(userId,responsibilityId,applicationId)

   -- replace the following code with correct value as get from sql above

   fnd_global.apps_initialize (2836, 20434, 101);

   --(  user_id , responsibility_id, application_id )

   v_request_id :=

      fnd_request.submit_request ('SQLGL',           -- Application short name

                                  'GLLEZLSRS',           -- Program short name

                                  '',

                                  --'Allows customers to submit Journal Import through the Standard Request Submission form.', -- description (Not require)

                                  '',        -- start_time (start immediately)

                                  FALSE,        -- sub_request (default FALSE)

                                  -- Next is the parameters list of ARACCPB

                                  '1000', --  Parameter  =   Data access_set_id

                                  '98',

                                  --    Parameter  =   Journal Source Name ( use journal soure name not journal suer source name)

                                  '1',          --     Parameter  =  Ledger ID

                                  '',            --      Parameter  = Group ID

                                  'N', --     Parameter  =  Post Error to Suspense

                                  'N', --     Parameter  = Create Summary Journal

                                  'N' --      Parameter  =  Import Descriptive Flexfeild

                                     );

   DBMS_OUTPUT.put_line ('Request submitted. ID = ' || v_request_id);

   fnd_file.put_line (fnd_file.output,

                      'Request submitted. ID = ' || v_request_id);

   COMMIT;

EXCEPTION

   WHEN OTHERS

   THEN

      DBMS_OUTPUT.put_line (

         'Request set submission failed - unknown error: ' || SQLERRM);

      fnd_file.put_line (

         fnd_file.output,

         'Request set submission failed - unknown error: ' || SQLERRM);

END;