Auto Invoice Master And Child Program in Oracle Apps
Auto Invoice Program is run once the Sales order is fulfilled in the shipping execution module of order management. It is used to used to import and validate transaction data from other financial systems from which one can create invoices, debit memos, credit memos, and on-account credits. It rejects transactions with invalid information to insure the integrity of the data. This fits well with in Oracle ERP or to integrate with any third party application.
It contains two main programs as explained below
It contains two main programs as explained below
1. Auto Invoice Master program RAXMTR
Selects and marks records in the interface tables to be processed based on the parameters the user entered and then calls the AutoInvoice Import program. Auto Invoice Master program has no report output.
•Gathers statistics, it means it gathers the stats on interface tables and set the stats on certain indices on interface tables
•Marks interface records for processing by marking request_id
•Submits multiple workers for Parallel Processing by creating instances for request.
2. Auto Invoice Import Program RAXTRX
Validates the selected record and creates transaction if it passes validation. Any record that fails validation is left in the interface table with an error code. Depending on the setup, related records may be rejected as well. This program has an output file called Auto Invoice Execution report, which you can view by clicking the View Report button in the Requests window.
Validates data,Inserts records,Deletes interface data and
Only when system option purge set to ‘Y’
There is a third program which is used to purge records
3. Auto Invoice Purge Program RAXDEL
Deletes records from the interface tables. If you set the Purge Interface Table system option to No in Define System Option window, Auto Invoice does not delete processed records from the interface tables after each run,and we must submit Auto Invoice Purge Program periodically to clean up the interface tables. This program only deletes transaction lines that have been successfully imported.
•Deletes all rows where interface_status =‘P’
•Ra_interface_lines
•Ra_interface_distributions
•Ra_interface_salescredits
Oracle Receivable’s Auto Invoice program will be used to import and validate Invoices.
A custom feeder program is required to transfer data from the Advantage extract files and populate the Auto Invoice interface tables (RA_INTERFACE_LINES_ALL and RA_INTERFACE_DISTRIBUTIONS_ALL).If there is need to run populate sales credit into RA_INTERFACE_SALESCREDITS_ALL table.
When run, AutoInvoice produces the AutoInvoice Execution Report and the AutoInvoice Validation Report. Any entries which failed validation can be reviewed in Oracle Receivables’ AutoInvoice Interface Exceptions window. Depending on the error, changes may need to be made in Receivables, the feeder program or the imported records in the interface tables.
How Autoinvoice Execution worksNormally, Auto Invoice can be divided into three major phases
Pre-grouping: here the validates all of the line level data takes place
Grouping: groups lines based on the grouping rules and validates header level data
Transfer :validates information that exists in Receivables tables
What happen when AutoInvoice run?
Once the Auto invoice Program gets called, the following activity takes place is part of execution process. When imported transactions are processed through the AutoInvoice program, the following
events happen:
• Line, accounting, and sales credit information populates three Receivables interface
tables.
• Transaction lines are ordered and grouped by the grouping and line ordering rules
defined.
• If the Contingencies for the Invoice lines are passed in AR_INTERFACE_CONTS_ALL
table, then a contingency is created on the appropriate line. Additionally, In the process
of creating invoice line via Autoinvoice, all the enabled rules for Revenue Contingencies
will get evaluated. If the matching criteria of the rules are met, the default contingencies
are assigned to the invoice line. The Revenue Management Engine will immediately
defer revenue for invoice lines that have contingencies assigned.
• Transaction is stamped with legal entity information. Because each transaction can only
belong to one legal entity, when multiple legal entities exist the system optionally
defaults a legal entity from the transaction type or transaction batch source, if defined. If
legal entity defaults are not defined, then the user must enter the legal entity manually.
AutoInvoice performs the following payment terms validations for imported balance
forward billing (BFB) transactions:
- Transactions with balance forward billing payment terms have balance forward
billing enabled at the account and site profiles.
- Transactions with non-balance forward billing payment terms for balance forward
billing customers have the Override Terms check box selected.
- Transactions with balance forward billing payment terms having the External
billing cycle have a billing date.
• Tax is calculated by Oracle E-Business Tax.
• GL (General Ledger) date is determined by the accounting rules or, if rules are not used,
from the ship or sales order date.
• GL accounts are assigned using AutoAccounting, except where accounting is provided on
the transaction.
• Tax, freight, commitments, and credit memos are linked to transaction lines based on the
Reference ID or Reference flexfield.
• All transactions are batched by batch source name and request ID.
• Validated lines are used to create the transactions.
• Error lines remain in the Interface Table for correction.
How Data is flowing?
Select, insert and update and delete take place on certain tables once it is logged out.
Selects– RA_INTERFACE_LINES_ALL
– RA_INTERFACE_DISTRIBUTIONS_ALL
– RA_INTERFACE_SALESCREDITS_ALL
Updates/Insert– RA_INTERFACE_ERRORS_ALL
– RA_CUSTOMER_TRX_ALL
– RA_CUSTOMER_TRX_LINES_ALL
– AR_PAYMENT_SCHEDULES_ALL
– AR_RECEIVABLE_APPLICATIONS_ALL
Inserts– RA_INTERFACE_ERRORS_ALL
AutoInvoice Exception Handling
Records that fail validation are called ‘Exceptions’
Exceptions stay in Interface Tables which is RA_INTERFACE_ERRORS_ALL
Errors can be corrected in the Exception Handling window
Once corrections are made, Auto invoice must be resubmitted
Records that pass validation get transferred to Receivables tables
AutoInvoice Exception Handling Windows
-Interface Exception window displays exception messages associated with all invalid records
-Interface Lines window displays records that fail validation, provides an error message and can be used to correct the errors
-The Line Errors windows displays errors associated with a specific line, and can only be opened from Interface Lines window
-Interface Exceptions window displays Interface Id, Exception Type, Error Message and Invalid Value associated to the error
-Data cannot be edited in this window, but error can be viewed and corrected by clicking the Details button
-Error Message and Column name with invalid data are displayed in the Message column, and the invalid value that needs to be corrected is displayed in the Invalid Value
•Deletes all rows where interface_status =‘P’
•Ra_interface_lines
•Ra_interface_distributions
•Ra_interface_salescredits
Oracle Receivable’s Auto Invoice program will be used to import and validate Invoices.
A custom feeder program is required to transfer data from the Advantage extract files and populate the Auto Invoice interface tables (RA_INTERFACE_LINES_ALL and RA_INTERFACE_DISTRIBUTIONS_ALL).If there is need to run populate sales credit into RA_INTERFACE_SALESCREDITS_ALL table.
When run, AutoInvoice produces the AutoInvoice Execution Report and the AutoInvoice Validation Report. Any entries which failed validation can be reviewed in Oracle Receivables’ AutoInvoice Interface Exceptions window. Depending on the error, changes may need to be made in Receivables, the feeder program or the imported records in the interface tables.
How Autoinvoice Execution worksNormally, Auto Invoice can be divided into three major phases
Pre-grouping: here the validates all of the line level data takes place
Grouping: groups lines based on the grouping rules and validates header level data
Transfer :validates information that exists in Receivables tables
What happen when AutoInvoice run?
Once the Auto invoice Program gets called, the following activity takes place is part of execution process. When imported transactions are processed through the AutoInvoice program, the following
events happen:
• Line, accounting, and sales credit information populates three Receivables interface
tables.
• Transaction lines are ordered and grouped by the grouping and line ordering rules
defined.
• If the Contingencies for the Invoice lines are passed in AR_INTERFACE_CONTS_ALL
table, then a contingency is created on the appropriate line. Additionally, In the process
of creating invoice line via Autoinvoice, all the enabled rules for Revenue Contingencies
will get evaluated. If the matching criteria of the rules are met, the default contingencies
are assigned to the invoice line. The Revenue Management Engine will immediately
defer revenue for invoice lines that have contingencies assigned.
• Transaction is stamped with legal entity information. Because each transaction can only
belong to one legal entity, when multiple legal entities exist the system optionally
defaults a legal entity from the transaction type or transaction batch source, if defined. If
legal entity defaults are not defined, then the user must enter the legal entity manually.
AutoInvoice performs the following payment terms validations for imported balance
forward billing (BFB) transactions:
- Transactions with balance forward billing payment terms have balance forward
billing enabled at the account and site profiles.
- Transactions with non-balance forward billing payment terms for balance forward
billing customers have the Override Terms check box selected.
- Transactions with balance forward billing payment terms having the External
billing cycle have a billing date.
• Tax is calculated by Oracle E-Business Tax.
• GL (General Ledger) date is determined by the accounting rules or, if rules are not used,
from the ship or sales order date.
• GL accounts are assigned using AutoAccounting, except where accounting is provided on
the transaction.
• Tax, freight, commitments, and credit memos are linked to transaction lines based on the
Reference ID or Reference flexfield.
• All transactions are batched by batch source name and request ID.
• Validated lines are used to create the transactions.
• Error lines remain in the Interface Table for correction.
How Data is flowing?
Select, insert and update and delete take place on certain tables once it is logged out.
Selects– RA_INTERFACE_LINES_ALL
– RA_INTERFACE_DISTRIBUTIONS_ALL
– RA_INTERFACE_SALESCREDITS_ALL
Updates/Insert– RA_INTERFACE_ERRORS_ALL
– RA_CUSTOMER_TRX_ALL
– RA_CUSTOMER_TRX_LINES_ALL
– AR_PAYMENT_SCHEDULES_ALL
– AR_RECEIVABLE_APPLICATIONS_ALL
Inserts– RA_INTERFACE_ERRORS_ALL
AutoInvoice Exception Handling
Records that fail validation are called ‘Exceptions’
Exceptions stay in Interface Tables which is RA_INTERFACE_ERRORS_ALL
Errors can be corrected in the Exception Handling window
Once corrections are made, Auto invoice must be resubmitted
Records that pass validation get transferred to Receivables tables
AutoInvoice Exception Handling Windows
-Interface Exception window displays exception messages associated with all invalid records
-Interface Lines window displays records that fail validation, provides an error message and can be used to correct the errors
-The Line Errors windows displays errors associated with a specific line, and can only be opened from Interface Lines window
-Interface Exceptions window displays Interface Id, Exception Type, Error Message and Invalid Value associated to the error
-Data cannot be edited in this window, but error can be viewed and corrected by clicking the Details button
-Error Message and Column name with invalid data are displayed in the Message column, and the invalid value that needs to be corrected is displayed in the Invalid Value
No comments:
Post a Comment