EWM Shipping Cockpit Planning and Execution: Overview

  • by Hein Botha, SAP SCM EWM Consultant, Argon Supply Chain Solutions
  • David Webb, SAP SCM Architect, Argon Supply Chain Solutions
  • April 16, 2015
Learn how to configure and transact with the Shipping Cockpit Framework in SAP Extended Warehouse Management (EWM) 9.1, starting with the planning stages (Shipping Cockpit Planning [SCOP]) through execution and monitoring (Shipping Cockpit Execution [SCOE]) in the outbound processes of your warehouse operation.
Learning Objectives

After reading this article, you’ll know how to:

  • Set up the shipping cockpit
  • Understand the differences between Shipping Cockpit Planning (SCOP) and Shipping Cockpit Execution (SCOE)
  • Process an outbound order through SCOP and SCOE
Key Concept
The Shipping Cockpit provides a single view in which the warehouse or shipping operators can plan, track, and manage the outbound delivery processes across the different outbound functions; for example, transport planning, picking, packing, staging, loading, all the way through to goods issue and vehicle departure from the yard. It also monitors shipment plans that have been interfaced from SAP Transportation Management (SAP TM) or external transport planning systems as well.
With the ever-changing demands of a supply chain and the software it uses, plus functionality that must be robust, user friendly, adaptive and efficient, it became necessary for a one-stop cockpit in which the outbound processes of your warehouse could be planned, executed, and monitored in an effective and easy-to-use manner.

We are sharing information about this functionality, for we believe it adds value in the outbound logistics area of a warehouse that uses SAP Extended Warehouse Management (EWM). If you browse the Internet, you will find some documentation mentioning the Shipping Cockpit at a high level of detail, but through this article we hope that you will see the simplicity and business benefit from a functionality perspective when you include it in your business processes. We also include some comments from a client for which we implemented the SCOP and SCOE functionality in the "Customer Testimony" sidebar.
Shipping Cockpit Planning (SCOP) and Shipping Cockpit Execution (SCOE) form part of the Shipping and Receiving area of SAP EWM. The Shipping Cockpit was introduced to fill a gap in the outbound planning and execution processes of the EWM system. This functionality was developed in earlier EWM releases by users as custom development in their existing EWM landscapes. These custom developments added extra cost and risk to their EWM implementations.

The Shipping Cockpit exists of two main transactions: The first is the planning side of the transportation functions (SCOP) and the other is the execution side (SCOE) of the plan. These are native EWM functions and executable inside the SAP NetWeaver Business Client (NWBC) as two separate transactions. This functionality is available from EWM 9.1 and requires other component releases equal to or higher including:

•    SAP NetWeaver 7.40
•    NWBC 4.0
•    SAPGUI 7.30

The main advantage of the SCOP and SCOE is that they are developed and maintained by SAP, and hence are tightly integrated with the rest of the EWM outbound functionality — for example, delivery statuses, wave management, the picking and packing progress, transportation unit management, loading, and goods issue status. All of these integration points are connected to one area in which you can manage the shipping processes.

Some Setup Tips and Tricks of the Shipping Cockpit

The transactions for the SCOP and SCOE are based on the NWBC platform and can be seen under the Shipping and Receiving node from a NWBC logon session (Figure 1).

Figure 1
NWBC Extended Warehouse Management menu and placing of the SCOP and SCOE

Hein Botha

Hein Botha is an SAP SCM EWM consultant at Argon Supply Chain Solutions. Hein has been involved with SAP since 2000 and operates from 2012 in the extended warehouse management (EWM) area as an SCM-EWM consultant. He has played integral roles in numerous ECC and EWM implementations on all levels for implementation projects across logistical areas. These projects covered the fast-moving consumer goods (FMCG) and chemicals industries, nationally and internationally. He has presented a WM/TRM and voice- picking solution at an SCM conference held in Paris in 2011. He considers this presentation one of the success stories of his career.

See more by this author

David Webb

David Webb is an SAP SCM architect at Argon Supply Chain Solutions. David is an experienced SAP supply chain solution architect with industry experience covering the retail, fast-moving consumer goods (FMCG), electronics and motor manufacturing sectors. He has more than 16 years of SAP design, configuration, and technical experience delivering solutions on both the SAP ERP and SCM platforms. He has designed, configured, and delivered solutions for clients all over the globe catering for numerous industry verticals, covering vast amounts of functionality integrated with warehousing and transportation. Along with his SAP experience, David also has a comprehensive grasp of the retail supply chain execution processes and its components. He has a proven track record through all life-cycle phases of SAP implementations. He is well respected by his colleagues for his deep and broad SAP knowledge, problem solving capabilities, positive attitude, commitment and motivation. He thrives under pressure.



See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.