Results for “fsk_property_2_ext”

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

Overview

CZ_IMP_ITEM_TYPE_PROPERTY is a staging and interface table within the Oracle Configurator (CZ) module. Its documented purpose is to hold data that is either imported into, or rejected from, the production table CZ_ITEM_TYPE_PROPERTIES. It therefore serves as an inbound staging buffer for the mapping between configurator item types and their associated properties. Records that pass validation are promoted to the base table; records that fail remain in the interface table with a non-successful status for review and correction.

The table is owned by the CZ schema and is marked VALID in the ETRM 12.2.2 metadata, carrying 31 documented columns. From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is standalone. This suggests that, rather than acting as a hub, link, or satellite within a conformed Data Vault model, the table functions as a self-contained operational staging entity. In practical terms it should be modeled as a transient or audit-oriented staging artifact whose keys mirror those of the target base table rather than as a durable warehouse dimension or fact.

Key Information Stored

The 31-column footprint includes a set of business and control columns. The most significant are:

• ITEM_TYPE_ID — foreign key to CZ_ITEM_TYPES, identifying the item type being configured. This is the anchoring business key for each staging row.
• PROPERTY_ID — identifies the property associated with the item type; together with ITEM_TYPE_ID it drives uniqueness of an item-type-to-property mapping.
• REC_NBR and RUN_ID — record sequence number and batch/run identifier, used to group rows by import execution.
• REC_STATUS and DISPOSITION — the outcome flags indicating whether a row was accepted, rejected, or pending disposition.
• DELETED_FLAG, EFF_FROM, EFF_TO, and EFF_MASK — effective-dating and soft-delete controls that govern the validity window of the mapping.
• USER_STR01–USER_STR04 and USER_NUM01–USER_NUM04 — eight generic user-defined attributes for extensibility without schema change.
• SRC_APPLICATION_ID and ORIG_SYS_REF — identify the source application and originating system reference for traceability.
• FSK_ITEMTYPE_1_1, FSK_ITEMTYPE_1_EXT, FSK_PROPERTY_2_1, and FSK_PROPERTY_2_EXT — foreign surrogate key columns supporting the item type and property relationships.
• Standard WHO columns — CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CHECKOUT_USER, and SECURITY_MASK.

No single surrogate primary key column is documented for this staging table; the natural business key is the combination of ITEM_TYPE_ID and PROPERTY_ID, qualified by RUN_ID and REC_NBR for batch lineage.

Common Use Cases and Queries

The table is primarily consumed by import/validation programs and by support analysts diagnosing failed loads. Typical reporting patterns include:

• Listing rejected rows for a specific load run: SELECT * FROM CZ_IMP_ITEM_TYPE_PROPERTY WHERE RUN_ID = :run_id AND REC_STATUS <> 'SUCCESS';
• Reconciling staged versus production mappings by joining to CZ_ITEM_TYPE_PROPERTIES on ITEM_TYPE_ID and PROPERTY_ID.
• Auditing source lineage: SELECT SRC_APPLICATION_ID, ORIG_SYS_REF, COUNT(*) FROM CZ_IMP_ITEM_TYPE_PROPERTY GROUP BY SRC_APPLICATION_ID, ORIG_SYS_REF;
• Reviewing pending or soft-deleted rows using DELETED_FLAG and the EFF_FROM/EFF_TO window.

Related Objects

• CZ_ITEM_TYPES — referenced via ITEM_TYPE_ID; the parent item type definition.
• CZ_ITEM_TYPE_PROPERTIES — the production target table receiving promoted rows.
• CZ_PROPERTIES — referenced through PROPERTY_ID; defines configurator properties.
• CZ_IMP_ITEM_TYPE_* — sibling interface tables sharing the same import framework and RUN_ID convention.
• CZ_IMP_RUNS (or equivalent run-log object) — reconciles RUN_ID against load execution history.