Results for “cz_imp_ps_nodes”

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

Overview

CZ_IMP_PS_NODES is a staging and interface table within the Oracle Configurator (CZ) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. Its documented purpose is to hold data that is to be imported into — or that has been rejected by — the production node structure table CZ_PS_NODES. The table is owned by the CZ schema and is classified as VALID in the ETRM repository.

In the Configurator data model, a "PS node" represents a node in a configuration model or product structure tree. The import table serves as the landing zone for bulk loads of model structure definitions, whether originating from external systems, data migration scripts, or the Configurator import utilities. Rows proceed from CZ_IMP_PS_NODES into CZ_PS_NODES upon successful validation; rows that fail validation remain in the staging table with a rejection status recorded. The REC_STATUS and DISPOSITION columns exist specifically to track this lifecycle.

From a Data Vault modeling perspective, the heuristic classification supplied in the metadata is standalone. This reflects the fact that the table is a transient interface object rather than a durable entity with its own business identity. A modeler would not typically treat it as a hub, link, or satellite; it is better understood as a staging construct whose natural home is a load or error-handling layer outside the core Data Vault.

Key Information Stored

The table is physically wide, with 99 documented columns in the 12.2.2 schema. The most operationally significant columns are the following.

• PS_NODE_ID — the surrogate primary key inherited from the target table CZ_PS_NODES; it is also a foreign key back to that table, so it is not a freely assignable business key here.
• DEVL_PROJECT_ID — identifies the development project (model) that owns the node, referencing CZ_DEVL_PROJECTS.
• NAME — the node name, one of the principal business identifiers for a configuration node.
• PS_NODE_TYPE, FEATURE_TYPE, ITEM_TYPE_BACKPTR — control the structural role of the node in the model tree.
• PARENT_ID — self-referencing pointer that establishes the parent/child hierarchy within the node tree.
• MINIMUM, MAXIMUM, MINIMUM_SELECTED, MAXIMUM_SELECTED, MAX_QTY_PER_OPTION — quantity and selection constraint thresholds governing configurable options.
• MUTUALLY_EXCLUSIVE_OPTIONS, OPTIONAL, BOM_REQUIRED, USER_INPUT_REQUIRED_FLAG, MULTI_CONFIG_FLAG, SYSTEM_NODE_FLAG — configuration behavior flags.
• INTL_TEXT_ID, SUB_CONS_ID, EFFECTIVITY_SET_ID — foreign keys to CZ_INTL_TEXTS, CZ_SUB_CON_SETS, and CZ_EFFECTIVITY_SETS respectively, supplying descriptive text, substitution constraints, and effectivity definition.
• REC_STATUS and DISPOSITION — the interface control columns indicating whether the row is accepted, pending, or rejected.
• RUN_ID — groups rows belonging to a single import or concurrent program run, enabling per-run reporting and rollback.
• ORGANIZATION_ID and ITEM_ID — the inventory context for the node where it corresponds to an item.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• DELETED_FLAG, UI_OMIT, UI_SECTION, TREE_SEQ, ORDER_SEQ_FLAG — presentation and ordering attributes.

The many FSK_* columns (for example FSK_INTLTEXT_1_1, FSK_PSNODE_3_1, FSK_DEVLPROJECT_5_1) are foreign-key surrogate/extension pairs generated by the Configurator's internal referential machinery; they mirror the relationships carried by the corresponding foreign keys.

Common Use Cases and Queries

The dominant scenario is diagnosing failed or partially applied model imports. A typical query retrieves all rejected rows for a given run:

SELECT ps_node_id, name, devl_project_id, rec_status, disposition
FROM   cz.cz_imp_ps_nodes
WHERE  run_id = :run_id
AND    rec_status NOT IN ('ACCEPTED', 'SUCCESS');

A second pattern reconciles staged rows against their target to confirm load completion:

SELECT i.ps_node_id, i.name, i.rec_status, n.ps_node_id AS target_id
FROM   cz.cz_imp_ps_nodes i
LEFT   JOIN cz.cz_ps_nodes n ON n.ps_node_id = i.ps_node_id
WHERE  i.run_id = :run_id;

Reporting use cases include summarizing rejection counts per development project, trending import volumes by RUN_ID over time, and auditing which user (CREATED_BY) submitted a given load. Because the table carries ORGANIZATION_ID and ITEM_ID, it can also be joined to inventory item master data to validate whether staged nodes resolve to legitimate items before promotion.

Related Objects

The following objects are most significant, based on the documented foreign-key relationships:

• CZ_PS_NODES — the production target, joined on PS_NODE_ID. Every staged row ultimately corresponds to one target node.
• CZ_DEVL_PROJECTS — joined on DEVL_PROJECT_ID; identifies the configuration model under development.
• CZ_INTL_TEXTS — joined on INTL_TEXT_ID; supplies internationalized descriptive text for the node.
• CZ_SUB_CON_SETS — joined on SUB_CONS_ID; defines substitution constraint sets governing the node.
• CZ_EFFECTIVITY_SETS — joined on EFFECTIVITY_SET_ID; provides date and usage effectivity for the node, complemented by the table's own EFF_FROM, EFF_TO, EFF_MASK, EFFECTIVE_FROM, EFFECTIVE_UNTIL, and EFFECTIVE_USAGE_MASK columns.
• CZ_IMP_BOM_COMPONENTS / Configurator import utilities — sibling staging objects and concurrent programs that populate and consume the import tables.