Search Results gme_gantt_pkg




Overview
Explore in AI Chat

Overview

GME_GANTT_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the Process Manufacturing (GME/GMD) module family. It provides the server-side data retrieval layer for the Gantt chart visualization used within Oracle Process Manufacturing (OPM) scheduling and batch execution functionality. The Gantt chart presents a graphical, time-oriented view of batch operations, activities, and resource assignments, allowing production planners and shop-floor supervisors to review the sequencing and duration of manufacturing steps across the shop calendar.

In Oracle EBS 12.1.1 and 12.2.2, the package functions as a data access API rather than a business transaction processor. Its role is to query batch headers, batch steps, step resources, operations, activities, and operation classes, then return that data in a structured form suitable for rendering in the client-side Gantt component. It also handles shop calendar retrieval so that working and non-working days can be correctly represented on the timeline. All objects are resolved through APPS synonyms, and the package operates in a VALID state in the documented environment.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions within GME_GANTT_PKG. Each supports the assembly of Gantt chart data for a given batch or set of batches.

  • INIT_SESSION — Establishes the package session state and initializes internal cursors and variables prior to data retrieval.
  • GET_OPERATIONS — Retrieves operation definitions, typically keyed to the routing or recipe associated with the batch being displayed.
  • GET_ACTIVITIES — Returns activity records associated with operations, forming the discrete work elements shown on the chart.
  • GET_RESOURCES — Fetches resource assignments for batch steps, enabling resource loading to be visualized across the timeline.
  • GET_BATCH_PROPERTIES — Returns header-level attributes of the batch, such as status, quantity, and identification data.
  • CLOSE_CURSORS — Releases open cursors to free session resources once the Gantt data set has been consumed.
  • GET_NEXT_BATCH_SET — Provides paginated or iterative retrieval of batch records when more than one batch is displayed.
  • FETCH_SHOP_CALENDAR — Retrieves the applicable shop calendar definition used to align the chart's time axis.
  • FETCH_WORK_NON_WORK_DAYS — Returns working and non-working day indicators so the Gantt timeline can shade non-productive periods.
  • VALIDATE_RESCHEDULE_EVENT — Validates whether a proposed reschedule action is permissible before it is applied.
  • DATE_TO_CLIENTDT — Converts server-side date values into the client date representation expected by the Gantt rendering layer.

Tables Accessed

The package reads from a defined set of OPM and common tables through APPS synonyms. Batch execution data is sourced from GME_BATCH_HEADER, GME_BATCH_STEPS, and GME_BATCH_STEP_RESOURCES. Process definition data is drawn from GMD_OPERATIONS_B, GMD_ACTIVITIES_B, GMD_OPERATION_CLASS_B, and their base tables GMD_OPERATIONS, GMD_ACTIVITIES, GMD_OPERATION_CLASS, and GMD_RECIPES. Item descriptions are resolved from MTL_SYSTEM_ITEMS_KFV. Resource master information is obtained from CR_RSRC_MST, while CM_ALYS_MST and FM_FORM_MST support resource and formula context. Calendar data is retrieved from BOM_CALENDARS.

Usage Notes

GME_GANTT_PKG is typically invoked by the OPM Gantt chart user interface and related scheduling forms to populate the display before rendering. Because no other packages reference it, it is not a shared utility dependency; callers interact with it directly. Custom extensions requiring Gantt-style batch or resource data may call the documented procedures, observing the conventional sequence of INIT_SESSION, retrieval calls, and CLOSE_CURSORS. The VALIDATE_RESCHEDULE_EVENT routine should be invoked prior to committing drag-and-drop rescheduling actions. All calls run under the APPS schema and inherit standard EBS security and MOAC behavior.