Results for “burden_cost_code”

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

Overview

PA_BURDEN_COST_MULTIPLIERS is a Projects (PA) module table that stores multipliers for the different types of overhead applied to raw cost in order to derive burdened cost. According to the ETRM metadata the table is documented as "R10SC Only," meaning its functional footprint belongs to the older burden-costing model that predates the standard Oracle Projects burden and rate schedule architecture in release 12.1.1 and 12.2.2. In those releases the table remains valid in the PA schema, and it is retained principally for backward compatibility, legacy migration, and historical burden-cost reporting rather than for new configuration.

From a modeling standpoint, the mined Data Vault classification is link. This is a heuristic suggestion: the table resolves relationships between burden cost codes, projects, tasks, and organizations rather than acting as a standalone descriptive hub or a satellite of a single parent. Its composite primary key reinforces that interpretation, since each row represents the intersection of those entities over an effective date range.

Key Information Stored

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

• ORGANIZATION_ID — the organization context for the multiplier; part of the composite primary key and a foreign key to HR_ALL_ORGANIZATION_UNITS.
• PROJECT_ID — identifies the project to which the multiplier applies; foreign key to PA_PROJECTS_ALL.
• TASK_ID — identifies the task level at which the multiplier is defined; foreign key to PA_TASKS.
• BURDEN_COST_CODE — the overhead type being multiplied; foreign key to PA_BURDEN_COST_CODES.
• START_DATE_ACTIVE — the effective start date of the multiplier; the date component of the primary key and unique index.
• END_DATE_ACTIVE — the effective end date, used for date-effective (or "date-tracked") lookups.
• MULTIPLIER — the numeric factor applied to raw cost to compute burden cost.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns providing audit and concurrency information.

The surrogate primary key is PA_BURDEN_COST_MULTIPLIERS_PK, defined over (ORGANIZATION_ID, PROJECT_ID, TASK_ID, BURDEN_COST_CODE, START_DATE_ACTIVE). A unique index, PA_BURDEN_COST_MULTIPLIERS_U1, is defined over the same five columns, making them the business-key candidate: no two multipliers may exist for the same organization, project, task, and burden cost code with the same effective start date.

Common Use Cases and Queries

Typical use cases include reconstructing historical burden calculations, auditing overhead factors applied at specific projects or tasks, and validating legacy data during upgrades to 12.1.1 or 12.2.2. A common reporting pattern joins the table back to PA_BURDEN_COST_CODES to display the overhead name alongside its multiplier:

• Effective-dated lookup: SELECT multiplier FROM pa.pa_burden_cost_multipliers WHERE project_id = :p AND task_id = :t AND burden_cost_code = :b AND :as_of BETWEEN start_date_active AND NVL(end_date_active, SYSDATE)
• Organization-level rollup: join to HR_ALL_ORGANIZATION_UNITS to report multipliers by operating unit or organization.
• Gap analysis: identify burden cost codes with no active multiplier for a given project or task.
• Migration audit: compare legacy multipliers against the corresponding burden schedules defined after upgrade.

Related Objects

The following objects are directly referenced through documented foreign keys or are the primary parent for this table's business keys:

• PA_BURDEN_COST_CODES — joined on BURDEN_COST_CODE; defines the overhead type.
• PA_PROJECTS_ALL — joined on PROJECT_ID; supplies the project context.
• PA_TASKS — joined on TASK_ID; supplies the task context.
• HR_ALL_ORGANIZATION_UNITS — joined on ORGANIZATION_ID; supplies the organization context.
• PA_BURDEN_COST_MULTIPLIERS_PK / _U1 — the primary key constraint and unique index enforcing the business key.

These relationships confirm that the table functions as an intersection or link record, tying overhead definitions to project, task, and organization attributes across an effective date range.