Solution Manager Content SAP EWM 9.3 Document Version: CUSTOMER. Transit Warehousing

Transcription

1 Solution Manager Content SAP EWM 9.3 Document Version:

2 Document History Document Version Description 1.0 Final version. May 27, 2015 Document History 2015 SAP SE or an SAP affiliate company. All rights reserved. 2

3 Table of Contents 1 Scenario: Integration Prerequisites Warehouse Structure and Master Data Process Process: Receive from Shipper Process Process: Ship to Next Transit Warehouse Process Configuration: Prerequisites Installed Components Prerequisites for System Connection in SAP ERP, SAP TM and SAP EWM Configuration Guide for LCL Air Freight Scenario in SAP TM User Roles for SAP TM and SAP EWM Overview of SAP ERP Master Data Customer Master Data in SAP ERP Vendor Master Data for Carriers in SAP ERP Configuration in SAP ERP Activating Business Transaction Events (BTE) in SAP ERP Configuring Logical Systems in SAP ERP Assigning EWM Logical System to RFC Destination in SAP ERP Configuring qrfc Destination in SAP ERP Configuration in SAP EWM Activating Business Functions in SAP EWM Configuring Logical Systems in SAP EWM Assigning Logical System to RFC Destination in SAP EWM Configuring Business Systems Configuring Business System Group Configuring qrfc Destination in SAP EWM Activating the Planning Version and Model for Master Data Activating BC Sets in SAP EWM Configuring Action Profiles for TU and Vehicle Configuring Action Conditions for Transportation Unit Checking Action Profiles for HU Activating Error and Conflict Handler in SAP EWM Defining Work Center Layout to Display Planned HUs Settings and Master Data in SAP ERP Preparing Initial Transfer of Master Data from SAP ERP Transferring Master Data from SAP ERP using CIF Scheduling Background Job for Master Data Transfer Configuration in SAP TM Assigning Warehouse Number to Location Transferring Locations and Business Partners from SAP TM to SAP EWM Settings and Master Data in SAP EWM Checking Business Partners of Transportation Network Checking Locations of Transportation Network Maintaining Supply Chain Units for Transit Warehouses Maintaining Logical Conditions for Bin Determination Table of Contents 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

4 4.8.5 Checking Assignment of Supply Chain Unit to Warehouse Number Creating Warehouse Structure and Condition Records for Bin Determination Creating Determination Records for Printing HU Waybill Labels Creating Packaging Materials Defining the Link between Packaging Material and MTR in SAP EWM Defining Resource Group Defining Queue Sequence for Resource Group Defining Presentation Device Defining Resources Configuration for SAP NetWeaver Process Integration Checking Connection to SLD in SAP TM and SAP EWM Creating a Configuration Scenario for Loading Appointment Integration Configuration of Navigation between SAP EWM and SAP TM Creating Connection for Navigation in SAP EWM Configuring User for Navigation in SAP EWM Creating Connection for Navigation in SAP TM Configuring User for Navigation in SAP TM Test Case: Receive from Shipper Prerequisites Features Activities Test Case: Ship to Next Transit Warehouse Prerequisites Features Activities Appendix Appendix A: Checking Basic Table Entries Used in SAP TM, SAP ERP, and SAP EWM Appendix B: Verifying Synchronization of Customizing between SAP TM, SAP ERP, and SAP EWM Appendix C: Condition Records for Bin Determination Appendix D: Determination of Packaging Materials in SAP EWM Appendix E: Additional Configuration for LCL Ocean Freight Scenario Appendix F: Hints for Dangerous Goods Handling Table of Contents 2015 SAP SE or an SAP affiliate company. All rights reserved. 4

5 1 Scenario: You can use this business scenario to integrate warehouse execution with freight forwarding operations using SAP Extended Warehouse Management (SAP EWM) and SAP Transportation Management (SAP TM). In Transit Warehousing, you receive cargo from shippers based on inbound planning from SAP TM. You consolidate cargo with the same destination in your transit warehouse before you ship it to the next location of the transportation chain or deliver it to the final consignee, based on outbound planning from SAP TM. As cargo received from numerous shippers in a transit warehouse is very variable, you do not manage product master data for it. Instead, you manage cargo as handling units (HUs) and keep cargo information directly in the documents used in the warehouse. The transit warehouse is structured in such a way that you put away HUs with the same destination country or region on the same storage bin, where they are available for the shipment to the next location or to the consignee. HUs with special attributes, such as dangerous goods or high-value cargo, are put away separately. With the next outbound plan sent by SAP TM, you either load the HUs directly from the staging area used for putaway, or you stage the HUs before loading them onto a vehicle. During these processes, SAP EWM informs SAP TM about the major steps performed in the transit warehouse, such as arrival at checkpoint, departure from checkpoint, and receiving or loading completion. 1.1 Integration The business scenario is integrated in the LCL Air Freight scenario in SAP TM. It describes the receiving of cargo from a shipper in the transit warehouse in Tokyo, and the shipping of cargo from the transit warehouse in Tokyo to the gateway in Narita. The consignee of the cargo is located in the USA. The transit warehouse in Tokyo is managed with SAP EWM. 1.2 Prerequisites You can implement this business scenario with different releases of the relevant application components. However, only certain combinations are valid. For more information, see the Master Guide for SAP Extended Warehouse Management on SAP Service Marketplace at For more information about the configuration prerequisites, see Configuration:. 1.3 Warehouse Structure and Master Data As transit warehousing processes strongly depend on the warehouse structure, all processes are integrated in a standard warehouse with a predefined structure and use common master data, such as business partners, locations, and resources. The warehouse structure consists in the following areas: Doors and staging areas for inbound and outbound Area with country-specific storage bins Area with region-specific storage bins Area with storage bins for postal codes Areas for cargo with special attributes, such as dangerous goods or high-value cargo Area for the handling of HU containers Clarification zone In this scenario, the warehouse structure is used for the Tokyo transit warehouse of the LCL Air Freight scenario from SAP TM, but the same warehouse structure can be used for all transit warehouses across the transportation chain of this scenario. Note You can find a detailed description of the warehouse structure in Creating Warehouse Structure and Condition Records for Bin Determination. Scenario: 2015 SAP SE or an SAP affiliate company. All rights reserved. 5

6 Process The business scenario contains the following processes: 1. Receive from Shipper 2. Ship to Next Transit Warehouse The processes described in this scenario interact with each other and build a consistent flow: cargo received in the inbound process is shipped in the outbound process. The business process descriptions include not only the system and user activities, but also the physical activities in the warehouse. For this reason, some process steps are not carried out in the system. Scenario: 2015 SAP SE or an SAP affiliate company. All rights reserved. 6

7 2 Process: Receive from Shipper You use this business process to receive cargo from a shipper in a transit warehouse managed with SAP Extended Warehouse Management (SAP EWM). After the creation of a forwarding order and of a pick-up freight order from the shipper to the transit warehouse, SAP Transportation Management (SAP TM) sends the inbound planning information to SAP EWM. When the truck arrives, you identify the freight order in SAP EWM and post the arrival at checkpoint. The truck drives to a door and you unload the cargo, which is usually packed on pallets. After unloading, you identify the handling units (HUs) based on the inbound plan sent by SAP TM. You attach an HU label to them, for example, a house airway bill (HAWB) label containing shipper and consignee information. The truck leaves the door and you post the departure from the checkpoint. You then put away HUs with the same destination country in the same storage bin, where they are available for the shipment to the next location or to the consignee. HUs with special attributes, such as overdimensional cargo or high-value cargo, are put away separately. In this process, SAP EWM informs SAP TM about arrival at checkpoint, receiving completion, and departure from checkpoint. The notification of receiving completion also includes information about the single HUs. 2.1 Process This business process runs as follows: 1. Create forwarding order (SAP TM) A customer service agent creates a forwarding order for the transportation of cargo from a shipper to a consignee. The cargo is to be picked up from the shipper and transported to the consignee via transit warehouses belonging to the transportation network of the freight forwarder and managed with SAP EWM. SAP TM creates freight units based on the forwarding order. 2. Create freight order for pick-up (SAP TM) The transportation planner carries out the transportation planning for the freight units. This creates a freight order for transporting cargo from the shipper s location to the first transit warehouse. The transportation planner communicates with a carrier. He or she assigns the carrier to the freight order in SAP TM, and communicates the freight order number to the carrier. 3. Pick up packages from shipper (SAP TM) The carrier picks up the cargo from the shipper s location and informs a capacity manager, who sets the status of the current stage of the freight order to Departed in SAP TM. When the transportation planning is complete, the transportation planner sends an unloading request message containing freight order information to SAP EWM. (This step can be done automatically.) SAP EWM automatically creates a vehicle, a transportation unit (TU), an inbound delivery, and HUs. The HUs are assigned to the TU. 4. Truck arrives at checkpoint (SAP EWM) When the truck arrives, the truck driver gives the receiving office clerk the freight order reference. The receiving office clerk selects the freight order in SAP EWM. He or she assigns a free door to the TU, sets the status Docked at Door, and tells the truck driver to drive to the assigned door. SAP EWM automatically prints HU labels to prepare for the receiving of HUs. In addition, SAP EWM sends an unloading notification message for arrival at checkpoint to SAP TM. SAP TM sets status of the current stage of the freight order to Arrived. In this step, you can also print an unloading list in SAP TM (optional). 5. Unload truck and receive packages (SAP EWM) A warehouse worker unloads the packages from the truck to the inbound staging area behind the door. A warehouse worker then receives the HUs using an RF device. He or she identifies the packages, attaches an HU label to each package, and scans the label. He or she enters the weight and dimensions of the packages. The system automatically posts goods receipt in SAP EWM for each received HU. With the last HU, the warehouse worker confirms the receiving completion in SAP EWM, which triggers the sending of an unloading notification message containing the received HUs to SAP TM. SAP TM updates the freight order and freight units. 6. Truck leaves (SAP EWM) The truck leaves the door and the premises. The receiving office clerk confirms the departure from the checkpoint, and therefore from the door. SAP EWM sends an unloading notification message for departure from checkpoint to SAP TM. SAP TM updates the execution status of the freight order. 7. Putaway HUs (SAP EWM) Process: Receive from Shipper 2015 SAP SE or an SAP affiliate company. All rights reserved. 7

8 The warehouse worker chooses the equipment necessary for the putaway, for example, a forklift truck and an RF device, and logs on as a resource. He or she then picks an HU from the inbound staging area and scans its label. The system automatically creates a warehouse order and proposes a destination bin. The warehouse worker brings the package to the destination bin and confirms the putaway. He or she proceeds in the same way with all HUs until the inbound staging area is empty. Process: Receive from Shipper 2015 SAP SE or an SAP affiliate company. All rights reserved. 8

9 Process: Receive from Shipper 2015 SAP SE or an SAP affiliate company. All rights reserved. 9

10 3 Process: Ship to Next Transit Warehouse You use this business process to ship cargo from your transit warehouse to the next location in the transportation chain. After the creation of a pre-carriage freight order, SAP Transportation Management (SAP TM) sends the outbound planning information to SAP Extended Warehouse Management (SAP EWM). When the truck arrives, you identify the freight order in SAP EWM and post the arrival at checkpoint. The truck arrives at a door. You load the requested handling units (HUs) directly from their storage bin, or you stage the HUs to a staging area first before loading them onto the truck. The truck departs from the door and you post the departure from the checkpoint. In this process, SAP EWM informs SAP TM about arrival at checkpoint, loading completion, and departure from checkpoint. The notification of the loading completion includes information about the loaded HUs. In this process, you print the waybills in SAP TM before handing them over to the truck driver. 3.1 Process This business process runs as follows: 1. Create freight order (SAP TM) The transportation planner carries out the transportation planning for the freight units. This creates a freight order for transporting the cargo to the next location. He or she assigns the carrier to the freight order in SAP TM, and communicates the freight order number to the carrier. 2. Send loading request to transit warehouse (SAP TM) When the transportation planning is complete, the transportation planner sends a loading request message to SAP EWM. (This step can be done automatically.) SAP EWM automatically creates a vehicle, a transportation unit (TU), an outbound delivery order, and planned HUs. The planned HUs are assigned to the TU. 3. Truck arrives at checkpoint (SAP EWM) When the truck arrives, the truck driver gives the shipping office clerk the freight order reference. The clerk selects the freight order in SAP EWM. He or she assigns a free door to the TU, sets the status Docked at Door, and tells the truck driver to drive to the assigned door. SAP EWM sends a loading notification message for arrival at checkpoint to SAP TM. SAP TM sets status of the current stage of the freight order to Arrived. With the arrival at checkpoint, SAP EWM creates staging warehouse tasks (WTs) for HUs that must be staged (optional). The system gathers the WTs into warehouse orders (WOs) to optimize the picking. The system assigns the WOs to one or more queues according to specific criteria, such as the activity area and the type of resource necessary to access the storage bins. 4. Stage handling units (optional) (SAP EWM) A warehouse worker picks and stages the HUs to the outbound staging area using an RF device. For this purpose, he or she chooses the equipment necessary for the picking, for example, a forklift truck and an RF device. He or she logs on to the system as a resource. He or she receives the first WO of the queue he or she is assigned to on the RF device, drives to the source bin of the first WT displayed on the RF device, picks the first HU from the source bin, and scans its label. He or she drops the HU at the staging area and scans the staging bin to confirm this step in the system. He or she proceeds in the same way with all requested HUs. 5. Load truck (SAP EWM) A warehouse worker begins to load the truck from the staging area. This step is carried out using an RF device. The warehouse worker chooses the equipment necessary for the loading, for example, a forklift truck and an RF device, and logs on as a resource. He or she scans the door bin to start the loading of the TU in the system. He or she then picks an HU from the staging area and scans its label. He or she loads the HU onto the truck and proceeds with the next HU until the staging area is empty. He or she checks for HUs from other areas that have not yet been loaded, for example, high-value or overdimensional cargo, and picks and loads these as well. With the last HU, the warehouse worker confirms the loading completion in SAP EWM. This triggers the sending of a loading notification message containing the loaded HUs to SAP TM. SAP TM updates the freight order and freight units. In this step, you can also print a road waybill in SAP TM (optional). 6. Truck leaves (SAP EWM) The truck leaves the door and the premises. The shipping office clerk confirms the departure from the checkpoint, and therefore from the door. SAP EWM posts the goods issue and sends a loading notification Process: Ship to Next Transit Warehouse 2015 SAP SE or an SAP affiliate company. All rights reserved. 10

11 message for departure from checkpoint to SAP TM. SAP TM updates the execution status of the freight order. Process: Ship to Next Transit Warehouse 2015 SAP SE or an SAP affiliate company. All rights reserved. 11

12 4 Configuration: This section describes the configuration necessary to run transit warehousing processes Receive from Shipper and Ship to Next Transit Warehouse with SAP Extended Warehouse Management (SAP EWM) in the first transit warehouse of the LCL Air Freight scenario of SAP Transportation Management (SAP TM). Note This section also contains configuration for additional transit warehouses in the LCL Air Freight scenario from SAP TM. In order to run both processes, you need to set up the configuration for the first transit warehouse only (warehouse numberjpty) of the LCL Air Freight scenario. The configuration described in this section is valid for a system landscape with SAP EWM, SAP TM, and SAP ERP installed on separate servers. Note In a system landscape with SAP EWM installed on the same server as SAP ERP or SAP TM, the configuration of logical systems, business systems, and Core Interface (CIF) transfer differs. For SAP EWM installed as Add-On to SAP ERP, see the configuration guide Integration of SAP ERP with SAP EWM. For SAP EWM installed on the same server as SAP TM, be aware that you use the same logical system and business system for SAP TM and SAP EWM, and that the transfer of master data from SAP ERP must only be set up once. 4.1 Prerequisites Installed Components You have installed and correctly configured the following applications: SAP EWM 9.3 SAP TM 9.3 EHP 7 for SAP ERP 6.0 or higher For more information, see the Master Guide for SAP EWM 9.0 on SAP Service Marketplace at Prerequisites for System Connection in SAP ERP, SAP TM and SAP EWM System administrators have to make specific settings for the integration of SAP ERP and SAP TM with SAP EWM before any customizing activity is carried out. Contact your system administrator to ensure the following prerequisites are met: An RFC user exists in each target system or client defined as an RFC destination in the examples below. For example, for the EWM test client to use the RFC destination for the ERP test client, an RFC user must exist in the ERP test client. RFC destinations exist for the corresponding ERP, EWM and TM clients. Create the following RFC destinations in Customizing for SAP NetWeaver under Application Server IDoc Interface/Application Link Enabling (ALE) Communication Create RFC Connections: In SAP ERP for SAP EWM, for exampleewmclnt001 (naming convention<sys>clnt<client>) In SAP TM for SAP EWM, for exampleewmclnt001 In SAP EWM for SAP TM, for exampletm1clnt001 Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 12

13 4.1.3 Configuration Guide for LCL Air Freight Scenario in SAP TM The Configuration Guide for LCL Air Freight scenario in SAP TM is already implemented, and the processes described in the LCL Air Freight scenario are already running with transit locations not managed by SAP EWM. 4.2 User Roles for SAP TM and SAP EWM The scenario contains process steps in SAP Transportation Management (SAP TM) and SAP Extended Warehouse Management (SAP EWM). You must assign the users in each system to specific user roles. If the process steps are performed by different users, you can use separate roles and users in each system, for example, a customer service agent, a transportation planner, and a capacity manager working exclusively in SAP TM, and a warehouse clerk working exclusively in SAP EWM. Standard roles available for this scenario: Role Name Application Description /SCWM/EXPERT SAP EWM Role for EWM Transactions /SCMTMS/TRANSPORTATION_MGR_V2 SAP TM Role for TM Transactions 4.3 Overview of SAP ERP Master Data The following master data is used in SAP ERP throughout the LCL Air Freight scenario. For information about how to create this data, see the configuration guide for the LCL Air Freight scenario in SAP TM. Customers and vendors created in SAP ERP are transferred via CIF to SAP TM, where they exist as locations and business partners. In this configuration guide you set up the transfer of this data via CIF to SAP EWM. Note The transfer of customers and vendors created in SAP ERP to SAP TM is described in the configuration guide for the LCL Air Freight scenario in SAP TM Customer Master Data in SAP ERP With the configuration of the LCL Air Freight scenario in SAP TM, you have created the following customer master data for shippers and consignees in SAP ERP. Check the entries on the SAP Easy Access screen for SAP ERP under Logistics Sales and Distribution Master Data Business Partner Customer Create Complete: Field/Value Shipper 1 Shipper 2 Shipper 3 Shipper 4 Consigne e 1 Consigne e 2 Consigne e 3 Consigne e 4 Customer ID Account Group Company Code Sales Organizatio n Distribution Channel OAF-CU- 01 KUNA: General Customer s OAF-CU- 02 KUNA: General Customer s OAF-CU- 03 KUNA: General Customer s OAF-CU- 04 KUNA: General Customer s OAF-CO- 01 KUNA: General Customer s OAF-CO- 02 KUNA: General Customer s OAF-CO- 03 KUNA: General Customer s OAF-CO- 04 KUNA: General Customer s Division Name Kanxinso n Wabei Electronic Japan Cable Samurai Fireworks Dosena Clothing Ten Media Soutwire Co. Scottsdal e Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 13

14 Clothing Co. LTD. s Factory LTD LTD Co. Factory Inc. Fireworks Inc. Street House Number Kioi-cho Denenchof u Kawabe Shirokan e State Route Stallard Pl West Main Street Alma School Road W N N Postal Code City Ota-ku Gifu Chiyodaku Minatoku Sedona Tucson Brawley Scottsdal e Region AZ AZ CA AZ Country JP JP JP JP US US US US Time Zone JAPAN JAPAN JAPAN JAPAN MSTNO MSTNO PST MSTNO Price Group Cust. pric. proc. Shipping Conditions Order Combinatio n Select Select Select Select Select Select Select Select Incoterm Incoterm Locations Terms of Payment (Sales area data) Tax Classificatio n Reconciliati on Account Terms of Payment Vendor Master Data for Carriers in SAP ERP With the configuration of the LCL Air Freight scenario in SAP TM, you have created the following customer master data for shippers and consignees in SAP ERP, Check the entries on the SAP Easy Access screen for SAP ERP under Logistics Materials Management Purchasing Master Data Vendor Central Create: Key Data: Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 14

15 Field/Value Carrier 1 Carrier 2 Carrier 3 Carrier 4 Carrier 5 Carrier 6 Carrier 7 Carrier 8 Vendor ID OAF- CR-03 OAF- CR-04 OAF- CR-05 OAF- CR-06 AF-JL- NRT AF-QF- NRT AF-JL- LAX AF-QF- LAX Company Code Purchasing Organization Account Group Addresses: Vendor ID Name Search Term Address OAF-CR-03 Uchida Trucking Truck Carrier JP Tome Nagi , , Ota-ku, Japan, Region 13 (Tokyo) OAF-CR-04 Ich-Ni Express Truck Carrier JP Hadaka-Jime 15, Nagoya, Japan, Region 23 (Aichi) OAF-CR-05 ACME Lines Truck Carrier US Beach Street 10, Long Beach, United States, Region CA First 355, OAF-CR-06 Desert Express 8848 Phoenix, Truck Carrier US Lines United States, Region AZ AF-JL-NRT AF-QF-NRT AF-JL-LAX AF-QF-LAX Accounting Information: Rising Sun Airlines Ltd. Oceanic Airways (Japan) KK Ltd. Rising Sun Airlines (US) Ltd. Oceanic Airways (US) KK Ltd. Air Carrier JP Air Carrier JP Air Carrier US Air Carrier US Higashi-shinagawa 2-chome, 4-11, , Tokyo, Japan, Region 13 (Tokyo) Toranomon 37th Mori Bldg 9F, , , Japan, Region 13 (Tokyo) 6041 W. Imperial Hwy # D, Los Angeles, California, United States 555 North Nash Street, Los Angeles, California, United States Vendor ID Reconciliation Account Cash Management Group OAF-CR A1 OAF-CR A1 OAF-CR A1 OAF-CR A1 AF-JL-NRT A1 Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 15

16 AF-QF-NRT A1 AF-JL-LAX A1 AF-QF-LAX A1 Payment Transactions Accounting: Vendor ID Payment Terms OAF-CR OAF-CR OAF-CR OAF-CR AF-JL-NRT 0002 AF-QF-NRT 0002 AF-JL-LAX 0002 AF-QF-LAX 0002 Purchasing Data: Field/Valu e Vendor ID Order Currency Terms of Payment Carrier 1 Carrier 2 Carrier 3 Carrier 4 Carrier 5 Carrier 6 Carrier 7 Carrier 8 OAF-CR- 03 OAF-CR- 04 OAF-CR- 05 OAF-CR- 06 AF-JL- NRT AF-QF- NRT AF-JL- LAX AF-QF- LAX JPY JPY USD USD JPY JPY USD USD Incoterms Purchase Group Planned Delivery Time Conf. Control Shipping Condition Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 16

17 Configuration in SAP ERP In this section, you set up the communication between SAP ERP and SAP EWM for the transfer of master data, such as vendors and customers, via CIF to SAP EWM. Important Skip this section if you have implemented the configuration guide Integration of SAP ERP with SAP EWM in your SAP ERP and SAP EWM systems as the settings already exist Activating Business Transaction Events (BTE) in SAP ERP Prerequisites You have authorizations for cross-client settings on user and client level. 1. Activate online transfer using BTEs in Customizing for Integration with Other SAP Components under Advanced Planning and Optimization Basic Settings for the Data Transfer Change Transfer Change Transfer for Transaction Data Activate Online Transfer Using BTE. 2. Select the ND-APO (New Dimension Plug-In APO) and NDI (New Dimension Integration) checkboxes. 3. Save your changes Configuring Logical Systems in SAP ERP Prerequisites You have authorizations for cross-client settings on user and client level. 1. Define a logical system for your ERP client (for example,erpclnt001) and a logical system for your EWM client (for example,ewmclnt001) in Customizing for Integration with Other SAP Components under Extended Warehouse Management Basic Settings for Setting Up the System Landscape Name Logical System. 2. Assign the ERP logical system defined in the first step to the ERP client (for example, in SAP ERP, assign ERPCLNT001 to client 001) in Customizing for Integration with Other SAP Components under Extended Warehouse Management Basic Settings for Setting Up the System Landscape Assign Logical System to a Client. 3. In SAP ERP, specify the system type and release of the EWM logical system defined in the first step. In Customizing for Integration with Other SAP Components under Extended Warehouse Management Basic Settings for Setting Up the System Landscape Specify SAP APO Release, enter the values as shown in the following table for the EWM logical system: Field Log. System Syst. Type Release Value <Logical System>, for exampleewmclnt001 SAP_SCMB <System Release>, for example7.13 (or higher) Assigning EWM Logical System to RFC Destination in SAP ERP Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 17

18 In Customizing for SAP NetWeaver, choose Application Server IDoc Interface/Application Link Enabling (ALE) Communication Determine RFC Destinations for Method Calls. 2. Select the EWM logical system, for example,ewmclnt Choose Standard BAPI destination. 4. Enter the RFC destination created by your system administrator for the corresponding SAP EWM system, and choose Enter. 5. Save your entries Configuring qrfc Destination in SAP ERP This setting is relevant for the qrfc communication from SAP ERP to SAP EWM. 1. Register the RFC destination for SAP EWM in the QOUT scheduler in SAP ERP. a. In SAP ERP, on the SAP Easy Access screen, call transactionsmqs. b. On the qrfc Monitor (QOUT Scheduler) screen, choose Register without activation. This means that the queue is not triggered immediately by the Outbound Scheduler. c. Enter the data as shown in the following table: Field Destination Value Max. Conn. 10 Max. Runtime 60 <RFC Destination>, for exampleewmclnt001 W/o trfc d. Choose Continue Leave this field empty 2. Set the queue type for the communication of master data by means of CIF from SAP ERP to SAP EWM. a. In Customizing for Integration with Other SAP Components, choose Extended Warehouse Management Basic Settings for Setting Up the System Landscape Set Target System and Queue Type. b. Create an entry for the EWM logical system with the following data: Field Log. System Q-Type Value <Logical System>, for exampleewmclnt001 I (Inbound Queues) Note The Operation Mode field is automatically filled by the system when you generate, activate, or deactivate CIF integration models. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 18

19 Configuration in SAP EWM Activating Business Functions in SAP EWM You use this procedure to activate the business functions required for using transit warehousing processes in SAP Extended Warehouse Management (SAP EWM). Carry out these steps in an SAP EWM client that allows cross-client settings and the creation of workbench requests. If necessary, use the workbench request to transport the settings to other SAP EWM systems. 1. On the SAP Easy Access screen for SAP EWM, enter transaction SFW5. 2. Check the following business functions and, if necessary, activate them Business Function Description SCM_EWM_FND EWM, Essential Foundation Functions FND_SOA_REUSE_1 Improvements for SOA Reuse Functions /BCV/MAIN FND, Business Context Viewer Main Application /BCV/MAIN_1 FND, Business Context Viewer Main Application 2 /BCV/NWBC_SIDEPANEL FND, Business Context Viewer NWBC Side Panel (Reversible) Configuring Logical Systems in SAP EWM Prerequisites You have authorizations for cross-client settings on user and client level. 1. Define a logical system for your ERP client (for example,erpclnt001), a logical system for your EWM client (for example,ewmclnt001), and a logical system for your TM client in Customizing for Integration with Other SAP Components under Extended Warehouse Management Basic Settings for Setting Up the System Landscape Name Logical System: Logical System ERPCLNT001 EWMCLNT001 TM1CLNT001 Name ERPCLNT001 EWMCLNT001 TM1CLNT Assign the EWM logical system defined in the first step to the EWM client (for example, in SAP EWM, assign EWMCLNT001 to client 001) in Customizing for Integration with Other SAP Components under Extended Warehouse Management Basic Settings for Setting Up the System Landscape Assign Logical System to a Client Assigning Logical System to RFC Destination in SAP EWM 1. In Customizing for SAP NetWeaver, choose Application Server IDoc Interface/Application Link Enabling (ALE) Communication Determine RFC Destinations for Method Calls. 2. Select the ERP logical system, for example,erpclnt001. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 19

20 Choose Standard BAPI destination. 4. Enter the RFC destination created by your system administrator for the corresponding SAP ERP system and choose Enter. 5. Select the TM logical system, for example,tm1clnt Choose Standard BAPI destination. 7. Enter the RFC destination created by your system administrator for the corresponding SAP ERP system and choose Enter. 8. Save your entries Configuring Business Systems You use this procedure to define the business systems for SAP TM, SAP ERP, and SAP EWM in SAP EWM, and to assign a business system to the client. Note The settings cannot be transported from a Customizing client to other systems and clients. Therefore, you must repeat the steps in every EWM client connected to SAP ERP and SAP TM. Carry out the following steps in each EWM client you want to connect to SAP ERP and SAP TM. 1. In Customizing for Extended Warehouse Management under Interfaces ERP Integration General Settings Define Business Systems, define a business system for the ERP client, the TM client, and the EWM client: Business System Logical System Manual Maint. ERP_001 ERPCLNT001 Flag is Not Set EWM_001 EWMCLNT001 Flag is Not Set TM1_001 TM1CLNT001 Flag is Not Set Note If you use the System Landscape Directory (SLD), the entries already exist. In this case, no action is required in this step. 2. In Customizing for Extended Warehouse Management under Interfaces ERP Integration General Settings Define Own Business Systems, enter the EWM business system defined in the first step as your own business system (for example, in system SAP EWM, client 001, enter EWM_001) Configuring Business System Group You use this procedure to define the business system group for SAP ERP, SAP TM, and SAP EWM in SAP EWM, and assign the logical systems to the business system group. The business system group is used for the CIF transfer of master data from SAP ERP to SAP EWM. As SAP TM, SAP EWM, and SAP ERP share the same master data, you define the same business system group for all the systems. Note The settings cannot be transported from a Customizing client to other systems and clients. Therefore you must repeat the steps in every EWM client connected to SAP ERP and SAP TM. Carry out the following steps in each EWM client you want to connect to SAP ERP and SAP TM. 1. Define a business system group for the ERP client in Customizing for SCM Basis under Integration Basic Settings for Creating the System Landscape Maintain Business System Group. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 20

21 ... BusSystGrp BG1 Description Business System Group TM & EWM & ERP 2. Assign the logical systems for SAP ERP and SAP EWM and a queue type to the business system group in Customizing for SCM Basis under Integration Basic Settings for Creating the System Landscape Assign Logical System and Queue Type. BusSystGrp Logical system SAP Ind. Release Queue Type Err. Hndlg Role BG1 EWMCLNT001 X 70 (or higher) BG1 TM1CLNT001 X 9.00 (or higher) BG1 ERPCLNT001 X 700 (or higher) I Inbound Queue I Inbound Queue I Inbound Queue Strict (Terminate at Errors) Strict (Terminate at Errors) Strict (Terminate at Errors) Not Specified Not Specified Not Specified Note The release for the EWM logical system relates to the installed component SCM_BASIS and not to the EWM component. Note You can keep the default setting for the Error Handling in Target System field Configuring qrfc Destination in SAP EWM You use this setting to configure the inbound queues in SAP EWM. This is relevant for the qrfc communication from SAP ERP to SAP EWM, as well as for the XI communication from SAP TM to SAP EWM. 1. Register the queue names in the QIN scheduler to configure the execution of inbound queues in SAP EWM. a. In the SAP EWM system, on the SAP Easy Access screen, call transactionsmqr. b. On the qrfc Monitor (QIN Scheduler) screen, choose Register without activation. This means that the queue is not triggered immediately, because the scheduler is inactive. c. Enter the data as shown in the following table: Field Queue Name Mode Value Max. Runtime 60 <used queue name>, we recommend that you use either* or the following queue names:cf*,wm*,x* D USERDEST Attempts 30 Pause 300 Scheduler Monitoring 0 d. Choose Continue Leave this field empty 2. Register display programs for the inbound queue in SAP EWM. This function enables you to display the data of a queue entry by double-clicking the queue name, or to display the application log of a queue entry by double-clicking the status text in the qrfc monitor for inbound queues. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 21

22 ... a. In SAP EWM, on the SAP Easy Access screen, call transactionsmqe. b. Choose Edit Register Display Program. c. Enter the queue and program names as shown in the following table: Queue Name CF* WM* Program Name CIFQEV02 (in case of EWM as Add-On to ERP) or /SAPAPO/CIF_QUEUE_EVENT2 (in the case of EWM as Add-On to SCM) /SCWM/QRFC_APPL_LOG_DISPLAY X* RSXMB_SHOW_ENTRY Activating the Planning Version and Model for Master Data You use this procedure to create a planning version 000 and a model 000 for the creation of master data in SAP EWM. This technical setting is required for the CIF communication. Carry out the following step in each EWM client you want to connect to SAP ERP: In SAP EWM, on the SAP Easy Access screen, call transaction/sapapo/actvercreate. The system informs you whether the planning version and model already exist, or if the system just created them. Important Transaction/SAPAPO/ACTVERCREATE requires an authorization for objects C_APO_MOD and C_APO_VERS with activity 01. You can use transactionsu53 to check failed authorization checks after report execution Activating BC Sets in SAP EWM You use this procedure to activate Business Configuration (BC) sets in SAP EWM. The BC sets contain Customizing settings at client level or at warehouse level. Important In order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, you need to activate the warehouse-dependent BC sets in warehousejpty only. In order to manage all transit warehouses of the scenario with SAP EWM, activate the warehousedependent BC sets in all the warehouses:jpty,jpnr,jpng,usla,ussa, andusph. 1. On the SAP Easy Access screen for SAP EWM, choose Tools Customizing Business Configuration Sets Activation of BC Sets (or use transactionscpr20). 2. Activate the following BC sets in the given sequence: Name BC Set Description Comment /SCWM/TW_10_10 TW Basic Settings (Client) - 10 BC set at client level /SCWM/TW_10_20 TW Basic Settings (Client) - 20 BC set at client level /SCWM/TW_15_90 TW Number Range Int. for Basic Settings (Client) Gen. BC set at client level Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 22

23 /SCWM/TW_20_10 TW Settings (Warehouse) 10 Enter the currency used in your warehouse, for example,jpy /SCWM/DLV_BASIC_NUMBER RANGE /SCWM/DLV_INBOUND_TW /SCWM/DLV_OUTBOUND_TW /SCWM/TW_20_15 Delivery in EWM - Number Ranges Inbound Process for Transit Warehouse Outbound Process for Transit Warehouse TW Number Range Int. for Basic Settings (Warehouse) Gen. Enter the factory calendar used in your warehouse, for example,jp Enter your warehouse number, for example,jpty BC set at client level. For more information, see the BC set documentation BC set at client level For more information, see the BC set documentation BC set at client level For more information, see the BC set documentation Enter your warehouse number, for example,jpty /SCWM/TW_20_20 TW Settings (Warehouse) 20 Enter your warehouse number, for example,jpty /SCWM/TW_25_91 /SCWM/SR_SCO_BCV (optional) /SCWM/TW_BCV (optional) TW Number Range Int. for Basic Settings (Warehouse) HU Configuration for Business Context Viewer - Shipping Cockpit Measurement Services for TW in Sidepanel a. For each BC set, press Activate BC Set Enter a number in the From number field, for example, In the Number range object subobject value field, enter your warehouse number, for example,jpty, Enter a number in the To number field, for example, If you activate the BC set in several transit warehouses, enter disjunctive internal HU number ranges for each transit warehouse. Otherwise a warehouse cannot receive an HU with a number given by another warehouse. BC set at client level To use side panels in the transit warehousing screens, activate this BC set. Enter your warehouse number, for example,jpty To use side panels in the transit warehousing screens, activate this BC set. b. Enter the variables to be used by the BC set during activation (see column Comment above) c. Press Copy Values Configuring Action Profiles for TU and Vehicle You use this procedure to activate action definitions for transportation units (TUs) and vehicles. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 23

24 Note For performance purposes, SAP recommends deactivating the PPF actions that are not needed for the business scenario, as shown in the tables below. However, you should not deactivate a PPF action if you use it in other scenarios or processes. 1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Shipping and Receiving Message Processing Define Action Profiles for Vehicles. 2. Select the action profile/scwm/tu and choose Action Definition in the dialog structure. 3. Choose Edit. 4. Activate actions/scwm/sr_send_tu_ldap_noti, /SCWM/SR_TU_CREATE_STAGING_WT and /SCWM/SR_TU_PRINT_HU_LABEL. 5. Deactivate the other PPF actions, unless you use them in other scenarios or processes, as shown in the following table: Action Definition /SCWM/BIF_TAPP_CANCELLED_NOTI X /SCWM/BIF_TAPP_CHANGED_NOTI X /SCWM/BIF_TAPP_CREATED_NOTI X /SCWM/SR_PRINT_TU_WAYBILL X /SCWM/SR_SEND_SHIPPL X /SCWM/SR_SEND_SHPMNT X /SCWM/SR_SEND_TU X /SCWM/SR_SEND_TU_FINAL X /SCWM/SR_SEND_TU_FINAL_CANCEL X /SCWM/SR_SEND_TU_LDAP_NOTI - /SCWM/SR_SET_TU_SYNC_DLV X /SCWM/SR_TU_CREATE_STAGING_WT - /SCWM/SR_TU_HU_TO_CREATE X /SCWM/SR_TU_PRINT_HU_LABEL - PRINT_LOADLISTTU X 6. Save your changes and choose Back (F3). 7. Select the action profile/scwm/veh and choose Action Definition in the dialog structure. 8. Choose Edit. 9. Activate action/scwm/sr_send_veh_ldap_noti. Inactive 10. Deactivate the other PPF actions, unless you use them in other scenarios or processes, as shown in the following table: Action Definition Inactive /SCWM/BIF_VAPP_CANCELLED_NOTI X /SCWM/BIF_VAPP_CHANGED_NOTI X /SCWM/BIF_VAPP_CREATED_NOTI X /SCWM/SR_PRINT_VEH_WAYBILL X /SCWM/SR_SEND_SHIPPL_VEH X /SCWM/SR_SEND_VEH X /SCWM/SR_SEND_VEH_FINAL_LOAD X /SCWM/SR_SEND_VEH_LDAP_NOTI - PRINT_LOADLISTVEH X 11. Save your entries Configuring Action Conditions for Transportation Unit You use this procedure to assign an output device to action definition /SCWM/SR_TU_PRINT_HU_LABEL. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 24

25 In Customizing for Extended Warehouse Management, choose Cross-Process Settings Shipping and Receiving Message Processing Define Action Conditions for Transportation Units. 2. Select the action profile /SCWM/TU and choose the action definition /SCWM/SR_TU_PRINT_HU_LABEL. 3. Choose Edit. 4. On the Processing Details tab page, enter the output devicelp Save your changes Checking Action Profiles for HU You use this procedure to activate action definitions for handling units (HUs). They are used for sending messages to SAP Transportation Management. 1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Handling Units Basics Print Define PPF Action Profiles. 2. Select the action profile/scwm/hu_tw and choose Action Definition in the dialog structure. 3. Choose Edit. 4. Check that actions/scwm/hu_tw_notify_tm_in and/scwm/hu_tw_notify_tm_out are active. If not, activate them Activating Error and Conflict Handler in SAP EWM You use this procedure to activate the error and conflict handling in service operations. This enables you to access detailed information about XI messages with errors in Monitor for Processed XML Messages (transaction SXI_MONITOR) and to process the messages after error resolution. 1. In Customizing for Extended Warehouse Management, choose Cross-Application Components Processes and Tools for Enterprise Applications Enterprise Services Error and Conflict Handler Activate Error and Conflict Handler. 2. Check whether the Activated checkbox is selected. 3. If the checkbox is not selected, choose New Entries. 4. In the Activate FEH for Clients screen area, select the Activated checkbox. 5. Save your entries Defining Work Center Layout to Display Planned HUs You use this procedure to create a work center layout for transaction Maintain Planned Shipping Handling Units (transaction/scwm/cap). Note Transaction Maintain Planned Shipping Handling Units is not required for transit warehousing processes, but can be used in the implementation phase for checking the system configuration or the data consistency. Therefore, the following setting is optional, but recommended. 1. In Customizing for Extended Warehouse Management, choose Master Data Work Center Specify Work Center Layout. 2. Create the following entry for your warehouse number, for example, JPTY: Warehouse Number Work Center Layout Description Transaction Type JPTY CAP Cartonization in Transit Whse 9 Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 25

26 Save your entry. 4. In Customizing for Extended Warehouse Management, choose Goods Issue Process Cartonization Planning Configure Cartonization Planning on Warehouse Number Level. 5. Create the following entry for your warehouse number: Warehouse Number Determination Layout JPTY 6. Save your entry CAP Result You can now use transaction/scwm/cap to display planned HUs created in transit warehousing processes by entering CAP Process Profile= space (explicitly use single value = by double-clicking on the entry field) in addition to the selection criteria for your transit warehousing delivery. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 26

27 Settings and Master Data in SAP ERP Preparing Initial Transfer of Master Data from SAP ERP You use this procedure to prepare the transfer of master data from SAP ERP to SAP EWM. In SAP ERP, you activate the immediate transfer of master data changes by means of business transaction events (BTEs). This means that changes to existing master data records are transferred immediately to SAP EWM. You generate a runtime version of the active integration model for performance purposes. The runtime version is adjusted after each activation or deactivation of integration models. For more information, see the documentation of the reportrcifimax. 1. Configure change transfer of master data using BTEs in Customizing for Integration with other SAP Components under Extended Warehouse Management Basic Settings for Data Transfer Change Transfer for Master Data Configure Change Transfer for Master Data. Enter the value2 (BTE Transfer, Immediately) in the following fields: Material Master Change Transfer Change Transfer for Customers Change Transfer for Vendors 2. Generate the runtime version of the active integration model. a. On the SAP Easy Access screen, choose Tools ABAP Workbench Development ABAP Editor. b. In the Program field, enterrcifimax and choose Execute. c. In the Action to Execute screen area, choose Generation and then Execute Transferring Master Data from SAP ERP using CIF You use this procedure to transfer master data from SAP ERP to SAP EWM. To transfer data using CIF, you first create an integration model. In the integration model, you define the selection criteria for the data. You activate the integration model manually. When you activate the model, the data is transferred. Once the data is contained in an active integration model, every change is communicated immediately to SAP EWM, as you have already activated the online transfer using BTE in the previous chapter, Carry out the following steps in the ERP client in which you create master data for SAP EWM: 1. Create an integration model (for example:imewmtw1) : a. On the SAP Easy Access screen for SAP ERP, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Create, or start transactioncfm1 b. Enter the following data: Modelname Logical System APO Application Customers Vendors Create Loc./BP IMEWMTW1 EWMCLNT001 EWM X X 2 c. Select the customers you want to transfer to SAP EWM, for example, by entering OAF* in the Customer field. d. Select the vendors you want to transfer to SAP EWM, for example, by entering OAF* in the Vendor field. e. Save the model as a variant, for example,vimewmtw1, and go back to the selection screen. f. Press Execute. 2. Activate the integration model manually: Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 27

28 ... a. On the SAP Easy Access screen for SAP ERP, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Create, or start transactioncfm2. b. Select the integration model you just created and press Activate. Note If you activate a model for the first time in a client, the system proposes in a dialog box to create a number range interval for the object CIF_LOAD automatically. Accept the proposal. c. Press Start Scheduling Background Job for Master Data Transfer To transfer master data that will be created in the future, you plan the transfer as a regular job. Carry out the following steps in the ERP client in which you create master data for SAP EWM: 1. Create a variant for programrimoddel: a. On the SAP Easy Access screen, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Delete. b. Enter the integration model, logical system, and APO application you changed in step 1. c. Select the Select Inactive IMs Only checkbox. d. Save as a variant, for example, VIMEWMTW1. 2. Create a variant for programrimodac2: a. On the SAP Easy Access screen, call transaction CFM3. b. Enter the integration model, logical system, and APO application you changed in step 1. c. Select the following checkboxes: Ignore Faulty Queue Entries Do Not Issue Warning in Case of Parallel CIF Load d. Save as a variant, for example, VIMEWMTW1. 3. Define a background job for programsrimoddel,rimodgen, andrimodac2. In this example, the job runs hourly. a. On the SAP Easy Access screen, in the menu, choose System Services Jobs Define Job. b. Enter the name of the job, for example,ewmcif_jpty (naming convention: EWMCIF_<warehouse>). c. Create step number 1 by choosing Step. i. In the ABAP program screen area, enter programrimoddel and variantvimewmtw1. ii. Save your entries. The Step List Overview screen appears. d. Create step number 2 by choosing Create. i. In the ABAP program screen area, enter programrimodgen and variantvimewmtw1. ii. Save your entries. The Step List Overview screen appears. e. Create step number 3 by choosing Create. i. In the ABAP program screen area, enter programrimodac2 and variantvimewmtw1. ii. f. Go back. Save your entries. The Step List Overview screen appears. g. Choose Start Condition. The Start Time screen appears. h. Choose Date/Time. i. Enter the scheduled start date and time. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 28

29 j. Select the Periodic job checkbox. k. Choose Period values. The Period Values screen appears. l. Select, for example, Hourly and save. m. On the Start Time screen, save your entries. n. On the Define Background Job screen, save your entries. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 29

30 Configuration in SAP TM In addition to the configuration of the LCL Air Freight scenario in SAP TM, some settings are required in SAP TM for managing a transit warehouse with SAP EWM Assigning Warehouse Number to Location You use this procedure to assign an SAP EWM warehouse number to a transit warehouse location in SAP TM. Important For the transit warehousing processes Receive from Shipper and Ship to Next Transit Warehouse, this setting is necessary for location OAF-STA-JPTYO only. 1. In SAP NetWeaver Business Client for SAP TM, choose Master Data Transportation Network Locations Define Location. 2. Enter the location and location type as described in the table below and press Enter. 3. Choose tabstrip TM. 4. Enter the target system for SAP EWM and the warehouse number: Location Location Type SAP EWM Target System SAP EWM Warehouse Number OAF-STA-JPTYO 1002 EWMCLNT001 JPTY OAF-STA-JPNGO 1002 EWMCLNT001 JPNG AF-GW-JPNRT 1150 EWMCLNT001 JPNR AF-GW-USLAX 1150 EWMCLNT001 USLA OAF-STA-USPHX 1002 EWMCLNT001 USPH OAF-STA-USSAN 1002 EWMCLNT001 USSA 5. Save your changes Transferring Locations and Business Partners from SAP TM to SAP EWM You use this procedure to transfer to SAP EWM the locations and business partner for all locations of the transportation network created manually in SAP TM. Report/SCMTMS/BUPA_SEND_TRANS_WH creates locations and business partners in SAP EWM. Note As warehouse numberjpty is assigned to locationoaf-sta-jptyo in SAP TM, the report automatically assigns the location (as a supply chain unit) to the warehouse numberjpty in SAP EWM, if the warehouse number does not have a supply chain unit yet. 1. In SAP TM, start transactionse38, enter program/scmtms/bupa_send_trans_wh, and press Execute. 2. Select the locations of the transportation network: Location AF-GW-JPNRT AF-GW-USLAX Description Gateway Airport Narita Gateway Airport Los Angeles Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 30

31 Refer OAF-STA-JPNGO OAF-STA-JPTYO OAF-STA-USPHX OAF-STA-USSAN FH Station Nagoya FH Station Tokyo FH Station Phoenix FH Station San Diego 3. Enter the logical system of SAP EWM, for exampleewmclnt001, in field Logical Target System. 4. Press Execute. 5. Check that the business partners and locations were transferred correctly to SAP EWM, as described in Checking Business Partners of Transportation Network and Checking Locations of Transportation Network.. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 31

32 Settings and Master Data in SAP EWM Checking Business Partners of Transportation Network The following table gives an overview of the business partners used for the transportation network of the LCL Air Freight scenario. In this procedure, you check that the business partners created manually in SAP TM and transferred to SAP EWM with report/scmtms/bupa_send_trans_wh are available in SAP EWM. Field/Value Business Partner ID BP Role Business Partner 1 Business Partner 2 Business Partner 3 Business Partner 4 Business Partner 5 OAF-FWH-05 OAF-FWH-01 AF-FWH-03 AF-FWH-20 OAF-FWH- 22 Business Partner Gen. Business Partner Gen. Business Partner Gen. Business Partner Gen. Name FH Tokyo FH Nagoya Gateway Narita Gateway Los Angeles Search Term 1/2 Street/Hous e number Postal Code/City FWH STATION/JP /Toky o FWH STATION/JP 8-3 Kanayama Cho /Nagoy a FWH Gateway/JP Building /Narit a FWH Gateway/U S Spectrum Drive 92602/Irvin e Business Partner Gen. FH San Diego FWH STATION/U S Niels Bohr Court /San Diego Country JP JP JP US US US Region CA CA AZ Business Partner 6 OAF-FWH- 21 Business Partner Gen. FH Tempe FWH STATION/U S South Hardy Drive Shiba/ /Temp e Time Zone JAPAN JAPAN JAPAN PST PST MSTNO 1. On the SAP Easy Access screen for SAP EWM, choose Master Data Maintain Business Partner. 2. Check that the business partners exist in SAP EWM Checking Locations of Transportation Network The following table gives an overview of the locations used for the transportation network of the LCL Air Freight scenario. In this procedure, you check that the locations created manually in SAP TM and transferred to SAP EWM with report/scmtms/bupa_send_trans_wh are available in SAP EWM. Field/Value Location1 Location 2 Location 3 Location 4 Location 5 Location 6 Location OAF-STA- OAF-STA- AF-GW- AF-GW- OAF-STA- OAF-STA- JPTYO JPNGO JPNRT USLAX USPHX USSAN Description FH Station Tokyo FH Station Nagoya Gateway Airport Narita Gateway Airport Los FH Station Phoenix FH Station San Diego Angeles Location Type Ext. Location OAF-STA- JPTYO OAF-STA- JPNGO AF-GW- JPNRT AF-GW- USLAX OAF-STA- USPHX OAF-STA- USSAN Bus.System Group BG1 BG1 BG1 BG1 BG1 BG1 Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 32

33 Time Zone JAPAN JAPAN JAPAN PST MSTNO PST Search Term FH Station FH Station Gateway Narita Gateway LAX FH Station FH Station Address Shiba, Minatoku, Tokyo, Kanayama Cho 1, Nagoya, Building 727-5, Narita Airport, Spectrum Drive, Building 1755,Irvi ne, South Hardy Drive, Tempe, Niels Bohr Court, San Diego, Country JP JP JP US US US Region CA AZ (Tokyo) (Chiba) (Californ (Arizona) CA (Californ ia) ia) IATA Code - - NRT LAX - - UN/LOCODE JPTYO JPNGO JPTYO USLAX USPHX USSAN Business OAF-FWH- OAF-FWH- AF-FWH-03 AF-FWH-20 OAF-FWH- Partner For each location, the following geo-coordinates should be available Location Longitude Latitude OAF-STA-JPTYO + 139: 30: : 45: 00 OAF-STA-JPNGO + 137: 15: : 00: 00 AF-GW-JPNRT + 140: 23: : 45: 53 AF-GW-USLAX - 118: 24: : 45: 53 OAF-STA-USPHX 112: 05: : 33: 31 OAF-STA-USSAN - 119: 30: : 30: 00 OAF-FWH On the SAP Easy Access screen for SAP EWM, choose SCM Basis Master Data Location Location. 2. Check that the locations exist in SAP EWM Maintaining Supply Chain Units for Transit Warehouses The locations of the transportation network transferred from SAP TM to SAP EWM also exist as supply chain units in SAP EWM. In this procedure, you maintain attributes for the supply chain units in order to use them as transit warehouse, receiving office, and shipping office in SAP EWM. Important In order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, you need to maintain supply chain unitoaf- STA-JPTYO only. 1. On the SAP Easy Access screen for SAP EWM, choose Master Data Maintain Supply Chain Unit. 2. Choose tab strip Alternative and enter the following business attributes for the supply chain units of your transit warehouses: Supply Chain Unit OAF-STA-JPTYO OAF-STA-JPNGO AF-GW-JPNRT AF-GW-USLAX OAF-STA-USPHX OAF-STA-USSAN 3. Save your entries Business Attributes INV, PLOC, RO, SO INV, PLOC, RO, SO INV, PLOC, RO, SO INV, PLOC, RO, SO INV, PLOC, RO, SO INV, PLOC, RO, SO Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 33

34 Maintaining Logical Conditions for Bin Determination You use this procedure to create logical conditions for bin determination. Note For more information about the condition records for bin determination, see Appendix C: Condition Records for Bin Determination. 1. On the SAP Easy Access screen for SAP EWM, choose Extended Warehouse Management -> Settings -> -> Maintain Logical Conditions for Bin Determination (or use transaction /SCWM/PUT_TW_WT_TWP5). 2. Create the following entries: Logical Condition Description Formula PC_JPTY_10_25 PC_JPNG_10_25 PC_JPNR_10_25 PC_JPTY_25_50 PC_JPNG_25_50 PC_JPNR_25_50 PC_JPTY_50_75 PC_JPNG_50_75 PC_JPNR_50_75 PC_JPTY_OTHER PC_JPNG_OTHER PC_JPNR_OTHER 3. Save your entries. 4. Create the following entries: PC_JPTY_10_25 PC_JPNG_10_25 PC_JPNR_10_25 PC_JPTY_25_50 PC_JPNG_25_50 PC_JPNR_25_50 PC_JPTY_50_75 PC_JPNG_50_75 PC_JPNR_50_75 PC_JPTY_OTHER PC_JPNG_OTHER PC_JPNR_OTHER Logical Condition Description Formula PC_USLA_80_86 PC_USSA_80_86 PC_USPH_80_86 PC_USLA_86_90 PC_USSA_86_90 PC_USPH_86_90 PC_USLA_90_93 PC_USSA_90_93 PC_USPH_90_93 PC_USLA_OTHER PC_USSA_OTHER PC_USPH_OTHER 5. Save your entries. PC_USLA_80_86 PC_USSA_80_86 PC_USPH_80_86 PC_USLA_86_90 PC_USSA_86_90 PC_USPH_86_90 PC_USLA_90_93 PC_USSA_90_93 PC_USPH_90_93 PC_USLA_OTHER PC_USSA_OTHER PC_USPH_OTHER &Cons. Postal Code& >= and &Cons. Postal Code& <= &Cons. Postal Code& > and &Cons. Postal Code& <= &Cons. Postal Code& > and &Cons. Postal Code& <= &Cons. Postal Code& > &Cons. Postal Code& >= and &Cons. Postal Code& <= &Cons. Postal Code& > and &Cons. Postal Code& <= &Cons. Postal Code& > and &Cons. Postal Code& <= &Cons. Postal Code& < and &Cons. Postal Code& > Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 34

35 Checking Assignment of Supply Chain Unit to Warehouse Number You use this procedure to check the assignment of a supply chain unit to your transit warehouse. Important In order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, an entry is required for warehouse numberjpty only. As warehouse number JPTY is assigned to location OAF-STA-JPTYO in SAP TM, report /SCMTMS/BUPA_SEND_TRANS_WH has automatically assigned the location (as a supply chain unit) to the warehouse number JPTY in SAP EWM, if the warehouse number did not have a supply chain unit yet. If a supply chain unit was already assigned to the warehouse number, the report did not update the assignment. In this case, the warehouse number uses a supply chain unit that differs from the location used in SAP TM. 1. On the SAP Easy Access screen for SAP EWM, choose Extended Warehouse Management Settings Assignments: Warehouse Numbers/Business Partners Assign Warehouse Numbers. 2. Check that a supply chain unit is assigned to your transit warehouse. If the assignment was created automatically by report/scmtms/bupa_send_trans_wh, the following supply chain units are assigned to the transit warehouses: Warehouse Number Supply Chain Unit Custodian JPTY OAF-STA-JPTYO - - JPNG OAF-STA-JPNGO - - JPNR AF-GW-JPNRT - - USLA AF-GW-USLAX - - USPH OAF-STA-USPHX - - USSA OAF-STA-USSAN - - Default Party Entitled to Dispose Creating Warehouse Structure and Condition Records for Bin Determination You use this procedure to create or maintain the following objects related to the warehouse structure of a transit warehouse automatically in SAP EWM: Storage bins Staging area and door determination Bin assignment for work centers Condition records for bin determination For this purpose, you use the BDC files attached to SAP Note Note In order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, you need to process BDC files related to warehouse numberjpty only. Note The same warehouse structure can be used for all transit warehouses across the transportation chain of the LCL Air Freight scenario. However, the bins created in some storage types are not Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 35

36 needed in all locations. For example, areas used for loading and unloading HU containers are only required in warehouses representing a gateway.... Implement the steps described in SAP Note Result You have created a warehouse structure that is typical for transit warehouses. The warehouse layout and the condition records for bin determination are meant as examples and illustrate several configuration options for the warehouse-internal processing, such as: Putaway to bins with limited or unlimited bin capacities Putaway to bins using document references, such as forwarding order reference, as consolidation groups Putaway to bins for single or multiple destination countries, regions, or postal codes Setup with or without a separate staging step before loading Note For more information about the condition records for bin determination, see Appendix C: Condition Records for Bin Determination. The following figure shows the warehouse layout you created with the BDC files, and is followed by a legend explaining the different elements of the warehouse layout: Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 36

37 Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 37

38 Legend Layout Storage Type Storage Type Description Use and Structure H040 Area for Dangerous Goods Used to store dangerous goods. Bin capacity for cargo that is not overdimensional. Cargo is stored together in storage sections by dangerous goods regulation and dangerous goods class. One section is for dangerous goods of regulation ADR class 1 and one section is for all other dangerous goods. Putaway is to bins with the same consolidation group (for example, consolidation by forwarding order) or next empty bin, depending on capacity and consolidation groups. Due to setup with capacity and putaway rule using consolidation group, a corresponding overflow bin is setup (see storage type H980 Overflow Zones). Cargo in this area is staged before physical loading. H050 Area for High Value Cargo Used to store high-value cargo in a special area in the warehouse with limited access. Bin capacity for cargo that is not overdimensional. No storage sections. Putaway is to bins with the same consolidation group (for example, consolidation by forwarding order) or next empty bin, depending on capacity and consolidation groups. Due to setup with capacity and putaway rule using consolidation group, a corresponding overflow bin is setup (see storage type H980 Overflow Zones). Cargo in this area is not staged before physical loading, in order to reduce the time in which the cargo is not in the limited access area. Note that if you load a transit HU from this area, the bins are still reserved until the TU has left the warehouse. H910 Staging Areas Inbound and Outbound Used for receiving HUs or HU containers. Bins are assigned to one or several doors. Some dedicated bins, GR-01 GR-05, are assigned to single doors that are used in inbound processes only, intended for the receiving of transit HUs from shipper. Bins are used as goods movement bin upon receiving. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 38

39 H920 H921 H922 Area by Postcode and Region Area by Country Bins by Shipment Area for Unloading from HU Container No capacity limitations. Used for cargo that is to be delivered to a final destination within same country or region as the one of the warehouse. Cargo with the following final destination is stored together: - The same region - The same group of regions - The same postal code ranges For this purpose, several storage sections exist: - For special regions - For all other regions - For storage by postal code range No capacity limitations. Cargo in this area is not staged before physical loading. The bins are already next to the doors that will be assigned to the TU by the warehouse clerk upon truck arrival. Used for cargo to be delivered to the next destination in another country. Cargo with the following next destination is stored together: - The same country - The same group of countries Putaway is to bins with same consolidation group (for example, consolidation by forwarding order) or next empty bin, depending on capacity and consolidation groups. Special bins are used for overdimensional cargo. Due to setup with capacity and putaway rule using consolidation group, a corresponding overflow bin is setup (see storage type H980 Overflow Zones ). Cargo in this area is staged before physical loading to TUs or TU containers, or is moved to the area for loading onto HU containers. Used for unloading cargo from HU containers. No capacity limitations. Bin is assigned to work center WUCH for unloading cargo from HU containers. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 39

40 H923 H970 Area for Loading onto HU Container Clarification Zone Used for loading cargo onto HU containers. No capacity limitations, but putaway is to bins with same consolidation group (for example, consolidation by freight booking) or next empty bin. Inbound sections of work centers WC01-WC03 are used for transit HUs. Main bins are used for HU containers and are assigned to a work center. Areas for loading of HU containers with the following final destination: - The same country - The same group of countries HU containers are not staged before physical loading. Used for transit HUs that require clarification such as damaged HUs or HUs with special attributes that are not detailed in the forwarding order. No capacity limitations. H980 Overflow Zones Used for transit HUs if no bin can be determined for putaway in the area where this cargo would normally go. - Bin C-OVERFLOW used for overflow in storage type H921 Area by Country Bins by Shipment. - Bin DG-OVERFLOW used for overflow in storage type H040 Area for Dangerous Goods. - Bin HV-OVERFLOW used for overflow in storage type H050 Area for High Value Cargo. No capacity limitations. Cargo from C-OVERFLOW and DG- OVERFLOW is staged before physical loading to TUs. Cargo from HV-OVERFLOW is not staged before physical loading to TUs in order to reduce the time in which this cargo is not in the limited-access area. After you have created the storage bins as described, you can display the warehouse layout. On the SAP Easy Access screen for Extended Warehouse Management, choose Monitoring Graphical Warehouse Layout Display Graphical Warehouse Layout. The following figure shows the rack view and the bin view of the graphical warehouse layout: Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 40

41 ... Rack View Bin View Graphical Warehouse Layout Creating Determination Records for Printing HU Waybill Labels You use this procedure to create condition records for printing HU labels, for example when executing action Print HU Label on the Loading Preparation screen or on the HU Stock List screen. The condition record decides if printing should take place. The decision to print is based on the fields maintained in the condition record. In addition, the condition record determines the printer, form, and spool data, and whether a house waybill label (form group1) or a master waybill label (form group2) is printed. Important In order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, you need to create a condition record for warehouse JPTY only. 1. On the SAP Easy Access screen for SAP EWM, choose Work Scheduling Print Settings Create Condition Records for Printing (HUs) (or use transactionprhu6). 2. On the selection screen, enter applicationphu, maintenance groupphu, and choose Execute (F8). 3. On the Selection of key combination screen, choose condition tablesaphu Create the following entries: Field Value Value Condition Type 0HU4 0HU4 HU Type - - Warehouse JPTY JPNR HU Cat. TR TR Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 41

42 ... Form Group 1 2 TrM Cat. 1 1 Form /SCWM/HU_TW_WB_LABEL /SCWM/HU_TW_WB_LABEL Printer <printer>, for example LP01 <printer>, for examplelp01 Spool Data PPF: Name of Action Definition HU_LABEL_GENERAL_AND_RF HU_LABEL_GENERAL_AND_RF Det. No. 2 2 Type C C 5. Save your entries Creating Packaging Materials You use this procedure to create packaging materials manually in SAP EWM. The packaging materials are used to create handling units (HUs), transportation units (TUs), HU containers, TU containers and planned vehicles (outbound only) in SAP EWM. Note For more information about the usage of packaging materials in transit warehousing processes, see Appendix D: Determination of Packaging Materials in SAP EWM. 1. On the SAP Easy Access screen for SAP EWM, choose Extended Warehouse Management Master Data Product Maintain Product. 2. Create the following entries: Field/Value Product 1 Product 2 Product 3 Product 4 Product 5 Product PALLET BOX OAF_TRUCK PAG6 PMC6 Product Description Base Unit of Measure Pkg Data/Pack.M at.type Pkg Data/HU Type Pallet Box OAF_TRUCK - Air Freight Scenario Pallet Q6 Contour (88x125x9 6) EA EA EA EA EA PAL BOX MTR2 ULDP ULDP E1 C1 M1 E1 E1 Gross Weight Unit of Weight Closed Packaging 3. Save your entries KG KG TO KG KG - X Create the following entries Pallet Q6 Contour (96x125x9 6) Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 42

43 ... Field/Value Product 7 Product 8 Product 3 Product 4 Product 5 Product 6 Product AKE AAP AMA PAG7 PGA7 PMC7 Product Description Base Unit of Measure Pkg Data/Pack.M at.type Pkg Data/HU Type Half- Width Lower Deck Cont (61x60) (LD3) Lower Deck Container (88 x 125) (LD9) Main Deck Container (96x125) (M1) Pallet Q7 Contour (96x125x1 18) Pallet Q7 Contour (96x125x1 18) EA EA EA EA EA EA ULD ULD ULD ULDP ULDP ULDP E1 E1 E1 E1 E1 E1 Gross Weight Unit of Weight KG KG KG KG KG KG Pallet Q7 Contour (96x125x1 18) Closed Packaging X X X Save your entries Defining the Link between Packaging Material and MTR in SAP EWM You use this procedure to link a packaging material to a means of transport for the creation of a TU or vehicle. Note For more information about using packaging materials in transit warehousing processes, see Appendix D: Determination of Packaging Materials in SAP EWM. 1. On the SAP Easy Access screen for SAP EWM, choose Extended Warehouse Management Settings Shipping and Receiving Link Between Packaging Material (TU) and Means of Transport. 2. Check that the following entries exist, and if they do not, create them: Cont MTr Pack.Material Optional Seq.PMs No. PMs in MTr. PM OAF_TRUCK OAF_TRUCK X OAF_TRUK_S OAF_TRUCK X OF_TR OAF_TRUCK X Save your entry Defining Resource Group You use this procedure to set up resource management in SAP EWM. A resource is an entity representing a user or equipment, which can execute work in the warehouse. Resources are typically used when working with radio frequency (RF) devices. With resource management, you can define work queues, assign warehouse orders to the queues, and allow specific resources to work on specific queues. A resource group groups together resources with similar characteristics. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 43

44 Important In order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, an entry is required for warehouse numberjpty only. 1. On the SAP Easy Access screen for SAP EWM, choose Master Data Resource Management Maintain Resource Group. 2. Create the following entries: Warehouse No. Resource Group Description JPTY RG01 Resource Group 01 JPNR RG01 Resource Group 01 JPNG RG01 Resource Group 01 USLA RG01 Resource Group 01 USSA RG01 Resource Group 01 USPH RG01 Resource Group Save your entries Defining Queue Sequence for Resource Group You use this procedure to create queue sequences for resource groups. Important In order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, entries are required for warehouse numberjpty only. 1. On the SAP Easy Access screen for SAP EWM, choose Master Data Resource Management Maintain Queue Sequence for Resource Group. 2. Create the following entries: Warehouse No. Resource Group Sequence No. Queue No Interleaving JPTY RG01 1 PUTAWAY - JPTY RG01 2 STAGE - JPTY RG01 3 MOVE2LOAD - JPNG RG01 1 PUTAWAY - JPNG RG01 2 STAGE - JPNG RG01 3 MOVE2LOAD - JPNR RG01 1 PUTAWAY - JPNR RG01 2 STAGE - JPNR RG01 3 MOVE2LOAD - USLA RG01 1 PUTAWAY - Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 44

45 USLA RG01 2 STAGE - USLA RG01 3 MOVE2LOAD - USSA RG01 1 PUTAWAY - USSA RG01 2 STAGE - USSA RG01 3 MOVE2LOAD - USPH RG01 3 PUTAWAY - USPH RG01 2 STAGE - USPH RG01 3 MOVE2LOAD - 3. Save your entries Defining Presentation Device You use this procedure to define a presentation device used in RF. 1. On the SAP Easy Access screen for SAP EWM, choose Master Data Maintain Presentation Devices. 2. Create the following entries: PresDevice Description Displ.Prof PD01 Handheld ** 3. Save your entries Defining Resources You use this procedure to create resources representing the warehouse workers. Important In order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, entries are required for users working in warehouse numberjpty only. 1. On the SAP Easy Access screen for SAP EWM, choose Master Data Resource Management Maintain Resource. 2. Create the following entries: Warehouse No. Resource Rsrce Type Rsrce Grp DefPresDvc JPTY <UserID> RT01 RG01 PD01 JPNG <UserID> RT01 RG01 PD01 JPNR <UserID> RT01 RG01 PD01 USLA <UserID> RT01 RG01 PD01 USSA <UserID> RT01 RG01 PD01 USPH <UserID> RT01 RG01 PD01 3. Save your entries Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 45

46 Configuration for SAP NetWeaver Process Integration Checking Connection to SLD in SAP TM and SAP EWM The application systems must be defined as business systems in the System Landscape Directory (SLD). You use this procedure to check that your application systems for SAP TM and SAP EWM are correctly connected to the SLD. Start transaction SLDCHECK in SAP EWM and SAP TM. If the connection to SLD is configured correctly, the System Landscape Directory application appears in a new window. Close this new window and check the log displayed in transaction SLDCHECK. If the SLDCHECK is not successful, and there are error messages displayed after execution of transaction SLDCHECK in one or more of your application systems, proceed as follows: 1. Start transaction SXMB_ADMIN. 2. In folder Configuration, execute Integration Engine Configuration. 3. Check the following data by pressing Change Configuration, and if necessary enter it: Category Parameters Subparameter Prefix Current Value Default Value RUNTIME ENGINE TYPE - - LOC UNDEFINED RUNTIME IS_URL - - Dest://IS_<3- digit SID of PI system> For example, Dest://IS_X3X RUNTIME LOGGING_SYNC Creating a Configuration Scenario for Loading Appointment Integration In the SAP NetWeaver PI system, you create a configuration scenario between SAP TM and SAP EWM by using the integration scenarioloading appointment integration: TM_EWMLoadingAppointmentIntegration as a template. 1. Start the Integration Directory in the SAP NetWeaver PI system by choosing Start Integration Builder: Configuration Integration Directory or entering transaction SXMB_IFR. 2. In the Integration Builder: Configuration screen, choose Tools Apply Model from ES Repository. 3. Select Process Integration Scenario. 4. Select the integration scenariotm_ewmloadingappointmentintegration, delivered by SAP, from the list and choose Continue. 5. Enter a name for the configuration scenario, for example TM_EWMLoadingAppointmentIntegration_TMS_001_EWM_001. Use the naming convention: <scenario name>_<tm business system>_<ewm business system>. 6. Choose Finish and close the wizard. The Process Configurator starts. 7. In the Configurator, click on the title of the first swimlane (SAP TM) and, on the Business System Component for A2A tab page, enter the communication component for SAP TM, for example,tms_ Click on the title of the second swimlane (SAP EWM) and, on the Business System Component for A2A tab page, enter the communication component for SAP EWM, for example,ewm_001. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 46

47 9. Click on the connector betweensend Loading Appointment Request in the SAP TM swimlane andreceive Loading Appointment Request in the SAP EWM swimlane. On the Connections from Component Assignment tab page, assign the communication channel for the Receiver Business System Component, for examplegeneratedreceiverchannel_xi. Note It is not necessary to assign a communication channel to the Sender Business System Component. 10. Click on the connector betweensend Loading Appointment Notification in the SAP EWM swimlane andreceive Loading Appointment Notification in the SAP TM swimlane. On the Connections from Component Assignment tab page, assign the communication channel for the Receiver Business System Component, for examplegeneratedreceiverchannel_xi. 11. Click on the connector between bothget Transportation Document URI boxes. On the Connections from Component Assignment tab page, assign the communication channel for the Receiver Business System Component, for examplegeneratedreceiverchannel_xi. In addition, select the Direct Connection checkbox, as this connection is used for the navigation between SAP TM and SAP EWM screens. 12. Create configuration objects by choosing the Create Configuration Objects button. The Create Configuration Objects dialog box appears. 13. Select Generation and choose the Start button. The system displays the result of the generation process in a log. You do not have to save the log. 14. Choose Save to save your entries and Apply to leave the wizard. 15. Activate all changes. For example, in the context menu for the configuration scenario, choose Activate. The system displays a screen on which you can select and activate all changes. More Information Important Since all configuration data is stored in the main memory, you must refresh the runtime cache in SAP NetWeaver PI with transactionsxi_cache, or SAP NetWeaver PI will not use the settings. For more information about configuring integration scenarios, see SAP Library for SAP NetWeaver 7.4 at under SAP NetWeaver Platform SAP NetWeaver 7.4 Application Help Function-Oriented View. Choose SAP NetWeaver Library: Function-Oriented View Process Integration Integration Directory Integration Directory (Dual Stack) Using Tools to Configure Efficiently Using the Process Model as a Configuration Template Configuring Process Integration Scenarios. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 47

48 4.10 Configuration of Navigation between SAP EWM and SAP TM In this section you set up the navigation from SAP EWM to SAP TM or vice versa using links that are available in the screens in the SAP NetWeaver Business Client. For example, when a vehicle arrives to pick up HU containers or TU containers with cargo from a freight booking, you navigate from the Loading Preparation screen in SAP EWM to the Freight Booking screen in SAP TM in order to create a pick-up freight order with reference to the freight booking in SAP TM. Prerequisites Note The navigation is not necessary to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario. It is recommended for processes involving freight bookings. Important If you start SAP NetWeaver Business Client from an SAP TM system, you can navigate to the SAP EWM screens Prepare Loading or Unloading and Process Freight Orders. Further navigation from these SAP EWM screens to other SAP EWM transactions is not supported. You have created and configured a configuration scenario for loading appointment integration in the SAP NetWeaver PI system as described in Creating a Configuration Scenario for Loading Appointment Integration. The same user exists in SAP TM and SAP EWM with user roles enabling him or her to perform process steps in both applications. Typically, a user role based on/scwm/expert is assigned to the user in SAP EWM and a user role based on/scmtms/transportation_mgr_v2 is assigned to the user in SAP TM. The user can start the SAP NetWeaver Business Client in SAP EWM and SAP TM Creating Connection for Navigation in SAP EWM The settings require authorizations for cross-client settings on user and client level. 1. In SAP EWM, ask your system administrator to create an RFC connection for SAP TM in Customizing for SAP NetWeaver under Application Server IDoc Interface/Application Link Enabling (ALE) Communication Create RFC Connections as follows: a. Create a connection of type ABAP Connections, for exampletm1clnt001_t. On the Logon & Security tab page, do not specify a user. Select Current User instead. b. Create a connection of type HTTP Connections to ABAP System, for example TM1CLNT001_T_HTTP ortm1clnt001_t_https. Select Current User here too. 2. In SAP EWM, create a new variable for the RFC destination with transactionsm30_ssm_rfc: Variable TM RFC Destination TM1CLNT001_T Configuring User for Navigation in SAP EWM You use this procedure to assign object-based navigation content to an SAP EWM user role. The content is needed for users starting the SAP NetWeaver Business Client from the SAP EWM system. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 48

49 1. On the SAP Easy Access screen for SAP EWM, choose Tools Administration User Maintenance Role Administration Roles. 2. Enter a role, for examplez_ewm_obn_tm, and press the Create Single Role button. 3. Enter a description, for example,obn Navigation EWM to TM, and save the role 4. On the Menu tab page, choose Copy Menus From Another Role Target System. 5. Select the RFC Destination for SAP TM, for example,tm1clnt Select role/scmtms/process_administrator. 7. Open the OBN-Target node and select the nodes needed for navigation, for example: Forwarding Order Management Freight Order Management EWM Integration 8. Press Add to copy the menu nodes to the new role. 9. In the hierarchy view, open the added menu nodes and enter a target system for the desired applications by pressing Other Node Details: Menu Node Application Target System Forwarding Order Management Forwarding Order TM Freight Order Management Freight Booking TM Freight Order Management Freight Order TM EWM Integration (Un-)Loading Preparation UI <space> EWM Integration Freight Order UI <space> 10. Assign users to the profile 11. Save your entries Creating Connection for Navigation in SAP TM The settings require authorizations for cross-client settings on user and client level. 1. In SAP TM, ask your system administrator to create an RFC connection for SAP EWM in Customizing for SAP NetWeaver under Application Server IDoc Interface/Application Link Enabling (ALE) Communication Create RFC Connections, as follows: a. Create a connection of type ABAP Connections, for example,ewmclnt001_t. On the Logon & Security tab page, do not specify a user. Select Current User instead. b. Create a connection of type HTTP Connections to ABAP System, for example EWMCLNT001_T_HTTP orewmclnt001_t_https. Select Current User here too. 2. In SAP TM, create a new variable for the RFC destination with transactionsm30_ssm_rfc: Variable EWM RFC Destination EWMCLNT001_T Configuring User for Navigation in SAP TM You use this procedure to assign object-based navigation content to an SAP TM user role. The content is needed for users starting the SAP NetWeaver Business Client from SAP TM. Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 49

50 1. On the SAP Easy Access screen for SAPTWM, choose Tools Administration User Maintenance Role Administration Roles. 2. Enter a role, for examplez_tm_obn_ewm, and press the Create Single Role button. 3. Enter a description, for example,obn Navigation TM to EWM, and save the role. 4. On the Menu tab page, choose Copy Menus From Another Role Local. 5. Select role/scmtms/process_administrator. 6. Open the OBN-Target node and select the nodes needed for navigation, for example: Forwarding Order Management Freight Order Management EWM Integration 7. Press Add to copy the menu nodes to the new role. 8. In the Hierarchy view, open the added menu nodes and enter a target system for the desired applications by pressing Other Node Details: Menu Node Application Target System Forwarding Order Management Forwarding Order <space> Freight Order Management Freight Booking <space> Freight Order Management Freight Order <space> EWM Integration (Un-)Loading Preparation UI EWM EWM Integration Freight Order UI EWM 9. Assign users to the profile 10. Save your entries Configuration: 2015 SAP SE or an SAP affiliate company. All rights reserved. 50

51 Test Case: Receive from Shipper You can use this test case to run the process Receive from Shipper in warehouse number JPTY. 5.1 Prerequisites This test case requires the following roles: Warehouse Operator with role EWM: Warehouse Expert (/SCWM/EXPERT) For more information, see the prerequisites for Configuration:. You have configured SAP ERP, SAP Extended Warehouse Management (SAP EWM), SAP Transportation Management (SAP TM) and XI as described in Configuration:. 5.2 Features This test case uses the following applications in SAP TM, which you can find in the Transportation Management menu of the SAP NetWeaver Business Client (NWBC): Forwarding Order Management Forwarding Order Create Forwarding Order Freight Order Management Road Create Road Freight Order Freight Order Management Road Edit Road Freight Order This test case uses the following applications in SAP EWM, which you can find in the Extended Warehouse Management menu of the NWBC: Process Single Freight Order Process Freight Orders Prepare Loading or Unloading Handling-Unit Stock List This test case uses the following transactions in SAP EWM, which you can find on the SAP Easy Access screen for Extended Warehouse Management: Execution Log On to RF Environment (transaction /SCWM/RFUI) 5.3 Activities Step Step Description 1 Create forwarding order (SAP TM) 2 Create freight order (SAP TM) 3 Send unloading request to transit warehouse (SAP TM) Step Processor Input Data Expected Results Customer Service Clerk Transportati on Planner Transportati on Planner See Testcase for LCL Air Freight Scenario (SAP TM) See Testcase for LCL Air Freight Scenario (SAP TM) 1. From the Transportation Management menu in NWBC, choose Freight Order Management Road Edit Road Freight Order. 2. Enter the freight order number noted down in step 2 and press Continue. 3. From the Set Item Status drop down list, choose Set to Cargo Ready for Unloading. 4. Press Save. 5. Choose the Output Management tab page and check that TOR_LDAP_REQ was successfully processed. Note down the forwarding order number for later use Note down the freight order number for later use The freight order is transferred to SAP EWM. The corresponding objects are created in SAP EWM, like vehicle, TU, and inbound delivery as freight order. Test Case: Receive from Shipper 2015 SAP SE or an SAP affiliate company. All rights reserved. 51

52 4 Assign a door to the TU and post the arrival at the door (SAP EWM) Receiving Office Clerk 1. In SAP EWM, open the Process Single Freight Order screen. 2. In the Freight Order field, enter the freight order number noted down in step 2. Leave the TOR Stop ID field empty and press Continue. 3. In the TUs/Container TUs tab page, select the row of the TU 4. Choose Arrival at Door and assign a free door. TU has status Arrival and At Door. 5 Receive the HUs (SAP EWM) Warehouse Clerk 1. Start transaction /SCWM/RFUI. 2. Log on to the warehouse JPTY as resource <Your Name> with presentation device PD Choose Inbound Processes Receiving of Handling Units Receiving by TU/Door (TW) (fast path 347). 4. Enter the door you used in step Press Enter. 6. Press F1 List. 7. Copy the first HU from the list. 8. Choose F7 Back. 9. Enter the HU you just copied. 10. Repeat steps 6 to 9 until all HUs are received. 11. Answer the question Receiving complete? with Yes. 12. After you are finished, choose Back (F7) until you come to the logoff screen. Choose Logoff (F1) and Save (F1). Goods receipt has been posted for the HUs and an LDAP-Notification message with the actual data is sent back to SAP TM. Note down the HU numbers for later use. 6 Truck leaves (SAP EWM) Receiving Office Clerk 1. In SAP EWM, open the Process Single Freight Order screen. 2. In the Freight Order field, enter the freight order number noted down in step 2. Leave the TOR Stop ID field empty and press Continue. 3. Press Departure from Checkpoint. TU has status Departure and an LDAP-Notification message with the departed status is sent back to SAP TM. 7 Putaway the HUs (SAP EWM) Warehouse Worker 1. Start transaction /SCWM/RFUI. 2. Log on to the warehouse JPTY as resource <Your Name> with presentation device PD Choose Inbound Processes Putaway Putaway by HU (fast path 331). 4. Enter the HU number noted down in step 8 and press Enter. 5. Verify the destination bin and the HU number. 6. Repeat this procedure for all the HUs you received. 7. After you are finished press Back (F7) until you come to the logoff screen and press Logoff (F1) and Save (F1). The HUs are put away into the destination storage type. Test Case: Receive from Shipper 2015 SAP SE or an SAP affiliate company. All rights reserved. 52

53 ... 6 Test Case: Ship to Next Transit Warehouse You can use this test case to run the process Ship to Next Transit Warehouse in warehouse number JPTY. 6.1 Prerequisites This test case requires the following roles: Warehouse Operator with role EWM: Warehouse Expert (/SCWM/EXPERT) For more information, see the prerequisites in Configuration:. You have configured SAP ERP, SAP Extended Warehouse Management (SAP EWM), SAP Transportation Management (SAP TM), and XI as described in Configuration:. 6.2 Features This test case uses the following applications in SAP TM, which you can find in the Transportation Management menu of the SAP NetWeaver Business Client (NWBC): Forwarding Order Management Forwarding Order Create Forwarding Order Freight Order Management Road Create Road Freight Order Freight Order Management Road Edit Road Freight Order This test case uses the following applications in SAP EWM, which you can find in the Extended Warehouse Management menu of the NWBC: Process Single Freight Order Process Freight Orders Prepare Loading or Unloading Handling-Unit Stock List This test case uses the following transactions in SAP EWM, which you can find on the SAP Easy Access screen for Extended Warehouse Management: Execution Log On to RF Environment (transaction /SCWM/RFUI) 6.3 Activities Step Step Description 1 Create freight order for stage 2 for precarriage (SAP TM) Step Processor Input Data Expected Results Transportati on Planner See Testcase for LCL Air Freight Scenario (SAP TM) Note down the freight order number for later use Test Case: Ship to Next Transit Warehouse 2015 SAP SE or an SAP affiliate company. All rights reserved. 53

54 2 Send loading request to transit warehouse (SAP TM) Transportati on Planner 1. From the menu choose Freight Order Management Road Edit Road Freight Order. 2. Enter the freight order number noted down in step 1 and press Continue. 3. From the Set Status drop down list, choose Set to Ready for Transportation Execution. 4. From the Set Item Status drop down list, choose Set to Cargo Ready for Loading. 5. Press Save. 6. Choose tabstrip Output Management, and check that TOR_LDAP_REQ was successfully processed. The freight order is transferred to SAP EWM. The corresponding objects are created in SAP EWM, like vehicle, TU, and outbound delivery as freight order. 3 Truck Arrives at Checkpoint (SAP EWM) Receiving Office Clerk 1. In SAP EWM, open the Process Single Freight Order screen. 2. In the Freight Order field, enter the freight order number noted down in step 1. Leave the TOR Stop ID field empty and press Continue. 3. In the TUs/Container TUs tab page, select the row of the TU. 4. Choose Arrival at Door and assign a free door. TU has status Arrival and At Door. Note down the HU numbers from the screen area HUs/Container HUs. 4 Stage HUs (optional) (SAP EWM) Warehouse Clerk 1. Start transaction /SCWM/RFUI. 2. Log on to the warehouse JPTY as resource <Your Name> with presentation device PD Choose Manual Selection Selection by HU (fast path 22) 4. Enter the HU number noted down in step 3 and press Enter. 5. The source data is displayed. Press Enter. 6. Verify the destination bin and press Enter. 7. Repeat this procedure for all the HUs you noted down. 8. After you are finished, press Back (F7) until you come to the logoff screen and press Logoff (F1) and Save (F1). The HUs are staged. Test Case: Ship to Next Transit Warehouse 2015 SAP SE or an SAP affiliate company. All rights reserved. 54

55 5 Load Truck (SAP EWM) Warehouse Clerk 1. Start transaction /SCWM/RFUI. 2. Log on to the warehouse JPTY as resource <Your Name> with presentation device PD Choose Outbound Processes Loading Loading by TU / Door (TW) (fast path 438). 4. Enter the door you used in step Press Enter. 6. Press F1 List. 7. Copy the first HU from the list. 8. Choose F7 Back. 9. Enter the HU you just copied. 10. Repeat step 6 to 9 until all HUs are loaded. 11. Answer the question Loading complete? with Yes. 12. After you are finished, choose Back (F7) until you come to the logoff screen. Choose Logoff (F1) and Save (F1). The HUs have the status Loaded and an LDAP- Notification message with the actual data is sent back to SAP TM. 6 Truck leaves (SAP EWM) Shipping Office Clerk 1. In SAP EWM, open the Process Single Freight Order screen. 2. In the Freight Order field, enter the freight order number noted down in step 1. Leave the TOR Stop ID field empty and press continue 3. Press Departure from Checkpoint. TU has the status Departure and an LDAP- Notification message with the departed status is sent back to SAP TM. Test Case: Ship to Next Transit Warehouse 2015 SAP SE or an SAP affiliate company. All rights reserved. 55

56 ... 7 Appendix The appendix contains additional information about the transit warehousing scenario. It describes additional information that gives a better understanding of the configuration. It also contains additional configuration not required in the preconfigured transit warehouse, but that may be necessary for using transit warehousing processes in your own warehouse. 7.1 Appendix A: Checking Basic Table Entries Used in SAP TM, SAP ERP, and SAP EWM Basic tables such as units of measure, currencies, countries, and languages are used by SAP ERP, SAP Transportation Management (SAP TM) and SAP Extended Warehouse Management (SAP EWM). Entries used in processes involving these applications must be identical in all systems. You use this procedure to check that the entries (especially the ISO codes) needed in your transit warehousing processes are identical in all systems that are part of your system landscape. 1. On the SAP Easy Access screen for SAP EWM choose Tools Administration Administration Client Administration Customizing Objects Object Comparison. 2. Compare the information in the following tables between the EWM client and the ERP client and between the EWM client and the TM client. Compare the entries you plan to use in your transit warehousing processes. Adjust the tables Customizing in SAP TM, SAP ERP or SAP EWM, if necessary. Table Field Description T006 ISOCODE Unit of measure T002 LAISO Language keys TCURC ISOCD Currency codes T005 INTCA Countries 7.2 Appendix B: Verifying Synchronization of Customizing between SAP TM, SAP ERP, and SAP EWM Some customizing entries must be defined in different tables in SAP ERP, SAP Transportation Management (SAP TM) and SAP Extended Warehouse Management (SAP EWM). For example, packaging material types of handling units in SAP EWM must be defined as package type codes in SAP TM. The following table gives an overview of table entries that must be synchronized across these applications: Setting Incoterms Customizing Path in SAP ERP Sales and Distribution Master Data Business Partners Customers Billing Document Define Incoterms Customizing Path in SAP TM SCM Basis Master Data Define Incoterms Customizing Path in SAP EWM Cross-Process Settings Delivery Warehouse Request General Settings Define Incoterms Means of Transport Not applicable Master Data Resources Define Means of Transport SCM Basis Master Data Transportation Lane Maintain Means of Transport Appendix 2015 SAP SE or an SAP affiliate company. All rights reserved. 56

57 Packaging Material Type (for transportation units) Packaging Material Type (for handling units in SAP EWM) or Package Type Code (SAP TM) Shipping Conditions (SAP ERP and SAP EWM) or Transportation Service Level Code (SAP TM) Logistics-General Handling Unit Management Basics Define Packaging Material Types Logistics-General Handling Unit Management Basics Define Packaging Material Types Logistics Execution Shipping Basic Shipping Functions Shipping Point and Goods Receiving Point Determination Define Shipping Conditions SCM Basics Pack Handling Units Basics Define Packaging Material Types Forwarding Order ManagementDefine Package Type Codes Forwarding Order ManagementDefine Transportation Service Level Codes Cross Process Settings Handling Units Basics Define Packaging Material Types Cross Process Settings Handling Units Basics Define Packaging Material Types Cross-Process Settings Delivery Warehouse Request General Settings Define Shipping Conditions For more information about synchronization of table entries between SAP ERP and SAP EWM, see Verifying Synchronization of ERP and EWM Customizing in Integration of SAP ERP with SAP EWM [External]. If you implement your own transit warehouse, check if you use any of the settings listed in the table above in your warehousing processes. Compare the entries between your EWM and your ERP customizing client and, if necessary, adapt the entries in the TM, EWM or ERP client. Tip You can either compare the settings manually or use the Customizing Scout, which is a tool delivered with the SAP Solution Manager (transactionsmsy). 7.3 Appendix C: Condition Records for Bin Determination This appendix contains the list of condition records created in Creating Warehouse Structure and Condition Records for Bin Determination, followed by an explanation of the bin determination using condition records. You can display the condition records from the SAP Easy Access screen for SAP EWM by choosing Extended Warehouse Management -> Settings -> -> Maintain Condition Records for Bin Determination (Validity: Today s Date to ). Alternatively, use transaction/scwm/put_tw_wt_gcm. Note The condition records listed below refer to warehouse number W100. In your system, the condition records exist in the warehouse numbers that you have created with the configuration document. Condition records for condition type 0TWP and condition table SAPTWP10 (clarification): Whn ToBeClarified Stor. Type Stor.Bin W100 X H970 CL-ZONE Condition records for condition type 0TWP and condition table SAPTWP20 (loading preparation): Whn NxtTWCtry Activity Stor.Type Section W100 US MLCH H923 C01I W100 DE MLCH H923 C02I W100 - MLCH H923 C99I Appendix 2015 SAP SE or an SAP affiliate company. All rights reserved. 57

58 Condition records for condition type 0TWP and condition table SAPTWP30 (specific dangerous goods class): Whn Sequence Activity Dang.Goods Regulation Class Stor.Type Section Stor.Bin W100 - STAG X ADR 3 H W X ADR 3 H040 DG1 - W X ADR 3 H980 - DG- OVERFLOW Condition records for condition type 0TWP and condition table SAPTWP40 (any dangerous goods class): Whn Sequence Activity Dang.Goods Stor.Type Section Stor.Bin W100 - STAG X H W X H040 DG9 - W X H980 - DG- OVERFLOW Condition records for condition type 0TWP and condition table SAPTWP50 (high-value cargo): Whn Sequence High-Value Stor.Type Section Stor.Bin W100 1 X H W100 2 X H980 - HV-OVERFLOW Condition records for condition type 0TWP and condition table SAPTWP60 (specific region or postal code): Whn Sequence FnlTWCtry FnlTWRegi Logical Condition Stor.Type Section Stor.Bin W100 - JP 12 - H920 R01 - W100 1 JP 13 PC_JPTY_10_25 H920 POC POSTCODE- 001 W100 2 JP 13 PC_JPTY_25_50 H920 POC POSTCODE- 002 W100 3 JP 13 PC_JPTY_50_75 H920 POC POSTCODE- 003 W100 4 JP 13 PC_JPTY_OTHER H920 POC POSTCODE- 999 W100 - JP 15 - H920 R02 - Condition records for condition type 0TWP and condition table SAPTWP70 (any region or postal code): Whn FnlTWCtry Stor.Type Section W100 JP H920 R99 Condition records for condition type 0TWP and condition table SAPTWP80 (other specific countries): Whn Sequence FnlTWCtry Activity Overdimen. Stor.Type Section Stor.Bin W100 1 DE - - H921 C02 - Appendix 2015 SAP SE or an SAP affiliate company. All rights reserved. 58

59 W100 2 DE - - H980 - C- OVERFLOW W100 - DE STAG - H W100 1 DE - X H921 C02L - W100 2 DE - X H980 - C- OVERFLOW W100 - DE STAG X H W100 1 US - - H921 C01 - W100 2 US - - H980 - C- OVERFLOW W100 - US STAG - H W100 1 US - X H921 C01L - W100 2 US - X H980 - C- OVERFLOW W100 - US STAG X H Condition records for condition type 0TWP and condition table SAPTWP90 (any other countries): Whn Sequence Activity Overdimen. Stor.Type Section Stor.Bin W H921 C99 - W H980 - C_OVERFLOW W100 - STAG - H W X H921 C99L - W X H980 - C_OVERFLOW W100 - STAG X H Condition records for condition type 0TWC and condition table SAPTWC01 (unloading): Whn Not Autom. Stor.Type Storage Bin W100 - H922 CHU-UNLOAD Condition records for condition type 0TWC and condition table SAPTWC02 (specific countries): Whn NxtTWCtry Stor.Type Section Storage Bin W100 US H923 C01 COUNTRY-01 W100 DE H923 C02 COUNTRY-01 Condition records for condition type 0TWC and condition table SAPTWC03 (any other countries): Whn Stor.Type Section Storage Bin W100 H923 C99 COUNTRY-99 Explanation of Bin Determination Using Condition Records Appendix 2015 SAP SE or an SAP affiliate company. All rights reserved. 59

60 The condition records listed above are an example adapted to the warehouse layout created in Creating Warehouse Structure and Condition Records for Bin Determination, and are used to determine an appropriate destination bin during warehouse task creation. The bin determination uses one or more condition records created in multiple condition tables containing fields from a global field catalog. Using multiple smaller condition tables in a strict order allows a reduction of the number of condition records necessary to map all required movements in the example layout. However, one trade-off when using multiple tables is the increased complexity when creating condition records and retracing which condition records match in a specific use case. The following figure shows the order in which SAP EWM accesses the condition tables when searching for a suitable bin for transit HUs (left-hand side) and for HU containers (right-hand side). Each row represents a unique condition table. The boxes refer to the different areas of the warehouse layout and indicate which result data (destination data) the condition records of the table contain. For example, the first table, SAPTWP10 represents the clarification zone in the warehouse layout. As this is the only box in the row, no result data other than clarification is defined in the condition record of this table. Compared to this, the third row for table SAPTWP30 contains one box for the dangerous goods area, one box for the staging area and one box for the overflow area. This means that the condition records of this condition table contain three different sets of result data. The order in which SAP EWM tries to find a matching condition record in one of the condition tables is defined by the access sequence. The determination according to the access sequence stops immediately if a matching condition record is found in one of the tables, so that no other table will be accessed. This does not mean that only a single condition record is returned for further processing: multiple condition records can be found in one condition table due to the use of the sequence number field in the condition table. As different condition tables are used for bin determination of transit HUs and HU containers, different determination procedures are assigned to the warehouse number. Note The determination procedures used for transit HUs and HU containers are assigned to the warehouse number in the Customizing activity Define Warehouse Number Control, in Customizing for Extended Warehouse Management under Master Data Define Warehouse Number Control. Appendix 2015 SAP SE or an SAP affiliate company. All rights reserved. 60

61 Note For information about the customizing for this example, see Customizing for Extended Warehouse Management under Goods Receipt Process Strategies Storage Bin Search Sequence for Transit HUs Search Sequence Table Description 1 SAPTWP10 Clarification 2 SAPTWP20 Loading Preparation The only relevant attribute is the To Be Clarified indicator. If the To Be Clarified status is set for a transit HU, the system determines a storage bin in the clarification zone (storage type H970) based on the single condition record of this table. The areas for loading transit HUs onto HU containers should only be found in the loading preparation process. Warehouse tasks for loading preparation use a special warehouse process type. It is assigned to the warehouse number and uses activity MLCH. All condition records in this table will match for this activity only. The destination data of the condition records contains different inbound sections of a work center (within storage type H923) that is used for loading cargo onto HU containers. Different inbound sections are found by the consolidation group. An additional criteria in this condition table is the country of the next unloading location, which also leads to the determination of different storage sections. For example USA (US) matches to the condition record with storage section C01 and Germany (DE) matches to a condition record with storage section C02. Note: This table is positioned very early in the access sequence in order to reduce the number of condition records that have to be created for any transit HU in the destination bin determination for loading preparation. By using a special warehouse process type with activity MLCH in this table, the loading preparation for all transit HUs finds condition records in this table as long as this activity is used. For example, there is no need to create additional condition records in table SAPTWP50 for loading preparation of high-value goods. Nor do you need to create additional condition records in table SAPTWP80 for loading preparation of transit HUs which are shipped to a different next unloading location country, like the US. 3 SAPTWP30 Specific Dangerous Goods Class With the example condition records, transit HUs containing dangerous goods of regulation code ADR and class 3 will be stored in a dedicated area. As there are capacity limitations, an overflow storage bin is also returned. Therefore the determination finds two matching condition records with different sequence numbers. The sequence number also gives the order in which the storage bin is used in searches in further processing. The destination data for class 3 and regulation code ADR of the first condition record is storage section DG1 of storage type H040. The system finds a different condition for warehouse tasks created with activity STAG, as a different destination bin should be found for the staging activity. Note that for any other activity, the system finds the condition records where the Activity field is empty, as the field is defined as optional ( field in free key part ) in customizing for the access sequence. 4 SAPTWP40 Any Dangerous Goods Class In the previous table, records exist for transit HUs containing dangerous goods of regulation code ADR and class 3 only. For any other dangerous goods data not maintained in table SAPTWP30, the system uses table SAPTWP40 for bin determination. In the example condition records, the system finds storage section DG9 in storage type H040 for any dangerous goods not classified as regulation code ADR and class 3. In this table, two other condition records might match: one with a different Appendix 2015 SAP SE or an SAP affiliate company. All rights reserved. 61

62 5 SAPTWP50 High-Value Goods sequence number for the overflow bin, and one with activity STAG for the staging activity. Note: In general, we recommend creating an additional condition record for an overflow storage bin if the storage types used in the determination have capacity limitations, to avoid interruptions in the process if all bins are occupied at a point in time. The table contains two condition records with different sequence numbers. The system searches for a storage bin in the storage type for high value goods (H050) first. As there are capacity restrictions, a second condition record with an overflow storage bin also exists. As there is no staging of high value cargo in the example warehouse layout, there is no additional condition record with activity STAG. Note: Since the dangerous goods tables are placed before the table for high-value cargo, the dangerous goods information implicitly has a higher priority than the high-value indicator. This means that a transit HU containing dangerous goods and high-value cargo will be stored in the area for dangerous goods. 6 SAPTWP60 Same Country with Specific Region/Postcode The condition records of this table are used to store cargo that is to be delivered in the same country as the transit warehouse; in this example in Japan (JP). In storage type H920, cargo is separated by region: cargo for region 12 is stored in section R01 and cargo for region 15 in section R02. For cargo to be delivered in the same region as the transit warehouse (region 13), condition records exist to group the cargo by postal code range in storage section POC of the same storage type. Using the postal code of the consignee, the system finds a suitable condition record by evaluating the logical condition, which leads to different storage bins for each postal code range. 7 SAPTWP70 Same Country for Any Region/Postcode 8 SAPTWP80 Other Specific Countries 9 SAPTWP90 Any Other Countries This table contains condition records for cargo for any region of the transit warehouse s country that has no condition record of its own in the previous table. Cargo for these regions is stored in storage section R99 of storage type H920. This table is used to store cargo where the country of the final transit warehouse is different to the country of the current transit warehouse. Cargo for specific countries is stored in different storage sections of storage type H921. In this example, cargo for the USA (US) is stored in section C01 and cargo for Germany (DE) in section C02. Overdimensional cargo is also stored in different sections per specific country. As the system finds a new bin for each consolidation group, it might happen that all storage bins within a section for a country are occupied. Therefore, an additional condition record with a different sequence number is returned for the overflow storage bin in storage type H980. This is valid for all activities except when using STAG. In this case, the system finds a different condition record. It points to storage type H910, to allow a staging to a storage bin close to the door used to load the cargo. Note: due to the fact that the staging activity is processed for normal cargo as well as for overdimensional cargo, two condition records exist with activity STAG, but only one is found at any one time. This table is used for storing cargo where the country of the final transit warehouse is different to the country of the current transit warehouse, but where the system cannot find a condition record in the previous tables. Cargo to be delivered to countries that are not specified in the previous table is stored in a separate storage section C99 of storage type H921. The system finds a different condition record for overdimensional cargo, pointing to section C99L of the same storage type. Different condition records are used for staging here too. Appendix 2015 SAP SE or an SAP affiliate company. All rights reserved. 62

63 Search Sequence for HU Containers Search Sequence Table Description 1 SAPTWC01 Unpack 2 SAPTWC02 Specific Countries 3 SAPTWC03 Any Other Country The condition record in this table is used to move HU containers to be unloaded to the unloading storage bin CHU-UNLOAD of storage type H922. It is valid for all HU containers with the indicator Unloaded Expected. Condition records of this table are considered for HU containers that are not expected to be unloaded. Otherwise the condition record in the previous table would match. The condition records separate the storage of HU containers into different storage sections depending on the country of the next transit warehouse location. In the example, HU containers with Next Transit Warehouse Location Country USA (US) match to condition record with section C01 and storage bin COUNTRY-01 of storage type H923, and HU containers with Next Transit Warehouse Location Country Germany (DE) match to condition record with section C02 and storage bin COUNTRY-02 of storage type H923. Note: The condition table contains an optional field for the activity defined in the warehouse process type. Therefore, it is possible to create condition records to build an additional process step, for example, staging of HU containers. HU containers with a Next Transit Warehouse Location Country that does not match any record of the previous table will match a condition record for storage section C99 and storage bin COUNTRY-99 of storage type H923. Note: the condition table also contains an optional field for the activity defined in the warehouse process type. Appendix 2015 SAP SE or an SAP affiliate company. All rights reserved. 63

64 7.4 Appendix D: Determination of Packaging Materials in SAP EWM In the example configuration described in this document, packaging materials exist in SAP EWM only, and are determined from vehicle types, transportation unit types, and package types in SAP TM when SAP TM sends a TransportationOrderLoadingAppointmentRequest message to SAP EWM. However, there are several options for determining a packaging material for vehicles, TUs, TU containers, HU containers, and HUs in SAP EWM, which are described more in detail in this appendix. Note Vehicles do not have a packaging material in SAP EWM, only a means of transport. A packaging material is only required for planned vehicles in an outbound process for technical reasons. Determination of packaging materials for vehicles and transportation units The following figure gives an overview of the packaging material determination for vehicles and TUs in SAP EWM: Case 1: Case 2: Case 3: If a packaging material is assigned to the resource master used in the freight document of SAP TM, SAP TM sends this packaging material to SAP EWM in the corresponding item of the TransportationOrderLoadingAppointmentRequest message. A packaging material with the same name must exist in SAP EWM. In this case, SAP EWM uses the packaging material with the same name to create the vehicle or TU. There is no packaging material in the vehicle resource master in SAP TM. In this case, the corresponding item in the TransportationOrderLoadingAppointmentRequest message contains a vehicle type. This type is mapped to a packaging material in SAP EWM that has the same name as the vehicle type. There is no direct relationship between the vehicle group in SAP TM and the packaging material type in SAP EWM, but in this case you can use the same names for vehicle groups and packaging material types. If the vehicle type cannot be mapped to a packaging material in SAP EWM because no packaging material of the same name exists, the packaging material is determined from the means of transport. For more information, see Defining the Link between Packaging Material and MTR in SAP EWM. Appendix 2015 SAP SE or an SAP affiliate company. All rights reserved. 64

65 Determination of packaging materials for TU containers and HU containers The following figure gives an overview of the packaging material determination for TU containers or HU containers in SAP EWM: The transportation unit type (TU type) of the resource used in the freight document of SAP TM is mapped to a packaging material in SAP EWM with the exact same name as the TU type (for example, container type20g0). There is no direct relationship between the TU group in SAP TM and the packaging material type in SAP EWM, but you can use the same names for TU groups and packaging material types (for example,cn for containers). In addition, the TU group is mapped to a means of transport of the same name in SAP EWM. Determination of packaging materials for transit HUs The following figure gives an overview of the packaging material determination for transit HUs in SAP EWM: The packaging type of the package item contained in the freight document of SAP TM is mapped to a packaging material type in SAP EWM with the exact same name (for example,pal for pallet). SAP EWM expects that only one packaging material (for example PALLET) exists for this packaging material type, and uses this packaging material to create the transit HUs. Important It is crucial that there is a 1:1 relation between the packaging material type and the packaging material itself in SAP EWM. If there are several packaging materials with the same packaging material type, the packaging material is determined randomly. Appendix 2015 SAP SE or an SAP affiliate company. All rights reserved. 65