Results for “dist_source_id”

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

Overview

AR_PERIOD_CLOSE_EXCPS_GT is a Receivables (AR) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas, owned by the AR schema and verified as VALID. The name suffix "GT" indicates that the object is a global temporary table. In Oracle EBS it functions as a transient staging and reporting structure used during the Receivables period-close process: rows are populated and consumed within a single session or transaction to capture accounting exceptions and distribution-level activity. Because it is a temporary table, it is not a persistent transaction-of-record store; it exists to hold intermediate results for period-close exception analysis, reconciliation, and validation activities such as the Create Accounting and revenue recognition exception reports run during period end.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. In Data Vault terms this table is best modeled as a staging area that draws from hubs and links rather than a permanent hub, link, or satellite. Its foreign-key-like references (TRANSACTION_HISTORY_ID to AR_TRANSACTION_HISTORY_ALL and LEGAL_ENTITY_ID to FV_LEGAL_ENTITIES) are inbound lookups that echo the business context of the exception records.

Key Information Stored

The documented physical schema contains 26 columns. The most significant are:

• TRANSACTION_HISTORY_ID – reference to AR_TRANSACTION_HISTORY_ALL, tying each exception row to the transaction-history event that generated it.
• CUSTOMER_TRX_ID / TRX_NUMBER – surrogate and human-readable identifier of the source transaction or receipt.
• CASH_RECEIPT_ID / RECEIPT_NUMBER – identifies the cash receipt involved when the exception concerns a receipt or application.
• ADJUSTMENT_ID / ADJUSTMENT_NUMBER – identifies the adjustment record when the exception relates to an adjustment.
• CUST_TRX_LINE_GL_DIST_ID, DIST_LINE_ID, DIST_SOURCE_ID, DIST_SOURCE_TABLE, DIST_SOURCE_TYPE – the accounting distribution context, indicating which distribution row and source object produced the exception.
• ACCOUNT_CLASS – the Receivables account class (for example REC, FREIGHT, TAX, or UNBILL) associated with the amount.
• EVENT_ID – the Subledger Accounting event reference.
• GL_DATE – the accounting date used for period-close grouping and exception reporting.
• AMOUNT_DR, AMOUNT_CR, ACCTD_AMOUNT_DR, ACCTD_AMOUNT_CR – entered and accounted debit/credit amounts, enabling balance validation.
• ORG_ID – operating unit context, critical for multi-org reporting.
• LEGAL_ENTITY_ID – reference to FV_LEGAL_ENTITIES, enabling legal-entity-level reconciliation.
• CURRENCY_CODE – currency of the entered amounts.
• CUSTOMER_ID – the customer associated with the transaction or receipt.
• PAYMENT_SCHEDULE_ID / APPLIED_PAYMENT_SCHEDULE_ID – the payment schedules created and applied, used when reconciling cash application.

There is no documented standalone surrogate primary key in the provided metadata; the table is populated for a single logical run and is normally keyed by the combination of the source identifiers (for example CUSTOMER_TRX_ID, CASH_RECEIPT_ID, ADJUSTMENT_ID, and DIST_LINE_ID) within the session.

Common Use Cases and Queries

The table is used during Receivables period close to isolate transactions that blocked accounting, failed validation, or created unbalanced accounting entries. Typical queries group exception amounts by GL date, operating unit, and legal entity to quantify exposure before closing the period. Sample patterns include:

• Listing transactions with unequal debits and credits: SELECT CUSTOMER_TRX_ID, TRX_NUMBER, SUM(AMOUNT_DR) - SUM(AMOUNT_CR) FROM AR_PERIOD_CLOSE_EXCPS_GT GROUP BY CUSTOMER_TRX_ID ...
• Summarizing exceptions by account class and currency: SELECT ACCOUNT_CLASS, CURRENCY_CODE, SUM(ACCTD_AMOUNT_DR), SUM(ACCTD_AMOUNT_CR) FROM AR_PERIOD_CLOSE_EXCPS_GT GROUP BY ...
• Joining to AR_TRANSACTION_HISTORY_ALL on TRANSACTION_HISTORY_ID to inspect the underlying event, and to FV_LEGAL_ENTITIES on LEGAL_ENTITY_ID for legal-entity reconciliation.
• Filtering by GL_DATE and ORG_ID to scope reporting to a specific period and operating unit.

Because it is a global temporary table, queries must run in the session that populated it; results are not retained across connections.

Related Objects

• AR_TRANSACTION_HISTORY_ALL – joined via TRANSACTION_HISTORY_ID.
• FV_LEGAL_ENTITIES – joined via LEGAL_ENTITY_ID.
• RA_CUSTOMER_TRX_ALL / RA_CUSTOMER_TRX_LINES_ALL – source customer transactions referenced by CUSTOMER_TRX_ID.
• AR_CASH_RECEIPTS_ALL – source receipts referenced by CASH_RECEIPT_ID.
• AR_ADJUSTMENTS_ALL – source adjustments referenced by ADJUSTMENT_ID.
• RA_CUST_TRX_LINE_GL_DIST_ALL – distribution detail referenced by CUST_TRX_LINE_GL_DIST_ID.
• AR_PAYMENT_SCHEDULES_ALL – payment schedules referenced by PAYMENT_SCHEDULE_ID and APPLIED_PAYMENT_SCHEDULE_ID.
• XLA_EVENTS – Subledger Accounting events referenced by EVENT_ID.
• AR_PERIODS / GL_PERIOD_STATUSES – period context for close validation and GL_DATE filtering.
• Receivables period-close concurrent programs and the Create Accounting process, which populate and consume this exception structure.