CUSTOMER STORY • LOGISTICS & SAP INTEGRATION
GWC WMS SAP Integration for Automated 3PL Operations
A modern SAP-to-WMS integration story for Costa F&B Qatar, connecting SAP ERP, GWC warehouse operations and PI/PO middleware through APIs to reduce manual SFTP dependency and improve timely supply-chain updates.
ABOUT GWC & PROJECT CONTEXT
From Manual File Exchange to API-Driven Warehouse Integration
GWC is a leading logistics and supply-chain solutions provider in Qatar. For Costa F&B operations, the earlier SAP and GWC WMS data exchange depended on manual SFTP-based file movement. This created avoidable tracking effort, delays and duplicate follow-ups when warehouse files were not visible on time.
The objective was to automate the exchange of article, ASN, GRN, PGI, movement and inventory information between SAP and GWC WMS through API-based integration.
- Qatar-focused 3PL warehouse integration scope
- Automated SAP ERP and GWC WMS data exchange
- Reduced manual SFTP dependency and follow-up effort
- Timely operational updates for supply-chain execution
PROJECT REQUIREMENT
What the SAP–WMS Integration Needed to Achieve
The integration needed to create a reliable digital bridge between SAP ERP and GWC WMS, enabling faster data interchange, cleaner warehouse execution and timely updates across inbound, outbound, inventory and exception processes.
Article Master Sync
Send new article/SKU creation details from SAP to GWC WMS so warehouse master data is available before transactional activity starts.
ASN-Based Inbound
Send Advanced Shipping Notice details instead of PO information for inbound delivery, including item and quantity details.
GRN, PGI & Delivery Updates
Receive timely GRN and PGI updates and send outbound delivery information smoothly between systems.
Inventory & Movement Visibility
Capture expiry updates, article movements, hold/damage status changes and balance-on-hand reporting through the integration layer.
SCOPE & ASSUMPTIONS
Clear Boundaries for SAP, GWC WMS and Middleware
The project scope was structured around Qatar operations, defined inbound/outbound ownership and controlled interface behavior so SAP, WMS and middleware could exchange operational data without creating process ambiguity.
- Integration scope focused on Qatar operations
- One-time Article Master load handled through batch process
- SKU synchronization required before PO/ASN creation
- Only new article/SKU data included in the Article Master interface
- ASN generated in SAP and sent to GWC WMS
- Inbound means data coming into SAP from GWC WMS
- Outbound means data going from SAP to GWC WMS
- Balance on Hand report generated in middleware/RAP
- Control-issue changes in GWC excluded from integration scope
PROCESS FLOW
End-to-End Data Movement Across SAP, Middleware and GWC WMS
The designed flow connects inbound delivery, warehouse receiving, goods receipt, outbound delivery, picking, PGI, article movement and balance-on-hand updates. The integration supports operational exceptions such as short receiving, picked quantity differences, batch changes and warehouse-to-warehouse movements within agreed business rules.
- GWC generates PGI after items are shipped from warehouse
- Short receiving handled through ordered vs received quantity columns
- Short picking handled through ordered vs picked quantity columns
- GWC should not pick extra quantity above ordered quantity
- Warehouse reports continue as once-daily email reports where required
- Article data routed based on site extension for GWC Qatar
INTERFACE ARCHITECTURE
Outbound, Inbound & Notification Interfaces
Outbound Interfaces
- Article Master: new item/SKU data from SAP ERP to 3PL via API
- Inbound Delivery / ASN: articles and expected receipt quantity sent to GWC WMS
- Outbound Delivery: pick-note style delivery data sent through integration platform
- Store returns and warehouse-to-warehouse stock transfer scenarios supported
Inbound Interfaces
- Goods Receipt / GRN confirmation consumed by SAP ERP
- Post Goods Issue / PGI details sent back against outbound delivery
- Article movement within 3PL for hold, damage and warehouse status changes
- Balance on Hand and batch movement updates used for variance visibility
Middleware Notifications
- GRN update alerts
- PGI update alerts
- Article movement alerts
- Batch movement alerts
SAP PI/PO MIDDLEWARE
SOAP Synchronous APIs Connecting SAP ERP and External WMS
The integration was implemented using SAP PI/PO middleware with SOAP synchronous APIs. SAP ERP communicates through ABAP proxy and XI protocol, while the external WMS communicates through SOAP protocol, allowing request-response communication between the enterprise and warehouse systems.
SAP ERP System
Source and destination for enterprise article, ASN, GRN, PGI, inventory and warehouse movement data.
SAP PI/PO Middleware
Central integration layer used for API orchestration, message handling and synchronous request-response exchange.
External GWC WMS
Warehouse execution system exchanging receiving, issue, movement and balance-on-hand updates.
Business Notifications
Middleware-driven email notifications for GRN, PGI, article movement and batch updates.
Need SAP-WMS or 3PL Integration?
Lumbini Elite Solutions helps enterprises connect SAP, warehouse systems, middleware platforms, APIs and operational workflows into reliable digital integration layers for logistics, retail, manufacturing and supply-chain environments.
