Results for “cz_config_attributes”

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

Overview

CZ_CONFIG_ATTRIBUTES is a configuration-item attributes table within the Oracle Configurator (CZ) product module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the descriptive attribute values that qualify a configured item — that is, the characteristic data captured against a specific configuration header, revision, and configuration item combination. In this sense the table is a dependent detail store that extends the core configuration item record with an attribute-category-scoped set of values.

From a data modeling perspective, the metadata classifies CZ_CONFIG_ATTRIBUTES as satellite-leaning. This heuristic reflects the fact that the table is keyed primarily by identifiers that derive their meaning from a parent configuration item, and that its main payload is descriptive attribute data rather than relationships between independent business entities. A modeler would therefore treat it in a Data Vault design as a satellite attached to the CZ_CONFIG_ITEMS hub, rather than as a hub or link in its own right.

Key Information Stored

The table is keyed by the unique index CZ_CONFIG_ATTRIBUTES_PK, which comprises four columns: CONFIG_HDR_ID, CONFIG_REV_NBR, CONFIG_ITEM_ID, and ATTRIBUTE_CATEGORY. In Oracle EBS Configurator terminology, CONFIG_HDR_ID identifies the configuration header (the CN transaction or configuration instance), CONFIG_REV_NBR identifies the revision of that configuration, and CONFIG_ITEM_ID identifies the specific configured item within it. ATTRIBUTE_CATEGORY provides the descriptive-flexfield context that qualifies which set of attributes applies to that item.

Unlike a synthetic surrogate key, this primary key is a composite business-key candidate drawn from the parent configuration structure. Business consumers should note that the same CONFIG_ITEM_ID can carry multiple rows distinguished by ATTRIBUTE_CATEGORY.

The descriptive payload is dominated by thirty generic columns, ATTRIBUTE1 through ATTRIBUTE30. These follow the standard Oracle EBS flexible-attribute convention and are populated according to the attribute category defined for the configuration item. They hold the actual configured characteristic values.

Standard audit and lifecycle columns are also present: DELETED_FLAG marks soft-deleted rows, while CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide the usual who-and-when tracking. In total the documented physical schema contains 40 columns.

Common Use Cases and Queries

Typical use cases center on reporting and extracting the configured attribute values for a given configuration or item. A frequent pattern joins CZ_CONFIG_ATTRIBUTES to CZ_CONFIG_ITEMS on CONFIG_HDR_ID, CONFIG_REV_NBR, and CONFIG_ITEM_ID, filtering by ATTRIBUTE_CATEGORY to isolate a particular attribute group:

• Retrieving all attribute rows for a single configuration header and revision, ordered by CONFIG_ITEM_ID, to reconstruct the full configured bill of attributes.
• Filtering on DELETED_FLAG to exclude soft-deleted rows from active reporting.
• Auditing changes through CREATION_DATE / LAST_UPDATE_DATE ranges to track when configuration attributes were captured or amended.
• Reporting on populated ATTRIBUTEn columns per ATTRIBUTE_CATEGORY to understand which flexible attributes are actually in use.

Related Objects

The most significant relationship is to CZ_CONFIG_ITEMS. The foreign key from CZ_CONFIG_ATTRIBUTES references CZ_CONFIG_ITEMS through CONFIG_HDR_ID, CONFIG_REV_NBR, and CONFIG_ITEM_ID, making the item record the parent of each attribute row. Because the primary key and the foreign key share these same leading columns, joins between the two tables are naturally formed on CONFIG_HDR_ID, CONFIG_REV_NBR, and CONFIG_ITEM_ID, with ATTRIBUTE_CATEGORY used to scope the attribute set. Oracle Configurator also exposes configuration data through related configuration header and revision structures and through the Configurator runtime and its published application programming interfaces, which read and write configuration item attributes through the CZ schema. Reporting solutions typically layer views over CZ_CONFIG_ATTRIBUTES and CZ_CONFIG_ITEMS to present configured characteristics to order management and manufacturing consumers.