Results for “pa_cost_base_exp_types_u1”

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

Overview

PA.PA_COST_BASE_EXP_TYPES is a transactional configuration table in the Oracle Projects (PA) schema that stores the relationships between cost bases and expenditure types. In Oracle EBS 12.1.1 and 12.2.2, this table defines which expenditure types are eligible for inclusion in a given cost base within a specific burden (cost plus) structure. It effectively controls the mapping logic that drives burdening and cost-plus calculation.

From a Data Vault modeling perspective, the heuristic classification for this object is a link. The table captures associations — not entity attributes — between three parent entities: burden structures, cost bases, and expenditure types. This link classification reflects its role as an intersection/association table resolving a many-to-many relationship between cost setup and expenditure classification.

Key Information Stored

The table contains nine documented columns. The four business-key columns form a compound unique constraint (PA_COST_BASE_EXP_TYPES_U1) and also serve as the primary key PA_COST_BASE_EXP_TYPES_PK:

• COST_PLUS_STRUCTURE (VARCHAR2(30), mandatory) — Name of the burden structure to which the mapping belongs.
• COST_BASE (VARCHAR2(30), mandatory) — Name of the cost base that the expenditure type feeds into.
• COST_BASE_TYPE (VARCHAR2(30), mandatory) — The type classification of the cost base.
• EXPENDITURE_TYPE (VARCHAR2(30), mandatory) — The expenditure type assigned to the cost base.

The remaining columns are standard Oracle Who columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. These provide audit tracking but carry no business semantics.

Note that PA_COST_BASE_EXP_TYPES that the surrogate key concept here is realized as a compound natural key; there is no single numeric identifier. Business-key candidates coincide with the PK columns, and PA_COST_BASE_EXP_TYPES_U1 is the unique index enforcing that constraint.

Common Use Cases and Queries

Typical scenarios include burden structure setup verification, expenditure type eligibility audits, and cost-plus structure reporting. A common pattern is to list all expenditure types assigned to a given burden structure and cost base:

• SELECT COST_PLUS_STRUCTURE, COST_BASE, COST_BASE_TYPE, EXPENDITURE_TYPE FROM PA.PA_COST_BASE_EXP_TYPES WHERE COST_PLUS_STRUCTURE = :structure AND COST_BASE = :base;
• Joining to PA_COST_BASES on COST_BASE to retrieve cost base descriptions.
• Joining to PA_EXPENDITURE_TYPES on EXPENDITURE_TYPE to fetch expenditure type names and descriptions.
• Reconciliation queries against PA_COST_PLUS_STRUCTURES to validate structure definitions prior to burden run.

Related Objects

The table participates in the following documented referential relationships:

• PA.PA_COST_BASES (referenced via COST_BASE) — supplies the cost base definition.
• PA.PA_EXPENDITURE_TYPES (referenced via EXPENDITURE_TYPE) — supplies the expenditure type definition.
• PA.PA_COST_PLUS_STRUCTURES (referenced via COST_PLUS_STRUCTURE) — supplies the burden structure header.
• PA.PA_COST_BASE_EXP_TYPES# — the underlying table synonym/subobject reference.

These relationships make PA_COST_BASE_EXP_TYPES a central junction for burden calculation and cost-plus processing in Oracle Projects.