Results for “pa_cost_base_cost_codes_pk”

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

Overview

PA.PA_COST_BASE_COST_CODES is a Projects (PA) module table that stores the burden cost codes associated with cost bases. In Oracle EBS costing and burdening, a cost base defines the pool of raw costs eligible for burdening (for example, straight-time labor or material), while a burden cost code identifies the specific component of burden (such as fringe, overhead, or G&A) that is applied against that base. This table is the associative object that binds those two concepts together, and it also stores the precedence that determines the sequence in which burden cost codes are applied within a given cost base and cost plus structure. The row is the atomic unit of burden configuration, and its surrogate identifier COST_BASE_COST_CODE_ID is the value users most commonly search on when troubleshooting burden setup or compiled multiplier issues.

From a Data Vault modeling perspective, the documented foreign key structure classifies this object as satellite-leaning. Its attributes (precedence and the audit columns) describe a specific business configuration, while its foreign keys to PA_COST_BASES, PA_IND_COST_CODES, and PA_COST_PLUS_STRUCTURES position it as a dependent detail rather than an independent hub.

Key Information Stored

The table contains 11 documented columns. The most significant are:

• COST_BASE_COST_CODE_ID — the surrogate primary key, enforced by unique index PA_COST_BASE_COST_CODES_PK and also by PA_COST_BASE_COST_CODES_U1.
• COST_PLUS_STRUCTURE — identifies the cost plus structure under which the burden mapping is defined; joins to PA_COST_PLUS_STRUCTURES.
• COST_BASE and COST_BASE_TYPE — together identify the cost base that the burden cost code is applied to; these join to PA_COST_BASES.
• IND_COST_CODE — the burden (indirect) cost code being associated with the base; joins to PA_IND_COST_CODES.
• PRECEDENCE — controls the order in which multiple burden cost codes are applied against the same base, which materially affects calculated burden amounts.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — support change tracking and are useful for incremental ETL and audit reporting.

The business-key candidate is PA_COST_BASE_COST_CODES_U2, a composite unique index over COST_PLUS_STRUCTURE, COST_BASE, COST_BASE_TYPE, and IND_COST_CODE, confirming that a given indirect cost code may appear only once per cost base within a cost plus structure.

Common Use Cases and Queries

Typical scenarios include reviewing burden setup for a cost plus structure, checking precedence ordering, and tracing compiled multipliers back to their source burden definition.

• List all burden cost codes for a cost plus structure, ordered by precedence:
  SELECT cbcc.cost_base_cost_code_id, cbcc.cost_base, cbcc.cost_base_type, cbcc.ind_cost_code, cbcc.precedence FROM pa_cost_base_cost_codes cbcc WHERE cbcc.cost_plus_structure = :structure ORDER BY cbcc.precedence;
• Join to the indirect cost code name for reporting:
  SELECT icc.cost_code, icc.description, cbcc.precedence FROM pa_cost_base_cost_codes cbcc, pa_ind_cost_codes icc WHERE cbcc.ind_cost_code = icc.cost_code;
• Find compiled multipliers generated from a given burden mapping:
  SELECT pcm.* FROM pa_compiled_multipliers pcm WHERE pcm.cost_base_cost_code_id = :id;
• Audit recently changed burden configurations:
  SELECT cost_base_cost_code_id, last_updated_by, last_update_date FROM pa_cost_base_cost_codes WHERE last_update_date > SYSDATE - 30;

Related Objects

• PA_COST_BASES — parent base definition; joined on COST_BASE and COST_BASE_TYPE.
• PA_IND_COST_CODES — the burden cost code attributed; joined on IND_COST_CODE.
• PA_COST_PLUS_STRUCTURES — the owning structure; joined on COST_PLUS_STRUCTURE.
• PA_COMPILED_MULTIPLIERS — child table referencing COST_BASE_COST_CODE_ID; stores the compiled burden rates derived from this configuration.