Search Results cz_persistent_rec_ids




Overview
Explore in AI Chat

Overview

CZ_PERSISTENT_REC_IDS is a table owned by the CZ schema within the Oracle Configurator module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. The table serves as a persistent record identifier registry for Configurator development projects. Its primary function is to track and allocate monolithically increasing record identifiers tied to a specific development project, ensuring that generated configuration records receive unique, non-colliding sequence values that survive across sessions and application restarts.

Under the heuristic Data Vault classification derived from the mined foreign key structure, this table is modeled as a standalone entity. It presents no downstream dependents within the documented FK graph, meaning it functions neither as a conventional hub with multiple satellite relationships nor as a link table joining two or more hubs. In modeling terms, it is best treated as an independent reference or control table scoped to the CZ_DEVL_PROJECTS parent, rather than as a core integration point within the Configurator data model.

Key Information Stored

The table contains eight documented columns. Of these, the columns most significant to functional and reporting purposes are:

  • DEVL_PROJECT_ID — The foreign key to CZ_DEVL_PROJECTS, identifying the Configurator development project to which the persistent record identifier applies. This column anchors the table's scope and forms the leading component of the unique index.
  • MAX_PERSISTENT_REC_ID — The high-water mark of the persistent record identifier allocated for the project. This value drives the next-available identifier logic used during configuration record generation.
  • DELETED_FLAG — A soft-delete indicator. Combined with DEVL_PROJECT_ID, it forms the unique business-key candidate.
  • CREATED_BY — The application user identifier responsible for the initial row creation.
  • CREATION_DATE — The timestamp at which the row was first inserted.
  • LAST_UPDATED_BY — The user identifier associated with the most recent modification.
  • LAST_UPDATE_DATE — The timestamp of the most recent modification, used commonly in incremental extraction and audit reporting.
  • LAST_UPDATE_LOGIN — The login session identifier associated with the last update, useful for session-level auditing.

No surrogate primary key column is documented in the ETRM metadata for this object. Instead, the uniqueness constraint is expressed through the unique index CZ_PERSISTENT_REC_IDS_U1 on the composite of DEVL_PROJECT_ID and DELETED_FLAG. This composite should be regarded as the business-key candidate: within a given project, at most one non-deleted (or one deleted) identifier row is permitted.

Common Use Cases and Queries

The table is queried primarily during Configurator runtime operations and during diagnostic investigation of identifier collisions or sequence gaps. Common scenarios include:

  • Determining the next persistent record identifier available for a project prior to generating new configuration records.
  • Auditing which projects have consumed record identifier ranges and identifying stale or abandoned identifier allocations.
  • Supporting incremental ETL extracts by filtering on LAST_UPDATE_DATE.
  • Troubleshooting duplicate identifier symptoms in Configurator by validating the composite uniqueness of DEVL_PROJECT_ID and DELETED_FLAG.

A representative query retrieves the current identifier high-water mark per active project:

SELECT p.DEVL_PROJECT_ID, p.PROJECT_NAME, r.MAX_PERSISTENT_REC_ID
FROM CZ_DEVL_PROJECTS p, CZ_PERSISTENT_REC_IDS r
WHERE p.DEVL_PROJECT_ID = r.DEVL_PROJECT_ID
AND r.DELETED_FLAG = 'N';

For audit purposes, the last-update columns allow targeted extraction:

SELECT DEVL_PROJECT_ID, MAX_PERSISTENT_REC_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE
FROM CZ_PERSISTENT_REC_IDS
WHERE LAST_UPDATE_DATE >= :p_since_date;

Related Objects

The documented relationship for this table is a foreign key from CZ_PERSISTENT_REC_IDS.DEVL_PROJECT_ID to CZ_DEVL_PROJECTS. The most significant related objects are:

  • CZ_DEVL_PROJECTS — The parent table holding Configurator development project definitions; joined on DEVL_PROJECT_ID.
  • CZ_CONFIG_HDRS / CZ_CONFIG_REVISIONS — Configuration header and revision tables that consume identifiers generated under the project scope.
  • CZ_CFG_ITEMS / CZ_CFG_FEATURES — Configuration item and feature tables whose persisted records rely on the identifier allocation.
  • CZ_PSR_INVENTORY / CZ_PSR_* tables — Persistent record collections associated with generated configuration sessions.
  • CZ_DEVL_PROJECT_VERSIONS — Project versioning table referenced during identifier allocation for multi-version projects.

Administrators and developers should treat CZ_PERSISTENT_REC_IDS as a low-volume, high-integrity control table. Direct DML should be avoided; identifier values should be advanced only through supported Configurator processes.