Results for “attribute_group”

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

Overview

CZ_CONFIG_EXT_ATTRIBUTES is a Configurator (CZ) module table in the Oracle E-Business Suite database, owned by the CZ schema. It stores extended attribute values attached to configuration items, providing the fully-normalized attribute attachment used for Installed Base integration. In functional terms, whenever a configured item is instantiated, the descriptive characteristics captured during configuration — beyond the core item definition — are persisted as individual attribute rows in this table. These attributes supply the detail that downstream Installed Base (CSI) records require to describe the as-built configuration of an asset.

The table's primary key, CZ_CONFIG_EXT_ATTRIBUTES_PK, is a composite of CONFIG_HDR_ID, CONFIG_REV_NBR, CONFIG_ITEM_ID, and ATTRIBUTE_NAME. This composite structure means each row is uniquely identified by the combination of the parent configuration, its revision, the specific configuration item, and the attribute name. Rather than storing attributes as repeated columns or delimited strings, the design normalizes them into one row per attribute per configuration item — an approach that supports arbitrary attribute sets without schema changes.

Under the heuristic Data Vault classification provided in the metadata, this object is characterized as satellite-leaning. In Data Vault modeling terms, that classification suggests this table functions primarily as a descriptive satellite attached to a parent configuration item key, holding attribute-level detail rather than acting as an independent hub or a pure associative link. The composite primary key reinforces this reading: the configuration header, revision, and item identifiers together form the parent key, while ATTRIBUTE_NAME and its associated value columns supply the descriptive payload.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are:

• CONFIG_HDR_ID — Identifier of the parent configuration header. Part of the primary key and the foreign key reference to CZ_CONFIG_ITEMS.
• CONFIG_REV_NBR — Configuration revision number. Part of the primary key, enabling multiple revisions of the same configuration to coexist.
• CONFIG_ITEM_ID — The specific configuration item within the configuration to which the attribute belongs. Part of the primary key.
• ATTRIBUTE_NAME — The name of the extended attribute. Completes the primary key and determines the identity of each attribute row.
• ATTRIBUTE_GROUP — Logical grouping of the attribute, useful for organizing related attributes together in reporting and presentation.
• ATTRIBUTE_VALUE — The actual value captured for the named attribute. This is the principal descriptive payload and the column most often queried.
• DELETED_FLAG — Soft-delete indicator, allowing attribute rows to be logically retired without physical removal.
• SEQUENCE_NBR — Ordering sequence, permitting attributes to be presented in a defined order within their group.
• CREATION_DATE, CREATED_BY — Standard Oracle audit columns recording when and by whom the row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle audit columns recording the most recent modification and the associated login session.

The primary key CZ_CONFIG_EXT_ATTRIBUTES_PK is the only documented unique index and therefore the sole business-key candidate. No separate surrogate key column is documented; the composite business key serves directly as the primary key, which is consistent with the satellite-leaning classification.

Common Use Cases and Queries

The most common requirement is retrieving all extended attributes for a given configuration item, typically to reconcile configuration data with Installed Base records or to produce as-built documentation.

• Retrieve attributes for a configuration item. Filter on the composite key components and exclude soft-deleted rows:

  SELECT attribute_name, attribute_group, attribute_value, sequence_nbr
  FROM   cz.cz_config_ext_attributes
  WHERE  config_hdr_id  = :p_config_hdr_id
  AND    config_rev_nbr = :p_rev
  AND    config_item_id = :p_item_id
  AND    NVL(deleted_flag, 'N') = 'N'
  ORDER  BY attribute_group, sequence_nbr;
  

• Locate a specific attribute value. Because ATTRIBUTE_NAME is part of the primary key, lookups by name are efficient and well supported.
• Attribute inventory reporting. Aggregating distinct ATTRIBUTE_NAME values across configurations reveals which attributes are actively populated, supporting configuration model governance.
• Audit and change tracking. The LAST_UPDATE_DATE and LAST_UPDATED_BY columns support queries identifying recently modified attribute values for compliance review.
• Installed Base reconciliation. Joining attribute rows to configuration items provides the enriched view required when validating that Installed Base records accurately reflect the configured asset.

Related Objects

The documented foreign key relationship establishes the principal dependency:

• CZ_CONFIG_ITEMS — The parent table. CZ_CONFIG_EXT_ATTRIBUTES.CONFIG_HDR_ID, CONFIG_REV_NBR, and CONFIG_ITEM_ID reference CZ_CONFIG_ITEMS, forming the association between attribute rows and their configuration item.

Beyond the documented foreign key, adjacent Configurator objects commonly referenced in the same functional area include the configuration header and revision structures within the CZ schema and the Installed Base tables in the CSI schema, which consume these attribute values during asset registration and update. Queries joining CZ_CONFIG_EXT_ATTRIBUTES to CZ_CONFIG_ITEMS should always carry the full composite key — header, revision, and item — to avoid over-matching across revisions.