Results for “rev_offset_exp_group”

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

Overview

PA_ALLOC_RUNS_ALL is a core transaction table in the Oracle E-Business Suite Projects (PA) module, residing in the PA schema. It stores the header-level information for every allocation run executed against a project, including the allocation rule applied, the basis and target parameters, run status, and the resulting monetary amounts. In Oracle EBS 12.1.1 and 12.2.2, allocation runs distribute pooled costs, revenue, or amounts across target projects and tasks according to a defined rule, and PA_ALLOC_RUNS_ALL serves as the master record that ties each run to its detailed basis, source, transaction, exception, and missing-cost records. The table is documented with 68 columns and a single-column primary key, RUN_ID, on constraint PA_ALLOC_RUNS_ALL_PK, with a matching unique index PA_ALLOC_RUNS_U1 on RUN_ID. Under the heuristic Data Vault classification mined from its foreign key structure, this object is hub-leaning: RUN_ID behaves as a stable business key around which dependent detail and history tables cluster. Note that this classification is a modeling suggestion rather than an Oracle-delivered concept.

Key Information Stored

The surrogate primary key and sole unique business-key candidate is RUN_ID, which uniquely identifies each allocation run and is the column referenced by all dependent detail tables and by GL_AUTO_ALLOC_BATCH_HISTORY. The rule governing the run is captured by RULE_ID, a foreign key to PA_ALLOC_RULES_ALL, while RUN_PERIOD and EXPND_ITEM_DATE anchor the run in time. Basis-side parameters include BASIS_METHOD, BASIS_AMOUNT_TYPE, BASIS_BALANCE_TYPE, BASIS_BALANCE_CATEGORY, BASIS_BUDGET_TYPE_CODE, BASIS_RELATIVE_PERIOD, and BASIS_RESOURCE_LIST_ID; the financial plan basis is identified by BASIS_FIN_PLAN_TYPE_ID (foreign key to PA_FIN_PLAN_TYPES_B). Target and offset configuration is held in TARGET_EXP_TYPE, TARGET_COST_TYPE, TARGET_EXP_ORG_ID, OFFSET_EXP_TYPE, OFFSET_COST_TYPE, OFFSET_METHOD, OFFSET_PROJECT_ID, and OFFSET_TASK_ID. Outcome and control columns include RUN_STATUS, TOTAL_POOL_AMOUNT, ALLOCATED_AMOUNT, TOTAL_ALLOCATED_AMOUNT, TOTAL_OFFSETTED_AMOUNT, and the missing-source/target/offset project amounts (MISSING_SOURCE_PROJ_AMT, MISSING_TARGET_PROJ_AMT, MISSING_OFFSET_PROJ_AMT). Reversal tracking uses REVERSAL_DATE, while draft and release workflow is tracked by DRAFT_REQUEST_ID, DRAFT_REQUEST_DATE, RELEASE_REQUEST_ID, and RELEASE_REQUEST_DATE. Standard multi-org and audit columns include ORG_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. An additional foreign key on CINT_RATE_NAME references PA_IND_COST_CODES.

Common Use Cases and Queries

Typical usage includes reviewing the status and financial outcome of allocation runs for a period, reconciling pooled amounts against allocated and offset amounts, and tracing a run to its basis and transaction detail. Because RUN_ID is the primary key, reporting queries generally join header to detail on RUN_ID.

• List recent runs for a rule: SELECT run_id, run_period, run_status, total_pool_amount, allocated_amount FROM pa.pa_alloc_runs_all WHERE rule_id = :rule_id ORDER BY creation_date DESC;
• Reconcile a run: SELECT run_id, total_pool_amount, total_allocated_amount, total_offsetted_amount FROM pa.pa_alloc_runs_all WHERE run_id = :run_id; and compare against SUM of PA_ALLOC_TXN_DETAILS amounts.
• Identify failed or incomplete runs: SELECT run_id, run_period, run_status FROM pa.pa_alloc_runs_all WHERE run_status IN ('E','F') AND org_id = :org_id;
• Trace exceptions and missing costs: join PA_ALLOC_EXCEPTIONS and PA_ALLOC_MISSING_COSTS on RUN_ID to explain variances.

Related Objects

PA_ALLOC_RUNS_ALL is the hub of the allocation run schema. It is referenced by PA_ALLOC_EXCEPTIONS.RUN_ID, PA_ALLOC_MISSING_COSTS.RUN_ID, PA_ALLOC_RUN_BASIS_DET.RUN_ID, PA_ALLOC_RUN_SOURCE_DET.RUN_ID, and PA_ALLOC_TXN_DETAILS.RUN_ID, which hold the basis derivation, source, transaction detail, exceptions, and missing-cost lines for each run. GL_AUTO_ALLOC_BATCH_HISTORY.PA_ALLOCATION_RUN_ID also references it, linking Projects allocation runs to General Ledger automatic allocation history. The table itself references PA_ALLOC_RULES_ALL (RULE_ID), PA_PROJECT_TYPES_ALL (PPL_PROJECT_TYPE), PA_FIN_PLAN_TYPES_B (BASIS_FIN_PLAN_TYPE_ID), and PA_IND_COST_CODES (CINT_RATE_NAME), providing the rule definition, project type context, financial plan basis, and indirect cost rate context for each run.