EWM Transit Warehousing

CUSTOMER

Solution Manager Content SAP EWM 9.4 Document Version: 1.0 - 2016-04-21

Transit Warehousing

Document History Document Version

Description

1.0

April 22, 2016

Transit Warehousing Scenario: Transit Warehousing

CUSTOMER © 2016 SAP SE or an SAP affiliate company. All rights reserved.

2

Table of Contents 1

Scenario: Transit Warehousing ........................................................................................................... 5 1.1 1.2 1.3 1.4

2

Process: Receiving from Shipper ........................................................................................................ 7 2.1

3

Process ............................................................................................................................................ 7

Process: Shipping to Next Transit Warehouse .................................................................................. 10 3.1

4

Integration ....................................................................................................................................... 5 Prerequisites ................................................................................................................................... 5 Warehouse Structure and Master Data ........................................................................................ 5 Process ............................................................................................................................................ 6

Process .......................................................................................................................................... 10

Configuration: Transit Warehousing .................................................................................................. 13 4.1

4.2 4.3

4.4

4.5

4.6

4.7

4.8

Prerequisites ................................................................................................................................. 13 4.1.1 Installed Components .................................................................................................... 13 4.1.2 Prerequisites for System Connection in SAP ERP, SAP TM and SAP EWM ............. 13 4.1.3 Configuration Guide for LCL Air Freight Scenario in SAP TM .................................... 14 User Roles for SAP TM and SAP EWM ........................................................................................ 14 Overview of SAP ERP Master Data .............................................................................................. 14 4.3.1 Customer Master Data in SAP ERP .............................................................................. 14 4.3.2 Vendor Master Data for Carriers in SAP ERP .............................................................. 16 Configuration in SAP ERP ............................................................................................................ 19 4.4.1 Activating Business Transaction Events (BTE) in SAP ERP ....................................... 19 4.4.2 Configuring Logical Systems in SAP ERP .................................................................... 19 4.4.3 Assigning EWM Logical System to RFC Destination in SAP ERP ...............................20 4.4.4 Configuring qRFC Destination in SAP ERP ..................................................................20 Configuration in SAP EWM........................................................................................................... 21 4.5.1 Activating Business Functions in SAP EWM ................................................................ 21 4.5.2 Configuring Logical Systems in SAP EWM .................................................................. 21 4.5.3 Assigning Logical System to RFC Destination in SAP EWM ....................................... 21 4.5.4 Configuring Business Systems ..................................................................................... 22 4.5.5 Configuring Business System Group ........................................................................... 22 4.5.6 Configuring qRFC Destination in SAP EWM................................................................. 23 4.5.7 Activating the Planning Version and Model for Master Data ...................................... 24 4.5.8 Activating BC Sets in SAP EWM.................................................................................... 24 4.5.9 Define Status Profile for Delivery – Warehouse Request ........................................... 26 4.5.10 Configuring Action Profiles for TU and Vehicle ........................................................... 26 4.5.11 Configuring Action Conditions for Transportation Unit.............................................. 27 4.5.12 Checking Action Profiles for HU .................................................................................... 28 4.5.13 Activating Error and Conflict Handler in SAP EWM .................................................... 28 4.5.14 Defining Work Center Layout to Display Planned HUs ............................................... 28 Settings and Master Data in SAP ERP ........................................................................................30 4.6.1 Preparing Initial Transfer of Master Data from SAP ERP ...........................................30 4.6.2 Transferring Master Data from SAP ERP using CIF ....................................................30 4.6.3 Scheduling Background Job for Master Data Transfer .............................................. 31 Configuration in SAP TM .............................................................................................................. 33 4.7.1 Assigning Warehouse Number to Location ................................................................. 33 4.7.2 Transferring Locations and Business Partners from SAP TM to SAP EWM ............. 33 Settings and Master Data in SAP EWM....................................................................................... 35 4.8.1 Checking Business Partners of Transportation Network ........................................... 35 4.8.2 Checking Locations of Transportation Network ......................................................... 35 4.8.3 Maintaining Supply Chain Units for Transit Warehouses ........................................... 36 4.8.4 Maintaining Logical Conditions for Bin Determination ............................................... 37



3

4.8.5 Checking Assignment of Supply Chain Unit to Warehouse Number......................... 38 4.8.6 Creating Warehouse Structure and Condition Records for Bin Determination ....... 38 4.8.7 Sort Storage Bins (Mandatory)..................................................................................... 47 4.8.8 Creating Determination Records for Printing HU Waybill Labels .............................. 48 4.8.9 Creating Packaging Materials ....................................................................................... 48 4.8.10 Defining the Link between Packaging Material and MTR in SAP EWM .....................50 4.8.11 Defining Resource Group ..............................................................................................50 4.8.12 Defining Queue Sequence for Resource Group ...........................................................50 4.8.13 Defining Presentation Device ........................................................................................ 51 4.8.14 Defining Resources ........................................................................................................ 51 4.9 Configuration for SAP NetWeaver Process Integration ............................................................ 53 4.9.1 Checking Connection to SLD in SAP TM and SAP EWM ............................................ 53 4.9.2 Creating a Configuration Scenario for Loading Appointment Integration ................ 53 4.10 Configuration of Navigation between SAP EWM and SAP TM ................................................. 55 4.10.1 Creating Connection for Navigation in SAP EWM ....................................................... 55 4.10.2 Configuring User for Navigation in SAP EWM ............................................................. 55 4.10.3 Creating Connection for Navigation in SAP TM .......................................................... 56 4.10.4 Configuring User for Navigation in SAP TM ................................................................. 56 5

Test Case: Receiving from Shipper ................................................................................................... 58 5.1 5.2 5.3

6

Test Case: Shipping to Next Transit Warehouse ................................................................................61 6.1 6.2 6.3

7

Prerequisites ................................................................................................................................. 58 Features ......................................................................................................................................... 58 Activities ........................................................................................................................................ 58 Prerequisites ................................................................................................................................. 61 Features ......................................................................................................................................... 61 Activities ........................................................................................................................................ 61

Appendix ........................................................................................................................................... 64 7.1 7.2 7.3 7.4 7.5 7.6

Appendix A: Checking Basic Table Entries Used in SAP TM, SAP ERP, and SAP EWM ......... 64 Appendix B: Verifying Synchronization of Customizing between SAP TM, SAP ERP, and SAP EWM ....................................................................................................................................... 64 Appendix C: Condition Records for Bin Determination ............................................................. 65 Appendix D: Determination of Packaging Materials in SAP EWM ............................................ 75 Appendix E: Additional Configuration for LCL Ocean Freight Scenario................................... 77 Appendix F: Hints for Dangerous Goods Handling .................................................................... 78



4

1

Scenario: Transit Warehousing

You can use this business scenario to integrate warehouse execution with freight forwarding operations using SAP Extended Warehouse Management (SAP EWM) and SAP Transportation Management (SAP TM). In Transit Warehousing, you receive cargo from shippers based on inbound planning from SAP TM. You consolidate cargo with the same destination in your transit warehouse before you ship it to the next location of the transportation chain or deliver it to the final consignee, based on outbound planning from SAP TM. As cargo received from numerous shippers in a transit warehouse is very variable, you do not manage product master data for it. Instead, you manage cargo as handling units (HUs) and keep cargo information directly in the documents used in the warehouse. The transit warehouse is structured in such a way that you put away HUs with the same destination country or region on the same storage bin, where they are available for the shipment to the next location or to the consignee. HUs with special attributes, such as dangerous goods or high-value cargo, are put away separately. With the next outbound plan sent by SAP TM, you either load the HUs directly from the staging area used for putaway, or you stage the HUs before loading them onto a vehicle. During these processes, SAP EWM informs SAP TM about the major steps performed in the transit warehouse, such as arrival at checkpoint, departure from checkpoint, and receiving or loading completion.

1.1

Integration

The business scenario Transit Warehousing is integrated in theLess than Container Load (LCL) Air Freight scenario in SAP TM. It describes the receiving of cargo from a shipper in the transit warehouse in Tokyo, and the shipping of cargo from the transit warehouse in Tokyo to the gateway in Narita. The consignee of the cargo is located in the USA. The transit warehouse in Tokyo is managed with SAP EWM. For more information about the LCL Air Freight scenario, see http://service.sap.com/instguides  SAP Business Suite Applications  SAP TM  Solution Manager Content Documentation  Using SAP TM 9.4  Scenario Configuration Guides  Air Freight.

1.2

Prerequisites

You can implement this business scenario with different releases of the relevant application components. However, only certain combinations are valid. For more information, see the Master Guide for SAP Extended Warehouse Management on SAP Service Marketplace at http://service.sap.com/instguides. For more information about the configuration prerequisites, see Configuration: Transit Warehousing.

1.3

Warehouse Structure and Master Data

As transit warehousing processes strongly depend on the warehouse structure, all processes are integrated in a standard warehouse with a predefined structure and use common master data, such as business partners, locations, and resources. The warehouse structure consists in the following areas: 

Doors and staging areas for inbound and outbound



Area with country-specific storage bins



Area with region-specific storage bins



Area with storage bins for postal codes



Areas for cargo with special attributes, such as dangerous goods or high-value cargo



Area for the handling of HU containers



Clarification zone

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

Note You can find a detailed description of the warehouse structure in Creating Warehouse Structure and Condition Records for Bin Determination.



5

1.4

Process

The business scenario contains the following processes: ...

1.

Receiving from Shipper

2.

Shipping to Next Transit Warehouse

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



6

2

Process: Receiving from Shipper

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

2.1

Process

This business process runs as follows: ...

1.

Create forwarding order (SAP TM) A customer service agent creates a forwarding order for the transportation of cargo from a shipper to a consignee. The cargo is to be picked up from the shipper and transported to the consignee via transit warehouses belonging to the transportation network of the freight forwarder and managed with SAP EWM. SAP TM creates freight units based on the forwarding order.

2.

Create freight order for pick-up (SAP TM) The transportation planner carries out the transportation planning for the freight units. This creates a freight order for transporting cargo from the shipper’s location to the first transit warehouse. The transportation planner communicates with a carrier. He or she assigns the carrier to the freight order in SAP TM, and communicates the freight order number to the carrier.

3.

Pick up packages from shipper (SAP TM) The carrier picks up the cargo from the shipper’s location and informs a capacity manager, who sets the status of the current stage of the freight order to ‘Departed’ in SAP TM. When the transportation planning is complete, the transportation planner sends an unloading request message containing freight order information to SAP EWM. (This step can be done automatically.) SAP EWM automatically creates a vehicle, a transportation unit (TU), an inbound delivery, and HUs. The HUs are assigned to the TU.

4.

Truck arrives at checkpoint (SAP EWM) When the truck arrives, the truck driver gives the receiving office clerk the freight order reference. The receiving office clerk selects the freight order in SAP EWM. He or she assigns a free door to the TU, sets the status ‘Docked at Door’, and tells the truck driver to drive to the assigned door. SAP EWM automatically prints HU labels to prepare for the receiving of HUs. In addition, SAP EWM sends an unloading notification message for arrival at checkpoint to SAP TM. SAP TM sets status of the current stage of the freight order to ‘Arrived’. In this step, you can also print an unloading list in SAP TM (optional).

5.

Unload truck and receive packages (SAP EWM) A warehouse worker unloads the packages from the truck to the inbound staging area behind the door. A warehouse worker then receives the HUs using an RF device. He or she identifies the packages, attaches an HU label to each package, and scans the label. He or she enters the weight and dimensions of the packages. The system automatically posts goods receipt in SAP EWM for each received HU. With the last HU, the warehouse worker confirms the receiving completion in SAP EWM, which triggers the sending of an unloading notification message containing the received HUs to SAP TM. SAP TM updates the freight order and freight units.

6.

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

7.

Putaway HUs (SAP EWM)

Transit Warehousing Process: Receiving from Shipper


7

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



8



9

3

Process: Shipping to Next Transit Warehouse

You use this business process to ship cargo from your transit warehouse to the next location in the transportation chain. After the creation of a pre-carriage freight order, SAP Transportation Management (SAP TM) sends the outbound planning information to SAP Extended Warehouse Management (SAP EWM). When the truck arrives, you identify the freight order in SAP EWM and post the arrival at checkpoint. The truck arrives at a door. You load the requested handling units (HUs) directly from their storage bin, or you stage the HUs to a staging area first before loading them onto the truck. The truck departs from the door and you post the departure from the checkpoint. In this process, SAP EWM informs SAP TM about arrival at checkpoint, loading completion, and departure from checkpoint. The notification of the loading completion includes information about the loaded HUs. In this process, you print the waybills in SAP TM before handing them over to the truck driver.

3.1

Process

This business process runs as follows: ...

1.

Create freight order (SAP TM) The transportation planner carries out the transportation planning for the freight units. This creates a freight order for transporting the cargo to the next location. He or she assigns the carrier to the freight order in SAP TM, and communicates the freight order number to the carrier.

2.

Send loading request to transit warehouse (SAP TM) When the transportation planning is complete, the transportation planner sends a loading request message to SAP EWM. (This step can be done automatically.) SAP EWM automatically creates a vehicle, a transportation unit (TU), an outbound delivery order, and planned HUs. The planned HUs are assigned to the TU.

3.

Truck arrives at checkpoint (SAP EWM) When the truck arrives, the truck driver gives the shipping office clerk the freight order reference. The clerk selects the freight order in SAP EWM. He or she assigns a free door to the TU, sets the status ‘Docked at Door’, and tells the truck driver to drive to the assigned door. SAP EWM sends a loading notification message for arrival at checkpoint to SAP TM. SAP TM sets status of the current stage of the freight order to ‘Arrived’. With the arrival at checkpoint, SAP EWM creates staging warehouse tasks (WTs) for HUs that must be staged (optional). The system gathers the WTs into warehouse orders (WOs) to optimize the picking. The system assigns the WOs to one or more queues according to specific criteria, such as the activity area and the type of resource necessary to access the storage bins.

4.

Stage handling units (optional) (SAP EWM) A warehouse worker picks and stages the HUs to the outbound staging area using an RF device. For this purpose, he or she chooses the equipment necessary for the picking, for example, a forklift truck and an RF device. He or she logs on to the system as a resource. He or she receives the first WO of the queue he or she is assigned to on the RF device, drives to the source bin of the first WT displayed on the RF device, picks the first HU from the source bin, and scans its label. He or she drops the HU at the staging area and scans the staging bin to confirm this step in the system. He or she proceeds in the same way with all requested HUs.

5.

Load truck (SAP EWM) A warehouse worker begins to load the truck from the staging area. This step is carried out using an RF device. The warehouse worker chooses the equipment necessary for the loading, for example, a forklift truck and an RF device, and logs on as a resource. He or she scans the door bin to start the loading of the TU in the system. He or she then picks an HU from the staging area and scans its label. He or she loads the HU onto the truck and proceeds with the next HU until the staging area is empty. He or she checks for HUs from other areas that have not yet been loaded, for example, high-value or overdimensional cargo, and picks and loads these as well. With the last HU, the warehouse worker confirms the loading completion in SAP EWM. This triggers the sending of a loading notification message containing the loaded HUs to SAP TM. SAP TM updates the freight order and freight units. In this step, you can also print a road waybill in SAP TM (optional).

6.

Truck leaves (SAP EWM)

Transit Warehousing Process: Shipping to Next Transit Warehouse


10

The truck leaves the door and the premises. The shipping office clerk confirms the departure from the checkpoint, and therefore from the door. SAP EWM posts the goods issue and sends a loading notification message for departure from checkpoint to SAP TM. SAP TM updates the execution status of the freight order.



11



12

4

Configuration: Transit Warehousing

This section describes the configuration necessary to run transit warehousing processes Receiving from Shipper and Shipping to Next Transit Warehouse with SAP Extended Warehouse Management (SAP EWM) in the first transit warehouse of the LCL Air Freight scenario of SAP Transportation Management (SAP TM). For more information about the LCL Air Freight scenario, see http://service.sap.com/instguides  SAP Business Suite Applications  SAP TM  Solution Manager Content Documentation  Using SAP TM 9.4  Scenario Configuration Guides  Air Freight.

Note This section also contains configuration for additional transit warehouses in the LCL Air Freight scenario from SAP TM. In order to run both processes, you need to set up the configuration for the first transit warehouse only (warehouse 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 ERP installed on separate servers.

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

Note If you have created preconfigured transit warehouses in SAP EWM 9.3 and you are upgrading to SAP EWM 9.4, no changes are required, unless you want to use air cargo security functionality. In this case, SAP recommends creating new preconfigured transit warehouses after the upgrade as they will automatically have a warehouse layout and a bin determination configuration adapted to air cargo security requirements.

4.1

Prerequisites

4.1.1

Installed Components

You have installed and correctly configured the following applications: 

SAP EWM 9.4



SAP TM 9.4



EHP 7 for SAP ERP 6.0 or higher

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

4.1.2

Prerequisites for System Connection in SAP ERP, SAP TM and SAP EWM

System administrators have to make specific settings for the integration of SAP ERP and SAP TM with SAP EWM before any customizing activity is carried out. Contact your system administrator to ensure the following prerequisites are met: 

An RFC user exists in each target system or client defined as an RFC destination in the examples below. For example, for the EWM test client to use the RFC destination for the ERP test client, an RFC user must exist in the ERP test client.



RFC destinations exist for the corresponding ERP, EWM and TM clients.

Transit Warehousing Configuration: Transit Warehousing


13

Procedure Create the following RFC destinations in Customizing for SAP NetWeaver under Application Server  IDoc Interface/Application Link Enabling (ALE)  Communication  Create RFC Connections: 

In SAP ERP for SAP EWM, for example EWMCLNT001 (naming convention CLNT)



In SAP TM for SAP EWM, for example EWMCLNT001



In SAP EWM for SAP TM, for example TM1CLNT001

4.1.3

Configuration Guide for LCL Air Freight Scenario in SAP TM

The Configuration Guide for LCL Air Freight scenario in SAP TM is already implemented, and the processes described in the LCL Air Freight scenario are already running with transit locations not managed by SAP EWM. For more information about configuring the LCL Air Freight scenario, see http://service.sap.com/instguides  SAP Business Suite Applications  SAP TM  Solution Manager Content Documentation  Using SAP TM 9.4  Scenario Configuration Guides  Air Freight.

4.2

User Roles for SAP TM and SAP EWM

The Transit Warehousing scenario contains process steps in SAP Transportation Management (SAP TM) and SAP Extended Warehouse Management (SAP EWM). You must assign the users in each system to specific user roles. If the process steps are performed by different users, you can use separate roles and users in each system, for example, a customer service agent, a transportation planner, and a capacity manager working exclusively in SAP TM, and a warehouse clerk working exclusively in SAP EWM. Standard roles available for this scenario: Role Name

Application

Description

/SCWM/EXPERT

SAP EWM

Role for EWM Transactions

/SCMTMS/TRANSPORTATION_MGR_V2

SAP TM

Role for TM Transactions

4.3

Overview of SAP ERP Master Data

The following master data is used in SAP ERP throughout the LCL Air Freight scenario. For information about how to create this data, see the configuration guide for the LCL Air Freight scenario in SAP TM. Customers and vendors created in SAP ERP are transferred via CIF to SAP TM, where they exist as locations and business partners. In this configuration guide you set up the transfer of this data via CIF to SAP EWM.

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

4.3.1

Customer Master Data in SAP ERP

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

Field/Value

Shipper 1

Shipper 2

Shipper 3

Shipper 4

Consigne e1

Consigne e2

Consigne e3

Consigne e4

Customer ID

OAF-CU01

OAF-CU02

OAF-CU03

OAF-CU04

OAF-CO01

OAF-CO02

OAF-CO03

OAF-CO04



14

Account Group

KUNA: General Customer s








Company Code

5000

5000

5000

5000

3000

3000

3000

3000

Sales 5000 Organization

5000

5000

5000

3000

3000

3000

3000

Distribution Channel

10

10

10

10

10

10

10

10

Division

00

00

00

00

00

00

00

00

Name

Kanxinso n Clothing Co. LTD.

Wabei Electronic s Factory

Japan Cable LTD

Samurai Fireworks LTD

Dosena Clothing Co. Factory

Ten Media Inc.

Soutwire Co.

Scottsdal e Fireworks Inc.

Street

Kioi-cho

Denenchof u

Kawabe

Shirokan e

State Route

Stallard Pl

West Main Street

Alma School Road

House Number

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

Chiyodaku

Ota-ku

Gifu

Minatoku

Sedona

Tucson

Brawley

Scottsdal e

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

Shipping Conditions

01

01

01

01

01

01

01

01

Order Combinatio n

Select

Select

Select

Select

Select

Select

Select

Select

Incoterm

-

-

-

-

-

-

-

-

Incoterm Locations

-

-

-

-

-

-

-

-



15

Terms of Payment (Sales area data)

-

-

-

-

-

-

-

-

Tax Classificatio n

0

0

0

0

0

0

0

0

Reconciliatio 145200 n Account

145200

145200

145200

144003

144003

144003

144003

Terms of Payment

0001

0001

0001

0001

0001

0001

0001

4.3.2

0001

Vendor Master Data for Carriers in SAP ERP

With the configuration of the LCL Air Freight scenario in SAP TM, you have created the following customer master data for shippers and consignees in SAP ERP, Check the entries on the SAP Easy Access screen for SAP ERP under Logistics  Materials Management  Purchasing  Master Data  Vendor  Central  Create: Key Data: Field/Value

Carrier 1

Carrier 2

Carrier 3

Carrier 4

Carrier 5

Carrier 6

Carrier 7

Carrier 8

Vendor ID

OAFCR-03

OAFCR-04

OAFCR-05

OAFCR-06

AF-JLNRT

AF-QFNRT

AF-JLLAX

AF-QFLAX

Company Code 5000

5000

3000

3000

5000

5000

3000

3000

Purchasing 5000 Organization

5000

3000

3000

5000

5000

3000

3000

Account Group

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 Long Beach, United States, Region CA

OAF-CR-06

Desert Express Lines

Truck Carrier US

First 355, 850258848 Phoenix, United States, Region AZ



16

AF-JL-NRT

Rising Sun Airlines Ltd.

Air Carrier JP

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

AF-QF-NRT

Oceanic Airways (Japan) KK Ltd.

Air Carrier JP

Toranomon 37th Mori Bldg 9F, 3-51, 1058483, Japan, Region 13 (Tokyo)

AF-JL-LAX

Rising Sun Air Carrier US Airlines (US) Ltd.

6041 W. Imperial Hwy # D, 90245 Los Angeles, California, United States

AF-QF-LAX

Oceanic Airways (US) KK Ltd.

555 North Nash Street, 90245 Los Angeles, California, United States

Air Carrier US

Accounting Information: Vendor ID

Reconciliation Account

Cash Management Group

OAF-CR-03

141100

A1

OAF-CR-04

141100

A1

OAF-CR-05

196300

A1

OAF-CR-06

196300

A1

AF-JL-NRT

141100

A1

AF-QF-NRT

141100

A1

AF-JL-LAX

196300

A1

AF-QF-LAX

196300

A1

Payment Transactions Accounting: Vendor ID

Payment Terms

OAF-CR-03

0002

OAF-CR-04

0002

OAF-CR-05

0002

OAF-CR-06

0002

AF-JL-NRT

0002

AF-QF-NRT

0002

AF-JL-LAX

0002

AF-QF-LAX

0002

Purchasing Data: Field/Val ue

Carrier 1

Carrier 2

Carrier 3

Carrier 4

Carrier 5

Carrier 6

Carrier 7

Carrier 8

Vendor ID

OAFCR-03

OAFCR-04

OAFCR-05

OAFCR-06

AF-JLNRT

AF-QFNRT

AF-JLLAX

AF-QFLAX

Order Currency

JPY

JPY

USD

USD

JPY

JPY

USD

USD



17

Terms of Payment

0002

0002

0002

0002

0002

0002

0002

0002

Incoterm s

-

-

-

-

-

-

-

-

Purchase Group

-

-

-

-

-

-

-

-

Planned Delivery Time

-

-

-

-

-

-

-

-

Conf. Control

-

-

-

-

-

-

-

-

Shipping Condition

-

-

-

-

-

-

-

-



18

4.4

Configuration in SAP ERP

In this section, you set up the communication between SAP ERP and SAP EWM for the transfer of master data, such as vendors and customers, via CIF to SAP EWM.

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

4.4.1

Activating Business Transaction Events (BTE) in SAP ERP

Prerequisites You 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 under Advanced Planning and Optimization  Basic Settings for the Data Transfer  Change Transfer  Change Transfer for Transaction Data  Activate Online Transfer Using BTE.

2.

Select the ND-APO (New Dimension Plug-In APO) and NDI (New Dimension Integration) checkboxes.

3.

Save your changes

4.4.2

Configuring Logical Systems in SAP ERP

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

Procedure ...

1.

Define a logical system for your ERP client (for example, ERPCLNT001) and a logical system for your EWM client (for example, EWMCLNT001) in Customizing for Integration with Other SAP Components under Extended Warehouse Management  Basic Settings for Setting Up the System Landscape  Name Logical System.

2.

Assign the ERP logical system defined in the first step to the ERP client (for example, in SAP ERP, assign ERPCLNT001 to client 001) in Customizing for Integration with Other SAP Components under Extended Warehouse Management  Basic Settings for Setting Up the System Landscape  Assign Logical System to a Client.

3.

In SAP ERP, specify the system type and release of the EWM logical system defined in the first step. In Customizing for Integration with Other SAP Components under Extended Warehouse Management  Basic Settings for Setting Up the System Landscape  Specify SAP APO Release, enter the values as shown in the following table for the EWM logical system: Field

Value

Log. System

, for example EWMCLNT001

Syst. Type

SAP_SCMB

Release

, for example 7.13 (or higher)



19

4.4.3

Assigning EWM Logical System to RFC Destination in SAP 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 ERP

This 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


Max. Conn.

10

Max. Runtime

60

W/o tRFC

Leave this field empty

d. Choose Continue 2.

Set the queue type for the communication of master data by means of CIF from SAP ERP to SAP EWM. a. In Customizing for Integration with Other SAP Components, choose Extended Warehouse Management  Basic Settings for Setting Up the System Landscape  Set Target System and Queue Type. b. Create an entry for the EWM logical system with the following data: Field

Value

Log. System


Q-Type

I (Inbound Queues)

Note The Operation Mode field is automatically filled by the system when you generate, activate, or deactivate CIF integration models.



20

4.5

Configuration in SAP EWM

4.5.1

Activating Business Functions in SAP EWM

You use this procedure to activate the business functions required for using transit warehousing processes in SAP Extended Warehouse Management (SAP EWM).

Procedure Carry out these steps in an SAP EWM client that allows cross-client settings and the creation of workbench requests. If necessary, use the workbench request to transport the settings to other SAP EWM systems. ...

1.

On the SAP Easy Access screen for SAP EWM, enter transaction SFW5.

2.

Check the following business functions and, if necessary, activate them

Business Function

Description

SCM_EWM_FND

EWM, Essential Foundation Functions

FND_SOA_REUSE_1

Improvements for SOA Reuse Functions

/BCV/MAIN

FND, Business Context Viewer Main Application

/BCV/MAIN_1

FND, Business Context Viewer Main Application 2

/BCV/NWBC_SIDEPANEL

FND, Business Context Viewer NWBC Side Panel (Reversible)

4.5.2

Configuring Logical Systems in SAP EWM

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

Procedure ...

1.

2.

Define a logical system for your ERP client (for example, ERPCLNT001), a logical system for your EWM client (for example, EWMCLNT001), and a logical system for your TM client in Customizing for Integration with Other SAP Components under Extended Warehouse Management  Basic Settings for Setting Up the System Landscape  Name Logical System: Logical System

Name

ERPCLNT001

ERPCLNT001

EWMCLNT001

EWMCLNT001

TM1CLNT001

TM1CLNT001

Assign the EWM logical system defined in the first step to the EWM client (for example, in SAP EWM, assign EWMCLNT001 to client 001) in Customizing for Integration with Other SAP Components under Extended Warehouse Management  Basic Settings for Setting Up the System Landscape  Assign Logical System to a Client.

4.5.3

Assigning Logical System to RFC Destination in SAP EWM

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.



21

3.


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.


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 Systems

You use this procedure to define the business systems for SAP TM, SAP ERP, and SAP EWM in SAP EWM, and to assign a business system to the client.

Note The settings cannot be transported from a Customizing client to other systems and clients. Therefore, you must repeat the steps in every EWM client connected to SAP ERP and SAP TM.

Procedure Carry out the following steps in each EWM client you want to connect to SAP ERP and SAP TM. ...

1.

In Customizing for Extended Warehouse Management under Interfaces  ERP Integration  General Settings  Define Business Systems, define a business system for the ERP client, the TM client, and the EWM client:

Business System

Logical System

Manual Maint.

ERP_001

ERPCLNT001

Flag is Not Set

EWM_001

EWMCLNT001

Flag is Not Set

TM1_001

TM1CLNT001

Flag is Not Set

Note If you use the System Landscape Directory (SLD), the entries already exist. In this case, no action is required in this step. 2.

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

4.5.5

Configuring Business System Group

You use this procedure to define the business system group for SAP ERP, SAP TM, and SAP EWM in SAP EWM, and assign the logical systems to the business system group. The business system group is used for the CIF transfer of master data from SAP ERP to SAP EWM. As SAP TM, SAP EWM, and SAP ERP share the same master data, you define the same business system group for all the systems.

Note The settings cannot be transported from a Customizing client to other systems and clients. Therefore you must repeat the steps in every EWM client connected to SAP ERP and SAP TM.

Procedure Carry out the following steps in each EWM client you want to connect to SAP ERP and SAP TM. ...

1.

Define a business system group for the ERP client in Customizing for SCM Basis under Integration  Basic Settings for Creating the System Landscape  Maintain Business System Group.



22

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 in Customizing for SCM Basis under Integration  Basic Settings for Creating the System Landscape 

Assign Logical System and Queue Type.

BusSystGrp

Logical system

SAP Ind.

Release

Queue Type

Err. Hndlg

Role

BG1

EWMCLNT001

X

70 (or

I Inbound Queue

Strict (Terminate at Errors)

Not Specified

I Inbound Queue


Not Specified

I Inbound Queue


Not Specified

higher)

BG1

TM1CLNT001

X

9.00 (or higher)

BG1

ERPCLNT001

X

700 (or higher)

Note The release for the EWM logical system relates to the installed component SCM_BASIS and not to the EWM component.

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

4.5.6

Configuring qRFC Destination in SAP EWM

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

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

, we recommend that you use either * 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 Continue 2.

Register display programs for the inbound queue in SAP EWM. This function enables you to display the data of a queue entry by double-clicking the queue name, or to display the application log of a queue entry by double-clicking the status text in the qRFC monitor for inbound queues. a. In SAP EWM, on the SAP Easy Access screen, call transaction SMQE.



23

b. Choose Edit  Register Display Program. c. Enter the queue and program names as shown in the following table:

4.5.7

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

Activating the Planning Version and Model for Master Data

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

Procedure Carry out the following step in each EWM client you want to connect to SAP ERP: In SAP EWM, on the SAP Easy Access screen, call transaction /SAPAPO/ACTVERCREATE. The system informs you whether the planning version and model already exist, or if the system just created them.

Important Transaction /SAPAPO/ACTVERCREATE requires an authorization for objects C_APO_MOD and C_APO_VERS with activity 01. You can use transaction SU53 to check failed authorization checks after report execution.

4.5.8

Activating BC Sets in SAP EWM

You use this procedure to activate Business Configuration (BC) sets in SAP EWM. The BC sets contain Customizing settings at client level or at warehouse level.

Important In order to run the processes Receiving from Shipper and Shipping to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, you need to activate the warehousedependent BC sets in warehouse JPTY only. In order to manage all transit warehouses of the scenario with SAP EWM, activate the warehousedependent BC sets in all the warehouses: JPTY, JPNR, JPNG, USLA, USSA, and USPH.

Procedure ...

1.

On the SAP Easy Access screen for SAP EWM, choose Tools  Customizing  Business Configuration Sets  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


/SCWM/TW_15_90

TW Number Range Int. for Basic Settings (Client) – Gen.




24

/SCWM/TW_20_10

TW Settings (Warehouse) – 10

Enter the currency used in your warehouse, for example, JPY Enter the factory calendar used in your warehouse, for example, JP Enter your warehouse number, for example, JPTY

/SCWM/DLV_BASIC_NUMBER RANGE

Delivery in EWM - Number Ranges

/SCWM/DLV_INBOUND_TW

Inbound Process for Transit Warehouse


Outbound Process for Transit Warehouse


ACS: Country Specific Security Status


Air Cargo Security Screening Methods and Exemptions


/SCWM/TW_20_15

TW Number Range Int. for Basic Settings (Warehouse) – Gen.

Enter your warehouse number, for example, JPTY

/SCWM/TW_20_20

TW Settings (Warehouse) – 20

Enter your warehouse number, for example, JPTY

/SCWM/TW_25_91

TW Number Range Int. for Basic Settings (Warehouse) – HU

Enter a number in the From number field, for example,

/SCWM/DLV_OUTBOUND_TW

/SCMB/ACS_NSS

/SCMB/ACS_SCRM_SCRE

BC set at client level. For more information, see the BC set documentation For more information, see the BC set documentation For more information, see the BC set documentation Since there will be transfer of freight orders between SAP TM and SAP EWM, you must have example customizing for country-specific security status available in both systems. This customizing must be kept in sync. Since there will be transfer of freight orders between SAP TM and SAP EWM, you must have example customizing for screening methods and exemptions available in both systems. This customizing must be kept in sync.

00000000000800000000 In the Number range object subobject value field, enter your warehouse number, for example, JPTY, Enter a number in the To number field, for example,

00000000000899999999 If you activate the BC set in several transit warehouses, enter disjunctive internal HU number ranges for each transit warehouse. Otherwise a warehouse cannot receive an HU with a number given by another warehouse.

/SCWM/SR_SCO_BCV (optional)


Configuration for Business Context Viewer - Shipping Cockpit

BC set at client level To use side panels in the transit warehousing screens, activate this BC set.


25

Measurement Services for TW in Sidepanel

/SCWM/TW_BCV (optional)

Enter your warehouse number, for example, JPTY To use side panels in the transit warehousing screens, activate this BC set.

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

4.5.9

Define Status Profile for Delivery – Warehouse Request

You use this procedure to adapt a status profile for delivery – warhouse request

Procedure ...

1.

In Customizing for SAP EWM, choose Cross-Process Settings  Delivery Processing  Status Management  Define Status Profiles.

2.

Select the status profile /SCWM/INB_PRD_CGO.

3.

In the dialogue structure, choose Status Types.

4.

Activate the following entries:

Status Type

Short Text

Inactive

DCC

Goods Issue HU

-

DTU

Assign Transportation Unit

-

DWA

Warehouse Act.

-

DWL

Receiving

-

5.

Save your entries

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

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

Procedure ...

1.

In Customizing for Extended Warehouse Management, choose Cross-Process Settings  Shipping and Receiving  Message Processing  Define Action Profiles for Vehicles.

2.

Select the action profile /SCWM/TU and choose Action Definition in the dialog structure.

3.

Choose Edit.

4.

Activate actions /SCWM/SR_SEND_TU_LDAP_NOTI, /SCWM/SR_TU_CREATE_STAGING_WT and /SCWM/SR_TU_PRINT_HU_LABEL.

5.

Deactivate the other PPF actions, unless you use them in other scenarios or processes, as shown in the following table:

Action Definition

Inactive

/SCWM/BIF_TAPP_CANCELLED_NOTI

X

/SCWM/BIF_TAPP_CHANGED_NOTI

X

/SCWM/BIF_TAPP_CREATED_NOTI

X



26

/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 the following table:

Action Definition

Inactive

/SCWM/BIF_VAPP_CANCELLED_NOTI

X

/SCWM/BIF_VAPP_CHANGED_NOTI

X

/SCWM/BIF_VAPP_CREATED_NOTI

X

/SCWM/SR_PRINT_VEH_WAYBILL

X

/SCWM/SR_SEND_SHIPPL_VEH

X

/SCWM/SR_SEND_VEH

X

/SCWM/SR_SEND_VEH_FINAL_LOAD

X

/SCWM/SR_SEND_VEH_LDAP_NOTI

-

PRINT_LOADLISTVEH

X

11.

Save your entries.

4.5.11

Configuring Action Conditions for Transportation Unit

You 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 and Receiving  Message Processing  Define Action Conditions for Transportation Units.

2.

Select the action profile /SCWM/TU and choose the action definition /SCWM/SR_TU_PRINT_HU_LABEL.

3.

Choose Edit.

4.

On the Processing Details tab page, enter the output device LP01.

5.

Save your changes.



27

4.5.12 Checking Action Profiles for HU You use this procedure to activate action definitions for handling units (HUs). They are used for sending messages to SAP Transportation Management.

Procedure ...

1.

In Customizing for Extended Warehouse Management, choose Cross-Process Settings  Handling Units  Basics  Print  Define PPF Action Profiles.

2.

Select the action profile /SCWM/HU_TW and choose Action Definition in the dialog structure.

3.

Choose Edit.

4.

Check that actions /SCWM/HU_TW_NOTIFY_TM_IN and /SCWM/HU_TW_NOTIFY_TM_OUT are active. If not, activate them.

4.5.13 Activating Error and Conflict Handler in SAP EWM You use this procedure to activate the error and conflict handling in service operations. This enables you to access detailed information about XI messages with errors in Monitor for Processed XML Messages (transaction SXI_MONITOR) and to process the messages after error resolution.

Procedure ...

1.

In Customizing for Extended Warehouse Management, choose Cross-Application Components 

5.

Save your entries.

Processes and Tools for Enterprise Applications  Enterprise Services  Error and Conflict Handler  Activate Error and Conflict Handler. 2. Check whether the Activated checkbox is selected. 3. If the checkbox is not selected, choose New Entries. 4. In the Activate FEH for Clients screen area, select the Activated checkbox.

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

Note Transaction Maintain Planned Shipping Handling Units is not required for transit warehousing processes, but can be used in the implementation phase for checking the system configuration or the data consistency. Therefore, the following setting is optional, but recommended.

Procedure ...

1.

In Customizing for Extended Warehouse Management, choose Master Data  Work Center  Specify

2.

Create the following entry for your warehouse number, for example, JPTY:

Work Center Layout.

Warehouse Number

Work Center Layout

Description

Transaction Type

JPTY

CAP

Cartonization in Transit Whse

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

JPTY


Determination Procedure

Layout

CAP


28

6.

Save your entry

...

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



29

4.6

Settings and Master Data in SAP ERP

4.6.1

Preparing Initial Transfer of Master Data from SAP ERP

You use this procedure to prepare the transfer of master data from SAP ERP to SAP EWM. In SAP ERP, you activate the immediate transfer of master data changes by means of business transaction events (BTEs). This means that changes to existing master data records are transferred immediately to SAP EWM. You generate a runtime version of the active integration model for performance purposes. The runtime version is adjusted after each activation or deactivation of integration models. For more information, see the documentation of the report RCIFIMAX.

Procedure ...

1.

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

Material Master Change Transfer Change Transfer for Customers Change Transfer for Vendors

  

2.

Generate the runtime version of the active integration model. a. On the SAP Easy Access screen, choose Tools  ABAP Workbench  Development  ABAP Editor. b. In the Program field, 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 CIF

You use this procedure to transfer master data from SAP ERP to SAP EWM. To transfer data using CIF, you first create an integration model. In the integration model, you define the selection criteria for the data. You activate the integration model manually. When you activate the model, the data is transferred. Once the data is contained in an active integration model, every change is communicated immediately to SAP EWM, as you have already activated the online transfer using BTE in the previous chapter,

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

1.

Create an integration model (for example: IMEWMTW1) : a. On the SAP Easy Access screen for SAP ERP, choose Logistics  Central Functions  Supply

Chain Planning Interface  Core Interface Advanced Planner and Optimizer  Integration Model  Create, or start 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 the Customer field. d. Select the vendors you want to transfer to SAP EWM, for example, by entering OAF* in the Vendor field. e. Save the model as a variant, for example, VIMEWMTW1, and go back to the selection screen. f. Press Execute. 2.

Activate the integration model manually:



30

a. On the SAP Easy Access screen for SAP ERP, choose Logistics  Central Functions  Supply

Chain Planning Interface  Core Interface Advanced Planner and Optimizer  Integration Model  Create, or start transaction CFM2.

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

Note If you activate a model for the first time in a client, the system proposes in a dialog box to create a number range interval for the object CIF_LOAD automatically. Accept the proposal. c. Press Start.

4.6.3

Scheduling Background Job for Master Data Transfer

To transfer master data that will be created in the future, you plan the transfer as a regular job.

Procedure Carry 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 Entries Do Not Issue Warning in Case of Parallel CIF Load

d. Save as a variant, for example, VIMEWMTW1. 3.

Define a background job for 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_). 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.


e. Create step number 3 by choosing Create. i.

In the ABAP program screen area, enter program RIMODAC2 and variant VIMEWMTW1.

ii.


f. Go back. g. Choose Start Condition. The Start Time screen appears. h. Choose Date/Time. i. Enter the scheduled start date and time. Transit Warehousing Configuration: Transit Warehousing


31

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.



32

4.7

Configuration in SAP TM

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

4.7.1

Assigning Warehouse Number to Location

You use this procedure to assign an SAP EWM warehouse number to a transit warehouse location in SAP TM.

Important For the transit warehousing processes Receiving from Shipper and Shipping 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 Network  Locations  Define Location.

2.

Enter the location and location type as described in the table below and press Enter.

3.

Choose tabstrip TM.

4.

Enter the target system for SAP EWM and the warehouse number:

Location

Location Type

SAP EWM Target System

SAP EWM Warehouse Number

OAF-STA-JPTYO

1002

EWMCLNT001

JPTY

OAF-STA-JPNGO

1002

EWMCLNT001

JPNG

AF-GW-JPNRT

1150

EWMCLNT001

JPNR

AF-GW-USLAX

1150

EWMCLNT001

USLA

OAF-STA-USPHX

1002

EWMCLNT001

USPH

OAF-STA-USSAN

1002

EWMCLNT001

USSA

5.

Save your changes

4.7.2

Transferring Locations and Business Partners from SAP TM to SAP EWM

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

Note As warehouse number JPTY is assigned to location OAF-STA-JPTYO in SAP TM, the report automatically assigns the location (as a supply chain unit) to the warehouse number JPTY in SAP EWM, if the warehouse number does not have a supply chain unit yet.

Procedure ...

1.

In SAP TM, start transaction SE38, enter program /SCMTMS/BUPA_SEND_TRANS_WH, and press

Execute. 2.

Select the locations of the transportation network:

Location

Description

AF-GW-JPNRT

Gateway Airport Narita

AF-GW-USLAX

Gateway Airport Los Angeles



33

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 Transportation Network..

Refer



34

4.8

Settings and Master Data in SAP EWM

4.8.1

Checking Business Partners of Transportation Network

The following table gives an overview of the business partners used for the transportation network of the LCL Air Freight scenario. In this procedure, you check that the business partners created manually in SAP TM and transferred to SAP EWM with report /SCMTMS/BUPA_SEND_TRANS_WH are available in SAP EWM. Business Partner 1

Business Partner 2

Business Partner 3

Business Partner 4

Business Partner 5

Business Partner 6

Business Partner ID

OAF-FWH-05

OAF-FWH-01

AF-FWH-03

AF-FWH-20

OAF-FWH22

OAF-FWH21

BP Role

Business Partner Gen.






Name

FH Tokyo

FH Nagoya

Gateway Narita

Gateway Los Angeles

FH San Diego

FH Tempe

Search Term 1/2

FWH STATION/JP

FWH STATION/JP

FWH Gateway/JP

FWH Gateway/U S

FWH STATION/U S

FWH STATION/U S

Street/Hou se number

6-23-15 Shiba/-

8-3 Kanayama Cho 1

Building 725-5

Spectrum Drive

Niels Bohr Court 2296

South Hardy Drive 8123

Postal Code/City

1080014/Tok yo

4560002/Nago ya

1080398/Nari ta

92602/Irvin e

92154/San Diego

852841106/Temp e

Country

JP

JP

JP

US

US

US

Region

13

23

12

CA

CA

AZ

Time Zone

JAPAN

JAPAN

JAPAN

PST

PST

MSTNO

Field/Value

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 Network

The following table gives an overview of the locations used for the transportation network of the LCL Air Freight scenario. In this procedure, you check that the locations created manually in SAP TM and transferred to SAP EWM with report /SCMTMS/BUPA_SEND_TRANS_WH are available in SAP EWM. Field/Value

Location1

Location 2

Location 3

Location 4

Location 5

Location 6

Location

OAF-STAJPTYO

OAF-STAJPNGO

AF-GWJPNRT

AF-GWUSLAX

OAF-STAUSPHX

OAF-STAUSSAN

Description

FH Station Tokyo

FH Station Nagoya

Gateway Airport Narita

Gateway Airport Los Angeles

FH Station Phoenix

FH Station San Diego

Location Type

1002

1002

1150

1150

1002

1002



35

Ext. Location

OAF-STAJPTYO

OAF-STAJPNGO

AF-GWJPNRT

AF-GWUSLAX

OAF-STAUSPHX

OAF-STAUSSAN

Bus.System Group

BG1

BG1

BG1

BG1

BG1

BG1

Time Zone

JAPAN

JAPAN

JAPAN

PST

MSTNO

PST

Search Term

FH Station

FH Station

Gateway Narita

Gateway LAX

FH Station

FH Station

Address

6-23-15 Shiba, Minatoku, Tokyo, 1080014

8-3 Kanayama Cho 1, Nagoya, 4560002

Building 727-5, Narita Airport, 1080398

Spectrum Drive, Building 1755,Irvi ne, 92602

8123 South Hardy Drive, Tempe,852 84-1106

2296 Niels Bohr Court, San Diego, 92154

Country

JP

JP

JP

US

US

US

Region

13 (Tokyo)

23

12 (Chiba)

CA (Californ ia)

AZ (Arizona)

CA (Californ ia)

IATA Code

-

-

NRT

LAX

-

-

UN/LOCODE

JPTYO

JPNGO

JPTYO

USLAX

USPHX

USSAN

Business Partner

OAF-FWH05

OAF-FWH01

AF-FWH-03

AF-FWH-20

OAF-FWH21

OAF-FWH22

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

Longitude

Latitude

OAF-STA-JPTYO

+ 139: 30: 00

+ 35: 45: 00

OAF-STA-JPNGO

+ 137: 15: 00

+ 35: 00: 00

AF-GW-JPNRT

+ 140: 23: 11

+ 35: 45: 53

AF-GW-USLAX

- 118: 24: 29

+ 33: 45: 53

OAF-STA-USPHX

– 112: 05: 44

+ 33: 33: 31

OAF-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 Warehouses

The locations of the transportation network transferred from SAP TM to SAP EWM also exist as supply chain units in SAP EWM. In this procedure, you maintain attributes for the supply chain units in order to use them as transit warehouse, receiving office, and shipping office in SAP EWM.

Important In order to run the processes Receiving from Shipper and Shipping to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, you need to maintain supply chain unit OAF-STA-JPTYO only.



36

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 Attributes

OAF-STA-JPTYO

INV, PLOC, RO, SO

OAF-STA-JPNGO

INV, PLOC, RO, SO

AF-GW-JPNRT

INV, PLOC, RO, SO

AF-GW-USLAX

INV, PLOC, RO, SO

OAF-STA-USPHX

INV, PLOC, RO, SO

OAF-STA-USSAN

INV, PLOC, RO, SO

3.

Save your entries

4.8.4

Maintaining Logical Conditions for Bin Determination

You use this procedure to create logical conditions for bin determination.

Note For more information about the condition records for bin determination, see Appendix C: Condition Records for Bin Determination.

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_25 PC_JPNG_10_25 PC_JPNR_10_25


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



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




PC_JPTY_OTHER PC_JPNG_OTHER PC_JPNR_OTHER

PC_JPTY_OTHER PC_JPNG_OTHER PC_JPNR_OTHER

&Cons. Postal Code& > 7500000

Logical Condition

Description

Formula

PC_USLA_80_86 PC_USSA_80_86 PC_USPH_80_86


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

3.

Save your entries.

4.




37







PC_USLA_OTHER PC_USSA_OTHER PC_USPH_OTHER

PC_USLA_OTHER PC_USSA_OTHER PC_USPH_OTHER

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

5.

Save your entries.

4.8.5

Checking Assignment of Supply Chain Unit to Warehouse Number

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

Important In order to run the processes Receiving from Shipper and Shipping to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, an entry is required for warehouse number JPTY only. As warehouse number JPTY is assigned to location OAF-STA-JPTYO in SAP TM, report /SCMTMS/BUPA_SEND_TRANS_WH has automatically assigned the location (as a supply chain unit) to the warehouse number JPTY in SAP EWM, if the warehouse number did not have a supply chain unit yet. If a supply chain unit was already assigned to the warehouse number, the report did not update the assignment. In this case, the warehouse number uses a supply chain unit that differs from the location used in SAP TM.

Procedure ...

1.

On the SAP Easy Access screen for SAP EWM, choose Extended Warehouse Management  Settings 

2.

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

Assignments: Warehouse Numbers/Business Partners Assign Warehouse Numbers.

Warehouse Number

Supply Chain Unit

Custodian

Default Party Entitled to Dispose

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 Records for Bin Determination

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

Storage bins



Staging area and door determination



38



Bin assignment for work centers



Condition records for bin determination

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

Note In order to run the processes Receiving from Shipper and Shipping to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, you need to process BDC files related to warehouse number JPTY only.

Note The same warehouse structure can be used for all transit warehouses across the transportation chain of the LCL Air Freight scenario. However, the bins created in some storage types are not needed in all locations. For example, areas used for loading and unloading HU containers are only required in warehouses representing a gateway.

Procedure ...

Implement the steps described in SAP Note 2214728.

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

Putaway to bins with limited or unlimited bin capacities



Putaway to bins using document references, such as forwarding order reference, as consolidation groups



Putaway to bins for single or multiple destination countries, regions, or postal codes



Putaway to bins depending on air cargo security requirements



Setup with or without a separate staging step before loading

Note For more information about the condition records for bin determination, see Appendix C: Condition Records for Bin Determination. The following figure shows the warehouse layout you created with the BDC files, and is followed by a legend explaining the different elements of the warehouse layout. The warehouse consists of two levels. The upper level is used for air cargo security handling, the lower level is used for non-secure cargo. In Customizing for Extended Warehouse Management, under Master Data  Define Storage Type, all storage types of the first level are configured with ACS Control set to Not Secure.



39

SA-15-17

D 0 2 0

D 0 1 9

D 0 1 8

D 0 1 7

D 0 1 6

D 0 1 5

First Level

SA-18-20 H910 Staging Areas (In- & Outbound)

H910 Staging Areas

H910 Staging Areas (In- & Outbound)

D 0 1 4

D 0 2 1


H923 Area for Loading on HU Container – Sections C01, C01I, C02, C02I, C99, C99I

D 0 1 3

SA-12-14

SA-21-23

COUNTRY-01-I02

COUNTRY-01-I04

COUNTRY-02-I02

COUNTRY-02-I04

COUNTRY-99-I02

COUNTRY-99-I04 D 0 2 3

D 0 1 2

COUNTRY-01

COUNTRY-02

COUNTRY-99



D 0 1 1

D 0 1 0

D 0 2 2

COUNTRY-01-I01

COUNTRY-01-I03

COUNTRY-02-I01

COUNTRY-02-I03

COUNTRY-99-I01

COUNTRY-99-I03 D 0 2 4

SA-09-11 SA-24-26

D 0 0 9

D 0 2 5

D 0 2 6

H922 Area for Unloading from HU Container

H921 Area per Country - Bins per Shipment – Sections C01, C01L, C02, C02L, C99, C99L

C01-01-11

C01-01-12

C02-03-11

C01-02-05

C01-01-09

C01-01-10

C01-01-07

C01-01-08

H980 Overflow Zones

C02-03-12

C01-02-06

C99-05-11

C02-04-05

C02-03-09

C02-03-10

C02-03-07

C02-03-08

C02-04-06

C99-05-10

C99-05-09

H910 Staging Areas (In- & Outbound) C99-05-07

D 0 0 8

C01-02-03

C01-02-04

C02-04-03

C02-04-04

C99-05-06

C-OVERFLOW

CHU-UNLOAD C01-01-05 D 0 0 7

C01-01-06

C02-03-05

C02-03-06

C99-05-05 H910 Staging Areas (In- & Outbound)

SA-06-08

D 0 2 7

C01-01-03

C01-01-04

C01-01-01

C01-01-02

D 0 0 6

C01-02-01

C02-03-03

C02-03-04

C02-03-01

C02-03-02

C01-02-02

C99-05-03

C02-04-01

C02-04-02

C99-05-02

SA-27-29

C99-05-01

D 0 2 8

D 0 2 9


D 0 0 5

GR-05

H920 Area per Region – Sections R01, R02, R99

H980 Overflow Zones

H040 Area for Dangerous Goods – Sections DG1, DG9

H050 Area for High Value Cargo

DG-01-09

DG-01-10

DG-02-09

DG-02-10

HV-01-13

HV-01-14

DG-01-07

DG-01-08

DG-02-07

DG-02-08

HV-01-11

HV-01-12

DG-01-05

DG-01-06

DG-02-05

DG-02-06

HV-01-09

HV-01-10


D 0 0 4

GR-04

DG-OVERFLOW



D 0 0 3

D 0 3 0

GR-03


D 0 0 2

DG-01-03

DG-01-04

DG-02-03

DG-02-04

HV-01-07

HV-01-08

DG-01-01

DG-01-02

DG-02-01

DG-02-02

HV-01-05

HV-01-06

HV-01-03

HV-01-04

HV-01-01

HV-01-02

REGION-99

REGION-02

REGION-01

SA-30-32

D 0 3 1

GR-02 D 0 3 2

H980 Overflow Zones

H970 Clarification Zone H910 Staging Areas (In- & Outbound) HV-OVERFLOW D 0 0 1

GR-01 CL-ZONE



H920 Area per Postcode – Section POC

D 0 4 4

D 0 3 3

POSTCODE-001 D 0 4 3

POSTCODE-002

POSTCODE-003

POSTCODE-999

SA-42-44 SA-33-35

D 0 4 2

D 0 3 4

D 0 3 5


SA-36-41

D 0 3 6

D 0 3 7

D 0 3 8

D 0 3 9

Configuration: Transit Warehousing

D 0 4 0

D 0 4 1

Transit Warehousing


40

Legend Layout

Storage Type

Storage Type Description

H040

Area for Dangerous Goods

Use and Structure Used to store dangerous goods. Bin capacity for cargo that is not overdimensional. Cargo is stored together in storage sections by dangerous goods regulation and dangerous goods class. One section is for dangerous goods of regulation ADR class 1 and one section is for all other dangerous goods. Putaway is to bins with the same consolidation group (for example, consolidation by forwarding order) or next empty bin, depending on capacity and consolidation groups. Due to setup with capacity and putaway rule using consolidation group, a corresponding overflow bin is setup (see storage type H980 Overflow Zones). Cargo in this area is staged before physical loading.

H050

Area for High Value Cargo

Used to store high-value cargo in a special area in the warehouse with limited access. Bin capacity for cargo that is not overdimensional. No storage sections. Putaway is to bins with the same consolidation group (for example, consolidation by forwarding order) or next empty bin, depending on capacity and consolidation groups. Due to setup with capacity and putaway rule using consolidation group, a corresponding overflow bin is setup (see storage type H980 Overflow Zones). Cargo in this area is not staged before physical loading, in order to reduce the time in which the cargo is not in the limited access area. Note that if you load a transit HU from this area, the bins are still reserved until the TU has left the warehouse.

H910

…


Staging Areas – Inbound and Outbound

Used for receiving HUs or HU containers. Bins are assigned to one or several doors. Some dedicated bins, GR-01 – GR-05, are assigned to single doors that are used in inbound processes only, intended for the receiving of transit HUs from shipper.


41

Bins are used as goods movement bin upon receiving. No capacity limitations. H920

Area by Postcode and Region

Used for cargo that is to be delivered to a final destination within same country or region as the one of the warehouse. Cargo with the following final destination is stored together: 

The same region



The same group of regions



The same postal code ranges

For this purpose, several storage sections exist: 

For special regions



For all other regions



For storage by postal code range

No capacity limitations. Cargo in this area is not staged before physical loading. The bins are already next to the doors that will be assigned to the TU by the warehouse clerk upon truck arrival. H921

Area by Country – Bins by Shipment

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

The same country



The same group of countries

Putaway is to bins with same consolidation group (for example, consolidation by forwarding order) or next empty bin, depending on capacity and consolidation groups. Special bins are used for overdimensional cargo. Due to setup with capacity and putaway rule using consolidation group, a corresponding overflow bin is setup (see storage type H980 “Overflow Zones”). Cargo in this area is staged before physical loading to TUs or TU containers, or is moved to the area for loading onto HU containers. H922

Area for Unloading from HU Container

Used for unloading cargo from HU containers. No capacity limitations. Bin is assigned to work center WUCH for unloading cargo from HU containers.



42

H923

Area for Loading onto HU Container

Used for loading cargo onto HU containers. No capacity limitations, but putaway is to bins with same consolidation group (for example, consolidation by freight booking) or next empty bin. Inbound sections of work centers WC01-WC03 are used for transit HUs. Main bins are used for HU containers and are assigned to a work center. Areas for loading of HU containers with the following final destination: 

The same country



The same group of countries

HU containers are not staged before physical loading. H970

Clarification Zone

Used for transit HUs that require clarification such as damaged HUs or HUs with special attributes that are not detailed in the forwarding order. No capacity limitations.

H980

…

Overflow Zones

Used for transit HUs if no bin can be determined for putaway in the area where this cargo would normally go. 

Bin C-OVERFLOW used for overflow in storage type H921 “Area by Country – Bins by Shipment”.



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



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

No capacity limitations. Cargo from C-OVERFLOW and DGOVERFLOW is staged before physical loading to TUs. Cargo from HV-OVERFLOW is not staged before physical loading to TUs in order to reduce the time in which this cargo is not in the limited-access area.



43

SA-15-17-G

G 0 2 0

G 0 1 9

G 0 1 8

G 0 1 7

G 0 1 6

G 0 1 5

Second Level

SA-18-20-G G910 Staging Areas (In- & Outbound)

G910 Staging Areas (In- & Outbound) G910 Staging Areas (In- & Outbound)

6 D 1 4

G 0 2 1

G910 Staging Areas (In- & Outbound)

G923 Area for Loading on HU Container – Sections C01, C01I, C02, C02I, C99, C99I

G 0 1 3

SA-21-23-G

SA-12-14-G

COUNTRY-01-I02G

COUNTRY-01-I04G

COUNTRY-02-I02G

COUNTRY-02-I04G

COUNTRY-99-I02G

G 0 2 3

G 0 1 2

COUNTRY-01-G

COUNTRY-02-G

COUNTRY-99-G


G910 Staging Areas (In- & Outbound) COUNTRY-01-I01G

G 0 1 1

G 0 1 0

G 0 2 2

COUNTRY-99-I04G

COUNTRY-01-I03G

COUNTRY-02-I01G

COUNTRY-02-I03G

COUNTRY-99-I01G

COUNTRY-99-I03G

G 0 2 4

SA-09-11-G SA-24-26-G

G 0 0 9

G 0 2 5

G 0 2 6

G922 Safe Area Unloading from HU Container

G921 Area per Country - Bins per Shipment – Sections C01, C01L, C02, C02L, C99, C99L

C01-01-11-G

C01-01-12-G

C02-03-11-G

C01-02-05-G

C01-01-09-G

C01-01-10-G

C01-01-07-G

C01-01-08-G

G980 Overflow Zones

C02-03-12-G

C01-02-06-G

C99-05-11-G

C02-04-05-G

C02-03-09-G

C02-03-10-G

C02-03-07-G

C02-03-08-G

C02-04-06-G

C99-05-10-G

C99-05-09-G

G910 Staging Areas (In- & Outbound) C99-05-07-G

G 0 0 8

C01-02-03-G

C01-02-04-G

C02-04-03-G

C02-04-04-G

C99-05-06-G

CHU-UNLOAD-G C01-01-05-G G 0 0 7

C01-01-06-G

C02-03-05-G

C02-03-06-G

C-OVERFLOW-G

C99-05-05-G G910 Staging Areas (In- & Outbound)

SA-06-08-G

G 0 2 7

C01-01-03-G

C01-01-04-G

C01-01-01-G

C01-01-02-G

G 0 0 6

C01-02-01-G

C02-03-03-G

C02-03-04_G

C02-03-01-G

C02-03-02-G

C01-02-02-G

C99-05-03-G

C02-04-01-G

C02-04-02-G

C99-05-02-G SA-27-29-G

G 0 2 8

C99-05-01-G

G 0 2 9


G 0 0 5

GR-05-G

G980 Overflow Zones

G040 Area for Dangerous Goods – Sections DG1 and DG9

DG-01-09-G

DG-01-10-G

DG-02-09-G

DG-02-10-G

DG-01-07-G

DG-01-08-G

DG-02-07-G

DG-02-08-G

DG-01-05-G

DG-01-06-G

DG-02-05-G

DG-02-06-G


G 0 0 4

GR-04-G

F910 Staging Areas (In- & Outbound)

F 0 0 3

DG-OVERFLOWG

F 0 3 0

GR-03-F


F 0 0 2


DG-01-03-G

DG-01-04-G

DG-02-03-G

DG-02-04-G

DG-01-01-G

DG-01-02-G

DG-02-01-G

DG-02-02-G

SA-30-32-F

F 0 3 1

GR-02-F F 0 3 2


F 0 0 1

GR-01-F


G960 Screening Zone

F 0 3 3

SCR-ZONE-DG

SCR-ZONE-01

SCR-ZONE-02

SCR-ZONE-99

SA-33-35-F

F 0 3 4

F 0 3 5



44

Legend Layout

Storage Type

Storage Type Description

F910

Un/Safe Staging Areas In- and Outbound

Used for receiving HUs or HU containers with and without air cargo security status.

Screening Zone

This is the main entry point from the non-secure area to the secure area of the warehouse. The storage type is used for screening. HUs are screened and air cargo security status is set in those bins.

Use and Structure

ACS Control of storage type is 1 Secure and Not Secure

… F960

…

ACS Control of storage type is 1 Secure and Not Secure G040

Safe Area for Dangerous Goods

Same as H040, but used for dangerous goods with air cargo security status.

ACS Control of storage type is 2 Secure

G910

Safe Staging Areas – Inbound and Outbound

Used for receiving HUs or HU containers with air cargo security status.

Safe Area by Country – Bins by Shipment

Same as H921, but used for cargo with air cargo security status to be delivered to the next destination in another country.


… G921

ACS Control of storage type is 2 Secure G922

Safe Area for Unloading from HU Container

Same as H922, but used for unloading cargo from HU containers containing HUs with air cargo security status.

ACS Control of storage type is 2 Secure Bin is assigned to work center WUCG for unloading cargo from HU containers. G923

Safe Area for Loading onto HU Container

Same as H923, but used for loading cargo with air cargo security status onto HU containers.

ACS Control of storage type is 2 Secure Inbound sections of work centers WCG1-WCG3 are used for transit HUs. Transit Warehousing Configuration: Transit Warehousing


45

Main bins are used for HU containers and are assigned to a work center. G980

Safe Overflow Zones

Same as G923 but used for transit HUs with air cargo security status if no bin can be determined for putaway in the area where this cargo would normally go.


…



Bin C-OVERFLOW-G used for overflow in storage type G921 “Area by Country – Bins by Shipment”.



Bin DG-OVERFLOW-G used for overflow in storage type G040 “Area for Dangerous Goods”.



HV is not stored separately in this safe area with authorized personal only, therefore no overflow bin is required.

No capacity limitations. After you have created the storage bins as described, you can display the warehouse layout. On the SAP Easy Access screen for Extended Warehouse Management, choose Monitoring  Graphical Warehouse Layout  Display Graphical Warehouse Layout. The following figure shows the rack view and the bin view of the graphical warehouse layout:

Rack View

Bin View

Graphical Warehouse Layout First Level



46

Rack View

Bin View

Graphical Warehouse Layout Second Level

4.8.7

Sort Storage Bins (Mandatory)

You use this procedure to sort storage bins in SAP EWM.

Important In order to run the processes Receiving from Shipper and Shipping to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, an entry is required for warehouse number JPTY only.

Procedure ...

1.

On the SAP Easy Access screen for SAP EWM, choose Extended Warehouse Management  Master Data

2.

Enter the following data:

 Storage Bin  Sort Storage Bins

Warehouse No.

Activity Area

Activity

JPTY

F001

-

Warehouse No.

Activity Area

Activity

JPTY

G001

-

3.

Click Execute.

4.

Enter the following data:

5.

Click Execute.

6.

If you want to run the complete air freight scenario with SAP EWM-managed warehouses, sort the storage bins for each of the warehouses JPNR, JPNG, USLA, USSA and USPH.



47

4.8.8

Creating Determination Records for Printing HU Waybill Labels

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

Important In order to run the processes Receiving from Shipper and Shipping to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, you need to create a condition record for warehouse JPTY only.

Procedure ...

1.

On the SAP Easy Access screen for SAP EWM, choose Work Scheduling  Print  Settings  Create Condition 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.


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

, for example LP01

, 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

5.

Save your entries

4.8.9

Creating Packaging Materials

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

Note For more information about the usage of packaging materials in transit warehousing processes, see Appendix D: Determination of Packaging Materials in SAP EWM.



48

Procedure ...

1.

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

2.


Field/Value

Product 1

Product 2

Product 3

Product 4

Product 5

Product

PALLET

BOX

OAF_TRUCK

PAG6

PMC6

Product Description

Pallet

Box

OAF_TRUCK - Air Freight Scenario

Pallet Q6 Contour (88x125x9 6)


Base Unit of Measure

EA

EA

EA

EA

EA

Pkg Data/Pack.M at.Type

PAL

BOX

MTR2

ULDP

ULDP

Pkg Data/HU Type

E1

C1

M1

E1

E1

Gross Weight

20

0.5

12

105

480

Unit of Weight

KG

KG

TO

KG

KG

Closed Packaging

-

X

-

-

-

3.

Save your entries

4.

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

Product Description

HalfWidth Lower Deck Cont (61x60) (LD3)

Lower Deck Container (88 x 125) (LD9)

Main Deck Container (96x125) (M1)





EA

EA

EA

EA

EA

EA

Pkg Data/Pack.M at.Type

ULD

ULD

ULD

ULDP

ULDP

ULDP

Pkg Data/HU Type

E1

E1

E1

E1

E1

E1

Gross Weight

100

222

360

480

480

480

Unit of Weight

KG

KG

KG

KG

KG

KG

Closed Packaging

X

X

X

-

-

-

5.

Save your entries



49

4.8.10 Defining the Link between Packaging Material and MTR in SAP EWM You use this procedure to link a packaging material to a means of transport for the creation of a TU or vehicle.

Note For more information about using packaging materials in transit warehousing processes, see Appendix D: Determination of Packaging Materials in SAP EWM.

Procedure ...

1.

On the SAP Easy Access screen for SAP EWM, choose Extended Warehouse Management  Settings  Shipping and Receiving  Link Between Packaging Material (TU) and Means of Transport.

2.

Check that the following entries exist, and if they do not, create them:

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.11 Defining Resource Group You use this procedure to set up resource management in SAP EWM. A resource is an entity representing a user or equipment, which can execute work in the warehouse. Resources are typically used when working with radio frequency (RF) devices. With resource management, you can define work queues, assign warehouse orders to the queues, and allow specific resources to work on specific queues. A resource group groups together resources with similar characteristics.

Important In order to run the processes Receiving from Shipper and Shipping to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, an entry is required for warehouse number JPTY only.

Procedure ...

1.

On the SAP Easy Access screen for SAP EWM, choose Master Data  Resource Management  Maintain

2.


Resource Group.

Warehouse No.

Resource Group

Description

JPTY

RG01

Resource Group 01

JPTY

RG02

Resource Group 02

3.

Save your entries

4.

If you want to run the complete air freight scenario with SAP EWM-managed warehouses, create and save the same entries for each of the warehouses JPNR, JPNG, USLA, USSA and USPH.

4.8.12 Defining Queue Sequence for Resource Group You use this procedure to create queue sequences for resource groups.



50

Important In order to run the processes Receiving from Shipper and Shipping to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, entries are required for warehouse number JPTY only.

Procedure ...

1.


2.


Queue 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

-

JPTY

RG02

1

GPUTAWAY

-

JPTY

RG02

2

GSTAGE

-

JPTY

RG02

3

GMOVE2LOAD

-

JPTY

RG02

4

PUTAWAY

-

JPTY

RG02

5

STAGE

-

JPTY

RG02

6

MOVE2LOAD

-

3.

Save your entries

4.


4.8.13 Defining Presentation Device You 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.


PresDevice

Description

Displ.Prof

PD01

Handheld

**

3.

Save your entries

4.8.14 Defining Resources You use this procedure to create resources representing the warehouse workers.

Important In order to run the processes Receiving from Shipper and Shipping to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario, entries are required for users working in warehouse number JPTY only.

Procedure ...

1.


Resource.



51

2.


Warehouse No.

Resource

Rsrce Type

Rsrce Grp

DefPresDvc

JPTY

RT01

RG01

PD01

JPTY

RT01

RG02

PD01

3.

Save your entries

4.




52

4.9

Configuration for SAP NetWeaver Process Integration

4.9.1

Checking Connection to SLD in SAP TM and SAP EWM

The application systems must be defined as business systems in the System Landscape Directory (SLD). You use this procedure to check that your application systems for SAP TM and SAP EWM are correctly connected to the SLD.

Procedure Start transaction SLDCHECK in SAP EWM and SAP TM. If the connection to SLD is configured correctly, the System Landscape Directory application appears in a new window. Close this new window and check the log displayed in transaction SLDCHECK. If the SLDCHECK is not successful, and there are error messages displayed after execution of transaction SLDCHECK in one or more of your application systems, proceed as follows: ...

1.

Start transaction SXMB_ADMIN.

2.

In folder Configuration, execute Integration Engine Configuration.

3.

Check the following data by pressing Change Configuration, and if necessary enter it:

Category

Parameters

Subparameter

Prefix

Current Value

Default Value

RUNTIME

ENGINE TYPE

-

-

LOC

UNDEFINED

RUNTIME

IS_URL

-

-

Dest://IS_<3digit SID of PI system>

-

For example,

Dest://IS_X 3X RUNTIME

4.9.2

LOGGING_SYN C

-

-

1

0

Creating a Configuration Scenario for Loading Appointment Integration

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

Procedure ...

1.

Start the Integration Directory in the SAP NetWeaver PI system by choosing Start Integration Builder: Configuration  Integration Directory or entering transaction SXMB_IFR.

2.

In the Integration Builder: Configuration screen, choose Tools  Apply Model from ES Repository.

3.

Select Process Integration Scenario.

4.

Select the integration 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: __. 6. Choose Finish and close the wizard. The Process Configurator starts. 7.

In the Configurator, click on the title of the first swimlane (SAP TM) and, on the Business System Component for A2A tab page, enter the communication component for SAP TM, for example, TMS_001.

8.

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



53

9.

Click on the connector between Send Loading Appointment Request in the SAP TM swimlane and Receive Loading Appointment Request in the SAP EWM swimlane. On the Connections from Component Assignment tab page, assign the communication channel for the Receiver Business System Component, for example GeneratedReceiverChannel_XI.

Note It 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 EWM swimlane and Receive Loading Appointment Notification in the SAP TM swimlane. On the Connections from Component Assignment tab page, assign the communication channel for the Receiver Business System Component, for example GeneratedReceiverChannel_XI.

11.

Click on the connector between both Get Transportation Document URI boxes. On the Connections from Component Assignment tab page, assign the communication channel for the Receiver Business System Component, for example GeneratedReceiverChannel_XI. In addition, select the Direct Connection checkbox, as this connection is used for the navigation between SAP TM and SAP EWM screens.

12.

Create configuration objects by choosing the Create Configuration Objects button. The Create Configuration Objects dialog box appears.

13.

Select Generation and choose the Start button. The system displays the result of the generation process in a log. You do not have to save the log.

14.

Choose Save to save your entries and Apply to leave the wizard.

15.

Activate all changes. For example, in the context menu for the configuration scenario, choose Activate. The system displays a screen on which you can select and activate all changes.

Important Since all configuration data is stored in the main memory, you must refresh the runtime cache in SAP 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 at http://help.sap.com/netweaver under SAP NetWeaver Platform  SAP NetWeaver 7.4  Application Help  Function-Oriented View. Choose SAP NetWeaver Library: Function-Oriented View  Process Integration  Integration Directory  Integration Directory (Dual Stack)  Using Tools to Configure Efficiently  Using the Process Model as a Configuration Template  Configuring Process Integration Scenarios.



54

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

Note The navigation is not necessary to run the processes Receiving from Shipper and Shipping to Next Transit Warehouse in the first transit warehouse of the LCL Air Freight scenario. It is recommended for processes involving freight bookings.

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

Prerequisites 

You have created and configured a configuration scenario for loading appointment integration in the SAP NetWeaver PI system as described in Creating a Configuration Scenario for Loading Appointment Integration.



The same user exists in SAP TM and SAP EWM with user roles enabling him or her to perform process steps in both applications. Typically, a user role based on /SCWM/EXPERT is assigned to the user in SAP EWM and a user role based on /SCMTMS/TRANSPORTATION_MGR_V2 is assigned to the user in SAP TM.



The user can start the SAP NetWeaver Business Client in SAP EWM and SAP TM.

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

Procedure ...

1.

In SAP EWM, ask your system administrator to create an RFC connection for SAP TM in Customizing for SAP NetWeaver under Application Server  IDoc Interface/Application Link Enabling (ALE)  Communication  Create RFC Connections as follows: a. Create a connection of type ABAP Connections, for 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 example TM1CLNT001_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 EWM You use this procedure to assign object-based navigation content to an SAP EWM user role. The content is needed for users starting the SAP NetWeaver Business Client from the SAP EWM system.



55

Procedure ...

1.

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 role

4.

On the Menu tab page, choose Copy Menus  From Another Role  Target System.

5.

Select the RFC Destination for SAP TM, for example, TM1CLNT001.

6.

Select role /SCMTMS/PROCESS_ADMINISTRATOR.

7.

Open the OBN-Target node and select the nodes needed for navigation, for example:

Forwarding Order Management Freight Order Management  EWM Integration 8. Press Add to copy the menu nodes to the new role.  

9.

In the hierarchy view, open the added menu nodes and enter a target system for the desired applications by pressing Other Node Details:

Menu Node

Application

Target System

Forwarding Order Management

Forwarding Order

TM

Freight Order Management

Freight Booking

TM


Freight Order

TM

EWM Integration

(Un-)Loading Preparation UI

EWM Integration

Freight Order UI

10.

Assign users to the profile

11.

Save your entries

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

Procedure ...

1.

In SAP TM, ask your system administrator to create an RFC connection for SAP EWM in Customizing for SAP NetWeaver under Application Server  IDoc Interface/Application Link Enabling (ALE)  Communication  Create RFC Connections, as follows: a. Create a connection of type ABAP Connections, for example, EWMCLNT001_T. On the Logon & Security tab page, do not specify a user. Select Current User instead. b. Create a connection of type HTTP Connections to ABAP System, for example EWMCLNT001_T_HTTP 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 TM You use this procedure to assign object-based navigation content to an SAP TM user role. The content is needed for users starting the SAP NetWeaver Business Client from SAP TM.



56

Procedure ...

1.

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 Management  Freight Order Management  EWM Integration 7. Press Add to copy the menu nodes to the new role. 

8.

In the Hierarchy view, open the added menu nodes and enter a target system for the desired applications by pressing Other Node Details:

Menu Node

Application

Target System

Forwarding Order Management

Forwarding Order


Freight Booking


Freight Order

EWM Integration

(Un-)Loading Preparation UI

EWM

EWM Integration

Freight Order UI

EWM

9. 10.

Assign users to the profile Save your entries



57

5

Test Case: Receiving from Shipper

You can use this test case to run the process Receiving from Shipper in warehouse number JPTY.

5.1 

Prerequisites This test case requires the following roles: 

Warehouse Operator with role EWM: Warehouse Expert (/SCWM/EXPERT)

For more information, see the prerequisites for Configuration: Transit Warehousing. 

5.2

You have configured SAP ERP, SAP Extended Warehouse Management (SAP EWM), SAP Transportation Management (SAP TM) and XI as described in Configuration: Transit Warehousing.

Features

This test case uses the following applications in SAP TM, which you can find in the Transportation Management menu of the SAP NetWeaver Business Client (NWBC): 

Forwarding Order Management  Forwarding Order  Create Forwarding Order



Freight Order Management  Road  Create Road Freight Order



Freight Order Management  Road  Edit Road Freight Order

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

Transit Warehousing  Process Single Freight Order



Transit Warehousing  Process Freight Orders



Transit Warehousing  Prepare Loading or Unloading



Transit 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 for

Extended Warehouse Management: 

5.3

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

Activities Step Description

Step Processor

Input Data

Expected Results

1

Create forwarding order (SAP TM)

Customer Service Clerk

See Testcase for LCL Air Freight Scenario (SAP TM) in the Solution Manager system.

Note down the forwarding order number for later use

2

Create freight order (SAP TM)

Transportati on Planner


Note down the freight order number for later use

Step

Transit Warehousing Test Case: Receiving from Shipper


58

...

3

Send unloading request to transit warehouse (SAP TM)


1.

2.

From the Transportation Management menu in NWBC, choose Freight Order Management  Road  Edit Road Freight Order. Enter the freight order number noted down in step 2 and press

The freight order is transferred to SAP EWM. The corresponding objects are created in SAP EWM, like vehicle, TU, and inbound delivery as freight order.

Continue. 3. From the Set Item Status drop down list, choose Set to Cargo Ready for Unloading. 4. Press Save. 5. Choose the Output Management tab page and check that TOR_LDAP_REQ was successfully processed. ...

4

Assign a door to the TU and post the arrival at the door (SAP EWM)

Receiving Office Clerk

1.

In SAP EWM, open the Process Single Freight Order screen.

2.

In the Freight Order field, enter the freight order number noted down in step 2. Leave the TOR Stop ID field empty and press

3.

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

4.

Choose Arrival at Door and assign a free door.

1.

Start transaction /SCWM/RFUI.

2.

Log on to the warehouse JPTY as resource with presentation device PD01.

3.

Choose Inbound Processes 

TU has status Arrival and

At Door.

Continue.

...

5

Receive the HUs (SAP EWM)

Warehouse Clerk

Receiving of Handling Units  Receiving by TU/Door (TW) (fast

Goods receipt has been posted for the HUs and an unloading notification message with the actual data is sent back to SAP TM. Note down the HU numbers for later use.

path 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 logoff screen. Choose Logoff (F1) and Save (F1).


59

...

6



1.


2.


3.

Press Departure from

1.


2.


3.

Choose Inbound Processes  Putaway  Putaway by HU (fast path 331).

4.

Enter the HU number noted down in step 6 and press Enter.

5.

Verify the destination bin and the HU number.

6.

Repeat this procedure for all the HUs you received.

7.

After you are finished press Back (F7) until you come to the logoff screen and press Logoff (F1) and Save (F1).

TU has status Departure and a notification message with the departed status is sent back to SAP TM.

Continue.

Checkpoint.

...

7

Putaway the HUs (SAP EWM)


Warehouse Worker

The HUs are put away into the destination storage type.


60

6

Test Case: Shipping to Next Transit Warehouse

You can use this test case to run the process Shipping to Next Transit Warehouse in warehouse number JPTY.

6.1 

Prerequisites This test case requires the following roles: 

Warehouse Operator with role EWM: Warehouse Expert (/SCWM/EXPERT)

For more information, see the prerequisites in Configuration: Transit Warehousing. 

6.2

You have configured SAP ERP, SAP Extended Warehouse Management (SAP EWM), SAP Transportation Management (SAP TM), and XI as described in Configuration: Transit Warehousing.

Features

This test case uses the following applications in SAP TM, which you can find in the Transportation Management menu of the SAP NetWeaver Business Client (NWBC): 

Forwarding Order Management  Forwarding Order  Create Forwarding Order



Freight Order Management  Road  Create Road Freight Order



Freight Order Management  Road  Edit Road Freight Order

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

Transit Warehousing  Process Single Freight Order



Transit Warehousing  Process Freight Orders



Transit Warehousing  Prepare Loading or Unloading



Transit 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 for

Extended Warehouse Management: 

6.3 Step

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

Activities Step Description

Step Processor

Input Data

Expected Results

...

1

Create freight order for stage 2 for precarriage (SAP TM)


Transit Warehousing Test Case: Shipping to Next Transit Warehouse


Note down the freight order number for later use


61

...

2

Send loading request to transit warehouse (SAP TM)


The freight order is transferred to SAP EWM.

1.

From the menu choose Freight Order Management  Road  Edit Road Freight Order.

2.

Enter the freight order number noted down in step 1 and press

3.

From the Set Status drop down list, choose Set to Ready for

4.

From the Set Item Status drop down list, choose Set to Cargo

5.

Press Save.

6.

Choose the Output Management, tab page and check that TOR_LDAP_REQ was successfully processed.

1.


TU has status Arrival and

2.


Note down the HU numbers from the screen area HUs/Container HUs.

Continue.

The corresponding objects are created in SAP EWM, like vehicle, TU, and outbound delivery order as freight order.

Transportation Execution.

Ready for Loading.

...

3

Truck Arrives at Checkpoint (SAP EWM)


At Door.

Continue. 3. In the TUs/Container TUs tab

page, select the row of the TU. 4.

Choose Arrival at Door and assign a free door.

1.


2.


3.

Choose Manual Selection  Selection by HU (fast path 22)

4.

Enter the HU number noted down in step 3 and press Enter.

5.

The source data is displayed. Press Enter.

6.

Verify the destination bin and press Enter.

7.

Repeat this procedure for all the HUs you noted down.

8.

After you are finished, press Back (F7) until you come to the logoff screen and press Logoff (F1) and Save (F1).

...

4

Stage HUs (optional) (SAP EWM)

Warehouse Clerk


The HUs are staged.


62

...

5

Load Truck (SAP EWM)

Warehouse Clerk

1.


2.


3.

Choose Outbound Processes 

4.

Enter the door you used in step 3.

The HUs have the status Loaded and an LDAPNotification message with the actual data is sent back to SAP TM.

Loading  Loading by TU / Door (TW) (fast path 438).

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 logoff screen. Choose Logoff (F1) and Save (F1).

...

6


Shipping Office Clerk

1.


2.


3.

Press Departure from

TU has the status Departure and an LDAPNotification message with the departed status is sent back to SAP TM.

continue


Checkpoint.


63

7

Appendix

The appendix contains additional information about the transit warehousing scenario. It describes additional information that gives a better understanding of the configuration. It also contains additional configuration not required in the preconfigured transit warehouse, but that may be necessary for using transit warehousing processes in your own warehouse.

7.1

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

Basic tables such as units of measure, currencies, countries, and languages are used by SAP ERP, SAP Transportation Management (SAP TM) and SAP Extended Warehouse Management (SAP EWM). Entries used in processes involving these applications must be identical in all systems. You use this procedure to check that the entries (especially the ISO codes) needed in your transit warehousing processes are identical in all systems that are part of your system landscape.

Procedure ...

1.

On the SAP Easy Access screen for SAP EWM choose Tools

Administration 2.

Customizing Objects

Administration

Administration

Client

Object Comparison.

Compare the information in the following tables between the EWM client and the ERP client and between the EWM client and the TM client. Compare the entries you plan to use in your transit warehousing processes. Adjust the tables Customizing in SAP TM, SAP ERP or SAP EWM, if necessary.

Table

Field

Description

T006

ISOCODE

Unit of measure

T002

LAISO

Language keys

TCURC

ISOCD

Currency codes

T005

INTCA

Countries

7.2

Appendix B: Verifying Synchronization of Customizing between SAP TM, SAP ERP, and SAP EWM

Some customizing entries must be defined in different tables in SAP ERP, SAP Transportation Management (SAP TM) and SAP Extended Warehouse Management (SAP EWM). For example, packaging material types of handling units in SAP EWM must be defined as package type codes in SAP TM. The following table gives an overview of table entries that must be synchronized across these applications: Customizing Path in SAP ERP

Customizing Path in SAP TM

Customizing Path in SAP EWM

Incoterms

Sales and Distribution  Master Data  Business Partners  Customers  Billing Document  Define Incoterms

SCM Basis  Master Data  Define Incoterms

Cross-Process Settings  Delivery Warehouse Request  General Settings  Define Incoterms

Means of Transport

Not applicable

Master Data  Resources  Define Means of Transport

SCM Basis  Master Data  Transportation Lane  Maintain Means of Transport

Setting

Transit Warehousing Appendix


64

Packaging Material Type (for transportation units)

Logistics-General  Handling Unit Management  Basics  Define Packaging Material Types

SCM Basics  Pack  Handling Units  Basics  Define Packaging Material Types

Cross Process Settings  Handling Units  Basics  Define Packaging Material Types

Packaging Material Type (for handling units in SAP EWM) or Package Type Code (SAP TM)

Logistics-General  Handling Unit Management  Basics  Define Packaging Material Types

Forwarding Order ManagementDefine Package Type Codes

Cross Process Settings  Handling Units  Basics  Define Packaging Material Types

Shipping Conditions (SAP ERP and SAP EWM) or Transportation Service Level Code (SAP TM)

Logistics Execution  Shipping  Basic Shipping Functions  Shipping Point and Goods Receiving Point Determination  Define Shipping Conditions

Forwarding Order ManagementDefine Transportation Service Level Codes

Cross-Process Settings  Delivery Warehouse Request  General Settings Define Shipping Conditions

Party Role Codes

-

Master Data Business Partners  Define Party Roles

Interfaces  TM Integration  Define Party Role Codes

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

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

Tip You can either compare the settings manually or use the Customizing Scout, which is a tool delivered with the SAP Solution Manager (transaction SMSY).

7.3

Appendix C: Condition Records for Bin Determination

This appendix contains the list of condition records created in Creating Warehouse Structure and Condition Records for Bin Determination, followed by an explanation of the bin determination using condition records. You can display the condition records from the SAP Easy Access screen for SAP EWM by choosing Extended

Warehouse Management -> Settings -> Transit Warehousing -> Maintain Condition Records for Bin Determination (Validity: Today’s Date to 31.12.9999). Alternatively, use transaction /SCWM/PUT_TW_WT_GCM.

Note The condition records listed below refer to warehouse number W100. In your system, the condition records exist in the warehouse numbers that you have created with the configuration document. Condition records for condition type 0TWQ and condition table SAPTWQ10 (clarification): Whn

ToBeClarified

Stor. Type

Stor.Bin

W100

X

H970

CL-ZONE

Condition records for condition type 0TWQ and condition table SAPTWQ15 (secure air cargo): Whn

NxtTWCtry

Dang.Goods

ACS Cntrl

Stor.Type

Stor.Bin

W100

US

-

1

F960

SCR-ZONE-01



65

W100

DE

-

1

F960

SCR-ZONE-02

W100

-

-

1

F960

SCR-ZONE-99

W100

-

X

1

F960

SCR-ZONE-DG

Condition records for condition type 0TWQ and condition table SAPTWQ20 (loading preparation): Whn

NxtTWCtry

Activity

ACS Cntrl

Stor.Type

Section

W100

US

MLCH

-

H923

C01I

W100

DE

MLCH

-

H923

C02I

W100

-

MLCH

-

H923

C99I

W100

US

MLCH

2

G923

C01I

W100

DE

MLCH

2

G923

C02I

W100

-

MLCH

2

G923

C99I

Condition records for condition type 0TWQ and condition table SAPTWQ30 (specific dangerous goods class): Whn

Sequence

Activity

Dang.Goods

Regulation

Class

ACS Cntrl

Stor.Type

Section

Stor.Bin

W10 0

1

STAG

X

ADR

3

-

H910

-

-

W10 0

2

STAG

X

ADR

3

-

F910

-

-

W10 0

1

-

X

ADR

3

-

H040

DG1

-

W10 0

2

-

X

ADR

3

-

H980

-

DGOVERFLOW

W10 0

1

STAG

X

ADR

3

2

G910

-

-

W10 0

2

STAG

X

ADR

3

2

F910

-

-

W10 0

1

-

X

ADR

3

2

G040

DG1

-

W10 0

2

-

X

ADR

3

2

G980

-

DGOVERFLOW -G

Condition records for condition type 0TWQ and condition table SAPTWQ40 (any dangerous goods class): Whn

Sequence

Activity

Dang.Goods

ACS Cntrl

Stor.Type

Section

Stor.Bin

W100

1

STAG

X

-

H910

-

-

W100

2

STAG

X

-

F910

-

-

W100

1

-

X

-

H040

DG9

-

W100

2

-

X

-

H980

-

DGOVERFLOW

W100

1

-

X

2

G040

DG9

-



66

W100

2

-

X

2

G980

-

DGOVERFLOWG

Condition records for condition type 0TWQ and condition table SAPTWQ50 (high-value cargo): Whn

Sequence

High-Value

ACS Cntrl

Stor.Type

Section

Stor.Bin

W100

1

X

-

H050

-

-

W100

2

X

-

H980

-

HVOVERFLOW

Condition records for condition type 0TWQ and condition table SAPTWQ60 (specific region or postal code): Sequenc e

FnlTWCtr y

FnlTWReg i

ACS Cntr l

Logical Condition

Stor.Typ e

Sectio n

Stor.Bin

W10 0

-

JP

12

-

-

H920

R01

-

W10 0

1

JP

13

-

PC_JPTY_10_2 5

H920

POC

POSTCODE -001

W10 0

2

JP

13

-

PC_JPTY_25_5 0

H920

POC

POSTCODE -002

W10 0

3

JP

13

-

PC_JPTY_50_7 5

H920

POC

POSTCODE -003

W10 0

4

JP

13

-

PC_JPTY_OTHE R

H920

POC

POSTCODE -999

W10 0

-

JP

15

-

-

H920

R02

-

Whn

Condition records for condition type 0TWQ and condition table SAPTWQ70 (any region or postal code): Whn

FnlTWCtry

ACS Cntrl

Stor.Type

Section

W100

JP

-

H920

R99

Condition records for condition type 0TWQ and condition table SAPTWQ80 (other specific countries): Whn

Sequence

FnlTWCtry

Activity

Overdimen.

ACS Cntrl

Stor.Type

Section

Stor.Bin

W100

1

DE

-

-

-

H921

C02

-

W100

2

DE

-

-

-

H980

-

COVERFLOW

W100

1

DE

-

-

2

G921

C02

-

W100

2

DE

-

-

2

G980

-

COVERFLOWG

W100

1

DE

STAG

-

-

H910

-

-

W100

2

DE

STAG

-

-

F910

-

-

W100

-

DE

STAG

-

2

G910

-

-

W100

-

DE

STAG

-

2

F910

-

-



67

W100

1

DE

-

X

-

H921

C02L

-

W100

2

DE

-

X

-

H980

-

COVERFLOW

W100

1

DE

-

X

2

G921

C02L

-

W100

2

DE

-

X

2

G980

-

COVERFLOWG

W100

1

DE

STAG

X

-

H910

-

-

W100

2

DE

STAG

X

-

F910

-

-

W100

1

DE

STAG

X

2

G910

-

-

W100

2

DE

STAG

X

2

F910

-

-

W100

1

US

-

-

-

H921

C01

-

W100

2

US

-

-

-

H980

-

COVERFLOW

W100

1

US

-

-

2

G921

C01

-

W100

2

US

-

-

2

G980

-

COVERFLOWG

W100

1

US

STAG

-

-

H910

-

-

W100

2

US

STAG

-

-

F910

-

-

W100

1

US

STAG

-

2

G910

-

-

W100

2

US

STAG

-

2

F910

-

-

W100

1

US

-

X

-

H921

C01L

-

W100

2

US

-

X

-

H980

-

COVERFLOW

W100

1

US

-

X

2

G921

C01L

-

W100

2

US

-

X

2

G980

-

COVERFLOWG

W100

1

US

STAG

X

-

H910

-

-

W100

2

US

STAG

X

-

F910

-

-

W100

1

US

STAG

X

2

G910

-

-

W100

2

US

STAG

X

2

F910

-

-

Condition records for condition type 0TWQ and condition table SAPTWQ90 (any other countries): Whn

Sequence

Activity

Overdimen.

ACS Cntrl

Stor.Type

Section

Stor.Bin

W100

1

-

-

-

H921

C99

-

W100

2

-

-

-

H980

-

C_OVERFLOW

W100

1

-

-

2

G921

C99

-

W100

2

-

-

2

G980

-

C_OVERFLOWG

W100

1

STAG

-

-

H910

-

-



68

W100

2

STAG

-

-

F910

-

-

W100

1

STAG

-

2

G910

-

-

W100

2

STAG

-

2

F910

-

-

W100

1

-

X

-

H921

C99L

-

W100

2

-

X

-

H980

-

C_OVERFLOW

W100

1

-

X

2

G921

C99L

-

W100

2

-

X

2

G980

-

C_OVERFLOWG

W100

1

STAG

X

-

H910

-

-

W100

2

STAG

X

-

F910

-

-

W100

1

STAG

X

2

G910

-

-

W100

2

STAG

X

2

F910

-

-

Condition records for condition type 0TWD and condition table SAPTWD10 (unloading): Whn

No Unpack.

ACS Cntrl

Stor.Type

Storage Bin

W100

-

-

H922

CHU-UNLOAD

W100

-

1

H922

CHU-UNLOAD

W100

-

2

H922

CHU-UNLOAD-G

Condition records for condition type 0TWD and condition table SAPTWD15 (secure air cargo): Whn

NxtTWCtry

Dang.Goods

ACS Cntrl

Stor.Type

Stor.Bin

W100

US

-

1

F960

SCR-ZONE-01

W100

DE

-

1

F960

SCR-ZONE-02

W100

-

-

1

F960

SCR-ZONE-99

W100

-

X

1

F960

SCR-ZONE-DG

Condition records for condition type 0TWD and condition table SAPTWD20 (specific countries): Whn

NxtTWCtry

ACS Cntrl

Stor.Type

Section

Storage Bin

W100

US

-

H923

C01

COUNTRY-01

W100

DE

-

H923

C02

COUNTRY-02

W100

US

2

G923

C01

COUNTRY-01G

W100

DE

2

G923

C02

COUNTRY-02G

Condition records for condition type 0TWD and condition table SAPTWD30 (any other countries): Whn

ACS Cntrl

Stor.Type

Section

Storage Bin

W100

-

H923

C99

COUNTRY-99

W100

2

G923

C99

COUNTRY-99-G



69

Explanation of Bin Determination Using Condition Records The condition records listed above are an example adapted to the warehouse layout created in Creating Warehouse Structure and Condition Records for Bin Determination, and are used to determine an appropriate destination bin during warehouse task creation. The bin determination uses one or more condition records created in multiple condition tables containing fields from a global field catalog. Using multiple smaller condition tables in a strict order allows a reduction of the number of condition records necessary to map all required movements in the example layout. However, one trade-off when using multiple tables is the increased complexity when creating condition records and retracing which condition records match in a specific use case. The following figure shows the order in which SAP EWM accesses the condition tables when searching for a suitable bin for transit HUs (left-hand side) and for HU containers (right-hand side). Each row represents a unique condition table. The boxes refer to the different areas of the warehouse layout and indicate which result data (destination data) the condition records of the table contain. For example, the first table, SAPTWQ10 represents the clarification zone in the warehouse layout. As this is the only box in the row, no result data other than clarification is defined in the condition record of this table. Compared to this, the fourth row for table SAPTWQ30 contains one box for the dangerous goods area, one box for the staging area and one box for the overflow area. This means that the condition records of this condition table contain three different sets of result data.

SAPTWQ10

SAPTWD10

Clarification

Unloading

SAPTWQ15

SAPTWD15

Secure Air Cargo

Secure Air Cargo

SAPTWQ20

SAPTWD20

Loading Preparation

Specific Countries

SAPTWQ30 Specific Dangerous Goods Class

SAPTWQ40 Any Dangerous Goods Class

STAG OV

SAPTWD30 Any Other Countries

STAG OV

SAPTWQ50

OV

High-Value Goods

Clarification Area

SAPTWQ60 Same Country with Specific Region/Postcode

Screening Area Dangerous Goods Area

SAPTWQ70 Same Country for Any Region/Postcode

High-Value Area Overflow Area

SAPTWQ80 Other Specific Countries

STAG OV

Area per Country Staging Area/Unloading from HU Container Area

SAPTWQ90 Any Other Countries

STAG OV

Area per Region and Postcode/Area for Loading on HU Container

The order in which SAP EWM tries to find a matching condition record in one of the condition tables is defined by the access sequence. The determination according to the access sequence stops immediately if a matching condition record is found in one of the tables, so that no other table will be accessed. This does not mean that only a single condition record is returned for further processing: multiple condition records can be found in one condition table due to the use of the sequence number field in the condition table. As different condition tables are used for bin determination of transit HUs and HU containers, different determination procedures are assigned to the warehouse number.



70

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

Note For information about the customizing for this example, see Customizing for Extended Warehouse Management under Goods Receipt Process  Strategies  Storage Bin Search Sequence for Transit HUs Search Sequence

Table

Description

1

SAPTWQ10

Clarification The only relevant attribute is the To Be Clarified indicator. If the To Be Clarified status is set for a transit HU, the system determines a storage bin in the clarification zone (storage type H970) based on the single condition record of this table. Note that clarification is done only on the first warehouse level. If a secure HU requires clarification, it is also moved to the (non-secure) clarification zone, meaning that it loses its air cargo security status.

2

SAPTWQ15

Secure Air Cargo Cargo that requires screening is put away to the screening area (storage type F960) upon warehouse task creation. There are different screening areas for dangerous goods and depending on the country of the next transit location. Note that the country of the next location is optional (“field in free key part”), which allows you to set up a screening zone for dangerous goods with a single condition record, valid for all countries.

3

SAPTWQ20

Loading Preparation The areas for loading transit HUs onto HU containers should only be found in the loading preparation process. Warehouse tasks for loading preparation use a special warehouse process type. It is assigned to the warehouse number and uses activity MLCH. All condition records in this table will match for this activity only. The destination data of the condition records contains different inbound sections of a work center within storage type H923 (secure cargo: G923) that is used for loading cargo onto HU containers. Different inbound sections are found by the consolidation group. An additional criteria in this condition table is the country of the next unloading location, which also leads to the determination of different storage sections. For example USA (US) matches to the condition record with storage section C01 and Germany (DE) matches to a condition record with storage section C02. Note: This table is positioned very early in the access sequence in order to reduce the number of condition records that have to be created for any transit HU in the destination bin determination for loading preparation. By using a special warehouse process type with activity MLCH in this table, the loading preparation for all transit HUs finds condition records in this table as long as this activity is used. For example, there is no need to create additional condition records in table SAPTWQ50 for loading preparation of high-value goods. Nor do you need to create additional condition records in table SAPTWQ80 for loading preparation of transit HUs which are shipped to a different next unloading location country, like the US.



71

4

SAPTWQ30

Specific Dangerous Goods Class With the example condition records, transit HUs containing dangerous goods of regulation code ADR and class 3 will be stored in a dedicated area. Different dangerous goods areas are used for secure and non-secure cargo. As there are capacity limitations, overflow storage bins are also returned. Therefore the determination finds two matching condition records with different sequence numbers. The sequence number also gives the order in which the storage bin is used in searches in further processing. The destination data for class 3 and regulation code ADR of the first condition record is storage section DG1 of storage type H040 (secure cargo: G040). The system finds different conditions for warehouse tasks created with activity STAG, as a different destination bin should be found for the staging activity. The additional condition records for staging to storage type F910 are used for loading secure and non-secure cargo at the same door. Note that for any other activity, the system finds the condition records where the Activity field is empty, as the field is defined as optional (“field in free key part”) in customizing for the access sequence.

5

SAPTWQ40

Any Dangerous Goods Class In the previous table, records exist for transit HUs containing dangerous goods of regulation code ADR and class 3 only. For any other dangerous goods data not maintained in table SAPTWQ30, the system uses table SAPTWQ40 for bin determination. In the example condition records, the system finds storage section DG9 in storage type H040 or G040 for any dangerous goods not classified as regulation code ADR and class 3. For non-secure cargo, other condition records might match: one with a different sequence number for the overflow bin (DG-OVERFLOW), and two with activity STAG for the staging activity. The first entry for staging (sequence 1) is for loading cargo at non-secure doors (storage type H910), the second one (sequence 2) for loading non-secure cargo together with secure cargo (storage type F910). The same logic applies to secure cargo. The overflow bin in this case is DGOVERFLOW-G in storage type G980. The first entry with activity STAG for secure cargo is for loading at secure doors (storage type G910), the second one for loading secure cargo together with non-secure cargo (storage type F910). Note: In general, we recommend creating an additional condition record for an overflow storage bin if the storage types used in the determination have capacity limitations, to avoid interruptions in the process if all bins are occupied at a point in time.

6

SAPTWQ50

High-Value Goods The table contains two condition records with different sequence numbers. The system searches for a storage bin in the storage type for high value goods (H050) first. As there are capacity restrictions, a second condition record with an overflow storage bin also exists. As there is no staging of high value cargo in the example warehouse layout, there is no additional condition record with activity STAG. Note: Since the dangerous goods tables are placed before the table for high-value cargo, the dangerous goods information implicitly has a higher priority than the high-value indicator. This means that a transit HU containing dangerous goods and high-value cargo will be stored in the area for dangerous goods. Note: The air cargo security control is part of the condition table but entries only exist for ACS Control – Not Relevant, as there is no additional separation of highvalue cargo in the secure area.

7

SAPTWQ60

Same Country with Specific Region/Postcode The condition records of this table are used to store cargo that is to be delivered in the same country as the transit warehouse; in this example in Japan (JP). In storage type H920, cargo is separated by region: cargo for region 12 is stored in section R01 and cargo for region 15 in section R02.



72

For cargo to be delivered in the same region as the transit warehouse (region 13), condition records exist to group the cargo by postal code range in storage section POC of the same storage type. Using the postal code of the consignee, the system finds a suitable condition record by evaluating the logical condition, which leads to different storage bins for each postal code range. Note: The air cargo security control is part of the condition table but entries only exist for ACS Control – Not Relevant, as the separation of cargo by postal code or region is only done in the transit warehouse delivering the cargo to the final consignee (after the flight). 8

SAPTWQ70

Same Country for Any Region/Postcode This table contains condition records for cargo for any region of the transit warehouse’s country that has no condition record of its own in the previous table. Cargo for these regions is stored in storage section R99 of storage type H920. Note: see previous condition table for the ACS Control field

9

SAPTWQ80

Other Specific Countries This table is used to store cargo where the country of the final transit warehouse is different from the country of the current transit warehouse. Cargo for specific countries is stored in different storage sections of storage type H921 (secure cargo: storage type G921). In this example, cargo for the USA (US) is stored in section C01 and cargo for Germany (DE) in section C02. Overdimensional cargo is also stored in different sections per specific country. As the system finds a new bin for each consolidation group, it might happen that all storage bins within a section for a country are occupied. Therefore, an additional condition record with a different sequence number is returned for the overflow storage bin in storage type H980 (secured cargo: storage type G980). This is valid for all activities except when using STAG. In this case, the system finds a different condition record. They point to storage types H910 and F910 (secure cargo: G910 and F910), to allow staging to a storage bin close to the door used to load the cargo. Note: due to the fact that the staging activity is processed for normal cargo as well as for overdimensional cargo, several condition records exist with activity STAG, but only one is found at any one time.

10

SAPTWQ90

Any Other Countries This table is used for storing cargo depending on the final transit warehouse location for which no entry has been found in the preceeding tables. For cargo not relevant for air cargo security handling, this means that the table is used when the country of the final transit warehouse is different to the country of the current transit warehouse, but not explicitly defined in the previous table, nor already determined by one of the other previous tables (for example, for dangerous goods or high value cargo). For secure cargo, the table is used to store cargo depending on the country of the final transit warehouse not yet explicitly defined in the previous table, nor determined by one of the previous tables (for example, for dangerous goods). Cargo to be delivered to countries that are not specified in the previous table is stored in a separate storage section C99 of storage type H921 (secure cargo: storage type G921). The system finds a different condition record for overdimensional cargo, pointing to section C99L of the same storage type. Different condition records are used for staging here too.

Search Sequence for HU Containers Search Sequence

Table

Description

1

SAPTWD10

Unpack The condition record in this table is used to move HU containers to be unloaded to the unloading storage bin CHU-UNLOAD of storage type H922 (secure cargo: CHU-UNLOAD-G of storage type G922). It is valid for all HU containers with the indicator Unloaded Expected.



73

2

SAPTWD15

Secure Air Cargo If a HU container contains cargo requiring screening, the HU container is put away to the screening area (storage type F960). There are different screening areas for dangerous goods and depending on the country of the next transit location. If the HU container contains dangerous goods, the determined bin is SCR-ZONE-DG, otherwise the screening area is determined by country.

3

SAPTWD20

Specific Countries Condition records of this table are considered for HU containers that are not expected to be unloaded. Otherwise the condition record in the previous table would match. The condition records separate the storage of HU containers into different storage sections depending on the country of the next transit warehouse location. For example, HU containers containing cargo not relevant for air cargo security with Next Transit Warehouse Location Country USA (US) match to condition record with section C01 and storage bin COUNTRY-01 of storage type H923, and HU containers with Next Transit Warehouse Location Country Germany (DE) match to condition record with section C02 and storage bin COUNTRY-02 of storage type H923. Note: The condition table contains an optional field for the activity defined in the warehouse process type. Therefore, it is possible to create condition records to build an additional process step, for example, staging of HU containers.

4

SAPTWD30

Any Other Country HU containers with a Next Transit Warehouse Location Country that does not match any record of the previous table will match a condition record for storage section C99 and storage bin COUNTRY-99 of storage type H923 (secure cargo: storage bin COUNTRY-99_G of storage type G923). Note: the condition table also contains an optional field for the activity defined in the warehouse process type.



74

7.4

Appendix D: Determination of Packaging Materials in SAP EWM

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

Note Vehicles do not have a packaging material in SAP EWM, only a means of transport. A packaging material is only required for planned vehicles in an outbound process for technical reasons. Determination of packaging materials for vehicles and transportation units The following figure gives an overview of the packaging material determination for vehicles and TUs in SAP EWM:

Case 1: If a packaging material is assigned to the resource master used in the freight document of SAP TM, SAP TM sends this packaging material to SAP EWM in the corresponding item of the TransportationOrderLoadingAppointmentRequest message. A packaging material with the same name must exist in SAP EWM. In this case, SAP EWM uses the packaging material with the same name to create the vehicle or TU. Case 2: There is no packaging material in the vehicle resource master in SAP TM. In this case, the corresponding item in the TransportationOrderLoadingAppointmentRequest message contains a vehicle type. This type is mapped to a packaging material in SAP EWM that has the same name as the vehicle type. There is no direct relationship between the vehicle group in SAP TM and the packaging material type in SAP EWM, but in this case you can use the same names for vehicle groups and packaging material types. Case 3: If the vehicle type cannot be mapped to a packaging material in SAP EWM because no packaging material of the same name exists, the packaging material is determined from the means of transport. For more information, see Defining the Link between Packaging Material and MTR in SAP EWM.



75

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

The transportation unit type (TU type) of the resource used in the freight document of SAP TM is mapped to a packaging material in SAP EWM with the exact same name as the TU type (for example, container type 20G0). There is no direct relationship between the TU group in SAP TM and the packaging material type in SAP EWM, but you can use the same names for TU groups and packaging material types (for example, CN for containers). In addition, the TU group is mapped to a means of transport of the same name in SAP EWM. Determination of packaging materials for transit HUs The following figure gives an overview of the packaging material determination for transit HUs in SAP EWM:

The packaging type of the package item contained in the freight document of SAP TM is mapped to a packaging material type in SAP EWM with the exact same name (for example, PAL for pallet). SAP EWM expects that only one packaging material (for example PALLET) exists for this packaging material type, and uses this packaging material to create the transit HUs.

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



76

7.5

Appendix E: Additional Configuration for LCL Ocean Freight Scenario

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

1.

In SAP EWM, create two additional transit warehouses JPYO (CFS Yokohama) and USLO (CFS Los Angeles) 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 as described in Assigning Warehouse Number to Location.

3.

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

4.

In SAP EWM, maintain the attributes for supply chain units OF-CFS-JPYO and OF-CFS-USLAX as described 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 in Maintaining Logical Conditions for Bin Determination. The logical conditions follow the same naming convention: PC__xxxxx.

6.

In SAP EWM, create the warehouse structure and condition records for bin determination for the new warehouses 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 as described in Creating Determination Records for Printing HU Waybill Labels. The entry is identical to the entry for warehouse JPNR.

8.

In SAP EWM, create the following packaging materials for containers as described in Creating Packaging Materials:

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


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 the Link 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.



77

12.

7.6

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

Appendix F: Hints for Dangerous Goods Handling

Dangerous goods are not part of the transit warehousing scenario, but can be used in general in transit warehousing processes. If a package item of a forwarding order contains dangerous goods, you enter dangerous goods information for this item in SAP TM. The dangerous goods information is communicated to SAP EWM in the TransportationOrderLoadingAppointmentRequest message, so that SAP EWM can determine a suitable bin in the dangerous goods area for the transit HUs of this package item.

Note The appendix does not contain a step-by-step instruction on how to set up dangerous goods in your system. 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 TM



You have set up an example dangerous goods customizing in SAP EWM. For this purpose, download the BC set from note 2162516 and activate it.



Since there will be transfer of freight orders between SAP TM and SAP EWM, you must have example customizing for dangerous goods data available in both system. This customizing and must be kept in sync.



During implementation, you have maintained the required customizing and dangerous goods master data, which serve as templates.

Note SAP delivers licensed dangerous goods master data and customizing which can be purchased by the customer. 

You have checked if you require an implementation of BAdI /SCWM/EX_DLV_DG_AGGR. The BAdI can be found in Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management  Cross-Process Settings  Delivery- Warehouse Request  BAdI: Aggregation

and Prioritization of Dangerous Goods Data



78

www.sap.com/contactsap

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

© 2016 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of 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.

EWM Transit Warehousing

Recommend Documents