Search Results create_line_reservations

Overview

APPS.GME_API_MAIN is the principal public API package for the Oracle EBS Process Manufacturing (OPM) batch and production module. It exposes a programmatic, business-logic-validated interface to the GME (Process Execution) schema, allowing batch headers, batch steps, material lines, and material reservations to be created and manipulated without direct table access. The package centralizes validation, recipe and product resolution, workday-calendar handling, and the FND message stack, returning standard FND_API return statuses and message lists. Its header identifies it as a 12.1.1/12.2.2-era file (GMEMAPIB.pls, version 120.40.12020000.2), and it operates under the APPS schema with an API classification of OTHER. The package is referenced by two other packages, confirming it is a foundational dependency within the OPM API layer.

Key Procedures and Functions

The documented interface comprises 37 procedures and functions. The core batch lifecycle procedures are:

• CREATE_BATCH — the central constructor; accepts a batch header record plus batch size, UOM, creation mode, recipe/product identifiers, and validation controls, and returns the created header record and an exception-material table. Handles setup, savepointed rollback, and message stack initialization.
• CREATE_PHANTOM — creates a phantom (non-physical) batch, typically for intermediate or sub-assembly production.
• SCALE_BATCH — rescales batch quantities, including UOM conversion.
• THEORETICAL_YIELD_BATCH — computes theoretical yield for a batch.
• INSERT_MATERIAL_LINE / UPDATE_MATERIAL_LINE / DELETE_MATERIAL_LINE — maintain the material detail lines attached to a batch.
• INSERT_STEP / DELETE_STEP — maintain batch routing steps.
• RESCHEDULE_BATCH / RESCHEDULE_STEP — reschedule batch and step dates.
• CREATE_BATCH_RESERVATIONS — creates reservations for all material lines of a batch.
• CREATE_LINE_RESERVATIONS — creates reservations for individual material lines; this is the procedure most relevant to the user's search term.
• RELEASE_BATCH / RELEASE_STEP — release batches or individual steps for execution.
• COMPLETE_BATCH / COMPLETE_STEP — record batch or step completion.
• REVERT_BATCH / REVERT_STEP — reverse release or completion actions.
• CLOSE_BATCH — close a completed batch.

Tables Accessed

The package reads and writes the core OPM execution tables through APPS synonyms:

• GME_BATCH_HEADER — the master batch record; inserted by CREATE_BATCH, updated by release, complete, reschedule, and close routines.
• GME_BATCH_STEPS — step-level routing records modified by step procedures.
• GME_MATERIAL_DETAILS — material line records maintained by the material-line procedures and used by reservation routines.
• GME_PENDING_PRODUCT_LOTS — pending lot information associated with batch production.
• MTL_SYSTEM_ITEMS_KFV — key flexfield view used to resolve and validate item identifiers.
• PLITBLM — the FND message/error stack table used to publish validation and error messages.

Usage Notes

GME_API_MAIN is typically invoked from the OPM Batch Maintenance forms and from concurrent programs that create or manipulate batches, and it is called by custom PL/SQL code and by the two packages that reference it. Because it performs gme_common_pvt.setup and honors the AFLOG_LEVEL profile for debug logging, callers should expect setup and message-stack side effects. Parameters such as p_validation_level, p_init_msg_list, and the various recipe, product, and calendar options should be set explicitly; callers must inspect x_return_status and x_message_list rather than relying on exceptions, as failures are converted to FND return statuses. Reservation creation via CREATE_LINE_RESERVATIONS and CREATE_BATCH_RESERVATIONS should be invoked after the relevant material lines exist and the batch is in an appropriate state.