SAP_TM_FAQ

SAP TM Requirements Report generated by: d034797, Wed Sep 24 13:54:52 CEST 2008 This document describes 154 Requirements This document is a preliminary version and not subject to your license agreement or any other agreementwith SAP. This �document contains only intended strategies, developments, and functionalities of the SAP®product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. Please note that this document is subject to change and may be changed by SAP at anytime without notice. SAP assumes no responsibility for errors or omissions in this document.

SAP TM Requirements d034797 SAP AG

I SAP Internal

Table of Content

1. Systemlandscape........................................................................................................................................1

1.1. Upgrade.....................................................................................................................................................................................1

1.1.1. How do I upgrade from SAP TM 6.0 to SAP TM 7.0 (168) ..................................................................................................1

1.1.2. Can I upgrade from SCM APO TP/VS to SCM TM? (7) .......................................................................................................1

1.2. General.......................................................................................................................................................................................1

1.2.1. For which hardware platform is SAP TM available (129) .....................................................................................................1

1.2.2. What deployment / installation options are currently available for SAP TM? (8) .................................................................2

1.3. Installation.................................................................................................................................................................................2

1.3.1. Which platforms are supported for the VSR optimizer and the Carrier Selection (CS) Optimizer? (84) .............................3

1.3.2. What hardware is required for SAP TM (sizing) (130) ..........................................................................................................3

1.3.3. How is the software component for the planning engine (optimizer) called? (77) ................................................................3

1.3.4. Can SAP TM installed on the same instance with SAP EWM (71) .......................................................................................3

1.3.5. Can SAP TM installed on the same instance with APO (72) .................................................................................................4

1.3.6. Can SAP TM installed on the same instance with an existing SCM system or can I upgrade an existing SCM system? (4) 4

1.3.7. Does SAP TM require Live Cache? (5) ..................................................................................................................................4

2. Features & Functions................................................................................................................................5

2.1. Freight Management................................................................................................................................................................5

2.1.1. Quick request entry for consignments (Shipment requests) (86) ...........................................................................................5

2.1.2. Capturing of incomplete shipment requests (87) ....................................................................................................................5

2.1.3. Quote / Quotation entry (88) ..................................................................................................................................................5

2.1.4. Shipment Requests templates for easy creation of repeating similar requests (89) ...............................................................6

2.1.5. Automatic assignment of organizational units to requests / order (123) ...............................................................................6

2.1.6. Against which dates is the validity of the Freight Agreement checked? (158) ......................................................................7

2.1.7. Additional services during transportation request maintenance. (60) ....................................................................................8

2.1.8. Order entry for consignments (shipment request) (63) ..........................................................................................................8

2.1.9. Entry of freight request (64) ...................................................................................................................................................9

2.1.10. Entry of Quotation (65) ........................................................................................................................................................9

2.1.11. Customer contracts (66) ......................................................................................................................................................10

2.1.12. Route determination for SRQ (67) .....................................................................................................................................10

2.1.13. Transportation charge management for SRQ / FRQ (68) ...................................................................................................10

2.1.14. Shipment Definition (69) ....................................................................................................................................................10

2.1.15. Confirmation for SRQ / FRQ (70) ......................................................................................................................................11

2.2. Transportation Dispatching & Execution............................................................................................................................11

2.2.1. Adaptive Planning (167) .......................................................................................................................................................11

2.2.2. Determination of the planning profile (124) ........................................................................................................................12


II SAP Internal

2.2.3. What is the relationship between the status of a tour and the status of a shipment order and freight order (161) ...............12

2.2.4. Tour (153) .............................................................................................................................................................................13

2.2.5. Planned and executed activities (154) ..................................................................................................................................13

2.2.6. Selection of resources / vehicles / trailer (145) ....................................................................................................................14

2.2.7. Manual Dispatching (35) ......................................................................................................................................................14

2.2.8. Planning / Optimization (36) ................................................................................................................................................14

2.2.9. Dynamic Route determination / Routing Guide (37) ...........................................................................................................15

2.2.10. Scheduling (38) ..................................................................................................................................................................15

2.2.11. Carrier Selection / TSP Selection (39) ...............................................................................................................................16

2.2.12. Shipment Order / Freight Order (40) ..................................................................................................................................16

2.2.13. Tendering (42) ...................................................................................................................................................................17

2.2.14. Continuous Move with Carrier Selection (43) ....................................................................................................................17

2.2.15. Compartment Planning (44) ...............................................................................................................................................18

2.2.16. Freight Space Booking (45) ................................................................................................................................................18

2.2.17. Execution and Track & Trace (46) .....................................................................................................................................18

2.2.18. Replanning during execution (47) ......................................................................................................................................19

2.2.19. Driver Planning (48) ...........................................................................................................................................................19

2.2.20. Multi-pick/Multi-drop Shipments (51) ...............................................................................................................................19

2.2.21. FTL / LTL Decision support (52) ......................................................................................................................................20

2.2.22. Intermodal & Cross-Dock Planning (Hub) (53) .................................................................................................................20

2.2.23. Appointments / Delivery Time Windows (54) ..................................................................................................................20

2.2.24. In/Compatibilities (55) .......................................................................................................................................................21

2.2.25. Dock scheduling (56) ..........................................................................................................................................................21

2.2.26. Capacity Allocation (57) .....................................................................................................................................................21

2.2.27. Container - Master data and handling within the manual dispatching (58) ........................................................................22

2.2.28. Freight Unit Building Rules (82) ........................................................................................................................................23

2.2.29. Freight Units (83) ..............................................................................................................................................................23

2.3. General.....................................................................................................................................................................................24

2.3.1. I would like to change the behavior of the business objects. It that possible (160) .............................................................24

2.3.2. Standard roles for SAP TM (170) .........................................................................................................................................25

2.3.3. Operation in Batch (136) ......................................................................................................................................................25

2.3.4. Support of all modi / means of transport (50) .......................................................................................................................26

2.3.5. Print document (61) ..............................................................................................................................................................26

2.3.6. Organization Units and Business Partners (128) ..................................................................................................................27

2.3.7. Printing of Barcodes (141) ....................................................................................................................................................27

2.4. Transportation Charge Management...................................................................................................................................28

2.4.1. TCM Functionality Overview (91) ......................................................................................................................................28

2.4.2. Transportation Charge Calculation (92) ..............................................................................................................................28

2.4.3. Are there standard capabilities to re-rate transportation charges based on either time or a trigger (164) ............................29

2.4.4. Automatic calculation / determination of freight charges (93) ............................................................................................29

2.4.5. Freight Agreements for Customers and Third Party contracts (94) ....................................................................................29

2.4.6. Maintenance of Rate tables (95) ..........................................................................................................................................30

2.4.7. Scales (96) ............................................................................................................................................................................31

2.4.8. Reusage of Rates and Scales (97) .........................................................................................................................................31


III SAP Internal

2.4.9. Transportation Charge Calculation Sheet (98) ....................................................................................................................31

2.4.10. Determination of Freight Agreements, tariffs and rates (99) ............................................................................................31

2.4.11. Determination of contribution margin and analysis of the transportation profitability (100) ............................................32

2.4.12. Incoterm split (101) ............................................................................................................................................................32

2.4.13. Multi-Currency (102) ..........................................................................................................................................................32

2.4.14. Exchange Rates (103) ........................................................................................................................................................32

2.4.15. Pricing analyses Tools (104) ..............................................................................................................................................33

2.4.16. Integration in the whole SAP TM process (105) ................................................................................................................33

2.4.17. Examples of Freight Rates and calculation methods (106) ................................................................................................33

2.4.18. Customer Freight Invoicing (Customer Billing) (107) ......................................................................................................34

2.4.19. Supplier Freight Invoicing (Supplier Settlement) (108) .....................................................................................................35

2.4.20. Simple Credit Limit Check (109) .......................................................................................................................................36

2.5. Analytics..................................................................................................................................................................................37

2.5.1. What is the standard BI content provided in SAP TM? (119) ..............................................................................................37

2.5.2. What is the reporting strategy for SAP TM (127) ...............................................................................................................37

3. General.....................................................................................................................................................39

3.1. Overview..................................................................................................................................................................................39

3.1.1. What is SAP TM? Please give a short overview about what SAP TM is? (111) .................................................................39

3.1.2. In which process steps can SAP TM be separated? (112) ....................................................................................................39

3.1.3. Does SAP TM has a direct integration to the SAP ERP Oil & Gas solution (TD shipment). Does SAP TM handle loss and

gain? (159) .......................................................................................................................................................................................40

3.1.4. Where can I find the official SAP TM 6.0 documentation? (137) .......................................................................................40

3.1.5. Where can I find additional SAP TM 6.0 Information? (139) .............................................................................................41

3.1.6. Where do I find the internal SAP sales kit for SAP TM 6.0 (143) .......................................................................................41

3.1.7. What is included in the Processing Transportation Requests in SAP TM? (113) ................................................................42

3.1.8. What is included in Planning and Executing Transportation Requests in SAP TM (114) ...................................................43

3.1.9. What is included in Managing Supplier Transportation Charges in SAP TM (115) ...........................................................45

3.1.10. What is included in Managing Customer Transportation Charges in SAP TM? (116) ......................................................47

3.1.11. How would an example shipper process who is using SAP TM would look like? (117) ..................................................48

3.2. General.....................................................................................................................................................................................49

3.2.1. What reference model is used on SAP TM? (135) ...............................................................................................................49

3.2.2. Why is feature X / system Y not included in the scope? This is the most important feature / system. (13) .......................49

3.2.3. Which volume is expected to get handled by SCM TM? (16) ............................................................................................50

3.2.4. How will we integrate to SCM APO in the future (19) ........................................................................................................50

3.2.5. What does abbreviation XXX mean? What are the offiziell names for the transportation components in SAP? (21) ........50

3.2.6. Does SAP TM support simulation / modeling (simulation version simular to APO)? (118) ..............................................51

3.2.7. Which languages are supported by SAP TM / unicode (28) ................................................................................................51

3.2.8. SAP TM is using Webdynpro for ABAP. Can I also use Webdynpro for Java to create customer / partner specific screens.

(31) ..................................................................................................................................................................................................53

3.3. Organisational.........................................................................................................................................................................53

3.3.1. What is the planned maintenance for SAP SCM TP/VS? Are there planned functional improvements for SAP SCM TP/VS?

(125) .............................................................................................................................................................................................53


IV SAP Internal

3.3.2. Who can I become part of the Ramp-up for SAP TM 6.0 (162) ..........................................................................................53

3.3.3. What is the planned date for general availability (end of Ramp-up) of SAP TM 7.0? (165) ..............................................54

3.3.4. SAP TM Training (157) ........................................................................................................................................................54

3.3.5. Where do I find more information on SAP TM Pricing? (144) ...........................................................................................54

3.3.6. What is the planned date for general availability (end of Ramp-up) of SAP TM 6.0? (147) ..............................................55

3.3.7. How can I get into contact with SAP TM interested people? (149) .....................................................................................55

3.3.8. How can I share SAP TM related information with others (wiki)? (150) ............................................................................56

3.3.9. Where can I find the application solution map for SCM? (78) ............................................................................................56

3.3.10. I would like to get access to a SAP TM test system / IDES system (80) ...........................................................................56

3.3.11. How can I get into contact with a reference customer? (17) .............................................................................................57

3.4. Delta.........................................................................................................................................................................................57

3.4.1. What is the main difference between SCM APO TPVS and ERP LES and SAP TM? (2) ..................................................57

4. Integration................................................................................................................................................59

4.1. General.....................................................................................................................................................................................59

4.1.1. Integration with SAP TM based on EDIFACT standards (133) ...........................................................................................59

4.1.2. What external services / interfaces does SAP TM provide? (134) .......................................................................................59

4.1.3. How can I influence the master data in SAP TM which is send from SAP ERP (166) .......................................................59

4.1.4. How can I find existing services (webservices) for SAP in general? (169) .........................................................................60

4.1.5. Which SAP ERP Release is required to integrate to SAP TM? (6) ....................................................................................60

4.1.6. Integration between SAP ERP and SAP TM - Master Data (15) .........................................................................................61

4.1.7. Will multi-backend system be supported? (23) ...................................................................................................................61

4.1.8. Can I use screen X to allow an external user to maintain / view Y in SAP TM? (25) ........................................................61

4.1.9. Can I use legacy system X or Web portal Y to integrated to SAP TM (59) ........................................................................62

4.1.10. Does SAP TM use the same business objects as SAP EWM? (73) ....................................................................................62

4.1.11. If I use SAP TM, SCM APO and / or SAP EWM how can I synchronize the master data for these systems. (74) ..........62

4.1.12. How can I select which customers and suppliers are integrated to SAP TM? (85) ............................................................63

4.1.13. Schedules (122) ..................................................................................................................................................................63

4.1.14. Transporation Allocation (140) ..........................................................................................................................................64

4.1.15. Does SAP TM has visibility of stocks / production orders or other supply elements? (120) ............................................64

4.1.16. Which integration of mobile devices does SAP provide? How is the mobile infrastructure integrated? (34) ...................64

4.2. Specific Systems......................................................................................................................................................................65

4.2.1. Are ERP shipments necessary if SAP TM is in usage? (132) ..............................................................................................65

4.2.2. What is xCarrier and how is it related to SAP TM? (138) ...................................................................................................65

4.2.3. Are handling units integrated from SAP ERP to SAP TM? (163) .......................................................................................66

4.2.4. Does SAP TM support stackabilty / Vehicle space optimization / loading sequence? (148) ...............................................66

4.2.5. Integration between SAP ERP Fleetmanagement and SAP TM (155) ................................................................................67

4.2.6. Can SAP TM still use SAP ERP rates for Carrier Selection? (156) ...................................................................................67

4.2.7. Which Map content provider do offer GIS integration? (79) ...............................................................................................67

4.2.8. How does Geocoding and Distance Calculation work with the eServer from the PTV AG (81) ........................................67

4.2.9. How will EH&S be integrated into SAP TM? (27) ..............................................................................................................68

4.2.10. Does SAP TM contain a strategic freight procurement solution? (32) ..............................................................................68

4.2.11. Integration between SAP CRM and SAP TM (9) ..............................................................................................................69


V SAP Internal

4.2.12. Integration between SAP ERP and SAP TM - Transactional Data (10) ............................................................................69

4.2.13. Integration between SAP GTS and SAP TM? (11) ............................................................................................................69

4.2.14. Can I integrate SAP ERP to SAP APO TP/VS and to SAP TM? (12) ...............................................................................70

4.3. Event Management.................................................................................................................................................................70

4.3.1. SAP EM integration processes (151) ....................................................................................................................................70

4.3.2. SAP TM - Order Taking Visibility Process (152) ................................................................................................................70

5. User Interface..........................................................................................................................................72

5.1. General.....................................................................................................................................................................................72

5.1.1. Does SAP TM support Drag-and-Drop? (22) ......................................................................................................................72

5.1.2. How can I open the same session several times? How can I open the entry of shipment request several times? (126) ......72

5.1.3. How can I extent the SAP TM Userinterface? (131) ............................................................................................................72

5.1.4. Which user parameters can be used to as part of the user profile in SAP TM to adjust system settings? (146) ..................72

5.1.5. How can I avoid the Basic View when creating/displaying certain documents – for example Shipment Request or Booking

Request – and start directly in the Detailed View? (142) ...............................................................................................................73

5.1.6. Which user interface do I use for SAP TM? (121) ...............................................................................................................74

5.1.7. Which user interface technology is used? (75) .....................................................................................................................74


VI SAP Internal

1. Systemlandscape

1.1. Upgrade

1.1.1. How do I upgrade from SAP TM 6.0 to SAP TM 7.0 (168) ID: 168

Release: Phase 1

Status : Answered

Description:

The upgrade process from SAP TM 6.0 to SAP TM 7.0 is described in note 1180890.

1.1.2. Can I upgrade from SCM APO TP/VS to SCM TM? (7) ID: 7

Release: Undefined

Status : Answered

Description:

No. There is not upgrade / technical migration available from TP/VS to SAP TM. The customer has to run a

customer specific project to perform this update.

SAP TM is designed to drive, manage and operate transportation across multiple enterprises, companies and

warehouse management systems, including process steps that are executed by retailers, manufacturers, and

Logistics Service Providers.

As the used technology and architecture is completely different a solution upgrade from SAP ERP LES-

TRA or from SAP SCM APO TPVS to SAP TM are not supported.

1.2. General

1.2.1. For which hardware platform is SAP TM available (129) ID: 129

Release: Undefined


1 SAP Internal

Status : Undefined

Description:

SAP TM is available on the same hardware platforms then SAP Netweaver.

The SAP TM optimizer is only available on Window and Linux. Depending on the provider of the geocoder

you may also have restrictions. Currenlty the geocoder from PTV runs on Windows.

To see the available components:

Transaktion bopp in CSN -> Old PPMS (PPMS 1.0) -> Products / Versions -> Product Version "SAP TM

6.0" -> Display -> Releases

Then for example SAP Optimizier -> Operating Systems

1.2.2. What deployment / installation options are currently available for SAP TM? (8) ID: 8

Release: Undefined

Status : Answered

Description:

SAP TM is based on Netweaver 2004S. With SAP TM you can also install SAP EM, Analytics, Portal on

the same server. The XI release used is the XI 7.0 release included in Netweaver 2004S.

The deployment scenario is SAP TM (and the listed other services) is "standalone".

This means that SAP TM cannot run on the same system as SAP ERP or an existing SAP SCM system.

The only exception is that SAP TM can run together with SAP EM 5.1 on one instance.

SAP in general allow to install several instances (systems) on the same server. Hence the customer may

decide to install SAP TM together with another instance of software on the same server. This will still not

share any SAP technology and will only use the same hardware. From the SAP TM perspective this

installation is similar to an installation on different servers.

1.3. Installation


2 SAP Internal

1.3.1. Which platforms are supported for the VSR optimizer and the Carrier Selection

(CS) Optimizer? (84) ID: 84

Release: Undefined

Status : Undefined

Description:

The VSR optimizer and CS Optimizer are available as for SAP SCM 2007 and SAP TM 6.0 on Linux and

on Windows plattforms.

Earlier versions of transportation management (TP/VS) are only available on windows. A small customer

development project could be performed to use the optimizers also on Linux.

Support will the be on x64 plattform (Windows und Linux).

Therefore if the SAP TM server is installed on these platforms then the optimizer can run on the same

server. Nethertheless SAP recommends to use a separate optimization server out of performance reasons.

1.3.2. What hardware is required for SAP TM (sizing) (130) ID: 130

Release: Undefined

Status : Undefined

Description:

SAP TM sizing is been created. Please contact Ivan Sesar for details ([email protected]).

1.3.3. How is the software component for the planning engine (optimizer) called? (77) ID: 77

Release: Undefined

Status : Undefined

Description:

The software component for the planning engines is called "SAP SCM OPTIMIZER 5.1". SAP TM will be

using the VSR (Vehicle Scheduling Routing) Optimizer and the TSPS (Transportation Service Provider

Selection) Optimizer (= CS Optimizer).


3 SAP Internal

1.3.4. Can SAP TM installed on the same instance with SAP EWM (71) ID: 71

Release: Undefined

Status : Undefined

Description:

No. See number 8 for details.

1.3.5. Can SAP TM installed on the same instance with APO (72) ID: 72

Release: Undefined

Status : Undefined

Description:

No. See number 8 for details.

1.3.6. Can SAP TM installed on the same instance with an existing SCM system or can

I upgrade an existing SCM system? (4) ID: 4

Release: Undefined

Status : Answered

Description:

No (except for Event Management). See number 8 for details.

1.3.7. Does SAP TM require Live Cache? (5) ID: 5

Release: Undefined

Status : Answered

Description:

No.


4 SAP Internal

2. Features & Functions

2.1. Freight Management

2.1.1. Quick request entry for consignments (Shipment requests) (86) ID: 86

Release: Undefined

Status : Undefined

Description:

SAP TM has a quick entry screen for shipment requests which is specially designed for booking agents who

have to capture shipment requests without further processing it (e.g. call center).

The quick entry allows fast access to the most important data entries of an order.

The system allows the user to toggle between quick entry and normal entry screen during request caturing

and display.

2.1.2. Capturing of incomplete shipment requests (87) ID: 87

Release: Undefined

Status : Undefined

Description:

Shipment requests can be incomplete at request entry time. The booking agent can capture data in the

quality the ordering party can provide it. Request processing can be started with incomplete data for some

functions. Request details can then be completed at a later point in time.

2.1.3. Quote / Quotation entry (88) ID: 88

Release: Undefined

Status : Undefined

Description:

Quotation can ben maintained in SAP TM system using the same user interface as the shipment request.

Most functionalities available for the requests are available for the quotation too. Routing guide requests and


5 SAP Internal

transportation charge requests can be started from the quotation to do an appropriate routing proposal

including price offering for the quotation. The quotation can be communicated to the ordering party via EDI,

fax or mail.

To create a quotation the user selects a different starting transaction in the system.

2.1.4. Shipment Requests templates for easy creation of repeating similar requests (89) ID: 89

Release: Undefined

Status : Undefined

Description:

Shipment Requests can be created as templates which can be basis for regularly incoming shipment

requests. The template is a complete shipment request which can contain already entered data. This data is

the populated into a new shipment request if the template is used for creation.

Use Cases:

Use Case (1)

A customer has weekly container shipments of textiles from Hongkong to Hamburg with a particular

shipping line. The template order can contain ordering party, ship-from, ship-to, shipping condition data,

container data and nature of goods data. Based on this template only the real item description and shipping

dates have to be entered to create a new shipment request.

2.1.5. Automatic assignment of organizational units to requests / order (123) ID: 123

Release: Undefined

Status : Undefined

Description:

A transportation document like a shipment order or a shipment request has to be associated with the

organization and the group that is doing the sales/purchasing of the order. This association of the order to a

group is necessary to allocate the costs/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 etc. The analysis will also lead to better demand forecasting.

In some cases, the sales or the purchasing group may need to be pre defined. For e.g.: a transport from

Hamburg to Munich is always sold by sales office Hamburg. In this case the responsible sales office should

be determined automatically by the ship-from and ship-to location.


6 SAP Internal

In order to provide such a generic framework to define conditions for determining organizational units,

condition technique together with the formula derivation tool (FDT) is used. On the basis of the standard

condition the customer can define in the FDT application his decision table

SAP TM has one pre-defined condition to determine the organisational units (see below).. Please use this

condition if you want to define the assignment of organisational units to the shipment request / shipment

order based on input values from the shipment request / shipment order.

Note: In order to define rules for finding organizational units you need to us the predefined condition:

/SCMTMS/SRQ_ORGUNITS - Organizational units for Shipment Request

/SCMTMS/FRQ_ORGUNITS - Organizational units for Freight Request

/SCMTMS/SOR_ORGUNITS - Organizational units for Shipment Order

/SCMTMS/FOR_ORGUNITS - Organizational units for Freight Order

/SCMTMS/BOR_ORGUNITS - Organizational units for Booking Order

/SCMTMS/HSH_ORGUNITS - Organization units for Shipment

Creating an own condition does not lead to a rules based finding of organizational units

2.1.6. Against which dates is the validity of the Freight Agreement checked? (158) ID: 158

Release: Undefined

Status : Undefined

Description:

The check can get customized.

SPRO -->

SAP Tranportation Management -->

Transportation Management -->

Transportation Charge Management -->

Freight Agreement -->

Define General Settings for Freight Agreement

per OrgUnit (in case of SRQ the Sales Org), WHICH Period Role Code shall be applied for the

determination.

if there is no special role code maintained, I check, if on the SRQ DateTimes a record with RoleCode 34


7 SAP Internal

exists.

if there is no such record on the srq the document creation date is taken.

2.1.7. Additional services during transportation request maintenance. (60) ID: 60

Release: Undefined

Status : Answered

Description:

SAP TM allow you to maintain within the shipment request on header and / or on stage level Transportation

Services. These services will be defined via ServiceRequirementCodes based on EDIFACT.

Information source: http://www.unece.org/trade/untdid/d06a/tred/tred7273.htm

Information for fumigation are maintained on header and / or item level via GovernmentActionCode.

Information source: http://www.unece.org/trade/untdid/d06a/tred/tred9417.htm

2.1.8. Order entry for consignments (shipment request) (63) ID: 63

Release: Undefined

Status : Undefined

Description:

SAP TM has a very powerful order entry screen which is separated into multiple views, addressing specific

aspects of the shipping request (consignment order). From the central order entry screen, all views can be

directly reached. Actions like setting status, doing routing and distance determination, price determination,

printing etc. can be triggered directly from the order view.

Shipment Requests can be maintained in SAP TM via the following:

Manually - User creates manually a SRQ based on fax, email, phone...

EDI - An EDI message is send to SAP TM (using Exchange Infrastructure)

Copy an existing SRQ - User uses a template to copy / create a new shipment request

Integration from ERP deliveries - ERP deliveries can be used to create a shipment request

Webservice using Exhange Infrastructure - Another application can call a webservice and create a shipment

request in SAP TM


8 SAP Internal

The following data can be maintained in the shipment request:

Role-based party information (ordering, ship-from, ship-to,…)

Role-based partner information (carriers, agents,..)

Flexible and extensible datetime definitions (pick-up, delivery,…)

Location and stage information for multimodal shipments (pick-up, POL, POD, final destination,…)

Payment terms and conditions

Freigth terms and conditions

Freight charges (selling prices, buying costs, internal costs)

Texts and notes capturing

Electronic attachments of documents (fax, scan, PDF, etc.)

Dossier functionality - links to all related business documents in TM (waybills, suborders, invoices,..)

Governmental procedure details (e.g. customs information, dangerous goods information, seals information)

Comprehensive cargo details with item specific party information

Packaging details with capability to capture hierarchical packaging

Equipment detail capturing for equipments information given by the ordering party (e.g. FCL container

details)"

2.1.9. Entry of freight request (64) ID: 64

Release: Undefined

Status : Undefined

Description:

Manually

EDI

2.1.10. Entry of Quotation (65) ID: 65

Release: Undefined

Status : Undefined

Description:

A quotation can be manually maintained in SAP TM . A quotation has then same structure as the shipment

request structure (both using the same business object). This quotation can for example be later used to

create a shipment request (copy-from).

A quotation will not be used for planning and execution.


9 SAP Internal

2.1.11. Customer contracts (66) ID: 66

Release: Undefined

Status : Undefined

Description:

Customer contracts are modelled as freight agreements.

2.1.12. Route determination for SRQ (67) ID: 67

Release: Undefined

Status : Undefined

Description:

From the SRQ the route determination can be started.

Please see transportation dispatching and execution for details.

2.1.13. Transportation charge management for SRQ / FRQ (68) ID: 68

Release: Undefined

Status : Undefined

Description:

From the SRQ the charge calculation can be started.

Please see transportation dispatching and execution for details.

2.1.14. Shipment Definition (69) ID: 69

Release: Undefined

Status : Undefined

Description:

The shipment is an object which represents the execution specific aspects of a set of freigt units. A shipment

can be used for documentation purposes, as basis for tracking and tracing of a consignment and for

consignment specific activities like customs declaration.


10 SAP Internal

The shipment is often the basis for printing or electronic transmission of consignment specific bills of lading

(CMR waybill, house airway bill, ocean waybill, etc.). This is especially the case, when the declarative

character of the consignment does not correspond to the logistic character, i.e. when multiple freight units

are reconsolidated for customs declaration purposes.

In SAP TM, tracking and tracing of the execution is initiated on shipment basis.

The shipment can be communicated via the WaybillNotification_Out message. Currently the shipment has

not an inbound interface. The shipment is based on EDIFACT standard IFTMCS.

The IFTMCS is defined in http://www.unece.org/trade/untdid/d06b/trmd/iftmcs_c.htm as:

A message from the party providing the transport/forwarding services to the party that issued the

instructions for those services stating the actual details, terms and conditions (charges when applicable) of

the service and of the consignment involved. In addition it can be used for the exchange of contract

information between carriers mutually.

2.1.15. Confirmation for SRQ / FRQ (70) ID: 70

Release: Undefined

Status : Undefined

Description:

2.2. Transportation Dispatching & Execution

2.2.1. Adaptive Planning (167) ID: 167

Release: Phase 1

Status : Answered

Description:


11 SAP Internal

Adaptive Planning in SAP TM 6.0 and SAP TM 7.0 allows the following:

Within a tour you can have executed and planned activities. Executed activities cannot be changed. For the

non-executed part of the tour (which begins after the (expected) end time of the last executed activity) the

following actions are possible:

1. Add new Stops and Freight Units to the tour (loading of the new freight units must take place in non-

executed part)

2. New Hubs can be used (for delivery of a freight unit to its destination).

3. Remove Stops and Freight Units from the tour (if loading takes place in non-executed part).

4. Planning times and durations can be changed in the non-ETA part)

5. As a result of actions 1.-4., existing PTA can be deleted(unless it is an unloading activity and the

corresponding loading activity is in the executed part), new PTAs can be created (empty run also possible).

6. Trailer, TU Resources, etc. can also be changed in the non-executed part.

Note that the transportation plan resulting from above changes of PTAs must be consistent:

- respect FU constraints, i.e. loading implies unloading

- respect FU constraints source and destination (within planning), i.e. it must be picked up at source and

delivered to destination

- the same time constraints are used as in regular planning

All these steps are also possible for several tours. If new stops and hubs are included in a tour then the

involved freight unit constraints must be completely delivered (to their final constraint destination).

The changes in SAP TM can be performed via the following system functionality:

1. Rescheduling button in planning: Based on the last ETA it will adjust the start/end times of the planned

activities accordingly, if feasible schedule can be determined. Limited to one resource.

2. Planning (manual / optimizer): Will add / remove freight units / stops / new hubs / change / delete / add

planned activities

2.2.2. Determination of the planning profile (124) ID: 124

Release: Undefined

Status : Answered

Description:

Based on the user the planning profile, containing the relevant planning settings, can be automatically

determined. For this purpose condition /SCMTMS/VSR_PROF_DETERMINATION is available.

2.2.3. What is the relationship between the status of a tour and the status of a shipment

order and freight order (161)


12 SAP Internal

ID: 161

Release: Undefined

Status : Undefined

Description:

TM allows the Tour to be set In Execution although a related Freight Order has a status of Unreleased and a

related Shipment Order has a status of Unreleased.

It is possible that a Tour is connected to more than one Shipment Order. The Shipment Orders would be

linked to only a part of the Tour in this case. So, starting the execution of the Tour would not mean that all

the Shipment Orders would also have to be released. It is possible that ETAs of the Tour with which the

Tour starts belong just to one of the other Shipment Orders of the Tour.

Beside this, the Tour shows just the logistical part of TM. It needs not to be linked to Shipment or Freight

Orders from execution status point of view.

2.2.4. Tour (153) ID: 153

Release: Undefined

Status : Undefined

Description:

Tour is a group of consecutive Transportation Activities with similar properties of involved resources. A

Tour can be a result of a planning run as well as manual planning. It is possible to assign multiple activities

which cover same topic in order to easily manage all activities from one tour.

2.2.5. Planned and executed activities (154) ID: 154

Release: Undefined

Status : Undefined

Description:

Planned Transportation Activity (PTA) is a result of transportation planning and represents activities as

loading, transportation, unloading, coupeling and uncoupeling. PTA contains information about resources

(used for execution of the transportation plan) and freight units (e.g. information about loaded, transported

units).

Executed Transportation Activity (ETA) is a result of transportation execution and it is changed whenever

execution information comes to Transportation Management System. ETA contains information about


13 SAP Internal

resources (used for execution of the transportation plan) and freight units (e.g. information about loaded,

transported units).

2.2.6. Selection of resources / vehicles / trailer (145) ID: 145

Release: Undefined

Status : Undefined

Description:

For manual and automatic planning the selected resources can be configured via a profile. For example

standard selection include resource master data attribute and among others the last known location of the

resource.

The last known location can be viewed under Master Data -> Resources -> Select a resource and then select

the tab "Last Activities".

The selection of resources can also be enhanced via an implicit BADI

/SCMTMS/CL_PROFILE_ACCESS=> SELECT_VEHICLES_AND_SCHEDULES. Here the customer

can for example filter on capacity of the resources.

2.2.7. Manual Dispatching (35) ID: 35

Release: Undefined

Status : Undefined

Description:

The system allow the manual creation of planned transports by selecting suitable resources, drivers and

equipment. Freight units can get assigned to resources, containers and / or trailers. The system provides

decision support by checking compartibilites between freight units, resources, drivers, etc and by

considering the capacitiy constraints.

The manual dispatching support unimodal and intermodal planning.

2.2.8. Planning / Optimization (36) ID: 36

Release: Undefined


14 SAP Internal

Status : Undefined

Description:

SAP TM employs a library of advanced, highly configurable planning and optimization algorithms to help

you optimize task-, industry-, and company-specific transportation processes, automate decision making,

and deliver realtime event notifications to the underlying business processes.

2.2.9. Dynamic Route determination / Routing Guide (37) ID: 37

Release: Undefined

Status : Undefined

Description:

Routing decisions have major impacts on service and costs.

The routing guide within the SAP TM application generates feasible transportation plans at the time of order

entry, e.g. shipment request, by determining routes, which freight units to include, the planning horizon, and

which modes, means-of-transport and which equipment to use.

You can view all possible routes based on carriers, capacities, real transportation charges, and lead times,

and then manually choose an option or use predefine strategies to allow automatic selection of the options

that best fit your needs.

The result of the routing guide can be set as constraints for the shipment request, e.g. if the user decides that

a certain hub should be used then this can be saved as a constraint for planning.

You have the option to analyse in detail only the main leg while considering infinite capacity for the other

legs.

2.2.10. Scheduling (38) ID: 38

Release: Undefined

Status : Undefined

Description:

SAP TM support scheduling of transports considering the geographical defined reachability, duration and

distance. Schedules, e.g. sailing schedules, train schedules) and resource availability will get considered

during scheduling.


15 SAP Internal

2.2.11. Carrier Selection / TSP Selection (39) ID: 39

Release: Undefined

Status : Undefined

Description:

Carrier selection functionality helps you determine which transportation service providers you will use to

deliver materials from

their origins to their destinations. SAP TM applies rules for TSP selection, including priority, business share,

and real transportation charges allowing you to base your decision on those factors.

SAP TM uses an optimization technique to help you select

carriers that offer the lowest-cost solution for all shipments. This

technique also considers constraints such as equipment availability

and allocations, customer-specific conditions, and continuous

moves. Constraints limit carriers’ minimum and maximum

number of shipments to specific time periods, geographic locations,

customers, and other factors.

TSP Selection run

- FORs and

- SORs which are not assigned to a FOR

2.2.12. Shipment Order / Freight Order (40) ID: 40

Release: Undefined

Status : Undefined

Description:

SAP TM allow to create manually or automatically a shipment order which represents a purchase order for

transportation services from a transportation service provider that acts as a subcontractor (Shipping

Instruction).

A shipment order can have a list of possible carriers assigned or have the finally selected carrier assigned.

The carrier the list of carriers can be assigned manually or automatically via a planning engine. If tendering

is required then the carrier in the shipment order / freight order is only assigned after the end of the

tendering process.

A Shipment order represents a single consignment and is based on EDIFACT IFTMIN.

A freight order represents a pre-consolidated load from one or more pick-up locations to one or more


16 SAP Internal

destinations and is based on EDIFACT IFCSUM.

A shipment order and a freight order are always unimodal. After all resources are unloaded a new freight

order starts.

2.2.13. Tendering (42) ID: 42

Release: Undefined

Status : Undefined

Description:

A tendering process starts if the user or the system determines more than one possible TSP. This tendering

process can use a mixture of different modes of tendering (peer-to-peer, broadcast or open tendering). To

start the tendering process outgoing transportation orders are created (Shipment order or freight order).The

tendering process results in one TSP being selected for carrying out the transportation activity.

SAP supports different modes of tendering.

Peer-to-peer tendering:

*Sequential tendering to preselected transportation service providers (TSP).

Broadcast tendering:

*Simultaneous tendering to preselected transportation service providers (TSP).

Open tendering:

*Simultaneous tendering to all transportation service providers (TSP) taken from the TSP repository.

These different modes of tendering can be mixed, e.g. you could start with peer-to-peer tendering and after a

defined time-period the system re-tendering. If all peer-to-peer carriers have been asked the system could

swich to broadcast tendering.

This behaviour is controllable via system settings.

Within tendering process a request for quotation is send to the external carrier. The carrier can then make a

quotation to the SAP TM system. The SAP TM system has then a decision support to select the best carrier.

Best can for example be based on costs and / or based on pasted performance.


17 SAP Internal

2.2.14. Continuous Move with Carrier Selection (43) ID: 43

Release: Undefined

Status : Undefined

Description:

The continuous-move option allows you to plan for the use of carriers’ equipment to and from shipping

locations.

2.2.15. Compartment Planning (44) ID: 44

Release: Undefined

Status : Undefined

Description:

Compartment planning within SAP TM allows a very flexible consideration of the compartment restrictions.

Flexible and fixed sized compartments are support while considering incompatibilities, such as restricting

dangerous

goods to certain compartments only

Compartments can be used to plan to concurrently transport different liquids/products (such as grades of

fuel) or for onsolidation of liquid bulk orders from different customers on one truck or trailer.

2.2.16. Freight Space Booking (45) ID: 45

Release: Undefined

Status : Undefined

Description:

SAP TM support the freight space booking, e.g. with an ocean, air or land carrier.

The system supports the sending of electronic booking requests to a variety of carriers instead of using

phone or fax to take

take advantage of data quality checks to avoid input errors.

2.2.17. Execution and Track & Trace (46)


18 SAP Internal

ID: 46

Release: Undefined

Status : Undefined

Description:

The SAP TM allow to print the necessary documents, e.g. B/L and to trace the execution process.

In the shipment-execution stage, SAP EM monitors the important stages of each shipment, as well as the

status of each delivery. The SAP Event Management application collects this data from different sources

and compares it automatically with the planned dates and time lines. The collected information is updated to

SAP TM.

2.2.18. Replanning during execution (47) ID: 47

Release: Undefined

Status : Undefined

Description:

SAP TM supports a replanning during the execution of a transport. If during the execution process a

shipment is deplayed then the system support that manually or via the planning algorihms the transport is

adjusted.

2.2.19. Driver Planning (48) ID: 48

Release: Undefined

Status : Undefined

Description:

SAP TM supports the driver as a separate business object including the modelling of the qualification of the

driver. The planner can manually assign a driver to a transport / vehicle and the system can automatically

check if the driver has the necessary qualification for the transport.

The planning will not support the legal restriction of the working hours of the driver (e.g. maximum working

hours, break regulations, etc.). This is planned to be developed for the second SAP TM release (SAP TM

2008).

2.2.20. Multi-pick/Multi-drop Shipments (51) ID: 51


19 SAP Internal

Release: Undefined

Status : Undefined

Description:

SAP TM support that goods are included in one transport from several pick-up locations as well as the

delivery to several delivery-to locations.

Inbound (purchase) and outbound (sales) can be included in the same transport.

2.2.21. FTL / LTL Decision support (52) ID: 52

Release: Undefined

Status : Undefined

Description:

The system supports the transportation charge based decision of a full-truck load and a less-then-full truck

load.

2.2.22. Intermodal & Cross-Dock Planning (Hub) (53) ID: 53

Release: Undefined

Status : Undefined

Description:

SAP TM support an arbitrary number of hub within a transportation chain during manuall or / and automatic

planning. Hub can be used for cross-docking activities.

This can included a combination of land, see and airfreight modes.

Use Cases:

Use Case (1)

The main leg is performed via a air carrier. The pre-carriage leg is a collection of goods for several

customers delivered via truck to the consolidation warehouse at the airport. The final delivery to the end

customer is again performed via truck

2.2.23. Appointments / Delivery Time Windows (54)


20 SAP Internal

ID: 54

Release: Undefined

Status : Undefined

Description:

SAP TM support the setup of delivery time windows based on an arbitrary classification of customers.

Customers can get classified by any attribute and delivery windows can be defined by customer / customer

group.

2.2.24. In/Compatibilities (55) ID: 55

Release: Undefined

Status : Undefined

Description:

In/compabitilties can be defined and considered:

- Freight Units

- Vehicle and Driver

- Freight Units and Vehicles

- Vehicles and Trailers

- Customer and resources (Vehicles / Trailer)

- Customer and TSP

- TSP and Mean-of-transport

......

2.2.25. Dock scheduling (56) ID: 56

Release: Undefined

Status : Undefined

Description:

Loading and unloading resources / capacity and opening hours can get defined for locations / suppliers /

customers.

2.2.26. Capacity Allocation (57) ID: 57


21 SAP Internal

Release: Undefined

Status : Undefined

Description:

The SAP TM system allows the definition of TSP capacity as allocation. A allocation defines for a number

of time periods the minimum and maximum number or shipments a TSP can perform.

Which an allocation you can define:

1.) Maximum number of shipments a TSP can perform for a giving time period

2.) Minimum number of shipments a TSP should perform for a giving time period

The allocation can be viewed as logistical information about the TSP ability to perform transportation

services and can also be used to setup business rules, e.g. TSP A should only receive 10 orders per month.

In contrast the freight agreement contain the contractual / legal agreement with the TSP.

2.2.27. Container - Master data and handling within the manual dispatching (58) ID: 58

Release: Undefined

Status : Undefined

Description:

The planner can manual configure a container.

A container provides the information what goods can be loaded and the capacity (dimension / units of

measurement )of what can be loaded.

The transported goods require these capacity and the system will check if any capacity restriction is violated.

After the container configuration the planner can manually / automatically plan the remaining transport.

Containers have the following attributes: metrics, e.g. volume, max loading capa, customer specific

attributes (leased, own)

For the carrier the selected container is important information which must be communicated to the carrier.

This would also include the weight of the selected container.

The system should allow the following for the definition of capacity requirements of the container:

- "Additive" = capacity requirement of Container + Sum of capacity requirements of freight units


22 SAP Internal

- "Maximum" = Maximum (capacity requirement of Container , Sum of capacity requirements of freight

units)

- "Direct" = capacity requirement of Container

A mixture of the same unit is also possible, e.g. additive and maximum.

For example this allow the system to model the following scenarios:

1.) Weight of the container is added to the weight of the transported goods

2.) Volumen of the container can be added to the volume of the transported goods

3.) The maximum of the volume of the container and the volume of the aggregated volume of the goods that

will be transported will be taken. This volume settings will be based on a setting on the container (closed

container).

4.) The container is using a certain minimum capacity ("eigenvolumen") plus the maximum of the container

loading volume and the sum of the volume of the freight units.

This can be maintained on the phy. properities of the container master data.

2.2.28. Freight Unit Building Rules (82) ID: 82

Release: Undefined

Status : Undefined

Description:

The freight unit building rules define how shipment / freight requests are transformed into freight units.

Which rule is used for building the freight units is defined via conditions.

1.) The system support different conditions for freight unit building rules

2.) All conditions with the type freight unit building rule will be evalulate

3.) As a result of the FUB condition evaluation several FU Building rules are selected

4.) The FU Building rule with the lowest prio is selected

5.) If several FU Building rules exists the system will select any rule (random selection)

2.2.29. Freight Units (83) ID: 83

Release: Undefined

Status : Answered

Description:


23 SAP Internal

Freight Units are the smallest logistical units which are moved together. Several freight units can be grouped

together for a transportated but the system will not automatically split a freight units.

The basis for the building of the freight units are the shipment requests and freight requests.

2.3. General

2.3.1. I would like to change the behavior of the business objects. It that possible (160) ID: 160

Release: Undefined

Status : Undefined

Description:

SAP TM offers for each business object three enhancements:

- Additional validatons: customer specfic check which are performed after each "Enter" or each action

- Additonal determination: customer specific determinaton of fields in the business objects

- Additonal actions: additional actions in the business objects which can be performed from the user

The BADI can be found under:

SAP Transportation Management

-> Transportation Management

---> Business Add-Ins (BADls) for Transportation Management

-----> Basic Functions

----------> Business Object Enhancement

---------------> Enhancement of Business Object Validation

and then:

Additonal Validation

Additional Determination

Additional Action


24 SAP Internal

2.3.2. Standard roles for SAP TM (170) ID: 170

Release: Phase 1

Status : Answered

Description:

The following roles are pre-defined:

/SCMTMS/BOOKING_AGENTTransportation Booking Agent

/SCMTMS/CHARGE_ADMINTransportation Charge Administrator

/SCMTMS/CHARGE_CLERKTransportation Charge Clerk

/SCMTMS/DISPATCHERTransportation Dispatcher

/SCMTMS/EXECUTION_CLERKTransportation Execution Clerk

/SCMTMS/MANAGER Transportation Manager

/SCMTMS/NETWORK_ADMINTransportation Network Administrator

/SCMTMS/SERVICE_PROVIDERTransportation Service Provider

/SCMTMS/SYSTEM_ADMINSystem Administrator for Transportation

The main role which contains the others is /SCMTMS/MANAGER. A standard user would have this role

assigned to him via transaction su01. A role assignment is necessary for using the Netweaver Business

Client.

2.3.3. Operation in Batch (136) ID: 136

Release: Undefined

Status : Undefined

Description:

SAP TM can operate in Batch and the following reports are provided:

/SCMTMS/OM_PREP_BATCH (Order Management Preparation Batch Processing)

/SCMTMS/CONF_EXEC_BATCH (Confirmation / Execution Batch Processing)

/SCMTMS/SUBCONTRACTING_BATCH (Subcontracting Batch Processing)

/SCMTMS/VSR_OPT_BGD (Planning)

/SCMTMS/TSPS_BACKGROUND_PLAN - Tendering


25 SAP Internal

2.3.4. Support of all modi / means of transport (50) ID: 50

Release: Undefined

Status : Answered

Description:

The SAP TM system is designed to support all modi / means of transport.

This includes land, sea, rail and airfreight.

2.3.5. Print document (61) ID: 61

Release: Undefined

Status : Undefined

Description:

SAP TM deliveries standard form for the most important print documents (for a list see below). Customers

can adjust the delivered print documents and also include include additional customer specific print

documents.

The SAP TM printing uses PDF forms based on ADOBE technology.

Documents can be printed manually or automatically

Printing triggered by business partner dependent (Shipper, Carrier, Consignee, ...) settings in case of

document status change.

SAP TM determines the means of communication (Print, Email, Fax) from the setting ‘Standard

Communication Method’ in the central address management of the derived business partner

The following business objects can print the following documents:

-----------------------------

Shipment Request:

Freight Forwarding Order document (FIATA Forwarding Instruction = FFI) - incoming

Confirmation of Freight Forwarding Order document (FIATA Forwarding Instruction = FFI)

Shipment:

House Sea Bill Of Lading based on UNECE Standards

House Air Waybill document based on IATA Standards

Road Waybill Document based on CMR Standards (with own trucks)


26 SAP Internal

Road Waybill Document based on VICS Standards (with own trucks)

Multimodal Transport Bill of Lading based on FIATA Standards

Labels

Shipment Order:

Freight Forwarding Order document (FIATA Forwarding Instruction = FFI) – outgoing

Road Waybill Document based on CMR Standards (with ordered trucks)

Road Waybill Document based on VICS Standards (with ordered trucks)

Master Air Waybill document based on IATA Standards

Master Sea Bill Of Lading based on UNECE Standards

Freight Order

Shipping Manifest

--------------------

2.3.6. Organization Units and Business Partners (128) ID: 128

Release: Undefined

Status : Undefined

Description:

SAP TM supports the creation of the organizational units for sales and purchasing. Everytime a organization

unit is created a business partner is automatically created.

For business objects which have to be paid by internal parties these business partners used for the

organization units can be used. These business partners can be found in transaction BP. The BP is found by

the search term of the organizational units (the number for the business partner is automatically created).

2.3.7. Printing of Barcodes (141) ID: 141

Release: Undefined

Status : Undefined

Description:


27 SAP Internal

Print Dokumente with barcodes can be created with the Adobe Lifecycle Designer which is integrated into

the SAP development environment (Transaction SFP). Adobe deliveres several barcode standards which

can be integrated into the print documents.

SAP TM has in the standard the barcode integrated into the packaging label (printed from the shipment).

2.4. Transportation Charge Management

2.4.1. TCM Functionality Overview (91) ID: 91

Release: Undefined

Status : Undefined

Description:

Efficient freight rating and the settlement with customers and subcontractors is one of the most important

parts in an end-to-end logistics process and integrates logfistics data with financial data.

Transportation Charge Management consisted of 5 elements

1.) Transportation Charge Calculation (Freight Rating and Costing): The determination of relevant freight

rates, assessorial charges, other surcharges and discounts for the selling (debit) as well as the buying (credit)

side for all modes of transport such as trucking (land transport), rail, sea, air and inland vessel cargo (barge).

2.) Customer Freight Invoicing (Customer Billing): Charging the customers (e. g. shippers, consignees) for

the transportation and other services

3.) Supplier Freight Invoicing (Subcontractor Settlement): Freight auditing & payment of costs for a

transportation service to the subcontractor (carrier or other 3rd parties)

4.) Inter- and intra-company Billing: Invoicing affiliates and allocating cost centers to be charged with

freight costs deriving from a transport or other services

5.) Financials Integration: Financial Accounting and Controlling (via SAP ERP)

2.4.2. Transportation Charge Calculation (92)


28 SAP Internal

ID: 92

Release: Undefined

Status : Undefined

Description:

The Transportation Charge Calculation determines the following:

- Determination of Selling price

- Determination of Buying Costs

- Determination of Internal Costs (own operating costs)

2.4.3. Are there standard capabilities to re-rate transportation charges based on either

time or a trigger (164) ID: 164

Release: Undefined

Status : Undefined

Description:

The transportation charges are automatically re-rated at the time of creating the invoices (CFIR/SFIR). By

doing this, the invoice gets always the latest calculation values (manual changes are certainly considered).

We have a batch report (/SCMTMS/CONF_EXEC_BATCH for order processing and

/SCMTMS/SUBCONTRACTING_BATCH for the subcontracting part.

2.4.4. Automatic calculation / determination of freight charges (93) ID: 93

Release: Undefined

Status : Undefined

Description:

TCM determines the freight charges based on transactional data, master data and defined rules.�

The result of the calculation can be manually influenced by the user according to his authorization (override,

add or remove charges).

2.4.5. Freight Agreements for Customers and Third Party contracts (94) ID: 94

Release: Undefined

Status : Undefined


29 SAP Internal

Description:

Freight Agreements contains contractual data (like contractor, contracting parties, validity, payment terms,

limits, other agreement information and attachments)

Freight Agreements can be maintained in SAP TM:

- Creating

- Retrieving

- Updating

- Deleting

Copying of Freight Agreements

It is the central object for maintaining and evaluating the tariffs, tariff charge calculation sheet, scales and

the negotiated freight rates

It can contain one or multiple Tariffs which are the pointer to the freight rates

2.4.6. Maintenance of Rate tables (95) ID: 95

Release: Undefined

Status : Undefined

Description:

Creating, Retrieving, Updating, Deleting and Copying of Freight rates.

Rates can be maintained as basic freights, assessorial charges, other surcharges, discounts or taxes

Freely definable access levels. The rates can be defined at any level. A level corresponds to the key fields

(parameters like customer, carrier, Tariff Zone, locations, zones, service level, freight class, dangerous

goods glasses) for the access to a rate. �The fields can reference to all available business objects (Shipment

Request, Freight Request, Shipment, Shipment order, Freight Order, Planned and execution activities and its

attributes.

Values can be maintained according to a scale. Multi-dimensional scales are supported (up to 9 dimensions,

e. g. milage / weight based)

Rates and rate tables can be maintained directly in SAP TM. Individual rates can also be uploaded or

downloaded via Excel. It is currently not possible to upload TCM master data (scales / rates / charge sheets /

freight agreements) via a generic interface.


30 SAP Internal

2.4.7. Scales (96) ID: 96

Release: Undefined

Status : Undefined

Description:

Scales are the axis of rate tables. Their dimensions can be configured flexible according to values,

quantities, volumes, weight, distances, points and others

The scales can be maintained independently of the Freight Agreement and rates and reused in any rate.

2.4.8. Reusage of Rates and Scales (97) ID: 97

Release: Undefined

Status : Undefined

Description:

Tariffs, Scales and rates can be maintained independently of the Freight Agreement and reused.

2.4.9. Transportation Charge Calculation Sheet (98) ID: 98

Release: Undefined

Status : Undefined

Description:

The Transportation Charge Calculation Sheet defines the charge elements relevant for the calculation and

the sequence in which the system takes these elements during calculation into account

Can be defined for each tariff differentially.

2.4.10. Determination of Freight Agreements, tariffs and rates (99) ID: 99

Release: Undefined

Status : Undefined

Description:


31 SAP Internal

Determination of Freight Agreements, tariffs and rates are based on freely definable preconditions and

therefore very flexible. Practically every logistical information of Business Objects and Master data can be

used for influencing the calculation.

2.4.11. Determination of contribution margin and analysis of the transportation

profitability (100) ID: 100

Release: Undefined

Status : Undefined

Description:

To maximize the profitability the sales price and buying costs are determined at runtime and always visible

in the Shipment Request, Freight Request, Shipment and Customer Invoice. The profitability is calculated

based on the sales price and buying costs.

2.4.12. Incoterm split (101) ID: 101

Release: Undefined

Status : Undefined

Description:

Ability to invoice different partners (e. g. shipper and consignee) according to the Incoterm.

2.4.13. Multi-Currency (102) ID: 102

Release: Undefined

Status : Undefined

Description:

Multi-Currency is supported.

2.4.14. Exchange Rates (103) ID: 103

Release: Undefined

Status : Undefined

Description:


32 SAP Internal

Exchange Rates can be automatically determined or manually defined

2.4.15. Pricing analyses Tools (104) ID: 104

Release: Undefined

Status : Undefined

Description:

Pricing analyses Tools enable the evaluation of the calculated values

2.4.16. Integration in the whole SAP TM process (105) ID: 105

Release: Undefined

Status : Undefined

Description:

Entire Integration into the logistic part of SAP TM is assured, e. g. the routing decision and the Carrier

Selection can be based on real costs

2.4.17. Examples of Freight Rates and calculation methods (106) ID: 106

Release: Undefined

Status : Undefined

Description:

Weight / Volume rates

Break weight calculation

Volumetric rate calculation (Bulkiness factors)

Rates based on quantity, distance, length, height, time, values, weight classes, etc.

Freight all kind / Commodity rates

Geography based rates�Various origin / destination point classifications such as point-to-point, point-to-zip,

point-to-state, postal-code-to-postal-code, zip-to-zip and state-to-state

Rates based on Equipment (container type / size), packaging classes or numbers of handling units

Rates based on dangerous goods classes

Rates based on service levels

Cost per stopover

Insurance

Handling charges


33 SAP Internal

Terminal handling, Cross docking, Loading / Unloading, Empty handling, Document handling, AMS filing,

Canal due, ISPS Security surcharge, etc.

Surcharges

Bunker adjustment, Currency adjustment, Congestion, Demurrage, Night time deliveries, Notification

charge, Hazardous surcharge, Waiting time, Feeder Costs, low tide surcharge, port congestion, etc.

Minimum, Maximum rates

The setup of the charge element requires configuration of the system.

2.4.18. Customer Freight Invoicing (Customer Billing) (107) ID: 107

Release: Undefined

Status : Undefined

Description:

Ensures correct billing, which reduces customer complaints.

The following functionality is supported:

Triggers Execution of the Billing Process in ERP

Creating, Retrieving, Updating and Deleting Customer Freight Invoicing Object (billing preprocessing)

with reference to Shipment Requests, Freight Requests and Shipments

Collective processing and manual processing.�Rule-based collective processing can be started to run online,

for a specific later date (e. g. during off-peak hours) or at periodic intervals (e. g. daily, weekly, fortnightly,

monthly) in background

Collective invoice (items pertaining to several preceding documents are billed together) or �single invoice

The preprocessing of the customer billing and the customer billing itself is decoupled, which enables the

integration of any ERP system (SAP, legacy or third party system).

Transfer to the customer billing document in ERP

Issue Credit and Debit Notes

Partial Billing

Internal Billing to own Companies (Affiliates) / Profit sharing (ERP based)


34 SAP Internal

Calculation of Profit share, Inter-company billing as well as intra-company billing is supported

Simple Credit Limit Check

Blocking of Customer Master

A maximum limit of sales can be defined in the Freight Agreement and is checked during order entry.

Issue Invoices in multiple formats (e.g. EDI, Print, Email.)

Invoice list lets create, at specified time intervals or on specific dates, a list of billing documents (invoices,

credit and debit memos) to send to a particular payer (SAP ERP)

Monitoring functions facilitates the administration of the customer freight invoicing

Financial Accounting (e. g. A/R)�Account assignment can be carried out at different levels, depending on

how detailed the costs should be tracked. (SAP ERP)

Revenue Assignment and Revenue Distribution (SAP ERP)

Payment Control (SAP ERP)

Payment Difference Handling (SAP ERP)

-> prerequisite: coupling with ERP-FI/CO, several listed activities takes place in ERP, some (but not all) of

this activiites are markted with SAP ERP

2.4.19. Supplier Freight Invoicing (Supplier Settlement) (108) ID: 108

Release: Undefined

Status : Undefined

Description:

Reduce costs by detecting incorrect carrier invoices

Trigger Execution of the settlement process

Creating, Retrieving, Updating and Deleting Supplier Freight Invoice Object with reference to Shipment

Orders and Freight Orders

Collective processing and manual processing.�Rule-based collective processing can be started to run online,


35 SAP Internal

for a specific later date (e. g. during off-peak hours) or at periodic intervals in background

Collective (items pertaining to several preceding documents are billed together) or�single invoice

Transfer to service entry sheet in the ERP system �Creating worklists for invoice verification

Posting of costs and accruals:�Assignment and forwarding of transportation charges to financial and cost

accounting for creation of accruals.

Advance Payment of Installment

Invoice Verification: The invoice verification can be executed in the ERP system when the invoice of the

carrier is received. The carriers invoice is validated against the expected costs. If there are differences,

exceeding predefined tolerances (general or vendor-specific), the invoice is blocked for payment. Otherwise

the system automatically posts the invoice document and these trigger the payment to the subcontractor.

Automated Self Billing (ERS Procedure): The freight costs can be settled with carriers automatically

without having received invoices from them via a credit note (SAP ERP)

Posting of subsequent debit and credit notes

Monitoring functions facilitates the administration of the supplier freight invoicing.

Internal Settlement from own Company Affiliates / Profit sharing�Calculation of Profit share, Inter-company

Settlement as well as intra-company settlement is supported

Partial Supplier Payment

Financial Accounting�Determination of the correct general ledger (e. g. A/P)

Cost Assignment and Cost Distribution: Distribution of freight costs according to the allocation-by-cause

principle

Difference Handling of Invoice Posting

-> prerequisite: coupling with ERP-FI/CO, several listed activities takes place in ERP, some (but not all) of

this activiites are markted with SAP ERP

2.4.20. Simple Credit Limit Check (109)


36 SAP Internal

ID: 109

Release: Undefined

Status : Undefined

Description:

In SAP TM a simple credit limit check is provided, via:

-Blocking of Customer Master

-A maximum limit of sales can be defined in the Freight Agreement and is checked during order entry

2.5. Analytics

2.5.1. What is the standard BI content provided in SAP TM? (119) ID: 119

Release: Undefined

Status : New

Description:

SAP TM delivers BI Content based on BOs:

shipment request

shipment order

shipment.

KPI: number of business transactions, net weigh, gross weigh, gross volume

Characteristics: Party (e.g. consignee, shipper, ordering party, bill-to); Locations, Terms (Incoterms, Priority

Codes).

For shipments SAP also delivers data for transport stages: mode of transport, means of transport, transport

resource.

For details on the available BI content please check the RKT material (how to find the RKT material ->

FAQ item 139)

2.5.2. What is the reporting strategy for SAP TM (127) ID: 127

Release: Undefined

Status : Undefined


37 SAP Internal

Description:

SAP TM will contains flexible lists (in form of the personal object working list) which will allow the user to

select data and view data.

Any additional reporting will be performed in SAP BI either an external BI system or internal in the SAP

TM system. SAP TM will provide standard BI content and extractors and the customer is free to create

additonal BI content.


38 SAP Internal

3. General

3.1. Overview

3.1.1. What is SAP TM? Please give a short overview about what SAP TM is? (111) ID: 111

Release: Undefined

Status : Undefined

Description:

Transportation management includes all activities related to the physical transport of goods from a certain

location to another location.

SAP TM is the integrated SAP software solution for all transportation related activities, including:

•Transportation request capturing

•Rough-cut transportation dispatching and scheduling

•Detailed transportation dispatching and scheduling

•Subcontracting of carriers and tendering

•Transportation charge calculation for the supplying and buying side

From a business perspective, the key functionalities for SAP TM are:

•Determination and ongoing monitoring of the most efficient transportation plan

• Fulfilment of the given constraints (such as costs, and resource availability).

•Identification of opportunities for cost savings (such as consolidation possibilities)

•Maximization the utilization of existing resources (such as using your own fleet).

•Ability to react on execution events and provide efficient solutions

3.1.2. In which process steps can SAP TM be separated? (112) ID: 112

Release: Undefined

Status : Undefined

Description:

Processing Transportation Requests in SAP TM

Planning and Executing Transportation Requests in SAP TM

Managing Supplier Transportation Charges in SAP TM

Managing Customer Transportation Charges in SAP TM


39 SAP Internal

3.1.3. Does SAP TM has a direct integration to the SAP ERP Oil & Gas solution (TD

shipment). Does SAP TM handle loss and gain? (159) ID: 159

Release: Undefined

Status : Undefined

Description:

No such a mapping needs to be build in a customer project. SAP TM does not keep track of stocks therefore

is does not handle loss and gain.

3.1.4. Where can I find the official SAP TM 6.0 documentation? (137) ID: 137

Release: Undefined

Status : Undefined

Description:

SAP Library (Online Help) for SAP

The documentation is available in German and English.

http://help.sap.com/

-> SAP Business Suite -> SAP Supply Chain Management -> SAP Transportation Management

SAP Library (Online Help) for Enterprise SOA

The documentation is available in English.

http://help.sap.com/

Enterprise SOA -> SAP Supply Chain Management -> Enterprise Services for SAP TM

Master Guide and Solution Operation Guide

These guides are available in English.

http://service.sap.com/instguides

-> SAP Business Suite Applications -> SAP SCM -> SAP TM -> Using SAP TM 6.0

Security Guide

This guide is available in English.

http://service.sap.com/securityguide -> SAP Transportation Management

SAP Solution Manager Content

In SAP Solution Manager, you can find process descriptions and configuration documentation based on SAP

TM 6.0. In addition, you can also find scenario descriptions and configuration documentation for industry

scenarios based on SAP TM 6.0. You can display the Solution Manager content in system SLQ in


40 SAP Internal

transaction SOLAR_LIBRARY.

SAP Solution Manager content is available in English.

The scenario can be found under Solution / Applications -> SAP for Logistic Service Provider -> Scenarios

-> Freight Forwarding

Service Marketplace

The Service Marketplace contains new content on SAP TM 6.0. Customers / Partners can refer to this site:

http://service.sap.com/scm -> New: Transportation.

3.1.5. Where can I find additional SAP TM 6.0 Information? (139) ID: 139

Release: Undefined

Status : Undefined

Description:

Using the SAP Service Marketplace (Link http://service.sap.com/scm-tm), you get SAP TM 6.0 related

information. Via the Sapnet you can use /go/RKT and then /rkt-scm. Select then SAP SCM 2007 -> SAP

Transportation Management 6.0.

You can access the personalizable Online Learning Map with prioritized content, which will support you

with all the knowledge you need for your SAP TM 6.0 project.

Learn what you need

SAP Tutor simulations, hands-on guides, detailed presentations and other documents

Prepare for your project

Scenario and process documentation, implementation and configuration guides with related links to the SAP

Library help portal. How-to-Guides for implementing SAP TM.


41 SAP Internal

3.1.6. Where do I find the internal SAP sales kit for SAP TM 6.0 (143) ID: 143

Release: Undefined

Status : Undefined

Description:

The SAP TM 6.0 sales kit can be found for SAP employees under the following link:

https://portal.wdf.sap.corp/irj/go/km/docs/corporate_portal/WS%20PTU%20Applications/PTU%20Apps%2

0Units/SCM%20PLM%20Manufacturing/ASM%20SCM%20PLM%20Man/SCM/Programs/SCM/Roll-

Out/SCM%20Roll-Out%20Map%202007.htm#SAP_TM_60_SalesKit

3.1.7. What is included in the Processing Transportation Requests in SAP TM? (113) ID: 113

Release: Undefined

Status : Undefined

Description:

Overview:

Within SAP Transportation Management (TM) transportation requests can be received, updated and

confirmed.

Purpose:

This business process is carried out to capture and evaluate transportation requests. These transportation

requests are the basis for the transportation planning and execution. Transportation proposals can to evaluate

possible paths through the network and transportation charge calculation can pre-evaluate the transportation

charges for the customer.

Detailed Description:

The logistics process in SAP TM starts with an incoming transportation request.

A transportation request represents a customer order to move goods from one location to another. SAP TM

supports two different types of transportation requests, the shipment request (close to the IFTMIN standard)

and the freight request (close to the IFCSUM standard).

The shipment request represents a customer order to ship goods from a source to a destination location while

the freight request represents a customer order to ship goods from multiple sources to multiple destination


42 SAP Internal

locations.

The transportation request contains the business data send by the customer including information how the

customer expects the handling of this transportation request.

Transportation requests can be received via open interfaces, such as Electronic Data Interchange (EDI) or

Web Services, as well as other common means of communication, such as email, fax or phone. The requests

can then be maintained in the system.

In addition to the integration from above SAP TM can be closely coupled to an existing SAP ERP system.

SAP ERP a standard mapping for ERP deliveries to shipment request in SAP TM is available.

Once the transportation requested have been captured the user may create transportation proposals to

evaluate possible paths through the transportation network and to pre-select certain paths though the

network which will be later constraints for the planning.

In the transportation management system the transportation network (geography) defines the possible

transportation ways. For example if a transport can be performed directly from the sending to the receiving

location or if this transport request must be transported via a transhipment point (hub) is defined by the

transportation network.

During the determination of transportation proposals the user can define additional constraints for the

transportation request, for example, based on the result of the transportation proposal the user may decide

that the order must be delivered via the harbour in New York.

The user can also run a transportation charge calculation (freight cost calculation). This can either be used

for evaluating the costs or for confirming the final transportation charges for the customer (freight billing).

The processing of transportation requests pertains to their screening (validated), adjustment (error corrected,

additional information is placed in the document) and confirmation. This last step is an optional step, which

can also be carried out at a later stage.

Credit checks can be performed for a transportation request within SAP TM.

After evaluation of the transportation request the user can send the customer a confirmation of his request.

This is also possible during a later stage of the process.

3.1.8. What is included in Planning and Executing Transportation Requests in SAP TM

(114) ID: 114

Release: Undefined


43 SAP Internal

Status : Undefined

Description:

Overview:

Based on the transportation requests maintained in SAP Transportation Management (TM) optimal

shipments are created. SAP TM offers multiple tools to create and manage the planning processes like best

in class optimization, dynamic routing and scheduling and continuous move optimization For creating the

shipments, the system uses the transportation charges and freight agreements., considering resource,

equipment and carrier availability at the same time. This process is known as Planning and Executing

Transportation Requests in TM.

This business process is carried out to create and execute the business objects that are required for driving

the transportation execution process, thus enabling margin maximisation.

Details:

Basis for the planning are the freight units (logistic planning units). The system reads the incoming

transportation requests and transfers them by means of the freight unit builder into freight units.

Freight units are non-separable units, which are transported together over the whole transportation chain.

The freight unit builder takes into account the maximum order size and available vehicle capacity.

After the freight units have been created, the transportation activities can either be created manually by the

user or automatically by the system. The system uses sophisticated planning algorithms (optimization)

depending on the business scenario. The planning activities can optionally be grouped into individual tours.

The freight units and transportation activities are grouped to loads and assigned to resources (such as trucks

or railcars).

The availability of drivers can be manually checked and drivers can be assigned to the resources. The

system automatically checks the qualification of the drivers required by the different resources.

If external transportation service providers (TSPs) are used, that is if a certain stage of the transportation is

subcontracted to an external TSP, they can be determined either manually or automatically by using the

transportation charges maintained in the system.

A tendering process starts if the user or the system determines more than one possible TSP. This tendering

process can use a mixture of different modes of tendering (peer-to-peer, broadcast or open tendering). In the

system, a timeout can be defined, so that the system will re-tender the transportation activity to another TSP


44 SAP Internal

or so that the system can switch from one mode to the next mode of tendering. The tendering process results

in one TSP being selected for carrying out the transportation activity.

Once the TSP has been selected, outgoing transportation orders are created. The Freight Order (IFCSUM)

and the Shipment Order (IFTMIN) are freight purchase orders to procure transportation services.

Orders for the same TSP are consolidated to get a better rate with the TSP and to get a continuous move

discount.

The purchase orders determine the business view of the supplier and the information structures in which the

supplier sends the invoice. This transportation order will be communicated to the carrier via EDI or via Fax/

Email.

After finishing the planning activities the transportation execution process starts.

During the transportation execution process in SAP Transportation Management:

•the transportation document is printed

•the status of executed activities is tracked

•shipments that are in execution are adjusted

•the confirmation of the completed execution is received

The integration with other systems, such as a customs management system or a warehouse management

system, can occur during the execution process.

Re-planning occurs several times, hence the cycle of planning and execution needs to be repeated.

3.1.9. What is included in Managing Supplier Transportation Charges in SAP TM

(115) ID: 115

Release: Undefined

Status : Undefined

Description:

Overview:

The transportation charges are calculated in SAP Transportation Management (TM) for the involved

business partners on the supplying side. This calculation is based on the outgoing transportation orders. The

involved business partners are supplying parties, such as the transportation service providers and / or

carriers. This process is known as Managing Supplier Transportation Charges in SAP TM


45 SAP Internal

This business process is carried out to evaluate, calculate, and distribute the transportation charges for the

supplying side. This enables the financial transactions for supplier invoicing.

Details:

The transportation charge calculation for the supplier is based on the outgoing transportation orders and it

allows a clear visibility of the costs for the outgoing transportation order level.

During the calculation the cost for the involved business partners is calculated using a central transportation

charge engine.

The user or the system starts the calculation of the supplier freight invoice request.based on one or several

shipment orders or freight orders.

The freight agreement defines if a valid business relationship exists. The freight agreement is the master data

element, which represents the information about the contract between the company the user is working for

and the supplier.

If a valid business relationship exists, the applicable rating table within the freight master data is determined

using logistics input parameters, such as the weight, the distance, or the mode of transport.

The calculation of the transportation charges are influenced by the transportation activities, the freight units,

the shipments orders, and the freight orders as well as certain master data elements.

The data collected from these elements is necessary to correctly calculate and settle the transportation

charges. The collection of the data is performed with the Transportation Charge Processing Request.

With this information the Transportation Charge Processing Request can call the Freight Calculation

Engine, which determines the final transportation charges by applying the agreed rules of calculation (for

example, break-weight calculation, bulkiness, or exclusions).

The result of the transportation charge calculation is saved in the Supplier Freight Invoicing Request.

The Supplier Freight Invoice Request represents the business view of the supplier. The structure and content

of this object refer to the transportation order (freight/shipment order) as well as to the freight agreement

between the company and the transportation service provider (credit side).

The Supplier Freight Invoice Request supports the integration with any ERP system by providing data in an

XI message. Accruals expecting invoices from the suppliers are posted. In the ERP system the invoice

creation and the invoice verification or the supplier self-billing takes place.

For the supplier self-billing (Evaluated Receipts Settlement - ERS) can be used or the SAP TM user

performs an invoice verification after he receives the final invoice from the supplier.


46 SAP Internal

3.1.10. What is included in Managing Customer Transportation Charges in SAP TM?

(116) ID: 116

Release: Undefined

Status : Undefined

Description:

Overview:

The transportation charges are calculated in SAP Transportation Management (TM) for the involved

business partners on the ordering side. This calculation is based on the incoming transportation requests. The

involved business partners include the ordering party, the consignee, and the shipper. This process is known

as Managing Customer Transportation Charges in SAP TM.

Evaluate, calculate and distribute the transportation charges for the ordering party. Enable the financial

transactions for customer billing.

Details:

The transportation charge calculation for the customer is based on the incoming transportation requests, and

allows clear visibility of the margin at the incoming transportation request level.

During the freight calculation, the cost for the involved business partners is consistently calculated using one

central transportation charge engine. The calculated freight costs are integrated into the ERP system where

the customer billing document (customer invoice) is created. ,

The shipment and freight request, the activities, freight units and the shipments are the data structures that

influence the calculation of the freight costs as well as certain master data elements.

The transportation charge calculation for customer follows the same process when then transportation

charge calculation for suppliers. The result for the transportation charge calculation for customer will result

in a Customer Freight Invoice Request.

The subject area Customer Freight Invoice Processing supports integration with any ERP system by

providing data in an XI message. For instance, the SAP ERP SD integration layer for FCM uses the

transferred data to account and bill the freight service with complete integration with FI/CO.


47 SAP Internal

3.1.11. How would an example shipper process who is using SAP TM would look like?

(117) ID: 117

Release: Undefined

Status : Undefined

Description:

The shipper would create sales order in SAP ERP. These sales orders are used to create deliveries in SAP

ERP.

The deliveries from SAP ERP are send to SAP TM via IDOCs / XI and create Shipment Requests in SAP

TM. From these shipment requests the freight units would be automatically or manually created using a rule

set. Freight units are the smalled logistical units which are undividable transported together.

The freight units are the basis for planning. The system (optimizer) or the user creates a transportation plan.

The transportation plan is created based on the selected FU's, vehicles / capacity reserverations and the

relevant geography. The result of the planning are activities (load, transport, unload) and tours. Tours are a

logical grouping of activities based on a rule set.

If the shipper uses external carriers / TSP's he can manual or system supported create the shipment orders /

freight orders. These orders are the order to an external party to perform a certain part of the transportation

activities. If the carrier is not yet determined for the shipment order / freight order a tendering process can be

started which will result in an update of the shipment order / freight order with the associated carrier.

The shipper create a shipment which is used to create the print documents and for the track and tracing via

Event Management. This can be done before the shipment order / freight order creation or after.

Based on the shipment / freight requests and the execution information the transportation charges for the

customer are calculated. This is only performed if the shipper will bill the service of transportation to

someone, e.g. another internal organization.

Based on the shipment / freight orders and the execution information the transportation charges for the

carrier / TSP's are calculated.

The transportation charge information is integrated back to SAP ERP and and can be used for for the invoice

verification / ERS in SAP ERP.


48 SAP Internal

Use Cases:

Use Case (1)

Shipper has its own fleet. He does not create shipment orders / freight orders.

Use Case (2)

Shipper has no own equipment. He performs the planning based on capacitiy reservations (booking order)

and based on external resources. After planning he creates shipment / freight order and selects the best

carrier via a tendering process.

Use Case (3)

The shipper uses a rule set that all shipment requests which is on the same pick-up and delivery date are

placed within one freight unit and therefore will be transported together.

Use Case (4)

The shipper uses a rule set that all shipment requests which is on the same pick-up and delivery date and

consolidated. Freight units are created for the consolidated quantities whereby a new freight units is created

after 20 tons or 20 m3 have been reached. This will ensure that the freight unit does not exceed the truck

capactiy.

3.2. General

3.2.1. What reference model is used on SAP TM? (135) ID: 135

Release: Undefined

Status : Undefined

Description:

SAP TM does not use an explicit modelling of the processes. The business objects of SAP TM are modelled

in the business object processing framework.

3.2.2. Why is feature X / system Y not included in the scope? This is the most

important feature / system. (13)


49 SAP Internal

ID: 13

Release: Undefined

Status : Answered

Description:

ASM (Application Solution Management) is very closely working with the industries and development,

field organizations and customer influence councils to prioritize requirements and define, based on the given

budget, the next steps for the solution enhancements in a collaborative way.

The ASM is capturing the business requirements and decides together with the different stackholders what

will be develop in the next release.

3.2.3. Which volume is expected to get handled by SCM TM? (16) ID: 16

Release: Undefined

Status : Answered

Description:

Currently the performance tests have not been conducted therefore a binding statement can not be issued.

We assume that a medium sized system will not have problems to handle transportation requests which will

result in 5000 shipments per day.

3.2.4. How will we integrate to SCM APO in the future (19) ID: 19

Release: Undefined

Status : Answered

Description:

The currently plan is to integrate to SCM APO based on SAP ERP. So the customer would send his orders

to SAP ERP and then from SAP ERP the orders would be send to SAP TM. SAP is planning to have a

tighter, direct integration between SCM APO and SCM TM in the future but at this point in time we cannot

confirm any development.

3.2.5. What does abbreviation XXX mean? What are the offiziell names for the

transportation components in SAP? (21) ID: 21

Release: Undefined

Status : Answered


50 SAP Internal

Description:

SAP APO TP/VS (SAP Advanced Planning & Optimization – Transportation Planning & Vehicle

Scheduling)

SAP ERP LES (SAP Enterprise Resource Planning – Logistics Execution System)

SAP TM (SAP Transportation Management)

SAP EM (SAP Event Management)

SAP ERP Enhancement Package (EHP)

SAP Customer Relationship Management (SAP CRM)

SAP Global Trade Services (SAP GTS)

SAP NetWeaver Business Intelligence (SAP NetWeaver BI) - Formerly named SAP Business Intelligence

(SAP BI). Includes the functionality of the predecessor component SAP Business Information Warehouse

(SAP BW).

All components will be officially called without versions.

The SAP TM release which will be released 2007 will be called SAP TM 6.0.

3.2.6. Does SAP TM support simulation / modeling (simulation version simular to

APO)? (118) ID: 118

Release: Undefined

Status : Undefined

Description:

No. SAP TM is designed for running the full transportation activities. It is not a tool for simulating

alternative transportation network models. For simulation and subsequent evaluations, we recommend to use

the SAP BW. This is not standard content in BW, but could be modeled.

SAP TM does of course support different optimization settings hence planning with alternative settings,

alternative evaluation or possibilities for the orders via the routing guide, etc. but it is not possible to

replicate the transactional and master data to perform strategic simulations.

3.2.7. Which languages are supported by SAP TM / unicode (28) ID: 28

Release: Undefined

Status : Answered

Description:


51 SAP Internal

SAP TM is unicode compliant.

For the supported languages in SAP TM 6.0 check the note 940714. Currently the following is supported:

EN

DE

FR

JA

RU

As of SAP TM 6.0 SP7 in additional the following will be supported:

IT

ES

A translation to additional languages might be possible but internal costs of approx. 50 000 Euro would

occur. These costs would have to be paid by the requesting party. Translation in the following languages

would be possible:

CZ

ES

DK

FI

FR

HU

IT

NL

NO

PL

BR

RU

SE

TR

GR

IL

HR

KR

TH

CN

TW

For other languages please check with ASM.


52 SAP Internal

3.2.8. SAP TM is using Webdynpro for ABAP. Can I also use Webdynpro for Java to

create customer / partner specific screens. (31) ID: 31

Release: Undefined

Status : Undefined

Description:

SAP does recommend to to use Webdynpro for ABAP to extend the SAP TM release.

Using Webdynpro for Java is possible but technical complicated.

The Java-Stack calls with a remote access to the ABAP-Stack. The technical interface for the Business

Objects is called the Local Client Proxy (LCP) The SAP TM LSP is not remote enabled hence the customer

/ partner needs to create the corresponding remote function modules. Also F4 help can not be used.

3.3. Organisational

3.3.1. What is the planned maintenance for SAP SCM TP/VS? Are there planned

functional improvements for SAP SCM TP/VS? (125) ID: 125

Release: Undefined

Status : Undefined

Description:

SAP TM will be the transportation solution in which we will do future functional development.

SAP SCM TP/VS will be available within SCM and maintained until March 2011. Extended maintenance is

available until 2014.

3.3.2. Who can I become part of the Ramp-up for SAP TM 6.0 (162) ID: 162

Release: Undefined

Status : Undefined


53 SAP Internal

Description:

Please contact the Ramp-up Owner for SAP TM 6.0 to join the ramp-up project.

EMEA Central: Jörg Reimesch

EMEA NEWS: Christophe Bertin

Additional info and the questionaire of joining the ramp-up can be found in the service marketplace under

rampup: http://service.sap.com/ramp

Then select: SAP Transportation Management 6.0

3.3.3. What is the planned date for general availability (end of Ramp-up) of SAP TM

7.0? (165) ID: 165

Release: Phase 1

Status : Answered

Description:

The general availability of SAP TM 7.0 will depend on the implementation success of the SAP TM 7.0, e.g.

how many customers are live with SAP TM 7.0. In general approx. after 6-12 months after begin of ramp-up

a release goes into general availability.

3.3.4. SAP TM Training (157) ID: 157

Release: Undefined

Status : Undefined

Description:

SAP Education offers the option to deliver SAP TM 6.0 training. This can be customer specific or general

training. If you are interested in a training or would like to organize a training for your customer please

contact Juergen Kohnle from SAP education for details.

3.3.5. Where do I find more information on SAP TM Pricing? (144) ID: 144

Release: Undefined

Status : Undefined


54 SAP Internal

Description:

Please view the SAP TM Roll-Out Map for a list of collaterals aimed at different target audiences, including

pricing information.

https://portal.wdf.sap.corp/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs//guid/20cd159e-6160-2910-

51a1-a90c35ff47c5

The Pricing PPT in the RO-Map can only provide some initial guidance. For further information please go

to the Corporate Portal and use the Search feature to look for ‘Global Pricing’.

3.3.6. What is the planned date for general availability (end of Ramp-up) of SAP TM

6.0? (147) ID: 147

Release: Undefined

Status : Undefined

Description:

07.November 2008

This depends on the defined keyfigured for SAP TM 6.0, e.g. number of ramp-up customers, number of

open error messages...

3.3.7. How can I get into contact with SAP TM interested people? (149) ID: 149

Release: Undefined

Status : Undefined

Description:

SAP internally we have a distribution list created.

https://portal.wdf.sap.corp/irj/servlet/prt/portal/prtmode/preview/prtroot/com.sap.sen.apps.reglist.RegList?id

=20080306110302395nVJR

You can register yourself in this list and send emails to all registered parties on this list.


55 SAP Internal

3.3.8. How can I share SAP TM related information with others (wiki)? (150) ID: 150

Release: Undefined

Status : Undefined

Description:

There is a wiki available for SAP TM related information.

https://wiki.wdf.sap.corp/display/SAPTM/Home

3.3.9. Where can I find the application solution map for SCM? (78) ID: 78

Release: Undefined

Status : Undefined

Description:

You and SAP customers can have a look at our Supply Chain Application/Business Map via following links

from external and internal sources:

Public web:

http://www.sap.com/solutions/businessmaps/99b4d4e97a624be5987bc14633908b9b/index.epx

Portal:

http://bupmain.wdf.sap.corp:1080/socoview(bD1kZSZjPTAwMSZkPW1pbg==)/smdisplay.asp?id=5F7358

118AA6D511B1A80090270F6F87&fragID=&packageid=74BA97B768AD1646996ECC11572A33DA&iv

=

On the SDN:

If you or your customer is an SDN (SAP developer network) memeber just log-in to the SDN and go to

enterprise SOA -> ES Workplace and find the great SCM map + defined services.

http://erp.esworkplace.sap.com/socoview/flddisplay.asp

3.3.10. I would like to get access to a SAP TM test system / IDES system (80) ID: 80

Release: Undefined

Status : Undefined

Description:


56 SAP Internal

Currently an IDES scenario is available.

Please check the IDES quicklink for details.

https://portal.wdf.sap.corp/go/ides

Click on "xADS Demo Database" and search for "010000005896". This number if the scenario ID.

Alternatively you can search for "Freight Forwarding Scenario".

3.3.11. How can I get into contact with a reference customer? (17) ID: 17

Release: Undefined

Status : Answered

Description:

SCM TM is currently in development hence there are no active customers.

For ERP LES and / or SCM APO TP/VS reference customers please use the reference customer database.

Here you find also the correct contact persons for the customers. Please use the quicklink: /customer-

references in SAPNET.

Currently the following reference customers exists for SCM TP/VS. Please use the link above to check for

the correct contact person.

- Fujitsu-Siemens

- Siemens

- Empress Polar

- Colgate

- International paper

- Coors

- M-real

3.4. Delta


57 SAP Internal

3.4.1. What is the main difference between SCM APO TPVS and ERP LES and SAP

TM? (2) ID: 2

Release: Undefined

Status : Answered

Description:

In addition to the functionality of SCM TP/VS and ERP LES the SCM TM provides the following

functionality:

- One combined system for all transportation activities

- Transportation planning and execution for multiple ERP systems

- Tendering allows peer-to-peer, broadcast and open tendering

- Combined inbound and outbound transportation execution possible

- Open eSOA based archtecture

- Based on EDIFOR standards

- One-step optimization is possible (Routing proposals and TSP selection in one step)

- DRD (Routing Guide) supports the same constraints as in planning, e.g. compartments, truck and trailer

- Independently of existing Product, Location and Partner master data

- Support of master data for standard routes, container and driver

- Adaptive planning even after the execution of the transportation activities has started

- Delta planning, e.g. ability to plan new transportation demands into existing shipments

- No limitation regarding the number of hubs used in one shipment (TP/VS has a limit of 2 hubs)

SCM TP/VS does currently supports more ERP transactional data integration. With SAP TM you can plan

on ERP deliveries and ERP shipment. With SCM TP/VS you can also plan ERP purchase orders, ERP sales

orders and ERP stock transport orders. It is planned for SAP TM that these elements will be supported in the

next release which is planned for 2009. In SCM TP/VS dynamic route determination is possible from the

ERP sales order entry which is not possible in SAP TM.


58 SAP Internal

4. Integration

4.1. General

4.1.1. Integration with SAP TM based on EDIFACT standards (133) ID: 133

Release: Undefined

Status : Undefined

Description:

The SAP TM business objects are based on the EDIFACT standard, e.g.:

Shipment Request : IFTMIN

Freight Request: IFCSUM

Shipment Order: IFTMIN

Freight Order: IFCSUM

Booking Order: IFTMBF (IFMBC for the confirmation)

SAP TM does not deliver standard mapping for EDIFACT based objects but the field and structure is

similar.

4.1.2. What external services / interfaces does SAP TM provide? (134) ID: 134

Release: Undefined

Status : Undefined

Description:

SAP TM delivers B2B ESA services for the external interfaces. These services can be used for XI mapping

and for A2A (application to application) communication.

SAP TM 6.0 does currently not contain standard A2X services for creating additional user interface but in

planning to include these services into the next SAP TM release. On a project basis the customer /

implementation partner can maintain these services directly.

4.1.3. How can I influence the master data in SAP TM which is send from SAP ERP

(166) ID: 166


59 SAP Internal

Release: Phase 1

Status : Answered

Description:

The location / material master data in SAP TM can be influence via BADI.

For example a location D1ST can be changed to D1ST@QPT002.

To do this you can use the following BADI:

Customizing -> SAP Transportation Management -> Transportation Management -> SCM Basis ->

Integration -> BAdIs for Specifiic Applications -> Location and Business Partner or alternative Product

4.1.4. How can I find existing services (webservices) for SAP in general? (169) ID: 169

Release: Phase 1

Status : Answered

Description:

https://www.sdn.sap.com/irj/sdn

Select Service-Oriented Architecture-> Explore Enterprise Services

4.1.5. Which SAP ERP Release is required to integrate to SAP TM? (6) ID: 6

Release: Undefined

Status : Answered

Description:

SAP develops a pre-defined integration from SAP TM to SAP ERP and vice versa. Integration out-of-the

box will be provided for SAP ERP 2005.

For this integration an add-on is required. This add-on will be responsible for the account determination

based on the logistical data coming from SAP TM. For the processing of SAP TM Transportaton Charge

Invoice Request in SAP ERP the ECC-SE 602 Service Pack 2 or Service Pack 1 with Note 1082930 is

required.

No note is required for run TM 6.0 with both (ECC-SE 603 or ECC-SE 604). SAP TM 7.0 runs also with

both (ECC-SE 603 or ECC-SE 604).


60 SAP Internal

The ERP delivery and shipment integration can be based on services as of ECC-SE 603 und ECC-SE 604

(with ERP 2005). Before these enhancement sets the integration is based on IDOCs.

The delivery and shipment IDOC integration is based on IDOC's version which are availabe in earlier

releases as ERP 2005. As SAP will not validate these release SAP can unfortunately not confirm that earlier

ERP releases then 2005 will be corrected integrated.

4.1.6. Integration between SAP ERP and SAP TM - Master Data (15) ID: 15

Release: Undefined

Status : Answered

Description:

For master data the ERP master data, e.g. material, plant, customer, supplier master data can be send to

SCM TM using the existing SAP Coreinterface.

This does not require any additonal system, e.g. no Exchange Infrastruction / Process Integration is required

for master data integration.

4.1.7. Will multi-backend system be supported? (23) ID: 23

Release: Undefined

Status : Answered

Description:

SAP TM can get connect to several SAP ERP system to perform centralized transportation management

activities. It is also possible to use several SAP TM system with one or more SAP ERP systems. Using the

open interface of SAP TM you can also connect to other systems then SAP ERP system, e.g. the legacy

systems.

The actual system landscape for the customer will depend on organizational requirements of the customer

and the order volume of the customer and need to get determined on a customer specific basis.

4.1.8. Can I use screen X to allow an external user to maintain / view Y in SAP TM?

(25) ID: 25

Release: Undefined

Status : Answered


61 SAP Internal

Description:

Most the transportation SAP TM screens are based on Webdynpro hence these screens will be running via

the SAP Portal. The SAP Portal can be allowed to have access via the internet. Please see the SAP Portal

documentation for details.

Most of the master data maintenance in SAP TM will require the SAP business client hence a remote

maintenance via the web for these screens is not possible (without additional software installed on the client

side).

4.1.9. Can I use legacy system X or Web portal Y to integrated to SAP TM (59) ID: 59

Release: Undefined

Status : Undefined

Description:

SAP TM provides interfaces for master data and transportation data hence every system could be integrated.

Use Cases:

Use Case (1)

A customer has a well established order entry system. He can still use this system for order entry capturing

and integrates the data to an SAP TM system.

4.1.10. Does SAP TM use the same business objects as SAP EWM? (73) ID: 73

Release: Undefined

Status : Undefined

Description:

No.

SAP TM has business objects designed for the transportation process while SAP EWM uses the business

objects to drive the warehouse activities.

4.1.11. If I use SAP TM, SCM APO and / or SAP EWM how can I synchronize the

master data for these systems. (74)


62 SAP Internal

ID: 74

Release: Undefined

Status : Undefined

Description:

The SAP ERP system can distribute the master data to several systems. You have then to distribute the

master data to the different systems on a regular basis.

4.1.12. How can I select which customers and suppliers are integrated to SAP TM? (85)ID: 85

Release: Undefined

Status : Undefined

Description:

For customers the following fields are available as selection fields:

Customer

Account group

Sales Org.

Company code

Partner Functn

Search term

Customer class.

For supplier the following fields are available as selection fields:

Vendor

Account group

Purchasing Org

Company Code

Search term

Purch. Group

Partner Functn

In addition to this standard selection the User Exit 003 in function CIF_CUSTOMER_LOCATION_MAP

bzw. 002 in function CIF_VENDOR_LOCATION_MAP can be used to do customer specific filtering.

4.1.13. Schedules (122) ID: 122


63 SAP Internal

Release: Undefined

Status : Undefined

Description:

Schedules allow the definition of pre-defined departure dates and sequences of locations / transportation

zone. E.g. sailing schedule or train schedule.

BAPI are available to upload them.

/SCTM/BAPI_LEG_READ_MULTI BAPI-FuBa for reading schedules

/SCTM/BAPI_LEG_SAVE_MULTI BAPI-FuBa for create, change, read, delete schedules

4.1.14. Transporation Allocation (140) ID: 140

Release: Undefined

Status : Undefined

Description:

Function modules for Transportation Allocation are available

/SCMTMS/BAPI_TAL_DOWNLOAD

/SCMTMS/BAPI_TAL_UPLOAD

in function group /SCMTMS/BAPI_TAL_IO.

4.1.15. Does SAP TM has visibility of stocks / production orders or other supply

elements? (120) ID: 120

Release: Undefined

Status : Undefined

Description:

No.

4.1.16. Which integration of mobile devices does SAP provide? How is the mobile

infrastructure integrated? (34) ID: 34

Release: Undefined


64 SAP Internal

Status : Answered

Description:

SAP does not provide out-of-the-box integration to any mobile devices. Print documents can be send to

printers, email, fax devices. The customer can then re-route these documents to mobile devices. For tracking

and tracing SAP provides for SAP TM open interfaces based on SAP EM which the customer can use to

connect the mobile devices / mobile applications to.

4.2. Specific Systems

4.2.1. Are ERP shipments necessary if SAP TM is in usage? (132) ID: 132

Release: Undefined

Status : Undefined

Description:

ERP shipment are not necessary with the usage of SAP TM, if SAP TM is used for the planning and

execution of the transportation activities.

The customer has the option to use SAP TM only for planning and still performs the execution in SAP ERP.

In this case SAP TM can trigger via the freight order the creation of a shipment in SAP ERP.

In addition the customer can use SAP ERP for planning and execution of transportation activities and use

SAP TM only for tendering. In this case SAP ERP would create a shipment and send it for SAP TM for

tendering. Once the carrier has been selected this information is send back to SAP ERP.

4.2.2. What is xCarrier and how is it related to SAP TM? (138) ID: 138

Release: Undefined

Status : Undefined

Description:

xCarrier has been a research initiative by the SAP Business Renovation team and addresses a gap in SAP’s

product offering around small parcel shipping. The initiative centered around a pilot program involving a

small number of shippers as well as small parcel carriers with a focus on shipping execution of small parcels

leveraging the concept of eSOA for collaboration. xCarrier has not been productized yet because of a lack of


65 SAP Internal

resources in SCM development as well as a lack of support from the shipper IBU’s within SAP.

Nevertheless the concept of xCarrier has been integrated into SAP TM which delivers a set of around 35

Enterprise Services for business partner collaboration in its first release of SAP TM 6.0. These services will

be packaged in an Enterprise Service Bundle called ‘Transportation Collaboration & Subcontracting’.

Additional services are being delivered within ERP via a bundle called ‘Logistics Execution – Integration of

External TMS’.

This concept in SAP TM is delivering first results as partners like ocean platforms INTTRA and GT Nexus

and Latin America partner Neoris for real-time tracking of assets like trucks are developing mapping content

for SAP’s services.

Of course a lot of functional backend functionality is still missing in ERP as well as SAP TM to enable a

next generation parcel shipping approach. The next Product Definition phases will address these issues

together with SAP’s Industry units.

4.2.3. Are handling units integrated from SAP ERP to SAP TM? (163) ID: 163

Release: Undefined

Status : Undefined

Description:

If handling units are maintained in the delivery they will be transferred to SAP TM and available as

packaging information .

4.2.4. Does SAP TM support stackabilty / Vehicle space optimization / loading

sequence? (148) ID: 148

Release: Undefined

Status : Undefined

Description:

SAP TM does support several units of measurement to be considered during planning, e.g. volume, weight,

pallets.

The system will calculate the sum of all freight units which are included in a vehicle and compares this with

the total available capactity of the vehicle.

Stackabilty or loading sequence is currently not considered by SAP TM.


66 SAP Internal

4.2.5. Integration between SAP ERP Fleetmanagement and SAP TM (155) ID: 155

Release: Undefined

Status : Undefined

Description:

SAP TM is not integrated with SAP ERP Fleetmanagement.

4.2.6. Can SAP TM still use SAP ERP rates for Carrier Selection? (156) ID: 156

Release: Undefined

Status : Undefined

Description:

Yes

The integration is based on the BAPI „BAPI_SHIPMENT_COST_ESTIMATE“. The ERP costs can be

used for the a cost estimation for TSP selection. In this process the shipment is temporary created in ERP

and the cost in calculated based on the ERP shipment.

After this calculation the temporary shipment is deleted (it can later be created if desired).

4.2.7. Which Map content provider do offer GIS integration? (79) ID: 79

Release: Undefined

Status : Undefined

Description:

Ptv (europe, us, etc)

Rand mcnally (us, canada)

Alk mit product pcmiler

Esri

mapsolute

4.2.8. How does Geocoding and Distance Calculation work with the eServer from the

PTV AG (81)


67 SAP Internal

ID: 81

Release: Undefined

Status : Undefined

Description:

The installation of PTV AG contains the eServer and is based on the world map of PTV.

The geocoding in the SAP standard works over the IGS (Internet Graphics Server). This geocoding is

included in the standard license for SAP TM and future releases.

The distance calculation between to location can also be performed with PTV AG distance matrix. This is

also done over the IGS. The display of the maps within the application can also be performed with IGS.

The standard delivery of SAP does only include the geocoding based on postal codes. For a more detailed

geocoding based on street level an additional license can be aquired from PTV. This same applies for the

display of maps and the distance calculation.

For questions regarding PTV licencing and functionality please contact [email protected]

Note consulting note: 934412

4.2.9. How will EH&S be integrated into SAP TM? (27) ID: 27

Release: Undefined

Status : Answered

Description:

There is currently no integration avaialable or planned between EH&S and SAP TM.

4.2.10. Does SAP TM contain a strategic freight procurement solution? (32) ID: 32

Release: Undefined

Status : Answered

Description:


68 SAP Internal

SAP TM does not have a strategic freight procurement (SFP) solution.

4.2.11. Integration between SAP CRM and SAP TM (9) ID: 9

Release: Undefined

Status : Answered

Description:

There is currently no direct integration planned betwen SAP CRM and SAP Transportation Management.

CRM can be integrated to SAP ERP as normal. SAP ERP will then get integrated to SAP Transportation

Management. Currently it is not planned to integrate CRM to SAP TM in the future

4.2.12. Integration between SAP ERP and SAP TM - Transactional Data (10) ID: 10

Release: Undefined

Status : Answered

Description:

SAP ERP and SAP TM can be integrated via the SAP ERP delivery and the SAP ERP shipment. This

integration is based on the SAP Process Integration component (formerly known as Exchange

Infrastructure).

SAP provides standard mapping for the SAP ERP delivery (inbound and outbound) which needs to be

applied in the SAP PI system.

It is possible to use a separate SAP PI system. It is also possible to use the SAP PI systen in SAP TM.

SAP PI is part of SAP Netweaver and therefore part of SAP TM. If a high load of messages is expected SAP

recommends to use an external SAP PI system to level the system load.

Sales Orders, Purchase Orders, Purchase Requisitions, Stock Transfer Orders and Stock are currently not

supported.

4.2.13. Integration between SAP GTS and SAP TM? (11) ID: 11

Release: Undefined

Status : Answered


69 SAP Internal

Description:

There is currently no direct integration planned between SAP GTS and SAP TM. SAP is planning to

integrated SAP GTS and SAP TM in the future.

4.2.14. Can I integrate SAP ERP to SAP APO TP/VS and to SAP TM? (12) ID: 12

Release: Undefined

Status : Answered

Description:

Technical yes but the processes need to be separated. SAP TM does not support a combined planning

togehter with SCM TP/VS. It is possible to use SAP TM for one part of the business and SCM TP/VS for

another part of the business.

4.3. Event Management

4.3.1. SAP EM integration processes (151) ID: 151

Release: Undefined

Status : Undefined

Description:

SAP TM offers four visibility scenarios together with SAP TM

1.Order Taking Visibility Process (Shipment request, Shipment)

2.Transportation Execution Visibility Process (Tour)

3.Resource Visibility Process (Transportation Unit/Vehicle resource)

4.Tendering Visibility Process (Request for supplier shipment/freight quote)

4.3.2. SAP TM - Order Taking Visibility Process (152) ID: 152

Release: Undefined

Status : Undefined

Description:


70 SAP Internal

A shipment request is created which is the input for the SAP TM planning process. After the transportation

planning, freight units and shipments will be created for the execution of the shipment request.

SAP EM enables you to you to achieve the following business goals:

- Monitor the status changes of shipment request (Shipper/Ordering Party).

- Monitor the expected/actual event of the shipment from loading the goods to the proof of delivery at the

consignee. (Shipper/Ordering Party/Consignee/TSP).

- Report events, both within the company and also by business partners such as transportation service

provider and consignee (including unexpected events, e.g. delay and/or customs events).

- Notify involved parties, e.g. the transportation dispatcher about events, e.g. delay

- The shipper/ordering party has an access the SAP EM to monitor/track his shipment request and also

shipment. (External format is used.)

- The transportation dispatcher has an access the SAP EM to monitor/track his shipment request and also

shipment. (Internal format is used.)

- The consignee can access the shipment though SAP EM. He can report ‘Proof of Delivery’

- The transportation service provider can access the shipment though SAP EM. He can report the all

expected events (‘Loading’, ‘Proof of Pickup’, ‘Departure’, ‘Arrival at Destination’ and ‘Unloading’). Also

unexpected events e.g. ‘Delay’. Reporting events from SAP EM update the ETA in SAP TM.

- The transportation dispatcher can access to SAP EM directly from shipment request/shipment in SAP TM.


71 SAP Internal

5. User Interface

5.1. General

5.1.1. Does SAP TM support Drag-and-Drop? (22) ID: 22

Release: Undefined

Status : Answered

Description:

No.

SAP TM uses Webdynpro for ABAP for it's screens which does not support Drag-and-Drop.

5.1.2. How can I open the same session several times? How can I open the entry of

shipment request several times? (126) ID: 126

Release: Undefined

Status : Undefined

Description:

In the NWBC you can start the same transaction several times by pressing Cntr+ the link.

This way you can start X times the entry of a shipment request.

5.1.3. How can I extent the SAP TM Userinterface? (131) ID: 131

Release: Undefined

Status : Undefined

Description:

In general the SAP TM Userinterface is not without modification extensible in regards to existing screens.

Some screens, e, g. the business partner are extentable via BADI.

5.1.4. Which user parameters can be used to as part of the user profile in SAP TM to

adjust system settings? (146)


72 SAP Internal

ID: 146

Release: Undefined

Status : Undefined

Description:

/SCMTMS/ARCH_DAC -> automatical retrieve in Archive

/SCMTMS/LOC_DEP_TZON -> Location dependent time zone indicator

/SCMTMS/MESSMGRLINES -> Message Manager: Number of Lines to display

/SCMTMS/NO_QAF_START ->Start OIFs in Basic View (where there is a QAF)

/SCMTMS/SELECT_TZONE -> User-selected timezone

/SCMTMS/USER_TZONE -> Use user-selected timezone

/SCMTMS/USER_UOM -> User-selected Unit of Measure

/SCMTMS/TS_VSR_SYNCHSynchronous Opt Call

/SCMTMS/UI_TRACEActivate tracing for TMS UIs

/SCMTMS/VSR_OPT_DESTDestination for VSR Optimizer

/SCMTMS/VSR_SHOW_MESShow VSR Mess.Immediately ( 'X' = Show all, 'H' hide all)

/SCMTMS/REQ_PROFILERequirements Profile

/SCMTMS/SIGNSelect Options Sign: I = Include, E = Exclude

/SCMTMS/TS_VSR_STOPStop after Opt

/SCMTMS/TS_VSR_SYNCHSynchronous Opt Call

/SCMTMS/DEF_UOM_AMOUDefault UOM for Amount

/SCMTMS/DEF_UOM_LNGTDefault UOM for Length

/SCMTMS/DEF_UOM_VOLDefault UOM for Volume

/SCMTMS/DEF_UOM_WGHTDefault UOM for Weight

/SCMTMS/OPTIONSelect Options: EQ, GT, GE, LT, LE, BT, NE, NB, CP

/SCMTMS/RATETBDSPMODRate Table Value Editing Mode(Excel/WD Table)

/SCMTMS/PLAN_PROFILEPlanning Profile

5.1.5. How can I avoid the Basic View when creating/displaying certain documents – for

example Shipment Request or Booking Request – and start directly in the Detailed

View? (142) ID: 142

Release: Undefined

Status : Undefined

Description:

Please maintain User Parameter /SCMTMS/NO_QAF_START (EMPTY / X) in the SAP Gui -> System ->

User Profile -> Own Data.


73 SAP Internal

5.1.6. Which user interface do I use for SAP TM? (121) ID: 121

Release: Undefined

Status : Answered

Description:

The end user / power user is recommended to use the Netweaver Business Client for working with SAP TM.

To configure the SAP TM application is is recommended to use SAP GUI.

5.1.7. Which user interface technology is used? (75) ID: 75

Release: Undefined

Status : Answered

Description:

SAP TM will mainly use webdynpro for ABAP for a user interface. This means that all new designed

screens, e.g. the business objects user interface (shipment request, shipment order, etc), the planning screens,

the tendering screens, etc are based on webdynro.

For master data the SAP TM re-uses existing screens which are based on SAP GUI. SAP is planning to

provide the Netweaver Business client so that the enduser have on user interface to use the complete SAP

TM system.


74 SAP Internal

Date post:	27-Dec-2015
Category:	Documents
Upload:	h240488
View:	91 times
Download:	2 times