Search Results item_org




Overview
Explore in AI Chat

Overview

MSC_UI_PEG_UTIL is a utility package body owned by APPS within the Advanced Supply Chain Planning (ASCP) schema of Oracle E-Business Suite. The package is classified as a UTIL (utility) module rather than a business API, and in both EBS 12.1.1 and 12.2.2 its purpose is to supply the pegging engine of the Planner Workbench user interface with structured result sets. Pegging answers the core planning question of which supply satisfies which demand (and vice versa), and the Planner Workbench renders that relationship as an expandable tree. MSC_UI_PEG_UTIL encapsulates the SQL and PL/SQL logic that walks those trees and returns the rows the UI expects.

The package is not intended for direct customer invocation. It is an internal companion to the pegging UI, exposing weakly typed result tables and record types (for example the peg node record table referenced in the declaration section) that the calling Java or Forms layer consumes. Because it references APPS synonyms only, it remains insulated from the underlying 12.1.1 versus 12.2.2 schema changes.

Key Procedures and Functions

  • GET_DISPOSITION_ID — Resolves the disposition identifier and origination type for a given demand, using the demand, plan, organization and source instance as the lookup key against MSC_DEMANDS. The extracted excerpt shows this routine implemented as a simple single-row cursor fetch with a re-raise exception handler.
  • GET_SUPTREE_SUP_VALUES — Returns the supply-side branch of a pegging tree for a given demand and plan, computing a combined "item/org" display label from MSC_SYSTEM_ITEMS and the organization name, along with supply quantity, schedule date, order type and pegged quantity. It supports demand pegging (peg up) and an item description display option.
  • GET_SUPTREE_DEM_VALUES — The demand-side counterpart, returning the demand nodes that hang beneath a supply in the pegging hierarchy.
  • GET_SUPTREE_DEM_VALUES_REP — A reporting variant of the demand-tree retrieval, used where repeated or report-style expansion of the tree is required.
  • GET_DEMTREE_DEM_VALUES — Returns demand-tree values from the perspective of a demand node, supporting top-down navigation.
  • GET_LABEL_AND_NODEVALUE — Produces the display label and node value pair used by the UI tree control for a given pegging record.

All six routines are read-only utilities: none creates, updates or deletes planning data.

Tables Accessed

The package reads from MSC_DEMANDS, MSC_SUPPLIES and MSC_FULL_PEGGING, which hold the demand, supply and precomputed pegging relationships respectively — these are the primary sources for tree expansion. MSC_SYSTEM_ITEMS supplies item name, description and organization context for the "item/org" label. MSC_BOM_COMPONENTS, MSC_ROUTING_OPERATIONS, MSC_ROUTINGS, MSC_OPERATION_COMPONENTS and MSC_RESOURCE_REQUIREMENTS are consulted to drill into component and routing-level pegging, allowing the UI to expand a planned order down to its material and resource requirements.

Usage Notes

MSC_UI_PEG_UTIL is invoked exclusively by the ASCP Planner Workbench pegging UI in response to user actions such as expanding a peg node, changing the pegging direction, or switching the item description display option. It is not registered as a concurrent program and, per the ETRM metadata, is referenced by zero other PL/SQL packages, confirming its status as a leaf-level UI service. Custom code should not call these routines directly, as their out parameters rely on package-defined record types that are subject to change between patch levels; the supported integration surface for pegging data remains the MSC schema views and public ASCP APIs.