Search Results cz_persistent_rec_ids_u1

Overview

CZ.CZ_PERSISTENT_REC_IDS is a configuration and control table within the Oracle E-Business Suite Configurator (CZ) product family, owned by the CZ schema and registered as VALID in the EBS 12.1.1 and 12.2.2 environments. The table is designated as FND Design Data (CZ.CZ_PERSISTENT_REC_IDS), indicating that it is seeded and managed as part of the Oracle Applications data model rather than customer-created data.

Functionally, the table acts as a persistent identifier registry. As stated in the object documentation, it "holds max persistent record id for a migrated model/copy of migrated model." Configurator models and their migrated copies generate persistent node identifiers (ps_node_ids) as users author and modify model structures. When a model is migrated between instances or duplicated, previously issued identifiers must not be re-used within the target model. This table records the high-water mark of those identifiers so that subsequently generated ps_node_id values are guaranteed to exceed any value already consumed.

Under the heuristic Data Vault classification supplied in the metadata, the object is modeled as standalone. Since the structure is keyed by a single business dimension (the model/project identifier) and holds descriptive control state rather than relationships between multiple hubs, it is most naturally treated as a satellite-like reference entity attached to the CZ_DEVL_PROJECTS hub, rather than as a transaction link or a pure hub.

Key Information Stored

The table contains eight documented columns. The most significant are summarized below.

• DEVL_PROJECT_ID (NUMBER, 15) — Model Identifier. This is the foreign key to CZ.CZ_DEVL_PROJECTS and the primary business-key component. It identifies which Configurator development project (model) the persistent record sequence belongs to.
• MAX_PERSISTENT_REC_ID (NUMBER) — The documented business meaning: "If not null, newly generated ps_node_id(s) in the model cannot be less than this value." This is the operational payload of the row, enforcing identifier monotonicity after migration or copy.
• DELETED_FLAG (VARCHAR2) — Software-deletion indicator. It participates in the unique index, allowing a model to be logically removed and subsequently re-registered without violating uniqueness.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard EBS "Who" auditing columns that capture row creation and modification provenance.

The unique index CZ_PERSISTENT_REC_IDS_U1 (NORMAL, UNIQUE, tablespace APPS_TS_TX_IDX) is defined on (DEVL_PROJECT_ID, DELETED_FLAG) and constitutes the documented business-key candidate. No separate surrogate numeric primary key column is documented; the composite of DEVL_PROJECT_ID and DELETED_FLAG serves as the logical unique identifier. All columns are documented as non-mandatory at the physical level except where noted. The table is stored in tablespace APPS_TS_TX_DATA with PCTFREE 10.

Common Use Cases and Queries

Typical scenarios include verifying the identifier ceiling for a migrated model, auditing which models have been copied across environments, and diagnosing duplicate ps_node_id generation after a migration cycle.

Retrieve the ceiling for a specific model:

• SELECT devl_project_id, max_persistent_rec_id FROM cz.cz_persistent_rec_ids WHERE devl_project_id = :project_id AND deleted_flag IS NULL;

Report all active models with recorded ceilings, joined to the project definition:

• SELECT p.project_id, p.project_name, r.max_persistent_rec_id FROM cz.cz_persistent_rec_ids r JOIN cz.cz_devl_projects p ON p.project_id = r.devl_project_id WHERE r.deleted_flag IS NULL ORDER BY p.project_name;

Audit creation and last update provenance for governance purposes:

• SELECT devl_project_id, created_by, creation_date, last_updated_by, last_update_date FROM cz.cz_persistent_rec_ids;

Related Objects

• CZ.CZ_DEVL_PROJECTS — Referenced through the foreign key CZ_PERSISTENT_REC_IDS.DEVL_PROJECT_ID → CZ_DEVL_PROJECTS. This is the principal join partner for model-level reporting.
• APPS.CZ_PERSISTENT_REC_IDS — The APPS-synonym view exposed to application code and concurrent programs.
• APPS.CZ_PERSISTENT_REC_IDS_T1 — The translation (TL) table associated with the base table, commonly present for CZ design data.
• CZ_PERSISTENT_REC_IDS_U1 — The unique index on (DEVL_PROJECT_ID, DELETED_FLAG) that enforces the business key and is the object referenced by the searched term.

The table does not reference any other database object apart from the CZ_DEVL_PROJECTS foreign key, confirming its role as a leaf-level control registry within the Configurator schema.