Search Results create_delivery_details




Overview
Explore in AI Chat

Overview

WSH_INTERFACE_PUB is a public PL/SQL API package in the Oracle E-Business Suite Shipping (WSH) module, owned by the APPS schema and classified as a PUBLIC (PUB) interface. Its purpose is to provide a controlled, supported entry point for external systems, feeder applications, and custom code that need to push shipment line information into the Oracle Shipping execution data model. The package header declares the AUTHID CURRENT_USER directive, indicating that its procedures execute with the privileges of the calling user rather than the definer, which is consistent with standard EBS public API security practice. The source header identifies the original development revision (115.2, dated 2002/11/18) and confirms it is part of the core shipping delivery detail import infrastructure. In the Oracle EBS 12.1.1 and 12.2.2 releases, this package serves as the thin public wrapper that decouples calling applications from the internal delivery details package, allowing Oracle to evolve the underlying implementation without breaking integrators that depend on the documented public signature.

Key Procedures and Functions

The ETRM metadata documents a single public procedure in this package:

  • Create_Shipment_Lines — This procedure is described in the source comments as a wrapper for create_delivery_details. It is called by any system that is pushing shipment lines into the shipping system. Its parameters follow the standard EBS API convention: an input/output delivery details record typed as WSH_DELIVERY_DETAILS_PKG.delivery_details_rec_type, an output parameter returning the generated delivery detail identifier (x_delivery_detail_id), and an output status parameter (x_return_status) indicating the outcome of the call. Because the record type is IN OUT NOCOPY, the calling program may receive modified values back in the same record structure it passed in. No other public procedures or functions are documented for this package in the 12.2.2 metadata.

Tables Accessed

The documented table reference for this package resolves through an APPS synonym to PLITBLM. This reference is consistent with the package's role as an interface wrapper: the bulk of the actual insert and update activity against the shipping delivery details tables (such as WSH_DELIVERY_DETAILS, WSH_DELIVERY_ASSIGNMENTS, and related inventory transaction tables) is performed inside the wrapped create_delivery_details logic, not directly within WSH_INTERFACE_PUB itself. The PLITBLM reference supports internal processing and lookup activity associated with staging and validating the incoming shipment line data. Integrators should treat the underlying delivery details tables as the ultimate persistence targets, while recognizing that WSH_INTERFACE_PUB is the sanctioned public entry point rather than a direct table-access layer.

Usage Notes

WSH_INTERFACE_PUB is typically invoked by feeder systems that need to create shipment lines programmatically — for example, order fulfillment interfaces, third-party logistics integrations, or custom concurrent programs that stage shipment data for the shipping execution engine. The ETRM metadata indicates the package is referenced by two other packages, confirming its role as a shared interface dependency within the WSH module rather than a terminal consumer. Callers must supply a properly populated delivery details record and should inspect x_return_status after every invocation to detect validation or processing errors; the returned x_delivery_detail_id should be persisted by the caller for subsequent processing such as delivery assignment or confirmation. As with all EBS public APIs, the procedure should be called within a properly managed transaction, and the caller is responsible for commit or rollback. Because the package is defined with AUTHID CURRENT_USER, the invoking session must have the necessary privileges on the underlying shipping and inventory objects. Direct modification of the delivery details records outside this API is not supported and may bypass validation logic embedded in the wrapper.