Results for “pa_ind_cost_codes”

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

Overview

PA_IND_COST_CODES is an Oracle Projects (PA) setup table that stores implementation-defined classifications of burden costs—commonly referred to in EBS as "indirect cost codes" or "burden cost codes." Indirect costs are those that a project does not incur directly (such as overhead, fringe, material handling, or administrative charges) but that are applied to direct costs through burden structures, cost bases, and rate schedules. The table therefore acts as the master reference from which an organization defines the distinct indirect cost pools it wishes to identify, calculate, and report against.

Indirect cost codes defined here are used throughout the burden calculation engine. They are attached to cost bases (via PA_COST_BASE_COST_CODES), to multipliers (via PA_IND_COST_MULTIPLIERS), to rate information (via PA_CINT_RATE_INFO_ALL), and to allocation runs (referenced by PA_ALLOC_RUNS_ALL.CINT_RATE_NAME). Because every costing extension, burden schedule, and allocation process resolves its indirect classification against this single table, the object functions as an authoritative reference within the Projects costing subsystem.

From a Data Vault modeling perspective, the heuristic classification of PA_IND_COST_CODES is hub-leaning. It carries a single business key (IND_COST_CODE) that is also the primary key, and multiple downstream tables reference it through foreign keys. This suggests modeling it as a hub in a Data Vault or dimensional design, with the descriptive attributes (description, active dates, expenditure type, and the ATTRIBUTE1–15 flexfields) treated as satellite-type columns.

Key Information Stored

The table is owned by the PA schema and consists of 27 documented columns. Its structure combines the business identity of the indirect cost code with descriptive attributes and auditing/flexfield columns.

• IND_COST_CODE — The primary key and the business identifier. It is the surrogate/business key on which the unique index PA_IND_COST_CODES_U1 is defined and is the column referenced by every downstream foreign key.
• DESCRIPTION — The user-facing name or explanation of the indirect cost code, used to identify the burden pool on setup forms and reports.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Date-range controls that define when the code is valid for selection in burden and rate definitions. These support effective-dated reference data and prevent obsolete codes from being used in new calculations.
• EXPENDITURE_TYPE — Associates the indirect cost code with an expenditure type classification, linking burden identification to the underlying cost transaction type.
• IND_COST_CODE_USAGE — A usage/classification indicator that governs how the code is applied (for example, which costing context consumes it).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — The standard EBS descriptive flexfield columns, providing a configurable extension area for client-specific burden attributes without schema changes.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN support standard EBS auditing and change tracking.

The primary key is defined by the constraint/index PA_IND_COST_CODES_PK (IND_COST_CODE). The unique index PA_IND_COST_CODES_U1 on the same column reinforces that IND_COST_CODE is a true business-key candidate rather than a system-generated surrogate.

Common Use Cases and Queries

Typical uses center on burden configuration, indirect cost analysis, and reporting. A common query is to list all currently active indirect cost codes within a given date window:

• Retrieve active codes: SELECT ind_cost_code, description, expenditure_type, ind_cost_code_usage FROM pa_ind_cost_codes WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE)+1);
• Join to cost bases to see which bases reference each code: SELECT c.ind_cost_code, c.description, b.cost_base FROM pa_ind_cost_codes c, pa_cost_base_cost_codes b WHERE c.ind_cost_code = b.ind_cost_code;
• Trace multiplier usage: SELECT m.ind_cost_code, m.rate_name FROM pa_ind_cost_multipliers m WHERE m.ind_cost_code = :code;
• Trace rate build-up through PA_CINT_RATE_INFO_ALL and exclusion rules through PA_CINT_EXP_TYPE_EXCL_ALL to understand why a burden is or is not applied to specific expenditure types.

Report developers frequently pull the DESCRIPTION and active dates to label burden amounts on project cost reports, while implementation teams query the flexfield columns to validate client-specific configuration. Because the code is referenced by allocation runs, it also appears in cross-charging and burden allocation reconciliation reports.

Related Objects

PA_IND_COST_CODES is referenced by several significant PA tables through documented foreign keys. Understanding these relationships is essential for impact analysis and data lineage.

• PA_COST_BASE_COST_CODES — joins on IND_COST_CODE; defines which indirect cost codes belong to which cost bases.
• PA_IND_COST_MULTIPLIERS — joins on IND_COST_CODE; stores the multipliers applied to a given indirect cost code.
• PA_CINT_RATE_INFO_ALL — joins on IND_COST_CODE; holds rate information for burden (indirect) cost calculations.
• PA_CINT_EXP_TYPE_EXCL_ALL — joins on IND_COST_CODE; defines expenditure types excluded from a given indirect cost code.
• PA_CINT_RATE_MULTIPLIERS — joins on RATE_NAME (IND_COST_CODE); links rate definitions to multipliers.
• PA_ALLOC_RUNS_ALL — joins on CINT_RATE_NAME; records allocation runs that reference the indirect code by name.

Together these dependencies confirm that PA_IND_COST_CODES is a central reference hub for Oracle Projects burden costing, and any change to an indirect cost code should be assessed against each of these dependent objects before it is deactivated or redefined.