Search Results create_node

Overview

APPS.AHL_MC_NODE_PVT is a private (PVT) PL/SQL package within the Oracle Enterprise Asset Management / Complex Maintenance, Repair, and Overhaul (CMRO) product family of Oracle E-Business Suite. The AHL prefix identifies it as part of the Asset Health / Lifecycle application module, and the _PVT suffix classifies it as an internal helper API rather than a public, supported interface. The package supplies the core node-level maintenance routines that underpin the Maintenance Configuration (MC) data model, in which maintenance requirements are organized as a hierarchy of nodes. Each node represents a position, assembly point, or requirement within a maintenance configuration header, and may be linked to a parent node to form a tree.

In the context of the search term "create_node," the package is the primary internal component responsible for instantiation of maintenance configuration nodes. The specification declares a Node_Rec_Type record structure that encapsulates the full node payload: relationship identifiers, header linkage, position key and reference code, ATA code, position necessity code, unit of measure, quantity, parent relationship, item group, display order, effective dates, object version number, security group, and a standard DML operation flag. The companion Node_Tbl_Type table type permits bulk, set-based processing of node rows, and a Counter_Rule_Rec_Type record supports counter update rule data attached to nodes.

Key Procedures and Functions

The package exposes seven documented procedures, all centered on the lifecycle and processing of maintenance configuration nodes:

• CREATE_NODE — Creates a new node within a maintenance configuration, populating position, quantity, parent, item group, and attribute data and inserting the corresponding relationship records.
• MODIFY_NODE — Updates an existing node's attributes, including position details, quantity, parent linkage, and effective dates.
• DELETE_NODE — Removes a node and its dependent relationship and position key rows from the maintenance configuration.
• COPY_NODE — Duplicates an individual node, typically as the basis for instantiating a copied or templated maintenance structure.
• COPY_MC_NODES — Performs bulk copying of nodes, used when replicating an entire maintenance configuration or a significant subtree of it.
• PROCESS_DOCUMENTS — Handles document references associated with nodes, resolving and persisting document linkage for the node structure.
• ASSOCIATE_ITEM_GROUP — Establishes the association between a node and an item group, supporting the grouping of items required at a given position.

Tables Accessed

The package operates almost exclusively against the AHL maintenance configuration schema, with supplementary lookups:

• AHL_MC_RELATIONSHIPS and AHL_MC_RELATIONSHIPS_S — primary node/relationship storage, with the _S table retaining superseded or shadow rows for audit and date-tracked changes.
• AHL_MC_CONFIG_RELATIONS and AHL_MC_CONFIG_REL_S — configuration-level relationship records to which nodes belong.
• AHL_MC_REL_POS_KEY_S — position key sequencing and control for node placement.
• AHL_MC_HEADERS_B — parent maintenance configuration header, validated on node creation and modification.
• AHL_ITEM_GROUPS_B — item group definitions used by ASSOCIATE_ITEM_GROUP and node item-group references.
• AHL_CTR_UPDATE_RULES and AHL_CTR_UPDATE_RULES_S — counter update rules associated with nodes, surfaced through the Counter_Rule record type.
• MTL_UNITS_OF_MEASURE — validation of the node UOM code, which defaults to 'Ea'.
• DUAL and PLITBLM — utility references for single-row selection and PL/SQL table infrastructure.

Usage Notes

As a private package, AHL_MC_NODE_PVT is not intended to be called directly by customer code. It is invoked by public APIs, Oracle Forms user exits, and concurrent programs that manage maintenance configurations, and it is referenced by ten other packages in the CMRO module. Customizations requiring node creation or modification should route through the supported public wrapper APIs so that validation, object versioning, and date-tracked shadow rows remain consistent. The presence of the OBJECT_VERSION_NUMBER and operation flag fields confirms that the package participates in Oracle's optimistic locking and DML-tracking conventions; callers should therefore populate these attributes correctly to avoid concurrency conflicts.