Results for “cz_eventtypes_lkv”

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

Overview

CZ_EVENTTYPES_LKV is a reporting and lookup view owned by the APPS schema within the Oracle Configurator (CZ) module. Its purpose is to expose the subset of signature definitions that represent event types used by the Configurator runtime and its event-binding framework. The view is a filtered projection over CZ_SIGNATURES, restricting rows to those whose SIGNATURE_TYPE equals 'EVT' and whose DELETED_FLAG equals '0'. Because it presents only active event signatures, it functions as a stable, query-friendly interface for reporting, integration, and lookup purposes without requiring callers to re-implement the filtering predicate or to be aware of the internal signature model.

In Oracle EBS 12.1.1 and 12.2.2 the view remains a VALID object in the APPS schema. It is not a table and stores no data of its own; all content is derived at runtime from the base synonym. This read-only nature makes it safe for ad hoc querying and for use inside concurrent programs, BI Publisher data templates, and OAF/Form personalization lookups.

Underlying Base Objects

The view is defined over a single referenced object: CZ_SIGNATURES, accessed through the CZ_SIGNATURES synonym. CZ_SIGNATURES is the Configurator repository table that holds signature metadata for events, functions, and related extensibility constructs. Each signature row carries a SIGNATURE_TYPE discriminator; CZ_EVENTTYPES_LKV exposes only the 'EVT' rows. The relationship is therefore one of simple vertical filtering: every row returned by the view corresponds to exactly one row in CZ_SIGNATURES, with no joins, aggregations, or derived columns. Because the base object is referenced by synonym rather than by fully qualified name, the view resolves against the APPS-owned synonym chain, ensuring consistent behavior across environments.

Key Columns

• SIGNATURE_ID – Primary identifier of the event signature; the join key back to CZ_SIGNATURES and to event-binding records.
• NAME – Internal name of the event type.
• DATA_TYPE / JAVA_DATA_TYPE – Logical and Java-level data types of the event payload.
• ARGUMENT_COUNT – Number of arguments the event signature accepts.
• COLLECTION_FLAG – Indicates whether the argument is treated as a collection.
• EVENT_BINDING_SCOPE – Scope in which the event may be bound.
• SIGNATURE_TYPE – Always 'EVT' in this view; retained for compatibility with the base table.
• ORIG_SYS_REF – Original system reference, used to trace the origin of a seeded or migrated signature; this is the column most frequently searched by users investigating cross-system or upgrade provenance.
• SEEDED_FLAG – Distinguishes Oracle-seeded definitions from customer-defined ones.
• DELETED_FLAG – Always '0' here; filtering is applied in the view definition.
• DESCRIPTION – Free-text description of the event type.
• Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS who-column auditing.

Common Use Cases and Queries

Typical usage includes enumerating available event types for configuration, tracing seeded definitions by their original reference, and joining event signatures to binding records for impact analysis.

• List all active event types: SELECT signature_id, name, data_type FROM cz_eventtypes_lkv ORDER BY name;
• Find a signature by its original system reference: SELECT signature_id, name, seeded_flag FROM cz_eventtypes_lkv WHERE orig_sys_ref = :ref;
• Count seeded versus customer-defined events: SELECT seeded_flag, COUNT(*) FROM cz_eventtypes_lkv GROUP BY seeded_flag;
• Join to the base table for full metadata: SELECT v.name, s.description FROM cz_eventtypes_lkv v, cz_signatures s WHERE v.signature_id = s.signature_id;

Because the view applies the DELETED_FLAG and SIGNATURE_TYPE predicates, queries against it are shorter and less error-prone than equivalent queries against CZ_SIGNATURES, and they remain insulated from changes to the underlying discriminators.