Results for “edwcmpallclasses”

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

Overview

EDWCMPALLCLASSES is a metadata repository table owned by the BIS schema and shipped with Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Business Intelligence / BIS product family and functions as the persistent store for the class definitions used by the Oracle E-Business Suite Data Warehouse and ETL metadata layer. In practical terms, the table registers the classification of warehouse elements — such as dimensions, hierarchies, transformations, mapping types, and configuration objects — that participate in the extract, transform, and load processes executed by the Oracle Warehouse Builder-derived components embedded in EBS.

The ETRM metadata for this object records 729 documented columns, which reflects a denormalized, attribute-rich design intended to describe a wide variety of metadata element classes through a single generic structure. The primary key is defined as IDX_ELEMENTID on the documented schema, and a secondary unique index I_2 is also present. The table is flagged as "Not implemented in this database" in the ETRM reference, meaning its physical presence depends on whether the BIS metadata component has been installed and instantiated. Administrators who search for "idx_elementid" are typically inspecting the primary key constraint or resolving a missing-index error in a partially configured environment. The heuristic Data Vault classification mined from the foreign key structure is standalone — a modeling suggestion that this object behaves as an independent reference entity rather than as a hub, link, or satellite, and that it can be treated as a code or class reference table when designing a dimensional or Data Vault model.

Key Information Stored

The most significant columns in EDWCMPALLCLASSES describe the identity, behavior, and classification of each metadata element class. They include:

• ELEMENTID — the surrogate identifier underpinning the primary key IDX_ELEMENTID; it uniquely identifies each class element.
• ELEMENT and CLASSNAME — the element name and its implementing class, providing the core business identity of the record.
• NAME, LONGNAME, PLURALNAME, DISPLAYNAME, and ALIAS — labeling attributes used in the metadata browser and generation utilities.
• CATEGORYTYPE, DIMENSIONTYPE, FUNCTIONTYPE, and TYPE — classification fields that group elements by role in the warehouse.
• APPLICATION, APPLICATIONID, OWNINGAPPLICATION, MODULENAME, and SOFTWAREMODULE — ownership and product assignment metadata.
• CREATEDBY, CREATIONTIMESTAMP, UPDATEDBY, UPDATETIMESTAMP, VERSION, and METADATAVERSION — audit and versioning columns.
• PARENTID, PARENTCLASSNAME, CHILDLEVEL, and PARENTLEVEL — hierarchy relationships among classes.
• PUBLISHED, SEEDED, VALID, and STATUS — lifecycle and availability flags.

The unique index I_2 provides a secondary business-key candidate, most plausibly on the class name or element/application combination. Users diagnosing problems with the primary key should query ALL_CONSTRAINTS and ALL_IND_COLUMNS for constraint name IDX_ELEMENTID to confirm the indexed column list.

Common Use Cases and Queries

Typical uses include auditing which metadata classes are seeded versus customer-defined, tracing ownership to a specific EBS module, and validating hierarchy consistency for generation utilities. A representative query retrieves the identity and ownership columns for a given class name:

• SELECT ELEMENTID, CLASSNAME, NAME, APPLICATION, STATUS FROM BIS.EDWCMPALLCLASSES WHERE CLASSNAME = :class_name;
• SELECT CLASSNAME, COUNT(*) FROM BIS.EDWCMPALLCLASSES GROUP BY CLASSNAME ORDER BY 2 DESC;
• SELECT c.ELEMENTID, c.CLASSNAME, c.PARENTID FROM BIS.EDWCMPALLCLASSES c WHERE c.PARENTID IS NOT NULL;
• Index inspection: SELECT index_name, column_name, column_position FROM all_ind_columns WHERE table_name = 'EDWCMPALLCLASSES' AND index_name = 'IDX_ELEMENTID';

These patterns support metadata reconciliation reports, impact analysis before ETL regeneration, and troubleshooting when index IDX_ELEMENTID is reported as unusable or missing.

Related Objects

Because the table is classified as standalone, no foreign key relationships were documented, but the following objects are commonly consulted alongside it when investigating ELEMENTID references and metadata dependencies:

• ALL_CONSTRAINTS / ALL_CONS_COLUMNS — resolve the IDX_ELEMENTID primary key definition.
• ALL_IND_COLUMNS / ALL_INDEXES — verify index I_2 and its uniqueness.
• ALL_TAB_COLUMNS — enumerate the 729 documented columns for the BIS-owned table.
• FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — map APPLICATION and MODULENAME values to installed EBS modules.
• DBA_OBJECTS / DBA_TABLES — confirm whether the object exists in the current database, given the "not implemented" flag.
• CMP* family tables — such as CMPITEM, CMPFUNCTION, and CMPRELATION, which describe the runtime metadata objects the classes instantiate.