Search Results create_batch

Overview

GMP_BATCH_WRAPPER_PKG is a public wrapper package in the Oracle E-Business Suite Process Manufacturing (OPM) module. It belongs to the APPS schema and is classified under the "OTHER" API category in the ETRM repository for release 12.1.1 and 12.2.2. The package provides a thin, versioned interface to the batch creation functionality exposed by GME_API_PUB, the core public API for GME (Process Manufacturing) batch objects.

Its central purpose is to allow callers—whether concurrent programs, forms, or custom extensions—to create a process batch record without binding directly to the underlying publication API. The single documented procedure, CREATE_BATCH, simply forwards its arguments to GME_API_PUB.CREATE_BATCH, preserving the standard Oracle API conventions (API version, validation level, initialization of the message list, commit flag, and the standard out parameters for messages and return status). This indirection insulates the wrapper's callers from changes in the underlying API and gives Oracle a controlled point at which batch creation behavior can be adjusted across releases.

Key Procedures and Functions

The ETRM metadata documents exactly one procedure on this package:

• CREATE_BATCH — Creates a process manufacturing batch. The procedure accepts the standard API framework parameters (API version, validation level, message list initialization, commit flag, and the corresponding out parameters for message count, message list, and return status). It also accepts the batch header record, organization code, batch size and its unit of measure, the creation mode, recipe identification (ID, number, and version), product identification (number, ID, and item revision), and a set of behavioral flags covering quantity-below-capacity handling, workday calendar use, contiguity override, and the least-cost validity rule. It returns the created batch header record and a table of exception materials. The procedure body performs no independent processing; it delegates the entire operation to GME_API_PUB.CREATE_BATCH, passing every parameter straight through. The header comment identifies the file as GMPBTWRB.pls, indicating this is a small, purpose-built wrapper rather than a business-logic implementation.

Tables Accessed

The documented table referenced through APPS synonyms is:

• GME_BATCH_HEADER — The base table for process batch header information. It is used in two ways: the incoming parameter p_batch_header_rec is typed against the GME_BATCH_HEADER rowtype, allowing the caller to supply header-level attributes for the new batch, and the outgoing parameter x_batch_header_rec returns the batch header as persisted, including system-generated identifiers and defaults. The actual insert is performed by GME_API_PUB.CREATE_BATCH; the wrapper itself neither reads nor writes the table directly, but the table is fundamental to the contract of its only procedure.

Usage Notes

CREATE_BATCH is typically invoked when an application or custom program needs to create an OPM batch programmatically—for example, from a concurrent program that generates batches from a planning or demand source, from a form-based extension, or from interface code that loads batch data from an external system. Because the wrapper exposes the same signature as GME_API_PUB.CREATE_BATCH, it can be used as a drop-in replacement in existing code paths.

Standard API calling conventions apply. Callers should pass a validation level and check x_return_status against FND_API.G_RET_STS_SUCCESS, inspect x_message_list for errors, and set p_commit to FND_API.G_TRUE only when the caller owns the transaction. When p_commit is G_FALSE, the caller is responsible for committing or rolling back. Recipe and product parameters may be supplied by ID or by number, and the creation mode determines how the batch is generated. The ETRM repository notes this package is referenced by one other package, confirming its role as a narrow, reusable entry point rather than a widely depended-upon utility.