Results for “burden_cost_type”

8 results




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

Overview

The PA_BURDEN_COST_CODES table resides in the PA (Projects) schema of Oracle E-Business Suite and is documented as an R10SC-only implementation object. It stores implementation-defined classifications of the different types of overhead burden costs. In practice, this table serves as a reference or lookup master that defines the valid set of burden cost codes an organization may assign when configuring burden structures and burden multipliers that drive overhead absorption in Oracle Projects costing.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as hub-leaning. That characterization is offered as a modeling suggestion: the surrogate-keyed row represents a unique business concept (a burden cost code) that other tables reference, rather than a transactional link or a descriptive satellite. Its role is therefore foundational—it anchors the definitional side of burden costing, while the multiplier tables supply the rates and the calculation logic that consume those definitions.

Key Information Stored

The table is documented with twelve physical columns in the ETRM 12.2.2 schema. The most important are:

The surrogate primary key is BURDEN_COST_CODE (single-column PK). The unique indexes on BURDEN_COST_CODE and MEANING act as business-key candidates, enforcing that both the code and its meaning are unique across the implementation.

Common Use Cases and Queries

Typical scenarios include validating burden cost code setup, reporting active burden classifications, and joining to multiplier definitions. Because the table is effective-dated, queries frequently filter on the active date range.

  • Listing currently active burden cost codes and their meanings for setup review.
  • Identifying which codes contribute to revenue buildup via REVENUE_BUILDUP_FLAG.
  • Joining to PA_BURDEN_COST_MULTIPLIERS to inspect rates associated with each code.

A representative query pattern:

SELECT bcc.BURDEN_COST_CODE, bcc.MEANING, bcc.BURDEN_COST_TYPE, bcc.REVENUE_BUILDUP_FLAG
FROM PA.PA_BURDEN_COST_CODES bcc
WHERE TRUNC(SYSDATE) BETWEEN bcc.START_DATE_ACTIVE AND NVL(bcc.END_DATE_ACTIVE, TRUNC(SYSDATE))
ORDER BY bcc.BURDEN_COST_CODE;

To relate codes to their multipliers:

SELECT bcc.BURDEN_COST_CODE, bcc.MEANING, bcm.*
FROM PA.PA_BURDEN_COST_CODES bcc, PA.PA_BURDEN_COST_MULTIPLIERS bcm
WHERE bcc.BURDEN_COST_CODE = bcm.BURDEN_COST_CODE;

Related Objects

The documented foreign-key relationship identifies the following significant dependent object:

  • PA_BURDEN_COST_MULTIPLIERS — references PA_BURDEN_COST_CODES via the column BURDEN_COST_MULTIPLIERS.BURDEN_COST_CODE → PA_BURDEN_COST_CODES. This is the primary consumer of the burden cost code definitions and links each code to its multiplier values.

Beyond the documented FK, burden cost codes are conventionally consumed by burden structure and burden schedule setup within Oracle Projects costing. Implementers should treat PA_BURDEN_COST_CODES as the definitional master, with PA_BURDEN_COST_MULTIPLIERS as the dependent transactional-style detail. The single documented inbound FK confirms the hub-leaning classification and indicates that the principal join path for reporting is through BURDEN_COST_CODE.