How Autoinvoice Grouping Rules Work

- Oracle-Developer.com -

How Autoinvoice Grouping Rules Work
Comment on this Topic

PURPOSE
-----------

To add to the documentation on Autoinvoice Grouping

SCOPE & APPLICATION
-------------------------

This article is intended for those supporting and developing scripts which
populate the autoinvoice interface tables.

How AutoInvoice Grouping Works
------------------------------------

Grouping is used to prevent autoinvoice lines from combining in a single
invoice. Other words you use grouping rules to determine how you want
autoinvoice lines to split into individual transactions. For example, you
may want to prevent order lines from two different sales orders from grouping
on the same invoice.

Grouping cannot be used to force rows in AutoInvoice together. For example, if
AutoInvoice is splitting freight rows from the revenue rows for a given sales
order, you may not force these rows together by adding an optional grouping
attribute to the grouping rule. Further investigation will be required to
determine which mandatory grouping attribute or optional grouping attribute
is causing the rows to split into different invoices.

The mandatory grouping attributes are columns on ra_interface_lines_all,
which if different for any row, will cause AutoInvoice to split rows to
separate transactions. These columns are mandatory and cannot be removed
from the grouping rules. Many of these columns can be found on the
transaction header.

The optional grouping attributes may be added in the grouping rule
definition. If added to the grouping rule definition they behave the same
as mandatory grouping attributes.

The following columns on ra_interface_lines_all are mandatory grouping columns:

agreement_id comments
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
document_number document_number_sequence_id
gl_date header_attribute1-15
header_attribute_category initial_customer_trx_id
internal_notes invoicing_rule_id
orig_system_bill_address_id orig_system_bill_contact_id
orig_system_bill_customer_id orig_system_ship_address_id
orig_system_ship_contact_id orig_system_ship_customer_id
orig_system_sold_customer_id orig_system_batch_name
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
term_id territory_id
trx_date trx_number

In addition, if you use the invoice transaction flexfield then the
interface_line_attributes which are defined for your invoice transaction
flexfield will become mandatory grouping columns.

Optional grouping columns include but are not limited to the following:

accounting_rule_duration accounting_rule_id
attribute1-15 attribute_category
interface_line_attribute1-15 interface_line_context
inventory_item_id reference_line_id
rule_start_date sales_order
sales_order_date sales_order_line
sales_order_revision sales_order_source
tax_code tax_rate

If your transaction lines are not grouping as expected you need to analyze
the mandatory and optional group columns on ra_interface_lines_all.

Comment on How Autoinvoice Grouping Rules Work

Owned and Operated by Varun Jain, Inc, an Oracle Consulting Firm