Results for “transaction_distribution_id”

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

Overview

ARBV_REVENUE_DISTRIBUTIONS is a read-only Oracle E-Business Suite view owned by the APPS schema in the Receivables (AR) product. Its documented purpose is to present information about revenue amounts posted to the General Ledger. The view is a reporting and integration construct rather than a transactional entity: it consolidates revenue accounting distributions generated by Subledger Accounting (SLA/XLA) so that consumers can query revenue postings without navigating the normalized accounting tables directly.

The view definition is declared WITH READ ONLY, confirming that it is intended exclusively for query and extract purposes. It is registered as VALID and is available in both Oracle EBS 12.1.1 and 12.2.2. Because revenue recognition and posting in Release 12 are handled by SLA rather than by the legacy transaction tables alone, this view serves as a bridge between Receivables transaction distributions and the General Ledger journal entries to which they were transferred.

Underlying Base Objects

The view is defined over two documented base objects:

• AR_XLA_CTLGD_LINES_V (VIEW) — aliased as TLGD in the view text. This is the Subledger Accounting lines view that supplies the customer transaction line GL distribution identifiers, account class, amounts, accounted amounts, GL date, and supporting identifier and WHO columns.
• XLA_AE_HEADERS (SYNONYM) — aliased as HED. This is joined to the lines view on AE_HEADER_ID to obtain the accounting event header, which carries the GL transfer status used by the view.

The view text further filters the underlying data with the predicate TLGD.ACCOUNT_CLASS = 'REV', restricting output to revenue account class distributions. The join between the lines view and the accounting headers is an inner equi-join on AE_HEADER_ID, so only distribution lines with a corresponding accounting event header are returned.

Key Columns

The view exposes a fixed column list. Notable columns include:

• TRANSACTION_DISTRIBUTION_ID — maps to CUST_TRX_LINE_GL_DIST_ID, the unique identifier of the transaction line GL distribution.
• "_LA:ACCOUNT_TYPE" — a descriptive flexfield-style attribute resolving the account class ('REV') against AR_LOOKUPS AUTOGL_TYPE MEANING.
• DEBIT_AMOUNT / CREDIT_AMOUNT — populated via DECODE on the sign of TLGD.AMOUNT, with negative amounts mapped to the debit column as absolute values and positive amounts to the credit column.
• FUNCTIONAL_DEBIT_AMOUNT / FUNCTIONAL_CREDIT_AMOUNT — the same sign logic applied to ACCTD_AMOUNT, expressed in functional (ledger) currency.
• GENERAL_LEDGER_DATE — sourced from TLGD.GL_DATE; this is the column returned when users search for "general_ledger_date" and represents the accounting date on which the revenue distribution is posted to the General Ledger.
• "_LA:POSTED_FLAG" — derived from HED.GL_TRANSFER_STATUS_CODE, returning 'Y' when the code is 'Y' and 'N' otherwise, indicating whether the distribution has been transferred to GL.
• CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, CUST_TRX_LINE_SALESREP_ID, CODE_COMBINATION_ID, ORG_ID — identifier columns linking the distribution back to the transaction, line, salesperson, accounting flexfield combination, and operating unit.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard WHO audit columns.

Common Use Cases and Queries

Typical use cases include reconciliation of revenue posted to GL, reporting revenue by GL date, verifying GL transfer status, and feeding downstream extracts or custom reports. A representative query filtering on the search term general_ledger_date is:

• SELECT transaction_distribution_id, customer_trx_id, general_ledger_date, credit_amount, functional_credit_amount, "_LA:POSTED_FLAG" FROM apps.arbv_revenue_distributions WHERE general_ledger_date BETWEEN :p_from AND :p_to AND org_id = :p_org_id;
• SELECT customer_trx_id, SUM(functional_credit_amount) revenue FROM apps.arbv_revenue_distributions WHERE "_LA:POSTED_FLAG" = 'Y' GROUP BY customer_trx_id;

Because the view is read-only, it should be used strictly for SELECT operations; all maintenance of revenue distributions must occur through the standard Receivables and Subledger Accounting processes.