Results for “cz_model_usages”

50+ results




Overview
Explore in AI Chat

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

Overview

CZ_MODEL_USAGES is a configuration management table within the Oracle E-Business Suite Configurator (CZ) module, owned by the CZ schema. It functions as the usages table for models in Oracle Configurator and is documented with a hard constraint limited to 64 records. Given that the table is small, bounded, and referenced widely through foreign keys rather than being a high-volume transactional store, it acts as a controlled reference or classification list for how configurable models are categorized or applied.

Following the heuristic Data Vault classification mined from its foreign key structure, CZ_MODEL_USAGES is best modeled as a hub-leaning entity. Its surrogate primary key (MODEL_USAGE_ID) and the presence of dependent child tables that reference it directly support treating it as a stable, low-cardinality business key hub around which descriptive satellites (such as the translated CZ_MODEL_USAGES_TL) and relationship links would be built. The 64-record ceiling reinforces that this is a controlled, slowly changing reference set rather than a transactional fact source.

Key Information Stored

The table contains 10 documented columns. The most significant are:

  • MODEL_USAGE_ID — the surrogate primary key defined by the unique index CZ_MODEL_USAGES_PK. It uniquely identifies each usage record and is the target of all inbound foreign keys.
  • NAME — the business-facing identifier for the usage. Together with IN_USE it forms the unique index CZ_MODEL_USAGES_U1, making (NAME, IN_USE) the business-key candidate that distinguishes meaningful usage definitions.
  • IN_USE — a status/flag column indicating whether a given usage is active. Its inclusion in the uniqueness constraint means the same NAME can exist in both active and inactive states across the constraint's scope.
  • DESCRIPTION and NOTE — descriptive text fields that provide human-readable context for each usage.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit (WHO) columns capturing record creation and modification lineage.

Distinguishing the surrogate key (MODEL_USAGE_ID) from the business-key candidate (NAME, IN_USE) is essential when integrating this table into any downstream model or data warehouse.

Common Use Cases and Queries

Typical use cases center on reference lookups, filtering active usages, and joining usage metadata to the models and configurations that reference it. A simple active-usage listing:

  • SELECT MODEL_USAGE_ID, NAME, DESCRIPTION FROM CZ.CZ_MODEL_USAGES WHERE IN_USE = 'Y' ORDER BY NAME;

Resolving configurations to their effective usage requires joining through CZ_CONFIG_HDRS:

Because the table is limited to 64 rows, it is frequently cached in application logic and used as a validation domain. Reporting scenarios include usage-based model counts, translation-aware reports via CZ_MODEL_USAGES_TL, and publication scoping using CZ_PUBLICATION_USAGES. Users should treat it as a low-cardinality dimensional/reference source rather than a fact table.

Related Objects

The foreign key metadata identifies the primary dependent and referencing objects:

  • CZ_CONFIG_HDRS — references CZ_MODEL_USAGES through EFFECTIVE_USAGE_ID, linking configurations to their effective usage.
  • CZ_MODEL_USAGES_TL — the translated (language) child table, joined on MODEL_USAGE_ID, holding language-specific NAME/DESCRIPTION text.
  • CZ_PUBLICATION_USAGES — references this table via USAGE_ID, associating usages with publications.
  • CZ_RP_ENTRIES — references this object through OBJECT_ID, integrating usages into rule-processing entry structures.
  • CZ_MODEL_USAGES_PK and CZ_MODEL_USAGES_U1 — the unique indexes enforcing the surrogate primary key and the (NAME, IN_USE) business key.

These relationships confirm the table's role as a referenced hub within the Configurator data model.