Loading...

Contact Us
Flag Dropdown Button
India Flag India Qatar Flag Qatar KSA Flag KSA

About GWC –

Delivering Logistic Innovation: GWC (Q.P.S.C.) is the leading provider of logistics and supply chain solutions in the State of Qatar. Established as a Qatari shareholding company in 2004; the company offers the full spectrum of high-quality solutions to a variety of industry verticals.

It has the largest self-contained logistics hub in the State of Qatar, the Logistics Village Qatar.

They are also supporting retail giants in the storage, packaging, and distribution of their product; and providing vital logistics support for nearly every major sporting event in the country.

Introduction –

 

GWC is the 3PL partner of Costa F&B in Qatar. The current process of data exchange between SAP and GWC WMS is manual. There is no direct integration between SAP and GWC system and data gets exchanged via SFTP. Many a times, the GWC team is not able to find the file in SFTP resulting in redundant work.

The project aims to integrate SAP and GWC system through API so that data exchange is automated enabling timely system update resulting in better supply chain operation.

About GWC_WMS_SAP Integration Project: Requirement

 

  • Integrate SAP and GWC WMS through API for faster data interchange so that respective systems is updated on time.
  • Send communication of new article creation in SAP to GWC WMS
  • Send ASN details instead of PO for Inbound Delivery
  • Issue GRN on timely basis
  • Send Outbound Delivery information smoothly
  • Any expiry date update in GWC system to be communicated to SAP
  • Get Updates regarding any article movement in 3PL for Article status change like hold, damage, etc.
  • Update PGI details in SAP on timely basis
  • To get variance report from RAP based on Balance on Hand inventory information sent by GWC
  • To get Email notification against updates in GWC system

Assumptions:

 

  • This integration is for Qatar
  • One time load of Article Master will be through batch process
  • Item must be synchronized with GWC system before PO is created in SAP for that item so that PO/ASN does not get rejected.
  • In Article Master Interface, only new article/SKU will be part of this interface. Any update in existing SKU will work as is via email to GWC.
  • Receipt line no is currently PO line no. When GWC sends back the confirmation. then SAP needs the same line number. The qty might change with same line number and batch number. There might be multiple qty with diff batches for same line number. For same batch number, the expectation is to consolidate the details and send rather than sending separately
  • Quantity filed in GRN file to be a natural number and not a decimal
  • Inbound Interface is all the data coming ‘in’ SAP system from GWC System
  • Outbound Interface is all the data going ‘from’ SAP system to GWC System
  • All control issues related changes in GWC will not be part of integration
  • ASN will be generated in SAP
  • Balance on Hand will be a report generated in RAP (middleware)
  • For Balance on Hand Report, GWC should not consider Articles quantity where GRN is not posted and sent to our system. Also, it should include stock which are in staging area for outbound but Outbound not done.

Process flow:

  • PGI gets generated by GWC after item is shipped from warehouse
  • Store to SAP integration is not part of this integration project.
  • Any excess or extra item identified by GWC during receiving will expect a new PO created in SAP corresponding ASN will be sent to GWC against which this new excess or extra item will be received and mapped
  • For short receiving, there will not be any impact and system should accept as there will be separate column for Ordered Qty and Received Qty in GRN file
  • For any short items picked by GWC for Outbound Delivery, there will not be any impact and system should accept as there will be separate column for Ordered Qty and Picked Qty in PGI file
  • GWC should not pick extra item for Outbound Delivery their system should not accept if picked qty is more than ordered Qty.
  • Store needs to create a new order if they want to increase Qty. No need to create an order if they want less qty than ordered.
  • Inbound and Outbound Report are sent once in a day by GWC via email and will continue to remain AS-IS and there will be no change after API Integration
  • Costa will send 2 UOM to GWC i.e. Master Unit & Secondary Unit along with Conversion details in Article Master and Inbound Delivery (ASN)
  • GWC will not accept any changes in the existing Article
  • Any Update in existing Inbound Delivery will be entertained by GWC
  • Amendment in existing Outbound Delivery cannot be entertained by GWC
  • GWC will issue 1 GRN per ASN to avoid any duplication
  • Outbound Delivery file will also include Shipment Details along with Grouping code number. Start Date for shipment details will be based on Business decision.
  • For Outbound Delivery, Costa will do batch determination based on FIFO and send GWC to pick up the items. GWC may or may not use this batch determination and is free to pick the items based on their own batch determination logic. We need to make sure if GWC changes the batch then our system should get updated automatically using the interface. In future, this batch details will not be sent to GWC
  • For Article Master, the data integration should be based on Site extension. If an SKU is extended to GWC Qatar, it should go to GWC Qatar and not to other 3PL sites.

  • Solution Provided:

    As part of this integration project, we will have both Outbound and Inbound Interfaces. The list of expected interfaces is listed below. Apart from Inbound and Outbound interfaces, the business was expecting Email notification for below transactions to get timely alert.

    • Goods Receipt (GRN)
    • Goods Issue (PGI)
    • Article Movements in 3PL
    • Article Movement in Batch

    These updates will come to middleware and middleware will generate a notification for each of these updates and send to Business.                                             

     

Outbound Interfaces                 

Article Master: Item Master data will be sent by SAP ERP to 3PL through the API with the help of the integration platform. Only new article/SKU will be part of this interface. Any update in existing SKU will work as is via email to GWC.

Inbound Delivery (ASN instead of PO): Inbound Delivery (ASN) along with Item Master data will be sent by SAP ERP through the API. This will include all the Articles expected to be received by 3PL along with quantity. The UoM will be in Store Issue Unit (Distribution Unit).

 This interface will also take care of:

  • Store Returns Process which will be Inbound for 3PL
  • Stock Transfer from warehouse to warehouse will be Inbound for one

Outbound Delivery: Outbound Delivery will be sent to SAP ERP through the API with the help of Integration platform. This would be considered as Out- document /

Pick Note in WMS.

This will cover Store Orders for delivery as well as Supplier Returns which needs to be sent from 3PL. This API Integration will also include shipment details.

This interface will also take care of:

  • Supplier Returns which will be Outbound for 3PL
  • Stock Transfer from Warehouse to Warehouse will be Outbound for one

Inbound Interface:

Goods Receipt (GRN): The GRN against Inbound Delivery will be sent to SAP ERP. Below would the interface layout need to be developed and hosted by the Integration Platform team which would be consumed by WMS to send the data.

Goods Issue (PGI): The Post Goods Issue details against Outbound Delivery will be sent to SAP ERP through the API. Below would be the interface layout that

needs to be developed and hosted by the Integration Platform which would be consumed by WMS to send the interface layout the data.

Article Movement in 3PL (Within Warehouse): This is SKU movement within the same warehouse. Ex- If an item gets damaged after receiving then the SKU will be moved to

Inbound Interface:

Goods Receipt (GRN): The GRN against Inbound Delivery will be sent to SAP ERP. Below would the interface layout need to be developed and hosted by the Integration Platform team which would be consumed by WMS to send the data.

Goods Issue (PGI): The Post Goods Issue details against Outbound Delivery will be sent to SAP ERP through the API. Below would be the interface layout that

needs to be developed and hosted by the Integration Platform which would be consumed by WMS to send the interface layout the data.

Article Movement in 3PL (Within Warehouse): This is SKU movement within the same warehouse. Ex- If an item gets damaged after receiving then the SKU will be moved to

Integration was done using Middleware PI/PO – SOAP Synchronous API’s

Scroll to Top