Results for “cz_config_usages”

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

Overview

CZ_CONFIG_USAGES is a Configurator (CZ) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that records the usage of configuration items by client applications. Each row captures an instance where a caller — identified by an application identifier and an external reference key — consumed a specific configuration item within a configuration header and revision. The table therefore serves as the audit and traceability backbone for Configurator-based selling, pricing, and order-capture integrations, allowing Oracle Order Management, Quoting, iStore, and other calling applications to link their own transactional artifacts back to the configuration structures that produced them.

Reflecting the documented foreign key to CZ_CONFIG_ITEMS on CONFIG_HDR_ID, CONFIG_REV_NBR, and CONFIG_ITEM_ID, the heuristic Data Vault classification for this table is satellite-leaning: it behaves as a descriptive, keyed detail structure hanging off the configuration item hub rather than as an independent master. The composite primary key (CALLING_APPLICATION_ID, CALLING_APPLICATION_REF_KEY, CONFIG_HDR_ID, CONFIG_ITEM_ID, CONFIG_REV_NBR) enforces that a given caller reference can reference a particular configuration item only once per configuration revision.

Key Information Stored

Beyond the five key columns, the table stores pricing, discount, availability, and lifecycle attributes for each usage record. The most significant columns include:

• CALLING_APPLICATION_ID — identifies the client application recording the usage; part of the surrogate primary key.
• CALLING_APPLICATION_REF_KEY — the caller's own reference key (for example, an order or quote line identifier); part of the primary key.
• CONFIG_HDR_ID, CONFIG_REV_NBR, CONFIG_ITEM_ID — foreign keys to CZ_CONFIG_ITEMS identifying the configuration header, revision, and item being used.
• LIST_PRICE, DISCOUNTED_PRICE — the list and net price resolved for the configured item.
• AUTO_DISCOUNT_ID, AUTO_DISCOUNT_LINE_ID, AUTO_DISCOUNT_PCT — the automatically applied discount and its percentage.
• MANUAL_DISCOUNT_ID, MANUAL_DISCOUNT_LINE_ID, MANUAL_DISCOUNT_PCT — the manually applied discount and its percentage.
• ATP_DATE — the available-to-promise date for the configured item.
• UOM_CODE — unit of measure for the usage.
• EFF_FROM, EFF_TO, EFF_MASK — effective-dating controls governing record validity.
• SECURITY_MASK — masking used for access control on the usage record.
• CHECKOUT_USER, DELETED_FLAG — checkout ownership and soft-delete indicator.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard who-columns.

The unique index CZ_CONFIG_USAGES_PK acts as the business-key candidate, guaranteeing uniqueness across the calling application, caller reference, configuration header, revision, and item combination.

Common Use Cases and Queries

Typical scenarios include tracing which orders or quotes consumed a configuration item, reconciling pricing and discount outcomes, and auditing soft-deleted or checked-out usage rows.

• Retrieve all usages for a configuration header joined to CZ_CONFIG_ITEMS on CONFIG_HDR_ID, CONFIG_REV_NBR, and CONFIG_ITEM_ID.
• Filter by CALLING_APPLICATION_ID and CALLING_APPLICATION_REF_KEY to locate the configuration behind a specific caller transaction.
• Report pricing integrity by comparing LIST_PRICE, AUTO_DISCOUNT_PCT, MANUAL_DISCOUNT_PCT, and DISCOUNTED_PRICE.
• Audit deleted or checked-out records using DELETED_FLAG and CHECKOUT_USER, and apply EFF_FROM/EFF_TO for point-in-time analysis.

A representative pattern is:

SELECT u.CALLING_APPLICATION_ID, u.CALLING_APPLICATION_REF_KEY, u.CONFIG_ITEM_ID, u.LIST_PRICE, u.DISCOUNTED_PRICE FROM CZ.CZ_CONFIG_USAGES u WHERE u.CONFIG_HDR_ID = :p_hdr AND u.DELETED_FLAG = 'N'

Related Objects

The principal related object is CZ_CONFIG_ITEMS, joined via the documented foreign key on CONFIG_HDR_ID, CONFIG_REV_NBR, and CONFIG_ITEM_ID. Other Configurator structures that commonly participate in the same reporting and integration flows include configuration header and component tables, discount and pricing definitions referenced by the AUTO_DISCOUNT_ID and MANUAL_DISCOUNT_ID columns, and the calling applications in Oracle Order Management and Quoting that supply CALLING_APPLICATION_ID and CALLING_APPLICATION_REF_KEY. Because the metadata documents only the CZ_CONFIG_ITEMS relation explicitly, additional joins should be validated against the actual instance before use.