Search Results pa_alloc_rules

Overview

PA_ALLOC_RULES is a Projects (PA) module view in Oracle EBS 12.1.1 and 12.2.2 that exposes the definition of allocation rules used by the Project Costing allocation engine. Allocation rules define how pooled costs and amounts from a source are distributed across target expenditure items, organizations, and cost types. This view presents a business-friendly, secured projection of the underlying allocation rule definition, allowing reporting tools, integrations, and custom extensions to retrieve rule configuration without querying the base table directly.

The view is defined over PA_ALLOC_RULES_ALL, the multi-organization (MOAC) base table that stores allocation rule definitions per operating unit. The view applies an ORG_ID security predicate derived from USERENV('CLIENT_INFO'), so rows returned are restricted to the operating unit context set by the current session. This makes the view suitable for use in concurrent programs, OAF pages, and ad hoc reporting where organization-level security must be honored. According to ETRM metadata, the object is not implemented as a standalone database object in this database, meaning it is a view rather than a physical table and is therefore read-only.

Underlying Base Objects

ETRM metadata documents no referenced base objects for this view beyond the projection itself. The view text reveals that PA_ALLOC_RULES selects from PA_ALLOC_RULES_ALL, applying an ORG_ID filter that resolves the current organization from the CLIENT_INFO session setting. Because the underlying table is the _ALL variant, the view participates in the standard Oracle EBS multi-org access control model. No additional joins to lookup tables or reference tables are performed in the view text, so all descriptive attributes—such as allocation method, source and basis amount types, and offset configuration—are stored denormalized on the base row. Consumers requiring decoded lookup meanings must join to the corresponding PA or FND lookup views separately.

Key Columns

• RULE_ID / RULE_NAME / DESCRIPTION – Primary identifier, user-visible name, and descriptive text for the allocation rule.
• ALLOCATION_METHOD – Determines the allocation calculation approach (for example, prorated, fixed amount, or target-based).
• POOL_PERCENT / FIXED_AMOUNT – Allocation percentage or fixed amount applied when the rule is executed.
• SOURCE_AMOUNT_TYPE, SOURCE_BALANCE_CATEGORY, SOURCE_BALANCE_TYPE – Define the source pool that supplies amounts to be allocated.
• BASIS_METHOD, BASIS_RELATIVE_PERIOD, BASIS_AMOUNT_TYPE, BASIS_BALANCE_CATEGORY, BASIS_BALANCE_TYPE – Define the basis used to drive distribution across targets.
• TARGET_EXP_TYPE_CLASS, TARGET_EXP_ORG_ID, TARGET_EXP_TYPE, TARGET_COST_TYPE – Identify the target expenditure classification receiving allocated costs.
• OFFSET_* columns – Configure offset (contra) expenditure type, organization, cost type, method, project, and task.
• AUTO_RELEASE_FLAG, IMP_WITH_EXCEPTION, DUP_TARGETS_FLAG – Control processing behavior during allocation runs.
• PERIOD_TYPE / START_DATE_ACTIVE / END_DATE_ACTIVE – Define the effective period and date range for which the rule is active.
• ORG_ID – Operating unit that owns the rule; drives MOAC security in the view predicate.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – Descriptive flexfield storage.

Common Use Cases and Queries

Typical uses include reporting on allocation rule configuration, validating rule setup before running allocation, auditing effective and inactive rules, and feeding integration extracts that replicate allocation definitions into external systems.

SELECT rule_id, rule_name, allocation_method,
       source_amount_type, basis_method, pool_percent,
       start_date_active, end_date_active
FROM   pa_alloc_rules
WHERE  end_date_active IS NULL
   OR  end_date_active >= SYSDATE;

SELECT r.rule_name, r.target_exp_type, r.target_cost_type,
       r.offset_exp_type, r.auto_release_flag
FROM   pa_alloc_rules r
WHERE  r.allocation_method = 'PRORATED';

Because the view enforces ORG_ID security from CLIENT_INFO, queries should be run in a session where the operating unit context is initialized (for example, through a standard EBS responsibility) to ensure correct results. For cross-organization analysis, query PA_ALLOC_RULES_ALL directly with appropriate MOAC initialization.