Search Results cz_address_uses_pk

Overview

The CZ_ADDRESS_USES table is a data object within the Oracle E-Business Suite (EBS) Configurator (CZ) module. As explicitly stated in its official description, this table is designated as "OBSOLETE" and its functional purpose is limited to "MDApp only for interface to OM." This indicates that the table's active use is confined to the Model and Data Application (MDApp), a component of the Configurator, for interfacing with the Order Management (OM) module. Its role is therefore historical and transitional, serving as a legacy structure to support data mapping and integration between the Configurator and Order Management systems during specific transactional processes, rather than representing a core, actively maintained business entity in later versions of EBS 12.1.1 and 12.2.2.

Key Information Stored

Based on the provided ETRM metadata, the table's structure centers on a primary key and a foreign key relationship. The primary key column is ADDRESS_USE_ID, which uniquely identifies each record. The primary foreign key relationship is defined with the CZ_ADDRESSES table via the ADDRESS_ID column in CZ_ADDRESS_USES. This structure suggests the table was designed to manage different contextual uses or applications (e.g., ship-to, bill-to) for a given address entity stored in CZ_ADDRESSES. The metadata does not list other specific attribute columns, implying the table's schema is minimal, focused primarily on establishing this relationship for integration purposes.

Common Use Cases and Queries

Given its obsolete status and specialized interface role, direct operational or reporting use cases for this table are extremely limited in standard EBS implementations. Interaction would primarily occur through the MDApp layer. A typical query pattern would involve joining to the related CZ_ADDRESSES table to resolve address information for an order interface context. For example:

• Identifying address uses for a specific configuration context: SELECT cau.*, ca.address_line1 FROM cz_address_uses cau, cz_addresses ca WHERE cau.address_id = ca.address_id;
• Data validation or migration scripts might reference this table to ensure referential integrity with the CZ_ADDRESSES table during legacy data audits.

Development or customization involving this table is strongly discouraged due to its obsolete classification.

Related Objects

The table maintains a direct and critical relationship with the CZ_ADDRESSES table via its foreign key on ADDRESS_ID. This is the primary documented relationship. As a component of the Configurator (CZ) module, it may also have implicit or historical relationships with other CZ transactional tables and with the Order Management (OM) module's interface tables, though these are not specified in the provided metadata. The table's primary key constraint is named CZ_ADDRESS_USES_PK. Developers and DBAs should note that any dependencies on this table are likely part of the legacy MDApp-to-OM interface and should be treated with caution.