Search Results save_all_data

Overview

APPS.GME_RESCHEDULE_STEP_PVT is a private (PVT) PL/SQL package within the Oracle E-Business Suite Process Manufacturing (GME) module. Its purpose is to support the recalculation and persistence of scheduling information for process batch steps. In process manufacturing, a batch is decomposed into discrete batch steps, each of which carries planned start and end dates governed by resource availability, dependencies between steps, and workday calendars. When a step's timing changes—whether because of a manual adjustment, a resource contention, or a cascading dependency realignment—the batch step records, their associated charges, items, resources, and material details must be updated consistently. GME_RESCHEDULE_STEP_PVT encapsulates this rescheduling logic so that the caller does not need to coordinate directly across the underlying GME tables.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, a design that makes it suitable for internal invocation by other GME packages and APIs operating under the APPS schema context. As a PVT classification package, it is intended for internal, Oracle-supported use rather than as a public integration surface.

Key Procedures and Functions

The package exposes two documented procedures:

• RESCHEDULE_STEP — Performs the core rescheduling operation for a given batch step. It accepts the batch step record and a collection of related source step identifiers, along with flags controlling contiguous scheduling, whether preceding and succeeding steps are rescheduled, and whether a workday calendar is applied. It returns the updated batch step record and a return status. This procedure is the primary entry point for recomputing step timing and propagating the effect to dependent steps.
• SAVE_ALL_DATA — Persists the rescheduled data. It accepts the batch step record together with calendar usage and contiguity override flags, a start date, and an end date, returning a status. This procedure writes the recalculated scheduling and associated detail rows to the database.

Tables Accessed

Through APPS synonyms, the package reads and writes the following documented tables:

• GME_BATCH_STEPS — the primary target; holds individual batch step records and their scheduling columns.
• GME_BATCH_HEADER — the parent batch definition, consulted for header-level context.
• GME_BATCH_STEP_CHARGES, GME_BATCH_STEP_ITEMS, GME_BATCH_STEP_RESOURCES — step-level detail rows that must remain consistent when step timing shifts.
• GME_BATCH_STEP_DEPENDENCIES — defines precedence relationships that drive cascading rescheduling.
• GME_MATERIAL_DETAILS — material consumption and production details tied to steps.
• GME_RESOURCE_TXNS and GME_RESOURCE_TXNS_GTMP — resource transaction records and the global temporary staging table used during recalculation.
• DUAL and PLITBLM — utility references for scalar selection and PL/SQL table handling.

Usage Notes

GME_RESCHEDULE_STEP_PVT is referenced by three other packages, indicating it is invoked internally by higher-level GME scheduling and batch maintenance routines rather than called directly by end users. Typical callers include batch scheduling and process execution APIs that detect a change in step timing and delegate the recalculation to this package. It may be triggered from the Process Manufacturing workbench forms when a planner adjusts a batch step, or from concurrent programs that perform bulk rescheduling across batches.

Because the package is a PVT API, customizations should avoid direct invocation; Oracle does not guarantee signature stability for private APIs across patch levels, including between 12.1.1 and 12.2.2. Where custom rescheduling is required, the supported approach is to use the corresponding public GME APIs, which in turn call this private package and manage transaction integrity and return-status handling on the caller's behalf.