Results for “wsh_cc_response_lines”

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

Overview

The WSH_CC_RESPONSE_LINES table is a Shipping Execution (WSH) module object that stores response line information returned by external trade compliance, screening, and restricted-party verification services invoked during Oracle E-Business Suite order and shipment processing. Each row captures the outcome of a compliance check performed against an entity such as a customer, ship-to address, or order line, recording flags for embargo conditions, license requirements, denied-party matches, and any error conditions returned by the screening engine. The table serves as the transactional detail layer beneath the response header, preserving per-entity results that downstream processes use to accept, hold, or block shipments.

Heuristic Data Vault classification for this object is standalone, though the presence of a foreign key to WSH_ITM_RESPONSE_HEADERS suggests it functions as a detail or satellite-style table attached to a response header hub. Under this modeling suggestion, the header acts as the parent hub, while WSH_CC_RESPONSE_LINES records descriptive and flag-bearing attributes linked to that header, including multi-valued screening results across entities.

Key Information Stored

The table contains 28 documented columns. The surrogate primary key is RESPONSE_LINE_ID, enforced by constraint WSH_CC_RESPONSE_LINES_PK. RESPONSE_HEADER_ID is a foreign key resolving to WSH_ITM_RESPONSE_HEADERS, establishing the parent-child relationship and serving as the principal join key for reporting.

• RESPONSE_LINE_ID — surrogate primary key for each response line.
• RESPONSE_HEADER_ID — foreign key to WSH_ITM_RESPONSE_HEADERS; links the line to its originating compliance response.
• SERVICE_TYPE_CODE — identifies the screening or compliance service invoked.
• TRANSACTION_SOURCE_TYPE — source of the transaction being screened.
• EMBARGO_FLAG — indicates whether an embargo condition was detected.
• LICENSE_REQUIRED — denotes whether an export license is required.
• LICENSE_CLASSIFIER, LICENSE_EXCEPTION, LICENSE_EXC_TYPE — license classification and exception details returned by the service.
• DENIED_PARTY_FLAG — signals a denied-party list match.
• RED_FLAG_WORDS — keywords flagged during screening.
• EXCEPTION_TYPE_CODE, REASON — categorization and narrative explanation of the finding.
• ERROR_CODE, ERROR_TEXT, ERROR_SOURCE, ERROR_TYPE — diagnostic fields for failed or partial service responses.
• ENTITY_CODE, ENTITY_ID — identifies the screened entity.
• ORIGINAL_SYSTEM_REFERENCE, ORIGINAL_SYSTEM_LINE_REFERENCE — external system linkage.
• USER_DEF_ID1, USER_DEF_ID2 — descriptive flexfield-style user identifiers.
• Audit columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Compliance and logistics teams query this table to audit screening outcomes, identify blocked shipments, and reconcile denied-party or embargo holds. A typical join retrieves header context alongside line-level flags:

SELECT l.response_line_id, l.denied_party_flag, l.embargo_flag,
       l.license_required, l.reason
FROM   wsh.wsh_cc_response_lines l,
       wsh.wsh_itm_response_headers h
WHERE  l.response_header_id = h.response_header_id
AND    l.denied_party_flag = 'Y';

Reporting use cases include exception trending by SERVICE_TYPE_CODE, error rate analysis using ERROR_CODE and ERROR_TYPE, and audit trails keyed on ENTITY_ID. Because audit columns are present, incremental extracts using LAST_UPDATE_DATE are practical.

Related Objects

• WSH_ITM_RESPONSE_HEADERS — parent table joined via RESPONSE_HEADER_ID.
• WSH_CC_RESPONSE_LINES_PK — primary key constraint on RESPONSE_LINE_ID.
• WSH Delivery and Shipment tables (e.g., WSH_DELIVERY_DETAILS, WSH_DELIVERIES) — consume compliance outcomes to hold or release shipments.
• OE_ORDER_HEADERS / OE_ORDER_LINES — order entities typically referenced via ENTITY_ID when screening sales orders.
• HZ_CUST_ACCOUNTS / HZ_LOCATIONS — customer and address entities subject to screening.
• Trade Compliance / Restricted Party Screening APIs — populate response headers and lines during integration calls.