Search Results wsh_ece_views_def




Overview
Explore in AI Chat

Overview

WSH_ECE_VIEWS_DEF is an Oracle E-Business Suite (EBS) PL/SQL package body owned by the APPS schema. Its name reflects its role within the WSH (Shipping) and ECE (E-Commerce/Electronic Commerce) integration layer: it supplies "views" of shipping-related data — that is, resolved and formatted attribute values retrieved at runtime for use by the trading-partner and outbound transaction interfaces. In EBS 12.1.1 and 12.2.2, this package is classified under the ETRM metadata as an OTHER API (neither a public nor a private standard interface), meaning it is an internal helper package rather than a documented, externally supported API.

Functionally, the package assembles descriptive and reference data required when shipping documents, advance ship notices (ASNs), and related outbound EDI/e-commerce messages are constructed. It resolves customer contact details, location codes, invoice references, vehicle type codes, payment terms, and cross-reference part numbers from the various base tables that hold that information. The package also exposes an update routine to persist delivery/ASN information, bridging the gap between the WSH delivery model and the ECE trading-partner header model.

Key Procedures and Functions

The ETRM metadata documents thirteen procedures and functions within WSH_ECE_VIEWS_DEF. They can be grouped as follows:

Each routine is a value-returning helper intended to be called by the calling integration process at the point where a specific field is required, rather than as a standalone transaction.

Tables Accessed

The package references a broad set of base tables through APPS synonyms, which confirms its role as a cross-domain data aggregator:

Usage Notes

WSH_ECE_VIEWS_DEF is an internal implementation package, not a public API. It is invoked by the standard shipping and e-commerce integration flows, and the metadata confirms that it is referenced by nine other packages — most likely the WSH outbound message builders and the ECE trading-partner processing routines. In practice it is called when an outbound shipping document, ASN, or e-commerce message is being assembled, so that the correct customer contacts, locations, payment terms, cross-references, and delivery data are resolved and formatted.

Because it is classified as OTHER and is not externally documented or supported, customization should be avoided. Any extension should instead be implemented by wrapping or copying the necessary logic into a customer-owned package, and the dependency list should be reviewed before upgrades between 12.1.1 and 12.2.2, since the HZ and WSH data model objects it depends upon are among those most frequently changed by Oracle patching.