Results for “gmo_dispense_grp”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMO_DISPENSE_GRP is an Oracle E-Business Suite PL/SQL package body owned by APPS and classified as a Group (GRP) API within the ETRM metadata model. In Oracle EBS 12.1.1 and 12.2.2, the GMO schema prefix designates the Process Manufacturing (OPM) dispensing and material consumption module. This package encapsulates the business logic that governs how materials are reserved, dispensed, and reconciled against production batches on the shop floor.

The package is the central programmatic entry point for material dispensing activities. It bridges the reservation records held against inventory and the physical or logical dispensing transactions recorded by operators. Its procedures and functions are used to validate whether an item is a dispense-controlled item, to transfer reservations between batch steps, to change the status of a dispensing transaction, to determine whether dispensing has occurred at a specific dispense booth or dispensing area, and to instantiate dispensing setup data. Because the package is classified as a GRP API, it is intended to be called by other Oracle EBS modules rather than directly by end users.

Key Procedures and Functions

The documented API surface contains seven procedures and functions:

• MAINTAIN_RESERVATION — Maintains the link between a material dispense record and its reservation. It updates reservation identifiers on the material dispense table, moving a reservation from an old to a new reservation for a given batch, item, material detail, and batch step. It follows the standard FND_API pattern of savepoint creation, compatibility checking, message list initialization, and return status handling.
• CHANGE_DISPENSE_STATUS — Alters the status of a dispensing transaction, supporting the lifecycle transitions that govern whether material has been dispensed, reversed, or otherwise updated.
• IS_DISPENSE_ITEM — A validation function that determines whether a given inventory item is subject to dispensing controls.
• GET_MATERIAL_DISPENSE_DATA — Retrieves dispensing data for a material line, returning the dispense details required by callers.
• INSTANTIATE_DISPENSE_SETUP — Creates or populates dispensing setup records, establishing the configuration under which dispensing occurs.
• ISDISPENSEOCCUREDATDISPBOOTH — Determines whether dispensing has occurred at a specific dispense booth.
• ISDISPENSEOCCUREDATDISPAREA — Determines whether dispensing has occurred within a specified dispensing area.

Tables Accessed

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

• GMO_MATERIAL_DISPENSES — The primary transactional table for dispensing activity. MAINTAIN_RESERVATION performs an UPDATE against this table, setting reservation_id to the new reservation value for the matching batch, inventory item, material detail, old reservation, and batch step. This is the core record that links a reserved quantity to a dispensed quantity.
• GMO_MATERIAL_UNDISPENSES — Records the reversal or undispense of previously dispensed material. It supports the status change and reconciliation logic, ensuring that quantities returned to inventory are tracked separately from the original dispense.

Usage Notes

GMO_DISPENSE_GRP is referenced by eight other packages within the EBS instance, indicating that it acts as a shared service layer for dispensing operations rather than a standalone utility. It is typically invoked from Process Manufacturing shop floor and dispensing forms, from batch-related concurrent programs, and from custom extensions that need to validate or manipulate dispensing records programmatically.

The header reference ($Header: GMOGDSPB.pls 120.10 2007/12/13) indicates the package was last shipped in the 12.x code line and remains available in both 12.1.1 and 12.2.2. Callers should invoke procedures using the standard FND_API conventions, passing p_api_version, p_init_msg_list, and p_commit, and should inspect x_return_status, x_msg_count, and x_msg_data for error handling. Note that the package first checks whether GMO is enabled via GMO_SETUP_GRP.IS_GMO_ENABLED; if GMO is disabled, MAINTAIN_RESERVATION returns success immediately with a GMO_DISABLED_ERR message rather than performing any reservation update. This behavior should be accounted for in any custom integration that depends on the procedure completing work.