Search Results cz_java_data_types_v




Overview
Explore in AI Chat

Overview

CZ_JAVA_DATA_TYPES_V is a seeded, VALID database view owned by the APPS schema within the Oracle E-Business Suite Configurator (CZ) product family. Its purpose is to expose the subset of Configurator signature records that describe Java data types used by the configuration engine. The view is defined over the CZ_SIGNATURES base table and filters that table so that only records with a signature type of 'JTY' (Java Type) and an active, non-deleted status are returned. Because the view resides in the APPS schema and is registered as a documented object in ETRM, it is treated as a supported, read-only interface for reporting, integration, and diagnostic purposes rather than as a transactional entity in its own right. In practice, it provides a stable, semantically narrowed window onto configuration data types that would otherwise require callers to know the internal SIGNATURE_TYPE and DELETED_FLAG conventions of CZ_SIGNATURES.

Underlying Base Objects

The view is defined exclusively over CZ_SIGNATURES, referenced through a synonym. The defining query is:

SELECT SIGNATURE_ID, NAME, DESCRIPTION, JAVA_DATA_TYPE, DATA_TYPE, SIGNATURE_TYPE, DELETED_FLAG, SEEDED_FLAG, CONFIG_ENGINE_TYPE FROM CZ_SIGNATURES WHERE SIGNATURE_TYPE = 'JTY' AND DELETED_FLAG = '0'

CZ_SIGNATURES stores metadata about the various signatures recognized by Oracle Configurator, including those describing Java data types. Two predicate conditions reduce the result set: SIGNATURE_TYPE = 'JTY' restricts output to Java type definitions, and DELETED_FLAG = '0' excludes logically deleted rows. The view therefore inherits the cardinality, indexing, and join behaviour of the underlying table, and any DML performed against CZ_SIGNATURES is immediately reflected in subsequent queries against the view.

Key Columns

  • SIGNATURE_ID — Primary identifier of the signature record; the unique key inherited from CZ_SIGNATURES.
  • NAME — The name assigned to the Java data type signature, used for display and lookup.
  • DESCRIPTION — Free-text description of the data type, useful for documentation and reporting.
  • JAVA_DATA_TYPE — The Java-side representation of the data type exposed to the configuration engine.
  • DATA_TYPE — The corresponding internal or database-level data type classification.
  • SIGNATURE_TYPE — Always 'JTY' in this view by construction; retained as a column for completeness and joins.
  • DELETED_FLAG — Always '0'; identifies records that have not been logically deleted.
  • SEEDED_FLAG — Indicates whether the record is Oracle-seeded or customer-defined.
  • CONFIG_ENGINE_TYPE — Classifies the type in relation to the configuration engine's processing model.

Common Use Cases and Queries

Typical uses include validating which Java data types are available to a Configurator model, auditing seeded versus custom type definitions, and building reporting extracts that feed external integration or documentation processes.

  • List all Java data types with their Java and internal type mappings: 
    SELECT name, java_data_type, data_type FROM apps.cz_java_data_types_v ORDER BY name;
  • Identify customer-defined (non-seeded) Java types: 
    SELECT signature_id, name, config_engine_type FROM apps.cz_java_data_types_v WHERE seeded_flag = 'N';
  • Join to configuration metadata by signature: 
    SELECT v.name, v.java_data_type FROM apps.cz_java_data_types_v v WHERE v.signature_id = :signature_id;

Because the view is read-only in intent, reporting and integration queries should not attempt DML against it; maintenance of the underlying type definitions belongs in CZ_SIGNATURES.