Search Results cst_lists_pk

Overview

CST_LISTS is a table owned by the BOM (Bills of Material) schema in Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. Its documented description is "Item list for item exploder," indicating that it stores the membership of item lists used by the bill of material exploder. Rather than holding descriptive item attributes, it functions as a transactional association object that records which entities (items) belong to a given list.

The reported physical schema is intentionally minimal: only two columns, LIST_ID and ENTITY_ID, with a composite primary key CST_LISTS_PK defined over both. A unique index, CST_LISTS_U1, exists over the same two columns, so the primary key and the single documented business-key candidate are coextensive. From a Data Vault modeling perspective, the mined classification is standalone, and no foreign keys were identified. A modeling suggestion therefore is to treat this object as a link-style association between a list and an entity, or, if entity attributes are resolved elsewhere, as a satellite-like membership record. Because no FK relationships are documented, any parent-child dependencies must be inferred from naming and application context.

Key Information Stored

Only two columns are documented in the ETRM physical schema for 12.2.2. Their roles are as follows:

• LIST_ID — The identifier of the item list. It supplies one half of the composite primary key and one half of the unique index. It groups member rows into a logical list used by the exploder.
• ENTITY_ID — The identifier of the entity that is a member of the list, typically an item or inventory entity referenced by the BOM exploder. It forms the second half of both CST_LISTS_PK and CST_LISTS_U1.

No descriptive columns such as list name, creation date, or organization context are documented for this table. Practically, LIST_ID behaves as the surrogate grouping key, while the pair (LIST_ID, ENTITY_ID) is the enforced business key by virtue of the unique index. Any attribute values, such as list descriptions or entity details, are expected to reside in companion tables rather than in CST_LISTS itself.

Common Use Cases and Queries

The primary use case is enumerating the members of an item list during BOM explosion. A representative query retrieving all members of a list is:

• SELECT LIST_ID, ENTITY_ID FROM BOM.CST_LISTS WHERE LIST_ID = :list_id;
• SELECT LIST_ID, COUNT(*) FROM BOM.CST_LISTS GROUP BY LIST_ID; — to count members per list.
• SELECT ENTITY_ID FROM BOM.CST_LISTS WHERE LIST_ID = :list_id ORDER BY ENTITY_ID; — for deterministic exploder output.

Because the object is standalone and has no documented foreign keys, reporting is usually narrowed by LIST_ID and then enriched through application-level joins to item master or list header tables. Typical scenarios include validating that a list is populated, detecting duplicate membership attempts (which the unique index prevents), and auditing which entities participate in a given exploder run.

Related Objects

The ETRM metadata documents no explicit foreign keys for CST_LISTS, so the following related objects are inferred from its BOM ownership, its column names, and standard EBS item-exploder design. Each is significant because it supplies the descriptive context that CST_LISTS deliberately omits:

• BOM.CST_LIST_HEADERS (or the corresponding list-header construct) — joined by LIST_ID to obtain list name and definition.
• MTL_SYSTEM_ITEMS_B — joined by INVENTORY_ITEM_ID = ENTITY_ID to resolve item attributes.
• MTL_SYSTEM_ITEMS_TL — joined via INVENTORY_ITEM_ID = ENTITY_ID for translated item descriptions.
• BOM_BILL_OF_MATERIALS — the parent structure whose explosion consumes these lists.
• BOM_COMPONENTS_B — component lines resolved during and after exploder processing.

Because no FK metadata is documented, all join columns above should be verified against the actual instance before being used in production SQL.