Search Results cz_imp_devl_project




Overview
Explore in AI Chat

Overview

CZ_IMP_DEVL_PROJECT is a staging and interface table within the Oracle Configurator (CZ) module of Oracle E-Business Suite, documented under release 12.1.1 and 12.2.2. The table holds data destined for import into, or rejection from, the CZ_DEVL_PROJECTS table. In the Configurator development cycle, projects represent a developer's working context — a container for modeling an item's configurable features, option classes, and rules. Rather than writing directly into the production development-project table, the import process lands candidate records in CZ_IMP_DEVL_PROJECT, validates them, and either promotes them to CZ_DEVL_PROJECTS or flags them as rejected. This separation protects the live model repository from malformed or partially loaded data.

The ETRM documentation records 35 columns owned by the CZ schema, with the object status marked VALID. The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning the table functions as neither a pure hub, link, nor satellite from a strict Data Vault modeling perspective. When modeling this source, it is best treated as a transient staging entity whose rows are short-lived and whose purpose is pipeline validation rather than long-term history retention.

Key Information Stored

Two foreign keys anchor the table to the Configurator core. DEVL_PROJECT_ID references CZ_DEVL_PROJECTS and serves as the principal business-key candidate linking a staging row to its target development project. INTL_TEXT_ID references CZ_INTL_TEXTS and associates internationalized descriptive text with the record. Because CZ_DEVL_PROJECTS supplies the DEVL_PROJECT_ID, that column is the natural join path; no independent surrogate key is documented in the metadata, so DEVL_PROJECT_ID and INTL_TEXT_ID together identify the staging row's relationships.

Additional flags such as SEEDED_FLAG, PERSISTENT_PROJECT_ID, CHECKOUT_USER, and CONFIG_ENGINE_TYPE support lifecycle and engine-specific behavior during import.

Common Use Cases and Queries

The most frequent operational need is inspecting the outcome of an import batch. Administrators query by RUN_ID and REC_STATUS to find rejected rows and their rejection reason, or to confirm successful promotion into CZ_DEVL_PROJECTS.

  • Monitor a specific run: SELECT devl_project_id, name, rec_status, disposition FROM cz_imp_devl_project WHERE run_id = :run_id;
  • Isolate rejects: SELECT * FROM cz_imp_devl_project WHERE rec_status = 'REJECTED';
  • Validate promotion: compare staging rows against CZ_DEVL_PROJECTS on DEVL_PROJECT_ID to detect rows that failed to load.
  • Purge stale staging data by CRATION_DATE for housekeeping.
  • Join to CZ_INTL_TEXTS via INTL_TEXT_ID to retrieve translated descriptions for user-facing error reports.

Related Objects

  • CZ_DEVL_PROJECTS – target table; joined on DEVL_PROJECT_ID.
  • CZ_INTL_TEXTS – internationalized text; joined on INTL_TEXT_ID.
  • CZ_IMP_* companion tables – sibling staging tables for related configurator entities loaded in the same run.
  • CZ_CFG_* model tables – downstream consumers of the promoted project definition.
  • MTL_SYSTEM_ITEMS_B / MTL_ITEM_REVISIONS – referenced indirectly through TOP_ITEM_ID and INVENTORY_ITEM_ID for item context.
  • FND_USER – resolves CREATED_BY/LAST_UPDATED_BY for audit reporting.