Results for “wsh_itm_request_control”

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

Overview

WSH_ITM_REQUEST_CONTROL is a Shipping Execution (WSH) table that functions as the Request Interface table for ITM (Inbound/Item Transaction Management) requests in Oracle E-Business Suite. It stores the header-level control information for each ITM request processed by the shipping module, acting as the entry point through which external or internal systems submit requests that are subsequently resolved into item-level records, response headers, and party data.

The table resides in the WSH schema and is documented as VALID in both EBS 12.1.1 and 12.2.2. Its physical schema contains 93 columns, reflecting a wide denormalized request structure that captures order context, shipping attributes, pricing, and conversion data in a single header record. Because other tables such as WSH_ITM_ITEMS and WSH_ITM_RESPONSE_HEADERS carry a foreign key back to REQUEST_CONTROL_ID, the object behaves as the anchor point of the ITM request family.

From a Data Vault modeling perspective, the heuristic classification of this table is hub-leaning. REQUEST_CONTROL_ID is a surrogate primary key that is also exposed as a unique index (WSHITM_REQUEST_CONTROL_U1), making it a strong candidate for a hub key, while the descriptive and transactional columns would naturally distribute across satellites and links.

Key Information Stored

The primary key of the table is defined by the constraint WSH_ITM_REQUEST_CONTROL_PK on the column REQUEST_CONTROL_ID, and the unique index WSHITM_REQUEST_CONTROL_U1 reinforces REQUEST_CONTROL_ID as the business-key candidate. Among the most significant columns are:

• REQUEST_CONTROL_ID — Surrogate primary key identifying a single ITM request control record.
• REQUEST_SET_ID — Groups related requests into a logical set for processing.
• APPLICATION_ID — Foreign key to FND_APPLICATION, identifying the calling application.
• TRANSACTION_DATE and REQUEST_DATE — Timestamps for the request lifecycle.
• MASTER_ORGANIZATION_ID and ORGANIZATION_ID — Organizational context for the request.
• PROCESS_FLAG and DEBUG_FLAG — Control flags governing processing behavior.
• ORDER_NUMBER, ORDER_TYPE, ORDER_LINE_NUMBER, and LINE_NUMBER — Order and line references supplied in the request.
• ORIGINAL_SYSTEM_REFERENCE and ORIGINAL_SYSTEM_LINE_REFERENCE — External source keys used for reconciliation.
• CUST_PO_NUM and ORDERED_DATE — Customer purchase order and order date context.
• PAYMENT_TERM_ID — Foreign key to PN_PAYMENT_TERMS_ALL for payment terms.
• SHIPPING_METHOD_CODE, FREIGHT_TERMS_CODE, SHIP_FROM_COUNTRY_CODE, and SHIP_TO_COUNTRY_CODE — Shipping attributes.
• ORDERED_QUANTITY, ORDERED_QUANTITY_UOM, UNIT_LIST_PRICE, and UNIT_SELLING_PRICE — Quantity and pricing details.
• ATTRIBUTE1 through ATTRIBUTE15 plus corresponding NAME and VALUE columns — Extensible descriptive flexfield style context.

Common Use Cases and Queries

The table is most often queried when diagnosing ITM request processing, tracing an external order to its resulting items and responses, or building operational reports over shipping request volume. A typical join retrieves the control header with its dependent item rows:

• SELECT rc.REQUEST_CONTROL_ID, rc.ORDER_NUMBER, i.* FROM WSH_ITM_REQUEST_CONTROL rc JOIN WSH_ITM_ITEMS i ON i.REQUEST_CONTROL_ID = rc.REQUEST_CONTROL_ID WHERE rc.PROCESS_FLAG = 'Y';
• Joining to WSH_ITM_RESPONSE_HEADERS on REQUEST_CONTROL_ID to inspect response outcomes for a given request header.
• Joining to FND_APPLICATION on APPLICATION_ID to identify which source application submitted the request.
• Filtering by TRANSACTION_DATE or REQUEST_DATE to audit request throughput over a period.

Reporting use cases include reconciliation of original system references against order numbers, analysis of shipping method and freight term distribution, and validation of pricing transmitted in requests.

Related Objects

The object participates in a well-defined referential network. Its own foreign keys point outward to FND_APPLICATION via APPLICATION_ID, to WSH_ITM_RESPONSE_HEADERS via RESPONSE_HEADER_ID, and to PN_PAYMENT_TERMS_ALL via PAYMENT_TERM_ID. Tables that reference this table through REQUEST_CONTROL_ID include WSH_ITM_ITEMS, WSH_ITM_RESPONSE_HEADERS, WSH_ITM_PARTIES, and XLA_UPGRADE_REQUESTS. Together these relationships establish WSH_ITM_REQUEST_CONTROL as the central request hub for ITM processing within Shipping Execution, with item, response, and party tables functioning as dependent detail and link structures.