Results for “pa_cost_base_v”

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

Overview

PA_COST_BASE_V is a database view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. As documented in the ETRM metadata, it is designated "R10SC Only" and functions as the base view for cost bases used in a burden structure. In the Oracle Projects cost accumulation and burdening model, a cost base defines the pool of raw cost upon which burden multipliers are applied to derive burdened cost. Standard cost base types include Raw Cost, Burdened Cost, and various user-defined bases. Because this view consolidates cost base definitions from multiple underlying configuration sources, it presents a single, de-duplicated reference set that reporting tools, concurrent programs, and integrations can query without needing to join the individual base tables directly. As a view rather than a table, it holds no data of its own; it is a read-only, virtual presentation that resolves at runtime against its constituent objects.

Underlying Base Objects

According to the documented metadata, PA_COST_BASE_V is defined over two referenced base objects, both accessed through synonyms in the APPS schema:

• PA_COST_BASE_COST_CODES — the configuration table that associates expenditure cost codes with a given cost base within a cost-plus (burden) structure.
• PA_COST_BASE_EXP_TYPES — the configuration table that associates expenditure types with a given cost base within a cost-plus structure.

The view text performs a UNION of two SELECT DISTINCT statements, one against each base table, projecting the same three columns from both. The DISTINCT operation eliminates duplicate cost base combinations that would otherwise appear when multiple cost codes or expenditure types map to the same cost base. The UNION (rather than UNION ALL) applies a further de-duplication across the two result sets. The net effect is that the view returns one row per unique combination of cost-plus structure, cost base, and cost base type, regardless of whether the underlying membership was defined by cost code, by expenditure type, or by both.

Key Columns

The view exposes three columns, each carrying specific meaning within the burdening configuration model:

• COST_PLUS_STRUCTURE — identifies the cost-plus (burden) structure to which the cost base belongs. A single cost base name may appear under multiple structures, so this column is essential for scoping queries to a specific burdening configuration.
• COST_BASE — the name or identifier of the cost base itself, representing the grouping of costs that will be burdened. This is the primary attribute that consumers of the view are typically searching for.
• COST_BASE_TYPE — classifies the nature of the cost base, distinguishing, for example, between standard raw cost bases and other defined types. This column supports filtering when only certain classes of cost base are relevant to a report or integration.

Because the view contains no descriptive or date-effective columns beyond these three, it is best regarded as a lightweight lookup rather than a full configuration record.

Common Use Cases and Queries

The view is commonly used to enumerate the cost bases available within a burden structure, to validate configuration during implementation or upgrade testing, and to drive LOV-style queries in custom reports and interfaces. A typical query retrieves all bases for a specific structure:

• SELECT cost_base, cost_base_type FROM pa_cost_base_v WHERE cost_plus_structure = :p_structure ORDER BY cost_base;
• SELECT DISTINCT cost_base_type FROM pa_cost_base_v; — to list the distinct cost base types in use.
• SELECT cost_plus_structure, cost_base FROM pa_cost_base_v WHERE cost_base = :p_base; — to determine which burden structures reference a given cost base.

Given its "R10SC Only" designation, the view should be treated as a legacy-compatible object; custom code referencing it should be reviewed during upgrades to later Projects releases, where cost base configuration may be surfaced through alternate or replacement objects.