Results for “hz_location_id”

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

Overview

WSH_ITM_PARTIES is a Shipping Execution (WSH) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the party-level records belonging to an Integration Transaction Manager (ITM) scan request. The ITM Adapter is Oracle's integration framework for transmitting shipping-related party, address, and contact data to external trading partners or regulatory systems. Every execution of the adapter is initiated by inserting a controlling row into WSH_ITM_REQUEST_CONTROL; the individual parties that must be scanned and transmitted as part of that request are then populated into WSH_ITM_PARTIES. The table is therefore the detail-level staging repository for outbound party data, one row per party per request.

The documented physical schema lists 89 columns owned by the WSH schema. The heuristic Data Vault classification mined from the foreign-key structure is hub-leaning. In Data Vault terms, this suggests modeling WSH_ITM_PARTIES as a hub keyed on PARTY_ID, with REQUEST_CONTROL_ID acting as a link back to the request control object, and the numerous descriptive attributes (address, contact, HZ-mirrored fields) treated as satellite content.

Key Information Stored

The primary key is defined by the constraint WSH_ITM_PARTIES_PK on the PARTY_ID column, and the unique index WSH_ITM_PARTIES_U1 also covers PARTY_ID, making it the single business-key candidate. Most other columns hold descriptive, non-unique data. The most significant columns include:

• PARTY_ID – Surrogate primary key uniquely identifying each party row within a request.
• REQUEST_CONTROL_ID – Foreign key to WSH_ITM_REQUEST_CONTROL, tying the party to its parent scan request.
• ORIGINAL_SYSTEM_REFERENCE and ORIGINAL_SYSTEM_LINE_REFERENCE – Source system identifiers for traceability back to the originating transaction.
• SOURCE_ORG_ID – Operating unit or organization context of the scan.
• PARTY_TYPE and PARTY_NAME – Classification and display name of the party.
• PARTY_ADDRESS1 through PARTY_ADDRESS5, PARTY_CITY, PARTY_STATE, PARTY_COUNTRY_CODE, POSTAL_CODE – Party address detail.
• CONTACT_NAME, PHONE, EMAIL, FAX, WEB – Contact information.
• HZ_PARTY_ID and HZ_PARTY_NUMBER – Links to the TCA (Trading Community Architecture) party model.
• CUST_SITE_USE_ID – Customer site-use reference for the party.
• ACCOUNT_NAME, ACCOUNT_NUMBER, TAX_REFERENCE – Financial and tax identifiers.
• ATTRIBUTE1_NAME through ATTRIBUTE15_NAME and corresponding ATTRIBUTE1_VALUE through ATTRIBUTE15_VALUE – A flexible, 15-slot descriptive flexfield-style extensibility mechanism for partner-specific attributes.

Common Use Cases and Queries

Typical uses include auditing which parties were submitted in a given ITM request, reconciling successful transmissions against response lines, and reporting duplicate or missing party data across requests. A representative query joins the party records to their controlling request:

• SELECT p.PARTY_ID, p.PARTY_NAME, p.HZ_PARTY_NUMBER, p.PARTY_CITY, p.POSTAL_CODE FROM WSH.WSH_ITM_PARTIES p WHERE p.REQUEST_CONTROL_ID = :request_id; – retrieves all parties for one scan request.
• Join to response lines to confirm which parties were acknowledged: SELECT p.PARTY_ID, r.RESPONSE_LINE_ID FROM WSH_ITM_PARTIES p, WSH_ITM_RESPONSE_LINES r WHERE r.PARTY_ID = p.PARTY_ID;
• Join to WSH_ITM_REQUEST_CONTROL on REQUEST_CONTROL_ID to filter by request status or creation date for operational monitoring dashboards.

Related Objects

The FK metadata identifies two direct relationships, and by extension the parent TCA and shipping objects are relevant:

• WSH_ITM_REQUEST_CONTROL – Parent table; WSH_ITM_PARTIES.REQUEST_CONTROL_ID references it.
• WSH_ITM_RESPONSE_LINES – Child table; WSH_ITM_RESPONSE_LINES.PARTY_ID references WSH_ITM_PARTIES.PARTY_ID, capturing adapter responses per party.
• HZ_PARTIES / HZ_PARTY_SITES / HZ_LOCATIONS – TCA reference tables mirrored through HZ_PARTY_ID, HZ_LOCATION_ID, and the HZ_* address columns.
• HZ_CUST_ACCOUNTS / HZ_CUST_SITE_USES_ALL – Source of CUST_SITE_USE_ID, ACCOUNT_NAME, and ACCOUNT_NUMBER.