Search Results cz_imp_item_type




Overview

CZ_IMP_ITEM_TYPE is a staging and interface table within the Oracle E-Business Suite Configurator (CZ) module, owned by the CZ schema. Its documented purpose is to hold data to be imported into — or rejected from — the CZ_ITEM_TYPES table. In this capacity it functions as an inbound data interface: records are loaded into CZ_IMP_ITEM_TYPE, validated and processed by Configurator import routines, and either promoted to the production CZ_ITEM_TYPES structure or flagged as rejected with a disposition. This pattern is common in EBS, where interface tables decouple bulk or external data loads from the concurrency and integrity constraints of the base transactional tables.

The table is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, with a physical schema of 28 columns. From a Data Vault modeling perspective, the ETRM relationship analysis classifies this object heuristically as standalone. That classification suggests the table is best treated as its own hub-like entity rather than as a satellite hanging off another hub, reflecting the fact that it carries its own identity (a record number and run identifier) independent of the parent item type. The single documented foreign key, ITEM_TYPE_ID referencing CZ_ITEM_TYPES, anchors each staged row to the item type it is intended to create or update.

Key Information Stored

The table's columns divide naturally into import-control fields, business attributes, and standard EBS audit columns.

  • ITEM_TYPE_ID — surrogate key identifying the target item type; the documented foreign key to CZ_ITEM_TYPES and the primary join point between staging and production data.
  • NAME and DESC_TEXT — the business-key candidates describing the item type; NAME is the human-readable identifier used to match staged rows against existing definitions.
  • REC_NBR and RUN_ID — record sequence number and import run identifier, allowing a single import batch to be tracked and rows reprocessed independently.
  • REC_STATUS and DISPOSITION — the processing outcome of each row (for example, pending, imported, or rejected), central to error handling and reconciliation reporting.
  • DELETED_FLAG and REC_STATUS — together support soft-delete semantics and staging lifecycle management.
  • ORIG_SYS_REF and SRC_APPLICATION_ID — capture the originating system reference and source application, enabling traceability when data arrives from external or legacy systems.
  • EFF_FROM, EFF_TO, and EFF_MASK — effective-dating attributes governing when the imported item type definition is valid.
  • USER_STR01USER_STR04 and USER_NUM01USER_NUM04 — four generic character and four generic numeric columns provided for customer-defined extension data.
  • CHECKOUT_USER and SECURITY_MASK — support concurrent editing control and row-level security on staged records.
  • CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified each staged row.

Common Use Cases and Queries

Typical usage centres on monitoring import runs and diagnosing rejected rows. A reconciliation query joins the staging table to its parent to confirm promotion:

SELECT i.REC_NBR, i.NAME, i.REC_STATUS, i.DISPOSITION
FROM   CZ.CZ_IMP_ITEM_TYPE i
WHERE  i.RUN_ID = :run_id
ORDER BY i.REC_NBR;

Rejected-record reporting filters on status and disposition:

SELECT i.NAME, i.ORIG_SYS_REF, i.SRC_APPLICATION_ID
FROM   CZ.CZ_IMP_ITEM_TYPE i
WHERE  i.REC_STATUS = 'REJECTED';

Verifying successful promotion requires the documented FK join:

SELECT c.ITEM_TYPE_ID, c.NAME
FROM   CZ.CZ_ITEM_TYPES c, CZ.CZ_IMP_ITEM_TYPE i
WHERE  c.ITEM_TYPE_ID = i.ITEM_TYPE_ID
AND    i.RUN_ID = :run_id;

Reporting use cases include import throughput by run, error-trend analysis by source application, and audit reconstruction using ORIG_SYS_REF and the user-defined columns.

Related Objects

  • CZ_ITEM_TYPES — the sole documented parent, joined on ITEM_TYPE_ID; the destination of successfully processed rows.
  • CZ_ITEM_TYPE_USAGES and related CZ item-type reference structures — downstream dependents of the promoted item type.
  • CZ_CONFIG_HDRS / CZ_CONFIG_REVISIONS — model headers referencing item types created from this staging flow.
  • FND_APPLICATION — resolves SRC_APPLICATION_ID to the source application name.
  • FND_USER — resolves CREATED_BY, LAST_UPDATED_BY, and CHECKOUT_USER to user identities.
  • Configurator import/validation APIs and concurrent programs — the loaders that consume CZ_IMP_ITEM_TYPE and populate CZ_ITEM_TYPES.