Search Results update_rcv_lots_supply

Overview

APPS.RCV_GML_CONV_MIG is a migration utility package in Oracle E-Business Suite that supports the conversion and migration of Process Manufacturing (GML/OPM) receiving data into the standard Oracle Inventory and Receiving transaction model. Its header identifies it as a non-shipped ($Header: RCVMGGMS.pls 120.0, marked "noship") object, indicating it is used internally for data migration rather than as a generally supported public API. The package consolidates legacy GML lot and supply records into the core RCV_LOTS_SUPPLY, RCV_SUPPLY, RCV_LOT_TRANSACTIONS, and RCV_TRANSACTIONS tables so that historical receiving activity becomes visible and usable through standard Receiving and Inventory functionality.

Key Procedures and Functions

The package exposes four documented procedures, each addressing a discrete stage of the migration:

• RCV_MIG_GML_DATA — The primary driver procedure. It orchestrates the overall GML receiving migration, coordinating the transformation of staged GML data into the standard receiving tables and serving as the entry point for the conversion process.
• UPDATE_RCV_LOT_TRANSACTIONS — Populates or reconciles lot-level transaction records in the receiving transaction tables, ensuring migrated GML lot movements are reflected as valid RCV lot transaction entries.
• UPDATE_RCV_SUPPLY — Updates receiving supply records so that migrated GML receipts contribute correctly to the open receiving supply picture.
• UPDATE_RCV_LOTS_SUPPLY — The procedure directly associated with the user's search term. It reconciles and updates lot-level supply records, tying migrated GML lots to their corresponding receiving supply rows so that lot quantity and availability are consistent with the converted data.

No parameter lists are documented in the available metadata; the procedures are named and described here by purpose only.

Tables Accessed

The package references a defined set of tables through APPS synonyms. Staging and source tables include GML_PO_MIG_ERRORS (migration error logging), GML_RCV_LOTS_MIGRATION, IC_ITEM_MST_B_MIG, and IC_LOTS_MST_MIG, which hold legacy item, lot, and migration data to be converted. Target receiving tables include RCV_LOTS_SUPPLY, RCV_SUPPLY, RCV_LOT_TRANSACTIONS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS. Supporting setup and validation tables include MTL_SYSTEM_ITEMS_B, MTL_UNITS_OF_MEASURE, MTL_TRANSACTION_REASONS, and MTL_PARAMETERS, used to validate items, units of measure, reasons, and inventory organization parameters during conversion.

Usage Notes

RCV_GML_CONV_MIG is classified under the OTHER API classification, meaning it is not a formally supported public API. Consistent with its "noship" header, it is typically invoked as a one-time or controlled migration utility, generally through custom concurrent programs, SQL*Plus scripts, or migration tooling rather than from standard EBS forms. It is referenced by no other packages, confirming it operates as a top-level conversion routine. Because it writes directly to core receiving supply and transaction tables, it should be executed only within a controlled migration window, with appropriate backups of RCV_SUPPLY, RCV_LOTS_SUPPLY, and related tables, and followed by validation reports against GML_PO_MIG_ERRORS. The procedures can be run individually to update specific target tables or collectively via RCV_MIG_GML_DATA to perform the complete migration. Given the metadata is limited, its exact invocation signature should be confirmed against the deployed source before use in a production migration.