Results for “pa_alloc_txn_details”

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

Overview

PA_ALLOC_TXN_DETAILS is a transaction table in the Oracle Projects (PA) schema that stores the individual detail records produced when an allocation run is executed. Allocation in Oracle Projects is the mechanism by which indirect costs, such as overhead, general and administrative charges, or burden, are redistributed from a source project, task, or expenditure organization to one or more target projects and tasks according to a defined allocation rule. Each row in PA_ALLOC_TXN_DETAILS captures one such generated allocation transaction together with the amounts, period identifiers, and source references that justify the calculation.

The object is owned by the PA schema and is documented as VALID in ETRM for release 12.1.1 and 12.2.2. The documented physical schema contains 41 columns. Heuristic Data Vault classification places this table as satellite-leaning: it is a transaction-level, insert-oriented table whose rows carry descriptive and measure attributes (amounts, codes, period identifiers) around a unique surrogate identifier, rather than serving as a pure hub of business keys or a pure link between two hubs. From a modeling perspective, it is best treated as a satellite or fact-like detail table hanging off the allocation run and allocation rule, with foreign keys to the affected project, task, and expenditure entities.

Key Information Stored

The surrogate primary key is ALLOC_TXN_ID, enforced by the PA_ALLOC_TXN_DETAILS_PK constraint and also by the unique index PA_ALLOC_TXN_DETAILS_U1. This identifier distinguishes each allocation transaction and is the column referenced by dependent child tables. Among the most operationally significant columns are the following:

• RUN_ID — links the transaction to the allocation run that produced it, recorded in PA_ALLOC_RUNS_ALL.
• RULE_ID — identifies the allocation rule from PA_ALLOC_RULES_ALL used for the run.
• TRANSACTION_TYPE and FISCAL_YEAR / QUARTER_NUM / PERIOD_NUM / RUN_PERIOD — classify the transaction and anchor it in the accounting calendar period.
• PROJECT_ID, TASK_ID, and EXPENDITURE_TYPE — identify the target project, task, and expenditure type receiving the allocated amount.
• EXPENDITURE_ID and EXPENDITURE_ITEM_ID — reference the source expenditure and expenditure item that formed the basis of the allocation.
• TOTAL_ALLOCATION, PREVIOUS_ALLOCATION, CURRENT_ALLOCATION — the running, prior-period, and current-period allocated amounts that support reconciliation and audit.
• REJECTION_CODE and STATUS_CODE — indicate whether the transaction was accepted, rejected, or processed, and the reason for any rejection.
• CINT_SOURCE_TASK_ID, CINT_EXP_ORG_ID, CINT_RATE_MULTIPLIER, CINT_PRIOR_BASIS_AMT, CINT_CURRENT_BASIS_AMT — source task, expenditure organization, rate multiplier, and prior/current basis amounts used in the allocation computation.
• IND_RATE_SCH_REVISION_ID — links to the indirect rate schedule revision applied, where applicable.

The standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE10 descriptive flexfield columns are also present.

Common Use Cases and Queries

Typical usage centers on allocation audit, period close reconciliation, and reporting on indirect cost distribution. A common pattern retrieves all transactions for a specific run and joins back to the rule definition:

• Reconciliation query: select ALLOC_TXN_ID, PROJECT_ID, TASK_ID, EXPENDITURE_TYPE, TOTAL_ALLOCATION, CURRENT_ALLOCATION from PA_ALLOC_TXN_DETAILS where RUN_ID = :run_id, joining to PA_ALLOC_RUNS_ALL for run metadata.
• Period reporting: filter by FISCAL_YEAR, PERIOD_NUM, and RUN_PERIOD to review allocations posted within a given accounting period.
• Exception review: select rows where REJECTION_CODE is not null or STATUS_CODE indicates a non-accepted state, to investigate failed or partial allocations.
• Source traceability: join EXPENDITURE_ITEM_ID to PA_EXPENDITURE_ITEMS_ALL and EXPENDITURE_ID to PA_EXPENDITURES_ALL to trace which source costs drove the allocation.
• Rate audit: join IND_RATE_SCH_REVISION_ID to PA_IND_RATE_SCH_REVISIONS to confirm the rate revision applied to the computed amounts.

Reports are frequently built on CINT_PRIOR_BASIS_AMT and CINT_CURRENT_BASIS_AMT to show the basis amounts, and on TOTAL_ALLOCATION to demonstrate the cumulative allocation for a project or task across periods.

Related Objects

PA_ALLOC_TXN_DETAILS participates in a well-defined dependency network through its foreign keys and dependent children. The most significant related objects are:

• PA_ALLOC_RUNS_ALL — parent allocation run header, joined on RUN_ID.
• PA_ALLOC_RULES_ALL — allocation rule definition, joined on RULE_ID.
• PA_PROJECTS_ALL — target project, joined on PROJECT_ID.
• PA_TASKS — target task (TASK_ID) and source task (CINT_SOURCE_TASK_ID).
• PA_EXPENDITURE_ITEMS_ALL — source expenditure item, joined on EXPENDITURE_ITEM_ID.
• PA_EXPENDITURES_ALL — source expenditure header, joined on EXPENDITURE_ID.
• HR_ALL_ORGANIZATION_UNITS — expenditure organization context via CINT_EXP_ORG_ID.
• PA_IND_RATE_SCH_REVISIONS — indirect rate schedule revision joined on IND_RATE_SCH_REVISION_ID.
• PA_CINT_SOURCE_DETAILS — child detail table referencing this table through ALLOC_TXN_ID.

The presence of PA_ALLOC_TXN_DETAILS_EFC.ALLOC_TXN_ID as a referencing column further indicates the table is included in the E-Business Tax or projects cross-reference structure, and any purge or archival process must account for these dependent references.