CG_TM_IOT_FINAL

SAP 1

SAP Transportation Management

Configuration Guide for International Outbound Transportation

CUSTOMER Document Version: 4.0 December 2013

SAP 2

Copyright Copyright 2013 SAP AG. All rights reserved. SAP Library document classification: PUBLIC

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#trademark for additional trademark information and notices.

SAP 3

Icons in Body Text Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of

information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions Type Style Description

Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and table titles. EXAMPLE TEXT Technical names of system objects. These include report names, program

names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

SAP 4

Table of Contents Configuration Guide for International Outbound Transportation ..................................................... 6

1 The Scenario ............................................................................................................................. 8 2 ERP Master Data .................................................................................................................... 11

2.1 Creating Customers in SAP ERP ..................................................................................... 12 2.2 Defining Vendor Master Data ........................................................................................... 17

3 SAP TM Basic Configuration .................................................................................................. 19 3.1 Creating Models and Active Versions .............................................................................. 20

4 Transferring Master Data to SAP TM (CIF) ............................................................................ 21 4.1 Creating Integration Models ............................................................................................. 22 4.2 Activating Integration Models ........................................................................................... 25

5 Creating Organizational Model in SAP TM ............................................................................. 27 5.1 Creating Sales Organizations, Sales Offices, and Sales Groups .................................... 28 5.2 Creating Purchasing Organization ................................................................................... 31 5.3 Creating Planning and Execution Organizations ............................................................. 34

6 Defining a Transportation Network ......................................................................................... 37 6.1 Defining Transportation Modes ........................................................................................ 38 6.2 Defining Means of Transport ............................................................................................ 39 6.3 Creating Locations for Warehouses and Seaports .......................................................... 40 6.4 Defining Transportation Zones ......................................................................................... 42 6.5 Defining a Transportation Zone Hierarchy ....................................................................... 43 6.6 Maintaining a Transportation Zone Hierarchy .................................................................. 44 6.7 Checking BP Type for Transportation Service Providers ................................................. 46 6.8 Defining Transportation Lanes ......................................................................................... 47 6.9 Assigning Transshipment Locations ................................................................................ 49

7 Defining Equipment Groups and Equipment Types................................................................ 50 8 Waybill Stock........................................................................................................................... 52

8.1 Defining Waybill Number Stock Types ............................................................................. 53 8.2 Defining Waybill Stocks .................................................................................................... 54

9 Freight Unit Building ................................................................................................................ 55 9.1 Defining Freight Unit Types .............................................................................................. 56 9.2 Creating Freight Unit Building Rules ................................................................................ 58 9.3 Defining Conditions for Determining the FUB Rule .......................................................... 59

10 Setting Up Customizing for Settlement Document Types .................................................... 61 10.1 Defining Freight Settlement Document Types ............................................................... 62 10.2 Defining Settlement Profiles ........................................................................................... 64 10.3 Defining General Settings for Charge Calculation ......................................................... 65 10.4 Defining Charge Calculation Profiles ............................................................................. 66

11 Order Management ............................................................................................................... 67 11.1 Defining Forwarding Order Type .................................................................................... 68

12 Transportation Charge Management .................................................................................... 70 12.1 Defining Forwarding Agreement Type ........................................................................... 71 12.2 Defining Freight Agreement Type .................................................................................. 72

13 Creating Freight Agreements for Customers and Vendors .................................................. 73 13.1 Defining a Forwarding Agreement for Shipper IOT-CU-01 ............................................ 74 13.2 Defining a Freight Agreement for Carrier IOT-CR-01 .................................................... 80 13.3 Defining a Freight Agreement for Carrier IOT-CR-03 .................................................... 84 13.4 Defining a Freight Agreement for Carrier IOT-CR-02 .................................................... 87

14 Setting Up Mapping Rules Between SAP TM and ERP ....................................................... 90 14.1 Defining the Assignment of Purchasing Business Areas ............................................... 91 14.2 Defining the Assignment of Sales and Distribution Business Areas .............................. 92 14.3 Assigning Transportation Charge Type Codes to Condition Types ............................... 93

15 Subcontracting ...................................................................................................................... 94 15.1 Defining Freight Order Types ......................................................................................... 95 15.2 Defining Freight Booking Type ....................................................................................... 97

SAP 5

16 Transportation Planning and Execution ................................................................................ 99 16.1 Defining Vehicle Resources ......................................................................................... 100 16.2 Creating Selection Profiles ........................................................................................... 102 16.3 Creating Planning Profiles ............................................................................................ 108

17 SAP Event Management ..................................................................................................... 121 17.1 Tracking Freight Unit and Freight Order Execution ..................................................... 122 17.2 Changing Application Object Types and Event Types ................................................. 123 17.3 Activating Freight Unit Types ....................................................................................... 125 17.4 Activating Freight Order Types .................................................................................... 126 17.5 Assigning Your Parameter Profile to a Mapping Area (SCEM).................................... 127 17.6 Assigning Your User to a User Profile in Web Interface (SCEM) ................................ 128

SAP 6

Configuration Guide for International Outbound Transportation

This document describes the configuration settings for the International Outbound Transportation scenario. You must implement this scenario as described and once you have verified the functionality, you can change the data to suit your own environment and operating conditions.

Change History

Version Date Description

1.0 December 2010

Initial version

1.1 February 2011

Harmonized configuration and master data; scenarios based on IDES.

2.0 July 2011 Updated the following sections:

Defining Charge Calculation Profiles [Page 66]

Defining General Settings for Freight Agreements and Charge Management (see comments for version 3.1)

Defining Forwarding Order Types [Page 68]

3.0 February 2012

Updated the following chapters for TM 9.0 setup:

Creating Selection Profiles [Page 102] (for profile IOT-GEN-SEL-OCEAN-01)

Defining Settlement Profiles [Page 64] (profile IOT_SP_02 changed)

Defining Freight Settlement Document Types [Page 62]

3.1 September 2012

Added the following sections and chapters:

Waybill Stock

o Defining Waybill Number Stock Types

o Defining Waybill Stocks

Updated the following sections:

Defining Freight Unit Type

Defining Forwarding Order Type

Defining Freight Order Types

Defining Freight Booking Type

Event Management

SAP 7

Removed the following chapters:

Defining General Settings for Freight Agreements and Charge Management

Defining Number Range Intervals for Freight Order Management

4.0 December 2013

Updated for SAP Transportation Management 9.1

Important SAP Notes

You must read the following SAP Notes before you start using this test scenario. These SAP Notes contain the most recent corrections required to test the scenario.

Make sure that you have the current version of each SAP Note, which you can find on SAP Service Marketplace at http://service.sap.com/notes.

SAP Note Number Description

1738013 TM: Integration with ERP Enhancement Packages

SAP 8

1 The Scenario

Geography

The International Outbound Transportation scenario describes the freight forwarding process from a customer in the United States to Germany by sea.

In this scenario, a U.S. customer delivers parts to the forwarders warehouse at Newark, New Jersey. The containers are to be delivered by sea to a consignee located in Duesseldorf, Germany.

Stages in the International Outbound Transportation Scenario

The following organizational structures and document types are used by default and must be changed to customer-specific organizational structures as required.

Company code 3000

3050

Controlling area 2000

Plant 3000

3050

Purchasing organizations 3000

3050

Sales organization 3000

3050

Distribution channel 10

14

Division 00

Sales document type OXXX

SAP 9

About this Document

Some settings in this guide can be copied from the existing SAP ERP configuration. In particular, SAP ERP Customizing settings can be reused for the following:

Enterprise structure definition and relevant assignments

Financial Accounting

Controlling

If you require a scenario-specific enterprise structure, we recommend that you copy the existing, standard configuration settings (such as Country Template for Company Codes incl. G/L Accounts) and change them as necessary (such as addresses). This scenario refers to an enterprise structure with two company codes assigned to one controlling area.

Business system groups, logical systems, RFC connections, and system connections used throughout this guide are examples only. Replace these with your own data.

This guide also assumes the use of Business Add-Ins (BAdIs), which add a prefix or suffix to master data objects transferred from SAP ERP to SAP TM (see SAP Note 458914). An overview of the prefixes and suffixes used is provided in the table below:

Business Object Prefix Suffix

Carrier CA- None

Customer CU- None

Plant PL- None

Shipping Point SP- None

Supplier SU- None

System None @ERP001

Shipping point name in SAP ERP: 1200

Shipping point name in SAP TM: SP1200@ERP001

If you have not implemented the corresponding BAdI in your system, the names of the objects are not changed.

Prerequisites

Before you begin to configure the International Outbound Transportation scenario, see the

following guides in SAP Solution Manager under SAP Transportation Management

Configuration Structures Basic Settings for SAP TM 9.1 :

Basic Settings for SAP TM

SAP 10

Integration of SAP TM with ERP

Integration of SAP TM and SAP Event Management

Output Management Configuration Guide

Visual Business Configuration with SAP TM

System Prerequisites

Your SAP ERP system must be configured to run the following processes:

SD: Order-to-cash process:

o Sales order entry

o Delivery creation

o Posting goods issue

o Billing document creation

o Transfer to accounting

MM: Purchase order process:

o Purchase order entry

o Posting goods receipt

o Invoice document creation (ERS settlement)

o Transfer to accounting

FI/CO

o Supporting the processes listed above

o Country-specific legal requirements (such as tax calculation)

SAP 11

2 ERP Master Data

SAP 12

2.1 Creating Customers in SAP ERP

In this procedure, you create customers in SAP ERP. You create business partners in their various roles (for example, shipper, consignee, payer) as customers in the system.

Prerequisites

You have defined appropriate account groups.

Procedure

Creating Shippers

1. On the SAP Easy Access screen for SAP ERP, choose Logistics Sales and

Distribution Master Data Business Partner Customer Create Complete or call

transaction XD01.

2. Enter the following data and press Enter:

Field Entry

Account Group TM1: Customer Account Group

Customer IOT-CU-01

Company Code 3000

Sales Organization 3000

Distribution Channel 10

Division 00

3. Choose OK.

4. Under General Data, go to the Address tab page and enter the name and address data as follows:

Field Entry

Customer Number IOT-CU-01

Name New York Abrasives

Search Term IOT-CU-01

Address 450 W.33 Street, New York, NY, US 10001.

5. Press Enter.

The Timezone screen appears.

6. Enter the following data:

SAP 13

Field Entry

Time Zone EST

Language EN

Telephone (212)210-5869

E-Mail

Maintain the region data within the address data.

7. Choose Company Code Data.

8. Go to the Account Management tab page.Enter the following data:

Customer Number Reconciliation Account

IOT-CU-01 140000

9. Choose Sales Area Data.

10. Go to the Sales tab page.Enter the following data:

Customer Number Sales Office Sales Group Customer Pricing Procedure

IOT-CU-01 3000 301 1

11. Go to the Shipping tab page.Enter the following data:

Customer Number Shipping Conditions

IOT-CU-01 01

12. Select the Billing Documents tab page.Enter the following data:

Customer Number Invoicing Dates Terms of Payment Taxes (for all Countries in the Table)

IOT-CU-01 US 0001 0

13. Save your entries.

If you have not yet made account group functional assignments, you may get the

message Data is incomplete when you try to save your entries. If so, you

need to assign the partner functions (column PF) mentioned in the table manually on the Partner Functions tab page. To do so, proceed as follows:

1. In Customizing for SAP ERP, choose Sales and Distribution Basic

Functions Partner Determination Set up Partner Determination .

SAP 14

2. Double-click Set up Partner Determination for Customer Master.

3. Expand the Partner Determination Procedure node in the hierarchical table on the left-hand side.

4. Double-click the Account Groups Function Assignment node in the hierarchical table on left-hand side.

5. Create a new entry.

6. In the table, under Partn.Funct., enter all partner functions that you find in the table that is open while you create customers in column PF (most

likely SP, BP, PY and SH).

7. In the same table, under Account Group, enter 0001 for all your partner

functions.


9. To create this customer in the second company code, return to the customer creation screen and repeat the process using the following data:

Field Entry

Account Group TM1: Customer Account Group

Customer IOT-CU-01

Company Code 3050



Division 00

10. Choose Continue.

11. Choose Save.

Creating Consignees

1. On the SAP Easy Access screen for SAP ERP, choose Logistics Sales and

Distribution Master Data Business Partner Customer Create Complete or call

transaction XD01.


Field Entry

Account group TM1: Customer Account Group

Customer IOT-CU-02

Company code 3000

SAP 15



Division 00

3. Press Enter:

4. Under General Data, select the Address tab page.Enter the following data:

Field Entry

Customer Number IOT-CU-02

Name Lebensmittelgrosshandlung Meyer

Search Term IOT-CU-02

Address Lichtstr. 69-71, 40235 Dsseldorf, DE, Region 05

5. Press Enter.


Field Entry

Time Zone CET

Language DE

Telephone 0211-239573

E-Mail

7. Choose Company Code Data, and, select the Account Management tab page. Enter the following data::

Customer Number Reconciliation Account

IOT-CU-02 140000

8. Choose Sales Area Data, and go to the Sales tab page.Enter the following data:

Customer Number Customer Pricing Procedure

IOT-CU-02 1

9. Go to the Shipping tab page.Enter the following data:

Customer Number Shipping Conditions

IOT-CU-02 01

10. Go to the Billing tab page.Enter the following data:

Customer Number Invoicing Dates Taxes (for all countries in

SAP 16

the table)

IOT-CU-02 01 0


SAP 17

2.2 Defining Vendor Master Data

In this procedure, you create vendor master data. You should assign carriers to a different account group to other suppliers.

Procedure

1. On the SAP Easy Access screen for SAP ERP, choose Logistics Materials

Management Purchasing Master Data Vendor Central Create or call

transaction XK01.

2. Create the vendors assigned to the American purchasing organization according to the tables below:

Vendor External Vendor Number

Vendor IOT-CR-01 / IOT-CR-02

Company Code 3000

Purch. Organization 3000

Account Group 0005

Addresses

Vendor Number Name Search Term Address

IOT-CR-01 P&G Truck Lines P&G Truck Lines

4075 Windgap

Ave, 15204,

Pittsburgh, US,

Region PA

IOT-CR-02 Global Cargo

Systems Global Cargo

Systems

303 Port Jersey

Blvd, 07305,

Jersey City, US,

Region NJ

3. Press Enter after specifying the country and regions above.

4. Enter CST as the time zone (you may have to go back to the Address screen by choosing

Previous Screen at the top left of the screen).

5. Go to the Accounting Information Accounting screen. Enter the following data:

Accounting Information Accounting

Vendor Number Reconciliation Account Cash Management Group

IOT-CR-01 160000 A1

IOT-CR-02 160000 A1

Purchasing Data

Vendor Number Order Currency Terms of Payment GR Based Inv. Verif.

SAP 18

IOT-CR-01 USD 0001 Select this checkbox

IOT-CR-02 USD 0001 Select this checkbox


After you have created the vendors in US, create the vendors assigned to the European purchasing organization according to the tables below:

1. On the SAP Easy Access screen for SAP ERP, choose Logistics Materials

Management Purchasing Master Data Vendor Central Create or call

transaction XK01.

2. Create the vendors assigned to the European purchasing organization according to the tables below:

Vendor External Vendor Number

Vendor IOT-CR-03

Company Code 3050

Purch. Organization: 3050

Account Group 0005

Addresses

Vendor Number Name Search Term Address Time Zones

IOT-CR-03 Europa

Express Europa

Express

Oranjelaan

46, 3181 HK

Rozenburg

Zh, NL

CET

Accounting Information

Vendor Number Reconciliation Account Cash Management Group

IOT-CR-03 160000 A1

Purchasing Data

Vendor Number Order Currency Terms of Payment GR Based Inv. Verif.

IOT-CR-03 EUR 0001 Select this checkbox


SAP 19

3 SAP TM Basic Configuration

Before transferring master data from SAP ERP to SAP TM, you need to define the settings detailed in the following chapters.

SAP 20

3.1 Creating Models and Active Versions

In this procedure, you create models and active versions.

In SAP Transportation Management, specific master data objects need to be assigned to an active version and model for transportation planning purposes. The following objects need to be assigned:

Transportation lanes

Locations

SAP Transportation Management performs this assignment automatically in the background, when the system creates the master data.

The system creates the active version and model exactly once. The active version and model does not need to be and cannot be created more than once. The system displays an error message if an active version and model exists and you try to create a new one.

Procedure

1. In Customizing for SAP Transportation Management, choose Transportation

Management Master Data Create Active Version and Model .

2. Create active model 000.

SAP 21

4 Transferring Master Data to SAP TM (CIF)

SAP 22

4.1 Creating Integration Models

In this procedure, you create integration models, which specify which data objects are to be selected from the total dataset in SAP ERP for the transfer to SAP TM. You do not need all available master data and transaction data in SAP ERP for planning in SAP TM.

To create the integration model, first mark the object types (for example, customer masters) to be selected on the Create Integration Model selection screen. Next, you select specific selection criteria that further restrict the object types you have already selected.

For this scenario you need to transfer the following master data types from SAP ERP to SAP TM:

Customer master

Carriers

You do not need to transfer plants in the Logistics Service Provider (LSP). However, the transfer of plants is required for the delivery scenario.

The transfer of transaction data is not required.

In SAP TM, you create business partners and/or locations based on the settings when activating the integration models (see Activating Integration Models [Page 25]).

Working with Variants

Since the system does not save the selection options you make when creating an integration model, you have to save the settings as a variant on the selection screen. By working with variants you can reuse the settings you have saved whenever you want. If you want to re-create an integration model at a later point in time, you can call up the required variant by choosing the Select Variant symbol in the toolbar at the top of the selection screen.

Integration Model Versions

If you regenerate an integration model, the system automatically generates a new version of this model. Different versions of an integration model are distinguished by their date and time of creation, as well as by the filter objects that they contain. You can create as many versions of an integration model as you wish. However, only one version may be active at one time.

Changing an Integration Model

We recommend that you change an existing variant of the integration model, generate a new

version using transaction CFM1, and then delete the variant.

Structure of an Integration Model

The structure of an integration model influences performance. When it integrates transaction data, the system checks whether the data concerned is contained in the active integration model. At the same time, the system loads and interprets all active integration models for the object type concerned to determine any target systems that may be affected. The greater the number of integration models per object type, the longer the runtime for the determination for target systems.

SAP 23

For performance reasons, we recommend that you use only one object type for each integration model.

Prerequisites

You have completed the Customizing and default settings for integration in both SAP TM and SAP ERP.

You have maintained the relationship between the source and target system in both systems.

Procedure

Create Integration Model for Customers

1. 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 call transaction CFM1.

2. Define an integration model with the following data:

Model Name Logical System APO Application

IOT-IM-001 Logical system of the target TM System as defined in Core Interface Settings in SAP ERP (for example, TM1CLNT001).

Customers

3. In the Material Independent Objects screen area, select Customers.

4. Choose Special Restrictions.

A selection screen for customers appears.

5. Select the customers representing your shippers and consignees (IOT-CU-01, IOT-CU-

02).

6. Choose Execute to close the customer selection screen.

7. Set the Create Loc/BP indicator to 2.

8. Save the Create Integration Model screen to create a selection variant for your integration model.

9. Name the variant IOT-IM-001 IOT: Customer and save again.

10. Choose Execute to create the integration model.

11. Choose Generate IM.

12. Choose Back.

Create Integration Model for Carriers



Integration Model Create or call transaction CFM1.

SAP 24

2. Define an integration model with the following data:

Model Name Logical System APO Application

IOT-IM-002 Logical system of the target SAP TM System as defined in Core Interface Settings in SAP ERP (for example, TM1CLNT001).

Carriers

3. In the Material Independent Objects screen area, select the Vendors checkbox.

4. Choose Special Restrictions. A selection screen for vendors appears.

5. Either directly select the vendors representing your carriers (IOT-CR-01, IOT-CR-03,

IOT-CR-02) or select them with the account group 0005.

6. Choose Execute to close the vendor selection screen.

7. Set the Create Loc/BP indicator to 1.

8. Save the Create Integration Model screen to create a selection variant for your integration model.

9. Name the variant IOT-Carriers and save again.

10. Choose Execute to create the integration model.

11. Choose Generate IM.

12. Choose Back.

SAP 25

4.2 Activating Integration Models

In this procedure, you activate integration models.

Activating an integration model causes an initial transfer of master data from SAP ERP to SAP TM. The integration models to be activated are compared with the integration models that are already active. In this way, the transfer restricts itself to differences. In other words, the system transfers only data for filter objects that are not contained in any active integration models.

To retransfer all data records, you have to deactivate and then reactivate all active integration models.

When activating the integration model, you must define whether you want to create a business partner, a business partner and a location, or only a location in SAP TM. Business partners are necessary for the commercial part of the business, whereas locations are necessary for planning and executing transportation. This means that whenever cargo needs to be picked up or delivered, a location is necessary. In this scenario, you create business partners and locations for the customers. Since the carriers are external, you only create business partners. If the distances and transportation times from the depot of the carrier are important, you need to create a location for the carrier.

Procedure

Activate Integration Model for Customers



Integration Model Activate or call transaction CFM2.

2. Make the following settings:

Field Value Remark

Model IOT-IM-001 None

Logical System See remark Logical system of the target SAP TM System as defined in Core Interface Settings in SAP ERP.

APO Application Customers None

3. Choose Execute.

The selection screen displays the available integration models for the model name you have specified.

Versions: If several integration models exist with the same name, they are displayed in chronological order (according to date and time).

4. Activate the required model by double-clicking it or by choosing Active/Inactive.

An OK icon displayed to the left of the model generation date and time shows that the integration model has been activated.

SAP 26

If you want to deactivate the integration model, repeat the above procedure and ensure that the OK icon is no longer displayed.

5. Choose Start to begin the data transfer.

The system transfers the data in the background.

6. You can use Check to carry out a consistency check on the status of the integration model.

The system tests all active models, including those models scheduled for activation, but excluding those models scheduled for deactivation.

Activate Integration Model for Carriers



Integration Model Activate or call transaction CFM2.

2. Make the following settings:

Field Value Remark

Model IOT-IM-002 None

Logical System See remark Logical system of the target SAP TM System

APO Application Carriers None

3. Choose Execute.

The selection screen displays the available integration models for the model name you have specified.

Versions: If several integration models exist with the same name, they are displayed in chronological order (according to date and time).

4. Activate the required model by double-clicking it or by choosing Active/Inactive.

An OK icon to the left of the model generation date and time shows that the integration model has been activated.

If you want to deactivate the integration model, repeat the above procedure and ensure that the OK icon is no longer displayed.

5. Choose Start to begin the data transfer.

The system transfers the data in the background.

6. You can use Check to carry out a consistency check on the status of the integration model.

The system tests all active models, including those models scheduled for activation, but excluding those models scheduled for deactivation.

SAP 27

5 Creating Organizational Model in SAP TM

For creating and maintaining organizational units, the HR functionality of the organizational plan has been reused in SAP TM 2008.

You use the organizational model to model the sales organization, purchasing organization and transportation execution organization. You use the organizational model to assign the responsible organizational units to transportation documents like a shipment request, a tour, a shipment order, and so on. This association of the order to an organizational unit is necessary to allocate the costs and profits of the order to a business unit. It is also necessary for profit analysis of various groups/organizations of the LSP. It helps analyze the costs that the company is incurring for various TSPs, routes, customers, and so on. The analysis can also lead to better demand forecasting.

You need to maintain the organizational model in the SAP TM system, since it is not transferred from the organizational units in SAP ERP.

SAP 28

5.1 Creating Sales Organizations, Sales Offices, and Sales Groups

In this procedure, you create sales organizations, sales offices, and sales groups. The organizational model and staffing reflect the enterprise structure of the company. You can create, assign, and staff organizational units.

The system reuses the HR functionality of the organizational plan to create and maintain organizational units.

Prerequisites

The system automatically creates a business partner for each organizational unit, which means that you have to configure the internal number assignment in Customizing for SAP Transportation

Management. You do so by choosing Cross-Application Components SAP Business Partner

Business Partner Basic Settings Number Ranges and Groupings Define Number Ranges

.

Procedure

Creating Sales Organization

1. In SAP NetWeaver Business Client (NWBC), choose Master Data Organization

Create Organization and Staffing .

2. In the dialog box, set the validity period from to 31.12.9999, and press Enter.

3. On the Basic Data tab page, in the Organizational Unit fields, enter IOT-SORG-1 and

Simon Express Corporation.

4. On the Org. Data tab page, choose Create.

5. For Organizational Unit Function, enter 4, and for Organizational Unit Role, enter 1.

6. Go to the Address tab page and enter the following data:

Field Value

House No./Street Industrial Parkway 4023

City Philadelphia

Postal Code 19088

Country US

Region PA


A business partner number is automatically generated for the sales organization and is visible in the Org. Data tab.

SAP 29

8. Repeat steps 3 to 7 to create a second sales organization in Europe: IOT-SORG-2: Deutsche bersee AG based in Germany. Enter the following data:

Field Value

House No./Street Martinistrasse 23

City Bremen

Postal Code 28201

Country Germany

Creating Sales Office

1. In NetWeaver Business Client (NWBC), choose Master Data Organization Edit

Organization and Staffing .

2. Select the entry IOT-SORG-2: Deutsche bersee AG.

3. Choose Create.

A dialog box appears.

4. Double-click Is line supervisor of.

5. On the Basic Data tab page, enter the abbreviation IOT-SAOFF-1 and the name Sales

Office Bremen in the Organizational unit field.


7. For Organizational Unit Function, enter 4, and for Organizational Unit Role, enter 2.

8. On the Address tab page, enter the address Martinistrasse 23, 28201 Bremen, Germany, Bremen.


10. Repeat the procedure and create a second sales office IOT-SAOFF-2: Sales Office Duisburg assigned to the sales organization Deutsche bersee AG in Germany.

The address for this is: Vodkaale 82, 47051, Duisburg, Germany, Nordrhein-Westphalia.

11. Repeat the procedure and create the sales offices IOT-SORG-1: Simon Express Corporation, IOT-SAOFF-3 Sales Office Chicago and IOT-SAOFF-4: Sales Office Boston.

Creating Sales Group

1. In NetWeaver Business Client (NWBC), choose Master Data Organization Edit

Organization and Staffing .

2. Select the sales office IOT-SAOFF-3 Sales Office Chicago of IOT-SORG-1: Simon Express Corp.

3. Choose Create.

A dialog box appears listing the available relationships.

SAP 30

4. Double-click Is line supervisor of.

5. Enter the description for the new organizational unit: IOT-SGRP-1: Sales Group

Chicago.


7. In the Organizational Unit Function field, enter 4, and in the Organizational Unit Role

field, enter 3.

8. On the Address tab page, enter the address.


10. Repeat the procedure and create another sales group IOT-SGRP-2 Sales Group Detroit for sales office IOT-SAOFF-3 Sales Office Chicago.

SAP 31

5.2 Creating Purchasing Organization

In this procedure, you create purchasing organizations. You need purchasing organizations, in addition to purchasing groups, for subcontracting.

For this scenario you need to define the following organizational units:

Purchasing US

Field Value

Abbreviation of Organizational Unit IOT-PORG-1

Name of the Organizational Unit Purchasing US

Supervisor Of Purchasing Group US East

Organizational Unit Function 2 (Purchasing)

Organizational Unit Role 1 (Organization)

Address 4023 Industrial Parkway, PA 19088 Philadelphia, US

Purchasing Group US East

Field Value

Abbreviation of Organizational Unit IOT-PGRP-1

Name of the Organizational Unit Purchasing Group US East

Supervisor Of Not applicable


Organizational Unit Role 3 (Group)


Purchasing Europe

Field Value

Abbreviation of Organizational Unit IOT-PORG-2

Name of the Organizational Unit Purchasing EU

Supervisor Of Purchasing group EU



Address Martinistrasse 23, 28201 Bremen

SAP 32

Purchasing group Europe

Field Value

Abbreviation of Organizational Unit IOT-PGRP-2

Name of the Organizational Unit Purchasing group EU




Address Martinistrasse 23, 28201 Bremen

Procedure

1. In SAP NetWeaver Business Client (NWBC), choose Master Data Organization


2. Enter a valid period for your organizational unit.

3. On the Basic Data tab page, in the Organizational unit fields, enter the IOT-PORG-1

Object Abbreviation and Purchasing US Object Name.

4. On the Org. Data tab page, choose Create and define the Organizational Unit Function and Organizational Unit Role according to the above table. In the Org. ID field, enter the abbreviation of the organizational unit as specified in the above table.

5. On the Address tab page, define the Main address of the organization according to above table.


7. Create the purchasing group IOT-PGRP-1 Purchasing Group US East as a

subordinate unit of the purchasing organization IOT-PORG-1 Purchasing US. To do this, select the purchasing organization IOT-PORG-1 Purchasing US and choose Create.

8. Choose the Is line supervisor of relationship.

9. On the Basic Data tab, in the Organizational unit fields, enter the IOT-PGRP-1 Object

Abbreviation and Purchasing Group US East Object Name.

10. On the Org. Data tab page, choose Create and define the Organizational Unit Function and Organizational Unit Role according to the above table.

11. On the Address tab page, define the Main address of the organization according to the above table.


13. Create the organizational units IOT-PORG-2 Purchasing EU and IOT-PGRP-2 Purchasing Group EU in the same way as IOT-PORG-1 Purchasing US and IOT-PGRP-1 Purchasing Group US East with the data from the above tables.

SAP 33

14. When you save the organizational units, the corresponding organizational unit number is automatically generated and is visible on the Org. Data tab page for the external ID of the organizational unit.

SAP 34

5.3 Creating Planning and Execution Organizations

For transportation planning and execution, you have to define planning and execution groups. These represent the different organizational units responsible for land, sea or air freight in different geographical regions.

Create planning and execution groups with the following data:

Point US-Land

Field Value

Abbreviation of Organizational Unit IOT-TPP-1

Name of the Organizational Unit Transportation Plan. Point US-Land

Supervisor Of IOT-TPGR-1

Organizational Unit Function 13 (Planning and Execution)



Group US-Land

Field Value

Abbreviation of Organizational Unit IOT-TPGR-1

Name of the Organizational Unit Transportation Plan. Group US-Land





Point US-Sea

Field Value


Name of the Organizational Unit Transportation Plan. Point US-Sea




SAP 35


Group US-Sea

Field Value


Name of the Organizational Unit Transportation Plan. Group US-Sea





Point EU-Land

Field Value


Name of the Organizational Unit Transportation Plan. Point EU-Land




Address Martinistrasse 23, 28201 Bremen, Bremen

Group EU-Land

Field Value


Name of the Organizational Unit Transportation Plan. Group EU-Land




Address Martinistrasse 23, 28201 Bremen, Bremen

SAP 36

Procedure

1. In the NetWeaver Business Client (NWBC), choose Master Data Organization


2. Enter a valid period for your organizational unit.

3. On the Basic Data tab page, in the Organizational unit fields, enter the IOT-TPP-1

Object Abbreviation and Transportation Plan. Point US-Land Object Name.

4. On the Org. Data tab page, choose Create and define the Organizational Unit Function and Organizational Unit Role according to the above tables.

5. On the Address tab page, define the Main address of the organization according to above tables.

6. Save your entries. An organizational unit number is generated, along with the corresponding business partner number, which is visible in the Org. Data tab page of the organizational unit.

7. Select the transportation planning point IOT-TPP-1 and choose Create.

8. Select the Is line supervisor of relationship.

9. On the Basic Data tab page, in the Organizational unit fields, enter the IOT-TPP-1

Object Abbreviation and Object Name Transportation Plan. Group US-Land.

10. On the Description tab page, choose Create and define the Organizational Unit Function and Organizational Unit Role according to the above tables.

11. On the Address tab page, define the Main address of the organization according to above tables.

12. Save your entries. An organizational unit number is generated, along with the corresponding business partner number, which is visible in the Org. Data tab page of the organizational unit.

13. Create the remaining transportation planning points and transportation planning groups with the data in the above tables using the same procedure.

SAP 37

6 Defining a Transportation Network

SAP 38

6.1 Defining Transportation Modes

In this procedure, you define a transportation mode.

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management Transportation

Management Master Data Transportation Network Transportation Lane Define

Transportation Mode .

2. Create the following entries if required:

Transportation Mode Code Transportation Mode MtrCat (Dangerous Goods) TModCat

03 Sea 4 Sea

01 Road 1 Road

04 Inland Waterway 3 Sea

02 Rail 2 Rail

05 Air 5 Air


SAP 39

6.2 Defining Means of Transport

A means of transport defines the following:

Own/detailed/external resources

GIS level and average speed

Optimizer costs

You subsequently assign a means of transport to a vehicle resource in the SAP TM master data.

Procedure

1. In Customizing for SAP Transportation Management, choose SCM Basis Master

Data Transportation Lane Maintain Means of Transport .

2. Check, and if required, create the following entries:

Field Value

Means of Transport IOT_SEA IOT_FTLUS IOT_FTLEU

MTr Description IOT: Sea transportation

IOT: External

FTL truck US IOT: External

FTL truck EU

Transportation Mode SEA ROAD ROAD

Multires. Not relevant Select this checkbox Select this checkbox

No. Res. Not relevant Not relevant Not relevant

Low/Medium/High Average Speed

Not relevant Not relevant Not relevant

Average Speed 300 80 80

Factor Not relevant 1 1

Schedule Select this checkbox Not relevant Not relevant

YourOwnMTR Not relevant Not relevant Not relevant

GIS Quality uncheck uncheck uncheck

Since the current scenario setup does not use a geographical information system (GIS), you must enter a factor and an average speed. If you have a connection to a GIS provider, you can select the GIS-Quality attribute and the three different average speeds.

When you save, the system may display a popup stating that the IGS or GIS tool is currently unavailable. This message is intended as information only and can be ignored.

SAP 40

6.3 Creating Locations for Warehouses and Seaports

Airports, seaports, railway stations, and so on, are modeled as locations in the TM system. Locations are necessary when cargo needs to be picked up from, delivered to or is being transshipped through that location.

In this scenario, you do not create business partners for warehouses and seaports, as the freight forwarder is not billed by the ports directly but by the warehousers and container shipping lines.

Naming conventions: you create the seaports using the UN/Locodes as location names.

If you have not implemented the Business Add-In (BAdI) APOCF001_TYPESYSDIF to create

business partners, you must create these business partners manually. For information about automatic creation of business partners, see SAP Note 1410353.

Procedure

1. In SAP Netweaver Business Client for SAP TM, choose Transportation Management

Master Data Transportation Network Locations Define Location .

2. Create locations as follows:

Location Name

Location Type

Description Address BP

IOT_USNEK 1030 Port Newark 215 Marsh St, Newark, NJ 07114,

Region NJ, US

(973)

IOT_NLRTM 1030 Port Rotterdam

222 Moezelweg, LS

Rotterdam -

Europoort,3198

LS, Region 12,

Netherlands, 0181

IOT_USSEC 1170 Simon Express

Corporation

Warehouse

7679 Thornton

Ave. Newark, NJ,

US. 94539

Maintain the region data within the address data.

SAP 41


SAP 42

6.4 Defining Transportation Zones

Transportation zones are used either for modeling geographic regions (such as countries) or for defining logical groupings of locations (for example, ports). Transportation zones can be used for modeling the transportation network for Transportation Charge Management, or they can serve as selection criteria for dispatching.

Procedure


Master Data Transportation Network Transportation Zone Define Transportation

Zone .

2. Choose Create and define the following zone:

Zone Zone Type Description

IOT-US Region Zone U.S.A.

3. Choose Continue.

4. On the tab page Zone - Region, choose Create.

5. Define the Country for your zone as US.


7. Define the following transportation zones in the same way:

Zone Zone Type Description Zone - Region Remark

IOT-EU Region Zone Europe Countries DE and NL

Not relevant

IOT-EU-DE Region Zone Germany Country DE Not relevant

IOT-EU-NL Region Zone Netherlands Country NL Not relevant

IOT-US-NY Region Zone State of New York

Country US and

region NY

Optional

IOT-US-NJ Region Zone State of New Jersey

Country US and

region NJ

Optional


SAP 43

6.5 Defining a Transportation Zone Hierarchy

You need a transportation zone hierarchy to correctly determine the geography relevant to shipping (transportation zones and relevant transportation lanes).

Procedure

1. In SAP Netweaver Business Client for SAP TM, choose Master Data Transportation

Network Transportation Zone Define Transportation Zone Hierarchy .

2. In the Hierarchy group box, enter RELH_ZONE in the Name field.

3. Enter RELH_ZONE as the hierarchy structure name.

4. Enter 007 (Transportation Zone) as the object type and 04 (Extended Hierarchy) as the

structure category

5. Choose Create.

6. In the Hierarchy Description field, enter TM Standard Hierarchy.


SAP 44

6.6 Maintaining a Transportation Zone Hierarchy

You must maintain a transportation zones hierarchy to organize your locations in such a way that you can run vehicles from the start location to the destination location via hubs, ports or transshipment locations. Furthermore, if you do not maintain the transportation zone hierarchy correctly, you are not able to preselect the right vehicles as defined in your planning profile.

You create the transportation zone hierarchy with the following data:

Hierarchy Has as Subordinate

RELH_ZONE IOT-EU

IOT-US

IOT-US IOT-US-NY

IOT-US-NJ

IOT-EU IOT-EU-DE

IOT-EU-NL

Procedure


Master Data Transportation Network Transportation Zone Define Transportation

Zone Hierarchy .

2. In the Hierarchy group box, enter RELH_ZONE in the Name field.

3. In the Hierarchy Structure group box, enter RELHS_ZONE in the Name field.

4. Choose Change.

5. In the lower screen area, in the hierarchy tree, double-click RELH_ZONE.

6. In the Hierarchy Fast Entry group box on the top right-hand side of the screen,

RELH_ZONE appears in Hierarchy Node field.

7. Enter IOT-EU and IOT-US in the Transportation Zone column.

8. Save your entries. Agree to update the hierarchy tree.

9. In the lower screen area, the updated hierarchy tree, double-click IOT-US.

10. In the Hierarchy Fast Entry group box on the top right-hand side of the screen, IOT-US

appears in the Hierarchy Node field,

11. Make the following entries in the Transportation Zone column:

o IOT-US-NJ

o IOT-US-NY

12. Save your entries. Agree to update the hierarchy tree.

SAP 45

13. Repeat steps 9 to 12 for IOT-EU, assigning IOT-EU-DE and IOT-EU-NL.

SAP 46

6.7 Checking BP Type for Transportation Service Providers

In this scenario, you transfer the transportation service providers from ERP via the core interface (CIF) to SAP TM and convert them into a business partner of type Organization. To do this, you need to define transportation service providers as business partners with the role Carrier. The transportation service provider selection and tendering function only contain the transportation service provider if you have assigned this role to it.

To be able to send e-mails to the transportation service provider within the tendering process, you need to maintain an e-mail address in the business partner representing the transportation service provider.

Procedure

1. In SAP NetWeaver Business Client (NWBC), choose Master Data General Define

Business Partner .

2. Search for your business partner representing the carriers and CSL by searching by

business partner number with the search terms IOT*CR*.

3. For each business partner (IOT-CR-01 to IOT-CR-03) check whether the role Carrier has been assigned by double-clicking the business partner in the results list. You can see the assigned role in the field below the BP Number in the business partner header data.

4. If the designated role is not Carrier, switch to Change mode and select CRM010 Carrier (Maintained) as the new role for the business partner.

5. Navigate to the Address tab and enter the e-mail address of the transportation service provider (or your business e-mail address) on the subscreens Communication and Address-Independent Communication.

6. Choose Email as the Standard Communication Method.


SAP 47

6.8 Defining Transportation Lanes

Transportation lanes are used to model the transportation network. A transportation lane represents a directed route that can be used to transport products from the source to the destination. Transportation lanes may be defined between locations (direct lanes), between transportation zones and locations, within transportation zones (intrazone lanes) and between transportation zones.

You can use intrazone lanes if all locations within a zone can be reached from all other locations within the same zone using certain means of transport, for example, trucking for the precarriage within a certain region.

You can use direct lanes to define connections between specific locations. In contrast to earlier releases of APO TP/VS, you do not need to define transportation lanes if you have booking orders or schedules between certain locations. Booking orders and schedules serve as transportation lanes in SAP TM.

The transportation lane defines which means of transport (for example, IOT_SEA, IOT_FTLUS, and so on) you can use for transportation in which geographic region.

In this scenario, you only need to create intrazone lanes for trucking in the US and in Europe, as the booking order for sea freight serves as a transportation lane itself.

Procedure

1. In SAP NetWeaver Business Client (NWBC), choose Master Data Transportation

Network Transportation Lanes Define Transportation Lanes .

2. On the Tr.Lane tab page, enter the start transportation zone IOT-US-NJ and destination

location IOT_USNEK and choose Create.

3. Create a transportation lane with the following data by clicking the Creation of a New Entry in the Means of Transport screen area:

Field Value

Means of transport IOT_FTLUS

Start Date 01.01.2008

End Date 31.12.2099

Relevant to Carrier Selection Select this checkbox

Priority/Costs Priority

Cost Origin Costs calculated by Component TCM

Contin. Move Type No Continuous Move

4. Choose (Copy and close). If a message appears prompting you to create a proposal, choose Yes.


SAP 48

6. Choose MTr. and choose Create to assign the carriers in the section below (Carrier for Means of Trans.).


Field Value

BP Number IOT-CR-01

Priority 1

8. Choose (Copy and close).


10. Define the following intrazone lane in the same way:

Field Value

Start Location IOT_NLRTM

Dest.Transportation Zone IOT-EU-DE

Means of transport IOT_FTLEU

Start Date 01.01.2010

End Date 31.12.2099

Relevant to Carrier Selection Select this checkbox

Priority/Costs Priority

Cost Origin Costs calculated by TCM component

Cont. Move Type No Cont. Move

Field Value

BP Number IOT-CR-03

Priority 1

SAP 49

6.9 Assigning Transshipment Locations

To enable the use of multimodal transportation, you have to define your transportation network in terms of which customers, suppliers, or regions serve which airports, seaports, rail stations or which hubs and terminals of your own organization. The transshipment location is the location where unloading and loading from one mode of transport or vehicle to another means of transport or vehicle takes place.

The assignment can be done one of the following ways:

Assignment of single locations (customers, suppliers, and so on) to one transshipment location

Assignment of a transportation zone (geographical region or logical grouping of locations) to one transshipment location.

Multiple assignments of a location to several transshipment locations are possible.

Procedure

1. In SAP Netweaver Business Client for SAP TM, choose Master Data Transportation

Network Locations Assign Transshipment Location .

2. Choose Assign Transshipment Locations.

3. Create the following entries:

Location Selection Transshipment Location Selection

IOT_USSECC (Location) IOT_USNEK

IOT-EU-DE (Zone) IOT_NLRTM


5. Choose Back and check in the overview table that both locations are assigned to the designated transshipment location.

SAP 50

7 Defining Equipment Groups and Equipment Types

You use equipment groups and equipment types to describe the equipment modeled as transportation units.

You can define the equipment group according to UN/EDIFACT Standard, segment EQD Equipment Details, 8053 Equipment type code qualifier.

The equipment type can be defined according to UN/EDIFACT Standard, segment EQD Equipment Details, 8155 Equipment size and type description code. In this scenario, you define the equipment type according to DIN EN ISO 6346, January 1996.

Procedure


Management Master Data Resources Define Equipment Groups and Equipment

Types .

2. Create the following equipment groups according to UN/EDIFACT Standard, segment EQD Equipment Details, 8053 Equipment type code qualifier by selecting the Equipment Group folder and choosing New Entries.

Equipment Group Description

AK Aircraft

AJ Flat Rack

AM Refrigerated Container

BX Boxcar enclosed railway goods wagon

CH Chassis wheeled carriage for containers

CN Container

RF Flat Car railway wagon without raised sides

RR Rail Car

TE Trailer a vehicle without motive power

UL ULD an aircraft container or pallet


4. Access the screen for Equipment Types by selecting the appropriate Equipment Group and choosing Equipment Types in the navigation tree and choosing New Entries.

5. Create the following equipment types according to DIN EN ISO 6346, January 1996. (A definition according to UN/EDIFACT Standard, segment EQD Equipment Details would also be possible, but this is less detailed than the ISO Standard.)

SAP 51

Equipment Group Equipment Type (DIN EN ISO 6346)

Description Remark

CN 22GP 20 STD, general purpose container

General 20 standard general purpose container, specified by size code (22) and group code (GP)

CN 22G0 20' STD, opening at one or both ends

CN 22G1 20' STD, vents in upper part of cargo space

CN 22G2 20' STD, full opening at ends and sides

CN 22G3 20' STD, partial openings at sides

AM 22RE 20 STD reefer container

General 20 standard reefer container, specified by size code (22) and group code (RE)

AM 22R0 20' STD, mechanically refrigerated

AM 22R1 20' STD, mech. refrigerated and heated


SAP 52

8 Waybill Stock

SAP 53

8.1 Defining Waybill Number Stock Types

You use waybill number stock types to create waybill number stocks. You can use these stocks to allocate waybill numbers to house bills of lading.

Procedure


Management Master Data Waybill Stock Define Waybill Number Stock Types .

2. Choose New Entries and create the following stock type if it does not exist:

Stock Type Description TrM Org. Category Digits

HBL House Bill of Lading

03 (Sea) Sales 10

3. Save the entry.

SAP 54

8.2 Defining Waybill Stocks

Procedure

1. In SAP NetWeaver Business Client (NWBC), choose Master Data General

Overview Waybill Stock .

2. Choose the New pushbutton.

3. In the Number Stock Type field, enter HBL and choose Continue.

4. Enter the following values:

Stock ID From Number To Number Valid-From Valid-To

IOT 9000000000 9999999999 31.12.9999

5. Add a new organizational unit ID by choosing the corresponding Insert pushbutton and

enter organizational unit IOT-SORG-1.


SAP 55

9 Freight Unit Building

SAP 56

9.1 Defining Freight Unit Types

Procedure


Management Planning Freight Unit Define Freight Unit Types .

2. Create a new entry with the following data:

Field Value

Freight Unit Type IOT1

Description IOT: FCL FU

Is Default Type Deselect this checkbox

Basic Settings

Freight Unit can be deleted Select this checkbox

Change Controller Settings

Default Strategy DEF_CHACO

Execution Settings Not relevant

Execution Tr. Relevance 3-Execution Tracking with External Event Management

Event Management Settings

Application Object Type ODT30_FU

Last Exp. Event UNLOAD_END

Number Range Settings

Time For Drawing S Draw Number when saving document

Number Range Interval 01

Additional Settings

BW Relevance Select this checkbox

Track Changes Select this checkbox

3. Save the data.


Field Value

Freight Unit Type 0001

SAP 57

Description Freight Unit

Is Default Type Select this checkbox

Basic Settings

Freight Unit can be deleted Select this checkbox

Change Controller Settings

Default Strategy NO_ACTION

Execution Settings Not relevant

Execution Tr. Relevance No Execution Tracking

Number Range Settings

Time For Drawing I Draw Number immediately

Number Range Interval FU

Additional Settings

Track Changes Select this checkbox


SAP 58

9.2 Creating Freight Unit Building Rules

Freight unit building rules (FUBs) define how the system should create freight units based on the forwarding order. In addition, FUBs define the dimensions that are transferred from the forwarding order to the freight unit as capacity requirements for planning.

For this scenario, you need one freight unit building rule:

IOT-FUBR-01: one freight unit per container in the full container load process (FCL)

Procedure

Create Freight Unit Building Rule

1. In SAP Netweaver Business Client for SAP Transportation Management, choose Application Administration Planning General Settings Freight Unit Building Rule

Create Freight Unit Building Rule .

2. Create a new rule with the following data:

General Data

Field Value Remark

ID of FUB Rule IOT-FUBR-01 None

FUB Rule Description FU per container None

Document Type IOT1 Enter the FU type created previously.

FU Building Strategy Consolidate per item None

Process Control Strategy (Advance Settings tab page)

FUB_AUTO None

Incompatibility Settings N/A None

Critical Quantity Pieces None

Item Split Allowed Select this checkbox None

Planning Quantities

Planning Qty UoM of Split Qty Split Qty Rounding Qty

Gross Volume M3 None None

Gross Weight KG None None

Pieces EA 1 1


SAP 59

9.3 Defining Conditions for Determining the FUB Rule

The conditions define when the system applies freight unit building rules.

For this scenario, you create a condition that determines the FUB rule IOT-FUBR-01 for an FCL order. The value of the field Service Level Code in the forwarding order determines this rule.

Procedure

1. On the SAP Easy Access screen for SAP TM (or, alternatively, in NetWeaver Business

Client), choose Application Administration General Settings Conditions Create

Condition .

2. Create a condition with the following General Data:

Condition Name Description Condition Type Origin of Condition

IOT-FUBR-DET-

COND-001 IOT-FUBR-DET-

COND-001 /SCMTMS/FUBR Condition Based on BRFplus

Decision Table

3. Choose Enter.

4. On the Data Access Definition screen, choose Create and enter the following data:

Field Value Remark

Data Object description

Service level code None

Name of BO Used In Condition

/SCMTMS/TRQ Freight units are created based on the forwarding order

Name of BO node

ROOT The field Service LevelC odeis part of the general data of the forwarding order. The condition is based on data of the root of the forwarding order.

BO node field name

TTRANSSRVLVL_CODE Name of the field Service Level Code.

5. Choose Enter.

6. Navigate to the Decision Table tab.

7. Choose Insert New Row.

8. Choose the String node and choose Direct Value Input.

9. Select the Case Sensitive checkbox.

10. Enter the following If statement and choose OK:

If String "matches pattern *FCL*

11. Choose the FUB Rule node and choose Direct Value Input.

SAP 60

12. Maintain the FUB rule as IOT-FUBR-01.

13. Choose OK and save the condition.

14. Maintain the FUB rule condition in the forwarding order type definition.

SAP 61

10 Setting Up Customizing for Settlement Document Types

You can define different settlement document types for different freight orders and define default settlement document types.

The settlement profile consists of a set of parameters, with which you can control how the system creates invoices. If you do not specify a settlement profile, the system uses standard default settings to create settlement documents.

You can also make default assignment of different charge calculation parameters, such as settlement profile, currency, and exchange rate, for the sales and purchasing organization units.

SAP 62

10.1 Defining Freight Settlement Document Types

You can define various types for freight settlement document (FSD) types. You can set a default FSD for each freight order. You should set one type as the default.

Prerequisites

You have defined the number range for the FSD types.

Procedure


Management Settlement Freight Settlement Define Freight Settlement Document

Types .

2. Create new entries with the following data:

Object Name

Value

FSD Type IOT1 IOT2 IOT3

Short Desc.

US Frt.Set.Inland

Trnsp. EU Frt.Set.Inland

Trnsp. Long Haul Ocean

FSD Category

10 Freight

Settlement Document 10 Freight

Settlement Document 10 Freight

Settlement Document

FSD Number Range

01 01 01

Default Wt UoM

KG KG KG

Default Vol UoM

M3 M3 M3

Default Pieces UoM

EA EA EA

Output Profile

/SCMTMS/TOR_INV_PREP /SCMTMS/TOR_INV_PREP /SCMTMS/TOR_INV_PREP

Add. Output Profile

/SCMTMS/SFIR_PRINT /SCMTMS/SFIR_PRINT /SCMTMS/SFIR_PRINT

Dyn Det of output

Deselect this checkbox Deselect this checkbox Deselect this checkbox

Bus. Warehouse

Select this checkbox Select this checkbox Select this checkbox

SAP 63


4. Update the FSD type in the freight order type as the default FSD.

SAP 64

10.2 Defining Settlement Profiles

In this procedure, you can define the profile for creating invoices. The settlement profile consists of a set of parameters with which you can control how the system creates invoices.

You can assign the defined settlement profile to an organizational unit using transaction /SCMTMS/TCM_FASET.

If you do not specify a settlement profile, the system uses standard default settings to create settlement documents.

Prerequisites

You have defined the organizational units.

Procedure


Management Settlement Define Settlement Profile .


Field Value

Settlement Profile IOT_SP_01 IOT_SP_02

Description IOT: Forwarding Settlement Profile

IOT:Freight Settlement

Profile

Data Source Confirmation Data Confirmation Data

Split/Cons. Not relevant FSD_CREAT

Calculation Option A-Copy Fixed Charges and Redetermine Other

A-Copy Fixed Charges

and Redetermine Other

Collective Invoice Deselect Deselect


SAP 65

10.3 Defining General Settings for Charge Calculation

You can make default assignment of different charge calculation parameters, such as settlement profile, currency, and exchange rate, for the sales and purchasing organization units.

Prerequisites

You have defined the organizational units.

Procedure


Management Basic Functions Charge Calculation Basic Settings for Charge

Calculation Define General Settings


Org Unit Settl. Prof. Local Currency

Default Purch. Org. Calculation Profile

IOT-SORG-1

(Sales Org.

US)

IOT_SP_01 USD Blank IOT_CLCPRF

IOT-SORG-2

(Sales org EU)

IOT_SP_01 EUR Blank IOT_CLCPRF

IOT-PORG-1

(Purch. Org

US)

IOT_SP_02 USD ID for IOT-PORG-1

IOT_CLCPRF

IOT-PORG-2

(Purch Org.

EU)

IOT_SP_02 EUR ID for IOT-PORG-2

IOT_CLCPRF

SAP 66

10.4 Defining Charge Calculation Profiles

Procedure

1. In Customizing for SAP TM, choose Transportation Management Basic Functions

Charge Calculation Basic Settings for Charge Calculation Define Calculation Profile

.

2. Choose New Entries to create an entry with the following data:

Field Value

Calculation Profile IOT_CLCPRF

Description IOT: Charge Calculation Profile

Calculation Date Type EET_DATE (Expected End Date of Complete

Carriage)

Calculation Level 1 (Calculation on Header Level)

Freight Agreement Determination Blank

Calculation Sheet Determination Rule Blank

Through Rate Blank

Dimensional Weight Profile I166

Dimensional Weight Condition Blank

Exchange Rate Type Blank

Data Source Actual Route


SAP 67

11 Order Management

SAP 68

11.1 Defining Forwarding Order Type

In this procedure, you specify types of forwarding orders. You can use these types to define certain parameters of the forwarding order that influences how the system processes this business document.

For example, the forwarding order type can determine the number range interval that is used to generate a number of the forwarding order, or it can define whether freight units are created automatically when you save the forwarding order. Furthermore, you can assign profiles, for example planning profile and dangerous goods profile, that determine how follow-up steps such as planning and dangerous goods checks are performed.

You can select and assign the types that you have defined in this procedure on the user interface of the forwarding order in SAP NetWeaver Business Client. You can also specify a default forwarding order type that is used when the forwarding order is created automatically based on electronic data interchange (EDI).

Prerequisites

You have set up the number ranges for the forwarding order types.

Procedure


Management Forwarding Order Management Forwarding Order Define Forwarding

Order Types .

2. Create an entry with the following data:

Field Value

Forwarding Order Type IOT1

Short Description FCL Ocean

Number Range Interval 01

Template No. Range Interval 01

Process Control/Business Object Mode

BW Relevance Select

Same Locations and BPs Select

Transportation mode Sea (03)

Traffic direction 1 (Export)

Shipping Type 3 (FCL)

Enable Forwarding Settlement Select

Automatic Confirmation Deselect

SAP 69

Automatic Freight Unit Building Deselect

Default FWSD Type 001

Default Conf. Type O-Based on Order Data

Output Profile /SCMTMS/TRQ_FWO

Additional Output Profile /SCMTMS/TRQ_FWO_PRINT

Propogate Changes B Synchronous Propagation of changes, fallback to asynchronous

Default Values

Default Weight UoM KG

Default Volume UoM M3

Default Pieces UoM EA

Freight Unit Building Rule IOT-FUBR-01

Organization Unit Determination

Consider User Assignment Deselect

Sales Organization IOT-SORG-1-Simon Expr Corp.


SAP 70

12 Transportation Charge Management

SAP 71

12.1 Defining Forwarding Agreement Type

You use the forwarding agreement type to define the shipper/consignee-relevant pricing structure. The forwarding agreement type is determined in the charge calculation process in the forwarding order.

Procedure


Management Master Data Agreements and Service Products Define FWA and

Service Product Catalog Types .


Field Value

Forw. Ord. Type IOT1

Short Description IOT: Customer Agreements

Default Agr. Type Deselect

Agr. No. Range 01

Track Changes Select


SAP 72

12.2 Defining Freight Agreement Type

You use the freight agreement type to define the suppliers/carrier-relevant pricing structure. The freight agreement type is determined in the charge calculation process in the freight order.

Procedure


Management Master Data Agreements and Service Products Define Freight

Agreement Types .


Field Value

Type IOT2

Short Description Carrier Agreements

Dflt Agr.Type Deselect

Track Changes Select

Agr. No. Range 02


SAP 73

13 Creating Freight Agreements for Customers and Vendors

SAP 74

13.1 Defining a Forwarding Agreement for Shipper IOT-CU-01

In this procedure, you enter a forwarding agreement for the shipper IOT-CU-01 in the SAP TM system that includes FCL shipments and Incoterm DDP from the US to Europe.

Procedure

Create Scales and Rate Table for US-EU Haulage

1. In SAP NetWeaver Business Client (NWBC), choose Master Data Charge

Management and Service Product Catalogs Scales Create Scale .

2. Define new scales with the following data:

Scale for Ocean Ports

Scale Description Scale Base

IOT-SCALE-OCEANPORTS All Ocean Ports LOC Location

Calculation Type Locations

Absolute IOT_USNEK

Absolute IOT_NLRTM

Scale for Carriers


IOT-SCALE-OCEANLINER All Ocean Liners BP-Business Partner

Calculation Type BP

Absolute IOT-CR-02


Management and Service Product Catalogs Rate Tables Create Rate Table Definition

.

5. Create a new rate with the following data:

Rate Table ID Charge Usage Code Charge Type Description

IOT-RATE-CU-01 Customer BSF Customer Rates, Ocean, US to EU

6. Navigate to the Scales tab.

7. Choose Insert and enter the following scale references:

SAP 75

Dimension No Scale Calculation Base Scale Type

1 IOT-SCALE-OCEANPORTS

SOURCELOC Same Scale (=)

2 IOT-SCALE-OCEANPORTS

DESTLOC Same Scale (=)

3 IOT-SCALE-OCEANLINER

TSP Same Scale (=)

8. Navigate to Dates and Values.

9. Enter a suitable validity period (such as 01.01.2010 to 31.12.2011) and set the currency to USD.

10. Select the validity period row

11. Navigate to the Calculation Rules tab.

12. Enter Calculation Base as QUANTITY_VAL and Price unit to 1 EA.

13. On the Rates tab page, choose Display Rates Display All Rate Combinations and maintain the following rates:

o IOT_NLRTM to IOT_USNEK = 1500 USD

o IOT_USNEK to IOT_NLRTM = 1800 USD

14. Save the rate.

15. Release the validity period of the rate.

Creating a Transportation Charge Calculation Sheet for Haulage Origin


Management and Service Product Catalogs Calculation Sheets Create Calculation

Sheet .

2. Create a transportation charge calculation sheet with the following data:

Calc. Sheet Charge Usage Description

IOT-TCCS-CU-01 Customer Customer Ocean US EU

3. Choose Calc. Sheet Items. Select New Entries and enter the following data:

Field Entry 1

Line Number 10

Instruction Type Sum

Charge Type Blank

Description Blank

SAP 76

Mandatory Blank

Amount Blank

Currency Blank

Rate Table Blank

Resolution Base Blank

Precondition Blank

Field Entry 2

Line Number 20

Instruction Type Standard

Charge Type PRE

Description Inland Transport

Mandatory (on the Classification tab page) No

Amount 1000

Currency USD

Rate Table Blank


Precondition Blank

Field Entry 3

Line Number 30


Charge Type BSF

Description Base Sea Freight

Mandatory (on the Classification tab page) Yes

Amount Blank

Currency USD

Rate Table IOT-RATE-CU-01

Calculation Resolution Base Stage

SAP 77

Precondition From Location: IOT_USNEK

To Location: IOT_NLRTM

Field Entry 4

Line Number 40


Charge Type THC

Description Terminal Handling Charge


Amount 500

Currency USD

Rate Table Blank


Precondition Blank

Field Entry 5

Line Number 50


Charge Type CFI

Description Customs Fine


Amount 700

Currency USD

Rate Table Blank


Precondition Blank

Field Entry 6

Line Number 60

SAP 78


Charge Type PAE

Description Port Additionals/Port Dues Export


Amount 500

Currency USD

Rate Table Blank


Precondition Blank

Field Entry 7

Line Number 70


Charge Type ULF

Description Logistics Fee


Amount 300

Currency USD

Rate Table Blank


Precondition Blank

7. Save the calculation sheet.

Creating a Forwarding Agreement for IOT-CU-01

1. In SAP NetWeaver Business Client (NWBC), choose Forwarding Agreement

Management Forwarding Agreements Create Forwarding Agreement .


Field Value

Agreement Type IOT1

Agreement IOT-FA-CU-01

SAP 79

Agreement Desc: OCEAN TRANSPORT

Valid From 01.01.2010

Valid To 31.12.2011

Document Currency USD

Sales Organization IOT-SORG-1

Ordering Party IOT-CU-01

3. Navigate to the Item tab page and enter the following data:

Field Value

Item Number 100

Calculation Sheet IOT-TCCS-CU-01

4. Save and set the status of the agreement to Released.

5. Save the agreement.

SAP 80

13.2 Defining a Freight Agreement for Carrier IOT-CR-01

In this procedure, you enter a freight agreement for the carrier IOT-CR-01 in the SAP Transportation Management (SAP TM) system that includes the trucking charges for moving the containers from the logistics service provider (LSP) warehouse to the port.

Procedure

Creating Scales and Rate Table for US Inland Transport


Management and Service Product Catalogs Scales Create Scale .

2. Define new scales with the following data:

Scale for Container Types


IOT-SCALE-CONTAINER Container Types EQPGRP

Items Tab Page

Calculation Type Equipment Group

Absolute CN

Absolute AM

Scale for Trucking Carriers


IOT-SCALE-TRUCKERS Trucking Companies BP-Business Partner

Items Tab Page

Calculation Type BP

Absolute IOT-CR-01

Abso

Date post:	06-Nov-2015
Category:	Documents
Upload:	billa-manoj
View:	12 times
Download:	4 times