ewm930solman tw

CUSTOMERSolution Manager ContentSAP EWM 9.3Document Version: 1.0 - 2015-05-27

Transit Warehousing

Transit Warehousing C U S T O M E R

Document History © 2015 SAP SE or an SAP affiliate company. All rights reserved. 2

Document HistoryDocument Version Description

1.0 Final version. May 27, 2015


Table of Contents © 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

Table of Contents1 Scenario: Transit Warehousing ...................................................................................................... 5

1.1 Integration ....................................................................................................................................... 51.2 Prerequisites ................................................................................................................................... 51.3 Warehouse Structure and Master Data ........................................................................................ 51.4 Process ............................................................................................................................................ 6

2 Process: Receive from Shipper ...................................................................................................... 72.1 Process ............................................................................................................................................ 7

3 Process: Ship to Next Transit Warehouse ..................................................................................... 103.1 Process .......................................................................................................................................... 10

4 Configuration: Transit Warehousing .............................................................................................. 124.1 Prerequisites ................................................................................................................................. 12

4.1.1 Installed Components .................................................................................................... 124.1.2 Prerequisites for System Connection in SAP ERP, SAP TM and SAP EWM ............. 124.1.3 Configuration Guide for LCL Air Freight Scenario in SAP TM .................................... 13

4.2 User Roles for SAP TM and SAP EWM ........................................................................................ 134.3 Overview of SAP ERP Master Data .............................................................................................. 13

4.3.1 Customer Master Data in SAP ERP .............................................................................. 134.3.2 Vendor Master Data for Carriers in SAP ERP .............................................................. 14

4.4 Configuration in SAP ERP ............................................................................................................ 174.4.1 Activating Business Transaction Events (BTE) in SAP ERP ....................................... 174.4.2 Configuring Logical Systems in SAP ERP .................................................................... 174.4.3 Assigning EWM Logical System to RFC Destination in SAP ERP ............................... 174.4.4 Configuring qRFC Destination in SAP ERP .................................................................. 18

4.5 Configuration in SAP EWM ........................................................................................................... 194.5.1 Activating Business Functions in SAP EWM ................................................................ 194.5.2 Configuring Logical Systems in SAP EWM................................................................... 194.5.3 Assigning Logical System to RFC Destination in SAP EWM ....................................... 194.5.4 Configuring Business Systems .....................................................................................204.5.5 Configuring Business System Group ...........................................................................204.5.6 Configuring qRFC Destination in SAP EWM ................................................................. 214.5.7 Activating the Planning Version and Model for Master Data ...................................... 224.5.8 Activating BC Sets in SAP EWM .................................................................................... 224.5.9 Configuring Action Profiles for TU and Vehicle ........................................................... 234.5.10 Configuring Action Conditions for Transportation Unit .............................................. 244.5.11 Checking Action Profiles for HU .................................................................................... 254.5.12 Activating Error and Conflict Handler in SAP EWM..................................................... 254.5.13 Defining Work Center Layout to Display Planned HUs ............................................... 25

4.6 Settings and Master Data in SAP ERP ........................................................................................ 274.6.1 Preparing Initial Transfer of Master Data from SAP ERP ........................................... 274.6.2 Transferring Master Data from SAP ERP using CIF .................................................... 274.6.3 Scheduling Background Job for Master Data Transfer .............................................. 28

4.7 Configuration in SAP TM ............................................................................................................. 304.7.1 Assigning Warehouse Number to Location ................................................................ 304.7.2 Transferring Locations and Business Partners from SAP TM to SAP EWM ............ 30

4.8 Settings and Master Data in SAP EWM ....................................................................................... 324.8.1 Checking Business Partners of Transportation Network ........................................... 324.8.2 Checking Locations of Transportation Network ......................................................... 324.8.3 Maintaining Supply Chain Units for Transit Warehouses ........................................... 334.8.4 Maintaining Logical Conditions for Bin Determination ............................................... 34

http://www.sap.com/contactsap


Table of Contents © 2015 SAP SE or an SAP affiliate company. All rights reserved. 4

4.8.5 Checking Assignment of Supply Chain Unit to Warehouse Number ......................... 354.8.6 Creating Warehouse Structure and Condition Records for Bin Determination ....... 354.8.7 Creating Determination Records for Printing HU Waybill Labels .............................. 414.8.8 Creating Packaging Materials ....................................................................................... 424.8.9 Defining the Link between Packaging Material and MTR in SAP EWM ..................... 434.8.10 Defining Resource Group............................................................................................... 434.8.11 Defining Queue Sequence for Resource Group ........................................................... 444.8.12 Defining Presentation Device ........................................................................................ 454.8.13 Defining Resources ........................................................................................................ 45

4.9 Configuration for SAP NetWeaver Process Integration ............................................................464.9.1 Checking Connection to SLD in SAP TM and SAP EWM.............................................464.9.2 Creating a Configuration Scenario for Loading Appointment Integration ................46

4.10 Configuration of Navigation between SAP EWM and SAP TM ................................................. 484.10.1 Creating Connection for Navigation in SAP EWM ....................................................... 484.10.2 Configuring User for Navigation in SAP EWM.............................................................. 484.10.3 Creating Connection for Navigation in SAP TM...........................................................494.10.4 Configuring User for Navigation in SAP TM .................................................................49

5 Test Case: Receive from Shipper .................................................................................................. 515.1 Prerequisites ................................................................................................................................. 515.2 Features ......................................................................................................................................... 515.3 Activities ........................................................................................................................................ 51

6 Test Case: Ship to Next Transit Warehouse .................................................................................. 536.1 Prerequisites ................................................................................................................................. 536.2 Features ......................................................................................................................................... 536.3 Activities ........................................................................................................................................ 53

7 Appendix ..................................................................................................................................... 567.1 Appendix A: Checking Basic Table Entries Used in SAP TM, SAP ERP, and SAP EWM ......... 567.2 Appendix B: Verifying Synchronization of Customizing between SAP TM, SAP ERP, and

SAP EWM ....................................................................................................................................... 567.3 Appendix C: Condition Records for Bin Determination ............................................................. 577.4 Appendix D: Determination of Packaging Materials in SAP EWM ............................................647.5 Appendix E: Additional Configuration for LCL Ocean Freight Scenario ...................................667.6 Appendix F: Hints for Dangerous Goods Handling .................................................................... 67


Scenario: Transit Warehousing © 2015 SAP SE or an SAP affiliate company. All rights reserved. 5

1 Scenario: Transit WarehousingYou can use this business scenario to integrate warehouse execution with freight forwarding operations usingSAP Extended Warehouse Management (SAP EWM) and SAP Transportation Management (SAP TM). In TransitWarehousing, you receive cargo from shippers based on inbound planning from SAP TM. You consolidate cargowith the same destination in your transit warehouse before you ship it to the next location of the transportationchain or deliver it to the final consignee, based on outbound planning from SAP TM. As cargo received fromnumerous 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 thewarehouse. The transit warehouse is structured in such a way that you put away HUs with the same destinationcountry or region on the same storage bin, where they are available for the shipment to the next location or to theconsignee. 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 forputaway, or you stage the HUs before loading them onto a vehicle. During these processes, SAP EWM informsSAP TM about the major steps performed in the transit warehouse, such as arrival at checkpoint, departure fromcheckpoint, and receiving or loading completion.

1.1 IntegrationThe business scenario Transit Warehousing is integrated in the LCL Air Freight scenario in SAP TM. It describesthe receiving of cargo from a shipper in the transit warehouse in Tokyo, and the shipping of cargo from the transitwarehouse in Tokyo to the gateway in Narita. The consignee of the cargo is located in the USA. The transitwarehouse in Tokyo is managed with SAP EWM.

1.2 PrerequisitesYou 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 ExtendedWarehouse Management on SAP Service Marketplace at http://service.sap.com/instguides.For more information about the configuration prerequisites, see Configuration: Transit Warehousing.

1.3 Warehouse Structure and Master DataAs transit warehousing processes strongly depend on the warehouse structure, all processes are integrated in astandard 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 outboundArea with country-specific storage binsArea with region-specific storage binsArea with storage bins for postal codesAreas for cargo with special attributes, such as dangerous goods or high-value cargoArea for the handling of HU containersClarification zone

In this scenario, the warehouse structure is used for the Tokyo transit warehouse of the LCL Air Freight scenariofrom SAP TM, but the same warehouse structure can be used for all transit warehouses across the transportationchain of this scenario.

NoteYou can find a detailed description of the warehouse structure in Creating Warehouse Structureand Condition Records for Bin Determination.

http://service.sap.com/instguides


Scenario: Transit Warehousing © 2015 SAP SE or an SAP affiliate company. All rights reserved. 6

1.4 ProcessThe business scenario contains the following processes:...

1. Receive from Shipper2. Ship to Next Transit Warehouse

The processes described in this scenario interact with each other and build a consistent flow: cargo received inthe inbound process is shipped in the outbound process.The business process descriptions include not only the system and user activities, but also the physical activitiesin the warehouse. For this reason, some process steps are not carried out in the system.


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

2 Process: Receive from ShipperYou use this business process to receive cargo from a shipper in a transit warehouse managed with SAP ExtendedWarehouse Management (SAP EWM). After the creation of a forwarding order and of a pick-up freight order fromthe shipper to the transit warehouse, SAP Transportation Management (SAP TM) sends the inbound planninginformation to SAP EWM. When the truck arrives, you identify the freight order in SAP EWM and post the arrival atcheckpoint. The truck drives to a door and you unload the cargo, which is usually packed on pallets. Afterunloading, you identify the handling units (HUs) based on the inbound plan sent by SAP TM. You attach an HUlabel to them, for example, a house airway bill (HAWB) label containing shipper and consignee information. Thetruck leaves the door and you post the departure from the checkpoint. You then put away HUs with the samedestination country in the same storage bin, where they are available for the shipment to the next location or tothe consignee. HUs with special attributes, such as overdimensional cargo or high-value cargo, are put awayseparately. In this process, SAP EWM informs SAP TM about arrival at checkpoint, receiving completion, anddeparture from checkpoint. The notification of receiving completion also includes information about the singleHUs.

2.1 ProcessThis 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 aconsignee. The cargo is to be picked up from the shipper and transported to the consignee via transitwarehouses 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 afreight order for transporting cargo from the shipper’s location to the first transit warehouse. Thetransportation planner communicates with a carrier. He or she assigns the carrier to the freight order inSAP 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 thestatus 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 requestmessage containing freight order information to SAP EWM. (This step can be done automatically.) SAPEWM automatically creates a vehicle, a transportation unit (TU), an inbound delivery, and HUs. The HUsare 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. Thereceiving office clerk selects the freight order in SAP EWM. He or she assigns a free door to the TU, sets thestatus ‘Docked at Door’, and tells the truck driver to drive to the assigned door. SAP EWM automaticallyprints HU labels to prepare for the receiving of HUs. In addition, SAP EWM sends an unloading notificationmessage for arrival at checkpoint to SAP TM. SAP TM sets status of the current stage of the freight orderto ‘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. Awarehouse worker then receives the HUs using an RF device. He or she identifies the packages, attaches anHU label to each package, and scans the label. He or she enters the weight and dimensions of thepackages. The system automatically posts goods receipt in SAP EWM for each received HU. With the lastHU, the warehouse worker confirms the receiving completion in SAP EWM, which triggers the sending of anunloading notification message containing the received HUs to SAP TM. SAP TM updates the freight orderand freight units.

6. Truck leaves (SAP EWM)The truck leaves the door and the premises. The receiving office clerk confirms the departure from thecheckpoint, and therefore from the door. SAP EWM sends an unloading notification message for departurefrom checkpoint to SAP TM. SAP TM updates the execution status of the freight order.

7. Putaway HUs (SAP EWM)



The warehouse worker chooses the equipment necessary for the putaway, for example, a forklift truck andan RF device, and logs on as a resource. He or she then picks an HU from the inbound staging area andscans its label. The system automatically creates a warehouse order and proposes a destination bin. Thewarehouse worker brings the package to the destination bin and confirms the putaway. He or she proceedsin the same way with all HUs until the inbound staging area is empty.


Process: Ship to Next Transit Warehouse © 2015 SAP SE or an SAP affiliate company. All rights reserved. 10

3 Process: Ship to Next Transit WarehouseYou use this business process to ship cargo from your transit warehouse to the next location in the transportationchain. After the creation of a pre-carriage freight order, SAP Transportation Management (SAP TM) sends theoutbound 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 loadthe requested handling units (HUs) directly from their storage bin, or you stage the HUs to a staging area firstbefore loading them onto the truck. The truck departs from the door and you post the departure from thecheckpoint. In this process, SAP EWM informs SAP TM about arrival at checkpoint, loading completion, anddeparture 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 ProcessThis 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 afreight order for transporting the cargo to the next location. He or she assigns the carrier to the freightorder 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 messageto SAP EWM. (This step can be done automatically.) SAP EWM automatically creates a vehicle, atransportation unit (TU), an outbound delivery order, and planned HUs. The planned HUs are assigned tothe 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 clerkselects the freight order in SAP EWM. He or she assigns a free door to the TU, sets the status ‘Docked atDoor’, and tells the truck driver to drive to the assigned door. SAP EWM sends a loading notificationmessage for arrival at checkpoint to SAP TM. SAP TM sets status of the current stage of the freight orderto ‘Arrived’.With the arrival at checkpoint, SAP EWM creates staging warehouse tasks (WTs) for HUs that must bestaged (optional). The system gathers the WTs into warehouse orders (WOs) to optimize the picking. Thesystem assigns the WOs to one or more queues according to specific criteria, such as the activity area andthe 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 thispurpose, he or she chooses the equipment necessary for the picking, for example, a forklift truck and an RFdevice. He or she logs on to the system as a resource. He or she receives the first WO of the queue he orshe 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 andscans 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 RFdevice.The warehouse worker chooses the equipment necessary for the loading, for example, a forklift truck andan RF device, and logs on as a resource. He or she scans the door bin to start the loading of the TU in thesystem. He or she then picks an HU from the staging area and scans its label. He or she loads the HU ontothe truck and proceeds with the next HU until the staging area is empty. He or she checks for HUs fromother areas that have not yet been loaded, for example, high-value or overdimensional cargo, and picks andloads 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 TMupdates 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 thecheckpoint, 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. 11

message for departure from checkpoint to SAP TM. SAP TM updates the execution status of the freightorder.


Configuration: Transit Warehousing © 2015 SAP SE or an SAP affiliate company. All rights reserved. 12

4 Configuration: Transit WarehousingThis section describes the configuration necessary to run transit warehousing processes Receive from Shipperand Ship to Next Transit Warehouse with SAP Extended Warehouse Management (SAP EWM) in the first transitwarehouse of the LCL Air Freight scenario of SAP Transportation Management (SAP TM).

NoteThis section also contains configuration for additional transit warehouses in the LCL Air Freightscenario from SAP TM. In order to run both processes, you need to set up the configuration for thefirst transit warehouse only (warehouse number JPTY) 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 ERPinstalled on separate servers.

NoteIn a system landscape with SAP EWM installed on the same server as SAP ERP or SAP TM, theconfiguration of logical systems, business systems, and Core Interface (CIF) transfer differs. ForSAP EWM installed as Add-On to SAP ERP, see the configuration guide ‘Integration of SAP ERP withSAP EWM’. For SAP EWM installed on the same server as SAP TM, be aware that you use the samelogical system and business system for SAP TM and SAP EWM, and that the transfer of master datafrom SAP ERP must only be set up once.

4.1 Prerequisites

4.1.1 Installed ComponentsYou have installed and correctly configured the following applications:

SAP EWM 9.3SAP TM 9.3EHP 7 for SAP ERP 6.0 or higher

For more information, see the Master Guide for SAP EWM 9.0 on SAP Service Marketplace athttp://service.sap.com/instguides.

4.1.2 Prerequisites for System Connection in SAP ERP, SAPTM and SAP EWM

System administrators have to make specific settings for the integration of SAP ERP and SAP TM with SAP EWMbefore 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. Forexample, for the EWM test client to use the RFC destination for the ERP test client, an RFC user must existin the ERP test client.RFC destinations exist for the corresponding ERP, EWM and TM clients.

ProcedureCreate the following RFC destinations in Customizing for SAP NetWeaver under Application Server IDocInterface/Application Link Enabling (ALE) Communication Create RFC Connections:

In SAP ERP for SAP EWM, for example EWMCLNT001 (naming convention <SYS>CLNT<CLIENT>)In SAP TM for SAP EWM, for example EWMCLNT001In SAP EWM for SAP TM, for example TM1CLNT001

http://service.sap.com/instguides



4.1.3 Configuration Guide for LCL Air Freight Scenario inSAP TM

The Configuration Guide for LCL Air Freight scenario in SAP TM is already implemented, and the processesdescribed 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 EWMThe Transit Warehousing scenario contains process steps in SAP Transportation Management (SAP TM) and SAPExtended 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, forexample, a customer service agent, a transportation planner, and a capacity manager working exclusively in SAPTM, 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 DataThe following master data is used in SAP ERP throughout the LCL Air Freight scenario. For information about howto 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 andbusiness partners. In this configuration guide you set up the transfer of this data via CIF to SAP EWM.

NoteThe transfer of customers and vendors created in SAP ERP to SAP TM is described in theconfiguration guide for the LCL Air Freight scenario in SAP TM.

4.3.1 Customer Master Data in SAP ERPWith the configuration of the LCL Air Freight scenario in SAP TM, you have created the following customer masterdata for shippers and consignees in SAP ERP. Check the entries on the SAP Easy Access screen for SAP ERPunder Logistics Sales and Distribution Master Data Business Partner Customer Create Complete:

Field/Value Shipper 1 Shipper 2 Shipper 3 Shipper 4 Consignee 1

Consignee 2

Consignee 3

Consignee 4

Customer ID OAF-CU-01

OAF-CU-02

OAF-CU-03

OAF-CU-04

OAF-CO-01

OAF-CO-02

OAF-CO-03

OAF-CO-04

AccountGroup

KUNA:GeneralCustomers








CompanyCode 5000 5000 5000 5000 3000 3000 3000 3000

SalesOrganization

5000 5000 5000 5000 3000 3000 3000 3000

DistributionChannel 10 10 10 10 10 10 10 10

Division 00 00 00 00 00 00 00 00

Name Kanxinson

WabeiElectronic

JapanCable

SamuraiFireworks

DosenaClothing

TenMedia

SoutwireCo.

Scottsdale



ClothingCo. LTD.

s Factory LTD LTD Co.Factory

Inc. FireworksInc.

Street Kioi-cho Denenchofu Kawabe Shirokan

eStateRoute

StallardPl

WestMainStreet

AlmaSchoolRoad

HouseNumber 7–1 2-53-12 3-25 1-27-6 1710 W 10940 N 575 2012 N

Postal Code 1020094 1020021 5011198 1080072 86336 85737 92227 85256

City Chiyoda-ku Ota-ku Gifu Minato-

ku Sedona Tucson Brawley Scottsdale

Region 13 13 23 13 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 01 01 01 01 01 01 01 01

Cust. pric.proc. 1 1 1 1 1 1 1 1

ShippingConditions 01 01 01 01 01 01 01 01

OrderCombination

Select Select Select Select Select Select Select Select

Incoterm - - - - - - - -

IncotermLocations - - - - - - - -

Terms ofPayment(Sales areadata)

- - - - - - - -

TaxClassification

0 0 0 0 0 0 0 0

Reconciliation Account 145200 145200 145200 145200 144003 144003 144003 144003

Terms ofPayment 0001 0001 0001 0001 0001 0001 0001 0001

4.3.2 Vendor Master Data for Carriers in SAP ERPWith the configuration of the LCL Air Freight scenario in SAP TM, you have created the following customer masterdata for shippers and consignees in SAP ERP, Check the entries on the SAP Easy Access screen for SAP ERPunder Logistics Materials Management Purchasing Master Data Vendor Central Create:Key Data:



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 5000 5000 3000 3000 5000 5000 3000 3000

PurchasingOrganization

5000 5000 3000 3000 5000 5000 3000 3000

AccountGroup

0005 0005 0005 0005 0005 0005 0005 0005

Addresses:Vendor ID Name Search Term Address

OAF-CR-03 Uchida Trucking Truck Carrier JP

Tome Nagi 7-53-12,1020021, Ota-ku,Japan, Region 13(Tokyo)

OAF-CR-04 Ich-Ni Express Truck Carrier JP

Hadaka-Jime 15,4600001 Nagoya,Japan, Region 23(Aichi)

OAF-CR-05 ACME Lines Truck Carrier US

Beach Street 10,90745-1246 LongBeach, UnitedStates, Region CA

OAF-CR-06 Desert ExpressLines Truck Carrier US

First 355, 85025-8848 Phoenix,United States,Region AZ

AF-JL-NRT Rising SunAirlines Ltd. Air Carrier JP

Higashi-shinagawa2-chome, 4-11,1408637, Tokyo,Japan, Region 13(Tokyo)

AF-QF-NRT Oceanic Airways(Japan) KK Ltd. Air Carrier JP

Toranomon 37thMori Bldg 9F, 3-5-1, 1058483, Japan,Region 13 (Tokyo)

AF-JL-LAX Rising SunAirlines (US) Ltd. Air Carrier US

6041 W. ImperialHwy # D, 90245 LosAngeles,California, UnitedStates

AF-QF-LAX Oceanic Airways(US) KK Ltd. Air Carrier US

555 North NashStreet, 90245 LosAngeles,California, UnitedStates

Accounting Information:Vendor ID Reconciliation Account Cash Management GroupOAF-CR-03 141100 A1OAF-CR-04 141100 A1OAF-CR-05 196300 A1OAF-CR-06 196300 A1AF-JL-NRT 141100 A1



AF-QF-NRT 141100 A1AF-JL-LAX 196300 A1AF-QF-LAX 196300 A1Payment Transactions Accounting:Vendor ID Payment TermsOAF-CR-03 0002OAF-CR-04 0002OAF-CR-05 0002OAF-CR-06 0002AF-JL-NRT 0002AF-QF-NRT 0002AF-JL-LAX 0002AF-QF-LAX 0002Purchasing Data: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

OrderCurrency JPY JPY USD USD JPY JPY USD USD

Terms ofPayment 0002 0002 0002 0002 0002 0002 0002 0002

Incoterms - - - - - - - -PurchaseGroup - - - - - - - -

PlannedDeliveryTime

- - - - - - - -

Conf.Control - - - - - - - -

ShippingCondition - - - - - - - -



4.4 Configuration in SAP ERPIn 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.

ImportantSkip this section if you have implemented the configuration guide “Integration of SAP ERP with SAPEWM” in your SAP ERP and SAP EWM systems as the settings already exist.

4.4.1 Activating Business Transaction Events (BTE) in SAPERP

PrerequisitesYou have authorizations for cross-client settings on user and client level.

Procedure...

1. Activate online transfer using BTEs in Customizing for Integration with Other SAP Components underAdvanced Planning and Optimization Basic Settings for the Data Transfer Change Transfer ChangeTransfer 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

4.4.2 Configuring Logical Systems in SAP ERPPrerequisitesYou have authorizations for cross-client settings on user and client level....

Procedure1. 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 underExtended Warehouse Management Basic Settings for Setting Up the System Landscape NameLogical System.

2. Assign the ERP logical system defined in the first step to the ERP client (for example, in SAP ERP, assignERPCLNT001 to client 001) in Customizing for Integration with Other SAP Components under ExtendedWarehouse Management Basic Settings for Setting Up the System Landscape Assign Logical Systemto 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 ManagementBasic Settings for Setting Up the System Landscape Specify SAP APO Release, enter the values asshown in the following table for the EWM logical system:

Field Value

Log. System <Logical System>, for example EWMCLNT001

Syst. Type SAP_SCMB

Release <System Release>, for example 7.13 (or higher)

4.4.3 Assigning EWM Logical System to RFC Destination inSAP ERP

Procedure...



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 EWM logical system, for example, EWMCLNT001.3. 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.

4.4.4 Configuring qRFC Destination in SAP ERPThis setting is relevant for the qRFC communication from SAP ERP to SAP EWM.

Procedure...

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 transaction SMQS.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 Value

Destination <RFC Destination>, for example EWMCLNT001

Max. Conn. 10

Max. Runtime 60

W/o tRFC Leave this field empty

d. Choose Continue2. 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 WarehouseManagement Basic Settings for Setting Up the System Landscape Set Target System andQueue Type.

b. Create an entry for the EWM logical system with the following data:

Field Value

Log. System <Logical System>, for example EWMCLNT001

Q-Type I (Inbound Queues)

NoteThe Operation Mode field is automatically filled by the system when you generate, activate, ordeactivate CIF integration models.



4.5 Configuration in SAP EWM

4.5.1 Activating Business Functions in SAP EWMYou use this procedure to activate the business functions required for using transit warehousing processes in SAPExtended Warehouse Management (SAP EWM).

Procedure

Carry out these steps in an SAP EWM client that allows cross-client settings and the creation of workbenchrequests. 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 DescriptionSCM_EWM_FND EWM, Essential Foundation FunctionsFND_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)

4.5.2 Configuring Logical Systems in SAP EWMPrerequisitesYou have authorizations for cross-client settings on user and client level....

Procedure1. 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 Integrationwith Other SAP Components under Extended Warehouse Management Basic Settings for Setting Up theSystem Landscape Name Logical System:

Logical System Name

ERPCLNT001 ERPCLNT001

EWMCLNT001 EWMCLNT001

TM1CLNT001 TM1CLNT001

2. Assign the EWM logical system defined in the first step to the EWM client (for example, in SAP EWM, assignEWMCLNT001 to client 001) in Customizing for Integration with Other SAP Components under ExtendedWarehouse Management Basic Settings for Setting Up the System Landscape Assign Logical Systemto a Client.

4.5.3 Assigning Logical System to RFC Destination in SAPEWM

Procedure...

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.



3. 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,TM1CLNT001.6. 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.

4.5.4 Configuring Business SystemsYou use this procedure to define the business systems for SAP TM, SAP ERP, and SAP EWM in SAP EWM, and toassign a business system to the client.

NoteThe 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.

ProcedureCarry 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 GeneralSettings Define Business Systems, define a business system for the ERP client, the TM client, and theEWM 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

NoteIf you use the System Landscape Directory (SLD), the entries already exist. In this case, no action isrequired in this step.

2. In Customizing for Extended Warehouse Management under Interfaces ERP Integration GeneralSettings Define Own Business Systems, enter the EWM business system defined in the first step as yourown business system (for example, in system SAP EWM, client 001, enter EWM_001).

4.5.5 Configuring Business System GroupYou 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 CIFtransfer of master data from SAP ERP to SAP EWM. As SAP TM, SAP EWM, and SAP ERP share the same masterdata, you define the same business system group for all the systems.

NoteThe 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.

ProcedureCarry 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 BasicSettings for Creating the System Landscape Maintain Business System Group.



BusSystGrp Description

BG1 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 inCustomizing for SCM Basis under Integration Basic Settings for Creating the System LandscapeAssign Logical System and Queue Type.

BusSystGrp Logical system SAP Ind. Release Queue Type Err. Hndlg Role

BG1 EWMCLNT001 X 70(or higher)

I InboundQueue

Strict(Terminateat Errors)

NotSpecified

BG1 TM1CLNT001 X 9.00(or higher)

I InboundQueue


NotSpecified

BG1 ERPCLNT001 X 700(or higher)

I InboundQueue


NotSpecified

NoteThe release for the EWM logical system relates to the installed component SCM_BASIS and not tothe EWM component.

NoteYou can keep the default setting for the Error Handling in Target System field.

4.5.6 Configuring qRFC Destination in SAP EWMYou use this setting to configure the inbound queues in SAP EWM. This is relevant for the qRFC communicationfrom SAP ERP to SAP EWM, as well as for the XI communication from SAP TM to SAP EWM.

Procedure...

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 transaction SMQR.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 Value

Queue Name <used queue name>, we recommend that you useeither * or the following queue names: CF*, WM*, X*

Mode D

Max. Runtime 60

USERDEST Leave this field empty

Attempts 30

Pause 300

Scheduler Monitoring 0

d. Choose Continue2. 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 entryby double-clicking the status text in the qRFC monitor for inbound queues.



a. In SAP EWM, on the SAP Easy Access screen, call transaction SMQE.b. Choose Edit Register Display Program.c. Enter the queue and program names as shown in the following table:

Queue Name Program Name

CF* 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)

WM* /SCWM/QRFC_APPL_LOG_DISPLAY

X* RSXMB_SHOW_ENTRY

4.5.7 Activating the Planning Version and Model for MasterData

You use this procedure to create a planning version 000 and a model 000 for the creation of master data in SAPEWM. This technical setting is required for the CIF communication.

ProcedureCarry 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 informsyou whether the planning version and model already exist, or if the system just created them.

ImportantTransaction/SAPAPO/ACTVERCREATE requires an authorization for objects C_APO_MOD andC_APO_VERS with activity 01. You can use transaction SU53 to check failed authorization checksafter report execution.

4.5.8 Activating BC Sets in SAP EWMYou use this procedure to activate Business Configuration (BC) sets in SAP EWM. The BC sets containCustomizing settings at client level or at warehouse level.

ImportantIn order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the firsttransit warehouse of the LCL Air Freight scenario, you need to activate the warehouse-dependentBC sets in warehouse JPTY only.In order to manage all transit warehouses of the scenario with SAP EWM, activate the warehouse-dependent BC sets in all the warehouses: JPTY, JPNR, JPNG, USLA, USSA, and USPH.

Procedure...

1. On the SAP Easy Access screen for SAP EWM, choose Tools Customizing Business ConfigurationSets Activation of BC Sets (or use transaction SCPR20).

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 BasicSettings (Client) – Gen.

BC set at client level



/SCWM/TW_20_10 TW Settings (Warehouse) – 10 Enter the currency used in yourwarehouse, for example, JPYEnter the factory calendar used in yourwarehouse, for example, JPEnter your warehouse number, forexample, JPTY

/SCWM/DLV_BASIC_NUMBERRANGE

Delivery in EWM - Number Ranges BC set at client level.For more information, see the BC setdocumentation

/SCWM/DLV_INBOUND_TW Inbound Process for TransitWarehouse

BC set at client levelFor more information, see the BC setdocumentation

/SCWM/DLV_OUTBOUND_TW Outbound Process for TransitWarehouse

BC set at client levelFor more information, see the BC setdocumentation

/SCWM/TW_20_15 TW Number Range Int. for BasicSettings (Warehouse) – Gen.

Enter your warehouse number, forexample, JPTY

/SCWM/TW_20_20 TW Settings (Warehouse) – 20 Enter your warehouse number, forexample, JPTY

/SCWM/TW_25_91 TW Number Range Int. for BasicSettings (Warehouse) – HU

Enter a number in the From numberfield, for example,00000000000800000000In the Number range object subobjectvalue field, enter your warehousenumber, for example, JPTY,Enter a number in the To number field,for example,00000000000899999999If you activate the BC set in severaltransit warehouses, enter disjunctiveinternal HU number ranges for eachtransit warehouse. Otherwise awarehouse cannot receive an HU with anumber given by another warehouse.

/SCWM/SR_SCO_BCV(optional)

Configuration for Business ContextViewer - Shipping Cockpit

BC set at client levelTo use side panels in the transitwarehousing screens, activate this BCset.

/SCWM/TW_BCV(optional)

Measurement Services for TW inSidepanel

Enter your warehouse number, forexample, JPTYTo use side panels in the transitwarehousing screens, activate this BCset.

a. For each BC set, press Activate BC Setb. Enter the variables to be used by the BC set during activation (see column Comment above)c. Press Copy Values.

4.5.9 Configuring Action Profiles for TU and VehicleYou use this procedure to activate action definitions for transportation units (TUs) and vehicles.



NoteFor performance purposes, SAP recommends deactivating the PPF actions that are not needed forthe business scenario, as shown in the tables below. However, you should not deactivate a PPFaction if you use it in other scenarios or processes.

Procedure...

1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Shipping andReceiving 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 Inactive/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.

10. Deactivate the other PPF actions, unless you use them in other scenarios or processes, as shown in thefollowing 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.

4.5.10 Configuring Action Conditions for Transportation UnitYou use this procedure to assign an output device to action definition /SCWM/SR_TU_PRINT_HU_LABEL.

Procedure...



1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Shipping andReceiving 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 device LP01.5. Save your changes.

4.5.11 Checking Action Profiles for HUYou use this procedure to activate action definitions for handling units (HUs). They are used for sendingmessages to SAP Transportation Management.

Procedure...

1. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Handling UnitsBasics 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.

4.5.12 Activating Error and Conflict Handler in SAP EWMYou use this procedure to activate the error and conflict handling in service operations. This enables you to accessdetailed information about XI messages with errors in Monitor for Processed XML Messages (transactionSXI_MONITOR) and to process the messages after error resolution.

Procedure...

1. In Customizing for Extended Warehouse Management, choose Cross-Application ComponentsProcesses and Tools for Enterprise Applications Enterprise Services Error and Conflict HandlerActivate 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.

4.5.13 Defining Work Center Layout to Display Planned HUsYou use this procedure to create a work center layout for transaction Maintain Planned Shipping Handling Units(transaction /SCWM/CAP).

NoteTransaction Maintain Planned Shipping Handling Units is not required for transit warehousingprocesses, but can be used in the implementation phase for checking the system configuration orthe data consistency. Therefore, the following setting is optional, but recommended.

Procedure...

1. In Customizing for Extended Warehouse Management, choose Master Data Work Center SpecifyWork 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 TransitWhse

9



3. 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 Procedure Layout

JPTY CAP

6. Save your entry...

ResultYou can now use transaction /SCWM/CAP to display planned HUs created in transit warehousing processes byentering CAP Process Profile = space (explicitly use single value ‘=‘ by double-clicking on the entry field) inaddition to the selection criteria for your transit warehousing delivery.



4.6 Settings and Master Data in SAP ERP

4.6.1 Preparing Initial Transfer of Master Data from SAP ERPYou 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 isadjusted after each activation or deactivation of integration models. For more information, see the documentationof the report RCIFIMAX.

Procedure...

1. Configure change transfer of master data using BTEs in Customizing for Integration with other SAPComponents under Extended Warehouse Management Basic Settings for Data Transfer ChangeTransfer for Master Data Configure Change Transfer for Master Data.Enter the value 2 (BTE Transfer, Immediately) in the following fields:

Material Master Change TransferChange Transfer for CustomersChange 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, enter RCIFIMAX and choose Execute.c. In the Action to Execute screen area, choose Generation and then Execute.

4.6.2 Transferring Master Data from SAP ERP using CIFYou 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 selectioncriteria for the data. You activate the integration model manually. When you activate the model, the data istransferred.Once the data is contained in an active integration model, every change is communicated immediately to SAPEWM, as you have already activated the online transfer using BTE in the previous chapter,

ProcedureCarry 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 ModelCreate, or start transaction CFM1

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 theCustomer field.

d. Select the vendors you want to transfer to SAP EWM, for example, by entering OAF* in the Vendorfield.

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:



a. On the SAP Easy Access screen for SAP ERP, choose Logistics Central Functions SupplyChain Planning Interface Core Interface Advanced Planner and Optimizer Integration ModelCreate, or start transaction CFM2.

b. Select the integration model you just created and press Activate.

NoteIf you activate a model for the first time in a client, the system proposes in a dialog box to create anumber range interval for the object CIF_LOAD automatically. Accept the proposal.

c. Press Start.

4.6.3 Scheduling Background Job for Master Data TransferTo transfer master data that will be created in the future, you plan the transfer as a regular job.

ProcedureCarry out the following steps in the ERP client in which you create master data for SAP EWM:...

1. Create a variant for program RIMODDEL: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 program RIMODAC2: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 EntriesDo Not Issue Warning in Case of Parallel CIF Load

d. Save as a variant, for example, VIMEWMTW1.3. Define a background job for programs RIMODDEL, RIMODGEN, and RIMODAC2. 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 program RIMODDEL and variant VIMEWMTW1.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 program RIMODGEN and variant VIMEWMTW1.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 program RIMODAC2 and variant VIMEWMTW1.ii. Save your entries.

The Step List Overview screen appears.f. Go back.

g. Choose Start Condition.The Start Time screen appears.

h. Choose Date/Time.i. Enter the scheduled start date and time.



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.



4.7 Configuration in SAP TMIn addition to the configuration of the LCL Air Freight scenario in SAP TM, some settings are required in SAP TMfor managing a transit warehouse with SAP EWM.

4.7.1 Assigning Warehouse Number to LocationYou use this procedure to assign an SAP EWM warehouse number to a transit warehouse location in SAP TM.

ImportantFor the transit warehousing processes Receive from Shipper and Ship to Next Transit Warehouse,this setting is necessary for location OAF-STA-JPTYO only.

Procedure...

1. In SAP NetWeaver Business Client for SAP TM, choose Master Data Transportation NetworkLocations 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 WarehouseNumber

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

4.7.2 Transferring Locations and Business Partners fromSAP TM to SAP EWM

You use this procedure to transfer to SAP EWM the locations and business partner for all locations of thetransportation network created manually in SAP TM. Report /SCMTMS/BUPA_SEND_TRANS_WH createslocations and business partners in SAP EWM.

NoteAs warehouse number JPTY is assigned to location OAF-STA-JPTYO in SAP TM, the reportautomatically assigns the location (as a supply chain unit) to the warehouse number JPTY in SAPEWM, if the warehouse number does not have a supply chain unit yet.

Procedure...

1. In SAP TM, start transactionSE38, enter program /SCMTMS/BUPA_SEND_TRANS_WH, and pressExecute.

2. Select the locations of the transportation network:

Location Description

AF-GW-JPNRT Gateway Airport Narita

AF-GW-USLAX Gateway Airport Los Angeles



OAF-STA-JPNGO FH Station Nagoya

OAF-STA-JPTYO FH Station Tokyo

OAF-STA-USPHX FH Station Phoenix

OAF-STA-USSAN FH Station San Diego

3. Enter the logical system of SAP EWM, for example EWMCLNT001, 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 TransportationNetwork..

Refer



4.8 Settings and Master Data in SAP EWM

4.8.1 Checking Business Partners of Transportation NetworkThe following table gives an overview of the business partners used for the transportation network of the LCL AirFreight scenario. In this procedure, you check that the business partners created manually in SAP TM andtransferred to SAP EWM with report /SCMTMS/BUPA_SEND_TRANS_WH are available in SAP EWM.

Field/Value BusinessPartner 1

Business Partner2

BusinessPartner 3

BusinessPartner 4

BusinessPartner 5

BusinessPartner 6

BusinessPartner ID

OAF-FWH-05 OAF-FWH-01 AF-FWH-03 AF-FWH-20 OAF-FWH-22

OAF-FWH-21

BP Role BusinessPartner Gen.

Business PartnerGen.

BusinessPartner Gen.

BusinessPartnerGen.



Name FH Tokyo FH Nagoya Gateway Narita GatewayLos Angeles

FH SanDiego

FH Tempe

Search Term1/2

FWHSTATION/JP

FWHSTATION/JP

FWHGateway/JP

FWHGateway/US

FWHSTATION/US

FWHSTATION/US

Street/House number

6-23-15Shiba/-

8-3 KanayamaCho 1

Building 725-5 SpectrumDrive

Niels BohrCourt 2296

South HardyDrive 8123

PostalCode/City

1080014/Tokyo

4560002/Nagoya

1080398/Narita

92602/Irvine

92154/SanDiego

85284-1106/Tempe

Country JP JP JP US US US

Region 13 23 12 CA CA AZ

Time Zone JAPAN JAPAN JAPAN PST PST MSTNO

Procedure...

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.

4.8.2 Checking Locations of Transportation NetworkThe following table gives an overview of the locations used for the transportation network of the LCL Air Freightscenario. In this procedure, you check that the locations created manually in SAP TM and transferred to SAP EWMwith report /SCMTMS/BUPA_SEND_TRANS_WH are available in SAP EWM.

Field/Value Location1 Location 2 Location 3 Location 4 Location 5 Location 6

LocationOAF-STA-JPTYO

OAF-STA-JPNGO

AF-GW-JPNRT

AF-GW-USLAX

OAF-STA-USPHX

OAF-STA-USSAN

Description FHStationTokyo

FHStationNagoya

GatewayAirportNarita

GatewayAirportLosAngeles

FHStationPhoenix

FHStationSan Diego

LocationType

1002 1002 1150 1150 1002 1002

Ext. Location OAF-STA-JPTYO

OAF-STA-JPNGO

AF-GW-JPNRT

AF-GW-USLAX

OAF-STA-USPHX

OAF-STA-USSAN

Bus.SystemGroup

BG1 BG1 BG1 BG1 BG1 BG1



Time Zone JAPAN JAPAN JAPAN PST MSTNO PSTSearch Term FH

StationFHStation

GatewayNarita

GatewayLAX

FHStation

FHStation

Address 6-23-15Shiba,Minato-ku,Tokyo,1080014

8-3KanayamaCho 1,Nagoya,4560002

Building727-5,NaritaAirport,1080398

SpectrumDrive,Building1755,Irvine, 92602

8123SouthHardyDrive,Tempe,85284-1106

2296NielsBohrCourt,SanDiego,92154

Country JP JP JP US US USRegion 13

(Tokyo)23 12

(Chiba)CA(California)

AZ(Arizona)

CA(California)

IATA Code - - NRT LAX - -UN/LOCODE JPTYO JPNGO JPTYO USLAX USPHX USSANBusinessPartner

OAF-FWH-05

OAF-FWH-01

AF-FWH-03 AF-FWH-20 OAF-FWH-21

OAF-FWH-22

For each location, the following geo-coordinates should be available

Location Longitude LatitudeOAF-STA-JPTYO + 139: 30: 00 + 35: 45: 00OAF-STA-JPNGO + 137: 15: 00 + 35: 00: 00AF-GW-JPNRT + 140: 23: 11 + 35: 45: 53AF-GW-USLAX - 118: 24: 29 + 33: 45: 53OAF-STA-USPHX – 112: 05: 44 + 33: 33: 31OAF-STA-USSAN - 119: 30: 00 + 37: 30: 00

Procedure...

1. 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

4.8.3 Maintaining Supply Chain Units for Transit WarehousesThe locations of the transportation network transferred from SAP TM to SAP EWM also exist as supply chain unitsin SAP EWM. In this procedure, you maintain attributes for the supply chain units in order to use them as transitwarehouse, receiving office, and shipping office in SAP EWM.

ImportantIn order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the firsttransit warehouse of the LCL Air Freight scenario, you need to maintain supply chain unit OAF-STA-JPTYO only.

Procedure...

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 Business AttributesOAF-STA-JPTYO INV, PLOC, RO, SOOAF-STA-JPNGO INV, PLOC, RO, SOAF-GW-JPNRT INV, PLOC, RO, SOAF-GW-USLAX INV, PLOC, RO, SOOAF-STA-USPHX INV, PLOC, RO, SOOAF-STA-USSAN INV, PLOC, RO, SO

3. Save your entries



4.8.4 Maintaining Logical Conditions for Bin DeterminationYou use this procedure to create logical conditions for bin determination.

NoteFor more information about the condition records for bin determination, see Appendix C: ConditionRecords for Bin Determination.

Procedure...

1. On the SAP Easy Access screen for SAP EWM, choose Extended Warehouse Management -> Settings ->Transit Warehousing -> 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_25PC_JPNG_10_25PC_JPNR_10_25


&Cons. Postal Code& >=1000000 and&Cons. Postal Code& <=2500000



&Cons. Postal Code& >2500000 and&Cons. Postal Code& <=5000000




PC_JPTY_OTHERPC_JPNG_OTHERPC_JPNR_OTHER

PC_JPTY_OTHERPC_JPNG_OTHERPC_JPNR_OTHER

&Cons. Postal Code& >7500000

3. Save your entries.4. Create the following entries:

Logical Condition Description Formula

PC_USLA_80_86PC_USSA_80_86PC_USPH_80_86


&Cons. Postal Code& >=80000 and&Cons. Postal Code& <=86000







PC_USLA_OTHERPC_USSA_OTHERPC_USPH_OTHER

PC_USLA_OTHERPC_USSA_OTHERPC_USPH_OTHER

&Cons. Postal Code& <80000 and&Cons. Postal Code& >93000

5. Save your entries.



4.8.5 Checking Assignment of Supply Chain Unit toWarehouse Number

You use this procedure to check the assignment of a supply chain unit to your transit warehouse.

ImportantIn order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the firsttransit warehouse of the LCL Air Freight scenario, an entry is required for warehouse number JPTYonly.

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 thewarehouse 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. Inthis case, the warehouse number uses a supply chain unit that differs from the location used in SAP TM.

Procedure...

1. On the SAP Easy Access screen for SAP EWM, choose Extended Warehouse Management SettingsAssignments: Warehouse Numbers/Business Partners Assign Warehouse Numbers.

2. Check that a supply chain unit is assigned to your transit warehouse. If the assignment was createdautomatically by report /SCMTMS/BUPA_SEND_TRANS_WH, the following supply chain units areassigned to the transit warehouses:

Warehouse Number Supply Chain Unit Custodian Default Party Entitled toDispose

JPTY OAF-STA-JPTYO - -

JPNG OAF-STA-JPNGO - -

JPNR AF-GW-JPNRT - -

USLA AF-GW-USLAX - -

USPH OAF-STA-USPHX - -

USSA OAF-STA-USSAN - -

4.8.6 Creating Warehouse Structure and Condition Recordsfor Bin Determination

You use this procedure to create or maintain the following objects related to the warehouse structure of a transitwarehouse automatically in SAP EWM:

Storage binsStaging area and door determinationBin assignment for work centersCondition records for bin determination

For this purpose, you use the BDC files attached to SAP Note 2124830.

NoteIn order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the firsttransit warehouse of the LCL Air Freight scenario, you need to process BDC files related towarehouse number JPTY only.

NoteThe same warehouse structure can be used for all transit warehouses across the transportationchain of the LCL Air Freight scenario. However, the bins created in some storage types are not

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=2124830&



needed in all locations. For example, areas used for loading and unloading HU containers are onlyrequired in warehouses representing a gateway.

Procedure...

Implement the steps described in SAP Note 2124830.

ResultYou have created a warehouse structure that is typical for transit warehouses. The warehouse layout and thecondition records for bin determination are meant as examples and illustrate several configuration options for thewarehouse-internal processing, such as:

Putaway to bins with limited or unlimited bin capacitiesPutaway to bins using document references, such as forwarding order reference, as consolidation groupsPutaway to bins for single or multiple destination countries, regions, or postal codesSetup with or without a separate staging step before loading

NoteFor more information about the condition records for bin determination, see Appendix C: ConditionRecords for Bin Determination.

The following figure shows the warehouse layout you created with the BDC files, and is followed by a legendexplaining the different elements of the warehouse layout:




Legend

Layout StorageType

Storage TypeDescription

Use and Structure

H040 Area forDangerousGoods

Used to store dangerous goods.Bin capacity for cargo that is notoverdimensional.Cargo is stored together in storagesections by dangerous goodsregulation and dangerous goods class.One section is for dangerous goods ofregulation ADR class 1 and one sectionis for all other dangerous goods.Putaway is to bins with the sameconsolidation group (for example,consolidation by forwarding order) ornext empty bin, depending on capacityand consolidation groups.Due to setup with capacity andputaway rule using consolidationgroup, a corresponding overflow bin issetup (see storage type H980Overflow Zones).Cargo in this area is staged beforephysical loading.

H050 Area for HighValue Cargo

Used to store high-value cargo in aspecial area in the warehouse withlimited access.Bin capacity for cargo that is notoverdimensional.No storage sections.Putaway is to bins with the sameconsolidation group (for example,consolidation by forwarding order) ornext empty bin, depending on capacityand consolidation groups.Due to setup with capacity andputaway rule using consolidationgroup, a corresponding overflow bin issetup (see storage type H980Overflow Zones).Cargo in this area is not staged beforephysical loading, in order to reduce thetime in which the cargo is not in thelimited access area.Note that if you load a transit HU fromthis area, the bins are still reserveduntil the TU has left the warehouse.

…

H910 Staging Areas –Inbound andOutbound

Used for receiving HUs or HUcontainers.Bins are assigned to one or severaldoors.Some dedicated bins, GR-01 – GR-05,are assigned to single doors that areused in inbound processes only,intended for the receiving of transitHUs from shipper.Bins are used as goods movement binupon receiving.



No capacity limitations.

H920 Area byPostcode andRegion

Used for cargo that is to be deliveredto a final destination within samecountry or region as the one of thewarehouse.Cargo with the following finaldestination is stored together:

- The same region- The same group of regions- The same postal code ranges

For this purpose, several storagesections exist:

- For special regions- For all other regions- For storage by postal code

rangeNo capacity limitations.Cargo in this area is not staged beforephysical loading. The bins are alreadynext to the doors that will be assignedto the TU by the warehouse clerk upontruck arrival.

H921 Area by Country– Bins byShipment

Used for cargo to be delivered to thenext destination in another country.Cargo with the following nextdestination is stored together:

- The same country- The same group of countries

Putaway is to bins with sameconsolidation group (for example,consolidation by forwarding order) ornext empty bin, depending on capacityand consolidation groups. Special binsare used for overdimensional cargo.Due to setup with capacity andputaway rule using consolidationgroup, a corresponding overflow bin issetup (see storage type H980“Overflow Zones”).Cargo in this area is staged beforephysical loading to TUs or TUcontainers, or is moved to the area forloading onto HU containers.

H922 Area forUnloading fromHU Container

Used for unloading cargo from HUcontainers.No capacity limitations.Bin is assigned to work center WUCHfor unloading cargo from HUcontainers.



H923 Area forLoading ontoHU Container

Used for loading cargo onto HUcontainers.No capacity limitations, but putaway isto bins with same consolidation group(for example, consolidation by freightbooking) or next empty bin.Inbound sections of work centersWC01-WC03 are used for transit HUs.Main bins are used for HU containersand are assigned to a work center.Areas for loading of HU containerswith the following final destination:

- The same country- The same group of countries

HU containers are not staged beforephysical loading.

H970 ClarificationZone

Used for transit HUs that requireclarification such as damaged HUs orHUs with special attributes that arenot detailed in the forwarding order.No capacity limitations.

…

H980 Overflow Zones Used for transit HUs if no bin can bedetermined for putaway in the areawhere this cargo would normally go.- Bin C-OVERFLOW used for

overflow in storage type H921“Area by Country – Bins byShipment”.

- Bin DG-OVERFLOW used foroverflow in storage type H040“Area for Dangerous Goods”.

- Bin HV-OVERFLOW used foroverflow in storage type H050“Area for High Value Cargo”.

No capacity limitations.Cargo from C-OVERFLOW and DG-OVERFLOW is staged before physicalloading to TUs.Cargo from HV-OVERFLOW is notstaged before physical loading to TUsin order to reduce the time in whichthis cargo is not in the limited-accessarea.

After you have created the storage bins as described, you can display the warehouse layout. On the SAP EasyAccess screen for Extended Warehouse Management, choose Monitoring Graphical Warehouse LayoutDisplay Graphical Warehouse Layout. The following figure shows the rack view and the bin view of the graphicalwarehouse layout:



Rack View Bin View

Graphical Warehouse Layout

4.8.7 Creating Determination Records for Printing HU WaybillLabels

You use this procedure to create condition records for printing HU labels, for example when executing action PrintHU Label on the Loading Preparation screen or on the HU Stock List screen. The condition record decides ifprinting should take place. The decision to print is based on the fields maintained in the condition record. Inaddition, the condition record determines the printer, form, and spool data, and whether a house waybill label(form group 1) or a master waybill label (form group 2) is printed.

ImportantIn order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the firsttransit warehouse of the LCL Air Freight scenario, you need to create a condition record forwarehouse JPTY only.

Procedure...

1. On the SAP Easy Access screen for SAP EWM, choose Work Scheduling Print Settings CreateCondition Records for Printing (HUs) (or use transaction PRHU6).

2. On the selection screen, enter application PHU, maintenance group PHU, and choose Execute (F8).3. On the Selection of key combination screen, choose condition table SAPHU004.4. Create the following entries:

Field Value Value

Condition Type 0HU4 0HU4

HU Type - -

Warehouse JPTY JPNR

HU Cat. TR TR



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 example LP01

Spool Data 01 01

PPF: Name of Action Definition HU_LABEL_GENERAL_AND_RF HU_LABEL_GENERAL_AND_RF

Det. No. 2 2

Type C C


4.8.8 Creating Packaging MaterialsYou use this procedure to create packaging materials manually in SAP EWM. The packaging materials are used tocreate handling units (HUs), transportation units (TUs), HU containers, TU containers and planned vehicles(outbound only) in SAP EWM.

NoteFor more information about the usage of packaging materials in transit warehousing processes, seeAppendix D: Determination of Packaging Materials in SAP EWM.

Procedure...

1. On the SAP Easy Access screen for SAP EWM, choose Extended Warehouse Management Master Data Product Maintain Product.


Field/Value Product 1 Product 2 Product 3 Product 4 Product 5

Product PALLET BOX OAF_TRUCK PAG6 PMC6

ProductDescription

Pallet Box OAF_TRUCK- AirFreightScenario

Pallet Q6Contour(88x125x96)


Base Unit ofMeasure

EA EA EA EA EA

PkgData/Pack.Mat.Type

PAL BOX MTR2 ULDP ULDP

Pkg Data/HUType

E1 C1 M1 E1 E1

Gross Weight 20 0.5 12 105 480

Unit ofWeight

KG KG TO KG KG

ClosedPackaging

- X - - -

3. Save your entries4. Create the following entries



Field/Value Product 7 Product 8 Product 3 Product 4 Product 5 Product 6

Product AKE AAP AMA PAG7 PGA7 PMC7

ProductDescription

Half-WidthLowerDeck Cont(61x60)(LD3)

LowerDeckContainer(88 x125)(LD9)

Main DeckContainer(96x125)(M1)




Base Unit ofMeasure

EA EA EA EA EA EA

PkgData/Pack.Mat.Type

ULD ULD ULD ULDP ULDP ULDP

Pkg Data/HUType

E1 E1 E1 E1 E1 E1

Gross Weight 100 222 360 480 480 480

Unit ofWeight

KG KG KG KG KG KG

ClosedPackaging

X X X - - -


4.8.9 Defining the Link between Packaging Material and MTR inSAP EWM

You use this procedure to link a packaging material to a means of transport for the creation of a TU or vehicle.

NoteFor more information about using packaging materials in transit warehousing processes, seeAppendix D: Determination of Packaging Materials in SAP EWM.

Procedure...

1. On the SAP Easy Access screen for SAP EWM, choose Extended Warehouse Management SettingsShipping 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:

MTr Pack.Material Optional Seq.PMs No. PMs in MTr Cont. PM

OAF_TRUCK OAF_TRUCK X - - -

OAF_TRUK_S OAF_TRUCK X - - -

OF_TR OAF_TRUCK X - - -

3. Save your entry.

4.8.10 Defining Resource GroupYou use this procedure to set up resource management in SAP EWM. A resource is an entity representing a useror equipment, which can execute work in the warehouse. Resources are typically used when working with radiofrequency (RF) devices. With resource management, you can define work queues, assign warehouse orders to thequeues, and allow specific resources to work on specific queues. A resource group groups together resourceswith similar characteristics.



ImportantIn order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the firsttransit warehouse of the LCL Air Freight scenario, an entry is required for warehouse number JPTYonly.

Procedure...

1. On the SAP Easy Access screen for SAP EWM, choose Master Data Resource Management MaintainResource Group.


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 01


4.8.11 Defining Queue Sequence for Resource GroupYou use this procedure to create queue sequences for resource groups.

ImportantIn order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the firsttransit warehouse of the LCL Air Freight scenario, entries are required for warehouse number JPTYonly.

Procedure...

1. On the SAP Easy Access screen for SAP EWM, choose Master Data Resource Management MaintainQueue Sequence for Resource Group.


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 -



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 -


4.8.12 Defining Presentation DeviceYou use this procedure to define a presentation device used in RF.

Procedure...

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 **


4.8.13 Defining ResourcesYou use this procedure to create resources representing the warehouse workers.

ImportantIn order to run the processes Receive from Shipper and Ship to Next Transit Warehouse in the firsttransit warehouse of the LCL Air Freight scenario, entries are required for users working inwarehouse number JPTY only.

Procedure...

1. On the SAP Easy Access screen for SAP EWM, choose Master Data Resource Management MaintainResource.


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




4.9 Configuration for SAP NetWeaver Process Integration

4.9.1 Checking Connection to SLD in SAP TM and SAP EWMThe application systems must be defined as business systems in the System Landscape Directory (SLD). You usethis procedure to check that your application systems for SAP TM and SAP EWM are correctly connected to theSLD.

ProcedureStart transaction SLDCHECK in SAP EWM and SAP TM. If the connection to SLD is configured correctly, theSystem Landscape Directory application appears in a new window. Close this new window and check the logdisplayed in transaction SLDCHECK.If the SLDCHECK is not successful, and there are error messages displayed after execution of transactionSLDCHECK 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 PIsystem>For example,Dest://IS_X3X

-

RUNTIME LOGGING_SYNC - - 1 0

4.9.2 Creating a Configuration Scenario for LoadingAppointment Integration

In the SAP NetWeaver PI system, you create a configuration scenario between SAP TM and SAP EWM by usingthe integration scenario Loading appointment integration:TM_EWMLoadingAppointmentIntegration as a template.

Procedure1. 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 scenario TM_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 SystemComponent for A2A tab page, enter the communication component for SAP TM, for example, TMS_001.

8. Click on the title of the second swimlane (SAP EWM) and, on the Business System Component for A2A tabpage, enter the communication component for SAP EWM, for example, EWM_001.



9. Click on the connector between Send Loading Appointment Request in the SAP TM swimlaneand Receive Loading Appointment Request in the SAP EWM swimlane. On the Connectionsfrom Component Assignment tab page, assign the communication channel for the Receiver BusinessSystem Component, for example GeneratedReceiverChannel_XI.

NoteIt is not necessary to assign a communication channel to the Sender Business System Component.

10. Click on the connector between Send Loading Appointment Notification in the SAP EWMswimlane and Receive Loading Appointment Notification in the SAP TM swimlane. On theConnections from Component Assignment tab page, assign the communication channel for the ReceiverBusiness System Component, for example GeneratedReceiverChannel_XI.

11. Click on the connector between both Get Transportation Document URI boxes. On theConnections from Component Assignment tab page, assign the communication channel for the ReceiverBusiness System Component, for example GeneratedReceiverChannel_XI.In addition, select the Direct Connection checkbox, as this connection is used for the navigation betweenSAP 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 ascreen on which you can select and activate all changes.

ImportantSince all configuration data is stored in the main memory, you must refresh the runtime cache inSAP NetWeaver PI with transaction SXI_CACHE, or SAP NetWeaver PI will not use the settings.

More Information

For more information about configuring integration scenarios, see SAP Library for SAP NetWeaver 7.4 athttp://help.sap.com/netweaver under SAP NetWeaver Platform SAP NetWeaver 7.4 Application HelpFunction-Oriented View. Choose SAP NetWeaver Library: Function-Oriented View Process IntegrationIntegration Directory Integration Directory (Dual Stack) Using Tools to Configure Efficiently Using theProcess Model as a Configuration Template Configuring Process Integration Scenarios.

http://help.sap.com/netweaver



4.10 Configuration of Navigation between SAP EWM and SAPTM

In this section you set up the navigation from SAP EWM to SAP TM or vice versa using links that are available inthe screens in the SAP NetWeaver Business Client. For example, when a vehicle arrives to pick up HU containersor TU containers with cargo from a freight booking, you navigate from the Loading Preparation screen in SAPEWM to the Freight Booking screen in SAP TM in order to create a pick-up freight order with reference to thefreight booking in SAP TM.

NoteThe navigation is not necessary to run the processes Receive from Shipper and Ship to Next TransitWarehouse in the first transit warehouse of the LCL Air Freight scenario. It is recommended forprocesses involving freight bookings.

ImportantIf you start SAP NetWeaver Business Client from an SAP TM system, you can navigate to the SAPEWM screens Prepare Loading or Unloading and Process Freight Orders. Further navigation fromthese SAP EWM screens to other SAP EWM transactions is not supported.

PrerequisitesYou have created and configured a configuration scenario for loading appointment integration in the SAPNetWeaver PI system as described in Creating a Configuration Scenario for Loading AppointmentIntegration.The same user exists in SAP TM and SAP EWM with user roles enabling him or her to perform processsteps in both applications. Typically, a user role based on /SCWM/EXPERT is assigned to the user in SAPEWM and a user role based on /SCMTMS/TRANSPORTATION_MGR_V2 is assigned to the user in SAPTM.The user can start the SAP NetWeaver Business Client in SAP EWM and SAP TM.

4.10.1 Creating Connection for Navigation in SAP EWMThe settings require authorizations for cross-client settings on user and client level.

Procedure1. 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 example TM1CLNT001_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 exampleTM1CLNT001_T_HTTP or TM1CLNT001_T_HTTPS. Select Current User here too.

2. In SAP EWM, create a new variable for the RFC destination with transaction SM30_SSM_RFC:

Variable RFC Destination

TM TM1CLNT001_T

4.10.2 Configuring User for Navigation in SAP EWMYou use this procedure to assign object-based navigation content to an SAP EWM user role. The content isneeded for users starting the SAP NetWeaver Business Client from the SAP EWM system.



Procedure1. On the SAP Easy Access screen for SAP EWM, choose Tools Administration User Maintenance Role

Administration Roles.2. Enter a role, for example Z_EWM_OBN_TM, and press the Create Single Role button.3. Enter a description, for example, OBN Navigation EWM to TM, and save the role4. On the Menu tab page, choose Copy Menus From Another Role Target System.5. Select the RFC Destination for SAP TM, for example, TM1CLNT001.6. Select role /SCMTMS/PROCESS_ADMINISTRATOR.7. Open the OBN-Target node and select the nodes needed for navigation, for example:

Forwarding Order ManagementFreight Order ManagementEWM 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 profile11. Save your entries

4.10.3 Creating Connection for Navigation in SAP TMThe settings require authorizations for cross-client settings on user and client level.

Procedure1. 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 exampleEWMCLNT001_T_HTTP or EWMCLNT001_T_HTTPS. Select Current User here too.

2. In SAP TM, create a new variable for the RFC destination with transaction SM30_SSM_RFC:

Variable RFC Destination

EWM EWMCLNT001_T

4.10.4 Configuring User for Navigation in SAP TMYou use this procedure to assign object-based navigation content to an SAP TM user role. The content is neededfor users starting the SAP NetWeaver Business Client from SAP TM.



Procedure1. On the SAP Easy Access screen for SAPTWM, choose Tools Administration User Maintenance Role

Administration Roles.2. Enter a role, for example Z_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 ManagementFreight Order ManagementEWM 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 profile10. Save your entries


Test Case: Receive from Shipper © 2015 SAP SE or an SAP affiliate company. All rights reserved. 51

5 Test Case: Receive from ShipperYou can use this test case to run the process Receive from Shipper in warehouse number JPTY.

5.1 PrerequisitesThis test case requires the following roles:

Warehouse Operator with role EWM: Warehouse Expert (/SCWM/EXPERT)For more information, see the prerequisites for Configuration: Transit Warehousing.You have configured SAP ERP, SAP Extended Warehouse Management (SAP EWM), SAP TransportationManagement (SAP TM) and XI as described in Configuration: Transit Warehousing.

5.2 FeaturesThis test case uses the following applications in SAP TM, which you can find in the Transportation Managementmenu of the SAP NetWeaver Business Client (NWBC):

Forwarding Order Management Forwarding Order Create Forwarding OrderFreight Order Management Road Create Road Freight OrderFreight Order Management Road Edit Road Freight Order

This test case uses the following applications in SAP EWM, which you can find in the Extended WarehouseManagement menu of the NWBC:

Transit Warehousing Process Single Freight OrderTransit Warehousing Process Freight OrdersTransit Warehousing Prepare Loading or UnloadingTransit Warehousing Handling-Unit Stock List

This test case uses the following transactions in SAP EWM, which you can find on the SAP Easy Access screen forExtended Warehouse Management:

Execution Log On to RF Environment (transaction /SCWM/RFUI)

5.3 Activities

StepStepDescription

StepProcessor Input Data Expected Results

1 Createforwardingorder (SAP TM)

CustomerServiceClerk

...

See Testcase for LCL Air FreightScenario (SAP TM)

Note down the forwardingorder number for later use

2 Create freightorder (SAP TM)

Transportation Planner

...


Note down the freightorder number for later use

3 Send unloadingrequest totransitwarehouse(SAP TM)


1. From the TransportationManagement menu in NWBC,choose Freight Order Management

Road Edit Road Freight Order.2. Enter the freight order number

noted down in step 2 and pressContinue.

3. From the Set Item Status dropdown list, choose Set to CargoReady for Unloading.

4. Press Save.5. Choose the Output Management

tab page and check thatTOR_LDAP_REQ was successfullyprocessed.

The freight order istransferred to SAP EWM.

The correspondingobjects are created in SAPEWM, like vehicle, TU, andinbound delivery as freightorder.


Test Case: Receive from Shipper © 2015 SAP SE or an SAP affiliate company. All rights reserved. 52

4 Assign a door tothe TU and postthe arrival at thedoor (SAPEWM)

ReceivingOffice Clerk

1. In SAP EWM, open the ProcessSingle Freight Order screen.

2. In the Freight Order field, enter thefreight order number noted down instep 2. Leave the TOR Stop ID fieldempty and press Continue.

3. In the TUs/Container TUs tab page,select the row of the TU

4. Choose Arrival at Door and assign afree door.

TU has status Arrival andAt Door.

5 Receive theHUs (SAPEWM)

WarehouseClerk

1. Start transaction /SCWM/RFUI.2. Log on to the warehouse JPTY as

resource <Your Name> withpresentation device PD01.

3. Choose Inbound ProcessesReceiving of Handling UnitsReceiving by TU/Door (TW) (fastpath 347).

4. Enter the door you used in step 4.5. 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 logoffscreen. Choose Logoff (F1) andSave (F1).

Goods receipt has beenposted for the HUs and anLDAP-Notificationmessage with the actualdata is sent back to SAPTM. Note down the HUnumbers for later use.

6 Truck leaves(SAP EWM)




3. Press Departure from Checkpoint.

TU has status Departureand an LDAP-Notificationmessage with thedeparted status is sentback to SAP TM.

7 Putaway theHUs (SAPEWM)

WarehouseWorker



3. Choose Inbound ProcessesPutaway Putaway by HU (fastpath 331).

4. Enter the HU number noted down instep 8 and press Enter.

5. Verify the destination bin and theHU number.

6. Repeat this procedure for all theHUs you received.

7. After you are finished press Back(F7) until you come to the logoffscreen and press Logoff (F1) andSave (F1).

The HUs are put away intothe destination storagetype.


Test Case: Ship to Next Transit Warehouse © 2015 SAP SE or an SAP affiliate company. All rights reserved. 53

6 Test Case: Ship to Next Transit WarehouseYou can use this test case to run the process Ship to Next Transit Warehouse in warehouse number JPTY.

6.1 PrerequisitesThis test case requires the following roles:

Warehouse Operator with role EWM: Warehouse Expert (/SCWM/EXPERT)For more information, see the prerequisites in Configuration: Transit Warehousing.You have configured SAP ERP, SAP Extended Warehouse Management (SAP EWM), SAP TransportationManagement (SAP TM), and XI as described in Configuration: Transit Warehousing.

6.2 FeaturesThis test case uses the following applications in SAP TM, which you can find in the Transportation Managementmenu of the SAP NetWeaver Business Client (NWBC):

Forwarding Order Management Forwarding Order Create Forwarding OrderFreight Order Management Road Create Road Freight OrderFreight Order Management Road Edit Road Freight Order

This test case uses the following applications in SAP EWM, which you can find in the Extended WarehouseManagement menu of the NWBC:

Transit Warehousing Process Single Freight OrderTransit Warehousing Process Freight OrdersTransit Warehousing Prepare Loading or UnloadingTransit Warehousing Handling-Unit Stock List

This test case uses the following transactions in SAP EWM, which you can find on the SAP Easy Access screen forExtended Warehouse Management:

Execution Log On to RF Environment (transaction /SCWM/RFUI)

6.3 Activities

StepStepDescription

StepProcessor Input Data Expected Results

1 Create freightorder for stage2 forprecarriage(SAP TM)


...


Note down the freightorder number for later use



2 Send loadingrequest totransitwarehouse(SAP TM)


1. From the menu choose FreightOrder Management Road EditRoad Freight Order.

2. Enter the freight order numbernoted down in step 1 and pressContinue.

3. From the Set Status drop down list,choose Set to Ready forTransportation Execution.

4. From the Set Item Status dropdown list, choose Set to CargoReady for Loading.

5. Press Save.6. Choose tabstrip Output

Management, and check thatTOR_LDAP_REQ was successfullyprocessed.

The freight order istransferred to SAP EWM.

The correspondingobjects are created in SAPEWM, like vehicle, TU, andoutbound delivery asfreight order.

3 Truck Arrives atCheckpoint(SAP EWM)




3. In the TUs/Container TUs tab page,select the row of the TU.

4. Choose Arrival at Door and assign afree door.

TU has status Arrival andAt Door.

Note down the HUnumbers from the screenarea HUs/Container HUs.

4 Stage HUs(optional) (SAPEWM)

WarehouseClerk



3. Choose Manual SelectionSelection by HU (fast path 22)

4. Enter the HU number noted down instep 3 and press Enter.

5. The source data is displayed. PressEnter.

6. Verify the destination bin and pressEnter.

7. Repeat this procedure for all theHUs you noted down.

8. After you are finished, press Back(F7) until you come to the logoffscreen and press Logoff (F1) andSave (F1).

The HUs are staged.



5 Load Truck(SAP EWM)

WarehouseClerk



3. Choose Outbound ProcessesLoading Loading by TU / Door(TW) (fast path 438).

4. Enter the door you used in step 3.5. 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 logoffscreen. Choose Logoff (F1) andSave (F1).

The HUs have the statusLoaded and an LDAP-Notification message withthe actual data is sentback to SAP TM.

6 Truck leaves(SAP EWM)

ShippingOffice Clerk


2. In the Freight Order field, enter thefreight order number noted down instep 1. Leave the TOR Stop ID fieldempty and press continue

3. Press Departure from Checkpoint.

TU has the statusDeparture and an LDAP-Notification message withthe departed status is sentback to SAP TM.


Appendix © 2015 SAP SE or an SAP affiliate company. All rights reserved. 56

7 AppendixThe appendix contains additional information about the transit warehousing scenario. It describes additionalinformation that gives a better understanding of the configuration. It also contains additional configuration notrequired in the preconfigured transit warehouse, but that may be necessary for using transit warehousingprocesses in your own warehouse.

7.1 Appendix A: Checking Basic Table Entries Used in SAPTM, SAP ERP, and SAP EWM

Basic tables such as units of measure, currencies, countries, and languages are used by SAP ERP, SAPTransportation Management (SAP TM) and SAP Extended Warehouse Management (SAP EWM). Entries used inprocesses 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 warehousingprocesses are identical in all systems that are part of your system landscape.

Procedure...

1. On the SAP Easy Access screen for SAP EWM choose Tools Administration Administration ClientAdministration Customizing Objects Object Comparison.

2. Compare the information in the following tables between the EWM client and the ERP client and betweenthe EWM client and the TM client. Compare the entries you plan to use in your transit warehousingprocesses. 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 Customizingbetween SAP TM, SAP ERP, and SAP EWM

Some customizing entries must be defined in different tables in SAP ERP, SAP Transportation Management (SAPTM) and SAP Extended Warehouse Management (SAP EWM). For example, packaging material types of handlingunits 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:

SettingCustomizing Path in SAPERP

Customizing Path in SAPTM

Customizing Path in SAPEWM

Incoterms Sales and DistributionMaster Data BusinessPartners CustomersBilling DocumentDefine Incoterms

SCM Basis MasterData Define Incoterms

Cross-Process Settings Delivery Warehouse

Request GeneralSettings DefineIncoterms

Means of Transport Not applicable Master Data Resources Define Means of

Transport

SCM Basis MasterData TransportationLane Maintain Meansof Transport



Packaging Material Type(for transportation units)

Logistics-GeneralHandling UnitManagement BasicsDefine Packaging MaterialTypes

SCM Basics PackHandling Units Basics

Define PackagingMaterial Types

Cross Process SettingsHandling Units Basics


Packaging Material Type(for handling units in SAPEWM) or Package TypeCode (SAP TM)

Logistics-GeneralHandling UnitManagement BasicsDefine Packaging MaterialTypes

Forwarding OrderManagement DefinePackage Type Codes

Cross Process SettingsHandling Units Basics


Shipping Conditions (SAPERP and SAP EWM) orTransportation ServiceLevel Code (SAP TM)

Logistics ExecutionShipping BasicShipping FunctionsShipping Point and GoodsReceiving PointDetermination DefineShipping Conditions

Forwarding OrderManagement DefineTransportation ServiceLevel Codes

Cross-Process Settings Delivery Warehouse

Request GeneralSettings DefineShipping Conditions

For more information about synchronization of table entries between SAP ERP and SAP EWM, see VerifyingSynchronization of ERP and EWM Customizing in Integration of SAP ERP with SAP EWM [External].

ProcedureIf you implement your own transit warehouse, check if you use any of the settings listed in the table above in yourwarehousing processes. Compare the entries between your EWM and your ERP customizing client and, ifnecessary, adapt the entries in the TM, EWM or ERP client.

TipYou can either compare the settings manually or use the Customizing Scout, which is a tooldelivered with the SAP Solution Manager (transaction SMSY).

7.3 Appendix C: Condition Records for Bin DeterminationThis appendix contains the list of condition records created in Creating Warehouse Structure and ConditionRecords 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 ExtendedWarehouse Management -> Settings -> Transit Warehousing -> Maintain Condition Records for Bin Determination(Validity: Today’s Date to 31.12.9999). Alternatively, use transaction /SCWM/PUT_TW_WT_GCM.

NoteThe condition records listed below refer to warehouse number W100. In your system, the conditionrecords 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.BinW100 X H970 CL-ZONE

Condition records for condition type 0TWP and condition table SAPTWP20 (loading preparation):

Whn NxtTWCtry Activity Stor.Type SectionW100 US MLCH H923 C01I

W100 DE MLCH H923 C02I

W100 - MLCH H923 C99I



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.BinW100 - STAG X ADR 3 H910 - -

W100 1 - X ADR 3 H040 DG1 -

W100 2 - 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 H910 - -

W100 1 - X H040 DG9 -

W100 2 - 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.BinW100 1 X H050 - -

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.BinW100 - JP 12 - H920 R01 -

W100 1 JP 13 PC_JPTY_10_25 H920 POC POSTCODE-001



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 SectionW100 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.BinW100 1 DE - - H921 C02 -



W100 2 DE - - H980 - C-OVERFLOW

W100 - DE STAG - H910 - -

W100 1 DE - X H921 C02L -

W100 2 DE - X H980 - C-OVERFLOW

W100 - DE STAG X H910 - -

W100 1 US - - H921 C01 -

W100 2 US - - H980 - C-OVERFLOW

W100 - US STAG - H910 - -

W100 1 US - X H921 C01L -

W100 2 US - X H980 - C-OVERFLOW

W100 - US STAG X H910 - -

Condition records for condition type 0TWP and condition table SAPTWP90 (any other countries):

Whn Sequence Activity Overdimen. Stor.Type Section Stor.BinW100 1 - - H921 C99 -

W100 2 - - H980 - C_OVERFLOW

W100 - STAG - H910 - -

W100 1 - X H921 C99L -

W100 2 - X H980 - C_OVERFLOW

W100 - STAG X H910 - -

Condition records for condition type 0TWC and condition table SAPTWC01 (unloading):

Whn Not Autom. Stor.Type Storage BinW100 - 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 BinW100 H923 C99 COUNTRY-99

Explanation of Bin Determination Using Condition Records



The condition records listed above are an example adapted to the warehouse layout created in CreatingWarehouse Structure and Condition Records for Bin Determination, and are used to determine an appropriatedestination bin during warehouse task creation.The bin determination uses one or more condition records created in multiple condition tables containing fieldsfrom a global field catalog.Using multiple smaller condition tables in a strict order allows a reduction of the number of condition recordsnecessary to map all required movements in the example layout. However, one trade-off when using multipletables is the increased complexity when creating condition records and retracing which condition records matchin a specific use case.The following figure shows the order in which SAP EWM accesses the condition tables when searching for asuitable bin for transit HUs (left-hand side) and for HU containers (right-hand side). Each row represents a uniquecondition 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 theonly 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 forthe staging area and one box for the overflow area. This means that the condition records of this condition tablecontain 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 bythe access sequence. The determination according to the access sequence stops immediately if a matchingcondition record is found in one of the tables, so that no other table will be accessed. This does not mean that onlya single condition record is returned for further processing: multiple condition records can be found in onecondition 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, differentdetermination procedures are assigned to the warehouse number.

NoteThe determination procedures used for transit HUs and HU containers are assigned to thewarehouse number in the Customizing activity Define Warehouse Number Control, in Customizingfor Extended Warehouse Management under Master Data Define Warehouse Number Control.



NoteFor information about the customizing for this example, see Customizing for Extended WarehouseManagement under Goods Receipt Process Strategies Storage Bin

Search Sequence for Transit HUs

SearchSequence

Table Description

1 SAPTWP10 ClarificationThe only relevant attribute is the To Be Clarified indicator. If the To Be Clarifiedstatus is set for a transit HU, the system determines a storage bin in theclarification zone (storage type H970) based on the single condition record of thistable.

2 SAPTWP20 Loading PreparationThe areas for loading transit HUs onto HU containers should only be found in theloading preparation process. Warehouse tasks for loading preparation use aspecial warehouse process type. It is assigned to the warehouse number anduses activity MLCH. All condition records in this table will match for this activityonly.The destination data of the condition records contains different inbound sectionsof a work center (within storage type H923) that is used for loading cargo ontoHU containers. Different inbound sections are found by the consolidation group.An additional criteria in this condition table is the country of the next unloadinglocation, which also leads to the determination of different storage sections. Forexample USA (US) matches to the condition record with storage section C01 andGermany (DE) matches to a condition record with storage section C02.Note: This table is positioned very early in the access sequence in order to reducethe number of condition records that have to be created for any transit HU in thedestination bin determination for loading preparation. By using a specialwarehouse process type with activity MLCH in this table, the loading preparationfor all transit HUs finds condition records in this table as long as this activity isused. For example, there is no need to create additional condition records in tableSAPTWP50 for loading preparation of high-value goods. Nor do you need tocreate additional condition records in table SAPTWP80 for loading preparation oftransit HUs which are shipped to a different next unloading location country, likethe US.

3 SAPTWP30 Specific Dangerous Goods ClassWith the example condition records, transit HUs containing dangerous goods ofregulation code ADR and class 3 will be stored in a dedicated area. As there arecapacity limitations, an overflow storage bin is also returned. Therefore thedetermination finds two matching condition records with different sequencenumbers. The sequence number also gives the order in which the storage bin isused in searches in further processing. The destination data for class 3 andregulation code ADR of the first condition record is storage section DG1 ofstorage type H040.The system finds a different condition for warehouse tasks created with activitySTAG, 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 theActivity field is empty, as the field is defined as optional (“field in free key part”) incustomizing for the access sequence.

4 SAPTWP40 Any Dangerous Goods ClassIn the previous table, records exist for transit HUs containing dangerous goods ofregulation code ADR and class 3 only. For any other dangerous goods data notmaintained in table SAPTWP30, the system uses table SAPTWP40 for bindetermination. In the example condition records, the system finds storagesection DG9 in storage type H040 for any dangerous goods not classified asregulation code ADR and class 3.In this table, two other condition records might match: one with a different



sequence number for the overflow bin, and one with activity STAG for the stagingactivity.Note: In general, we recommend creating an additional condition record for anoverflow storage bin if the storage types used in the determination have capacitylimitations, to avoid interruptions in the process if all bins are occupied at a pointin time.

5 SAPTWP50 High-Value GoodsThe table contains two condition records with different sequence numbers. Thesystem 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 anoverflow storage bin also exists.As there is no staging of high value cargo in the example warehouse layout, thereis no additional condition record with activity STAG.Note: Since the dangerous goods tables are placed before the table for high-valuecargo, the dangerous goods information implicitly has a higher priority than thehigh-value indicator. This means that a transit HU containing dangerous goodsand high-value cargo will be stored in the area for dangerous goods.

6 SAPTWP60 Same Country with Specific Region/PostcodeThe condition records of this table are used to store cargo that is to be deliveredin 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 storedin 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 sectionPOC of the same storage type. Using the postal code of the consignee, thesystem finds a suitable condition record by evaluating the logical condition, whichleads to different storage bins for each postal code range.

7 SAPTWP70 Same Country for Any Region/PostcodeThis table contains condition records for cargo for any region of the transitwarehouse’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.

8 SAPTWP80 Other Specific CountriesThis table is used to store cargo where the country of the final transit warehouseis different to the country of the current transit warehouse. Cargo for specificcountries is stored in different storage sections of storage type H921. In thisexample, 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 sectionsper 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 isreturned for the overflow storage bin in storage type H980.This is valid for all activities except when using STAG. In this case, the systemfinds a different condition record. It points to storage type H910, to allow astaging 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 aswell as for overdimensional cargo, two condition records exist with activity STAG,but only one is found at any one time.

9 SAPTWP90 Any Other CountriesThis table is used for storing cargo where the country of the final transitwarehouse is different to the country of the current transit warehouse, but wherethe system cannot find a condition record in the previous tables.Cargo to be delivered to countries that are not specified in the previous table isstored in a separate storage section C99 of storage type H921. The system findsa different condition record for overdimensional cargo, pointing to section C99Lof the same storage type.Different condition records are used for staging here too.



Search Sequence for HU Containers

SearchSequence

Table Description

1 SAPTWC01 UnpackThe condition record in this table is used to move HU containers to be unloadedto the unloading storage bin CHU-UNLOAD of storage type H922. It is valid for allHU containers with the indicator Unloaded Expected.

2 SAPTWC02 Specific CountriesCondition records of this table are considered for HU containers that are notexpected to be unloaded. Otherwise the condition record in the previous tablewould match. The condition records separate the storage of HU containers intodifferent storage sections depending on the country of the next transitwarehouse location. In the example, HU containers with Next Transit WarehouseLocation Country USA (US) match to condition record with section C01 andstorage bin COUNTRY-01 of storage type H923, and HU containers with NextTransit Warehouse Location Country Germany (DE) match to condition recordwith section C02 and storage bin COUNTRY-02 of storage type H923.Note: The condition table contains an optional field for the activity defined in thewarehouse process type. Therefore, it is possible to create condition records tobuild an additional process step, for example, staging of HU containers.

3 SAPTWC03 Any Other CountryHU containers with a Next Transit Warehouse Location Country that does notmatch any record of the previous table will match a condition record for storagesection C99 and storage bin COUNTRY-99 of storage type H923.Note: the condition table also contains an optional field for the activity defined inthe warehouse process type.



7.4 Appendix D: Determination of Packaging Materials inSAP EWM

In the example configuration described in this document, packaging materials exist in SAP EWM only, and aredetermined from vehicle types, transportation unit types, and package types in SAP TM when SAP TM sends aTransportationOrderLoadingAppointmentRequest message to SAP EWM. However, there are several options fordetermining a packaging material for vehicles, TUs, TU containers, HU containers, and HUs in SAP EWM, whichare described more in detail in this appendix.

NoteVehicles do not have a packaging material in SAP EWM, only a means of transport. A packagingmaterial is only required for planned vehicles in an outbound process for technical reasons.

Determination of packaging materials for vehicles and transportation unitsThe following figure gives an overview of the packaging material determination for vehicles and TUs in SAP EWM:

Case 1:If a packaging material is assigned to the resource master used in the freight document of SAP TM, SAPTM sends this packaging material to SAP EWM in the corresponding item of theTransportationOrderLoadingAppointmentRequest message. A packaging material with the same namemust exist in SAP EWM. In this case, SAP EWM uses the packaging material with the same name tocreate the vehicle or TU.

Case 2:There is no packaging material in the vehicle resource master in SAP TM. In this case, the correspondingitem in the TransportationOrderLoadingAppointmentRequest message contains a vehicle type. This typeis 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 inSAP EWM, but in this case you can use the same names for vehicle groups and packaging material types.

Case 3:If the vehicle type cannot be mapped to a packaging material in SAP EWM because no packaging materialof the same name exists, the packaging material is determined from the means of transport. For moreinformation, see Defining the Link between Packaging Material and MTR in SAP EWM.



Determination of packaging materials for TU containers and HU containersThe following figure gives an overview of the packaging material determination for TU containers or HU containersin SAP EWM:

The transportation unit type (TU type) of the resource used in the freight document of SAP TM is mapped to apackaging material in SAP EWM with the exact same name as the TU type (for example, container type 20G0).There is no direct relationship between the TU group in SAP TM and the packaging material type in SAP EWM, butyou 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 HUsThe 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 packagingmaterial type in SAP EWM with the exact same name (for example, PAL for pallet). SAP EWM expects that onlyone packaging material (for example PALLET) exists for this packaging material type, and uses this packagingmaterial to create the transit HUs.

ImportantIt is crucial that there is a 1:1 relation between the packaging material type and the packagingmaterial itself in SAP EWM. If there are several packaging materials with the same packagingmaterial type, the packaging material is determined randomly.



7.5 Appendix E: Additional Configuration for LCL OceanFreight Scenario

Although this configuration guide describes the configuration necessary to run transit warehousing processesReceive from Shipper and Ship to Next Transit Warehouse with SAP EWM in the first transit warehouse of the LCLAir Freight scenario of SAP TM, it can also be used to configure a transit warehouse managed with SAP EWM inthe LCL Ocean Freight scenario of SAP TM.This appendix describes additional settings for managing container freight stations (CFS) as SAP EWM transitwarehouses.

1. In SAP EWM, create two additional transit warehouses JPYO (CFS Yokohama) and USLO (CFS LosAngeles) as described in Activating BC-Sets in SAP EWM.

2. In SAP TM, assign the new transit warehouses to locations OF-CFS-JPYO and OF-CFS-USLAX asdescribed in Assigning Warehouse Number to Location.

3. In SAP TM, transfer the locations OF-CFS-JPYO and OF-CFS-USLAX and the business partners OF-FWH-03 and OF-FWH-20 to SAP EWM as described in Transferring Locations and Business Partnersfrom SAP TM to SAP EWM.

4. In SAP EWM, maintain the attributes for supply chain unitsOF-CFS-JPYO and OF-CFS-USLAX asdescribed in Maintaining Supply Chain Units for Transit Warehouses

5. In SAP EWM, maintain the logical conditions for bin determination in the new warehouses as described inMaintaining Logical Conditions for Bin Determination. The logical conditions follow the same namingconvention: PC_<warehouse>_xxxxx.

6. In SAP EWM, create the warehouse structure and condition records for bin determination for the newwarehouses as described in Creating Warehouse Structure and Condition Records for Bin Determination.

7. In SAP EWM, create the determination record for printing HU waybill labels in warehouse JPYO asdescribed in Creating Determination Records for Printing HU Waybill Labels. The entry is identical to theentry for warehouse JPNR.

8. In SAP EWM, create the following packaging materials for containers as described in Creating PackagingMaterials:

Field/Value Product 1 Product 2 Product 3

Product 20G0 42G0 22R1

Product Description 20 ft Dry Cont,20x8

40 ft Dry Cont,40x8.6

20 ft Reefer Cont,20x8.6

Base Unit of Measure EA EA EA

Pkg Data/Pack.Mat.Type CN CN CN

Pkg Data/HU Type M1 M1 M1

Gross Weight 2570 4030 2570

Unit of Weight KG KG KG

Closed Packaging X X X

9. In SAP EWM, define the following link between packaging material and MTR as described in Defining theLink between Packaging Material and MTR in SAP EWM:

MTr Pack.Material Optional Seq.PMs No. PMs in MTr Cont. PM

CN 20G0 X - - -

CN 22R1 X - - -

CN 42G0 X - - -

10. In SAP EWM, define the resource groups for the new warehouses as described in Defining Resource Group.11. In SAP EWM, define the queue sequence for resource groups for the new warehouses as described in

Defining Queue Sequence for Resource Group.12. In SAP EWM, define resources for the new warehouses as described in Defining Resource.



7.6 Appendix F: Hints for Dangerous Goods HandlingDangerous goods are not part of the transit warehousing scenario, but can be used in general in transitwarehousing processes. If a package item of a forwarding order contains dangerous goods, you enter dangerousgoods information for this item in SAP TM. The dangerous goods information is communicated to SAP EWM in theTransportationOrderLoadingAppointmentRequest message, so that SAP EWM can determine a suitable bin in thedangerous goods area for the transit HUs of this package item.

NoteThe appendix does not contain a step-by-step instruction on how to set up dangerous goods in yoursystem. Instead it is intended to provide some hints about the required settings and master data.The exact settings and master data must be defined in an implementation project.

Prerequisites...

You have set up an example dangerous goods customizing in SAP TMYou have set up an example dangerous goods customizing in SAP EWM. For this purpose, download the BCset from note 2162516 and activate it.Since there will be transfer of freight orders between SAP TM and SAP EWM, you must have examplecustomizing for dangerous goods data available in both system. This customizing and must be kept insync.During implementation, you have maintained the required customizing and dangerous goods master data,which serve as templates.

NoteSAP delivers licensed dangerous goods master data and customizing which can be purchased bythe customer.

You have checked if you require an implementation of BAdI /SCWM/EX_DLV_DG_AGGR. The BAdI can befound in Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for ExtendedWarehouse Management Cross-Process Settings Delivery- Warehouse Request BAdI: Aggregationand Prioritization of Dangerous Goods Data


www.sdn.sap.com/irj/sdn/howtoguides

© 2015 SAP AG or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted inany form or for any purpose without the express permission of SAPAG. The information contained herein may be changed withoutprior notice.Some software products marketed by SAP AG and its distributorscontain proprietary software components of other softwarevendors. National product specifications may vary.These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not beliable for errors or omissions with respect to the materials. Theonly warranties for SAP Group products and services are thosethat are set forth in the express warranty statementsaccompanying suchproducts and services, if any. Nothing herein should be construedas constituting an additional warranty.SAP and other SAP products and services mentioned herein as wellas their respective logos are trademarks or registered trademarksof SAP AG in Germany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

www.sap.com/contactsap

ewm930solman tw

Documents