Basic Settings of SAP TM form SAP

8/17/2019 Basic Settings of SAP TM form SAP

http://slidepdf.com/reader/full/basic-settings-of-sap-tm-form-sap 1/59

SAP Transportation Management

Basic Settings for SAP Transportation Management

PUBLIC

Document Version: 2.0 – September 2012



(C) SAP AG 2

Copyright

© Copyright 2012 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 purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture,Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC,BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF,Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet aretrademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registeredtrademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World WideWeb Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina,Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.



(C) SAP AG 3

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch,BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World aretrademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, GoogleMobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, GoogleUpdater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks orregistered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks ofBusiness Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks ofCrossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National productspecifications may vary.



(C) SAP AG 4

These materials are subject to change without notice. These materials are provided by SAP AGand its affiliated companies ("SAP Group") for informational purposes only, without representationor warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect tothe materials. The only warranties for SAP Group products and services are those that are setforth in the express warranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additional warranty.



(C) SAP AG 5

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 Classesand Information Classes for Business Information Warehouse on the first page of any version ofSAP Library .

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include field names, screentitles, 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, programnames, transaction codes, table names, and key concepts of a programminglanguage when they are surrounded by body text, for example, SELECT andINCLUDE.

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 ofinstallation, upgrade and database tools.

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

<Example text> Variable user entry. Angle brackets indicate that you replace these words andcharacters with appropriate entries to make entries in the system.

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



(C) SAP AG 6

Table of Contents

Basic Settings for SAP Transportation Management ...................................................................... 8

Technical Settings ...................................................................................................................... 11

Naming Logical Systems for the Connection to SAP ERP and SAP TM ............................... 12

Assigning Logical Systems to Clients .................................................................................... 13

Defining SLD Data of Business Systems ............................................................................... 14

Maintaining Business System Groups ................................................................................... 15

Assigning Logical Systems and Queue Types ....................................................................... 16

Activating Queues .................................................................................................................. 17

Creating Active Versions and Models .................................................................................... 18

Activating Business Functions................................................................................................ 19

Activating Error and Conflict Handler ..................................................................................... 20

General Customizing Settings ................................................................................................... 21

Defining Capacity Variants ..................................................................................................... 22

Creating ISO Units ................................................................................................................. 23

Creating Units of Measurement.............................................................................................. 24

Changing Units of Measurement ............................................................................................ 25

Defining Equipment Groups and Types ................................................................................. 26

Maintaining Transportation Groups ........................................................................................ 27

Specifying Language Selection .............................................................................................. 28

Activating Usage of Transportation Allocations ...................................................................... 29

Defining Default Freight Document Types for Stages ............................................................ 30

Defining Stage Type Sequence for Movement Types ........................................................... 32

Displaying SAP TM-Specific User Menu ................................................................................ 34

Defining Schedule Types ....................................................................................................... 35

Defining Common Settings for Dangerous Goods Processing .................................................. 37

Specifying Settings for Mixed Loading Checks .......................................................................... 38

Defining Segregation Keys ..................................................................................................... 39

Defining Responses ............................................................................................................... 40

Specifying Segregation Rules for Segregation Keys ............................................................. 41

Defining Agreement Deactivation Reasons ........................................................................... 42

Configuring Basic Settings for Charge Calculations .................................................................. 43

Defining Category Codes ....................................................................................................... 44

Defining Subcategory Codes.................................................................................................. 46

Defining Charge Types ........................................................................................................... 47

Defining Conditions for OTR Type Determination .................................................................. 50



(C) SAP AG 7

Configuring SAP Transportation Management for Order Integration ........................................ 53

Defining Text Schemas .......................................................................................................... 54

Defining Text Types ............................................................................................................... 55

Setting Up SAPconnect E-Mail .................................................................................................. 56

Configuring SAP Transportation Management for ERP Shipment Integration .......................... 57

Configuring Inbound Integration of Shipments ....................................................................... 58

Configuring Outbound Integration of Shipments .................................................................... 59



(C) SAP AG 8

Basic Settings for SAP Transportation Management

This guide provides information about the settings that you must configure in SAP TransportationManagement (SAP TM) to enable integration with SAP ERP.

Change History

Version Date Description

1.0 December 2010 Initial version

1.1 April 2011Harmonized configuration and master data; scenarios basedon IDES

1.2 November 2011

Updates to:

o Defining Subcategory Codes [Page 46]

o Defining Charge Type Codes [Page 47]

Added sections:

o Defining Schedule Types [Page 35]

o Defining Number Range Intervals forSchedules [External]

o Defining Stage Type Sequence forMovement Types [Page 32]

o Defining Default Agreement Party Roles forStages [External]

o Displaying SAP TM-Specific User Menu [Page 34]

o Configuring Inbound Integration ofShipments [Page 58]

2.0 September 2012 Update for SAP TM 9.0

Important SAP Notes

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

Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP

Service Marketplace at http://service.sap.com/notes.

SAP NoteNumber

Description Valid with Release

1561162 Address data not possible in Event Messagereporting profile

SAP TM 8.1

1581944 Image Source does not work in Link to Action in SAP TM 8.1

http://service.sap.com/notes



http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1561162&_NLANG=en&_NVERS=0









(C) SAP AG 9

SAP NoteNumber

Description Valid with Release

FPM_TREE_UIBB

1620298 Port data incorrectly copied to referencing gatewayschedule

SAP TM 8.1

1599238 Credit Segment information FWSD outboundstructure

SAP TM 8.1

1624325 Empty lines appear in the beginning of a list UIBB SAP TM 8.1

1622146 FBI: Action usages changed in Exit class notconsidered

SAP TM 8.1

1623764 FUB: error in message inbound SAP TM 8.1

1634207 Error when trying to insert a schedule withinTrans.Cockpit

SAP TM 8.1

1629698 /SCMTMS/XPRA_101_TC_RATES: usage ofnumber range for scales

SAP TM 8.1

1634568 Event with reason code from EM is not propagatedto TM

SAP TM 8.1

1679921 Views /SCMB/V_EQU_CODE and/SCMB/V_EQU_MOT are inconsistent

SAP TM 9.0

1729082 Actual Route data cleared when saving FWO SAP TM 9.0 SP01

1736290 Authorization not working for waybill stock SAP TM 9.0 SP01

1739767 Times not taken over from schedule SAP TM 9.0 SP01

1736359 Misleading Error message in Freight Order Typecustomizing

SAP TM 9.0 SP01

Prerequisites

You have set up the system landscape as follows:

You have completed the technical installation of SAP TM, SAP Integration Engine, SAPEvent Management, SCM Optimizer, and SAP ERP IDES Enhancement Package 5.

You have established the connection to the System Landscape Directory (SLD) for all

systems.

You have configured the settings that are required to connect a business system to anIntegration Engine.

You have configured the settings that are required to use the Core Interface (CIF) formaster data transfer.

You have established a trusted connection between the SAP ERP and SAP TM systems.










































(C) SAP AG 10

You have defined all required RFC users, RFC connections, logical system names,technical system names, and business system names.

You have configured Adobe Document Services.

You have completed e-mail setup.

More Information

For information about setting up SAP NetWeaver Process Integration, see the following:

SAP NetWeaver Process Integration installation documentation on SAP ServiceMarketplace at http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver

PI 7.1

SAP Library for SAP NetWeaver 7.0 Including Enhancement Package 2 athttp://help.sap.com/netweaver . In SAP Library, choose SAP NetWeaver TechnologyConsultant's Guide Business Process Management Configuration of Usage Type

Process Integration (PI) .

In particular, see General Setup of Integration Engine and Configuration of BusinessSystems with an Integration Engine sections.

For information about setting up the Core Interface (CIF), see the following:

SAP Library for SAP Supply Chain Management at http://help.sap.com/scm. In SAPLibrary, choose SAP Advanced Planning and Optimization (SAP APO) Integration

via Core Interface (CIF) .

In particular, see the section Checklist for Setting Up the System Infrastructure under

Technical Integration Core Interface (CIF) Setting Up the System Infrastructure .

Best practices document on SAP Service Marketplace at http://service.sap.com Application Life-Cycle Management Methodologies Run SAP Best Practice

Documents Manage APO Core Interface in SAP APO (3.x) / SAP SCM (4.x, 5.x)

For information about setting up Adobe Document Services, see SAP Library for SAP NetWeaver7.0 Including Enhancement Package 2 at http://help.sap.com/netweaver . In SAP Library, choose

SAP NetWeaver Technology Consultant's Guide Business Task Management Adobe

Document Services (Configuration) .

For information about setting up e-mail in an SAP NetWeaver system, see SAP Library for SAPNetWeaver 7.0 Including Enhancement Package 2 at http://help.sap.com/netweaver . In SAP

Library, choose SAP NetWeaver SAP NetWeaver by Key Capability Application Platformby Key Capability Platform-Wide Services Connectivity Communication Interfaces for Mail

and Telephony SAPconnect (BC-SRV-COM) SMTP Config Guide .

See also the following SAP Notes:

SAP Note 455140: Configuration of e-mail, fax, paging or SMS using SMTP

SAP Note 455127: E-mail (SMTP) in different SAP releases

SAP Note 557377: E-mail connection for internal SAP systems

For information about integrating SMC3, see SAP Note 1636870.

http://service.sap.com/instguides


http://help.sap.com/netweaver


http://help.sap.com/scm



http://service.sap.com/
































(C) SAP AG 11

Technical Settings



(C) SAP AG 12

Naming Logical Systems for the Connection to SAPERP and SAP TM

You use this Customizing activity to name the logical system used in the remote function call

(RFC) connection to SAP TM.

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management SCM Basis Integration Basic Settings for Creating the System Landscape Name Logical

Systems .

This is a cross client-activity.

2. Define the logical system for SAP ERP, for example, ERPCLNT001. The standard naming

convention is <SID

>CLNT<client no.

>, for example, QV5CLNT750.

3. Define the logical system for SAP TM, for example, TMCLNT001. The standard naming

convention is <SID >CLNT<client no.>, for example, B1TCLNT750.

More Information

For more information, see the Customizing activity documentation.



(C) SAP AG 13

Assigning Logical Systems to Clients

You use this Customizing activity to assign a logical system to a client in SAP TM.

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management SCM Basis Integration Basic Settings for Creating the System Landscape Assign Logical

Systems to a Client .

This is a cross-client activity.

2. Check whether the logical system for the TM client exists, for example, B1T750.

If it does not exist, define the logical system for the ERP client first. For more informationabout how to define a logical system, see Naming Logical Systems for the Connection to

SAP ERP and SAP TM [Page 12].

More Information

For more information, see the Customizing activity documentation.



(C) SAP AG 14

Defining SLD Data of Business Systems

These settings should be published from your system landscape directory (SLD) automatically.Check whether the corresponding data sets have been imported into your SAP TM system.

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management Transportation Management Basic Functions Define SLD Data of Business

Systems .

2. Check whether an entry exists for your SAP ERP system. If so, no further action isrequired. If not, create the entry as follows.

1. Choose New Entries.

2. In the Business System field, enter a name that relates to your system ID andclient. For example, QV5_750.

3. In the Logical System field, enter your logical system in the format<SID >CLNT<Client Number >.

4. In the Manual Maint. field, choose Flag set. Event has occurred.

5. Save your entries.

If you have installed IDES as your SAP ERP system, the logical system name for the

SAP ERP system is always T90CLNT090.



(C) SAP AG 15

Maintaining Business System Groups

In this step, you determine the assignment to a business system group of SAP TM, and the SAPERP systems that are to be connected. By doing this, you create areas with the same namingconvention that guarantee the unique naming of master data and its synchronization in distributed

system landscapes. If you do not have a specific reason, your SAP TM system and your ERPsystem should be in the same business system group.

This example uses different business system groups due to internal restrictions of SAP systems.

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management SCM Basis Integration Basic Settings for Creating the System Landscape Maintain Business

System Group .

2. Check whether the Business System Group table contains an entry for your SAP ERP

system and your SAP TM system in the format <SID >CLNT<Client Number >. If so, no

further action is required. If not, create the two entries as follows:


2. In the Business System Group field, enter a name that relates to your system ID

and client as <SID ><Client Number > (for example, QV5750 for your SAP

ERP system).

3. In the Description field, enter a name that relates to your system ID and client as

<SID ><Client Number > (for example, QV5750 for your SAP ERP system and

B1T750 for your SAP TM system).




(C) SAP AG 16

Assigning Logical Systems and Queue Types

You use this Customizing activity to assign the logical system and queue types to a businesssystem group (BSG).

Prerequisites

You have assigned all of the systems that form your system landscape to the same BSG.

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management SCM Basis Integration Basic Settings for Creating the System Landscape Assign Logical

System and Queue Type .

2. In the Assignment of Logical System to Business System Group table, create entriesusing inbound queues, for example, for the two-client scenario for SAP SCM:

BusinessSystem Group Logical System

SAP SystemIndicator Release Queue Type

<SID ><CLNT >

(for example,B1T750)

<SID >CLNT<CL

NT > (for

example,

B1TCLNT750)

X <TM Release>,

for example, 9.0 Inbound Queues

<SID ><CLNT >

(for example,QV5750)

<SID >CLNT<CL

NT > (for

example,QV5CLNT750)

X

<ERP

Release>, for

example, 600 Inbound Queues

If the SAP ERP system has active IS-CWM (Catch Weight Management), enter Catch

Weight Management ERP System in the Role field.



(C) SAP AG 17

Activating Queues

In SAP TM, use transaction SMQR to register the queue types CF*. As we use inbound queues,

the queues only need to be registered at the inbound scheduler in the target system (SAP TM).

Procedure

1. In SAP TM, call the QIN scheduler using transaction SMQR.

2. Choose Registration.

3. Enter the following data:

o Queue name: CF*

o EXEMODE: D (Dialog processing) or B (Background processing)

o MAXTIME: 10 (maximum processing time)

o ATTEMPTS: 30 (number of repetitions for locked queues)

o PAUSE: 300 (time between two repetitions)

4. Choose Enter .



(C) SAP AG 18

Creating Active Versions and Models

Procedure

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

Transportation Management Basic Functions Create Active Version and Model .

2. Choose Execute.



(C) SAP AG 19

Activating Business Functions

Procedure

1. In Customizing for SAP TM, choose Activate Business Functions.

2. Confirm the warning message by choosing Continue.

3. Expand the Enterprise Business Functions folder and set the indicator in the PlannedStatus column for the following business functions:

o /BCV/MAIN – FND, Business Context Viewer

o /BCV/MAIN_1 – FND, Business Context Viewer 2

o FND_SOA_REUSE_1 – Improvements for SOA Reuse Functions

o FND_VISUAL_BUSINESS – Visual Business

o SCM_EHS_DG_CI_1 – EH&S and DG Integration Services

o SCM_SCMB_TM_FND1 – Foundation for External Transportation Management

System

o SCM_SCMB_TR_NETWORK – Enhanced Services for Transportation Network

o SCM_SAPTM_SCMB_FND – SAP TM-Specific Enhancements in SCM Basis

4. Choose Activate Changes.



(C) SAP AG 20

Activating Error and Conflict Handler

You use this Customizing activity to specify how the system responds to errors and conflicts inservice operations. In particular, you can specify whether service operations are to be executedagain or terminated.

Procedure

1. In Customizing for SAP TM, choose Cross-Application Components Processes andTools for Enterprise Applications Enterprise Services Error and Conflict Handler

Activate Error and Conflict Handler .

2. In the Activate FEH for Clients screen area, select the Activated checkbox.


More Information

For more information, see SAP Library for SAP Enhancement Package 5 for SAP ERP 6.0 at

http://help.sap.com/erp. In SAP Library, choose Processes and Tools for Enterprise

Applications Error and Conflict Handler (CA-FS-ECH) .

http://help.sap.com/erp





(C) SAP AG 21

General Customizing Settings



(C) SAP AG 22

Defining Capacity Variants

Procedure


Transportation Management Master Data Resources Specify Capacity Variants .


3. Create a capacity variant with the following settings:

Field Value

Cap. Var. 1

Status 2 Normal Capacity

Description Normal Capacity




(C) SAP AG 23

Creating ISO Units

Procedure

1. In Customizing for SAP TM, choose SAP NetWeaver General Settings Check

Units of Measurement .

2. Choose ISO codes.


4. Create a new ISO unit with the following data:

ISO Code ISO Code Text

TEU 20-Foot Container

20 20–Foot Equivalent Unit




(C) SAP AG 24

Creating Units of Measurement

Procedure



2. In the dropdown box, select AAAADL (no dimensions) and choose Units ofmeasurement .

3. Create a new unit of measurement as follows:

1. In the Int. meas. unit field, enter TEU.

2. In the Display screen area, proceed as follows:

In the Commercial field, enter TEU.

In the Technical field, enter TEU.

Leave the Decimal places and float. point exp. fields blank.

3. In the Measurement unit text screen area, proceed as follows:

In the long field, enter 20' Container.

In the short field, enter 20' Contr.

4. In the ALE/EDI screen area, proceed as follows:

In the ISO code field, enter TEU.

Select the Primary code checkbox.

5. In the Application Parameters screen area, select the Commercial meas.unit checkbox.




(C) SAP AG 25

Changing Units of Measurement

Procedure



2. In the dropdown box, select Mass and choose Units of measurement .

3. Display the details for the LB unit and enter ISO code LBR in the ALE/EDI screen area.

4. Save your changes and return to the initial screen.

5. In the dropdown box, select Volume and choose Units of measurement .

6. Display the details for the FT3 unit and enter ISO code FTQ in the ALE/EDI screen area.




(C) SAP AG 26

Defining Equipment Groups and Types

In this Customizing activity, you define equipment groups and equipment types. Equipmentgroups and types are used to specify the container type of a TU resource. If the equipmentgroups and equipment types as listed below do not already exist in your system, create them

using the following procedure.

Procedure

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

General Settings Define Equipment Groups and Equipment Types .

2. Select Equipment Group.

3. Create an entry with the equipment group CN , the description Container, and the

resource class Container.

4. Select equipment group CN and choose Mode of Transport .

5. Add transportation mode category 3 Sea.

6. Choose Equipment Types and add the following entries:

EquipType

Description

TEUCapacity

MaxPayloadWeight

UoMCubic

CapacityUoM

22GP

20’ STD

generalpurposecontainer

1 20 TO Blank M3

28GP

40’ STD

generalpurposecontainer

2 30 TO Blank M3




(C) SAP AG 27

Maintaining Transportation Groups

You use this Customizing activity to define transportation groups, which classify importantattributes relating to how a product is to be transported. Each product is assigned to atransportation group. For example, product attributes could be “refrigerated transportation

required” or “dangerous goods”.

Procedure

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

Master Data Product Maintain Transportation Group .


Tr. Grp. Trans. Group Description

0002 In Liquid Form

0001 On Pallets




(C) SAP AG 28

Specifying Language Selection

In this Customizing activity, you specify the languages that you can use for phrases in EH&SServices.

Procedure

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

EH&S Services Phrase Management Specify Language Selection .

Enter the following data:

L Name of Language Sort

EN English 1

DE German 2




(C) SAP AG 29

Activating Usage of Transportation Allocations

Transportation allocations provide information about which carriers can be used in variousgeographical areas with which means of transport. A transportation allocation defines theminimum and maximum delivery quantities that have been agreed with a carrier, and is taken into

consideration, for example, during carrier selection. A transportation allocation also storesallocated quantities, which are also used, for example, during carrier selection.

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management Transportation Management Planning General Settings Define Transportation

Allocation Settings .

2. Select the Activate TAL/BS checkbox.




(C) SAP AG 30

Defining Default Freight Document Types for Stages

In this procedure, you specify which freight document type (freight order type or freight bookingtype) is used to generate settlement documents through the shortcuts in the forwarding order.

You can specify different freight order types for each stage type and transportation mode.

Prerequisites

You have set up the required freight document type in the system or you are using thestandard values.

You have specified the required stage types and transportation modes or you are usingthe standard values.

Procedure

1. In Customizing for Transportation Management , choose Forwarding OrderManagement Forwarding Order Define Default Freight Document Types for Stages

.

2. Create an entry using the following data:

Seq. No.Shipping

TypeStage Type

Transportation Mode

Planningand

ExecutionOrganization

DocumentType

1

LCL (LessthanContainerLoad)

01 01 Blank OF05

2


02 01 Blank OF10

3


03 03 Blank OF04

4


04 01 Blank OF10

5


05 01 Blank OF05

3. For all cases, select the following checkboxes:



(C) SAP AG 31

o Create FD (Freight Document)

o Select FD (Freight Document)

o Sel. Schedule (Select Schedule)



(C) SAP AG 32

Defining Stage Type Sequence for Movement Types

Movement types predefine stages in your forwarding order. In this procedure, you can specifywhich stages are to be added to your freight order when the corresponding movement type isused.

Check whether the following movement types exist in your system and create them if necessary:

DD: Door to door for LCL Ocean Freight

CC: CFS to CFS for International Outbound Transportation

Prerequisites

You have maintained the Customizing settings for the required movement type.

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management Transportation Management Basic Functions Type Codes and Role Codes General Type Codes and Role Codes Define Stage Type Sequence for Movement

Types .

2. Create the following entries if they do not already exist:

Mov. Type Seq. No. Stage Type Stage Proposal StgeTpeOcc

DD 1 01 SelectedStage type mustoccur at leastonce

DD 2 02 Blank

Stage type can

occur in anynumber


DD 4 04 BlankStage type canoccur in anynumber


CC 1 02 BlankStage type canoccur in anynumber

CC 2 03 SelectedStage type mustoccur at leastonce



(C) SAP AG 33

Mov. Type Seq. No. Stage Type Stage Proposal StgeTpeOcc

CC 3 04 BlankStage type canoccur in anynumber



(C) SAP AG 34

Displaying SAP TM-Specific User Menu

In this Customizing activity, you define which area menu is to be displayed as the initial menuwhen you log on to the system.

Procedure

1. In Customizing for SAP TM, choose SAP NetWeaver Application Server System

Administration Definition on initial menu .

2. Check whether /SCMB/MENUE is defined as the initial menu. If so, no further action is

required. If not, proceed with the next step.

3. Choose Definition of initial menu.

4. Set the initial menu to /SCMB/MENUE.


This setting is client-independent, which means that all clients are affected.



(C) SAP AG 35

Defining Schedule Types

In this Customizing activity, you define which number range is to be used for the schedule typesin the scenarios.

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management Transportation Management Master Data Transportation Network Schedule

Define Schedule Types .

2. Change schedule type 1000 as follows:

Field Value

Type 1000

Description Ocean Carrier Schedule

Transportation Mode 04 - Inland Waterway

Default Schedule Ty. Selected

Gateway Selected

Document Type BSEA – Ocean Booking

Reference Not selected

Template Not selected

Header No. Range 07

Voyage No. Range 01

CC Strategy Not selected

Deletion Strategy Not selected



Field Value

Type 2000

Description Sailing Schedule

Transportation Mode 04 - Inland Waterway

Default Schedule Ty. Not selected

Gateway Selected



(C) SAP AG 36

Field Value


Reference Not selected

Template Selected

Header No. Range 07

Voyage No. Range 01

CC StrategySCHCHG_DEF – Default ScheduleChange Strategy

Deletion StrategySCHDEL_DEF – Default ScheduleDeletion Strategy



Field Value

Type 2100

Description Sailing Schedule with Reference

Transportation Mode 03 - Sea

Default Schedule Ty. Not selected

Gateway Selected


Reference Selected

Template Selected

Header No. Range 07

Voyage No. Range 01

CC Strategy Not selected

Deletion Strategy Not selected




(C) SAP AG 37

Defining Common Settings for Dangerous GoodsProcessing

In this Customizing activity, you define general settings for dangerous goods processing in SAP

TM.

Procedure

1. In Customizing for SAP TM, choose Basic Functions Dangerous Goods Define

Common Settings for Dangerous Goods Processing .


DG ActivateStrategy for DG

ChkDG Print Strat.

DG ActivateFUB

DG ActivateVSR

Selected DG_EHS_CHK DG_EHS_PRT Selected Selected




(C) SAP AG 38

Specifying Settings for Mixed Loading Checks



(C) SAP AG 39

Defining Segregation Keys

In this Customizing activity, you specify segregation keys for the mixed loading checks.

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management SCM Basis EH&S Services Dangerous Goods Management Dangerous Goods Checks and

Dangerous Goods Documents Dangerous Goods Checks Specify Settings for Mixed

Loading Checks Specify Segregation Keys .


Regulation Segr. KeyDescription of Segregation

Key

ADR 3 Inflammable fluid substances

ADR 5.2 Organic peroxides

IMDG 3 Inflammable fluid substances

IMDG 5.2 Organic peroxides

RID 5.2 Organic peroxides

RID 3 Inflammable fluid substances

CN 3 Organic peroxides

CN 5.2 Inflammable fluid substances




(C) SAP AG 40

Defining Responses

In this Customizing activity, you define responses that are used in the segregation rules for thefollowing:

Segregation keys

Enterprise-specific mixed loading groups

Procedure


Dangerous Goods Documents Dangerous Goods Checks Specify Settings for Mixed

Loading Checks Specify Responses .


Response Desc. of Response Resp. Type

E1Error: Mixed loading notallowed

E




(C) SAP AG 41

Specifying Segregation Rules for Segregation Keys

In this Customizing activity, you specify segregation rules for the segregation keys. Thesegregation rules are a regulation-dependent decision matrix in which you specify thecombinations of segregation keys that are prohibited or permitted.

Procedure


Dangerous Goods Documents Dangerous Goods Checks Specify Settings for MixedLoading Checks Specify Segregation Rules for Segregation Keys .


DG Regulation Segr. Key Segr. Key Response

ADR 3 5.2 E1

IMDG 3 5.2 E1

RID 3 5.2 E1

CN 3 5.2 E1




(C) SAP AG 42

Defining Agreement Deactivation Reasons

Procedure


Transportation Management Master Data Agreements and Service Products Define Deactivation Reasons .

2. Create the following entries:

Field Value

01 Incorrect Maintenance-No longerused

02 Outdated-No longer used

3. Save your entries and ignore any warning messages.



(C) SAP AG 43

Configuring Basic Settings for Charge Calculations





(C) SAP AG 45

Charge Category Short Description

023 Supply of Customs Formalities, Transit

024 Supply of Customs Formalities, Import

025 Already Invoiced Amount

026 Adjustment / Quotation Amount



(C) SAP AG 46

Defining Subcategory Codes

Procedure


Transportation Management Basic Functions Charge Calculation Basic Settingsfor Charge Calculation Define Charge Subcategory Codes .

2. Check that the following entries exist and create any that are missing:

Charge Subcategory Description

100000 Freight Charges

101000 Basic Freight

101021 Rate

103001 Bunker Adjustment Factor

103008 Fuel Surcharge

103009 Surcharge

104000 Toll Fee Fix

104007 Terminal Handling Charges

104012 Destination Port Additional

104013 Origin Port Additional

104130 Destination Port Service Charge

104131 Origin Port Service Charge

104132 Detention Charges

609102 Stop in Transit

710000 Discount



(C) SAP AG 47

Defining Charge Types

In this Customizing activity, you define charge types that you can assign to calculation sheets andrate tables. Once assigned to a calculation sheet line item or a rate table, a charge type plays animportant role in how the system calculates the transportation charges for that line.

When defining charge types, you can configure the following settings:

Specify whether a charge type can result in a positive or negative value

Specify whether a charge type can be an absolute value or a percentage value

Specify whether you want to set the charge type as an absolute value or a percentagevalue each time you assign the charge type

Assign a default calculation base to the charge type so you do not need to assign acharge type each time you create a calculation sheet line item

Indicate whether a charge type is a leading charge type and so must have a value for the

system to be able to calculate the charges

Mark a charge type as inactive so the system cannot use it to create new calculationsheets or rate tables

Enter a charge type description in multiple languages

Procedure

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

for Charge Calculation Define Charge Types .

2. Check that the following entries exist and create any that are missing:

Charge Type Charge Subcategory Charge Category Description

FB00 100000 004 Basic Freight

LMPR 104132 002 Lumper Charges

FUEL 103008 003 Fuel Surcharge

STOP 609102 002 Stop Off Charges

DISC 710000 004 Freight discount

CFI 100000 012 Customs Fine

PAE 104131 010Port Additionals / PortDues – Export

PAI 104130 007Port Additionals / PortDues – Import

ULF 101021 012 Logistics Fee



(C) SAP AG 48


ROAD 100000 004Road TransportationCharge

PIO 101000 014Pick-Up/ Drop-Off

Charge

BSF 101021 003 Base Sea Freight

IPSD 104012 002Int. Port SecurityDestination

IPSO 104013 002Int. Port SecurityOrigin

THCD 104007 007Terminal HandlingCharge (THC)Destination

THCO 104007 010 Terminal HandlingCharge (THC) Origin

RAIL 100000 003Rail TransportationCharge

HAUF 101000 003 FTL Haulage

ADJ N/A 026 Adjustment /Quotation Amount

BASE 100000 004 Base freight

BAF 103001 012 Bunker Adj. Factor

THC 104007 014Terminal HandlingCharge

PEAK 103009 008 Peak Season Charge

LSFS 103009 008Low SulphurSurcharge

PRE 100000 014 Land Pre Carriage

TOLL 104000 002 Toll Fee Fix

BLAD 104000 002 B/L Fee Fix

CAF 103009 012Currency AdjustmentFactor

PRS 103009 012Piracy RiskSurcharge

EBAF 103001 002 E-BAF (Emergency



(C) SAP AG 49


Bunker Adj. Factor)

ON 100000 014 On Carriage

AMS 104000 002 Automated ManifestSubmission Fee



(C) SAP AG 50

Defining Conditions for OTR Type Determination

The system permits only one condition for determining order-based transportation requirements(OTRs). If a condition does not exist in your system, you must create one. Alternatively, you mayhave to change the condition.

Before you can maintain the decision table for this condition, you must create thecorresponding document types in SAP TM. For more information, see the configurationguide for your scenario.

Procedure

1. In SAP NetWeaver Business Client, choose Application Administration General

Settings Conditions Create Condition .

2. On the New Condition Definition screen, enter the following data:

Field Value

Condition ZOTR_TYPE

Description OTR Type Determination

Condition Type /SCMTMS/OTR_TYPE

Origin of Condition Condition Based on BRFplus Decision Table

3. Choose Continue.

If the system displays an error message stating that the condition already exists,choose Application Administration General Settings Conditions Edit

Condition and create or check the data specified below.

4. Choose Data Access Definitionand enter the following data in the table:

5. In the Data Access Definition area, choose Create and enter the following data in the newtable row:

Field Value

Column Position in BRFplus Table 10

Data Access Definition for Conditions /SCMTMS/TRQ_ORD_CAT

Data Object Description TR: Original Order Category

6. In the Business Object Based Data Access Definition area below the table, enter thefollowing data:

Field Value



(C) SAP AG 51

Field Value

Name of BO Used in Condition /SCMTMS/TRQ

Name of BO Node Used in Condition ROOT

Name of the Field of the BO Node BASE_BTD_TCO

7. In the Data Access Definition area, choose Create and enter the following data in the newtable row:

Field Value

Column Position in BRFplus Table 20

Data Access Definition for Conditions /SCMTMS/TRQ_ORD_TYPE

Data Object Description TR: ERP Order Type

8. In the Business Object Based Data Access Definition area below the table, enter the

following data:

Field Value

Name of BO Used in Condition /SCMTMS/TRQ

Name of BO Node Used in Condition ROOT

Name of the Field of the BO Node BASE_BTD_PROCTCO

9. Choose Save and Back to save your entries and return to initial screen of the condition.

10. Choose Edit .

11. In the Table Contents area, choose Insert New Row to create a new condition record line.

12. Enter or check each parameter value for the new condition record as specified below.

1. In the TR: Original Order Category column, choose the icon in your new row andchoose Direct Value Input from the context menu.

2. In the dropdown menu, select is equal to and enter 001 (purchase order) in the

adjacent field.

3. Choose OK .

4. In the same row, choose the icon in the TR: ERP Order Type column and chooseDirect Value Input from the context menu.

5. In the dropdown menu, select is equal to and enter DIT1 in the adjacent field.

6. Choose OK .

7. In the same row, choose the icon in the OTR Type column and choose DirectValue Input from the context menu.

8. In the available field, enter DIT1.



(C) SAP AG 52


13. Repeat the process above to create or check the following parameter values by choosingDirect Value Input in the corresponding cells:

These values are scenario-specific and need to be created only if you intend toimplement the corresponding scenario:

o OTR type DIT1 is required for the Domestic Inbound Transportation

scenario.

o OTR type IIL2 is required for the International Inbound Transportation

scenario.

o OTR type DOT1 is required for the Domestic Outbound Transportation

scenario.

o OTR type OTTL is required for the Outsourced Transportation scenario.

RowTR: Original Order

CategoryTR: ERP Order Type OTR Type

2 is equal to 001 is equal to IIL4 IIL2

3 is equal to 114 is equal to ODOT4 DOT1

4 is equal to 114 is equal to OTTL OTTL



(C) SAP AG 53

Configuring SAP Transportation Management forOrder Integration



(C) SAP AG 54

Defining Text Schemas

Procedure

1. In Customizing for SAP TM, choose Cross-Application Components Processes and

Tools for Enterprise Applications Reusable Objects and Functions for BOPFEnvironment Dependent Object Text Collection Maintain Text Schema .

2. In the navigation tree, double-click Text Type and enter the following data:

Field Value

Text Type TM01

Description Driver Notes

3. In the navigation tree, double-click Text Schema and enter the following data:

Field Value

Txt Schema OT0001

Description Text schema for OT

4. Select your new text schema and double-click Text Type to Text Schema Assignment inthe navigation tree.

5. Enter your data based on the following example:

Text Type Mandatory Internal Lang. Text

TM01 Not selected Not selected Not selected

A0001 Not selected Not selected Not selected

6. In the navigation tree, double-click Assign Text Schema to BO and Node and enter thefollowing data:

Business Object Name Node Name Txt Schema

/SCMTMS/TOR ROOT OT0001

/SCMTMS/TOR TENDERING OT0001

/SCMTMS/TRQ ROOT OT0001

7. Ignore any warnings that appear when value OT0001 is inserted automatically into theTxt Schema column.

8. Save your changes.



(C) SAP AG 55

Defining Text Types

Procedure

1. In Customizing for SAP TM, choose Cross-Application Components Processes and

Tools for Enterprise Applications Reusable Objects and Functions for BOPFEnvironment Dependent Object Text Collection Maintain Text Schema .

2. Choose New Entries and create the following entry:

Field Value

Text Type 020

Description General Header Text

3. Choose Text Schema.

4. Select ERP_DFLT.

5. Choose Text Type to Text Schema Assignment .



Text Type Mandatory Internal Language Text

20 Not selected Not selected Not selected




(C) SAP AG 56

Setting Up SAPconnect E-Mail

For information about how to configure your SAPconnect e-mail, see SAP Note 455140.







(C) SAP AG 57

Configuring SAP Transportation Management forERP Shipment Integration



(C) SAP AG 58

Configuring Inbound Integration of Shipments

Once you have configured shipment integration in your SAP ERP system, you have to carry outthe following steps in the SAP TM system.

Procedure

1. Specify the freight order type that the SAP TM system uses to create freight orders basedon shipments received from SAP ERP.

You have the following options:

o You can assign freight order types to ERP shipment types in Customizing forSAP TM under SAP Transportation Management TransportationManagement Integration ERP Logistics Integration Shipment Integration

Assign Freight Order Types to ERP Shipment Types .

o You can specify a default freight order type that the system uses if it cannot findan entry for an ERP shipment type in the Customizing activity Assign Freight

Order Types to ERP Shipment Types . To specify the default freight order type,select the Default Type for ERP Shipment Integration checkbox in the relevant

freight order type in Customizing for SAP TM under SAP TransportationManagement Transportation Management Freight Order Management

Freight Order Define Freight Order Types .

In the Define Freight Order Types Customizing activity, you also have to assign a suitableoutput profile to the freight order types and specify that they are relevant forsubcontracting. You do this as follows:

o In the Basic Settings screen area, set the value in the Freight Order Can BeSubcontracted field to Relevant for Subcontracting .

o In the Output Options screen area, enter the output profile in the Output Profile field.

2. Enable PPF output agent /SCMTMS/TOR_TENDERING, which is used to send the

tendering result to SAP ERP.

You do this in Customizing for Cross-Application Components under Processes andTools for Enterprise Applications Reusable Objects and Functions for BOPFEnvironment PPF Adapter for Output Management Maintain Output Management

Adapter Settings .

You have to enable the following entry:

o Output Agent: /SCMTMS/TOR_TENDERING

o Business Object: /SCMTMS/TOR

o Node: TENDERING

o Agent Class for BO Node: /SCMTMS/CL_PPF_SERV_TOR_TEND



Configuring Outbound Integration of Shipments

Outbound integration of shipments enables you to create, change, and delete shipments in SAPERP based on freight orders received from SAP TM. To send a freight order to SAP ERP, youhave to set up the freight order type accordingly.

Procedure

1. In Customizing for SAP TM, choose SAP Transportation Management Transportation Management Freight Order Management Freight Order Define

Freight Order Types .

2. Select the relevant freight order type.

3. In the Output Options screen area, enter output profile /SCMTMS/TOR.

4. In the Additional Settings screen area, select Shipment Creation in SAP ERP .