This table stores the accounting records for revenue, unearned revenue
and unbilled receivables for each invoice or credit memo line. Each row
includes the GL account and the amount of the accounting entry. The
AMOUNT column in this table is required even though it is null
You need one row for each accounting distribution. You must
have at least one (but you can have multiple) accounting distributions
for each invoice or credit memo line. Oracle Receivables uses this
information to post the proper amounts to your general ledger. If your
invoice or credit memo has a transaction type where Post to GL is set to
No, Oracle Receivables assigns Null to GL_DATE.
If your AutoAccounting is unable to complete your general ledger default
accounts using the AutoAccounting rules you define, incomplete
general ledger accounts are stored in CONCATENATED_SEGMENTS.
If you are importing a transaction through AutoInvoice and the general
ledger date of your transaction is in a closed accounting period,
AutoInvoice uses the general ledger date of the first open accounting
period and stores the original general ledger date in
ORIGINAL_GL_DATE. ACCOUNT_CLASS defines which type of
distribution row you are on.
The ACCOUNT_CLASS REC represents the receivable account and is for the total amount of the invoice. There
can be at most two REC rows. One that has a ACCOUNT_SET_FLAG
set to Y and the other has ACCOUNT_SET_FLAG set to N. Use
LATEST_REC_FLAG to join to the later of the two rows.
ACCOUNT_SET_FLAG is Y if this row is part of an account set. An
account set is a set of rows that represent a model distribution. Account
sets are used for invoices with rules. The rows represent how the actual
distribution rows should be created and what percentage of the actual
distribution should be allocated to each account.
For invoices with rules, the distributions are not created when the invoice is initially
created. Instead, the invoices are created when the Revenue Recognition
program is run. The primary key for this table is CUST_TRX_LINE_GL_DIST_ID.
This table stores all transactions except adjustments and miscellaneous
cash receipts. Oracle Receivables updates this table when activity occurs
against an invoice, debit memo, chargeback, credit memo, on account
credit, or receipt. Oracle Receivables groups different transactions by
the column CLASS. These classes include invoice (INV), debit memos
(DM), guarantees (GUAR), credit memos (CM), deposits (DEP),
chargebacks (CB), and receipts (PMT).
Transaction classes determine which columns in this table Oracle Receivables updates when a
transaction occurs, and whether a transaction relates to either the
RA_CUSTOMER_TRX_ALL table or the AR_CASH_RECEIPTS_ALL
table. AR_PAYMENT_SCHEDULES_ALL joins to the
RA_CUSTOMER_TRX_ALL table for nonâ€“payment transaction entries
such as the creation of credit memos, debit memos, invoices,
chargebacks, or deposits.
AR_PAYMENT_SCHEDULES_ALL uses the foreign key CUSTOMER_TRX_ID to join to the
RA_CUSTOMER_TRX_ALL table for these transactions.
AR_PAYMENT_SCHEDULES_ALL joins to the AR_CASH_RECEIPTS_ALL table for invoiceâ€“related payment
transactions using the foreign key CASH_RECEIPT_ID. When a receipt
is applied, Oracle Receivables updates AMOUNT_APPLIED, STATUS
and AMOUNT_DUE_REMAINING. STATUS changes from â€™OPâ€™ to â€™CLâ€™
for any transaction that has an AMOUNT_DUE_REMAINING value of
ACTUAL_DATE_CLOSED and GL_DATE_CLOSED are populated
with the date of the latest transaction. For a receipt, the amount due
remaining includes on account and unapplied amounts. Oracle
Receivables stores debit items such as invoices, debit memos,
chargebacks, deposits, and guarantees as positive numbers in the
AMOUNT_DUE_REMAINING and AMOUNT_DUE_ORIGINAL
columns. Credit items such as credit memos and receipts are stored as
negative numbers. In Release 10, receipts can be confirmed or not
confirmed as designated by the CONFIRMED_FLAG column. The sum
of the AMOUNT_DUE_REMAINING column for a customer for all
confirmed payment schedules reflects the current customer balance. If
this amount is negative, then this column indicates the credit balance
amount currently available for this customer. For invoices with split
terms, one record is created in RA_CUSTOMER_TRX_ALL and one
record is stored in AR_PAYMENT_SCHEDULES_ALL for each
installment. In AR_PAYMENT_SCHEDULES_ALL, DUE_DATE and
AMOUNT_DUE_REMAINING can differ for each installment of a split
term invoice. Each installment is differentiated by the
If you create a debit memo reversal when you reverse a receipt, Oracle Receivables creates a new
payment schedule record for the debit memo and fills in
REVERSED_CASH_RECEIPT_ID with the CASH_RECEIPT_ID of the
receipt that was reversed. Oracle Receivables creates a new payment
schedule record when you create a chargeback in the Receipts window.
ASSOCIATED_CASH_RECEIPT_ID is the cash receipt of the payment
you entered when you created the chargeback in this window.
GL_DATE_CLOSED indicates the general ledger date on which your
transaction was closed.
This column identifies which transactions Oracle Receivables selects when it displays current and overdue debit
items in the aging reports. The aging reports also utilize the current
balances in AMOUNT_DUE_REMAINING to display outstanding
amounts for current and overdue debit items.
ACTUAL_DATE_CLOSED gives the date on which you applied a
payment or credit to an open transaction that set
AMOUNT_DUE_REMAINING to 0 for that transaction. Oracle
Receivables uses ACTUAL_DATE_CLOSED to determine which
transactions to include when you print statements. The primary key for
this table is PAYMENT_SCHEDULE_ID, which identifies the transaction
that created the row.
Try MockupTiger to build Wireframes for your next software prototypes or initial Mockups when you are just iterating over ideas.
MockupTiger Wireframes builds instant wireframes for your Dashboards or Oracle Forms