Search Results get_shipmethod_meaning




Overview

GML_MOBILE_SHIP_CONFIRM is an Oracle EBS PL/SQL package owned by the APPS schema and classified as a mobile-oriented shipping API. It belongs to the process manufacturing/logistics execution family of modules (the GML prefix) and provides the server-side logic that supports mobile shipping confirmation workflows. Its primary business function is to allow warehouse personnel using handheld or mobile devices to confirm outbound deliveries, record shipped and missing quantities, return lines to stock, and submit delivery line information against inventory and shipping tables used by Oracle Shipping Execution (WSH) and Oracle Inventory (INV).

The package exposes both query procedures that populate mobile user interfaces with lookup data and transactional procedures that update delivery and inventory records. It also encapsulates validation and confirmation logic, including shipping method resolution, delivery line assignment, and full delivery confirmation.

Key Procedures and Functions

The API is composed of thirteen documented procedures and functions grouped by purpose.

Most transactional procedures return a standard return status along with message data and message count, in keeping with the Oracle Applications API conventions defined by FND_API.

Tables Accessed

The package reads and writes data through APPS synonyms. It references WSH_NEW_DELIVERIES, WSH_DELIVERY_DETAILS, and WSH_DELIVERY_ASSIGNMENTS for delivery headers, delivery lines, and the link between lines and deliveries. Carrier and service information is obtained from WSH_CARRIERS, WSH_CARRIER_SERVICES, and WSH_ORG_CARRIER_SERVICES. Item data is resolved through MTL_SYSTEM_ITEMS_KFV and MTL_CROSS_REFERENCES. WMS_LICENSE_PLATE_NUMBERS supports warehouse management license plate references, OE_SETS is used for line sets, and DUAL provides standard singleton queries.

Usage Notes

GML_MOBILE_SHIP_CONFIRM is typically invoked from Oracle Mobile Supply Chain Applications (MSCA) forms and related RF/mobile shipping pages rather than from batch concurrent programs. The ETRM metadata records no packages that reference it, indicating it is an entry-point API consumed by the mobile application layer. Customizations should call the transactional procedures using the documented parameters and must honor the FND_API commit and return-status conventions, checking x_return_status and processing x_msg_data and x_msg_count on every call.