Search Results msd_cs_clmn_identifiers_pk

Overview

MSD_CS_CLMN_IDENTIFIERS is a table owned by the MSD schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the MSD - Demand Planning product family and stores column identifiers used by Custom Data Streams. In the Oracle Demand Planning architecture, Custom Data Streams allow implementers and administrators to define additional dimensional or measure-based data beyond the standard planning hierarchies. This table supplies the authoritative list of column identifiers that those streams reference, providing the naming and typing metadata that keeps custom stream definitions consistent across the planning engine.

From a data-modeling perspective, the heuristic Data Vault classification inferred from the foreign-key structure is standalone. This suggests the object functions effectively as a reference or lookup entity that is not itself dependent on a parent hub through a declared FK relationship. The primary key, MSD_CS_CLMN_IDENTIFIERS_PK, is defined on the single column COLUMN_IDENTIFIER.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• COLUMN_IDENTIFIER — The surrogate primary key and the core value of the table; holds the identifier used to name or reference a custom data stream column.
• IDENTIFIER_TYPE — Classifies the identifier, distinguishing the category or role the column plays within the custom stream definition.
• SYSTEM_FLAG — Indicates whether the identifier is seeded by the application (system-defined) or created by users.
• CREATION_DATE / CREATED_BY — Standard audit columns recording when and by whom the row was inserted.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification.
• REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the request and program that last touched the row.
• ZD_EDITION_NAME — The editioning column used by Oracle EBS 12.2 online patching infrastructure.

Regarding business-key candidates, the unique index MSD_CS_CLMN_IDENTIFIERS_U1 is defined on the combination (COLUMN_IDENTIFIER, ZD_EDITION_NAME). Because ZD_EDITION_NAME participates, the practical business uniqueness of COLUMN_IDENTIFIER is scoped to the active edition, which is characteristic of edition-enabled 12.2 objects.

Common Use Cases and Queries

Typical use cases center on validating and reporting custom data stream configuration. Administrators may query the table to confirm which identifiers exist before defining a stream, or to audit system versus user-defined entries.

• Listing all user-defined identifiers:

  SELECT COLUMN_IDENTIFIER, IDENTIFIER_TYPE
  FROM   MSD.MSD_CS_CLMN_IDENTIFIERS
  WHERE  SYSTEM_FLAG = 'N';

• Separating seeded from custom identifiers for migration or upgrade assessment.
• Joining to edition views to confirm which identifiers are active in the current patching edition.
• Auditing recent changes by filtering on LAST_UPDATE_DATE, LAST_UPDATED_BY, or PROGRAM_ID.

These queries support configuration reviews, pre-upgrade impact analysis, and troubleshooting of custom stream definitions in Demand Planning.

Related Objects

Because the documented relationship data classifies this object as standalone, no foreign-key parents or children are formally recorded. Related objects are therefore inferred from functional context rather than declared constraints. Significant related objects include the MSD Custom Data Stream definition and instance tables that consume these identifiers, the Demand Planning collections and hierarchies tables (for example, MSD_DP_HIERARCHIES and related dimension tables), the concurrent program and request metadata referenced by the audit columns, and the EBS editioning views over MSD tables in 12.2. Joins are established through COLUMN_IDENTIFIER wherever a custom stream references a column identifier, and through ZD_EDITION_NAME for edition-aware access.