Search Results cst_pac_low_level_codes




Overview
Explore in AI Chat

Overview

CST_PAC_LOW_LEVEL_CODES is a BOM-schema table within the Oracle E-Business Suite Bills of Material module. Its documented purpose is to store low level codes for inventory items for a given period and organization cost group. Low level codes are integers assigned to items that express their deepest position in a bill of materials explosion; an item that is a component of another assembly receives a higher code than its parent. These codes are the foundation of any dependent-demand or cost-rollup calculation, since they determine the sequence in which items must be processed so that component costs or requirements are resolved before the parent assembly is evaluated.

In the ETRM 12.2.2 documented schema the table resides in the BOM schema and contains 13 columns. Its foreign key structure identifies it as an intersection of two reference entities: CST_PAC_PERIODS and CST_COST_GROUPS, qualified by INVENTORY_ITEM_ID. From a Data Vault modeling perspective, the metadata heuristic classifies this object as a link. That classification is appropriate because the table records an association between a period, a cost group, and an item rather than functioning as an independent hub of business keys or a descriptive satellite. Modeling it as a link makes the cost-rollup dependency explicit and permits effective-dated or period-dated low level code snapshots to coexist for the same item.

Key Information Stored

The most significant columns are the composite business key and the dependent value:

The documented schema does not enumerate a separate surrogate key column; the unique identity logically comprises PAC_PERIOD_ID, COST_GROUP_ID, and INVENTORY_ITEM_ID, which together act as the business-key candidate. Where a single-column primary key is defined in the physical database, it functions only as a row identifier, not as the semantic key.

Common Use Cases and Queries

The primary use case is determining the processing order for cost rollups and dependent-demand explosions. A typical query joins an item's on-hand or requirement data to the low level code so that processing occurs from the lowest level upward:

  • Sequencing a cost rollup by ordering items by LOW_LEVEL_CODE in ascending order per cost group.
  • Reporting the low level code assigned to a given item for a specific period and cost group.
  • Identifying items whose low level code changed between periods, indicating BOM structural changes.
  • Auditing which concurrent program last recalculated a period's low level codes using PROGRAM_ID and REQUEST_ID.

A representative pattern joins the table to CST_PAC_PERIODS on PAC_PERIOD_ID and to CST_COST_GROUPS on COST_GROUP_ID, filtering by the desired period and cost group, and orders the result by LOW_LEVEL_CODE. Because the table is period-scoped, any query must constrain PAC_PERIOD_ID to avoid returning stale codes from prior periods.

Related Objects

The documented foreign keys establish the following relationships:

  • CST_PAC_PERIODS — joined on CST_PAC_LOW_LEVEL_CODES.PAC_PERIOD_ID = CST_PAC_PERIODS.PAC_PERIOD_ID.
  • CST_COST_GROUPS — joined on CST_PAC_LOW_LEVEL_CODES.COST_GROUP_ID = CST_COST_GROUPS.COST_GROUP_ID.

Beyond the documented keys, the INVENTORY_ITEM_ID value corresponds to MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID, and the table is populated and consumed by the periodic costing and PAC low-level-code concurrent programs that drive cost rollup processing. It should be read together with the CST_PAC_PERIODS and CST_COST_GROUPS reference tables and the item master to interpret any stored low level code correctly.