Search Results cz_addresses_pk




Overview
Explore in AI Chat

Overview

The CZ_ADDRESSES table is a data object within the CZ (Configurator) schema of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It was historically designed to store address information for entities managed within the Configurator module, such as customers and contacts. However, as explicitly noted in the ETRM documentation, this table is now marked as "OBSOLETE, MDApp only." This status indicates that the table is no longer actively developed or used by the core Configurator application for new implementations. Its primary remaining purpose is to support the Model Development Application (MDApp), a legacy tool used for developing configuration models, suggesting its data is maintained for backward compatibility and migration purposes rather than for transactional processing in the live system.

Key Information Stored

Based on the provided metadata, the central column for uniquely identifying a record is ADDRESS_ID, which serves as the primary key (CZ_ADDRESSES_PK). A critical relational column is CUSTOMER_ID, which links an address to a specific customer record in the CZ_CUSTOMERS table via a foreign key constraint. While the full column list is not detailed in the excerpt, a table of this nature would typically store standard address attributes such as address lines, city, state, postal code, and country. The foreign key relationships confirm it stores both bill-to and ship-to addresses for quotes, as well as general addresses for contacts.

Common Use Cases and Queries

Given its obsolete status, direct operational use cases in production EBS environments are minimal. Its primary use is within the context of the MDApp tool for model development and potentially for data migration or historical reporting on legacy configuration data. Sample queries would typically involve joining to related customer or quote tables to retrieve associated address information for analysis. For instance, a query to list addresses for a specific customer might follow this pattern:

  • SELECT addr.* FROM cz.cz_addresses addr WHERE addr.customer_id = <CUSTOMER_ID>;

For reporting on quote addresses, a join to CZ_QUOTE_HDRS would be necessary:

  • SELECT qh.quote_number, bill_addr.address_line1 AS bill_to, ship_addr.address_line1 AS ship_to FROM cz.cz_quote_hdrs qh LEFT JOIN cz.cz_addresses bill_addr ON qh.billto_address_id = bill_addr.address_id LEFT JOIN cz.cz_addresses ship_addr ON qh.shipto_address_id = ship_addr.address_id;

Related Objects

The CZ_ADDRESSES table maintains several defined foreign key relationships, as documented. It is a parent table referenced by:

  • CZ_ADDRESS_USES: Links via ADDRESS_ID, likely for categorizing address purposes.
  • CZ_CONTACTS: Links via ADDRESS_ID to associate contacts with specific addresses.
  • CZ_QUOTE_HDRS: Referenced twice, for both BILLTO_ADDRESS_ID and SHIPTO_ADDRESS_ID columns, defining billing and shipping addresses for quotes.

Conversely, it is a child table to:

  • CZ_CUSTOMERS: References via CUSTOMER_ID, tying addresses to a customer record.

These relationships illustrate its former role as a central hub for address data within the Configurator module's customer and quote management structures.