Search Results items_tree




Overview
Explore in AI Chat

Overview

MSC_OWB_TREE is an internal Oracle Advanced Supply Chain Planning (ASCP) package body owned by the APPS schema. It supports the graphical tree representation used by Oracle Web Builder (OWB) based planning user interfaces, most notably the horizontal and vertical pegging trees that show how a demand element is connected to its upstream supplies. The package is a structural and presentation utility: it assembles node sets, assigns depth, state, label and icon attributes to each node, and returns those collections to the calling layer so that a tree can be rendered and expanded interactively. It is not a business transaction API. Its scope is the querying, shaping and expansion of pegging hierarchy data for display, including the calculation of exception counts and the formatting of customer hierarchy strings that appear on tree nodes. In Oracle EBS 12.1.1 and 12.2.2 the package remains a supporting component of the MSC schema family and is referenced by other planning packages rather than being invoked directly by end users.

Key Procedures and Functions

The documented program units fall into two groups: entry points that build or summarise trees, and utilities that supply descriptive attributes for individual nodes.

  • GETSTRUCTURE — The principal builder. It receives a session identifier and a mode indicator and returns the populated node collection that constitutes the tree. The mode value selects the source of the hierarchy, such as planning results viewed from the order management side versus supply chain ATP processing, and controls how many nodes are pre-created through the internal extend routine.
  • GET_EXCP_COUNT — Returns the count of exceptions associated with the tree or its nodes, allowing the UI to flag items requiring planner attention.
  • GET_CUST_HIER_STRING — Produces the formatted customer hierarchy string used as a node label, resolving the customer grouping into the concatenated display form expected by the tree viewer.
  • GET_DEMAND_CLASS — Determines and returns the demand classification for a tree element, which drives labelling and colour or icon selection.
  • GET_SOURCING_NODES — Retrieves the sourcing-related node set used when the tree is expanded along supply or sourcing relationships.
  • GET_LOOKUPS — Resolves lookup codes to their display meanings so that node attributes are presented in user-readable form.

Internally, the body also declares helpers such as get_node, get_next_level_nodes and get_supply_only_nodes, plus overloaded extend procedures that grow the parallel arrays (tree_type, parent_node_type, state, depth, label, icon and data) comprising an owb_tree node collection. Debug tracing is controlled by the MSC_ATP_DEBUG profile option.

Tables Accessed

The package works against a small set of planning data structures, reached through APPS synonyms.

  • MRP_ATP_DETAILS_TEMP — The temporary planning table holding ATP detail rows that supply the pegging and availability information from which tree nodes and exception counts are derived. It is read to populate and expand the tree.
  • PLITBLM — The standard EBS temporary index or line table used by the MSC layer for intermediate result storage and lookup during processing.

Because these are transient planning structures, the package neither owns nor persists master data; it consumes session-scoped results and shapes them for presentation.

Usage Notes

MSC_OWB_TREE is invoked indirectly. The ASCP planning workbench and related pegging and exception screens call it through the planning UI stack to render expandable trees, and two other MSC packages reference it as part of the same framework. Customisations should treat it as a private implementation detail: rather than calling GETSTRUCTURE directly, developers should use the supported planning views and public APIs, since the node collection types and internal helpers are not part of a published interface and may change between patch levels. When diagnosing tree display problems, the MSC_ATP_DEBUG profile option can be set to trace execution, and the contents of MRP_ATP_DETAILS_TEMP at the time of the request should be verified, as missing or stale planning data is the most common cause of an incomplete or empty tree.