Search Results wsh_document_instances




The WSH_DOCUMENT_INSTANCES table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical data structure within the Oracle Shipping Execution module. It serves as a repository for tracking document instances associated with shipping transactions, ensuring proper documentation and compliance throughout the logistics process. This table is part of the broader Oracle Shipping Execution architecture, which integrates with other EBS modules like Order Management, Inventory, and Purchasing to facilitate end-to-end shipping operations.

Purpose and Functionality

The primary purpose of WSH_DOCUMENT_INSTANCES is to store metadata and references to shipping-related documents, such as bills of lading, packing slips, commercial invoices, and customs documentation. Each record in this table represents a unique instance of a document linked to a specific shipping transaction. The table acts as a bridge between shipping documents and their corresponding delivery or shipment records, enabling traceability and auditability.

Key Columns and Relationships

The table includes several important columns:
  • DOCUMENT_INSTANCE_ID: Primary key identifier for each document instance.
  • DOCUMENT_ID: References the document type from WSH_DOCUMENTS.
  • DELIVERY_ID: Links to the delivery record in WSH_DELIVERIES.
  • SHIPMENT_ID: Associates the document with a shipment in WSH_NEW_DELIVERIES.
  • DOCUMENT_STATUS: Indicates the current status (e.g., 'PRINTED', 'SENT', 'ARCHIVED').
  • CREATION_DATE and LAST_UPDATE_DATE: Track document lifecycle timestamps.
The table maintains foreign key relationships with:
  • WSH_DOCUMENTS (defines document types)
  • WSH_DELIVERIES (core delivery records)
  • WSH_NEW_DELIVERIES (shipment information)

Integration Points

WSH_DOCUMENT_INSTANCES integrates with multiple EBS components:
  1. Order Management: Shipping documents reference sales orders.
  2. Inventory: Packing slips reflect inventory movements.
  3. Accounts Receivable: Invoices generated from shipping documents.
  4. Customs Compliance: Stores export/import documentation.

Business Process Flow

The typical document lifecycle involves:
  1. Document creation when a delivery is confirmed
  2. Status updates as documents are processed
  3. Archival or purging based on retention policies

Technical Considerations

Key technical aspects include:
  • Indexes on frequently queried columns (DELIVERY_ID, SHIPMENT_ID)
  • Triggers for status change validation
  • Concurrent programs for document purge operations
  • API interfaces (WSH_DOCUMENTS_PUB) for programmatic access

Customization and Extensions

Common extensions include:
  • Adding custom document types
  • Extending status values
  • Integrating with third-party document management systems
  • Creating custom reports on document history

Performance Implications

The table can grow significantly in high-volume shipping environments. Recommended maintenance includes:
  • Regular purging of obsolete records
  • Partitioning strategies for large implementations
  • Materialized views for reporting
In summary, WSH_DOCUMENT_INSTANCES provides the foundational structure for managing shipping documentation in Oracle EBS, supporting compliance, traceability, and operational efficiency in logistics processes. Its proper configuration and maintenance are essential for organizations with complex shipping requirements.