Results for “from_acctd_amount”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_CASH_BASIS_DISTS_ALL is the Oracle Receivables (AR) table that stores the distribution of payments over revenue accounts when Cash Basis Accounting is enabled in a ledger. It is the staging and audit record for accounting entries that arise when cash is actually received against a receivable, rather than at the time the invoice is booked. In Oracle EBS 12.1.1 and 12.2.2, this table sits at the intersection of the subledger accounting flow and General Ledger transfer, providing the Receivables posting engine with the exact revenue and related account combinations that must be debited or credited upon payment application.

The table is owned by the AR schema and is documented in ETRM with 33 columns in 12.2.2. Because its structure is dominated by transactional distribution rows that reference a parent application, and because it carries a small natural/business key plus multiple contextual attributes, the heuristic Data Vault classification is satellite-leaning. This is a modeling suggestion only: the physical design remains a standard Oracle EBS subledger distribution table rather than an actual Data Vault construct.

Key Information Stored

The surrogate primary key is CASH_BASIS_DISTRIBUTION_ID, enforced by AR_CASH_BASIS_DISTRIBUTIONS_PK and also by unique index AR_CASH_BASIS_DISTRIBUTIONS_U1. A second unique constraint, AR_CASH_BASIS_DISTRIBUTIONS_UK1, is defined on the combination of RECEIVABLE_APPLICATION_ID, SOURCE, SOURCE_ID, and TYPE, which together act as a business-key candidate that ties each distribution row back to a single application event.

• CASH_BASIS_DISTRIBUTION_ID — surrogate primary key for the distribution row.
• RECEIVABLE_APPLICATION_ID / RECEIVABLE_APPLICATION_ID_CASH — foreign keys to AR_RECEIVABLE_APPLICATIONS_ALL, identifying the payment application and its cash basis counterpart.
• PAYMENT_SCHEDULE_ID — foreign key to AR_PAYMENT_SCHEDULES_ALL, linking the distribution to the underlying installment.
• CODE_COMBINATION_ID — foreign key to GL_CODE_COMBINATIONS, the revenue or related account combination being distributed.
• POSTING_CONTROL_ID — foreign key to AR_POSTING_CONTROL, governing posting status.
• GL_DATE / GL_POSTED_DATE — accounting date and the date the entry was posted to General Ledger.
• CURRENCY_CODE / BASE_CURRENCY — transaction and ledger base currencies, both referencing FND_CURRENCIES.
• AMOUNT / ACCTD_AMOUNT — entered and accounted amounts of the distribution.
• FROM_AMOUNT / FROM_ACCTD_AMOUNT — source amounts carried into the cash basis distribution.
• LEDGER_ID — identifies the ledger for the accounting entry, referenced through FND_CURRENCIES as documented.
• SOURCE, SOURCE_ID, TYPE — identify the originating transaction and the nature of the distribution, and form the business-key candidate with RECEIVABLE_APPLICATION_ID.
• REF_ACCOUNT_CLASS, REF_CUSTOMER_TRX_ID, REF_CUSTOMER_TRX_LINE_ID, REF_CUST_TRX_LINE_GL_DIST_ID, REF_LINE_ID — the reference chain back to the invoice, line, and original GL distribution that generated the cash basis entry.
• ORG_ID — operating unit identifier supporting multi-org reporting.
• ACTIVITY_BUCKET — supports receivables aging and reporting bucket assignment.

Common Use Cases and Queries

The primary operational use case is reconciliation of cash basis accounting entries before and after transfer to General Ledger. Report developers join the table to GL_CODE_COMBINATIONS to obtain the revenue account flexfield values and to AR_PAYMENT_SCHEDULES_ALL to trace the installment. A typical pattern is:

• Querying unposted distributions by joining AR_POSTING_CONTROL on POSTING_CONTROL_ID to find rows where GL_POSTED_DATE is null.
• Reconciling cash basis revenue by summing AMOUNT and ACCTD_AMOUNT grouped by CODE_COMBINATION_ID, GL_DATE, and LEDGER_ID.
• Auditing multi-currency activity by joining FND_CURRENCIES on both CURRENCY_CODE and BASE_CURRENCY.
• Drilling from a payment application to its cash basis entries using RECEIVABLE_APPLICATION_ID and the UK1 key columns.
• Reporting by operating unit through ORG_ID and by ledger through LEDGER_ID.

Because the table holds accounted distributions for multiple ledgers, queries should always filter on LEDGER_ID and GL_DATE to avoid cross-ledger aggregation errors, and should join to AR_RECEIVABLE_APPLICATIONS_ALL rather than relying on denormalized columns.

Related Objects

• AR_RECEIVABLE_APPLICATIONS_ALL — parent applications referenced by RECEIVABLE_APPLICATION_ID and RECEIVABLE_APPLICATION_ID_CASH.
• AR_PAYMENT_SCHEDULES_ALL — installment header joined via PAYMENT_SCHEDULE_ID.
• GL_CODE_COMBINATIONS — account combination for each distribution via CODE_COMBINATION_ID.
• AR_POSTING_CONTROL — posting status via POSTING_CONTROL_ID.
• FND_CURRENCIES — currency validation for CURRENCY_CODE and BASE_CURRENCY.
• AR_MC_CASH_BASIS_DISTS_ALL — multi-currency companion child table referencing CASH_BASIS_DISTRIBUTION_ID.