Search Results wsh_interface_errors

Overview

WSH_INTERFACE_ERRORS is a Shipping Execution (WSH) transaction table that stores error and diagnostic records generated when data is loaded into Oracle E-Business Suite through the shipping open interfaces. Whenever freight, delivery, trip, or shipping-related records pass through inbound interface programs, rows in this table capture the outcome for any interface record that fails validation or processing. It therefore functions as the audit and troubleshooting repository for shipping interface execution, allowing users to identify which rows were rejected and why.

The table is owned by the WSH schema and is documented as VALID across Oracle EBS 12.1.1 and 12.2.2. The documented physical structure contains 18 columns. Based on the FK relationship data mined from the schema, the object is a standalone structure with no dependent foreign-key relationships and no parent tables — a heuristic Data Vault classification that suggests it is best modeled as a satellite (or, if treated as a self-contained source of truth for interface failures, as a standalone descriptive table) rather than as a hub or link. The modeling classification here is a suggestion derived from the observed FK structure and should not be interpreted as a functional dependency.

Key Information Stored

The table is anchored by a surrogate primary key and also carries a unique business-key candidate:

• INTERFACE_ERROR_ID — the surrogate primary key (WSH_INTERFACE_ERRORS_PK) uniquely identifying each error record. A separate unique index, WSH_INTERFACE_ERRORS_U1, also exists on this column, making it the documented business-key candidate.
• INTERFACE_ERROR_GROUP_ID — groups related error rows produced by a single interface run, so that multiple errors against one interface record can be traced together.
• INTERFACE_TABLE_NAME — the name of the target interface table (e.g., the staging table) into which the record was being loaded.
• INTERFACE_ID — the identifier of the specific interface record, used to correlate the error back to the originating row in the source interface table.
• MESSAGE_CODE and MESSAGE_NAME — the coded message and its descriptive name, used for error categorization and reporting.
• ERROR_MESSAGE — the full text of the error returned by the interface program.
• INTERFACE_ACTION_CODE — the action being attempted (for example, insert or update) when the failure occurred.

Standard EBS Who columns are also present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_BY, LAST_UPDATE_LOGIN, and LAST_UPDATED_BY, plus concurrent-program context columns PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID, which identify the process and request that produced the error. These audit columns support traceability from an error row back to a specific concurrent request.

Common Use Cases and Queries

Typical scenarios include diagnosing why shipping interface records failed, reporting error counts by interface table or message code, and re-processing corrected records. A common query pattern retrieves all errors for a given concurrent request:

SELECT interface_error_id, interface_table_name, interface_id,
       message_code, error_message, interface_action_code
  FROM wsh.wsh_interface_errors
 WHERE request_id = :request_id
 ORDER BY interface_error_id;

For grouping, use INTERFACE_ERROR_GROUP_ID to reconstruct all failures from a single run. Reporting queries frequently aggregate by INTERFACE_TABLE_NAME or MESSAGE_CODE to quantify failure trends, while joins on INTERFACE_ID correlate the error to the specific staging row requiring correction.

Related Objects

The documented FK structure shows WSH_INTERFACE_ERRORS as standalone with no foreign keys. In practice, it is referenced alongside the shipping interface staging tables (identified by INTERFACE_TABLE_NAME and INTERFACE_ID) and with the concurrent request framework via REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID (joining FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS). Related operational objects include the WSH shipping interface programs and their staging tables, plus FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS for run-level context. Because the object is standalone, joins to it are keyed on INTERFACE_ID, INTERFACE_ERROR_GROUP_ID, and REQUEST_ID rather than enforced foreign keys.