Results for “wsh_itm_items”

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

Overview

WSH_ITM_ITEMS is a Shipping Execution (WSH) table that stores item information required for license determination within Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the staging and reference structure through which shipping transactions submit item-level details to the ITM Adapter, the integration point responsible for import/export license screening and compliance validation. When a transaction requires license determination, a control row is created in WSH_ITM_REQUEST_CONTROL, and every item participating in that transaction must be populated into WSH_ITM_ITEMS. This table therefore acts as the item manifest for a single license-determination request.

The table is owned by the WSH schema, is marked VALID, and exposes 65 documented columns in the 12.2.2 physical schema. Its primary key is WSH_ITM_ITEMS_PK, defined on ITEM_ID. Based on the foreign key topology mined from the ETRM metadata, the object exhibits a satellite-leaning Data Vault classification: it carries descriptive, request-scoped attributes keyed to a parent request, rather than serving as a pure hub or a many-to-many link. This classification is a heuristic modeling suggestion derived from the FK structure and should be validated against the specific integration design in use.

Key Information Stored

The surrogate primary key is ITEM_ID, enforced by WSH_ITM_ITEMS_PK. The principal foreign key is REQUEST_CONTROL_ID, which links each item row to its parent license-determination request in WSH_ITM_REQUEST_CONTROL; together these form the core business relationship of the table. The most operationally significant columns include:

• ITEM_ID – surrogate primary key and the column referenced by downstream response lines.
• REQUEST_CONTROL_ID – foreign key to WSH_ITM_REQUEST_CONTROL, identifying the parent request.
• INVENTORY_ITEM_ID and ORGANIZATION_ID – the actual inventory item and the inventory organization context.
• SRC_ORGANIZATION_ID and ORGANIZATION_CODE – source organization identifiers used for shipment origin tracking.
• ORIGINAL_SYSTEM_REFERENCE and ORIGINAL_SYSTEM_LINE_REFERENCE – external system keys that tie the item row back to the originating transaction line.
• PRODUCT_CODE, DESCRIPTION, LONG_DESCRIPTION – product identification and descriptive text used in screening.
• CLASSIFIER_TYPE, CLASSIFIER_LABEL, CLASSIFICATION_TYPE, CLASSIFICATION_LABEL – classification metadata for license logic.
• ITEM_VALUE, INCOMING_CURRENCY, INCO_TERM – commercial value, currency, and Incoterms required for export control evaluation.
• END_USE_TYPE, MILITARY_ENDUSER, NON_US_GOVT, END_USER_CERT – end-use and end-user compliance attributes.
• ENC_MASSMARKET, ENC_PUBLIC, ENC_TYPE – encryption classification flags.
• HAZARD_CLASS, ITEM_TYPE, UNIT_OF_MEASURE, COUNTRY – handling and shipment-level attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard audit columns.
• ATTRIBUTE1_NAME through ATTRIBUTE15_NAME and ATTRIBUTE1_VALUE through ATTRIBUTE15_VALUE – the flexible attribute framework allowing extensible, configurable screening fields.

Common Use Cases and Queries

Typical uses include troubleshooting stalled license determinations, reconciling submitted items against responses, and building compliance reporting extracts. A common pattern joins items to their parent request to review all items for a given request:

• Request review: SELECT i.ITEM_ID, i.PRODUCT_CODE, i.ORGANIZATION_CODE FROM WSH_ITM_ITEMS i WHERE i.REQUEST_CONTROL_ID = :request_id;
• Response reconciliation: join WSH_ITM_ITEMS to WSH_ITM_RESPONSE_LINES on ITEM_ID to confirm each submitted item received a screening outcome.
• Screening accuracy audits: filter by COUNTRY, END_USE_TYPE, or MILITARY_ENDUSER to identify high-risk submissions and verify the correct compliance flags were populated.
• Integration diagnostics: detect missing items by comparing expected shipped quantities against rows staged in this table for the corresponding request control record.

Related Objects

The most significant relationship is to the objects that define the license-determination lifecycle:

• WSH_ITM_REQUEST_CONTROL – parent request table; joined via WSH_ITM_ITEMS.REQUEST_CONTROL_ID. Provides request-level context for each item.
• WSH_ITM_RESPONSE_LINES – response detail table; references WSH_ITM_ITEMS via WSH_ITM_RESPONSE_LINES.ITEM_ID. Holds the ITM Adapter's screening results per item.
• INVENTORY_ITEM_ID (MTL_SYSTEM_ITEMS_B) – the underlying item master, used to enrich staged rows with item definitions.
• ORGANIZATION_ID (HR_ALL_ORGANIZATION_UNITS / MTL_PARAMETERS) – resolves the inventory and operating unit context referenced on the item row.

Because WSH_ITM_ITEMS is an internal staging structure for the ITM Adapter integration, it should be treated as reference/diagnostic data rather than a primary transactional source. Direct DML is not recommended; submissions should flow through the standard Shipping Execution license-determination process that manages WSH_ITM_REQUEST_CONTROL and WSH_ITM_ITEMS together.