Search Results gme_insert_step_pvt




Overview
Explore in AI Chat

Overview

GME_INSERT_STEP_PVT is a private (PVT-classified) PL/SQL package in the APPS schema that belongs to the Oracle Process Manufacturing (OPM) batch and recipe execution layer of Oracle E-Business Suite. Its business purpose is to persist and maintain batch step records and their associated resource requirements within the OPM batch control framework. In OPM terminology, a batch is composed of one or more steps, and each step may consume or produce materials and require resources such as equipment and labor. This package encapsulates the logic required to insert a single batch step together with the derived resource and capacity information needed to schedule and execute production.

Because the package is classified as PVT, it is an internal helper rather than a supported public API. It is not intended for direct invocation by customers or integrators. Instead, it is called by other OPM packages that expose the supported batch maintenance interfaces, such as GME_API_MAIN and GME_UPDATE_STEP_QTY_PVT. This layering allows the public APIs to delegate low-level insert and capacity-calculation work to a shared, reusable unit, while preserving a controlled public interface.

Key Procedures and Functions

The documented package exposes two program units:

  • INSERT_BATCH_STEP — Performs the insertion of a batch step into the OPM batch structure. It creates the step row and the related resource requirement records, and it consults recipe and operation master data to validate and resolve the step definition.
  • CALC_MAX_CAPACITY — Determines the maximum capacity available for a batch step, based on the resources assigned to that step. This value supports capacity checking and scheduling decisions for the batch.

The supported public entry points that drive this package are GME_API_MAIN, GME_INSERT_STEP_PVT itself, and GME_UPDATE_STEP_QTY_PVT. Dependencies also include GMD_RECIPE_FETCH_PUB, which is used to retrieve recipe information, and the Oracle STANDARD package.

Tables Accessed

The package reads and writes the following documented tables (referenced through APPS synonyms):

  • GME_BATCH_HEADER — the parent batch record; used to identify and validate the batch to which a step is being added.
  • GME_BATCH_STEPS — the primary target table; stores the individual batch step records.
  • GME_BATCH_STEP_RESOURCES — stores the resource requirements associated with each batch step.
  • CR_RSRC_MST — the resource master; provides resource definitions and attributes.
  • GMD_OPERATIONS_B — the operations base table; supplies operation definitions used to validate step data.
  • GME_TEXT_HEADER — holds text and note headers that may be attached to step records.
  • MTL_PARAMETERS — inventory organization parameters; supplies organization-level defaults and context.
  • MTL_UNITS_OF_MEASURE and MTL_UOM_CONVERSIONS — used to resolve and convert units of measure for step quantities.
  • PLITBLM — an internal PL/SQL table type used within the package for processing, listed here as a documented dependency.

Usage Notes

GME_INSERT_STEP_PVT is an internal package invoked from within the OPM batch and recipe APIs. It is not a supported public interface, and customers should not call it directly. Typical invocations occur indirectly through user actions in the OPM batch maintenance forms (for example, adding or modifying a batch step) and through batch processing logic, where the public wrapper packages—primarily GME_API_MAIN and GME_UPDATE_STEP_QTY_PVT—call INSERT_BATCH_STEP and CALC_MAX_CAPACITY. Because the package manipulates core OPM batch tables, any direct use in custom code risks corrupting batch integrity and is unsupported. Developers extending OPM functionality should rely on the documented public APIs instead, and treat the ETRM dependency information as the authoritative reference for supported usage.