Results for “update_move_order_lines”

14 results




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

Overview

GME_MOVE_ORDERS_PVT is a private PL/SQL package body in the APPS schema that provides the core application logic for creating, maintaining, and querying move orders within Oracle Process Manufacturing (OPM). In Oracle EBS 12.1.1 and 12.2.2, move orders are the internal inventory replenishment and transfer documents that stage material between subinventories, locators, or organizations. This package is the process manufacturing extension of the standard Oracle Inventory move order infrastructure exposed by INV_MOVE_ORDER_PUB. Its primary business role is to translate OPM batch and material requirements into move order transactions, ensuring that components and ingredients are staged where they are needed prior to consumption. The package is classified as PVT (private), meaning it is an internal implementation layer rather than a public API; callers are expected to reach it through the higher-level GME transactions and batch APIs that depend upon it. It is referenced by ten other database objects, confirming its central position in the OPM material movement flow.

Key Procedures and Functions

The package exposes nine documented procedures and functions that cover the move order lifecycle:

  • CREATE_MOVE_ORDER_HDR — creates the move order header record, establishing the transaction request that subsequent lines attach to.
  • CREATE_MOVE_ORDER_LINES — creates individual move order lines, defining the item, quantity, and source/destination details for each movement.
  • CREATE_BATCH_MOVE_ORDER — generates move orders for an OPM batch, grouping the material requirements of a batch into move order documents.
  • GET_MOVE_ORDER_LINES — retrieves existing move order lines for display, validation, or downstream processing.
  • DELETE_MOVE_ORDER_LINES — removes move order lines that are no longer required, typically when batch requirements change.
  • UPDATE_MOVE_ORDER_LINES — modifies existing move order lines to reflect revised quantities or destinations.
  • PENDING_MOVE_ORDERS_EXIST — a validation function that determines whether outstanding move orders remain for a given context.
  • GET_PENDING_MOVE_ORDER_QTY — returns the aggregate quantity still pending across open move orders.
  • DELETE_BATCH_MOVE_ORDERS — removes the complete set of move orders associated with a batch.

No parameter signatures are documented in the ETRM metadata; parameter details should be obtained from the package specification in the database.

Tables Accessed

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

Usage Notes

Because GME_MOVE_ORDERS_PVT is a private package, it is not intended for direct invocation by end users. It is typically called from OPM batch and material transaction forms, from concurrent programs that stage or replenish batch components, and from other PL/SQL packages such as GME_TRANSACTIONS_PVT, GME_COMMON_PVT, and INV_MOVE_ORDER_PUB. Custom code should generally invoke the public Inventory move order APIs (INV_MOVE_ORDER_PUB) rather than this private layer. When extending OPM material movement behavior, developers should review the package specification for actual parameter lists, as the ETRM metadata documents procedures by name only.