Search Results gmd_operation_class

Overview

GME_GANTT_PKG is a PL/SQL package body owned by the APPS schema that provides the data-access and scheduling logic underpinning the Oracle EBS Process Manufacturing Gantt chart. It serves as the server-side engine for displaying and rescheduling process manufacturing batches in a graphical timeline, resolving the relationships between recipes, routings, operations, activities, resources, and shop calendars into a form consumable by the Gantt user interface. The package is classified as an OTHER API within the ETRM 12.2.2 repository and is recorded with VALID status.

The package assembles the hierarchical structure of a batch — batch header, batch steps, step activities, and step resources — and correlates these with the master process definitions (operations, activities, operation classes, and routings) as well as the plant calendar, so that the Gantt display reflects both planned and actual timing. It also supports interactive rescheduling by validating reschedule events submitted from the client. The package depends on the Oracle Application Object Library utilities (FND_DATE, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, FND_TIMEZONES_PVT, FND_TIMEZONES_PVT), DBMS_SQL, PLITBLM, and GME_DEBUG, and it references a global temporary table, GME_GANTT_GTMP, for staging result sets.

Key Procedures and Functions

Eleven documented procedures and functions constitute the public interface of GME_GANTT_PKG:

• INIT_SESSION — Initializes the package session state, establishing the context (profile values, timezone, and working storage) required by the subsequent Gantt queries.
• GET_OPERATIONS — Retrieves the operations associated with the batches or routings being charted, drawing on the operation and operation-class master data.
• GET_ACTIVITIES — Returns the activity-level detail that sits beneath each operation, providing the granularity displayed within the Gantt bars.
• GET_RESOURCES — Fetches the resources assigned to batch steps and activities, supporting resource loading and utilization display.
• GET_BATCH_PROPERTIES — Supplies the header-level attributes of the batches, such as identifiers, statuses, and scheduling attributes.
• CLOSE_CURSORS — Releases any open cursors and temporary structures held by the session, preventing cursor leakage between invocations.
• GET_NEXT_BATCH_SET — Implements the pagination mechanism that retrieves the next block of batches for display, allowing the Gantt to render large result sets incrementally.
• FETCH_SHOP_CALENDAR — Reads the applicable manufacturing calendar for the organization so that working and non-working time can be represented accurately.
• FETCH_WORK_NON_WORK_DAYS — Distinguishes working days from non-working days within the calendar, enabling shaded or suppressed rendering of non-productive periods.
• VALIDATE_RESCHEDULE_EVENT — Validates a user-initiated reschedule action (for example, a drag-and-drop or date change in the Gantt) before it is committed, enforcing calendar and scheduling constraints.
• DATE_TO_CLIENTDT — Converts an Oracle date into the client-side date representation, respecting timezone and formatting conventions for transmission to the UI.

Tables Accessed

The package reads process manufacturing transactional and master data through APPS synonyms. Batch data is drawn from GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_ACTIVITIES, GME_BATCH_STEP_RESOURCES, and GME_MATERIAL_DETAILS. Process definitions are sourced from GMD_RECIPES, GMD_RECIPE_VALIDITY_RULES, GMD_ROUTINGS, GMD_OPERATIONS and its _B base table, GMD_ACTIVITIES and its _B table, and GMD_OPERATION_CLASS and its _B table — the operation-class tables being central to grouping operations by the classification the user searched for. Resource, calendar, and organization data come from CR_RSRC_MST, CM_ALYS_MST, FM_FORM_MST, BOM_CALENDARS, MTL_PARAMETERS, and MTL_SYSTEM_ITEMS_KFV. Results are staged in the GME_GANTT_GTMP global temporary table. GMP_CALENDAR_API is used for calendar calculations.

Usage Notes

GME_GANTT_PKG is invoked from the Process Manufacturing Gantt chart user interface, typically as part of the batch scheduling and rescheduling workflow. The calling form drives session initialization, then iterates the GET_* procedures to populate the chart, using GET_NEXT_BATCH_SET for paging and the calendar fetches to render working time. Reschedule interactions from the client pass through VALIDATE_RESCHEDULE_EVENT before changes are applied. Because it is a package body with no dependent objects referencing it, it is not intended as a general-purpose integration API; custom code should treat it as an internal implementation unit. Sessions should always conclude with CLOSE_CURSORS to avoid resource leakage, and GME_DEBUG can be enabled to trace execution during troubleshooting.