Search Results pa_burden_cost_codes




Overview
Explore in AI Chat

Overview

The PA_BURDEN_COST_CODES table is a core reference table within the Oracle E-Business Suite (EBS) Projects module (PA). It serves as a repository for implementation-defined classifications of various overhead burden cost types. Its primary role is to establish a standardized coding structure for indirect costs—such as administrative overhead, fringe benefits, or facility costs—that are applied to direct project expenditures. This table is a foundational element for the burden costing engine, enabling the systematic calculation, allocation, and reporting of overhead across projects. The metadata specifies its status as "R10SC Only," indicating its design and usage are specific to the R10SC (Release 10 Smart Client) architecture, which is integral to the financial logic in EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to catalog unique burden cost classifications. While the full column list is not detailed in the provided metadata, the primary key is explicitly documented as BURDEN_COST_CODE. This column is the unique identifier for each burden cost type (e.g., 'FACILITIES', 'ADMIN', 'FRINGE'). Other typical columns in such a reference table would include a description field (e.g., BURDEN_COST_CODE_DESC) to provide a meaningful name for the code, and control columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY for auditing. The table's sole purpose is to maintain this validated list of codes, which are then referenced by transactional and calculation tables.

Common Use Cases and Queries

This table is primarily used during the setup and execution of burden cost schedules. Common operational and reporting scenarios include validating burden cost codes during data entry, generating lists of active codes for setup screens, and supporting burden cost analysis reports. A typical query would involve joining this table to the PA_BURDEN_COST_MULTIPLIERS table to retrieve the full burden schedule definition. For example:

  • SELECT bcc.burden_cost_code, bcc.description, bcm.multiplier FROM pa_burden_cost_codes bcc, pa_burden_cost_multipliers bcm WHERE bcc.burden_cost_code = bcm.burden_cost_code AND bcm.org_id = :p_org_id;

This pattern is essential for reports that analyze the composition of applied burden costs by project or task, tracing calculated overhead back to its source classification.

Related Objects

The PA_BURDEN_COST_CODES table has a direct and critical relationship with the PA_BURDEN_COST_MULTIPLIERS table, as defined by the documented foreign key. The PA_BURDEN_COST_MULTIPLIERS.BURDEN_COST_CODE column references the primary key of PA_BURDEN_COST_CODES, enforcing referential integrity. This relationship means that every burden multiplier defined in the system must be associated with a valid, pre-defined code from this table. Consequently, this table is a parent to any transactional data that stores burden calculations. It is also indirectly related to core project costing tables (e.g., PA_COST_DISTRIBUTION_LINES_ALL) through the burden engine's processing logic, where burden costs are computed and posted based on these code classifications.