Results for “pa_cost_base_exp_types”

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

Overview

PA_COST_BASE_EXP_TYPES is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that defines the association between expenditure types and the cost bases used in burdening and cost-plus calculations. In Oracle Projects, a cost base (for example, raw cost, burdened cost, or a user-defined base) determines the pool of costs against which a burden schedule or cost-plus structure is applied. This table records which expenditure types are eligible to participate in a given cost base within a specified cost-plus structure, effectively bridging expenditure type definitions and burden configuration.

Because the table stores a relationship between multiple independent entities — cost-plus structure, cost base, and expenditure type — its heuristic Data Vault classification is a link table. This classification is a modeling suggestion only; the physical table functions as a traditional intersection or association table that materializes many-to-many relationships among configuration entities rather than transactional events.

Key Information Stored

The table contains nine documented columns. The most significant are the four that form the composite business key and primary key:

• COST_PLUS_STRUCTURE — Identifies the cost-plus structure (from PA_COST_PLUS_STRUCTURES) under which the cost base and expenditure type combination is valid.
• COST_BASE — The cost base identifier (from PA_COST_BASES) to which the expenditure type is assigned.
• COST_BASE_TYPE — A discriminator column that qualifies the cost base, distinguishing among base variants associated with the cost base definition. It participates in both the primary key and the PA_COST_BASES foreign key.
• EXPENDITURE_TYPE — The expenditure type (from PA_EXPENDITURE_TYPES) being associated with the cost base.

There is no separate single-column surrogate key for this table. The primary key, PA_COST_BASE_EXP_TYPES_PK, is the composite of COST_PLUS_STRUCTURE, COST_BASE, COST_BASE_TYPE, and EXPENDITURE_TYPE. A unique index, PA_COST_BASE_EXP_TYPES_U1, covers the same four columns, making them the business-key candidate and enforcing uniqueness of the association.

The remaining columns are standard Oracle EBS who-columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. These support auditing, concurrency control, and the Oracle Applications audit trail, and are maintained automatically by the application's WHO framework.

Common Use Cases and Queries

This table is primarily referenced during burden schedule and cost-plus setup validation, and by reporting queries that explain how a given expenditure type is burdened. A typical query retrieves all expenditure types associated with a cost base for a structure:

• Joining PA_COST_BASE_EXP_TYPES to PA_EXPENDITURE_TYPES to display expenditure type names and descriptions associated with a cost base.
• Joining to PA_COST_BASES and PA_COST_PLUS_STRUCTURES to report on the full burden configuration for a project or organization.
• Validating that all expenditure types requiring burden processing are mapped to the correct cost base before running burden cost calculations.

A representative SQL pattern selects PCBT.EXPENDITURE_TYPE, PET.EXPENDITURE_TYPE_NAME, PCBT.COST_BASE, and PCBT.COST_PLUS_STRUCTURE from PA_COST_BASE_EXP_TYPES PCBT joined to PA_EXPENDITURE_TYPES PET on PCBT.EXPENDITURE_TYPE = PET.EXPENDITURE_TYPE, filtered by COST_PLUS_STRUCTURE. Such queries support configuration auditing, migration validation, and correlation of burden pools with project transaction sources.

Related Objects

Documented foreign keys establish the following dependencies:

• PA_COST_BASES — referenced via COST_BASE (and COST_BASE_TYPE); the parent cost base definition.
• PA_EXPENDITURE_TYPES — referenced via EXPENDITURE_TYPE; the parent expenditure type definition.
• PA_COST_PLUS_STRUCTURES — referenced via COST_PLUS_STRUCTURE; the parent structure defining cost-plus logic.

In practice, reporting and functional analysis commonly extend these with cost base type lookups, burden schedule tables (PA_BURDEN_SCHEDULES), and the Projects transaction tables that reference expenditure types, providing a complete picture of how raw costs flow into burdened and cost-plus amounts.