Search Results persistent_component_id

Overview

CZ_CONFIG_HDRS_V is an Oracle E-Business Suite APPS schema view belonging to the Configurator (CZ) product family, which forms part of the Oracle Configurator / ETRM (Enterprise Territory and Revenue Management) application stack. As documented in the ETRM 12.1.1 and 12.2.2 metadata, the view is described as the "Client view of Saved-Configuration headers." It presents a filtered, user-facing projection of the configuration header records that underlie a configured model instance — that is, the header-level data representing a saved (persisted) runtime configuration created when a user configures a model, such as an item or a quote within Oracle Configurator.

The design intent of the view is to expose a stable interface for client-side code and reporting. It layers a business filter over the physical header table by restricting output to rows where DELETED_FLAG equals '0', thereby hiding soft-deleted configurations. This makes the view a reliable source for integration points, custom reports, and diagnostics that must reflect only live configuration headers without requiring callers to apply the deletion predicate themselves.

Underlying Base Objects

Per the documented ETRM metadata, CZ_CONFIG_HDRS_V is defined over a single referenced base object: the synonym CZ_CONFIG_HDRS, which resolves to the physical APPS table of the same name. The view text is a direct column selection with one WHERE predicate:

• Base object: CZ_CONFIG_HDRS (accessed through its synonym).
• Filter: WHERE DELETED_FLAG = '0'.
• Projection: all significant header columns, including PERSISTENT_COMPONENT_ID and configuration-model metadata such as MODEL_INSTANTIATION_TYPE and COMPONENT_INSTANCE_TYPE.

The view therefore carries no joins and no aggregation; it is a single-table projection. Because it is a view, availability of the underlying synonym and table privileges must be in place for any consumer schema or reporting tool querying it.

Key Columns

The view exposes the full documented column list of CZ_CONFIG_HDRS. Notable columns include:

• CONFIG_HDR_ID — Primary identifier of the saved-configuration header; the principal key for joining to configuration detail and component tables.
• CONFIG_STATUS — Lifecycle status of the saved configuration.
• NAME, CONFIG_REV_NBR, BASELINE_REV_NBR — Configuration name and revision/baseline revision numbering.
• PERSISTENT_COMPONENT_ID — The identifier of the persistent component instance associated with the header. This is the column most relevant to the search term that led here, and it enables linkage from a saved configuration header back to its persisted component identity.
• COMPONENT_ID, COMPONENT_INSTANCE_TYPE, MODEL_IDENTIFIER — Identify the underlying component and the instantiation characteristics of the model.
• UI_DEF_ID, OPPORTUNITY_HDR_ID — Reference to the configurator UI definition and to the associated opportunity, supporting CRM-side traceability.
• CONFIG_DATE_CREATED, USER_ID_CREATED, USER_ID_FOR_WHOM_CREATED — Audit and ownership attributes.
• EFFECTIVE_USAGE_ID, EFFECTIVE_DATE — Effective-dating and usage context for the configuration.
• HAS_FAILURES, MODEL_POST_MIGR_CHG_FLAG — Flags indicating runtime failures and post-migration changes.
• USER_NUM01–04, USER_STR01–04 — Extensible user-defined attribute slots.
• DELETED_FLAG — Retained for transparency, always '0' in rows returned by this view.

Common Use Cases and Queries

Because the view already excludes soft-deleted headers, it is the preferred source for any report or interface seeking current saved configurations. Typical scenarios include identifying all configurations created for a model, tracing a header to its persistent component, and auditing configurations that recorded failures.

List all live configuration headers for a given model:

• SELECT CONFIG_HDR_ID, NAME, CONFIG_STATUS, CONFIG_REV_NBR, PERSISTENT_COMPONENT_ID FROM APPS.CZ_CONFIG_HDRS_V WHERE MODEL_IDENTIFIER = :model_identifier ORDER BY CONFIG_DATE_CREATED DESC;

Locate the header corresponding to a known persistent component:

• SELECT CONFIG_HDR_ID, NAME, CONFIG_STATUS, CONFIG_DATE_CREATED FROM APPS.CZ_CONFIG_HDRS_V WHERE PERSISTENT_COMPONENT_ID = :persistent_component_id;

Review configurations that experienced failures:

• SELECT CONFIG_HDR_ID, NAME, MODEL_IDENTIFIER, HAS_FAILURES, CONFIG_DATE_CREATED FROM APPS.CZ_CONFIG_HDRS_V WHERE HAS_FAILURES = 'Y';

These patterns make the view suitable for both ad hoc DBA investigation and repeatable reporting against the Configurator data model.