Search Results table_code




Overview

The CZ_PB_TEMP_IDS table is a core data structure within the Oracle Configurator (CZ) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a temporary mapping table that supports the publishing process for configurable models. Specifically, its role is to maintain a transient correlation between source system identifiers (ORIG_ID) and the corresponding remote identifiers generated in the runtime environment during a publishing session. This mapping is essential for accurately deploying and synchronizing configuration models, rules, and data from the development repository to the runtime server, ensuring that all internal references remain intact.

Key Information Stored

The table's structure is designed to track ID mappings for a specific publishing operation. Its primary key, CZ_PB_TEMP_IDS_PK, is a composite key consisting of three columns that uniquely identify each mapping record. The RUN_ID column identifies the specific publishing session or job instance. The TABLE_CODE column specifies the type of Configurator entity (e.g., model, component, rule) to which the IDs belong, acting as a reference to the master table. The ORIG_ID column holds the original source identifier from the development repository. While the provided metadata excerpt does not list all columns explicitly, a typical implementation includes a corresponding REMOTE_ID column to store the identifier generated in the target runtime system, completing the critical source-to-remote mapping.

Common Use Cases and Queries

The primary use case for this table is during and immediately after a model publishing run. It is queried by the Configurator engine to resolve ID references when generating runtime artifacts. Common operational queries include verifying mappings for a specific publishing run or troubleshooting failed publications by examining unmapped records. A typical diagnostic SQL pattern would be:

  • SELECT run_id, table_code, orig_id, remote_id FROM cz_pb_temp_ids WHERE run_id = &RUN_ID_VALUE ORDER BY table_code;

This table is generally not used for direct end-user reporting. Its data is transient and is typically purged after a successful publishing cycle. Its main reporting use case is for technical support to analyze the integrity of the ID translation process within a given RUN_ID.

Related Objects

As a central component of the Configurator publishing subsystem, CZ_PB_TEMP_IDS is intrinsically linked to other CZ schema objects. It is directly referenced by various publishing engine packages and procedures that populate and consume the ID mappings. The TABLE_CODE column logically relates to master data tables in the CZ schema, such as CZ_MODELS, CZ_RULES, or CZ_ITEMS, indicating which entity type the ORIG_ID originates from. The RUN_ID likely correlates with a controlling table or package that manages publishing job queues and statuses. Given its temporary nature, it may also be involved in cleanup routines that purge old session data.

  • Table: CZ_PB_TEMP_IDS 12.1.1

    owner:CZ,  object_type:TABLE,  fnd_design_data:CZ.CZ_PB_TEMP_IDS,  object_name:CZ_PB_TEMP_IDS,  status:VALID,  product: CZ - Configuratordescription: Maps source IDs to remote IDs for Publishing ,  implementation_dba_data: CZ.CZ_PB_TEMP_IDS

  • Table: CZ_PB_TEMP_IDS 12.2.2

    owner:CZ,  object_type:TABLE,  fnd_design_data:CZ.CZ_PB_TEMP_IDS,  object_name:CZ_PB_TEMP_IDS,  status:VALID,  product: CZ - Configuratordescription: Maps source IDs to remote IDs for Publishing ,  implementation_dba_data: CZ.CZ_PB_TEMP_IDS