Search Results wsh_bols_rd_v

DeepSeek eTRM - WSH Tables and Views in Oracle EBS 12.1.1/12.2.2

The Oracle E-Business Suite (EBS) Shipping Execution module relies on a structured database schema to manage shipping transactions, tracking, and logistics. The DeepSeek Electronic Technical Reference Manual (eTRM) provides comprehensive documentation on the underlying tables and views associated with the WSH (Shipping) module in Oracle EBS 12.1.1 and 12.2.2. This summary outlines the key tables, views, and their functional significance in the shipping process.

Core WSH Tables

The WSH module's database schema consists of several critical tables:

WSH_DELIVERIES: Stores delivery header information, including delivery IDs, statuses, and dates. This is the primary table for tracking shipments.
WSH_DELIVERY_DETAILS: Contains line-level details of deliveries, such as item quantities, weights, and references to sales orders or inventory moves.
WSH_TRIPS: Manages trip records, which group multiple deliveries for consolidated shipping.
WSH_TRIP_STOPS: Tracks stops (pickup/drop-off locations) associated with trips.
WSH_CARRIERS: Stores carrier information, including names, service levels, and tracking methods.
WSH_FREIGHT_COSTS: Captures freight charges and billing details for shipments.

Key WSH Views

Oracle EBS provides views to simplify reporting and integration:

WSH_DELIVERIES_V: A comprehensive view combining delivery headers with related attributes.
WSH_DELIVERY_DETAILS_V: Aggregates delivery line details with item and order information.
WSH_TRIPS_V: Enhances trip data with carrier and stop details for logistics planning.
WSH_FREIGHT_CHARGES_V: Facilitates freight cost analysis by joining cost tables with delivery data.

Functional Workflow

The WSH tables support end-to-end shipping operations:

Order Fulfillment: Sales orders or inventory transfers trigger delivery creation in WSH_DELIVERIES and WSH_DELIVERY_DETAILS.
Consolidation: Deliveries are grouped into trips (WSH_TRIPS) with defined stops (WSH_TRIP_STOPS).
Carrier Assignment: WSH_CARRIERS links shipments to logistics providers.
Freight Calculation: WSH_FREIGHT_COSTS records shipping expenses for invoicing.
Tracking: Status updates propagate through tables, enabling real-time visibility.

Integration Points

WSH tables interface with other EBS modules:

Order Management (OM): WSH_DELIVERY_DETAILS references OE_ORDER_LINES_ALL.

Inventory (INV)

MTL_MATERIAL_TRANSACTIONS

Receivables (AR): Freight costs integrate with RA_CUSTOMER_TRX_ALL for billing.

Conclusion

The DeepSeek eTRM for WSH tables and views in Oracle EBS 12.1.1/12.2.2 provides a foundational blueprint for shipping execution. By leveraging these structures, organizations can automate logistics, improve shipment visibility, and ensure seamless integration with supply chain and financial processes. Understanding these tables is essential for custom reporting, performance tuning, and extending shipping functionality.

View: WSH_BOLS_RD_V 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:WSH.WSH_BOLS_RD_V, object_name:WSH_BOLS_RD_V, status:VALID, product: WSH - Shipping Execution , implementation_dba_data: APPS.WSH_BOLS_RD_V ,
View: WSH_BOLS_RD_V 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:WSH.WSH_BOLS_RD_V, object_name:WSH_BOLS_RD_V, status:VALID, product: WSH - Shipping Execution , implementation_dba_data: APPS.WSH_BOLS_RD_V ,
APPS.FTE_TRACKING_WRAPPER dependencies on WSH_BOLS_RD_V 12.1.1
APPS.FTE_TRACKING_WRAPPER dependencies on WSH_BOLS_RD_V 12.2.2
APPS.FTE_TRACKING_WRAPPER dependencies on WSH_TRIPS 12.2.2
APPS.FTE_TRACKING_WRAPPER dependencies on WSH_NEW_DELIVERIES 12.1.1
APPS.FTE_TRACKING_WRAPPER dependencies on WSH_TRIP_STOPS 12.2.2
APPS.FTE_TRACKING_WRAPPER dependencies on WSH_TRIP_STOPS 12.1.1
APPS.FTE_TRACKING_WRAPPER dependencies on WSH_TRIPS 12.1.1
APPS.FTE_TRACKING_WRAPPER dependencies on WSH_NEW_DELIVERIES 12.2.2
APPS.FTE_TRACKING_WRAPPER dependencies on WSH_DELIVERY_LEGS 12.1.1
PACKAGE BODY: APPS.FTE_TRACKING_WRAPPER 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FTE_TRACKING_WRAPPER, status:VALID,
SYNONYM: APPS.WSH_DOCUMENT_INSTANCES 12.1.1
owner:APPS, object_type:SYNONYM, object_name:WSH_DOCUMENT_INSTANCES, status:VALID,
SYNONYM: APPS.WSH_DOCUMENT_INSTANCES 12.2.2
owner:APPS, object_type:SYNONYM, object_name:WSH_DOCUMENT_INSTANCES, status:VALID,
APPS.FTE_TRACKING_WRAPPER dependencies on WSH_DELIVERY_LEGS 12.2.2
PACKAGE BODY: APPS.FTE_TRACKING_WRAPPER 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FTE_TRACKING_WRAPPER, status:VALID,
12.2.2 DBA Data 12.2.2
12.1.1 DBA Data 12.1.1
12.1.1 FND Design Data 12.1.1
12.2.2 FND Design Data 12.2.2
SYNONYM: APPS.WSH_LOCATIONS 12.2.2
owner:APPS, object_type:SYNONYM, object_name:WSH_LOCATIONS, status:VALID,
SYNONYM: APPS.WSH_LOCATIONS 12.1.1
owner:APPS, object_type:SYNONYM, object_name:WSH_LOCATIONS, status:VALID,
SYNONYM: APPS.WSH_TRIPS 12.1.1
owner:APPS, object_type:SYNONYM, object_name:WSH_TRIPS, status:VALID,
SYNONYM: APPS.WSH_TRIPS 12.2.2
owner:APPS, object_type:SYNONYM, object_name:WSH_TRIPS, status:VALID,
VIEW: APPS.WSH_BOLS_RD_V 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:WSH.WSH_BOLS_RD_V, object_name:WSH_BOLS_RD_V, status:VALID,
VIEW: APPS.WSH_BOLS_RD_V 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:WSH.WSH_BOLS_RD_V, object_name:WSH_BOLS_RD_V, status:VALID,
SYNONYM: APPS.WSH_TRIP_STOPS 12.2.2
owner:APPS, object_type:SYNONYM, object_name:WSH_TRIP_STOPS, status:VALID,
SYNONYM: APPS.WSH_DELIVERY_LEGS 12.2.2
owner:APPS, object_type:SYNONYM, object_name:WSH_DELIVERY_LEGS, status:VALID,
SYNONYM: APPS.WSH_DELIVERY_LEGS 12.1.1
owner:APPS, object_type:SYNONYM, object_name:WSH_DELIVERY_LEGS, status:VALID,
SYNONYM: APPS.WSH_TRIP_STOPS 12.1.1
owner:APPS, object_type:SYNONYM, object_name:WSH_TRIP_STOPS, status:VALID,
SYNONYM: APPS.WSH_NEW_DELIVERIES 12.1.1
owner:APPS, object_type:SYNONYM, object_name:WSH_NEW_DELIVERIES, status:VALID,
SYNONYM: APPS.WSH_NEW_DELIVERIES 12.2.2
owner:APPS, object_type:SYNONYM, object_name:WSH_NEW_DELIVERIES, status:VALID,
PACKAGE: APPS.HR_SECURITY 12.1.1
owner:APPS, object_type:PACKAGE, object_name:HR_SECURITY, status:VALID,
PACKAGE: APPS.HR_SECURITY 12.2.2
owner:APPS, object_type:PACKAGE, object_name:HR_SECURITY, status:VALID,
APPS.FTE_TRACKING_WRAPPER SQL Statements 12.1.1
APPS.FTE_TRACKING_WRAPPER SQL Statements 12.2.2
VIEW: APPS.PO_VENDORS 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.PO_VENDORS, object_name:PO_VENDORS, status:VALID,
SYNONYM: APPS.HZ_CUST_ACCOUNTS 12.1.1
owner:APPS, object_type:SYNONYM, object_name:HZ_CUST_ACCOUNTS, status:VALID,
VIEW: APPS.HR_ORGANIZATION_UNITS 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PER.HR_ORGANIZATION_UNITS, object_name:HR_ORGANIZATION_UNITS, status:VALID,
VIEW: APPS.HR_ORGANIZATION_UNITS 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PER.HR_ORGANIZATION_UNITS, object_name:HR_ORGANIZATION_UNITS, status:VALID,
SYNONYM: APPS.HZ_CUST_ACCOUNTS 12.2.2
owner:APPS, object_type:SYNONYM, object_name:HZ_CUST_ACCOUNTS, status:VALID,
SYNONYM: APPS.HZ_PARTIES 12.2.2
owner:APPS, object_type:SYNONYM, object_name:HZ_PARTIES, status:VALID,
PACKAGE BODY: APPS.FTE_TRACKING_WRAPPER 12.1.1
PACKAGE BODY: APPS.FTE_TRACKING_WRAPPER 12.2.2
PACKAGE: APPS.HR_GENERAL 12.2.2
owner:APPS, object_type:PACKAGE, object_name:HR_GENERAL, status:VALID,
SYNONYM: APPS.HZ_PARTIES 12.1.1
owner:APPS, object_type:SYNONYM, object_name:HZ_PARTIES, status:VALID,
PACKAGE: APPS.HR_GENERAL 12.1.1
owner:APPS, object_type:PACKAGE, object_name:HR_GENERAL, status:VALID,
eTRM - WSH Tables and Views 12.1.1
description: Stores hierarchy for zones. Each region component of a zone has a record in this table. ,
eTRM - SQLAP Tables and Views 12.2.2
description: Set Distribution Table. ,
eTRM - WSH Tables and Views 12.2.2
description: Stores hierarchy for zones. Each region component of a zone has a record in this table. ,