Search Results cst_lists_u1

Overview

BOM.CST_LISTS is a Cost Management (CST) table owned by the BOM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores lists of items generated by the item list exploder for use by the Cost Management concurrent programs CMCCOC, CMCICU, CMCMEC, and CMRICU. In practical terms, CST_LISTS acts as a transient or semi-persistent staging structure: the exploder decomposes a user-supplied item selection into its constituent entities and writes one row per list/entity pairing, which the cost rollup, cost update, and related cost processors subsequently consume as their driving set.

The table is deliberately narrow, carrying only two numbered columns, and is physically stored in the APPS_TS_NOLOGGING tablespace with a PCTFREE of 10. The NOLOGGING attribute is consistent with a high-volume, regenerable work table whose contents can be reproduced by re-running the exploder. Under the heuristic Data Vault classification mined from the documented foreign-key structure, this object is identified as standalone, meaning it participates in no declarative foreign-key relationships and therefore does not cleanly resolve into a hub, link, or satellite. From a modeling standpoint it is best treated as a dependent staging or bridge construct keyed by the exploder's list identity rather than as a durable business entity.

Key Information Stored

The documented physical schema comprises exactly two columns, both mandatory and both NUMBER, and both participate in the primary key.

• LIST_ID — The list identifier. This is the value assigned by the item list exploder to a single invocation or logical list. Many rows share one LIST_ID; it is the grouping key that the consumer concurrent programs use to isolate the set of entities belonging to one run.
• ENTITY_ID — A generic entity identifier. It represents the item or entity that the exploder resolved into the list. Because the column is generically named, the semantic meaning of ENTITY_ID is interpreted by the consuming program in the context of the specific exploder and cost process that populated the list.

The surrogate primary key is documented as CST_LISTS_PK over (LIST_ID, ENTITY_ID). A separate unique index, CST_LISTS_U1, is defined over the identical column pair (LIST_ID, ENTITY_ID) in the APPS_TS_NOLOGGING tablespace. Because the columns of the unique index are exactly those of the primary key, CST_LISTS_U1 is not an alternative business-key candidate; it is a redundant uniqueness enforcement that guarantees no duplicate entity can appear twice within a single list. The search term referenced by the user, "cst_lists_u1," therefore identifies this unique index rather than a distinct business identifier.

Common Use Cases and Queries

The principal use case is diagnostic and operational: identifying which entities were included in a given cost process run, and confirming that an exploder produced the expected membership before or after a cost rollup or cost update executes. Because the table is regenerable, queries are typically scoped tightly by LIST_ID.

• Retrieve the full membership of a list: SELECT LIST_ID, ENTITY_ID FROM BOM.CST_LISTS WHERE LIST_ID = :list_id;
• Count the entities per list to validate exploder output volume: SELECT LIST_ID, COUNT(*) FROM BOM.CST_LISTS GROUP BY LIST_ID;
• Detect a specific entity across recent lists: SELECT LIST_ID FROM BOM.CST_LISTS WHERE ENTITY_ID = :entity_id;
• Identify duplicate membership anomalies, which should be impossible given CST_LISTS_U1: SELECT LIST_ID, ENTITY_ID, COUNT(*) FROM BOM.CST_LISTS GROUP BY LIST_ID, ENTITY_ID HAVING COUNT(*) > 1;

Reporting against CST_LISTS is generally limited to troubleshooting and to supporting reconciliation of the CMCCOC, CMCICU, CMCMEC, and CMRICU programs. It is not a source for historical or financial reporting, and its rows should not be treated as an auditable record of cost outcomes.

Related Objects

The documented metadata records no outbound foreign keys, so CST_LISTS references no database object. It is referenced by the APPS synonym CST_LISTS, which is the normal access path for concurrent programs and for ad hoc SQL executed in the APPS schema. The functional dependencies are programmatic rather than declarative and center on the concurrent programs that consume the exploder's output:

• CMCCOC (Cost Rollup / Cost Concurrent) — consumes list membership to drive cost rollup processing.
• CMCICU (Inventory Cost Update) — uses the list to constrain which entities are costed.
• CMCMEC (Cost Management entity processor) — reads the list to determine processing scope.
• CMRICU (Resource / Item Cost Update) — consumes lists for its update scope.
• The item list exploder — the producing component that inserts rows into CST_LISTS for each of the above consumers.

Because ENTITY_ID is generic and no foreign key is enforced, joins to item, cost, or organization tables must be constructed by the consuming program or by the developer, using the exploder context to determine the correct target. This absence of referential integrity is the defining characteristic of CST_LISTS: it is a lightweight, non-logged work structure whose correctness depends on the exploder and its consumers rather than on database constraints.