TCD Configuration and Process Description

Configuration Script

Transportation Cross-Docking

Version History No

Issued by

Date

0.5

Christian Reinhardt

18.07.2008

0.9

Christian Reinhardt

25.07.2008

1.0

Christian Reinhardt

05.09.2008

Major Changes

Table of Contents 1

Introduction ........................................................................................................................................5

2

Maintaining the necessary Settings for TCD ...................................................................................7 2.1 Transportation Cross-Docking Settings ERP Part...................................................................7 2.1.1 Check Customizing Documentation ................................................................................7 2.1.2

Define Shipping Data for Plants.......................................................................................8

2.1.3

Plant assignment to Vendor..............................................................................................9

2.1.4

Maintain Storage Location .............................................................................................10

2.1.5

Assign warehouse number to plant/storage location ....................................................12

2.1.6

Assign shipping point to plant........................................................................................13

2.1.7

Maintain Storage Locations and Shipping Points for CD Warehouses.......................14

2.1.8

Set Up Partner Determination for Deliveries ................................................................15

2.1.9

Create Event Groups .......................................................................................................18

2.1.10

Maintain Output Types ...................................................................................................19

2.1.11

Maintain Output Determination Procedure ...................................................................21

2.1.12

Assign Output Determination Procedures .....................................................................23

Page 1 of 103

2.1.13

Set QM Check and Delivery Type for Each Movement Type .....................................24

2.1.14

Delivery Type Determination.........................................................................................25

2.1.15

Define Packaging Material Types..................................................................................27

2.1.16

Condition Creation for the Output Processing ..............................................................27

2.2 Transportation Cross-Docking Settings EWM Part ..............................................................29 2.2.1 Activation of BC Sets .....................................................................................................29 2.2.2

Map Storage Locations from ERP System to EWM ....................................................30

2.2.3

Define Partner Roles .......................................................................................................30

2.2.4

Define Date Profiles........................................................................................................32

2.2.5

Map Document Types from ERP System to EWM ......................................................34

2.2.6

Map Item Types from ERP System to EWM................................................................35

2.2.7

Map Partner Roles from ERP System to EWM ............................................................36

2.2.8

Control Message Processing Dependent on Recipient .................................................37

2.2.9

Define Packaging Material Types..................................................................................37

2.2.10

Assign Number Range Intervals to Packaging Material Types ...................................38

2.2.11

Define Hierarchy Structure.............................................................................................39

2.2.12

Maintain Hierarchy .........................................................................................................40

2.2.13

General Settings for Routing Guide...............................................................................42

2.2.14

Assign Number Range Intervals to Packaging Material Types ...................................42

2.2.15

Method Parameter for Each Strategy.............................................................................44

2.2.16

Assignments: Warehouse Number/Business Partners ..................................................45

2.2.17

Maintain Route ................................................................................................................46

2.2.18

Simulate Route Determination .......................................................................................49

2.2.19

Define Storage Types......................................................................................................50

2.2.20

Define Storage Sections..................................................................................................56

2.2.21

Create Storage Bin ..........................................................................................................57

2.2.22

Define Work Center........................................................................................................60

2.2.23

Define Master Data Attributes .......................................................................................63

2.2.24

Define Process-Oriented Storage Control .....................................................................65

Page 2 of 103

3

2.2.25

Define Creation Rule of Warehouse Orders..................................................................68

2.2.26

Define Warehouse Process Type ...................................................................................69

2.2.27

Determine Warehouse Process Type .............................................................................72

Processing Transportation Cross-Docking.....................................................................................73 3.1 ERP Part – First Inbound Delivery.........................................................................................73 3.1.1 Create Material................................................................................................................73 3.1.2

Purchase Order Creation.................................................................................................75

3.1.3

Inbound Delivery Creation .............................................................................................75

3.2 EWM Part – First Inbound Delivery......................................................................................77 3.2.1 Maintain inbound delivery..............................................................................................77 3.3 ERP Part – Starting Outbound Delivery ................................................................................78 3.3.1 Outbound Delivery Creation ..........................................................................................78 3.4 EWM Part – Starting Outbound Delivery..............................................................................80 3.4.1 Maintain Outbound Delivery Order...............................................................................80 3.4.2

Stock Removal for Outbound Delivery Order ..............................................................81

3.4.3

Confirmation of Warehouse Tasks ................................................................................82

3.4.4

Maintain Outbound Delivery Order...............................................................................83

3.5 ERP Part – Delivery Pair in ERP ...........................................................................................85 3.5.1 Outbound Delivery Display............................................................................................85 3.5.2

Transportation Cross-Docking Monitor ........................................................................85

3.6 EWM Part – Cross-Docking Inbound Delivery ....................................................................87 3.6.1 Maintain Inbound Delivery ............................................................................................87 3.7 EWM Part – Cross-Docking Outbound Delivery Order.......................................................91 3.7.1 Maintain Outbound Delivery Order...............................................................................91 3.8 ERP Part – Stock Situation .....................................................................................................94 3.8.1 Stock per Material ...........................................................................................................94 3.9 EWM Part – Cross-Docking Processing................................................................................95 3.9.1 Stock Removal for Outbound Delivery Order ..............................................................95 3.9.2

Confirmation of Warehouse Tasks ................................................................................96

3.9.3

Monitoring of CD-Process in EWM ..............................................................................96

3.9.4

Deconsolidation...............................................................................................................97

3.9.5

Deconsolidation...............................................................................................................98

Page 3 of 103

3.9.6

Maintain Outbound Delivery Order.............................................................................100

3.10 ERP Part – Outbound Delivery ............................................................................................102 3.10.1 Outbound Delivery Display..........................................................................................102 3.10.2

Stock per Material .........................................................................................................102

Page 4 of 103

1 Introduction The following configuration guide is dealing with the customizing of the Transportation CrossDocking (TCD) process. The configuration was done in the P9Q/001 which is a EWM 2007 system installed as add on to an ERP system. However the settings should be compatible to all other possible standard EWM deployments as well as to the previous releases EWM 2007 (5.1) and EWM 5.0. Transportation Cross-Docking is used to send goods from a sending facility not direct to a receiving one but via an intermediate facility. There the goods are cross-docked through the warehouse and send to the next destination. Cross-Docking can happen over multiple steps. In this guide a scenario is shown where the Transportation Cross-Docking is set up as process between warehouse as source and customer as destination. So the customer P9L_CUS_01 orders a product from warehouse LMWH. The product is packed and send, due to the result of the route determination, to the warehouse P9Q1 and then to the customer itself.

Page 5 of 103

Figure 1: Overview of a Stock Transfer Order Process using Transportation Cross-Docking

Page 6 of 103

2 Maintaining the necessary Settings for TCD 2.1

Transportation Cross-Docking Settings ERP Part

2.1.1 Check Customizing Documentation Customizing: SAP Customizing Implementation Guide Parts Management (SPM)

Logistics Execution

Transportation Cross-Docking (SPM)

Service

Basic Settings for

Transportation Cross-Docking

In the ERP customizing (see screenshot) is a complex documentation available that clarifies the main steps that have to be executed when TCD should be set up. Some steps are available in the standard customizing. These steps will not be described in detail here. Only the steps and actions that need to be executed in this special system are mentioned.

Page 7 of 103

Figure 2: Customizing overview for Transportation Cross-Docking in ERP

2.1.2 Define Shipping Data for Plants Customizing: SAP Customizing Implementation Guide Purchasing

Scheduling Agreement

Materials Management

Set up Stock Transport Scheduling Agreement

Define Shipping Data for Plants

In this customizing setting assign the customer to the plant. This needs to be done in order to enable the TCD process. The plant needs a customer assigned.

Page 8 of 103

Figure 3 Assignment of a customer to a plant

2.1.3 Plant assignment to Vendor Application: SAP menu

Logistics

Purchasing

Master Data

Vendor

Central

Change (XK03)

Not only a customer has to be assigned to the plant but also there has to be an assignment between plant and vendor. This assignment is done in the application in the vendor maintenance. In the purchasing data tab there is the possibility to assign via the menu additional data to the vendor like the plant.

Page 9 of 103

Figure 4: Assignment of a vendor to a plant

2.1.4 Maintain Storage Location Customizing: SAP Customizing Implementation Guide Materials Management

Enterprise Structure

Definition

Maintain storage location

Transportation Cross-Docking needs a special storage location to separate the stock to be crossdocked from the normal stock. This storage location is assigned to the sending plant but also to the cross-docking warehouse. Therefore the stock is under the control of the sending plant during the whole cross-docking chain but visible in the different warehouses in the chain. So between the warehouses in the cross-docking chain transfer postings are happening.

Page 10 of 103

Figure 5: Overview about the involved storage locations

For the given scenario the storage location CD1 has been defined to be the cross-docking storage location.

Page 11 of 103

Figure 6: Creation of the Cross-Docking storage location

2.1.5 Assign warehouse number to plant/storage location Customizing: SAP Customizing Implementation Guide Assignment

Logistics Execution


Assign warehouse number to plant/storage location

After the storage location has been defined the warehouse needs to be assigned to the plant/storage location combination. As described above the storage location has to be assigned to the intermediate warehouse that is in the given example the ERP warehouse EWM (warehouse EWM in the ERP is mapped to warehouse P9Q1 for the EWM).

Page 12 of 103

Figure 7: Assignment of a warehouse to a CD storage location

2.1.6 Assign shipping point to plant Customizing: SAP Customizing Implementation Guide Assignment

Logistics Execution


Assign shipping point to plant

In order to send products that are belonging to a plant from a warehouse that is assigned to a different plant, the two different plants need the same shipping point assigned. In the given example the shipping point is 0001.

Page 13 of 103

Figure 8: Assignment of a shipping point to a plant

2.1.7 Maintain Storage Locations and Shipping Points for CD Warehouses Customizing: SAP Customizing Implementation Guide Parts Management (SPM)

Logistics Execution

Transportation Cross-Docking (SPM)

Locations and Shipping Points for CD Warehouses

Page 14 of 103

Service

Maintain Storage

After the definition above has been done the whole chain needs to be modeled in ERP. This is done in this activity. Here it’s defined how the products are transferred. This setting means when sending from P9L1 to P9Q1 use storage location CD1 and shipping point 0001.

Figure 9: Creation of the relationship between the plants and the CD storage locations

2.1.8 Set Up Partner Determination for Deliveries Customizing: SAP Customizing Implementation Guide Basic Shipping Functions

Partners

Logistics Execution

Shipping

Set Up Partner Determination for Deliveries

For TCD special partners are needed in the delivery. These partners are assigned to partner determination procedures in this customizing activity and also it’s determined which delivery types are using the partners. Overall the inbound delivery has to contain two new partner roles for TCD, EC (Receiving CrossDocking Warehouse) and SC (Supplying Cross-Docking Warehouse). Similarly the outbound delivery needs the partner role EC. The partner determination procedures IDCD for cross-docking inbound and ODCD for crossdocking outbound, that contain the partner roles mentioned above, are already delivered as standard customizing. They have to be assigned to delivery types. For the given process, IDCD has been assigned to DIG and ODCD to LO. This means to start a TCD process as set up a LO delivery need to be used. By extending this setting also other delivery types can be enabled for TCD.

Page 15 of 103

Figure 10: Assignment of partners to the CD determination profile

Figure 11: Assignment of partners to the CD outbound determination profile

Page 16 of 103

Figure 12: Assignment of partner determination procedure to delivery type

Page 17 of 103

2.1.9 Create Event Groups Customizing: SAP Customizing Implementation Guide Basic Shipping Functions

Scheduling

Logistics Execution

Additional Deadlines

Shipping

Create Event

Groups

The TCD process needs also different deadlines and events to determine these deadlines. These settings are already part of the standard customizing. The template for the deadline events is WS STANDARD DEL, for the inbound the assigned transaction is WS CD RECEIPT and for outbound it’s WS CD GOODS ISSUE. Due to these events the TCD delivery get additional deadlines compared to the standard delivery.

Figure 13: Time segment procedures

Page 18 of 103

Figure 14: Assignment of deadline events to time segment procedures

2.1.10 Maintain Output Types Customizing: SAP Customizing Implementation Guide Basic Shipping Functions

Logistics Execution

Output Control

Output Determination

Output Determination for Outbound Deliveries

Maintain Output Types

Shipping Maintain

Normally the ERP is set up to create and process the follow-up deliveries in the TCD chain after the initial goods issue from the sending warehouse automatically. To ensure that this process is working the right output control has to be used. There is already a standard customizing existing that contains the link to the program that processes the output, which means in this case creates the delivery pair for the next warehouse in the TCD chain or the inbound delivery if the next warehouse is the final recipient. The standard entry delivered is CDOD.

Page 19 of 103

Figure 15: Definition of output types

Page 20 of 103

Figure 16: Defintion of the processing routine for the output type

2.1.11 Maintain Output Determination Procedure Customizing: SAP Customizing Implementation Guide Basic Shipping Functions

Output Control


Logistics Execution


Shipping Maintain

Maintain Output Determination

Procedure

Page 21 of 103

After definition of an output type this output type has to be assigned to a determination procedure. In the standard there was already a procedure existing (SPEV10) that contained the output type CDOD but in the process described here the decision was taken to enhance the determination procedure V10000. So all the output types that are assigned to SPEV10 have been copied over to the output determination procedure V10000 (SPED, SPER, CDOD).

Figure 17: Definition of output determination procedures

Page 22 of 103

Figure 18: Assignment of condition types to output determination procedures

2.1.12 Assign Output Determination Procedures Customizing: SAP Customizing Implementation Guide Basic Shipping Functions

Output Control


Logistics Execution


Shipping Maintain

Assign Output Determination

Procedures

The output determination procedures have to be assigned to the delivery type. This means for the given delivery type the depending output determination procedures are executed which means in the TCD case that for each delivery type with the assigned procedure V10000 in case of TCD the delivery pair for the next warehouse is created. The system has been set up that the process should run with delivery type LO but can be easily enhanced to us also other delivery types as starting point.

Page 23 of 103

Figure 19: Assignment of output determination procedure to delivery types

2.1.13 Set QM Check and Delivery Type for Each Movement Type Customizing: SAP Customizing Implementation Guide Unit Management

Basics


Logistics - General

Handling

Inventory Management

Set

QM Check and Delivery Type for Each Movement Type

The movement of the products between the different warehouses in the TCD chain is represented in the system as transfer movements which mean that the deliveries created for the cross-docking warehouses contain movement types for the transfer posting. In the standard customizing the movement types are 315 for the inbound delivery and 313 for the outbound side (only in the case that the outbound delivery is not the final one to a customer but points to another warehouse).

Page 24 of 103

Figure 20: Setting of the movement type for the TCD pair creation

2.1.14 Delivery Type Determination Customizing: SAP Customizing Implementation Guide Unit Management

Basics

Delivery

Logistics - General

Handling

Delivery Type Determination

Based on the movement type maintained in the customizing mentioned above also a delivery category is found. This delivery category is used in this customizing to determine the delivery type used to create the inbound delivery for the cross-docking warehouse. So the activity that has to be executed is “Set delivery type determination for inbound delivery”. The SAP proposal is to use DIG as delivery type and this has been set up for this process. The determination has been set up to determine the delivery type based on the delivery category ID and the sending plant P9L1.

Page 25 of 103

Figure 21: Setting for the determination of the delivery type for the inbound delivery

Figure 22: Inbound delivery type setting for the CD inbound delivery

Page 26 of 103

2.1.15 Define Packaging Material Types Customizing: SAP Customizing Implementation Guide Unit Management

Basics

Logistics - General

Handling

Define Packaging Material Types

To separate the HUs used for the TCD process an own packaging material type has been defined. This step is an optional one.

Figure 23: Definition of a packaging material type for the TCD process

2.1.16 Condition Creation for the Output Processing Application: SAP menu Shipping

Logistics

Outbound Deliveries

Logistics Execution Create (VV21)

Page 27 of 103

Master Data

Output

In the customizing the output determination process has been defined. Now in the application conditions have to be maintained when this process has to be used and when the process is executed. These settings are evaluated for the outbound deliveries in the TCD chain starting with the first one. In this transaction first the output type is chosen, for TCD is CDOD. After this on the next screen it has to be set up for which delivery types this output should be chosen, in the given example it’s LO. At this point settings have to be done if the process should also work with other delivery types. The entry in the column medium is corresponding to the customizing entry for the output type where the message transmission medium 8 was set up. The column Date/Time represents the scheduling of the output, the entry 4 means “Send immediately (when saving the application)”.

Figure 24: Condition definition for the output determination

Figure 25: Setting for delivery type LO with immediate processing

Page 28 of 103

2.2

Transportation Cross-Docking Settings EWM Part

At the beginning a general remark: this guide focuses on the cd-warehouse. Therefore there are no special settings made for the sending warehouse. This means all steps in the sending warehouse shown later in the document are based on the standard customizing. 2.2.1 Activation of BC Sets Application: SAP menu

Tools

Customizing

Business Configuration Sets

Activation of BC Sets (SCPR20)

In the EWM the TCD customizing is not part of the standard customizing. However to enable an easy way to get a first draft process running so called BC-Sets have been used. These BC-Sets contain a number of customizing entries thought for a special process. There is one BC-Set existing that covers the TCD process called “/SCWM/DLV_TCD”. This BC-Set has to be activated and the delivery depending TCD are created like new delivery types for the inbound and outbound process in the cross-docking warehouse. To check the content of the BC-Set Tx SCPR3 – Display and Maintain BC Sets can be used. There all customizing contained in the BC-Set is displayed.

Figure 26: Activation of the CD BC-Set

Page 29 of 103

2.2.2 Map Storage Locations from ERP System to EWM Customizing: SAP Customizing Implementation Guide Management

Extended Warehouse Management

Goods Movement

SCM Extended Warehouse Interfaces

ERP Integration

Map Storage Locations from ERP System to EWM

In this customizing activity the EWM view to the TCD storage location has to be maintained. To enter the right settings here it has to be kept in mind that the storage location is depending to the sending plant which means also the entitled is the entitled of the sending plant. So the plant must be in the current example P9L1, the storage location CD1 but the warehouse is P9Q1.

Figure 27: Mapping of the ERP storage location to an EWM availability group

2.2.3 Define Partner Roles Customizing: SAP Customizing Implementation Guide Management


Delivery Processing

Partner Processing

SCM Extended Warehouse Cross-Process Settings

Define Partner Roles

As mentioned above the BC set for the TCD has already set up the delivery customizing; but this only means the TCD depending settings. The settings regarding the standard outbound delivery have not been adapted. But this is needed to ensure that the process TCD is running well. As the TCD process is determined in the sending warehouse already the first outbound delivery has to provide some information to the ERP system. In the partner roles customizing the profiles used for the first

Page 30 of 103

outbound delivery order and outbound delivery have to be adapted. Here the partner role ship-to party final has to be activated (STPRTF). This role is used after a cross-docking route has been determined to store the final recipient of the delivery while the ship-to party will be the next crossdocking location.

Figure 28: Maintenance of the partner profile for the outbound delivery order

Figure 29: Activation of the final ship-to partner for the outbound delivery order

Page 31 of 103

Figure 30: Maintenance of the partner profile for the final delivery

Figure 31: Activation of the final ship-to partner for the final delivery

2.2.4 Define Date Profiles Customizing: SAP Customizing Implementation Guide Management


Delivery Processing

Dates/Times


Define Date Profiles

Page 32 of 103

Not only the partner customizing has to b adapted but also the settings for the dates and times stored in the first outbound delivery. Similar to the partner processing also special dates and times are determined and filled after a cross-docking route has been determined. The dates are TCDLOGGI “Goods Issue for Next TCD Location” and TDELIVERY “Final Delivery Date”. These date have to be maintained for the outbound delivery order and the outbound delivery.

Figure 32: Maintenance of the partner profile for the outbound delivery order

Figure 33: Activation of the receiving date at the next cross-docking location and the final delivery date

Page 33 of 103

Figure 34: Maintenance of the partner profile for the final delivery

Figure 35: Activation of the receiving date at the next cross-docking location and the final delivery date

2.2.5 Map Document Types from ERP System to EWM Customizing: SAP Customizing Implementation Guide Management


Delivery Processing


ERP Integration

Map Document Types from ERP System to EWM

Page 34 of 103

The delivery types used for the cross-docking scenario in ERP have to be mapped to delivery types in EWM. This is valid for the inbound delivery in the cross-docking warehouse as well as for the outbound delivery. The mapping will be done based on the ERP delivery information and a “Code for Initiator of a Communication Chain” indicating that the deliveries depend to the cross-docking process.

Figure 36: Mapping of the ERP outbound delivery type and the TCD indicator to the EWM outbound delivery type

2.2.6 Map Item Types from ERP System to EWM Customizing: SAP Customizing Implementation Guide Management


Delivery Processing


ERP Integration

Map Item Types from ERP System to EWM

Not only the document types but also the item types can be mapped to special item types depending to a differentiation attribute and the EWM document type already determined. This leads to the fact that it’s possible to determine a special item type for cross-docking if needed. In the given example already the right settings where done by the BC-Set.

Page 35 of 103

Figure 37: Mapping of the ERP inbound delivery type and the TCD indicator to the EWM inbound item type

2.2.7 Map Partner Roles from ERP System to EWM Customizing: SAP Customizing Implementation Guide Management


Delivery Processing


ERP Integration

Map Partner Roles from ERP System to EWM

The special cross-docking partners set up in ERP have to be also filled into the inbound and outbound delivery for the cross-docking warehouse in the EWM. For this reason the ERP partner roles have to be mapped to EWM partner roles and depending ID Types. For the current process the partner role form the ERP “EC” had to be mapped to the partner role “STPRTF” which is also mapped to the IDType “CRM002” that represents ERP customer number.

Figure 38: Mapping of the TCD specific partners from ERP to EWM

Page 36 of 103

2.2.8 Control Message Processing Dependent on Recipient Customizing: SAP Customizing Implementation Guide Management


Delivery Processing


ERP Integration

Control Message Processing Dependent on Recipient

Based on delivery type this setting can be done to maintain the processing of the messages to ERP depending to the recipients. This setting is optional for the given process but maintaining an entry prohibits warning messages during delivery processing.

Figure 39: Setting of the recipient-dependent control of message processing

2.2.9 Define Packaging Material Types Customizing: SAP Customizing Implementation Guide Management Handling Units

Extended Warehouse Management Basics


Define Packaging Material Types

Page 37 of 103

To ensure that the TCD process runs independent from the other warehouse processes an own packaging material type is used. This packaging material type will later be assigned to different number ranges for the HU identification.

Figure 40: Creation of a packaging material type in EWM

2.2.10 Assign Number Range Intervals to Packaging Material Types Customizing: SAP Customizing Implementation Guide Management


Handling Units

External Identification


Assign Number Range Intervals to Packaging

Material Types

After the definition of the packaging material type the number range needs to be assigned. This number range is used to create the given HU number from the sending warehouse in the crossdocking warehouse.

Page 38 of 103

Figure 41: Maintenance of the number range for the packaging material

2.2.11 Define Hierarchy Structure Customizing: SAP Customizing Implementation Guide Management

SCM Basis

Hierarchy

SCM Extended Warehouse

Define Hierarchy Structure

After the basic customizing now the routing guide has to be activated and configured. For this reason several settings in the customizing and in the application have to be executed. The first point is that a hierarchy structure has to be maintained in the customizing. This structure will later be used to define a hierarchy in the application that is used for the routing guide. The hierarchy used for this example is already part of the standard customizing and can be used without changes.

Page 39 of 103

Figure 42: Assignment of hierarchy structures

Figure 43: Assignment of levels to the hierarchy structures

2.2.12 Maintain Hierarchy Application: SAP menu Master Data

Hierarchy

SCM Extended Warehouse Management

SCM Basis

Maintain Hierarchy (/SAPAPO/RELHSHOW)

After this a hierarchy has to be defined in the application. These hierarchies are used in the routing guide. For EWM the routing guide just needs one hierarchy with a special (hard-coded) name “RELH_ZONE”. This is also documented in note 1137521. Remark: In releases earlier then 5.1 SP 6 this hierarchy has to be maintained also in the customizing to indicate that this is a transportation zone.

Page 40 of 103

Figure 44: Definintion of a hierarchy

Figure 45: Hierarchy definition details

Page 41 of 103

2.2.13 General Settings for Routing Guide Application: SAP menu

SCM Extended Warehouse Management

Warehouse Management

Master Data

Extended

Shipping and Receiving

General Settings

for Route Determination (/SCTM/RG_BASIC)

The routing guide has to be activated globally in the client. Only if the routing guide is active the determination of routes happens and this is the key to enable the TCD process. Later in the customizing it’s possible to restrict the automatic route determination by warehouse number and delivery type to ensure that the route determination is only running in special processes.

Figure 46: Activation of the routing guide

2.2.14 Assign Number Range Intervals to Packaging Material Types Customizing: SAP Customizing Implementation Guide Management


Outbound Delivery

Route Determination

SCM Extended Warehouse Goods Issue Processing

Activate or Deactivate Route Determination

In this customizing it can be maintained based on warehouse, document type and document category if the route determination is active or not. For the sending warehouse in the given example the route

Page 42 of 103

determination has been switched on for the outbound delivery. Only with active route determination it’s possible to start the cross-docking process. In the cross-docking warehouse the route determination has been switched on for the cross-docking outbound delivery. This is not mandatory but useful because it could be that there is more then one TCD step until the final destination is reached and the process works that way, that always from the actual location to the final destination the route is determined, which means that starting from the CD-warehouse again a route determination for the route to the destination is started. The result of this determination for sure can be another CD-route.

Figure 47: Route Determination Actiovation for the CD Inbound Delivery

Page 43 of 103

Figure 48: Route Determination Actiovation for the CD Onbound Delivery

2.2.15 Method Parameter for Each Strategy Application: Method Parameter for Each Strategy (/SCTM/PC03)

Some parameters that control the routing guide are hidden in transactions that are not visible in the menu. These transactions are called /SCTM/PC01 - /SCTM/PC06. The most important transaction for the TCD process is the Tx /SCTM/PC03. There a setting can be made that influences if a route can consist of more then one leg which is the case in the TCD scenario. The parameter PATHLENGTH indicates this values; in standard the value is 1, for crossdocking the value has to be higher then 1 to enable the system to find a cross-docking route.

Figure 49: Maintenance of routing guide specific attributes

Page 44 of 103

2.2.16 Assignments: Warehouse Number/Business Partners Application: Application: SAP menu Extended Warehouse Management

SCM Extended Warehouse Management Settings

Assignments: Warehouse

Number/Business Partners

After the basis settings for the routing guide have been done the master data for the routes need to be created. First the supply chain unit for the different warehouses involved needs to be determined. The supply chain unit will later be used for the route definition as source and as cross-dkcing warehouse. All parts of the route have to be maintained as location in APO (/SAPAPO/LOC3).

Figure 50: Assignment of supply chain unit and business partners to the EWM warehouse

Page 45 of 103

Figure 51: Assignment of supply chain unit and business partners to the EWM warehouse

2.2.17 Maintain Route Application: Application: SAP menu Extended Warehouse Management Determination

SCM Extended Warehouse Management Master Data


Route

Maintain Route (/SCTM/ROUTE)

For the TCD process a route with a special attribute is needed. This attribute is the cross-docking location (SCU) which means the cross-docking warehouse, in the given case P9Q1. A cross-docking route points from the source to the destination and consists not of legs but of other routes. In other terms routes pointing from the source to the cross-docking warehouse and from the cross-docking warehouse to the destination have to be combined in the cross-docking route. A cross-docking route can contain other cross-docking routes as parts so it’s possible to configure complex transportation networks with multiple cross-docking steps. For the current process three routes have been defined. Route 1 “LMWH_P9Q1” is the route for the first part of the cross-docking route going from the source warehouse LMWH to the cross-docking warehouse P9Q1. The second route “P9Q1_CUST” points from the cross-docking warehouse P9Q1 to the final the final destination, the customer P9L_CUS_01. The combination of these two routes is the third route “LMWH_CUST” that represents the cross-docking route. This route has the sending warehouse as source and the final destination, the customer, as destination. No legs are maintained

Page 46 of 103

for this route but on the tab CD routes the two other routes are assigned, one route as incoming route to the cross-docking warehouse and one route as outgoing route from the cross-docking warehouse. On the third level it’s possible to maintain the CD attributes which means the indicator “Transshipment”. This indicator is used to control whether a unloading from the truck to a new truck has to take place in the cross-docking warehouse or if the product remains in the original truck. In the current case the transshipment flag is used.

Figure 52: Creation of the route from the source warehouse to the CD warehouse

Page 47 of 103

Figure 53: Route from the CD warehouse to the customer

Page 48 of 103

Figure 54: CD route from the source warehouse to the customer

2.2.18 Simulate Route Determination Application: Application: SAP menu Extended Warehouse Management Determination



Route

Simulate Route Determination (/SCTM/RGINT)

To check the route determination the simulation of the route determination can be used. This helps to check if the route that has been created will be determined.

Page 49 of 103

Figure 55: Checking of the route definition using the routing guide simulation

2.2.19 Define Storage Types Customizing: SAP Customizing Implementation Guide Management


SCM Extended Warehouse Master Data

Define Storage

Type

For this process also in warehouse own storage types have been defined to separate the warehouse internal processes from the normal processes. The storage types are: GRCD

Goods Receipt for CD

CD81

Deconsolidation for CD

CD83

Packing in GI for CD

CD25

Re-Packing in Staging for CD

GICD

Goods Issue for CD

Page 50 of 103

Figure 56: TCD goods receipt

Page 51 of 103

Figure 57: TCD deconsolidation

Page 52 of 103

Figure 58: TCD packaging

Page 53 of 103

Figure 59: TCD staging

Page 54 of 103

Figure 60: TCD goods issue

Page 55 of 103

2.2.20 Define Storage Sections Customizing: SAP Customizing Implementation Guide Management



Sections

Assigned to the storage types the different storage sections have been defined.

Figure 61: Storage section definition


Page 56 of 103

Define Storage


2.2.21 Create Storage Bin Application: Application: SAP menu Extended Warehouse Management


Storage Bin

Create Storage Bin

(/SCWM/LS01)

After the customizing regarding storage types and storage sections has been done now the depending storage bins have to be created. These storage bins will be used for the movements of the TCD products in the warehouse. The storage bins in the GR and GI represent staging areas, the other bins will be assigned to work centers defined later.

Page 57 of 103

Figure 64: Goods receipt storage bin

Figure 65: Goods issue storage bin

Page 58 of 103

Figure 66: TCD deconsolidation bin

Figure 67: TCD packaging bin

Page 59 of 103

Figure 68: TCD staging bin

2.2.22 Define Work Center Customizing: SAP Customizing Implementation Guide Management



Work Center

Define Work Center

For the deconsolidation, packing and staging work center have been defined. These work centers are maintained in customizing with the standard layout. To the work center the storage type and the external process step is assigned. Later in the process oriented storage control the work center are determined “hard” for the different steps so no rule-based determination is used.

Page 60 of 103

Figure 69: Deconsolidation work center

Page 61 of 103

Figure 70: Packing work center

Page 62 of 103

Figure 71: Staging work center

2.2.23 Define Master Data Attributes Application: Application: SAP menu Extended Warehouse Management


Data Attributes (/SCWM/TWORKST)

Page 63 of 103

Work Center

Define Master

First the work centers have to be defined in the customizing and afterwards the application the storage bins have to be assigned to them. In the given example to each work center one special bin as created above is assigned.

Figure 72: Definition of the deconsolidation work center

Figure 73: Definition of the packaging work center

Page 64 of 103

Figure 74: Definition of the staging work center

2.2.24 Define Process-Oriented Storage Control Customizing: SAP Customizing Implementation Guide Management Warehouse Task



Define Process-Oriented Storage Control

Using this customizing activity the inbound and outbound process for the sending and the crossdocking warehouse is defined. For the inbound side the storage process ITCD has bee defined that contains the steps ICD1 – Unload, ICD2 – Deconsolidation and IB03 – Putaway, the outbound process OB01 – Picking, OCD2 – Packing, OCD3 – Staging and OCD4 – Loading. For the different process steps the destination data has been defined fixed in this customizing. It’s also possible to do these settings rule based but for this example fixed values is enough. This means when evaluating these settings the storage control will lead the work always to the given bin as next step.

Page 65 of 103

Figure 75: Definition of the external process steps for the inbound process

Figure 76: Definition of the external process steps for the outbound process

Figure 77: Definition of the inbound process

Page 66 of 103

Figure 78: Definition of the outbound process

Figure 79: Fix assignment of bins for the inbound process steps

Figure 80: Fix assignment of bins for the outbound process steps

Page 67 of 103

2.2.25 Define Creation Rule of Warehouse Orders Customizing: SAP Customizing Implementation Guide Management


Warehouse Order


Define Creation Rule for Warehouse Orders

The given example uses the WO creation rules a link to the storage process for the outbound side. In the inbound the storage process has been directly assigned to the warehouse process type, for the outbound the WOCR has been assigned to the warehouse process type. This means after the determination of the warehouse process type during warehouse order creation take the assigned creation rule and then determine the storage process from the determined rule. To make the example easy there has been only one WOCR created and with easy filter criterias.

Figure 81: Definition of the warehouse order creation rule for the CD outbound process

Page 68 of 103

2.2.26 Define Warehouse Process Type Customizing: SAP Customizing Implementation Guide Management Warehouse Task



Define Warehouse Process Type

For each inbound and outbound process a warehouse process type has been defined. This process type will be used to determine the process in the warehouse. On the inbound side the process is CDI1 with activity putaway. This process has the storage process fixed assigned. Also the source bin for this process has been defined as a door. This could also be determined through the delivery/TU assignment dynamically. CDO1 is used for the outbound part of the TCD process with activity picking. This process type has a fixed warehouse order creation rule assigned. Also this WPT has a fixed destination the TCD goods issue zone.

Page 69 of 103

Figure 82: TCD inbound warehouse process type

Page 70 of 103

Figure 83: TCD outbound warehouse process type

Page 71 of 103

2.2.27 Determine Warehouse Process Type Customizing: SAP Customizing Implementation Guide Management Warehouse Task



Determine Warehouse Process Type

After the definition of the warehouse process type rules have to be set up to determine the warehouse process type. These rules can be based delivery type or item type but also on priority and process type determination indicator. As the TCD process uses own delivery types for the inbound and outbound side in this example this can be used as the only criteria to determine the warehouse process type. This has the advantage that in the CD-warehouse no warehouse number specific data has to be stored, the global data is enough. A usage of this could be for example that the CD warehouse is no real warehouse but a distribution center. Delivery items with the delivery type ITCD will find WPT CDI1, delivery items with the delivery type OTCD will find WPT CDO1.

Figure 84: Determination of the warehouse process type for the inbound and outbound process based on delivery type

Page 72 of 103

3 Processing Transportation Cross-Docking This chapter shows how these settings react in the system. A simple cross-docking will be executed. The steps needed to execute the process will be shown and explained. Also some possibilities to control the process are show.

3.1

ERP Part – First Inbound Delivery

The process starts in the ERP. From the ERP the delivery documents will be distributed and in EWM the processing will be done. After the goods issue in EWM the cross-docking delivery pair will be created in ERP and from there distributed to the next warehouse were again the processing starts and so on till the end of the TCD chain is reached. The process shown will follow exactly the graphic shown at the beginning of this document 3.1.1 Create Material Application: Application: SAP menu Create (General)

Logistics


Material

Immediately (MM01)

For the cross-docking the global material master data needs to be created in ERP for the sending warehouse and the intermediate warehouse. In the sending warehouse all storage locations should be maintained, for the CD-warehouse one storage location is enough and in addition the cross-docking storage location needs to be maintained. After the creation of the material master the materials need to be distributed to the EWM system of the involved warehouses.

Page 73 of 103

Figure 85: Creation of the material for the CD warehouse

Figure 86: Creation of the material for the sending warehouse

Page 74 of 103

3.1.2 Purchase Order Creation Application: Application: SAP menu Create

Logistics


Purchasing

Vendor/Supplying Plant known (ME21N)

Before the TCD process starts in the sending warehouse stock needs to be stored. To store the stock a purchase order is created. This purchase order is later used to create an inbound delivery. In this example the purchase order contains two items with two different products that can be used in crossdocking. The created purchase order has the number 4500000580.

Figure 87: Creation of a purchasing order to create stock in the sending warehouse

3.1.3 Inbound Delivery Creation Application: Application: SAP menu Execution Create

Inbound Process

Logistics


Goods Receipt for Inbound Delivery

Logistics

Inbound Delivery

Single Document (VL31n)

Based on the purchase order 4500000580 an inbound delivery is created. After saving, the inbound delivery is distributed to the EWM system. To ensure that the delivery is distributed the combination of plant and storage location needs to be maintained in the delivery document and needs to be mapped to an ERP warehouse number that is marked to be controlled by an decentralized warehouse management system.

Page 75 of 103

Figure 88: Creation of an inbound delivery based on the purchasing order

Figure 89: Distribution of the created delivery to EWM

Page 76 of 103

3.2 EWM Part – First Inbound Delivery After the distribution of the delivery the processing goes on in the source warehouse that means in the EWM system. The delivery can now only be changed in this system. 3.2.1 Maintain inbound delivery Application: Application: SAP menu Extended Warehouse Management

SCM Extended Warehouse Management Delivery Processing

Inbound Delivery

Maintain Inbound Delivery (/SCWM/PRDI)

In the EWM the delivery gets a new number but can also still be selected using the ERP document number. As this delivery is just the inbound delivery the details will not be explained here but later in the outbound part. This stock will be putawayed in the warehouse and later used for picking for the TCD scenario.

Figure 90: Goods receipt posting and starting of the putaway in the sending warehouse

Page 77 of 103

3.3

ERP Part – Starting Outbound Delivery

Depending to the graphic in the beginning of the document the process should start with a sales order as the delivery should point to the customer. To shorten the process a little bit the example starts with a delivery without reference. Of course the TCD scenario could also be started with a sales order or other delivery types if the customizing is maintained in a proper way. 3.3.1 Outbound Delivery Creation Application: Application: SAP menu Process Document

Logistics

Logistics Execution

Outbound

Goods Issue for Outbound Delivery

Outbound Delivery

Create

Single

Without Order Reference (VL01NO)

This delivery is the starting point for the TCD process. In the ERP the delivery is pointing from the issuing warehouse directly to the customer. The cross-docking relevance will be determined in EWM during the route determination. For the show TCD process just one piece of the product TCD_PROD01 is ordered. Important for the outbound side is, similar to the inbound, that the right plat/storage location is maintained. In the current example the source location is the plant P9L1 that is mapped to the EWM warehouse LMWH. As customer P9L_CUS_01 is used. (Remark: In the chapter above the route pointing from LMWH to P9L_CUS_01 is described.)

Figure 91: Starting screen for creation of an outbound delivery

Page 78 of 103

Figure 92: Outbound delivery is automatically replicated to the EWM

Page 79 of 103

3.4 EWM Part – Starting Outbound Delivery 3.4.1 Maintain Outbound Delivery Order Application: Application: SAP menu Extended Warehouse Management


Outbound Delivery

Maintain Outbound Delivery Order (/SCWM/PRDO)

After saving the outbound delivery is distributed to EWM. There the outbound delivery request is created and directly activated to the outbound delivery order. This document is the document the warehouse is working on. During activation of the outbound delivery request the route determination happened. As result the rout LMWH_CUST has been determined. This route has the indicator to be a cross-docking route and the cross-docking location is maintained with P9Q1. Based on this information the system updates the outbound delivery order in EWM and adds additional data. First the route is added. This route is only pointing to the next destination in the TCD chain so to the cross-docking warehouse. Therefore not the cross-docking route has been set but the route LMWH_P9Q1 from LMWH to P9Q1 which has been setup as part of the CD route. Also the system has updated the partners in the delivery. A new partner has been added, the final ship-to party. This partner represents the final recipient of the delivery that is in the given example P9L_CUS_01. The ship-to party represents the next recipient that is the cross-docking warehouse P9Q1 (in the delivery the business partner is shown, BP0001V is the BP assigned to P9Q1).

Page 80 of 103

Figure 93: Starting outbound delivery in EWM with the route to the intermediate warehouse

3.4.2 Stock Removal for Outbound Delivery Order Application: Application: SAP menu Extended Warehouse Management Warehouse Request

SCM Extended Warehouse Management Work Scheduling

Create Warehouse Task for

Stock Removal for Outbound Delivery Order (/SCWM/TODLV_O)

Based on the outbound delivery order the warehouse tasks for the stock removal are created. To make this outbound process very lean the standard settings have been taken and nothing new has been maintained. So the warehouse task that will be created represents just the movement from the source bin to the goods issue staging area. There is also no explicit packing step defined. As the

Page 81 of 103

TCD process requires packed products during confirmation the products will be packed into a pickHU which will be used for the TCD process.

Figure 94: Picking warehouse task in the sending warehouse

3.4.3 Confirmation of Warehouse Tasks Application: Application: SAP menu Extended Warehouse Management

SCM Extended Warehouse Management Execution

Confirm Warehouse Task

(/SCWM/TO_CONF)

To confirm the warehouse task for picking the products the desktop transaction will be used. This could also be done using RF but this is not focus of this example. After the confirmation the products are in the goods issue zone and can be posted goods issue. As there is no explicit packing step maintained in the customizing for the sending warehouse during confirmation a pick HU needs to be created and the products have to be confirmed into this HU. The HU is mandatory for the TCD process as the following steps in the CD warehouse will not work for unpacked products!

Page 82 of 103

Figure 95: Confirmation of the picking warehouse task

3.4.4 Maintain Outbound Delivery Order Application: Application: SAP menu Extended Warehouse Management


Outbound Delivery


When the picking is confirmed directly the goods issue can be posted. This is done again from the outbound delivery order. After the goods issue the information is transferred back to ERP. This updates then the ERP delivery and triggers the creation of the cross-docking delivery pair for the CD-warehouse.

Page 83 of 103

Figure 96: Goods issue posting in the sending warehouse

Page 84 of 103

3.5 ERP Part – Delivery Pair in ERP 3.5.1 Outbound Delivery Display Application: Application: SAP menu Process

Logistics

Logistics Execution

Outbound


Outbound Delivery

Display (VL03N)

After the goods issue in the EWM the outbound delivery in ERP is updated. A new partner is added to the outbound delivery “EC – Receiv. CD Warehouse”.

Figure 97: New partner in the outbound delivery in ERP determined based on the TCD scenario

3.5.2 Transportation Cross-Docking Monitor Application: Application: SAP menu Cross-Docking

Logistics

Logistics Execution

Transportation

Transportation Cross-Docking Monitor (/SPE/CDMON)

In the ERP a transaction can be used to monitor the TCD chain. Only this transaction offers the overview about the whole process. In EWM only the process in the current warehouse is visible, in ERP the whole TCD process can be seen. The transaction transportation cross-docking monitor can be used to check if the process does not work properly. Then the deliveries where the output processing was wrong are displayed with a red traffic light. If everything was fine the subsequent deliveries are displayed.

Page 85 of 103

Figure 98: Selection screen for the cross-docking monitor in ERP

Figure 99: Delivery flow over the cross-docking chain

Page 86 of 103

3.6

EWM Part – Cross-Docking Inbound Delivery

3.6.1 Maintain Inbound Delivery Application: Application: SAP menu Extended Warehouse Management


Inbound Delivery

Maintain Inbound Delivery (/SCWM/PRDI)

In the EWM the cross-docking inbound and outbound deliveries are now visible. The best way to select these deliveries is the TCD process number. This number is the starting outbound delivery for the process. The number remains the same during the whole TCD process. The inbound delivery is created with a special delivery type. This delivery type is determined based on the mapping maintained in the customizing. From the ERP also an additional “Code for Initiator of a Communication Chain” is distributed that indicates the TCD process (see the mapping in the customizing section). Some additional values can be found in the inbound delivery. The stock coming with this inbound delivery is D1. This stock type posts the stock into the cross-docking storage location CD1. The entitled in the delivery is P9L_ENTD01 which represents the plant P9L1. The reason for this is that the storage location CD1 depends to the plant P9L1. The stock remains in the ownership of P9L1 till the goods issue to the final recipient is posted. On the partner tab the final ship-to partner is indicated. This also indicates that the delivery is not planned for the actual warehouse but for a different recipient. The reference tab contains information about the ASN and the TCD process number. The ASN and the TCD process number are the original outbound delivery number of the starting outbound delivery. At the HU tab the HU is listed that was sent out of the sending warehouse.

Remark: Before the process can start for the inbound delivery the goods receipt has to be posted.

Page 87 of 103

Figure 100: Selection of the TCD inbound delivery using the TCD process number

Figure 101: Inbound delivery with the special TCD delivery type and source plant as entitled

Page 88 of 103

Figure 102: Final Ship-To party automatically maintained in the inbound delivery

Figure 103: Original outbound delivery used as TCD process number and ASN

Page 89 of 103

Figure 104: HU from the sending warehouse is taken over into the inbound delivery

Page 90 of 103

3.7

EWM Part – Cross-Docking Outbound Delivery Order



Outbound Delivery


Similar to the inbound delivery also the outbound delivery can be selected. This document has also a special delivery type and is pointing to the same stock as in the inbound delivery. Like in the sending warehouse a route has been determined for the trip from the CD-warehouse to the customer. This route can be seen in the outbound delivery. If this route would be a cross-docking route a next delivery pair would be created after the goods issue; but in the given example it’s a normal route. The reference tab contains like in the inbound delivery some special data. There also the TCD process number is listed that is the same like in the inbound delivery. An additional reference to the inbound delivery is the TEI number, the “TCD ERP Inbound Delivery Reference” that’s pointing to the inbound delivery of the delivery pair. The last new reference is the ERO the pointer to the ERP original document.

Figure 105: Selection of the outbound delivery based on the TCD process number

Page 91 of 103

Figure 106: Outbound delivery with the special delivery type and special stock type for TCD

Page 92 of 103

Figure 107: Reference documents to the original outbound deliver,y the TCD process number and the TCD inbound delivery

Page 93 of 103

3.8 ERP Part – Stock Situation 3.8.1 Stock per Material Application: Application: SAP menu System

Warehouse

Stock

Logistics

Logistics Execution

Information

Total Stock per Material (Inventory Management)

(MMBE)

Using the stock overview in ERP the stock can be seen in theCD1 storage location after the goods receipt in the CD-warehouse.

Figure 108: Selection of the TCD stock for the source plant in ERP in the TCD storage location

Figure 109: Stock overview in the TCD storage location

Page 94 of 103

3.9

EWM Part – Cross-Docking Processing

3.9.1 Stock Removal for Outbound Delivery Order Application: Application: SAP menu Extended Warehouse Management Warehouse Request

SCM Extended Warehouse Management Work Scheduling

Create Warehouse Task for

Stock Removal for Outbound Delivery Order (/SCWM/TODLV_O)

After the goods receipt has been posted, the TCD process in the intermediate warehouse can be executed. The process can be started from the inbound or from the outbound side which means the warehouse tasks can be created from the inbound delivery or from the outbound delivery. In this example the process will start from the outbound side. The warehouse task for the inbound side will be created actively, the pick-HU WT from the outbound delivery will be created inactively. After the confirmation of the last inbound step (before putaway) the pick-HU WT will be activated.

Figure 110: Creation of the picking WT for the CD-HU

Page 95 of 103

3.9.2 Confirmation of Warehouse Tasks Application: Application: SAP menu Extended Warehouse Management


Confirm Warehouse Task

(/SCWM/TO_CONF) The process starts with unloading WT. This one has to be confirmed. After the confirmation directly the next WT to the deconsolidation will be created. This one will be also confirmed directly to do the movement.

Figure 111: Confirmation of the putaway and picking warehouse tasks

3.9.3 Monitoring of CD-Process in EWM Application: Application: SAP menu Extended Warehouse Management

SCM Extended Warehouse Management Monitoring

Warehouse Management Monitor

(/SCWM/MON) In the monitor based on the inbound delivery the inbound process can be seen until the pick-HU WT is confirmed. Using the outbound delivery the outbound process can be monitored.

Page 96 of 103

Figure 112: Overview of the WTs with reference to the inbound delivery

3.9.4 Deconsolidation Application: Application: SAP menu Extended Warehouse Management


Deconsolidation in Goods Receipt

(/SCWM/DCONS) The deconsolidation has been setup as mandatory step in the current example. To make the process easier the HU is just completed in the deconsolidation. Normally a deconsolidation is done which means sorting out the products. A good example is that a cross-delivery HU is coming into the CDwarehouse that contain products that have to putawayed and products that will be cross-docked. Deconsolidation in this case is used to separate these products. After the deconsolidation is completed the pick-HU WT is activated as the deconsolidation was the last inbound step.

Figure 113: Starting screen of the deconsolidation

Page 97 of 103

Figure 114: Exceution of the deoncolidation

Figure 115: Situation in the monitor after deconsolidation, picking HU-WT is now active

3.9.5 Deconsolidation Application: Application: SAP menu Extended Warehouse Management


Packing General (/SCWM/PACK)

Page 98 of 103

After the confirmation of the pick-HU WT the HU is sent to the packing. In the outbound storage process this step has been defined with a fixed bin. Also in the packing the HU is just closed. In the packing also a repacking could happen. This is supported by the cross-docking process but will not be done in this example. After the completion of the packing a WT to the staging is automatically created. This WT will be confirmed from the monitor.

Figure 116: Starting screen of the packing process

Figure 117: Execution of the packing

Page 99 of 103

Figure 118: Staging from the monitor after the packing



Outbound Delivery


When the staging has been executed the goods issue can be posted from the outbound delivery order. This will trigger also the posting of the goods issue in the ERP. As this delivery is directly send to the customer after the goods issue the TCD process is completed.

Figure 119: Outbound delivery after the picking is done

Page 100 of 103

Figure 120: Goods issue posting for the outbound delivery

Page 101 of 103

3.10 ERP Part – Outbound Delivery 3.10.1 Outbound Delivery Display Application: Application: SAP menu Process

Logistics

Logistics Execution

Outbound


Outbound Delivery

Display (VL03N)

Finally after the goods issue is posted in EWM the depending posting is also done in ERP.

Figure 121: Goods movement status in the outbound delivery in ERP

3.10.2 Stock per Material Application: Application: SAP menu System

Warehouse

Stock

Logistics

Logistics Execution

Information

Total Stock per Material (Inventory Management)

(MMBE)

After the goods issue the stock is gone from ERP.

Page 102 of 103

Figure 122: Stock selection for sending plant in ERP

Figure 123: Stock overview after goods issue in the CD warehouse

Page 103 of 103

TCD Configuration and Process Description

Recommend Documents