Results for “engineering_flag”

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

Overview

CST_COST_TYPE_HISTORY is a Bills of Material (BOM) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores historical information about cost rollups and cost type purge activity. It functions as the audit and history repository for the costing engine, capturing the parameters, dates, and outcomes of each cost rollup execution and each cost type purge operation performed against a specific cost type within a specific organization. The table resides in the BOM schema and is composed of 30 documented columns.

Based on the foreign key structure documented in the ETRM metadata, the heuristic Data Vault classification for this object is a link. It resolves relationships between cost types, inventory items, categories, and category sets, and carries descriptive and event-oriented attributes such as rollup dates and purge dates. This classification should be treated as a modeling suggestion rather than a definitional constraint.

Key Information Stored

The table's primary key is CST_COST_TYPE_HISTORY_PK, defined on COST_TYPE_ID and ORGANIZATION_ID. A second unique index, CST_COST_TYPE_HISTORY_U1, is defined on COST_TYPE_ID, ORGANIZATION_ID, ROLLUP_DATE, and PURGE_DATE, which serves as the principal business-key candidate for identifying a specific rollup or purge event.

• COST_TYPE_ID — Identifies the cost type to which the rollup or purge history belongs; joins to CST_COST_TYPES.
• ORGANIZATION_ID — Identifies the inventory organization in which the rollup or purge was executed.
• ROLLUP_ID — Identifier of the specific cost rollup run.
• ROLLUP_DATE — The date on which the cost rollup was performed.
• PURGE_DATE — The date on which a purge operation was executed for the cost type.
• REPORT_OPTION and REPORT_TYPE — Control which cost rollup report was generated and in what format.
• ROLLUP_OPTION — Indicates the scope or behavior applied during the rollup.
• INVENTORY_ITEM_ID — The inventory item associated with the history record; joins to MTL_SYSTEM_ITEMS_B.
• CATEGORY_SET_ID and CATEGORY_ID — The category set and category defining the range of items included; join to MTL_CATEGORY_SETS_B and MTL_CATEGORIES_B.
• RANGE_LOW and RANGE_HIGH — The low and high boundaries of the item range processed.
• RANGE — The range specification used to select items for the rollup.
• ALTERNATE_BOM_DESIGNATOR and ALTERNATE_RTG_DESIGNATOR — The alternate bill and routing designators applied during the rollup.
• ENGINEERING_FLAG and UNIMPLEMENTED_ECN_FLAG — Flags indicating whether engineering items or unimplemented engineering change orders were included.
• REQUEST_ID and PROGRAM_ID — Identify the concurrent request and program that produced the record, supporting reconciliation with concurrent manager logs.

Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — are also present.

Common Use Cases and Queries

Costing and supply chain analysts use this table to reconstruct the history of cost rollups for a cost type, to verify when a purge last occurred, and to troubleshoot discrepancies in frozen or average costs. A typical query returns all rollups for a cost type in an organization, ordered by date:

• Querying rollup history: SELECT COST_TYPE_ID, ORGANIZATION_ID, ROLLUP_ID, ROLLUP_DATE, INVENTORY_ITEM_ID, REQUEST_ID FROM CST_COST_TYPE_HISTORY WHERE COST_TYPE_ID = :cost_type_id AND ORGANIZATION_ID = :org_id ORDER BY ROLLUP_DATE DESC;
• Identifying purge activity: SELECT COST_TYPE_ID, ORGANIZATION_ID, PURGE_DATE, PURGE_OPTION FROM CST_COST_TYPE_HISTORY WHERE PURGE_DATE IS NOT NULL;
• Linking history to concurrent requests to retrieve execution diagnostics.
• Auditing which alternate BOM or routing designators were in effect during a rollup.

Related Objects

• CST_COST_TYPES — joined on CST_COST_TYPE_HISTORY.COST_TYPE_ID; supplies the cost type definition.
• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID; supplies item attributes.
• MTL_CATEGORIES_B — joined on CATEGORY_ID; supplies category descriptions.
• MTL_CATEGORY_SETS_B — joined on CATEGORY_SET_ID; supplies category set definitions.
• CST_ITEM_COSTS — the item cost table populated by rollups recorded here.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID for concurrent program execution detail.