Search Results product_key




Overview
Explore in AI Chat

Overview

CZ_PRODUCTKEY_LOOKUP_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, belonging to the CZ (Configurator) product family. Its purpose is narrow and deliberately constrained: it returns the distinct set of product keys that identify published Configurator models, restricted to those publications that are eligible for export to Order Management. The view functions as a lookup source rather than a general-purpose reporting object. Downstream Configurator and Order Management code, particularly logic that maps a model publication to an orderable product key, can query this view instead of repeatedly filtering the much larger publication table. Because it exposes only a single column and enforces all filtering internally, the view is best understood as an encapsulated eligibility check for a product key. It remains in VALID status and is compatible with both EBS 12.1.1 and 12.2.2, with the documented metadata reflecting the 12.2.2 reference environment.

Underlying Base Objects

The view is defined over a single synonym, CZ_MODEL_PUBLICATIONS, which resolves to the base table that stores records of Configurator model publications and their export state. No joins are performed; the view is a projection with a filter. The five predicates imposed on the base table define exactly which publication records qualify to surface a product key:

  • DELETED_FLAG = '0' — excludes logically deleted publication records.
  • OBJECT_TYPE = 'PRJ' — restricts to project-type objects, specifically the model publication entries created for exported models.
  • SOURCE_TARGET_FLAG = 'T' — selects the target-side record, i.e., the publication as it exists in the destination environment rather than the source definition.
  • EXPORT_STATUS = 'OK' — requires that the export completed successfully, so only usable publications are returned.
  • PRODUCT_KEY IS NOT NULL — discards rows lacking an assigned product key.

The SELECT DISTINCT clause collapses any duplicate product keys that arise when multiple qualifying publication rows share the same key, guaranteeing one row per distinct key.

Key Columns

The view exposes a single column:

  • PRODUCT_KEY — the identifier assigned to a Configurator model publication and used to associate the published model with its orderable product representation. In practice it corresponds to the inventory item or product key under which the configuration is sold. Because the view already filters on non-null values and successful export, every value returned is expected to be a valid, exported product key suitable for downstream reference.

No other columns from CZ_MODEL_PUBLICATIONS are projected, so attributes such as export date, status history, or source system identifiers must be obtained directly from the base table when required.

Common Use Cases and Queries

The primary use case is validating or resolving an orderable product key before it is used by Configurator or Order Management integration logic. Typical patterns include existence checks, populating LOV-style selections, and reconciling keys present in publication data against keys referenced in ordering flows.

To list all eligible product keys:

  • SELECT PRODUCT_KEY FROM APPS.CZ_PRODUCTKEY_LOOKUP_V;

To confirm a specific key is exported and available:

  • SELECT PRODUCT_KEY FROM APPS.CZ_PRODUCTKEY_LOOKUP_V WHERE PRODUCT_KEY = :p_key;

To drive a value set or validation query, the view can be joined to ordering or model tables on PRODUCT_KEY. When additional context is needed — for example, which publication produced a given key or its export details — query CZ_MODEL_PUBLICATIONS directly using the same predicates applied in the view definition. Because the view is a simple synonym-based projection, it carries no additional grants or logic beyond APPS ownership; access follows the standard APPS schema privileges.