This table stores invoice, debit memo, commitment, and credit memo
header information. Each row includes general invoice information
such as customer, transaction type, and printing instructions. You need
one row for each invoice, debit memo, commitment, and credit memo
you create in Oracle Receivables.
Invoices, debit memos, credit memos,and commitments are all distinguished by their transaction types stored
in RA_CUST_TRX_TYPES_ALL. If you entered a credit memo,
PREVIOUS_CUSTOMER_TRX_ID stores the customer transaction
identifier of the invoice you credited. In the case of on account credits,
which are not related to any invoice at creation,
PREVIOUS_CUSTOMER_TRX_ID is null. If you created an invoice
against a commitment, Oracle Receivables stores the customer
transaction identifier of the commitment in
INITIAL_CUSTOMER_TRX_ID, otherwise it is null.
COMPLETE_FLAG stores â€™Yâ€™ for Yes and â€™Nâ€™ for No to indicate if your
invoice is complete.
When you complete an invoice, Oracle Receivables
creates your payment schedules and updates any commitments against
this invoice. Before an invoice can be completed, it must have at least
one invoice line, revenue records must exist for each line and add up to
the line amount, and a sales tax record must exist for each line.
SOLD_TO_CUSTOMER_ID, SOLD_TO_SITE_USE_ID,BILL_TO_CUSTOMER_ID, BILL_TO_SITE_USE_ID,
SHIP_TO_SITE_USE_ID, PRINTING_OPTION, PRINTING_PENDING,
TERM_ID, REMIT_TO_ADDRESS_ID, PRIMARY_SALES_REP_ID, and
INVOICE_CURRENCY_CODE are required even though they are null
allowed. The primary key for this table is CUSTOMER_TRX_ID.
This table stores information about invoice, debit memo, credit memo,
and commitment lines. For example, an invoice can have one line for
Product A and another line for Product B. You need one row for each
line. Invoice, debit memo, credit memo, and commitment lines are
distinguished by the transaction type of the corresponding
Also, credit memos are required to
have a value in PREVIOUS_CUSTOMER_TRX_LINE_ID, except on
account credits which are not related to specific invoices/invoice lines at
creation time, will not have values in this column.
QUANTITY_ORDERED stores the amount of product ordered.
QUANTITY_INVOICED stores the amount of product invoiced. For
invoices entered through the window, QUANTITY_ORDERED and
QUANTITY_INVOICED must be the same.
For invoices imported through AutoInvoice, QUANTITY_ORDERED and
QUANTITY_INVOICED can be different. If you enter a credit memo,
QUANTITY_CREDITED stores the amount of product credited.
UOM_CODE stores the unit of measure code as defined in
MTL_UNITS_OF_MEASURE. UNIT_STANDARD_PRICE stores the list
price per unit for this transaction line. UNIT_SELLING_PRICE stores
the selling price per unit for this transaction line. For transactions
imported through AutoInvoice, UNIT_STANDARD_PRICE and
UNIT_SELLING_PRICE can be different. DESCRIPTION,
TAXING_RULE, QUANTITY_ORDERED, UNIT_STANDARD_PRICE,
UOM_CODE, and UNIT_SELLING_PRICE are required even though
they are null allowed.
LINE_TYPE differentiates between the different types of lines that are stored in this table. LINE points to regular invoice
lines that normally refer to an item. TAX signifies that this is a tax line.
The column LINK_TO_CUST_TRX_LINE_ID references another row in
this table that is the invoice line associated with the row of type TAX.
FREIGHT works the same way as TAX but there you can have at most
one FREIGHT type l ine per invoice line of type LINE. You can also
have one line of type FREIGHT that has a null LINK_TO_CUST_TRX_LINE_ID (and this is referred to as header level
freight). CHARGES works just like the LINE type. A line_type of â€™CBâ€™ is
created for a Chargeback line. For every row in this table that belongs to
a complete transaction (where RA_CUSTOMER_TRX.COMPLETE_FLAG = Y), there must be at least
one row in the table RA_CUST_TRX_LINE_GL_DIST (which stores
accounting information), even for nonâ€“postable transactions. The
primary key for this table is CUSTOMER_TRX_LINE_ID.