Search Results hz

The WSH.WSH_ITM_PARTY_CONTACTS table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical data structure within the Shipping Execution module. It serves as a junction table that establishes relationships between item parties (shipping entities) and their associated contact information, enabling comprehensive tracking and communication capabilities throughout the shipping lifecycle. This table plays a pivotal role in maintaining the complex web of relationships between trading partners, carriers, and other logistics stakeholders.

Table Structure and Key Columns

The table's primary columns include:

• ITEM_PARTY_CONTACT_ID: Primary key identifier
• ITEM_PARTY_ID: Foreign key reference to WSH_ITEM_PARTIES
• CONTACT_ID: Foreign key to HZ_CONTACT_POINTS in Trading Community Architecture
• PRIMARY_FLAG: Indicates if this is the primary contact
• STATUS: Active/inactive status of the relationship
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY: Standard Oracle audit columns

Functional Integration

The table integrates with multiple EBS modules:

1. Trading Community Architecture (TCA): Links to HZ_CONTACT_POINTS for contact details
2. Order Management: Provides shipping contact information for order fulfillment
3. Logistics: Enables carrier communication during shipment execution

Business Process Context

WSH_ITM_PARTY_CONTACTS supports critical shipping processes:

• Automated shipment notifications to designated contacts
• Carrier communication management
• Exception handling with responsible parties
• Multi-party shipping coordination

Technical Implementation

The table is maintained through:

• Shipping Execution APIs (WSH_ITM_PARTIES_PUB)
• Oracle Forms in the Shipping Transaction Manager
• PL/SQL packages in the shipping module

Data Relationships

Key foreign key relationships exist with:

• WSH_ITEM_PARTIES (shipping party details)
• HZ_CONTACT_POINTS (contact information)
• WSH_DELIVERY_DETAILS (shipment items)

Customization Considerations

Common extension scenarios include:

• Adding custom contact attributes through descriptive flexfields
• Extending contact validation logic
• Integrating with external contact management systems

Performance Implications

The table should be indexed on:

• ITEM_PARTY_ID for party-based queries
• CONTACT_ID for contact-based lookups
• Composite index on status fields for active record retrieval

Upgrade Impact

Between 12.1.1 and 12.2.2, the table structure remained stable, but underlying TCA integration was enhanced in 12.2.2 to support additional contact point types and validation rules.

Security Model

Access is controlled through:

• Oracle function security
• Data security rules in TCA
• Shipping responsibility restrictions

This table represents a critical integration point between Oracle's shipping functionality and the broader trading partner ecosystem, enabling sophisticated supply chain communication capabilities while maintaining data integrity across the EBS architecture.