Integration of SAP ERP with

SAP Transportation
Management
(SAP Enhancement Package 4
for SAP ERP 6.0
Support Package 9)

Copyright
Copyright 2011 SAP AG. All rights reserved.
SAP Library document classification: PUBLIC
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM,
z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,
Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower,
PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2
Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,
WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM
Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World
Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany and other
countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of
Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase, Inc. Sybase is an SAP company.

(C) SAP AG

All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP
AG and its affiliated companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

(C) SAP AG

Icons in Body Text

Icon

Meaning
Caution
Example
Note
Recommendation
Syntax

Additional icons are used in SAP Library documentation to help you identify different types of
information at a glance. For more information, see Help on Help
General Information
Classes and Information Classes for Business Information Warehouse on the first page of any
version of SAP Library.

Typographic Conventions
Type Style

Description

Example text

Words or characters quoted from the screen. These include field

names, screen titles, pushbuttons labels, menu names, menu paths,
and menu options.
Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, graphic titles, and table

titles.

EXAMPLE TEXT

Technical names of system objects. These include report names,

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

Example text

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

Example text

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

<Example text>

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

EXAMPLE TEXT

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

(C) SAP AG

Table of Contents
Integration of SAP ERP with SAP Transportation Management ............................................. 6
Integration: Invoice Processing (MM-IV/SD-BIL) - SAP TM................................................. 7
Prerequisites: Invoice Processing (MM-IV/SD-BIL) - SAP TM ....................................... 10
Processing of Outgoing Invoices (LO-TM)..................................................................... 12
Processing of Incoming Invoices (LO-TM)..................................................................... 13
Release of Incoming Invoices (LO-TM) ......................................................................... 14
Archiving of Incoming Invoices (LO-TM) ....................................................................... 15
Evaluated Receipt Settlement (ERS) (LO-TM) .............................................................. 16
Maintenance of GR/IR Clearing Account (LO-TM)......................................................... 17
Integration: Order and Delivery Processing - SAP TM ...................................................... 18
Prerequisites for Order and Delivery Integration............................................................ 19
Enterprise Services for Order and Delivery Integration .............................................. 20
Transportation Planning and Execution......................................................................... 22

(C) SAP AG

Integration of SAP ERP with SAP Transportation

Management
The following functions are included in the scope of the integration of SAP Transportation
Management (SAP TM):
Invoice processing
You can perform invoice processing for SAP TM in SAP ERP and thus make use of
important functions in ERP invoice processing in Materials Management (MM) and
Sales and Distribution (SD).
See Integration: Invoice Processing (MM-IV/SD-BIL) - SAP Transportation
Management (SAP TM) [Page 7]
Order and delivery processing
You can perform transportation planning for sales documents (sales orders and
returns orders), stock transport orders, and purchase orders in SAP TM, and execute
transportation on the basis of the relevant inbound and outbound deliveries.
See Integration: Order and Delivery Processing SAP TM [Page 18]

Integration
These functions are only available if you have SAP TM connected.

(C) SAP AG

Integration: Invoice Processing (MM-IV/SD-BIL) SAP TM

In integrated invoice processing, you can enter, process, or display invoices that refer to
documents in SAP Transportation Management (SAP TM).
You can use the following functions in SAP ERP, for example:
Create invoices
Process and check invoices
Release invoices
Archive invoices
Maintain GR/IR clearing account
Evaluated receipt settlement

Integration
These functions are only available if you have SAP TM connected.
NOTE
To be able to use this function, you must activate the business function TMS-ERP:
Invoice Integration (LOG_TM_IV_INT). Invoice verification for documents that
originate from SAP Transportation Management (SAP TM) is then possible with SAP
Transportation Management 8.0 (SAP TM 8.0) or higher.
Enterprise Services
Technically, the data is transferred from SAP TM to SAP ERP using enterprise services:
Logistics Invoice Verification (MM-IV)
In SAP ERP for Logistics invoice verification, internal documents that the system
requires for invoice creation are created on the basis of this TM data. When incoming
invoices are entered or canceled, SAP TM is informed by enterprise service
(Supplier Invoice Notification - InvoiceNotification_Out).
Billing (SD-BIL)
In SAP ERP, outgoing invoices are created on the basis of TM data and sent to the
bill-to parties.
Other services used:
TransportationOrderSUITEInvoicingPreparationRequest_In
TransportationOrderSUITEInvoicingPreparationCancellationRequest
_In
TransportationOrderSUITEInvoicingPreparationCancellationRequest
_In
For more information, see the documentation for the enterprise services.

(C) SAP AG

BAPIs (Incoming Invoice)

The following BAPIs were enhanced or adapted:
BAPI_INCOMINGINVOICE_CREATE
BAPI_INCOMINGINVOICE_PARK
BAPI_INCOMINGINVOICE_GETDETAIL
BAPI_INCOMINGINVOICE_GETLIST
BAPI_INCOMINGINVOICE_CHANGE
BAPI_INCOMINGINVOICE_DELETE
BAPI_INCOMINGINVOICE_POST
BAPI_INCOMINGINVOICE_CANCEL
IDoc (Incoming Invoice)
In the IDoc INVOIC01/INVOIC02 (invoice/billing document) in the segment type E1EDP02,
the following qualifiers are relevant:
T01 = Freight order
T02 = Bill of lading
T03 = Air waybill
T04 = Flight number
T05 = Voyage number
NOTE
For technical reasons, in SAP ERP one purchase order is created per freight
settlement document, which the system requires for invoice creation. If several freight
settlement documents are transferred with reference to one TM document, the EDI
invoice item can only be assigned using this purchase order number. For a unique
assignment, there is also the qualifier TP1 (TM purchase order number). It is possible
to transfer several segment types E1EDP02 per invoice item with the IDoc (for
example, the qualifiers T01, T03, and TP1).

More Information
Subject

Document

Prerequisites

Prerequisites: Invoice Processing (MM-IV/SD-BIL) - SAP TM [Page 10]

Outgoing Invoice
(SD-BIL)

Processing of Outgoing Invoices (LO-TM) [Page 12] and SAP Help Portal
http://help.sap.com SAP Transportation Management (SAP TM)
Forwarding Settlement
Processing of Incoming Invoices (LO-TM) [Page 13]

Incoming Invoice
(MM-IV)

Release of Incoming Invoices (LO-TM) [Page 14]

Evaluated Receipt Settlement (LO-TM) [Page 16]

(C) SAP AG

Subject

Document
Maintenance of GR/IR Clearing Account (LO-TM) [Page 17]
Archiving of Incoming Invoices (LO-TM) [Page 15]
SAP Help Portal http://help.sap.com
(SAP TM) Freight Settlement

(C) SAP AG

SAP Transportation Management

Prerequisites: Invoice Processing (MM-IV/SD-BIL) SAP TM

Prerequisites
Set up Customizing
For incoming and outgoing invoices, make the appropriate Customizing settings for
Integration with Other SAP Components under Transportation Management
Invoice Integration .
Activate business function
You must activate the business function Operations, Enterprise Services [External]
(LOG_ESOA_OPS_2) to be able to use enterprise services for incoming and outgoing
invoices.
Set user parameters
You must set up the user parameter TM_INVOICE_CLERK in the user data
accordingly. With the user parameter TM_INVOICE_CLERK, you control which tabs
the user sees when entering or changing incoming invoices in the transactions MIRO
and MIR7, in change mode in the transaction MIR4, and in GR/IR clearing account
maintenance in the transaction MR11.
The user parameter has the following alternatives:
o

Blank
In invoice creation, the user sees the TM Reference and PO Reference tabs,
as well as the G/L Account tab that is visible according to Customizing.

01
The user only sees the TM Reference tab and, depending on Customizing,
the G/L Account tab. The PO Reference tab is hidden.

02
The user does not see the TM Reference tab, but sees the PO Reference
tab, as well as all tabs that are visible according to Customizing (Material
Account, G/L Account, and Contract Reference).

Display reference document

In the transactions MIRO, MIR4, MIR7, and MRBR, you can navigate to the details of
the reference document in SAP TM.
The synchronous outbound service GetTransportationDocumentURI transfers
the document type and document number from SAP ERP to SAP TM and requests a
URL.
The transportation management system returns the URL from SAP TM to SAP ERP.
SAP ERP requires this URL to display a document from SAP TM in the browser.
The service is in the Enterprise Services Repository in the software component
SAP_APPL 6.04 (namespace http://sap.com/xi/APPL/PI/TM/UX).

(C) SAP AG

10

To use the service, you must set up communication with the corresponding service in
SAP TM. For more information, see SAP Note 1451472.
Set up workflow
You must activate the workflow WS53800006 for the incoming invoice (BUS2081) so
that the connected transportation management system is informed by a service. In
addition, you must activate event linkage for the events POSTED and CANCELLED.

(C) SAP AG

11

Processing of Outgoing Invoices (LO-TM)

You can also use the functions for editing outgoing invoices for invoices that originate from
SAP Transportation Management (SAP TM).

Prerequisites
See Prerequisites: Invoice Processing (MM-IV/SD-BIL) - SAP TM [Page 10]

More Information
Billing (SD-BIL) [External]

(C) SAP AG

12

Processing of Incoming Invoices (LO-TM)

You can enter, process, or display invoices that refer to documents in SAP Transportation
Management (SAP TM).

Prerequisites
See Prerequisites: Invoice Processing (MM-IV/SD-BIL) - SAP TM [Page 10]

Features
You can use the following functions:
Enter and check invoices
In the transaction MIRO, you can enter and check invoices with reference to SAP TM.
The TM Reference tab is available for this purpose. Here you can determine
documents based on logistics data such as freight order, carrier, bill of lading, air
waybill, voyage number, and flight number.
NOTE
In the transactions MIRO, MIR4, and MIR7, you can navigate to the details of
the reference document in SAP TM (via the service
GetTransportationDocumentURI). In the Details column, select the
Reference Document (TM) pushbutton.
Park and hold invoices
In the same way as in transaction MIRO, in transaction MIR7 you can park, hold, or
completely enter invoices with reference to SAP TM. The TM Reference tab is
available for this purpose.
Display invoices
In the transaction MIR4, you also see TM-specific data in the invoice.
List invoices
In the transaction MIR6, you can list incoming invoices that were entered with
reference to SAP TM. On the initial screen, you can restrict the selection to invoice
documents with a TM reference. Select Transportation Management (TM).
Cancel invoices
In the transaction MR8M, you can completely cancel invoices that were entered with
reference to SAP TM.
When you display the invoices to be canceled, the TM-specific data is displayed on
the TM Reference tab.

Note that background processing of invoices is not supported.

More Information
Logistics Invoice Verification (MM-IV-LIV) [External]

(C) SAP AG

13

Release of Incoming Invoices (LO-TM)

You can release blocked invoices that refer to documents in SAP Transportation
Management (SAP TM).

Prerequisites
See Prerequisites: Invoice Processing (MM-IV/SD-BIL) - SAP TM [Page 10]

Features
In the transaction MRBR, you can search for blocked invoices with a TM reference and release
them.
You can use the following functions:
Search for and release document
On the initial screen, select the TM Documents Only indicator and enter TM-specific
selection criteria to search explicitly for documents with a TM reference.
Display reference document
You can navigate to the details of the reference document in SAP TM (via the service
GetTransportationDocumentURI). In the results list, select the Reference
Document (TM) pushbutton in the Details column.

More Information
Logistics Invoice Verification (MM-IV-LIV) [External]

(C) SAP AG

14

Archiving of Incoming Invoices (LO-TM)

When invoice documents are archived with the archiving reports RM08RW47 and RM08RD47,
TM-relevant data is also archived (table RSEG_TM; archiving object MM_REBEL).

More Information
Archiving of Invoice Documents [External]
Archiving in Invoice Verification (MM-IV) [External]

(C) SAP AG

15

Evaluated Receipt Settlement (ERS) (LO-TM)

You can execute evaluated receipt settlement with reference to documents in SAP
Transportation Management (SAP TM).

Integration
In the same way as when incoming invoices are entered, in evaluated receipt settlement SAP
TM is informed by enterprise service (SupplierInvoiceNotification InvoiceNotification_Out).

Prerequisites
See Prerequisites: Invoice Processing (MM-IV/SD-BIL) - SAP TM [Page 10]

Features
You can use the following functions in evaluated receipt settlement:
Search for and settle document
The selection screen for evaluated receipt settlement has been enhanced to include
TM-specific data (transaction MRRL). On the initial screen, select the Settle
Documents indicator and enter TM-specific selection criteria.
Output invoice
Instead of purchasing data, TM-specific data is now output in the invoice. You can
transmit messages with the output type ERS by fax and print output (transaction
MR90).
NOTE
Transmission by EDI is not implemented.

More Information
Logistics Invoice Verification (MM-IV-LIV) [External]

(C) SAP AG

16

Maintenance of GR/IR Clearing Account (LO-TM)

You can balance the GR/IR clearing account for documents that refer to SAP Transportation
Management (SAP TM).

Prerequisites
See Prerequisites: Invoice Processing (MM-IV/SD-BIL) - SAP TM [Page 10]

Features
In the transaction MR11, you can select items with a balance in the clearing account based on
transportation-relevant data.
You can use the following functions:
The Transportation Management tab is available on the selection screen to allow you
to search for the relevant documents.
The results list displays information relevant for transportation, such as freight order
or bill of lading.
NOTE
Set up the user parameter TM_INVOICE_CLERK in the user data accordingly. You
use this user parameter to control whether the Transportation Management tab is
displayed.

More Information
GR/IR Account Maintenance (MM-IV-CA) [External]

(C) SAP AG

17

Integration: Order and Delivery Processing - SAP

TM
You can integrate order and delivery processing in SAP ERP with transportation planning and
execution in SAP Transportation Management (SAP TM).

Integration
You have to connect your SAP ERP system to one or more SAP TM systems. You exchange
information between SAP ERP and SAP TM using enterprise services. For more information,
see Enterprise Services for Order and Delivery Integration [Page 20].

Features
Order Integration
You can carry out transportation planning for orders created in SAP ERP in SAP TM.
Delivery Proposals
You can create inbound and outbound deliveries in SAP ERP based on delivery proposals
received from SAP TM.
Delivery Integration
You can execute inbound and outbound deliveries created in SAP ERP in SAP TM.

(C) SAP AG

18

Prerequisites for Order and Delivery Integration

To be able to use these functions, you must activate the ERP-TMS: Basic Order Integration
(LOG_TM_ORD_INT_TRQ) business function. The integration of order processing and delivery
processing with SAP Transportation Management (SAP TM) is then possible with SAP
Transportation Management 8.0 (SAP TM 8.0) or higher.
To integrate orders and deliveries with SAP Transportation Management (SAP TM), you must
make the following settings.
Business Functions
To transfer purchase orders and stock transport orders to SAP TM, you have to activate the
Operations, Enterprise Services 2 (LOG_ESOA_OPS_2) business function. The following
business functions are also recommended:
Advanced Returns Management (OPS_ADVRETURNS_1) for transferring returns
orders to SAP TM
Logistics Simplification (SD_01) or Operations, Enterprise Services (ESOA_OPS01)
for transferring sales orders to SAP TM
For more information, see SAP Note 1530240.
Document Transfer
In Customizing for Integration with Other SAP Components, you activate the transfer of
documents to SAP TM under Transportation Management Order Integration
by
making the following settings:
1. In the Customizing activity Define Control Keys for Document Transfer, you define
control keys that are used to determine which documents in a document chain are to
be transferred to SAP TM.
2. You assign the control keys to the relevant document types in the Customizing
activities Activate Transfer of Sales Documents, Activate Transfer of Purchase
Orders, and Activate Transfer of Delivery Documents. If you are using more than one
transportation management system, you can also enter a technical transportation
management number, which is used to route the document to the correct
transportation management system.
Messaging Settings
For sales documents and deliveries, you have to set up output determination and
create condition records. For more information, see the documentation of the
Customizing activities Activate Transfer of Sales Documents and Activate Transfer of
Delivery Documents.
For purchase orders and stock transfer orders, you have to set up the required
workflows by defining the service output and event type linkage. For more
information, see the documentation of the Customizing activity Activate Transfer of
Purchase Orders.
Service Operations
You have to implement the required enterprise services. For more information, see Enterprise
Services for Order and Delivery Integration [Page 20].

(C) SAP AG

19

Enterprise Services for Order and Delivery

Integration
You can use the following enterprise services to exchange information about orders and
deliveries with SAP Transportation Management (SAP TM).
Sales Document Integration
To transfer individual sales orders to SAP TM, you use the following service operations in the
Sales Order Processing process component:
SLO_TransportationRequestSUITERequest_Out
SLO_TransportationRequestSUITECancellationRequest_Out
To transfer individual returns orders to SAP TM, you use the following service operations in
the Customer Return Processing process component:
CRP_TransportationRequestSUITERequest_Out
CRP_TransportationRequestSUITECancellationRequest_Out
Purchase Order Integration
To transfer individual purchase orders to SAP TM for transportation planning, you use the
following service operations in the Purchase Order Processing process component:
POP_TransportationRequestSUITERequest_Out
POP_TransportationRequestSUITECancellationRequest_Out
Outbound Delivery Integration
The following service operations in the Outbound Delivery Processing component enable you
to create outbound deliveries in your ERP system, based on information received from SAP
TM:
OutboundDeliveryBulkCreateRequest_In
OutboundDeliveryBulkConfirmation_Out
To transfer individual outbound deliveries to SAP TM, you use the following service
operations in the Outbound Delivery Processing process component:
ODP_TransportationRequestSUITERequest_Out
ODP_TransportationRequestSUITECancellationRequest_Out
Inbound Delivery Integration
The following service operations in the Inbound Delivery Processing process component
enable you to create inbound deliveries in your ERP system, based on information received
from SAP TM:
InboundDeliveryCreateRequest_In
InboundDeliveryConfirmation_Out_V1
To transfer individual inbound deliveries created in SAP ERP to SAP TM, you use the
following service operations in the Inbound Delivery Processing process component:

(C) SAP AG

20

IDP_TransportationRequestSUITERequest_Out
IDP_TransportationRequestSUITECancellationRequest_Out
NOTE
In the integration of SAP ERP with SAP Transportation Management 6.0 and 7.0,
similar functions were provided by the ShipmentRequestRequest_out service
operation.

More Information
For information, see SAP Note 1569375.

(C) SAP AG

21

Transportation Planning and Execution

You can use this process to integrate order and delivery processing in SAP ERP with
transportation planning and execution in SAP Transportation Management (SAP TM). You
exchange information between the systems using enterprise services.

Prerequisites
You have connected your SAP ERP system to SAP TM and made the required settings for
orders and deliveries. For more information, see Prerequisites for Order and Delivery
Integration [Page 19].

Process
1. Create orders (SAP ERP).
You create orders in SAP ERP and the system sends the orders to SAP TM. The
following types of orders can be sent:
o

Sales orders

Purchase orders

Stock transport orders

Returns orders

2. Perform transportation planning (SAP TM).

SAP TM performs transportation planning for the orders received from SAP ERP.
3. Create delivery proposals (SAP TM).
SAP TM creates delivery proposals based on the transportation planning results and
sends the proposals to SAP ERP.
4. Create deliveries (SAP ERP).
SAP ERP creates deliveries based on the proposals received from SAP TM.
Depending on the corresponding order types, the deliveries can be inbound
deliveries, outbound deliveries, or returns deliveries. SAP ERP sends a confirmation
of the deliveries to SAP TM.
5. Execute transportation (SAP TM).
SAP ERP sends the deliveries to SAP TM, which executes transportation.
NOTE
You can use other variants of this process, such as the following:
Order integration without delivery integration: Transportation planning and
execution is carried out in SAP TM without creating delivery proposals in SAP
TM and deliveries in SAP ERP.
Delivery integration without order integration: Orders and deliveries are
created in SAP ERP without using SAP TM to create delivery proposals.
Transportation planning is carried out in SAP TM after receiving the
confirmed deliveries from SAP ERP.

(C) SAP AG

22