Search Results basis_method

Overview

PA_ALLOC_RUNS is a Projects (PA) module view that presents allocation run definitions and execution results generated by the Oracle EBS Project Allocations engine. Each row corresponds to a single allocation run identified by RUN_ID, capturing the pool setup, basis configuration, target and offset account determinations, reversal information, and monetary results produced when the allocation engine processes a rule for a given GL period. The view is defined as a secured (ROWID/multi-org) view over the underlying table PA_ALLOC_RUNS_ALL, applying an ORG_ID filter driven by the USERENV('CLIENT_INFO') session attribute. This confirms that the view is compliant with Multi-Org Access Control (MOAC): rows are only returned for the operating unit currently set in the user's session.

In Oracle EBS 12.1.1 and 12.2.2, PA_ALLOC_RUNS functions as the principal reporting and inquiry layer for allocation activity. Allocation administrators, project accountants, and integration developers query it to audit what was allocated, from which pool, to which target expenditure type and cost type, and whether the run was drafted, released, or reversed. Because the view is not documented as a "Not Implemented" object in the ETRM excerpt, it is available for query in supported releases, although Oracle does not guarantee its structure as a public API.

Underlying Base Objects

The view is defined over a single base table, PA_ALLOC_RUNS_ALL, which stores allocation run data at the operating-unit level. The WHERE clause applies the standard MOAC predicate:

• ORG_ID is compared against the operating unit derived from USERENV('CLIENT_INFO');
• When no valid client information is present, the NVL/DECODE logic defaults the comparison value to -99, effectively filtering out rows unless a session context is established;
• Columns suffixed with _ALL (such as those in PA_ALLOC_RUNS_ALL) are the multi-org enabled base columns that the view exposes without the suffix.

The view does not itself store data; it is a secured projection of PA_ALLOC_RUNS_ALL. Related allocation metadata (rules, resource lists, and expenditure type classifications) resides in companion tables such as PA_ALLOC_RULES_ALL, PA_ALLOC_RUN_AMOUNTS, and the expenditure type/classification tables referenced by the TARGET_EXP_TYPE and OFFSET_EXP_TYPE columns.

Key Columns

• RUN_ID / RULE_ID — Unique identifier for the allocation run and the allocation rule that generated it.
• RUN_PERIOD / PERIOD_TYPE / FISCAL_YEAR / QUARTER / PERIOD_NUM — The GL period context in which the allocation was executed.
• TARGET_EXP_TYPE / TARGET_EXP_TYPE_CLASS / TARGET_EXP_ORG_ID / TARGET_COST_TYPE — The expenditure type, expenditure type class, organization, and cost type to which the allocated amounts are charged. This is the column set referenced by the search term "target_exp_type."
• OFFSET_EXP_TYPE / OFFSET_EXP_TYPE_CLASS / OFFSET_EXP_ORG_ID / OFFSET_COST_TYPE / OFFSET_METHOD / OFFSET_PROJECT_ID / OFFSET_TASK_ID — The counterpart accounting destination for the offset side of the allocation entry.
• SOURCE_AMOUNT_TYPE / SOURCE_BALANCE_CATEGORY / SOURCE_BALANCE_TYPE / BASIS_METHOD / BASIS_AMOUNT_TYPE / BASIS_BALANCE_CATEGORY / BASIS_BUDGET_TYPE_CODE — Define the pool source and the basis used to distribute it.
• POOL_PERCENT / FIXED_AMOUNT / TOTAL_POOL_AMOUNT / ALLOCATED_AMOUNT / TOTAL_ALLOCATED_AMOUNT / TOTAL_OFFSETTED_AMOUNT — Quantitative results of the run.
• RUN_STATUS / AUTO_RELEASE_FLAG / DUP_TARGETS_FLAG / IMP_WITH_EXCEPTION — Status and control flags indicating whether the run was drafted, released, duplicated targets, or processed with exceptions.
• REVERSAL_DATE / REV_TARGET_EXP_GROUP / REV_OFFSET_EXP_GROUP — Reversal tracking for previously released allocations.
• MISSING_SOURCE_PROJ_AMT / MISSING_TARGET_PROJ_AMT / MISSING_OFFSET_PROJ_AMT — Reconciliation amounts highlighting unallocated or unoffset balances.
• ORG_ID — The operating unit key enforced by the MOAC predicate.

Common Use Cases and Queries

The most frequent use case is auditing allocation output by target expenditure type. The following example lists runs for a given period where a specific target expenditure type was used:

• SELECT run_id, rule_id, run_period, target_exp_type, target_cost_type, allocated_amount FROM pa_alloc_runs WHERE run_period = :period AND target_exp_type = :exp_type;
• SELECT rule_id, run_status, total_pool_amount, total_allocated_amount FROM pa_alloc_runs WHERE rule_id = :rule_id AND run_status = 'D';
• SELECT run_id, run_period, reversal_date, rev_target_exp_group FROM pa_alloc_runs WHERE reversal_date IS NOT NULL;

Because the view enforces the operating-unit filter, callers must initialize CLIENT_INFO or query within the correct operating unit responsibility. For high-volume extraction, joining PA_ALLOC_RUN_AMOUNTS on RUN_ID provides line-level detail beyond the summarized columns exposed here.