Search Results pc_node_rec

Overview

APPS.AHL_PC_NODE_PVT is a private PL/SQL package within the Oracle E-Business Suite Product Classification (AHL) module. Product Classification provides the hierarchical catalog that organizes products into reusable class nodes, supporting attributes, associations, and documentation linkages across the enterprise. The package is declared with AUTHID CURRENT_USER and exposes the private procedural layer that implements node-level data manipulation for the Product Classification node entity.

The package name carries the "_PVT" suffix, indicating that its procedures form the internal implementation tier behind the public API surface, typically APPS.AHL_PC_NODE_PUB. The public layer validates and orchestrates; the private layer performs the actual inserts, updates, and deletes against the underlying base tables. The package depends on the standard EBS API framework, using FND_GLOBAL.LOGIN_ID to resolve the current user and FND_API constants for commit and validation control. Package-level constants define the DML mode codes (create, update, delete, copy, assign, link) and the node type discriminators for unit versus part classification, reflecting the breadth of operations the Product Classification model supports.

Key Procedures and Functions

The documented interface exposes three procedures:

• CREATE_NODE — Marked as private, this procedure creates a new Product Classification node. It accepts the standard API framework parameters (API version, initialization of the message list, commit flag, and validation level) together with the node record itself, and returns the standard return status, message count, and message data. The node record is passed using the public API record type, AHL_PC_NODE_PUB.PC_NODE_REC, passed IN OUT NOCOPY, allowing the procedure to return generated identifiers and derived values to the caller.
• UPDATE_NODE — Updates an existing Product Classification node. It follows the same standard parameter conventions as CREATE_NODE and is used when node attributes, associations, or hierarchy placement must be changed.
• DELETE_NODES — Performs deletion of Product Classification nodes. This is the procedure most commonly reached when users or administrators remove classification nodes from the hierarchy. Because it is the private implementation of the delete operation, callers typically invoke it indirectly through the public API wrapper, which applies validation and referential checks before the private layer physically removes the node rows.

Tables Accessed

The package reads and writes a set of AHL Product Classification tables through APPS synonyms:

• AHL_PC_NODES_B and AHL_PC_NODES_B_S — the base and sequence tables storing node records; these are the primary targets of CREATE_NODE, UPDATE_NODE, and DELETE_NODES.
• AHL_PC_HEADERS_B and AHL_PC_ASSOCIATIONS — header and association tables that define node context and relationships; delete and update logic must respect associations tied to a node.
• AHL_DOC_TITLE_ASSOS_B and AHL_DOC_TITLE_ASSOS_TL — documentation title associations, base and translated, linking nodes to documentation.
• AHL_MEL_CDL_HEADERS and AHL_MR_EFFECTIVITIES — model/effectivity structures used when a node participates in model-based classification.
• DUAL and PLITBLM — utility references for scalar evaluation and PL/SQL table handling.

Usage Notes

AHL_PC_NODE_PVT is not intended for direct invocation by end users or custom code. It is called by the public Product Classification API package, which in turn is invoked from the Product Classification setup forms, concurrent programs that import or maintain classification hierarchies, and any custom integration that manipulates classification nodes. The documented metadata shows the package is referenced by two other packages, consistent with its role as a shared private implementation layer.

Developers extending or troubleshooting Product Classification behavior, particularly node removal, should trace the delete path from the public API into DELETE_NODES. Because the private layer performs physical DML without the validation and message-stack handling of the public layer, custom code should always call the public API rather than this package directly. Any changes to node structures must also account for the association and documentation tables referenced above, as these establish the referential context that governs safe deletion.