Results for “usage_id”

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

Overview

CZ_PUBLICATION_USAGES is a Configurator (CZ) module table within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. As documented in the ETRM metadata, the object is owned by the CZ schema and holds a VALID status. Its documented purpose is straightforward: it serves as a join table between publications and usages. In the Configurator data model, publications represent published model structures that can be consumed by external applications or runtime configuration sessions, while usages define how a given model or component is applied within a configuration context. This table materializes the many-to-many association between those two entities.

Applying Data Vault modeling heuristics to the documented foreign-key structure, CZ_PUBLICATION_USAGES is best classified as a link table. It contains no descriptive attributes of its own; rather, it records the association between two independent hubs (publications and usages). This classification is offered as a modeling suggestion derived from the FK topology, not as a formal Oracle designation.

Key Information Stored

The documented physical schema for this table in ETRM 12.2.2 lists only two columns, both of which participate in the primary key. There are no non-key payload columns recorded.

• PUBLICATION_ID — The first component of the composite primary key. This column is a foreign key referencing CZ_MODEL_PUBLICATIONS and identifies the publication side of the association.
• USAGE_ID — The second component of the composite primary key. This column is a foreign key referencing CZ_MODEL_USAGES and identifies the usage side of the association.

The primary key, CZ_PUBLICATION_USAGES_PK, is defined over the column pair (PUBLICATION_ID, USAGE_ID). Because the table contains only these two columns and both are members of the primary key, there is no separate surrogate key distinct from the business-key candidate. The unique index CZ_PUBLICATION_USAGES_PK is the sole documented uniqueness constraint, and it also functions as the business-key candidate. This design enforces that any given publication-usage pairing appears at most once.

Common Use Cases and Queries

Typical usage centers on resolving which publications are associated with which usages, and conversely. Common scenarios include impact analysis before modifying a usage, auditing published configurations, and building reports that bridge the two parent entities.

To list all usages for a given publication:

• SELECT usage_id FROM cz_publication_usages WHERE publication_id = :pub_id;

To list all publications that reference a given usage:

• SELECT publication_id FROM cz_publication_usages WHERE usage_id = :usage_id;

A reporting join to resolve names typically combines this link table with both parent tables:

• SELECT p.publication_id, u.usage_id FROM cz_publication_usages pu JOIN cz_model_publications p ON p.publication_id = pu.publication_id JOIN cz_model_usages u ON u.usage_id = pu.usage_id;

Because the table is narrow and purely relational, it is frequently used as a bridge in BI extracts and in dependency queries that determine whether deleting a usage would orphan any publication associations.

Related Objects

The following objects are documented as directly related through foreign-key and primary-key relationships:

• CZ_MODEL_PUBLICATIONS — Referenced by CZ_PUBLICATION_USAGES.PUBLICATION_ID; the parent hub for the publication side.
• CZ_MODEL_USAGES — Referenced by CZ_PUBLICATION_USAGES.USAGE_ID; the parent hub for the usage side.
• CZ_PUBLICATION_USAGES_PK — The unique index and primary-key constraint defined on (PUBLICATION_ID, USAGE_ID).

These three objects constitute the full documented relationship set for CZ_PUBLICATION_USAGES. Any additional dependencies, such as Configurator runtime or publishing APIs, are not enumerated in the ETRM metadata and should be confirmed against the specific implementation before being relied upon.