Results for “current_allocation”

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

Overview

PA_ALLOC_TXN_DETAILS_EFC is a table in the PA (Projects) schema within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to archive allocation transaction detail rows at the point of an EFC (Enterprise Financial Consolidation) switch. As allocations are processed against project and expenditure items, the transactional detail associated with each allocation run is preserved in this archive table so that pre-switch allocation history remains available for reconciliation, audit, and reporting after the consolidation cutover. The table is reported as VALID in the ETRM 12.2.2 metadata and carries eight documented physical columns.

From a data-modeling perspective, the mined foreign-key structure classifies this object heuristically as standalone. This is a modeling suggestion rather than a normative Data Vault designation; because the table is archival in nature and holds a denormalized snapshot of allocation amounts and run attributes, it behaves less like a rigid hub, link, or satellite and more like a flat history/archive store. Its single documented foreign key (ALLOC_TXN_ID referencing PA_ALLOC_TXN_DETAILS) nonetheless gives it a dependent satellite-like relationship to the live allocation transaction detail table.

Key Information Stored

The eight documented columns capture the identity of the allocation run, the rule applied, the accounting context, and the three-way allocation amount breakdown. The most significant columns are:

• ALLOC_TXN_ID — The allocation transaction identifier. This is the documented foreign key back to PA_ALLOC_TXN_DETAILS and serves as the strongest business-key candidate for joining archived rows to their live counterparts.
• RUN_ID — Identifies the allocation run under which the archived transaction was generated, enabling grouping by processing event.
• RULE_ID — The allocation rule applied to produce the transaction, supporting rule-level analysis and audit of allocation logic.
• SET_OF_BOOKS_ID — The ledger context for the allocation, critical for multi-organization and multi-ledger reporting.
• TOTAL_ALLOCATION — The cumulative allocated amount attributable to the archived transaction.
• PREVIOUS_ALLOCATION — The allocation amount carried forward from prior processing, used for variance tracking.
• CURRENT_ALLOCATION — The incremental allocation amount produced by the current run.
• CREATION_DATE — The timestamp at which the archive row was created, supporting period-based reporting and retention management.

The metadata documents no separate surrogate primary key beyond ALLOC_TXN_ID, and no unique indexes are enumerated. In practice, ALLOC_TXN_ID combined with RUN_ID and SET_OF_BOOKS_ID is the most reliable composite business key for de-duplication and joining.

Common Use Cases and Queries

Typical scenarios include reconciling allocation balances before and after an EFC switch, auditing which rules drove specific allocation amounts, and reporting allocation history by ledger or project period. A representative query joining the archive to its live source is:

• SELECT e.ALLOC_TXN_ID, e.RUN_ID, e.RULE_ID, e.TOTAL_ALLOCATION, e.CURRENT_ALLOCATION FROM PA.PA_ALLOC_TXN_DETAILS_EFC e WHERE e.SET_OF_BOOKS_ID = :ledger AND e.CREATION_DATE BETWEEN :from_date AND :to_date;
• Variance analysis: SELECT RUN_ID, RULE_ID, SUM(CURRENT_ALLOCATION - PREVIOUS_ALLOCATION) FROM PA.PA_ALLOC_TXN_DETAILS_EFC GROUP BY RUN_ID, RULE_ID;
• Archive-to-live reconciliation: SELECT a.ALLOC_TXN_ID, e.TOTAL_ALLOCATION FROM PA.PA_ALLOC_TXN_DETAILS a, PA.PA_ALLOC_TXN_DETAILS_EFC e WHERE a.ALLOC_TXN_ID = e.ALLOC_TXN_ID;

These patterns are useful for period-close validation, EFC migration verification, and retention reporting. Because the table is archival, queries are typically read-only.

Related Objects

• PA_ALLOC_TXN_DETAILS — the live allocation transaction detail table and the documented FK target via ALLOC_TXN_ID.
• PA_ALLOC_RUNS (or equivalent run header) — joins on RUN_ID for run context.
• Allocation rule definition tables (for example, the PA allocation rule / rule-detail objects) — join on RULE_ID.
• GL_SETS_OF_BOOKS / ledger objects — join on SET_OF_BOOKS_ID for ledger naming.
• PA allocation concurrent programs and their reporting views that consume archived allocation amounts.
• Project and expenditure item tables that provide the underlying source transactions feeding allocations.

Because documentation is limited, the FK relationship to PA_ALLOC_TXN_DETAILS is the authoritative dependency; other associations should be validated against the target instance.