Results for “msc_gantt_pkg”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.MSC_GANTT_PKG is the core PL/SQL package body behind the Oracle Advanced Supply Chain Planning (ASCP) Gantt chart interface in Oracle E-Business Suite 12.1.1 and 12.2.2. It assembles and manages the hierarchical node structures that the Gantt graphical scheduling views render, translating planner actions — firming, moving, and pegging — into updates against the MSC planning tables. The package is classified as OTHER in the ETRM repository and sits in the APPS schema. Its specification, MSC_GANTT_PKG, is the sole entry point; the body is not referenced by any other package, making it a leaf dependency invoked directly by the Gantt UI layer.

The body opens by declaring constants inherited from MSC_GANTT_UTILS: field, record, and resource separators; the format mask; and separator literals used to build the delimited data strings the applet consumes. It then defines view-type constants (DEMAND_VIEW, ORDER_VIEW, RES_ACTIVITIES_VIEW, RES_UNITS_VIEW, RES_HOURS_VIEW, SUPPLIER_VIEW), node-type constants (END_DEMAND_NODE, JOB_NODE, OP_NODE, RES_NODE, COPROD_NODE, RES_INST_NODE), and order/pegging view constants (PEG_ORDERS, PEG_DOWN, PEG_UP, PEG_UP_AND_DOWN, SHOW_CHILDREN, SHOW_PARENT, SHOW_PARENT_CHILDREN).

Key Procedures and Functions

The documented public interface spans twenty-six procedures and functions. The view builders — ORDERVIEW, RESOURCEVIEW, and SUPPLIERVIEW — construct the node hierarchies for the orders, resource, and supplier Gantt presentations respectively. ADDTOORDERSVIEW, ADDRESTORESVIEW, ADDSUPPTOSUPPVIEW, and ADDSIMUALTRESTOVIEW add nodes to an already materialized view, supporting incremental expansion without a full rebuild.

Edit operations are handled by FIRMUNFIRM, which toggles the firm status of a planned order, and by MOVENODE and MOVEANDFIRM, which reposition a node in time and optionally firm it in a single call. UPDATERESUNITSDIRECTLY and UPDATERESHOURSDIRECTLY write edited resource units and hours back to the resource requirement rows. SORTRESSUPPVIEW and RESCHARGES order and cost the resource/supplier view content. SEGMENTPEGGING drives the pegging traversal used to display up, down, or bidirectional pegging.

Supporting utilities include GETUSERPREF (retrieves Gantt display preferences for the current user), GETPLANINFO (returns plan attributes), ISPLANGANTTENABLED, ISPLANDSENABLED, and GETSIMURESOURCE.

Tables Accessed

Through APPS synonyms the package reads and writes the MSC planning schema. MSC_DEMANDS, MSC_SUPPLIES, and MSC_SUPPLIER_REQUIREMENTS supply the demand, supply, and supplier rows that populate the views. MSC_RESOURCE_REQUIREMENTS, MSC_RESOURCE_INSTANCE_REQS, and MSC_DEPT_RES_INSTANCES provide resource loading and instance detail. MSC_ROUTING_OPERATIONS and MSC_OPERATION_NETWORKS provide routing and network structure, while MSC_FULL_PEGGING supplies pegging relationships. MSC_SYSTEM_ITEMS, MSC_PLANS, and MSC_PLAN_ORGANIZATIONS supply item, plan, and organization context. MSC_FORM_QUERY, MSC_GANTT_QUERY, and MSC_GANTT_DTL_QUERY hold the saved query definitions that parameterize the views.

Usage Notes

MSC_GANTT_PKG is invoked by the ASCP Gantt chart forms and Java applet layer rather than by concurrent programs. When a planner opens a Gantt view, the form calls the appropriate view builder to assemble the node string; planner gestures in the chart generate calls to the add, move, firm, and update routines. The "from_node" reference users encounter corresponds to the source node identifier passed to pegging and traversal routines such as SEGMENTPEGGING and MOVENODE, which expand or relocate the hierarchy from a given origin node. Because the body is referenced by zero other packages, it should be treated as an application-internal API; custom code should prefer documented public interfaces and avoid direct dependence on the delimited-string constants, which are subject to change between patch levels.