Search Results event_binding_scope

Overview

CZ_CX_EVENT_DEFS_V is an APPS-owned view within the Oracle E-Business Suite Configurator (CZ) product family. It presents a filtered, reporting-friendly projection of event-type signature definitions that are registered in the Configurator extensibility framework. In Oracle EBS 12.1.1 and 12.2.2, the CZ_SIGNATURES table stores the master definitions for signatures, models, and events used by Oracle Configurator and its integration points, including Oracle Advanced Pricing and Order Management. This view isolates only those rows whose SIGNATURE_TYPE is 'EVT' and whose DELETED_FLAG is '0', thereby exposing active event definitions without the overhead of filtering raw base-table content.

Because the view exposes EVENT_BINDING_SCOPE—the column most frequently searched in this context—it is commonly used to determine the scope at which a given configuration event is bound. This makes the view relevant for diagnostics, upgrade validation, and integration reporting, where developers and functional analysts need to confirm which event definitions are active and how they are scoped before wiring them into configuration rules, extensibility hooks, or interface programs.

Underlying Base Objects

The view is defined over CZ_SIGNATURES, referenced through the APPS synonym. Its defining query is:

SELECT SIGNATURE_ID, NAME, DESCRIPTION, EVENT_BINDING_SCOPE, SIGNATURE_TYPE, DELETED_FLAG, SEEDED_FLAG FROM CZ_SIGNATURES WHERE SIGNATURE_TYPE = 'EVT' AND DELETED_FLAG = '0'

Documented ETRM metadata also associates the view with CZ_DEVL_PROJECTS (SYNONYM), CZ_MODEL_PROP_ENGTYP_COMPAT_V (VIEW), and the FND_PROFILE package. These references reflect the broader dependency footprint of the Configurator signature and event framework: CZ_DEVL_PROJECTS supports extensibility development contexts, CZ_MODEL_PROP_ENGTYP_COMPAT_V supports model/property/engineering-type compatibility resolution, and FND_PROFILE supplies environment and user-level profile option values used during runtime resolution. The view itself remains a thin projection; it does not join these objects directly, but its output is consumed alongside them.

Key Columns

• SIGNATURE_ID — Primary identifier for the signature record; used as the foreign key when joining to related Configurator tables.
• NAME — The internal name of the event signature, typically the event identifier referenced by configuration rules and extensions.
• DESCRIPTION — User-facing description of the event, useful in reporting and diagnostics.
• EVENT_BINDING_SCOPE — Indicates the scope at which the event binding applies, distinguishing event definitions by their functional reach (for example, model-level versus component-level binding). This is the column most commonly queried when validating event configuration.
• SIGNATURE_TYPE — Always 'EVT' in this view, since the WHERE clause restricts results to event signature definitions.
• DELETED_FLAG — Always '0' in this view; indicates the record is active and not logically deleted.
• SEEDED_FLAG — Identifies whether the event definition was delivered by Oracle as seed data or created by a customer. Useful for upgrade-impact analysis.

Common Use Cases and Queries

The view is typically used to inventory active event definitions, audit seeded versus customer-defined events, and confirm binding scope before deploying configuration extensions.

List all active event definitions:

SELECT SIGNATURE_ID, NAME, EVENT_BINDING_SCOPE, SEEDED_FLAG FROM APPS.CZ_CX_EVENT_DEFS_V ORDER BY NAME;

Filter by binding scope:

SELECT SIGNATURE_ID, NAME, DESCRIPTION FROM APPS.CZ_CX_EVENT_DEFS_V WHERE EVENT_BINDING_SCOPE = :p_scope;

Identify customer-defined events:

SELECT SIGNATURE_ID, NAME FROM APPS.CZ_CX_EVENT_DEFS_V WHERE SEEDED_FLAG = 'N';

Join to signature usage detail:

SELECT e.NAME, e.EVENT_BINDING_SCOPE, s.USAGE_CONTEXT FROM APPS.CZ_CX_EVENT_DEFS_V e, APPS.CZ_SIGNATURES s WHERE e.SIGNATURE_ID = s.SIGNATURE_ID;

These queries support ongoing maintenance and pre-upgrade assessment of Configurator event extensibility.