Results for “fsk_itemtype_1_ext”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CZ_IMP_ITEM_MASTER is a staging table owned by the CZ schema in Oracle E-Business Suite Configurator (CZ). Its documented purpose is to hold data that is to be imported into, or rejected from, the production CZ_ITEM_MASTERS table. It therefore functions as an inbound interface or batch-load buffer that decouples external or bulk item data from the validated master tables used by the Configurator runtime.

In Oracle EBS 12.1.1 and 12.2.2, Configurator relies on a defined set of item master attributes (item type, base UOM, lead time, status, effective dating) to drive model and option class selection rules. CZ_IMP_ITEM_MASTER captures that same attribute set before validation, allowing import programs to process records in controlled batches via RUN_ID and to flag rejections through REC_STATUS and DISPOSITION. The 37 documented columns largely mirror the shape of the target master table, plus import-control columns.

The ETRM metadata lists only one foreign key, ITEM_TYPE_ID referencing CZ_ITEM_TYPES. The heuristic Data Vault classification derived from that FK structure is standalone — that is, the table does not participate in a classic hub/link/satellite chain. This classification should be treated as a modeling suggestion only, since a staging interface table typically has no integration-layer lineage by design.

Key Information Stored

The table combines a surrogate key, raw business attributes, import-control fields, and Configurator-specific extension columns. The most significant of the 37 documented columns are listed below.

• ITEM_ID — the primary identifier for the staged item record. In the EBS CZ design this is the closest candidate to a surrogate primary key on the staging table.
• ITEM_TYPE_ID — the only documented foreign key, referencing CZ_ITEM_TYPES. This is the principal business-key candidate for the item type dimension and the pivot for joins.
• ORIG_SYS_REF and REF_PART_NBR — the originating system reference and the referenced part number, providing traceability back to the source system of the imported record.
• DESC_TEXT — the item description carried into Configurator.
• PRIMARY_UOM_CODE — the base unit of measure for the item.
• LEAD_TIME and ITEM_STATUS — planning and lifecycle attributes used by Configurator rules.
• QUOTEABLE_FLAG and DECIMAL_QTY_FLAG — indicator flags controlling whether the item may be quoted and whether quantities permit decimals.
• RUN_ID, REC_NBR, REC_STATUS, DISPOSITION, DELETED_FLAG — import batch and outcome control fields. REC_STATUS and DISPOSITION distinguish successfully imported records from rejected ones.
• EFF_FROM, EFF_TO, EFF_MASK — effective-dating columns supporting date-range validity for imported items.
• USER_STR01–USER_STR04 and USER_NUM01–USER_NUM04 — generic user-defined extension attributes.
• SRC_TYPE_CODE and SRC_APPLICATION_ID — source classification and originating application identifier.
• SECURITY_MASK, CHECKOUT_USER, FSK_ITEMTYPE_1_1, FSK_ITEMTYPE_1_EXT — Configurator flexfield and security/checkout attributes.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS "Who" columns.

Common Use Cases and Queries

The primary scenario is monitoring and troubleshooting Configurator item imports. Administrators review staged rows by batch, inspect rejections, and re-drive failed records. A typical rejection query returns the batch, reference, and disposition fields:

• Identify rejected records for a batch: SELECT REC_NBR, ORIG_SYS_REF, REF_PART_NBR, REC_STATUS, DISPOSITION FROM CZ_IMP_ITEM_MASTER WHERE RUN_ID = :run_id AND REC_STATUS = 'ERROR'.
• Count outcomes per import run: SELECT RUN_ID, REC_STATUS, COUNT(*) FROM CZ_IMP_ITEM_MASTER GROUP BY RUN_ID, REC_STATUS.
• Resolve the item type for staged rows: SELECT i.ITEM_ID, i.REF_PART_NBR, t.ITEM_TYPE FROM CZ_IMP_ITEM_MASTER i, CZ_ITEM_TYPES t WHERE i.ITEM_TYPE_ID = t.ITEM_TYPE_ID.
• Audit recently loaded records: filter on LAST_UPDATE_DATE and CREATED_BY within a defined window.

Reporting use cases center on import quality: rejection rates by source (SRC_TYPE_CODE), aging of staged records, and reconciliation of staged counts against rows ultimately created in CZ_ITEM_MASTERS. Because the table is a staging object, it should generally be purged after successful processing rather than used as a long-term reporting source.

Related Objects

• CZ_ITEM_MASTERS — the target production table that receives validated rows from this staging table.
• CZ_ITEM_TYPES — referenced by CZ_IMP_ITEM_MASTER.ITEM_TYPE_ID; supplies the item type classification.
• CZ_ITEM_MASTER_ATTRS or equivalent attribute tables in the CZ schema, joined via ITEM_ID where attribute detail is required.
• The Configurator import concurrent programs and associated PL/SQL packages that populate and validate CZ_IMP_ITEM_MASTER and publish results to CZ_ITEM_MASTERS.
• Concurrent request and run-history tables, correlating RUN_ID to a specific import program submission.

All joins should be grounded on the documented FK (ITEM_TYPE_ID) and the identifier column ITEM_ID; the absence of additional documented FKs indicates that referential enforcement for imported item data is applied during validation rather than by database constraint.