Search Results wsh_interface_errors_s




Overview

WSH_INTERFACE_VALIDATIONS_PKG is the validation engine for Oracle Shipping Execution's open interface. Its business purpose is to inspect inbound delivery, delivery detail, and delivery assignment records staged in the WSH interface tables before the Shipping Interface concurrent programs promote them into the live shipping tables. Records that fail validation are rejected, and the reason is written back to the interface error table so users can correct the source data and resubmit. The package also supports the ship-request/advice comparison and document validation logic used by integration points such as XML Gateway (ECX_TP_HEADERS) and requisition-driven inbound flows.

The package body is documented in ETRM for both 12.1.1 and 12.2.2 with owner APPS and status VALID. It is a dependency-heavy package: it relies on FND_API, FND_MESSAGE, FND_GLOBAL, FND_PROFILE, WSH_UTIL_CORE, WSH_DEBUG_SV, and WSH_DEBUG_INTERFACE. It is referenced by five other database packages while itself referencing no additional application packages beyond those listed.

Key Procedures and Functions

ETRM documents seven procedures/functions for this package. Because parameter lists are not exposed in the metadata, only purposes are described below.

  • VALIDATE_DOCUMENT — Performs document-level validation of inbound shipping data, checking header/document attributes for consistency before the associated delivery lines are processed.
  • GET_CLIENT_DETAILS — Retrieves client and operating-unit context details (via MTL_PARAMETERS and MTL_CLIENT_PARAMETERS) needed to drive validation rules for the current inventory organization.
  • NAME — Returns the name identifier associated with the validation context; a utility helper used to label or route validation logic.
  • VALIDATE_DELIVERIES — The core validation routine for staged delivery, delivery detail, and delivery assignment interface records, applying business rules and flagging failures.
  • COMPARE_SHIP_REQUEST_ADVICE — Compares shipper request data with advanced shipment notice (advice) data to detect discrepancies between what was requested and what a trading partner indicates will be shipped.
  • LOG_INTERFACE_ERRORS — Writes validation failures into WSH_INTERFACE_ERRORS (using the WSH_INTERFACE_ERRORS_S sequence), producing the error records users query when reviewing rejected interface rows.

Tables Accessed

The package reads reference and setup data from MTL_PARAMETERS, MTL_CLIENT_PARAMETERS, HR_ORGANIZATION_INFORMATION, and ECX_TP_HEADERS (trading partner information). It validates against live transactional tables including WSH_DELIVERY_DETAILS, WSH_DELIVERY_ASSIGNMENTS, WSH_NEW_DELIVERIES, WSH_SHIPMENT_BATCHES, WSH_TRANSACTIONS_HISTORY, OE_ORDER_LINES_ALL, PO_REQUISITION_HEADERS_ALL, and PO_REQUISITION_LINES_ALL. The interface staging tables are WSH_DEL_DETAILS_INTERFACE, WSH_DEL_ASSGN_INTERFACE, and WSH_NEW_DEL_INTERFACE. Error output is stored in WSH_INTERFACE_ERRORS with the WSH_INTERFACE_ERRORS_S sequence; WSH_INTERFACE_ERRORS_S is the object most commonly searched in this context, as it is the sequence that generates the surrogate error identifier surfaced in shipping interface error inquiries.

Usage Notes

In typical EBS deployments this package is invoked indirectly by the Shipping Interface concurrent programs rather than being called directly by end users. It executes during the interface run, validating each staged record prior to insert into the live delivery tables, and returns errors that appear in the shipping interface error forms and reports. Because WSH_INTERFACE_ERRORS_S is the sequence behind WSH_INTERFACE_ERRORS.INTERFACE_ERROR_ID, custom code that inserts interface errors or queries them should follow the same sequencing convention. Customizations that bypass validation, or that insert directly into the live WSH tables, risk missing the checks this package enforces. Debug output can be enabled through WSH_DEBUG_SV and WSH_DEBUG_INTERFACE profile options when diagnosing validation failures.