AutoInvoice Grouping Rules

When Data is populated into the AR interface and we run the Auto Invoice import Program , Oracle will process the data in the interface and Create invoices for them .

Eg : If we have 10 records in the Ar interface table and we know that all these records belong to 1 invoice then Oracle then when the AutoInvoice import program runs it should group these 10 lines to a Single invoice header . this grouping is done by Oracle on the basis of the Grouping Rules.

Grouping rules specify which columns of the AR Interface (ra_interface_lines_all) when grouped together will form 1 set of records , this Global set will become the invoice header and the individual lines will become the invoice lines.

Oracle has specified a set of Columns in Oracle R12 as Mandatory Grouping columns i.e. grouping will happen based on these columns and in addition users can specify additional Columns by creating different grouping rules and attaching it to the invoice batch source.

Below is the of columns that Oracle specifies as mandatory grouping columns

AGREEMENT_ID
APPLICATION_ID
BILLING_DATE
COMMENTS
CONS_BILLING_NUMBER
CONTRACT_ID
CONVERSION_DATE
CONVERSION_RATE
CONVERSION_TYPE
CREDIT_METHOD_FOR_ACCT_RULE
CREDIT_METHOD_FOR_INSTALLMENTS
CURRENCY_CODE
CUSTOMER_BANK_ACCOUNT_ID
CUST_TRX_TYPE_ID
DEFAULT_TAXATION_COUNTRY
DOCUMENT_NUMBER
DOCUMENT_NUMBER_SEQUENCE_ID
DOCUMENT_SUB_TYPE
GL_DATE
HEADER_ATTRIBUTE1-15
HEADER_ATTRIBUTE_CATEGORY
HEADER_GDF_ATTRIBUTE1-30
HEADER_GDF_ATTR_CATEGORY
INITIAL_CUSTOMER_TRX_ID
INTERNAL_NOTES
INVOICING_RULE_ID
LEGAL_ENTITY_ID
ORIG_SYSTEM_BILL_ADDRESS_ID
ORIG_SYSTEM_BILL_CONTACT_ID
ORIG_SYSTEM_BILL_CUSTOMER_ID
ORIG_SYSTEM_SOLD_CUSTOMER_ID
PAYMENT_ATTRIBUTES
ORIG_SYSTEM_BATCH_NAME
PAYMENT_SET_ID
PREVIOUS_CUSTOMER_TRX_ID
PRIMARY_SALESREP_ID
PRINTING_OPTION
PURCHASE_ORDER
PURCHASE_ORDER_DATE
PURCHASE_ORDER_REVISION
REASON_CODE
RECEIPT_METHOD_ID
RELATED_CUSTOMER_TRX_ID
SET_OF_BOOKS_ID
TAXED_UPSTREAM_FLAG
TERM_ID
TERRITORY_ID
TRX_DATE
TRX_NUMBER

when running Autoinvoice oracle will perform a grouping based on these columns to determine how many invoices need to be created , In addition if any custom Grouping Rules are specified those columns will also be included.

Many a times you might be facing the issue that you expected the lines to create 1 single invoice but multiple invoices got created , it is because of the Grouping rules and whenever you face such an issue check the Grouping Rules.

A common issue faced is the Error : Duplicate Invoice number , If you are supplying Invoice number in the AR interface and have not enabled Duplicate transactions Numbers in the setup then in case the grouping rules of an invoice face Auto Invoice will give the error Duplicate Invoice Number.

Make sure to check the grouping rules thoroughly

Auto application of Credit Note to Invoice Using AutoInvoice

When Creating a Credit note by Auto Invoice import Oracle provides the option of auto application of a Credit Note to an invoice i.e. When you are creating a credit note as soon as a credit note is created it will be immediately applied to an AR invoice.
This functionality can be used by by populating the reference_line_attribute columns of ra_interface_lines_all tables By populating the reference line_id or the combination of reference line_context and reference line attributes which correspond to a given AR invoice line you can apply the CM line being created to an existing Invoice.
Ensure that the CM line which you want to apply has an amount less than or equal to the invoice line open amount else you will get an error by Auto Invoice if over application is not enabled.
This is an efficient way of Creating credit notes and also applying them to Open invoices/Debit notes in the system if the information of application is available beforehand

AutoInvoice Import Error : Tax lines with the same Tax Regime and Tax cannot be allocated to the same transaction line more than once.

When importing invoices via the AR Interfaces , in cases where 1 invoice line is associated to multiple tax lines Oracle can throw an error : Tax lines with the same Tax Regime and Tax cannot be allocated to the same transaction line more than once if the TAX setup is incorrect.

For 1 invoice lines we will be having 2 or more tax lines each having its own tax_rate_codes.

For each of these tax rates we cannot have the same combination of regime and Tax. Multiple tax allocations is only possible if tax lines belong to combination of different regimes and tax.

In case of such an issue the TAX setups need to be checked and corrective measures need to be taken

AutoInvoice Line Transaction flex field Error

When importing invoices by the Autoinvoice Import Program , many times we are faced with the error : Please provide a value for the line transaction flexfield.
If we check the setup we see that even though the flexfield has been enabled in the setup the Requeired flag is not checked. How ever Auto invoice when importing the invoice does not check for the required flag being set or not. If the Flexfield is enabled Oracle expects a value to be provided in the interface if the value is not provided the record will be errored out in import.

Moreover the combination of the flexfield values need to be unique , else we will get the error : This line has the same transaction flexfield as another row in the interface table.  For each transaction line, the
               combination of interface_line_context and interface_line_attribute values must be unique

AutoInvoice Error : The supplied unit of measure and the primary unit of measure of your system item must share the same unit of measure class

When Importing Data via AutoInvoice we get an error : The supplied unit of measure and the primary unit of measure of your system item must share the same unit of measure class

This error occurs due to the below reasons:

The item has not been assigned to the warehouse for which the data is trying to be imported.

The item UOM definition and the setup are different.

Thanks

Auto Invoice Error : The supplied unit of measure and the primary unit of measure of your system item must share the same unit of

When importing invoice from ra_interface_lines_All table the user can be faced with an error : The supplied unit of measure and the primary unit of measure of your system item must share the same unit of.
This error message is generally reported because of either of the below reason:

1. The Unit of Measure specified for the item in ra_interface_lines_all is different from what is specified in the item setup
2. The item is not assigned to the warehouse for which the invoice line is being tried to be imported