Results for “cz_global_caption_properties_v”

20 results




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

Overview

CZ_GLOBAL_CAPTION_PROPERTIES_V is a reporting and integration view owned by the APPS schema within the Oracle Configurator (CZ) product family. It exposes a filtered, display-ready projection of the global caption properties defined for a Configurator model, presenting one row per distinct caption property. Captions in Oracle Configurator are the system property type (SYSTEM_PROPERTY_TYPE = 'CAP') that drive the user-facing labels rendered against configurable nodes and option features during a configuration session. Because the view joins across the property and data-type layers, it delivers both the raw property attributes and a formatted display name in a single, denormalized result set.

Its principal role is to support reporting on how captions are defined across a model's global property set, to assist in diagnosing duplicate or conflicting caption definitions, and to serve as a lightweight integration source when extracting Configurator metadata into external reporting or migration utilities. The view is documented as VALID in both 12.1.1 and 12.2.2, and depends on two other views plus a profile package rather than on base tables directly.

Underlying Base Objects

The ETRM metadata documents three referenced base objects:

  • CZ_GLOBAL_PROPERTIES_V (VIEW) — the primary driver. Referenced with the alias MAINPROP in the FROM clause and filtered to SYSTEM_PROPERTY_TYPE = 'CAP'. A second correlated reference to this same view, aliased DUPPROP, is used to detect sibling caption properties that share a property name but differ in PROPERTY_ID.
  • CZ_DATA_TYPES_V (VIEW) — referenced with the alias SIG and joined on SIG.SIGNATURE_ID = MAINPROP.DATA_TYPE. It supplies the data-type signature name used to decorate the generated caption token.
  • FND_PROFILE (PACKAGE) — the Oracle Application Object Library profile package, cited as a referenced object and used in the Configurator context to resolve profile-dependent behavior at runtime.

Because the definition is built entirely over views, it inherits the security and filtering behavior of the Configurator global-property layer, including any responsibility- or organization-based predicates applied there.

Key Columns

  • PROPERTY_ID — the unique identifier of the caption property row.
  • PROPERTY_NAME — the internal, system-assigned property name.
  • NAME — a computed column formed by concatenating PROPERTY_TOKEN with an optional bracketed data-type signature. The signature suffix appears only when a duplicate caption property (same name, different ID) exists.
  • DATA_TYPE — the signature identifier of the property's data type, joined to CZ_DATA_TYPES_V.
  • ATTACHED_TO_NODE_TYPE — indicates the node type to which the caption is bound.
  • MUTABLE_FLAG — whether the caption property may be modified.
  • COLLECTION_FLAG — whether the property represents a collection rather than a scalar value.
  • SEQ_NBR — the ordering sequence applied to the property.

Common Use Cases and Queries

Typical scenarios include enumerating all caption properties for review, identifying duplicate property names, and exporting caption metadata for migration or audit. A basic listing follows:

SELECT property_id, property_name, name, data_type, seq_nbr
FROM apps.cz_global_caption_properties_v
ORDER BY property_name, seq_nbr;

To surface only those captions whose generated NAME carries a data-type signature — a reliable indicator of a duplicate definition — filter on the presence of the bracketed token:

SELECT property_id, property_name, name
FROM apps.cz_global_caption_properties_v
WHERE name LIKE '% [%]';

For a concise inventory of caption mutability and attachment, use:

SELECT attached_to_node_type, mutable_flag, collection_flag,
       COUNT(*) AS caption_count
FROM apps.cz_global_caption_properties_v
GROUP BY attached_to_node_type, mutable_flag, collection_flag;

Because the view is read-only and derives its rows from other Configurator views, no DML should be issued against it; all querying should be performed under a responsibility with access to the Configurator global property data.