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
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
No comments:
Post a Comment