Search Results close_trip

Overview

WMS_DIRECT_SHIP_PVT is a private PL/SQL package body in the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite. Its business purpose is to support the direct ship (also known as drop ship or cross-ship) fulfillment flow, in which goods move from a supplier or a warehouse staging location directly to a customer without passing through standard receiving and put-away. The package orchestrates the transactional steps required to confirm such shipments, build and manage trips and trip stops, update deliveries, generate shipping documentation, and close out the trip once the load has departed. Internally the package maintains rich PL/SQL record and collection types, including lpn_content_rec, lpn_contents_tab, lpn_contents_lookup_rec, lpn_contents_lookup_tab, and checked_delivery_tab, which together model the contents of a License Plate Number (LPN) and track which deliveries have already been validated against that LPN. This LPN-centric data model is central to the package's direct-ship logic, and it is the reason the "load_lpn" search term maps to this object: LPN contents are assembled, validated, and confirmed here before shipment.

Key Procedures and Functions

The package exposes 47 documented procedures and functions. The principal ones are described below; parameter lists are intentionally omitted.

• SHIP_CONFIRM and CONFIRM_ALL_DELIVERIES — perform shipment confirmation for a delivery or for all eligible deliveries, driving the core direct-ship transaction.
• CHECK_DIRECT_SHIP_FOR_LPN and CHECK_DELIVERY — validate whether an LPN or delivery qualifies for the direct-ship process, returning status used by the confirmation routines.
• GET_DELIVERY_INFO and GET_TRIPSTOP_INFO — retrieve delivery and trip-stop attributes required during shipment processing.
• CREATE_TRIP, UPDATE_TRIPSTOP, CLOSE_TRIP, and UNLOAD_TRUCK — manage the trip lifecycle, from creation through trip-stop updates, vehicle unloading, and final closure.
• UPDATE_DELIVERY — writes back delivery status and related attributes after confirmation.
• PRINT_SHIPPING_DOCUMENT — triggers generation of shipping paperwork such as the Bill of Lading.
• GET_BOL, GET_ENFORCE_SHIP, GET_FREIGHT_TERM, GET_FOB_LOCATION, GET_FOBLOC_CODE_MEANING, and GET_SHIPMETHOD_MEANING — supply descriptive and control values (Bill of Lading, shipping enforcement flag, freight terms, FOB location and code meanings, ship method meaning) used in documents and validation.
• GET_CATCH_WEIGHT — computes catch weight for an LPN given the organization, LPN, item, revision, lot, and picked quantity in the primary unit of measure.
• MISSING_ITEM_CUR — a cursor-based routine identifying items missing from the expected LPN contents.
• DEBUG — internal diagnostic/logging utility.

Tables Accessed

The package reads and writes a broad set of inventory, order, and project tables through APPS synonyms. Inventory master and location data come from MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, and MTL_SYSTEM_ITEMS_KFV for item attributes and descriptions, and MTL_ITEM_LOCATIONS and MTL_SECONDARY_INVENTORIES for locator and subinventory context. Lot, serial, and catch-weight handling draws on MTL_LOT_NUMBERS, MTL_LOT_UOM_CLASS_CONVERSIONS, MTL_SERIAL_NUMBERS, and MTL_SERIAL_NUMBERS_TEMP. Transactional shipment activity is recorded through MTL_MATERIAL_TRANSACTIONS_S, MTL_RESERVATIONS, and MTL_TRANSACTION_TYPES. Order information is sourced from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, which tie the direct shipment back to the originating sales order. PJM_ORG_PARAMETERS provides organization-level project manufacturing parameters that govern direct-ship eligibility and processing behavior.

Usage Notes

WMS_DIRECT_SHIP_PVT is a private (PVT) package and is therefore not intended as a public integration API. It is referenced by three other packages within the WMS and shipping stack and is typically invoked indirectly through those packages, Oracle Shipping forms, or WMS mobile pages that drive shipment confirmation and trip management. Because the confirmation routines perform transactional writes to inventory and delivery records, any custom invocation should follow the same validation sequence used internally: check direct-ship eligibility for the LPN or delivery, confirm the shipment, update the delivery, and only then create or update the trip and print shipping documents. Debug logging can be enabled through the DEBUG routine for troubleshooting. Custom code should treat the package as version-sensitive, since its internal record structures and LPN handling logic are subject to change across 12.1.1 and 12.2.2 patch levels.