Search Results get_node

Overview

OWB_TREE is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It functions as a thin delegating wrapper layered over the MSC_OWB_TREE package, which is the substantive implementation of the Oracle Warehouse Builder (OWB) tree model used within the Advanced Supply Chain Planning (ASCP) and related MSC schema modules. The package supplies the hierarchical tree rendering and node-fetching logic that planning and pegging workbenches depend upon, most notably in the Planner Workbench interfaces where end-pegging relationships are displayed as expandable trees.

In the ETRM classification for release 12.2.2, OWB_TREE is registered as an OTHER-type API. Its individual entry points simply call their MSC_OWB_TREE counterparts, so the APPS package presents a stable, application-facing surface while MSC_OWB_TREE holds the business logic. The header comment dates the source to 2002, and the package has carried forward through 12.1.1 and 12.2.2 without a public signature change.

Key Procedures and Functions

• GETSTRUCTURE — Returns a populated node structure (nodeRec) for a given session and tree mode. This is the primary entry point for constructing the tree hierarchy that a form or workbench will render.
• GET_EXCP_COUNT — A function returning the count of exceptions associated with a given session and column number, used to flag nodes or columns that carry exception conditions.
• GET_CUST_HIER_STRING — The procedure the user searched for. It returns the customer hierarchy string representation. In planning and order-management contexts this string expresses the position of a customer or customer site within its hierarchical relationship chain, enabling the workbench to display the full customer hierarchy path for a selected node.
• GET_SOURCING_NODES — Populates a NodeData collection with sourcing nodes for a given end-pegging identifier, session, and expansion level, with an optional checkbox indicator. It drives the expansion of sourcing relationships in the tree.
• GET_LOOKUPS — Initializes or refreshes lookup values used by the tree presentation logic.

Additional procedures such as EXTEND, GET_NODE, and GET_NEXT_LEVEL_NODES appear in the source but are commented out in the documented body, confirming they are no longer routed through APPS.OWB_TREE.

Tables Accessed

The ETRM metadata does not enumerate direct table references through APPS synonyms. Because every documented entry point delegates to MSC_OWB_TREE, all persistent access is performed by the underlying MSC package against planning, pegging, and session-data structures in the MSC schema. APPS.OWB_TREE itself performs no direct DML.

Usage Notes

OWB_TREE is invoked indirectly by Planner Workbench and pegging-detail forms and by the concurrent/logic layers that build tree views for planning sessions. Custom code should call APPS.OWB_TREE rather than MSC_OWB_TREE to remain within the supported APPS API boundary. The package body is referenced by two other packages, indicating other APPS-level components depend on its delegating signatures. When tracing the customer hierarchy string in a diagnostic session, the practical flow is APPS.OWB_TREE.GET_CUST_HIER_STRING to MSC_OWB_TREE.GET_CUST_HIER_STRING, with the session identifier carrying the planning context.