Search Results cz_publication_usages_pk




Overview
Explore in AI Chat

Overview

The CZ.CZ_PUBLICATION_USAGES table is a core data object within the Oracle Configurator module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a junction table that defines the applicability of Configurator Publications by mapping them to specific model usages. A publication is a runtime representation of a configurable model, and its applicability determines in which transactional contexts (usages) it is valid for use. This table is critical for ensuring that the correct configuration models are presented in the appropriate business flows, such as sales orders, service requests, or quotations. It is stored in the APPS_TS_SEED tablespace, indicating its role as a seeded, reference data table fundamental to the Configurator's runtime engine.

Key Information Stored

The table is structurally simple but essential, consisting of two mandatory numeric columns that form a composite primary key. The PUBLICATION_ID column uniquely identifies a specific Configurator publication. The USAGE_ID column identifies a specific model usage context to which that publication applies. A single publication can have multiple records in this table, each linking it to a different valid usage. A critical behavioral note documented for some versions of Oracle Configurator is that a USAGE_ID value of -1 is a special indicator meaning the publication is applicable to "all usages." The integrity of these relationships is enforced by the unique primary key index, CZ_PUBLICATION_USAGES_PK, on the combination of PUBLICATION_ID and USAGE_ID.

Common Use Cases and Queries

The primary use case is administrative and diagnostic: verifying or auditing the applicability rules for Configurator publications. For instance, an implementer may need to list all usages for which a specific publication is valid, or identify all publications applicable to a particular usage context. A common reporting requirement is to join this table to the base publication and usage master tables to get descriptive names. The fundamental query, as indicated in the ETRM, is a direct selection from the table. A more practical, descriptive query would join to related master data, for example:

  • Identifying all usages for a given publication:
    SELECT cpu.USAGE_ID FROM cz.cz_publication_usages cpu WHERE cpu.publication_id = <ID>;
  • Finding publications applicable to a specific usage (or the special 'all usages' flag):
    SELECT cpu.PUBLICATION_ID FROM cz.cz_publication_usages cpu WHERE cpu.usage_id = <ID> OR cpu.usage_id = -1;

Related Objects

As a junction table, CZ.CZ_PUBLICATION_USAGES sits between master data tables for publications and usages. It will have a foreign key relationship to a publications master table (e.g., CZ_PUBLICATIONS) on the PUBLICATION_ID column and to a usages master table on the USAGE_ID column. The dependency information confirms it is referenced by an object in the APPS schema named CZ_PUBLICATION_USAGES, which is likely a public synonym or a view that provides a non-owner access point to the underlying CZ schema table, adhering to EBS standards. This structure ensures that runtime components in the APPS schema can resolve publication applicability without direct access to seed data in the CZ schema.