Search Results signature_type




Overview
Explore in AI Chat

Overview

The view APPS.CZ_JAVA_DATA_TYPES_V is a filtered, read-only projection over the Oracle E-Business Suite configuration management data model. It exists to expose the subset of signature records that describe Java data types, allowing concurrent programs, configuration engine logic, and reporting queries to retrieve Java type definitions without scanning the full signature population maintained by the Configurator (CZ) schema. The view is owned by the APPS schema and is available in both EBS 12.1.1 and 12.2.2, where it is treated as a standard seeded database object.

The defining characteristic of the view is its two-part filter predicate: SIGNATURE_TYPE = 'JTY' and DELETED_FLAG = '0'. The literal 'JTY' identifies Java data type signatures, so every row returned by the view is a non-deleted Java type registration. The view therefore presents a semantically meaningful slice of the signature catalog rather than the complete table contents, which is the primary reason applications reference the view instead of the base table directly.

Underlying Base Objects

The view is defined over a single documented base object: CZ_SIGNATURES, referenced through a synonym. CZ_SIGNATURES is the central repository for signature definitions used by the configuration engine, storing identifiers, descriptive text, type mappings, and status flags for all registered signature categories. Because the view queries only one table with a constant predicate, it is non-updatable in the conventional sense; inserts, updates, and deletes must be directed at CZ_SIGNATURES.

The dependency chain is straightforward: CZ_JAVA_DATA_TYPES_V depends on the synonym for CZ_SIGNATURES, which in turn resolves to the underlying CZ-owned table. Any structural change to CZ_SIGNATURES — such as adding or renaming a column — propagates to the view and can invalidate dependent PL/SQL units until recompilation.

Key Columns

The view projects nine columns from the base table:

  • SIGNATURE_ID — the primary identifier for the signature record; used as the join key throughout the configuration model.
  • NAME — the internal name of the Java data type signature.
  • DESCRIPTION — user-facing descriptive text for the type.
  • JAVA_DATA_TYPE — the Java-side type mapping, typically a fully qualified or canonical Java type designation.
  • DATA_TYPE — the corresponding data type designation used within the configuration data model.
  • SIGNATURE_TYPE — the discriminator column; always evaluates to 'JTY' within this view.
  • DELETED_FLAG — soft-delete indicator; always '0' in this view, excluding logically removed rows.
  • SEEDED_FLAG — indicates whether the row is Oracle-seeded or customer-defined.
  • CONFIG_ENGINE_TYPE — the classification used by the configuration engine to route or interpret the signature.

Common Use Cases and Queries

Typical uses include validating which Java data types are available to the configuration engine, joining type metadata to dependent configuration records, and driving reports on seeded versus customer-defined Java types.

  • List all active Java data types: SELECT SIGNATURE_ID, NAME, JAVA_DATA_TYPE FROM APPS.CZ_JAVA_DATA_TYPES_V ORDER BY NAME;
  • Isolate Oracle-seeded types only: SELECT * FROM APPS.CZ_JAVA_DATA_TYPES_V WHERE SEEDED_FLAG = '1';
  • Join to configuration engine consumers by signature identifier: SELECT v.NAME, v.DATA_TYPE FROM APPS.CZ_JAVA_DATA_TYPES_V v JOIN some_config_table c ON c.SIGNATURE_ID = v.SIGNATURE_ID;

Because SIGNATURE_TYPE, DELETED_FLAG, and SIGNATURE_ID are the principal filtering columns, queries are most efficient when they constrain on those fields or join on the signature identifier.