Results for “first_posted_record_flag”

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

Overview

AR.AR_TRANSACTION_HISTORY_ALL is a core Oracle Receivables (AR) table that stores the transactional life cycle of a receivable transaction. Each row captures a discrete historical event or state change associated with a transaction — creation, adjustment, posting, application, and related accounting milestones — providing a longitudinal audit trail rather than a single current-state record. In Oracle EBS 12.1.1 and 12.2.2, it acts as the bridge between the base transaction in RA_CUSTOMER_TRX_ALL and the downstream accounting, distribution, and application activity that flows through the AR subledger.

The object is classified in the metadata as VALID under the AR schema, owned by the Receivables product. Its heuristic Data Vault classification is hub-leaning, mined from the foreign-key structure. From a modeling perspective, this suggests the table behaves primarily as a central hub of transaction-history identities, with satellite-style descriptive and status attributes and link-style relationships to adjustments, distributions, and receivable applications. This classification should be treated as a modeling suggestion rather than a documented Oracle design statement.

Key Information Stored

The table contains 47 documented columns. The surrogate primary key is TRANSACTION_HISTORY_ID, enforced by constraint AR_TRANSACTION_HISTORY_PK and by unique index AR_TRANSACTION_HISTORY_U1. The most significant business columns include:

• CUSTOMER_TRX_ID — the parent transaction this history row belongs to, linking back to the customer transaction.
• STATUS and EVENT — the state and event type that define the life-cycle step recorded.
• TRX_DATE and GL_DATE — transaction date and accounting date for the event.
• CURRENT_RECORD_FLAG, CURRENT_ACCOUNTED_FLAG, POSTABLE_FLAG, FIRST_POSTED_RECORD_FLAG — flag columns identifying the active, accounted, postable, and first-posted states.
• POSTING_CONTROL_ID, GL_POSTED_DATE — posting control linkage and the date the record was posted to the general ledger.
• PRV_TRX_HISTORY_ID — a self-referencing predecessor pointer that chains history rows in sequence.
• BATCH_ID — grouping identifier for batch processing context.
• MRC_POSTING_CONTROL_ID, MRC_GL_POSTED_DATE, MRC_CREATED_FROM — multi-reporting-currency equivalents of the posting and origination attributes.
• ORG_ID — the operating unit that owns the record, supporting multi-org access.
• MATURITY_DATE and EVENT_ID — maturity timing and event identity for downstream consumers.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE flex columns are also present. The documented foreign key to AR_POSTING_CONTROL via POSTING_CONTROL_ID anchors the record to its posting run.

Common Use Cases and Queries

Typical scenarios include reconstructing a transaction's audit trail, identifying postable versus posted events, and reporting on accounting activity by GL date or operating unit. A frequent pattern joins the history table to the base transaction and posting control:

• Life-cycle audit: SELECT th.TRANSACTION_HISTORY_ID, th.CUSTOMER_TRX_ID, th.STATUS, th.EVENT, th.TRX_DATE, th.GL_DATE FROM AR_TRANSACTION_HISTORY_ALL th WHERE th.CUSTOMER_TRX_ID = :trx_id ORDER BY th.CREATION_DATE;
• Unposted / postable events: filter on POSTABLE_FLAG = 'Y' and GL_POSTED_DATE IS NULL.
• Current record lookup: filter on CURRENT_RECORD_FLAG = 'Y' to isolate the latest effective history row per transaction.
• Posting control reconciliation: join to AR_POSTING_CONTROL on POSTING_CONTROL_ID to reconcile history events against posting runs.
• Multi-org reporting: constrain by ORG_ID to respect operating unit security.

Related Objects

The table participates in several documented foreign-key relationships. It references AR_POSTING_CONTROL through POSTING_CONTROL_ID. Conversely, the following objects reference it, and these form the primary join paths for reporting and reconciliation:

• AR_ADJUSTMENTS_ALL via LINK_TO_TRX_HIST_ID — ties adjustments to the originating history event.
• AR_DISTRIBUTIONS_ALL via SOURCE_ID — accounting distributions generated from history rows.
• AR_MC_DISTRIBUTIONS_ALL via SOURCE_ID — multi-currency distribution equivalents.
• AR_MC_TRANSACTION_HISTORY via TRANSACTION_HISTORY_ID — reporting-currency history records.
• AR_RECEIVABLE_APPLICATIONS_ALL via LINK_TO_TRX_HIST_ID — cash application references to history events.

Additional documented referrers include FV_PYA_TRANSACTION_HISTORY, PQH_SS_APPROVAL_HISTORY, PQH_SS_STEP_HISTORY, and PQH_SS_TRANSACTION_HISTORY, each keyed on TRANSACTION_HISTORY_ID. Together these relationships establish AR_TRANSACTION_HISTORY_ALL as the hub from which adjustments, distributions, applications, and currency-converted history records derive their lineage.