Search Results wsh_itm_denied_parties




Overview
Explore in AI Chat

Overview

The WSH_ITM_DENIED_PARTIES table is a critical data object within the Oracle E-Business Suite Shipping Execution (WSH) module, specifically supporting the Integrated Trade Management (ITM) functionality. Its primary role is to serve as the repository for detailed records of denied party screening matches. When a shipping transaction undergoes automated compliance screening against government and internal restricted party lists, any potential match or "hit" identified for a party (such as a customer, supplier, or ship-to location) is logged in this table. It functions as a child table to WSH_ITM_RESPONSE_LINES, storing the granular match details that result from the broader scanning process. This table is essential for maintaining an audit trail of compliance checks, enabling businesses to investigate potential violations and demonstrate due diligence in their global trade operations.

Key Information Stored

While the provided metadata does not list specific columns, the table's description and foreign key relationship define its core data elements. The central column is RESPONSE_LINE_ID, which is a foreign key linking each denied party record back to its parent scanning result in the WSH_ITM_RESPONSE_LINES table. Based on its purpose, the table typically stores details about the specific denied party list entry that triggered the match. This would include fields such as the matched party name and address from the list, the source list identifier (e.g., OFAC SDN, BIS Denied Persons), the matching score or confidence level, the specific rule or criteria that triggered the hit, and potentially the severity or risk rating of the match. This data provides the necessary context for a compliance officer to review and clear or confirm a potential match.

Common Use Cases and Queries

The primary use case is generating reports and conducting investigations into denied party screening alerts. Compliance teams query this table to analyze all matches over a period, identify recurring issues, or review the details of a specific blocked shipment. A common SQL pattern involves joining to the parent response lines and related shipping entities to get a full context of the transaction. For example, to find all denied party matches for shipments created in the last week, a query might join WSH_ITM_DENIED_PARTIES to WSH_ITM_RESPONSE_LINES, and then to WSH_DELIVERY_DETAILS or WSH_NEW_DELIVERIES to retrieve shipment numbers and party information. Another critical use case is integration with workflow notifications, where data from this table populates alerts sent to users to take action on a held shipment.

Related Objects

The table has a direct and documented foreign key relationship with one core object, as per the provided metadata:

  • WSH_ITM_RESPONSE_LINES: This is the primary parent table. The relationship is defined by the column WSH_ITM_DENIED_PARTIES.RESPONSE_LINE_ID referencing WSH_ITM_RESPONSE_LINES. Every record in WSH_ITM_DENIED_PARTIES must correspond to a single scanning result record in this table.

Indirectly, through WSH_ITM_RESPONSE_LINES, this table is related to the broader shipping transaction entities, such as delivery details (WSH_DELIVERY_DETAILS) and delivery assignments (WSH_DELIVERY_ASSIGNMENTS), which store the actual business data of the parties being screened.

  • Table: WSH_ITM_DENIED_PARTIES 12.1.1

    owner:WSH,  object_type:TABLE,  fnd_design_data:WSH.WSH_ITM_DENIED_PARTIES,  object_name:WSH_ITM_DENIED_PARTIES,  status:VALID,  product: WSH - Shipping Execution ,  description: In WSH_ITM_RESPONSE_LINES we store the scanning results of all the parties in a request. If a Denied Party match is found for any of the parties the corresponding details of the match are stored in this table ,  implementation_dba_data: WSH.WSH_ITM_DENIED_PARTIES , 

  • Table: WSH_ITM_DENIED_PARTIES 12.2.2

    owner:WSH,  object_type:TABLE,  fnd_design_data:WSH.WSH_ITM_DENIED_PARTIES,  object_name:WSH_ITM_DENIED_PARTIES,  status:VALID,  product: WSH - Shipping Execution ,  description: In WSH_ITM_RESPONSE_LINES we store the scanning results of all the parties in a request. If a Denied Party match is found for any of the parties the corresponding details of the match are stored in this table ,  implementation_dba_data: WSH.WSH_ITM_DENIED_PARTIES , 

  • Table: WSH_ITM_RESPONSE_LINES 12.2.2

    owner:WSH,  object_type:TABLE,  fnd_design_data:WSH.WSH_ITM_RESPONSE_LINES,  object_name:WSH_ITM_RESPONSE_LINES,  status:VALID,  product: WSH - Shipping Execution ,  description: The response header stores general information about the response. For every request a response Header is created. ,  implementation_dba_data: WSH.WSH_ITM_RESPONSE_LINES , 

  • Table: WSH_ITM_RESPONSE_LINES 12.1.1

    owner:WSH,  object_type:TABLE,  fnd_design_data:WSH.WSH_ITM_RESPONSE_LINES,  object_name:WSH_ITM_RESPONSE_LINES,  status:VALID,  product: WSH - Shipping Execution ,  description: The response header stores general information about the response. For every request a response Header is created. ,  implementation_dba_data: WSH.WSH_ITM_RESPONSE_LINES ,