Results for “allow_updates_flag_dsp”

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

Overview

CST_COST_TYPES_ALL_V is a single-organization view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Despite the "ALL" suffix commonly associated with multi-org objects, the ETRM metadata explicitly classifies this view as a "SINGLE-ORG view" exposing "All Cost types." It presents the rows of the CST_COST_TYPES table, filtered only by the organization context supplied by the caller, and decorates each row with the decoded meaning of the ALLOW_UPDATES_FLAG through a join to the MFG_LOOKUPS view. The view is registered under the BOM – Bills of Material product and is status VALID.

In practice, CST_COST_TYPES_ALL_V serves as the primary read interface for cost type definitions used by costing, inventory, and bills-of-material reporting. Users searching for default_cost_type_id typically do so to identify the cost type designated as the default for a given organization, to join cost type definitions to transaction or item cost records, or to feed integration and reconciliation queries.

Underlying Base Objects

The ETRM documentation identifies two referenced base objects: CST_COST_TYPES (SYNONYM) and MFG_LOOKUPS (VIEW). The view text is a simple join:

• CST_COST_TYPES CCT — the driving table; supplies all functional and descriptive columns.
• MFG_LOOKUPS LU — joined on LU.LOOKUP_TYPE = 'SYS_YES_NO' and LU.LOOKUP_CODE = CCT.ALLOW_UPDATES_FLAG, producing the decoded value exposed as ALLOW_UPDATES_FLAG_DSP.

Because the join is on a Yes/No lookup, the view effectively translates the stored flag into a user-readable meaning while leaving the raw code intact. The organization identity is carried on the ORGANIZATION_ID column from CST_COST_TYPES; callers are responsible for supplying the appropriate single-org context.

Key Columns

• COST_TYPE_ID — primary key of the cost type definition; the join key to cost, transaction, and item cost tables.
• ORGANIZATION_ID — the organization owning the cost type row; central to single-org filtering.
• COST_TYPE — the code identifying the cost type (for example, FIFO, Standard, Average).
• DESCRIPTION — the descriptive name of the cost type.
• COSTING_METHOD_TYPE — the costing method associated with the cost type.
• DEFAULT_COST_TYPE_ID — the identifier of the cost type designated as the default, the column most frequently targeted by searches on this view.
• FROZEN_STANDARD_FLAG, BOM_SNAPSHOT_FLAG, AVAILABLE_TO_ENG_FLAG, COMPONENT_YIELD_FLAG — control flags governing costing and BOM behavior.
• ALLOW_UPDATES_FLAG and ALLOW_UPDATES_FLAG_DSP — the raw Yes/No code and its decoded meaning from MFG_LOOKUPS.
• ALTERNATE_BOM_DESIGNATOR, DISABLE_DATE, PL_ELEMENT_FLAG, PL_RESOURCE_FLAG, PL_OPERATION_FLAG, PL_ACTIVITY_FLAG — additional configuration and lifecycle attributes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — the WHO/concurrent-program audit columns.

Common Use Cases and Queries

Typical scenarios include resolving the default cost type for an organization, listing all cost types available to a costing process, and joining cost type definitions to item cost or transaction data.

To retrieve cost types for a specific organization:

SELECT cost_type_id, cost_type, description, costing_method_type
FROM   cst_cost_types_all_v
WHERE  organization_id = :org_id
AND    disable_date IS NULL;

To identify the default cost type row:

SELECT cost_type_id, cost_type, description
FROM   cst_cost_types_all_v
WHERE  organization_id = :org_id
AND    cost_type_id = (SELECT default_cost_type_id
                       FROM   cst_cost_types_all_v
                       WHERE  organization_id = :org_id
                       AND    cost_type = :cost_type);

Because the view exposes DEFAULT_COST_TYPE_ID directly alongside COST_TYPE_ID, integrations that must propagate the default cost type can resolve it in a single query rather than joining back to base tables. All queries should always restrict on ORGANIZATION_ID to honour the single-org semantics documented in the ETRM metadata.