Results for “create_lcf_batch”

8 results




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

Overview

GME_API_GRP is the public API package for Oracle Process Manufacturing (OPM) material transaction processing within the Oracle E-Business Suite. In release 12.1.1 and 12.2.2, OPM batch manufacturing, material issue, and material return activities are driven through the GME schema family, and GME_API_GRP acts as a consolidated group API (classification GRP) that exposes the core routines used to pre-process, validate, post, and report on material movements. The package is owned by APPS and is called by both seeded OPM forms and other program units; the ETRM metadata records that it is referenced by thirteen other packages, confirming its role as a shared service layer rather than an end-user facing component.

The package is most commonly encountered by developers searching for get_mat_trans, a documented procedure that returns material transaction records, alongside its companion routines for lot transactions, material reservations, and pending product lots. Together these procedures form the read-side interface that reporting, reconciliation, and UI components use to retrieve OPM material transaction detail.

Key Procedures and Functions

The ETRM metadata documents twenty-five procedures and functions. The principal transactional routines are GME_PRE_PROCESS_TXNS, which prepares a batch header for transaction processing, and GME_POST_PROCESS_TXNS, which finalizes a transaction and returns status and message data. CREATE_MATERIAL_TXN and CREATE_LCF_BATCH create material transaction and batch records respectively, while UPDATE_MATERIAL_DATE and UPDATE_STEP_QUALITY_STATUS maintain material detail dates and step quality information.

Validation and availability routines include VALIDATE_SUPPLY_DEMAND, which checks a supply/demand combination and returns a validity indicator together with the standard API message list, and GET_AVAILABLE_SUPPLY_DEMAND, which computes available quantity and returns the source unit of measure codes. GET_PLANNING_OPEN_QTY supplies planning open quantity, and CHECK_INV_NEGATIVE tests whether an inventory position would go negative.

The reporting cursors are the most frequently referenced: GET_MAT_TRANS returns material transactions, GET_LOT_TRANS returns lot-level transactions, GET_MAT_RESVNS returns material reservations, and GET_MAT_PPLOTS returns pending product lots, each backed by one of the strongly typed REF CURSOR declarations (G_GMO_TXNS, G_GMO_LOT_TXNS, G_GMO_RESVNS, G_GMO_PPLOTS). Supporting routines include GET_MATERIAL_RESERVATIONS, GET_TOTAL_QTY, GET_BATCH_SHORTAGES, IS_RESERVATION_FULLY_SPECIFIED, SUBSTITUTE_INGREDIENTS, and GET_INGR_SUB_DATE, which support ingredient substitution and reservation completeness checks.

Tables Accessed

The package operates against OPM and Oracle Inventory tables through APPS synonyms. Batch-level data is read from GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_ACTIVITIES, GME_BATCH_STEP_ITEMS, and GME_BATCH_STEP_RESOURCES. Material detail and transaction data flow through GME_MATERIAL_DETAILS, GME_TRANSACTION_PAIRS, FM_MATL_DTL, and GME_RESOURCE_TXNS_GTMP.

Inventory integration occurs through MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_TEMP, and MTL_TRANSACTIONS_INTERFACE, which the transaction creation and posting routines use to stage and commit inventory movements. Pending product output is held in GME_PENDING_PRODUCT_LOTS. Recipe and message metadata are read from GMD_RECIPE_VALIDITY_RULES and FND_NEW_MESSAGES.

Usage Notes

GME_API_GRP is invoked by OPM batch and material transaction forms, by concurrent programs that post or reconcile material activity, and by custom PL/SQL extensions requiring access to OPM transaction detail. Callers should invoke the transactional procedures with the standard FND_API message list initialization and inspect X_RETURN_STATUS, X_MSG_COUNT, and X_MSG_DATA before proceeding. The cursor-returning procedures are intended for read-only reporting and should be closed by the calling program. Because the package is referenced by numerous other packages, customizations should call it rather than modify it, and version compatibility should be confirmed against the target 12.1.1 or 12.2.2 patch level.