Results for “explosion_type”

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

Overview

CZ_XFR_PROJECT_BILLS is a Configurator (CZ) module table within the Oracle E-Business Suite environment, documented as valid in both 12.1.1 and 12.2.2. Its stated purpose is the project bills import control table. It governs the transfer and staging of project bill-of-material explosion data between source and target environments, using the Configurator Transfer (CZ_XFR) framework. The table therefore sits at the intersection of project definitions, cross-instance transfer run information, and item bill explosion data.

From a modeling perspective, the heuristic Data Vault classification derived from the foreign-key structure is link. This classification is offered as a suggestion only: the table functions primarily as an associative structure that joins a project node (MODEL_PS_NODE_ID) to a transfer run (LAST_IMPORT_RUN_ID) and to a source server (SOURCE_SERVER), while also carrying descriptive attributes that qualify each import event.

Key Information Stored

The table is documented with fifteen physical columns. The single-column primary key, enforced through CZ_XFR_PROJ_BILLS_PK, is MODEL_PS_NODE_ID. This column is the surrogate identifier and simultaneously serves as the unique business-key candidate, and it is the column that anchors the foreign key to CZ_DEVL_PROJECTS.

• MODEL_PS_NODE_ID — the primary key and business-key candidate; identifies the project structure node whose bills are being imported.
• ORGANIZATION_ID — the inventory organization context for the bill data.
• COMPONENT_ITEM_ID — the component item referenced by the imported bill line.
• TOP_ITEM_ID — the top-level assembly item under which the component is exploded.
• LAST_IMPORT_RUN_ID — foreign key to CZ_XFR_RUN_INFOS, identifying the transfer run that last processed the record.
• LAST_IMPORT_DATE — timestamp of the most recent import.
• SOURCE_SERVER — foreign key to CZ_SERVERS, identifying the originating instance of the bill data.
• SOURCE_BILL_DELETED — flag indicating the source bill was removed, driving deletion propagation.
• DELETED_FLAG — internal deletion indicator for the staging row.
• EXPLOSION_TYPE — the bill explosion mode applied during import.
• BILL_REVISION_DATE, EFF_FROM, EFF_TO — effective-dating and revision columns that control which bill version is in scope.
• COPY_ADDL_CHILD_MODELS — controls whether additional child models are copied during the transfer.
• DESCRIPTION — descriptive text associated with the imported record.

These columns collectively distinguish the surrogate key from the descriptive, effectivity, and audit attributes that make the table import-manageable rather than a pure lookup.

Common Use Cases and Queries

Typical usage centers on verifying what bills were transferred and whether the transfer completed successfully. A common query joins the table to its run information to audit recent imports:

• Listing records for a specific run: SELECT pb.MODEL_PS_NODE_ID, pb.TOP_ITEM_ID, pb.COMPONENT_ITEM_ID FROM CZ_XFR_PROJECT_BILLS pb WHERE pb.LAST_IMPORT_RUN_ID = :run_id;
• Identifying source systems: SELECT SOURCE_SERVER, COUNT(*) FROM CZ_XFR_PROJECT_BILLS GROUP BY SOURCE_SERVER;
• Detecting deletions requiring reconciliation: SELECT MODEL_PS_NODE_ID FROM CZ_XFR_PROJECT_BILLS WHERE SOURCE_BILL_DELETED = 'Y' AND DELETED_FLAG = 'N';
• Effective-dating checks using EFF_FROM and EFF_TO to confirm the import captured the intended revision window.

Reporting use cases include transfer reconciliation between instances, post-import validation of bill completeness, and operational dashboards tracking LAST_IMPORT_DATE per server.

Related Objects

• CZ_DEVL_PROJECTS — joined on CZ_XFR_PROJECT_BILLS.MODEL_PS_NODE_ID; supplies project structure node context.
• CZ_XFR_RUN_INFOS — joined on LAST_IMPORT_RUN_ID; provides transfer run metadata and status.
• CZ_SERVERS — joined on SOURCE_SERVER; identifies the originating instance.
• CZ_XFR_PROJ_BILLS_PK — the unique index enforcing MODEL_PS_NODE_ID uniqueness.
• Other CZ_XFR tables (such as transfer control and staging tables) that share the CZ_XFR naming family and participate in the same Configurator Transfer workflow.