Search Results connector_expl_type

Overview

APPS.CZ_REFS is a PL/SQL package belonging to the Oracle E-Business Suite Configurator (CZ) schema, part of the Oracle Configurator and model management infrastructure. Its primary business purpose is to manage the node structure of configured models — specifically references between model nodes, explanation and rule node types, and the hierarchical relationships that define how configurable items connect within a model. The package handles node deletion, movement, reference addition, structural changes, and various validation checks against model nodes and reference explanations.

The package defines several constants used to classify node and explanation behavior: OPTIONAL_EXPL_TYPE (1), MANDATORY_EXPL_TYPE (2), CONNECTOR_EXPL_TYPE (3), and MINMAX_EXPL_TYPE (4), along with rule constants NOT_MIN_MAX_RULE (0), MIN_RULE (1), and MAX_RULE (2). It also defines NULL_VALUE (-1), NO_FLAG ('0'), YES_FLAG ('1'), and an ERROR_CODE variable. These constants drive the logic used across the package's procedures when validating node types, min/max rules, and flag-based conditions.

Key Procedures and Functions

The package exposes 18 documented procedures and functions. Among them:

• ISNONVIRTUAL — Determines whether a given node is non-virtual, returning an output flag based on the node and model identifiers.
• CHECK_NODE — Performs validation of a node against model data, maximum/minimum values, a reference identifier, and explanation attributes, returning error and virtual-flag outputs.
• DELETE_NODE — Removes a node, supporting both physical and logical deletion (via the p_del_logically parameter), and returns an error code.
• MOVE_NODE — Repositions a node from one parent to another within a project, returning an error code.
• CHECK_REF_REQUEST — Evaluates a reference request between a root model, parent node, and target model, returning a status code.
• GET_NODE_UP and GET_NODE_DOWN — Traverse the model hierarchy upward and downward respectively, returning node, explanation, and level information.
• ADD_REFERENCE — Adds a reference between nodes.
• CHANGE_STRUCTURE — Modifies the structural arrangement of nodes in a model.
• SOLUTIONBASEDMODELCHECK — Validates models constructed on a solution basis.
• SET_TRACKABLE_CHILDREN_FLAG — Sets the flag governing whether child nodes are tracked.
• UPDATE_CHILD_NODES — Updates child node records.
• UPDATE_NODE_DEPTH — Recalculates and updates node depth values.
• RESET_MODEL_ARRAY — Resets the internal model array used during processing.
• POPULATE_COMPONENT_ID — Populates component identifier values.
• VALIDATE_INST_FLAG — Validates instantiation flags.
• CHECK_INST_RULE — Checks instantiation rules.
• POPULATE_PARENT_EXPL_TREE — Populates the parent explanation tree structure.

Tables Accessed

The package reads and writes several core Configurator tables through APPS synonyms. CZ_PS_NODES stores the primary model node structure operated upon by node-related procedures. CZ_MODEL_REF_EXPLS and CZ_MODEL_REF_EXPLS_S hold reference explanation data central to reference and node handling. CZ_EXPRESSION_NODES supports expression node logic. CZ_RULES underpins rule evaluation for min/max and instantiation checks. CZ_DES_CHART_CELLS, CZ_DES_CHART_COLUMNS, and CZ_DES_CHART_FEATURES relate to design chart presentation. CZ_COMBO_FEATURES, CZ_FUNC_COMP_SPECS, and CZ_RP_ENTRIES support feature and component specifications. CZ_DEVL_PROJECTS anchors project context. CZ_UI_ACTIONS, CZ_UI_DEFS, and CZ_UI_PAGES support user interface definition and action metadata.

Usage Notes

CZ_REFS is referenced by four other packages and is typically invoked indirectly through Oracle Configurator runtime and model maintenance flows rather than being called directly by end users. It is most commonly triggered by Configurator UI forms and model administration screens when users add, move, or delete nodes, modify reference explanations, or restructure models. Concurrent programs and custom extensions that manipulate model node hierarchies may also call these procedures. The DELETE_NODE procedure — the object of the user's "delete_node" search — is the documented entry point for removing nodes, with logical deletion supported as the default mode. The header comment indicates the package was last modified in 2009 and shipped at version 120.0.12010000.2, consistent with its role in the 12.1.1 and 12.2.2 code lines.