Results for “primary_cost_method_id”

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

Overview

CSTBV_LE_COST_TYPES is an APPS-owned read-only view in Oracle E-Business Suite, residing within the Bills of Material (BOM) product family and the broader Cost Management (CST) schema. Its purpose is to present the association between legal entities and the cost types configured against them, enriched with the legal entity name and the cost type name. In EBS 12.1.1 and 12.2.2, the view functions as a reporting and integration surface for cost type assignments that are governed by legal entity and ledger context. Because the view is defined WITH READ ONLY, it is intended strictly for query and extraction purposes rather than for direct data manipulation, making it suitable for BI Publisher reports, custom concurrent programs, and outbound interfaces that must confirm which cost types belong to which legal entity.

Underlying Base Objects

The view is defined over three documented base objects:

• CST_COST_TYPES (referenced via a synonym) — the cost type master, supplying the cost type name and cost type identifier.
• CST_LE_COST_TYPES (referenced via a synonym) — the legal entity to cost type assignment table, which is the primary driver of the view.
• XLE_FIRSTPARTY_INFORMATION_V — a view in the XLE (Subledger Accounting) schema that resolves the legal entity identifier to its descriptive name.

The join is expressed as XFI.LEGAL_ENTITY_ID = CLCT.LEGAL_ENTITY and CCT.COST_TYPE_ID = CLCT.COST_TYPE_ID, so the view returns one row per legal entity and cost type combination recorded in CST_LE_COST_TYPES, decorated with the first-party legal entity name and the cost type name. The inclusion of XLE_FIRSTPARTY_INFORMATION_V is significant: it ties cost type configuration to the legal entity model introduced by Subledger Accounting, allowing cost types to be reported in a legal-entity-aware manner.

Key Columns

• LEGAL_ENTITY — the legal entity identifier from CST_LE_COST_TYPES.
• COST_TYPE_ID — the cost type identifier linking to CST_COST_TYPES.
• LEGAL_ENTITY_NAME — the legal entity name resolved through XLE_FIRSTPARTY_INFORMATION_V.
• COST_TYPE_NAME — the descriptive cost type name from CST_COST_TYPES.
• LEDGER_ID — the set of books or ledger associated with the cost type assignment.
• PRIMARY_COST_METHOD_ID — the primary cost method configured for the legal entity and cost type.
• PAC_RATES_COST_TYPE_ID — the cost type used for periodic average cost (PAC) rates.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, UPDATED_BY — standard audit columns.

Note that the view text aliases some columns differently from the documented column list; for example, XFI.NAME is surfaced as LEGAL_ENTITY_NAME and CCT.COST_TYPE as COST_TYPE_NAME. Consumers should reference the documented column names when writing queries.

Common Use Cases and Queries

Typical scenarios include validating cost type setup per legal entity, populating cost-related extracts, and reconciling PAC rate configuration. A representative query is:

• SELECT legal_entity_name, cost_type_name, ledger_id, primary_cost_method_id FROM apps.cstbv_le_cost_types WHERE legal_entity_name = :p_legal_entity;
• SELECT cost_type_name, ledger_id FROM apps.cstbv_le_cost_types WHERE pac_rates_cost_type_id IS NOT NULL;

Because the view is read-only and joins across BOM/CST and XLE objects, it is well suited to reporting layers that must not alter transactional cost setup.