Results for “denied_party_flag”

44 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_ITM_RESPONSE_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the WSH (Shipping Execution) product family. It presents consolidated results from Oracle's Item Validation / response-processing framework, exposing the outcome of requests submitted through the Item Validation Organization (ITM) integration with external service providers such as restricted party screening, embargo checking, and export compliance services. The view joins request-control records to their associated response headers and response lines, producing a single reporting surface that answers, for a given shipment line or order line, whether an item or trading partner was cleared, denied, or flagged.

For integration and reporting purposes the view is particularly valuable because it flattens a header/line hierarchy into one denormalized row per response line, and because it carries the SHIP_FROM_COUNTRY_CODE attribute at the request-control level. That column allows compliance outcomes to be analysed by the originating country of shipment, which is a common filtering dimension in export-compliance investigations.

Underlying Base Objects

The view is defined over three documented base objects, referenced in the ETRM metadata through public synonyms:

  • WSH_ITM_REQUEST_CONTROL (aliased WRC) — the driving table, holding the original system reference, original system line reference, process flag, ship-from country code, transaction date, and application identifier.
  • WSH_ITM_RESPONSE_HEADERS (aliased H) — joined on RESPONSE_HEADER_ID, supplying request control ID, vendor, message ID, response date, header-level error diagnostics, and the overall export compliance status.
  • WSH_ITM_RESPONSE_LINES (aliased L) — joined with an outer (+) on RESPONSE_HEADER_ID, supplying party, line-level compliance results, denied-party and embargo flags, and red-flag word detection.

The join between WSH_ITM_REQUEST_CONTROL and WSH_ITM_RESPONSE_HEADERS is an inner join, while WSH_ITM_RESPONSE_LINES is outer-joined. A response that returned only a header with no detail lines therefore still appears, with the line-level columns null.

Key Columns

Common Use Cases and Queries

Typical usage includes export-compliance dashboards, denied-party audit extracts, and reconciliation of screening responses back to shipment lines.

Shipments denied by origin country:

SELECT original_system_reference, original_system_line_reference, ship_from_country_code, party_id, denied_party_flag FROM wsh_itm_response_v WHERE denied_party_flag = 'Y' AND ship_from_country_code = 'CN';

Header responses with no detail line:

SELECT request_control_id, message_id, export_compliance_status FROM wsh_itm_response_v WHERE response_line_id IS NULL;

Error triage by request:

SELECT original_system_reference, h_error_code, l_error_code, export_compliance_description FROM wsh_itm_response_v WHERE h_error_code IS NOT NULL OR l_error_code IS NOT NULL;