Search Results move_node

Overview

BOM_RTG_APPLET_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the "OTHER" API category. It supports the Oracle Bills of Material routing functionality, specifically the graphical operation network maintained through the Routing/Network (Routing Applet) interface. The package encapsulates the server-side logic required to manipulate the operation network graph that underlies a routing: the nodes representing operations and the links representing precedence/transition relationships between them.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the definer, and it is designed to be invoked from an applet-based client (as the name implies) as well as from any PL/SQL caller passing the requisite identifiers and audit columns. Its four procedures collectively cover the lifecycle operations performed when a user edits a routing network: attaching operations to events, creating or modifying links, validating links before they are committed, and repositioning a node on the graphical canvas.

Key Procedures and Functions

• ASSOCIATE_EVENT — Establishes an association between an operation and an event context. It accepts an event operation sequence identifier, an operation type discriminator (procedure or "lnop" — line operation), and the target parent operation sequence identifier, along with standard audit columns. It returns a status code and error message through OUT parameters.
• ALTER_LINK — Creates, updates, or deletes a transition link between two operations. It receives the source and target operation sequence identifiers, the transition type, an optional planning percentage, a transaction type indicating insert/update/delete, the full set of audit and descriptive flexfield attribute columns, and OUT parameters for return status and error messaging.
• VALIDATE_LINK — Performs validation of a proposed link before it is persisted. It takes the from/to operation sequence identifiers, transition type, planning percentage, and transaction type, and returns a success/failure indicator and error message. This allows the calling interface to reject invalid precedence relationships prior to database modification.
• MOVE_NODE — Updates the graphical coordinates of an operation node within the routing network. It accepts the operation sequence identifier, the new X and Y coordinates, and audit information, and returns a status code and error message. This procedure supports the drag-and-drop repositioning behavior of the routing applet.

Tables Accessed

The package operates against two core Oracle Bills of Material tables, accessed through APPS synonyms:

• BOM_OPERATION_SEQUENCES — Stores the routing operations (nodes) belonging to a manufacturing routing, including sequence identifiers and operation attributes. Rows here are the targets of ASSOCIATE_EVENT and MOVE_NODE updates, and the endpoints referenced by link operations.
• BOM_OPERATION_NETWORKS — Stores the network links (transitions) that connect operations in a routing network, capturing from/to relationships, transition types, and planning percentages. It is the primary table written by ALTER_LINK and read/checked by VALIDATE_LINK.

Usage Notes

BOM_RTG_APPLET_PKG is typically invoked from the Oracle EBS Bills of Material routing window's network/applet interface, where user actions on the graphical routing canvas trigger calls to Move_Node, Alter_Link, Associate_Event, and Validate_Link. The OUT return codes ("S" for success, "F" for failure) and error message parameters allow the client to present validation feedback before commits are finalized.

Because the package is classified as "OTHER" rather than a formally supported public API, and because ETRM indicates it is referenced by zero other packages, it should be treated as an internal implementation object. Custom code may call these procedures to automate routing network maintenance, but doing so carries upgrade risk in 12.1.1 and 12.2.2, and callers must supply all audit columns (created_by, last_updated_by, last_update_login, dates) themselves. Direct DML against BOM_OPERATION_SEQUENCES and BOM_OPERATION_NETWORKS is discouraged in favor of the validated procedural path.