Results for “target_exp_org_id”

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

Overview

PA_ALLOC_RULES_ALL is the master definition table for allocation rules within the Oracle Projects (PA) module of Oracle E-Business Suite. An allocation rule specifies how a pool of source amounts—typically burdened or raw costs, or a defined resource pool—is distributed across one or more target projects, tasks, or expenditure types, and how the corresponding offsetting entry is generated. The table stores both the source-side (basis) configuration and the target-side (allocation) configuration, together with the offset accounting treatment, in a single row per rule.

In 12.1.1 and 12.2.2 this object is owned by the PA schema and is exposed through the same physical structure, comprising 65 documented columns. Where the row is multi-organization enabled, the ORG_ID column distinguishes operating unit ownership. Rules are consumed by the allocation engine during the Generate Allocations process, and the results are persisted in the companion transaction tables described below.

From a Data Vault modeling perspective, PA_ALLOC_RULES_ALL is heuristically classified as a hub. It carries a single-column surrogate primary key, RULE_ID, and is referenced by numerous dependent tables, which is consistent with a hub distributing a stable business key across many satellites and links.

Key Information Stored

The primary key of the table is RULE_ID, enforced by the unique index PA_ALLOC_RULES_ALL_PK1. A second unique index, PA_ALLOC_RULES_U1 (also on RULE_ID) and PA_ALLOC_RULES_U2 on RULE_NAME, establish RULE_NAME as the natural business key. Among the most significant columns are:

• RULE_ID — surrogate primary key and foreign-key anchor for all dependent allocation tables.
• RULE_NAME — user-facing identifier, protected by unique index U2.
• ALLOCATION_METHOD — governs how the source pool is apportioned to targets.
• TARGET_EXP_TYPE_CLASS / TARGET_EXP_TYPE / TARGET_COST_TYPE / TARGET_EXP_ORG_ID — define the target expenditure classification; the type columns reference PA_SYSTEM_LINKAGES and PA_EXPENDITURE_TYPES.
• ALLOC_RESOURCE_LIST_ID — resource list defining the generated target resources; FK to PA_RESOURCE_LISTS_ALL_BG.
• BASIS_RESOURCE_LIST_ID / BASIS_FIN_PLAN_TYPE_ID — define the source population and financial plan basis.
• OFFSET_EXP_TYPE_CLASS / OFFSET_EXP_TYPE / OFFSET_COST_TYPE / OFFSET_PROJECT_ID / OFFSET_TASK_ID — control the offsetting entry, referencing PA_SYSTEM_LINKAGES, PA_EXPENDITURE_TYPES, PA_PROJECTS_ALL, and PA_TASKS.
• PERIOD_TYPE / BASIS_RELATIVE_PERIOD — periodicity and relative-period logic.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date window for rule execution.
• ORG_ID — operating unit, where multi-org security applies.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield segment columns.

Common Use Cases and Queries

The principal functional use is the definition, maintenance, and audit of allocation rules. Reporting typically resolves the rule master to its descriptive lookups and to execution history. For example, listing active rules for an operating unit can be written as:

SELECT r.rule_id, r.rule_name, r.allocation_method, r.start_date_active, r.end_date_active
FROM   pa_alloc_rules_all r
WHERE  r.org_id = :p_org_id
AND    TRUNC(SYSDATE) BETWEEN NVL(r.start_date_active, TRUNC(SYSDATE))
                          AND NVL(r.end_date_active, TRUNC(SYSDATE));

Confirming which rules have generated transactions requires joining to PA_ALLOC_RUNS_ALL, PA_ALLOC_TXN_DETAILS, or PA_ALLOC_GL_LINES on RULE_ID. Such queries are the basis of allocation reconciliation and of diagnosing rules that returned no output. Rule definitions may also be compared across instances during migration by projecting the columns enumerated above.

Related Objects

PA_ALLOC_RULES_ALL is the parent in several one-to-many relationships. The following are the most operationally significant dependents, each joined on RULE_ID:

• PA_ALLOC_RUNS_ALL — allocation run history for the rule.
• PA_ALLOC_SOURCE_LINES and PA_ALLOC_TARGET_LINES — the generated source and target amounts.
• PA_ALLOC_TXN_DETAILS — detailed allocation transactions.
• PA_ALLOC_GL_LINES — GL lines produced by the allocation.
• PA_ALLOC_RESOURCES — resources associated with the rule.
• PA_ALLOC_EXCEPTIONS — exceptions raised during processing.
• GL_AUTO_ALLOC_BATCHES — batch references from General Ledger auto-allocation.

On the referenced side, PA_ALLOC_RULES_ALL draws its target and offset expenditure definitions from PA_EXPENDITURE_TYPES and PA_SYSTEM_LINKAGES, its resource lists from PA_RESOURCE_LISTS_ALL_BG, its offset project and task from PA_PROJECTS_ALL and PA_TASKS, and its basis financial plan type from PA_FIN_PLAN_TYPES_B.