Results for “pl_activity_flag”

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

Overview

CST_COST_TYPES_VAL_V is a single-organization validation view owned by the APPS schema in Oracle E-Business Suite, documented under the BOM – Bills of Material product family. Its purpose is to expose cost types that have not been disabled, presenting only those records whose DISABLE_DATE is null or in the future. The predicate NVL(CCT.DISABLE_DATE, SYSDATE+1) > SYSDATE ensures that cost types without an explicit disable date remain visible, while those that have elapsed are excluded from the result set.

Because it is a single-org view, the organization context is carried explicitly on each row through ORGANIZATION_ID; the view does not restrict output to a session organization, so callers must supply their own organization filter where appropriate. The view is registered as VALID in the ETRM metadata for 12.2.2 and is also available in 12.1.1, where it is widely used by costing and bills-of-material setup forms, list-of-values, and reporting queries that must ignore retired cost types.

Underlying Base Objects

The view is defined over two documented referenced objects:

• CST_COST_TYPES (SYNONYM) — the primary source of cost type definitions, supplying all identification, costing-method, flag, and descriptive-flexfield columns.
• MFG_LOOKUPS (VIEW) — joined to decode the ALLOW_UPDATES_FLAG value, restricted to LOOKUP_TYPE = 'SYS_YES_NO' and matched via LOOKUP_CODE = CCT.ALLOW_UPDATES_FLAG. The resolved MEANING is projected as the display column.

The join is an inner join, so any cost type whose ALLOW_UPDATES_FLAG has no corresponding SYS_YES_NO lookup code is excluded. Combined with the disable-date predicate, the view yields only active, mutually consistent cost type rows.

Key Columns

• COST_TYPE_ID — primary surrogate key for the cost type; the join column for downstream costing and inventory tables.
• ORGANIZATION_ID — organization context; single-org views expose this directly rather than filtering on it.
• COST_TYPE / DESCRIPTION — user-facing identifier and description of the cost type.
• COSTING_METHOD_TYPE — the associated costing method (for example standard, average, FIFO, LIFO).
• FROZEN_STANDARD_FLAG, DEFAULT_COST_TYPE_ID, BOM_SNAPSHOT_FLAG, ALTERNATE_BOM_DESIGNATOR, COMPONENT_YIELD_FLAG, AVAILABLE_TO_ENG_FLAG — behavioral flags governing freezing, defaulting, BOM snapshotting, alternate designators, component yield handling, and engineering availability.
• ALLOW_UPDATES_FLAG and ALLOW_UPDATES_FLAG_DSP — the raw Yes/No code and its decoded meaning from MFG_LOOKUPS.
• PL_ELEMENT_FLAG, PL_RESOURCE_FLAG, PL_OPERATION_FLAG, PL_ACTIVITY_FLAG — flags controlling which cost element categories (element, resource, operation, activity) participate in the cost type; these are frequently queried in Project Manufacturing and cost rollup logic.
• DISABLE_DATE — the date the cost type becomes inactive; the view's central filter column.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield storage.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus the concurrent program columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical consumers include cost type list-of-values, bill of material setup validation, cost rollup programs, and custom reports that must present only enabled cost types. A search for pl_element_flag indicates a requirement to identify cost types that carry project element costing, as shown below.

• List active cost types for an organization.
• Identify cost types participating in project element costing.
• Drive LOVs that must exclude disabled cost types.

Sample queries:

SELECT cost_type_id, cost_type, description, costing_method_type
FROM apps.cst_cost_types_val_v
WHERE organization_id = :org_id
ORDER BY cost_type;

SELECT cost_type_id, cost_type, pl_element_flag, pl_resource_flag,
       pl_operation_flag, pl_activity_flag, allow_updates_flag_dsp
FROM apps.cst_cost_types_val_v
WHERE organization_id = :org_id
  AND pl_element_flag = 'Y';

Because the view is not organization-restricted, always supply ORGANIZATION_ID to avoid cross-organization results.