Featured post

Functionality of Segment Value Inheritance ESS Process

  The Segment Value Inheritance process simplifies the maintenance of the chart of accounts. When the characteristics of values in the value...

Wednesday 14 December 2016

Oracle Projects Billing Interface with Oracle Receivables

Oracle Projects (PA) generates draft invoices and uses Oracle Receivables (AR) features to create invoices and interface the accounting transactions to Oracle General Ledger (GL).  When you interface invoices to Receivables, a Projects process is used to collect all eligible, released draft invoices in PA and interfaces them to the Receivables interface tables.  This process also maintains project balances of Unbilled Receivables and unearned revenue and creates accounting transactions for these amounts. 
Once in the AR interface tables, the draft invoices await further processing by the Oracle Receivables AutoInvoice process.  After the AutoInvoice program is run to create invoices in Oracle Receivables, you need to run the tieback process to ensure that your data successfully loaded into Receivables and that there are no transactions requiring correction.   If you have rejected invoices, you will need to correct and resubmit them.
Standard Oracle Projects reports can be used to track your invoices as you interface data between Projects and Receivables. You can also use AutoInvoice output reports to review imported transaction data and transaction data that fails when you run AutoInvoice. Modification Of Transaction Lines (PA/AR Out of Sync). It is possible to modify or delete invoice transactions transferred from Projects to Receivables using the Transaction Entry Workbench (ARXTWMAI). 
THE MODIFICATION OR DELETION OF INVOICE TRANSACTIONS IN THIS MANNER IS NOT RECOMMENDED BECAUSE IT COULD CAUSE AR TO BE OUT OF SYNC WITH PA.
Refer to the scripts below to verify the information contained in the PA-AR invoice interface.  Both scripts should normally return the same lines and revenue amounts:
     SELECT l.interface_line_attribute2, l.interface_line_attribute6,   
     l.revenue_amount, l.interface_line_attribute1, h.reason_code,   
     l.interface_line_context
     FROM ra_customer_trx_all h, ra_customer_trx_lines_all l
     WHERE h.customer_trx_id = l.customer_trx_id
     AND h.interface_header_attribute2 = l.interface_line_attribute2
     AND h.trx_number = &Transaction_no.
     ORDER BY l.interface_line_attribute6;
..and..
     SELECT h.draft_invoice_num, l.line_num, amount, p.segment1,
     h.transfer_status_code
     FROM pa_draft_invoices_all h, pa_draft_invoice_items l, pa_projects_all p
     WHERE h.ra_invoice_number = &Transaction_no.
     AND h.project_id = l.project_id
     AND h.draft_invoice_num = l.draft_invoice_num
     AND l.project_id = p.project_id(+)
     ORDER BY l.line_num;

No comments:

Post a Comment

Please review my topic and update your comments

Note: only a member of this blog may post a comment.