Basic Settings of SAP TM form SAP

May 8, 2018 | Author: sheriff_scribd | Category: Sap Se, C (Programming Language), Ibm Db2, Business Process, Enterprise Resource Planning
Share Embed Donate


Short Description

basic settings of SAP TM...

Description

SAP Transportation Management

Basic Settings for SAP Transportation Management

PUBLIC Document Version: 2.0 2.0 –  September 2012  – September

Copyright © Copyright 2012 SAP AG. All rights reserved.

SAP Library document classification: PUBLIC No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. 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, PowerPoint, Silverlight, and Visual Studio 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, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.  Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.

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

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin 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.

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

(C) SAP AG

2

Copyright © Copyright 2012 SAP AG. All rights reserved.

SAP Library document classification: PUBLIC No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. 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, PowerPoint, Silverlight, and Visual Studio 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, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.  Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.

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

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin 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.

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

(C) SAP AG

2

IOS is a registered trademark of Cisco Systems Inc.

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

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

INTERMEC is a registered trademark of Intermec Technologies Corporation.

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

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as 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.

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

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

(C) SAP AG

3

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

4

Icons in Body Text Icon

Meaning Caution Example Note Recommendation Syntax

 Additional icons are used in SAP Librar y 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 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

(C) SAP AG

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

5

Table of Contents Basic Settings for SAP Transportation Management ...................................................................... 8 Technical Settings ...................................................................................................................... 11 Naming Logical Systems for the Connection to SAP ERP and SAP TM ............................... 12  Assigning Logical Systems to Clients ...... ................. ................. .................. ................. ......... 13 Defining SLD Data of Business Systems ............................................................................... 14 Maintaining Business System Groups ................................................................................... 15  Assigning Logical Systems and Queue Types ................................. .................. ................. ... 16  Activating Queues ........................... ................. .................. ................. ................. .................. 17 Creating Active Versions and Models .................................................................................... 18  Activating Business Functions......... ................. .................. ................. .................. ................. 19  Activating Error and Conflict Handler ................................. ................. ................. .................. 20 General Customizing Settings ................................................................................................... 21 Defining Capacity Variants ..................................................................................................... 22 Creating ISO Units ................................................................................................................. 23 Creating Units of Measurement.............................................................................................. 24 Changing Units of Measurement .................................. ................. .................. .................. ..... 25 Defining Equipment Groups and Types ................................................................................. 26 Maintaining Transportation Groups ........................................................................................ 27 Specifying Language Selection .............................................................................................. 28  Activating Usage of Transportation Allocations .................. ................. .................. ................. 29 Defining Default Freight Document Types for Stages .................................. .................. ........ 30 Defining Stage Type Sequence for Movement Types ........................................................... 32 Displaying SAP TM-Specific User Menu ................................................................................ 34 Defining Schedule Types ....................................................................................................... 35 Defining Common Settings for Dangerous Goods Processing ................................ .................. 37 Specifying Settings for Mixed Loading Checks ................................. .................. ................. ...... 38 Defining Segregation Keys ..................................................................................................... 39 Defining Responses ............................................................................................................... 40 Specifying Segregation Rules for Segregation Keys ............................................................. 41 Defining Agreement Deactivation Reasons ........................................................................... 42 Configuring Basic Settings for Charge Calculations .................................................................. 43 Defining Category Codes ....................................................................................................... 44 Defining Subcategory Codes.................................................................................................. 46 Defining Charge Types ................. ................. .................. ................. .................. ................. ... 47 Defining Conditions for OTR Type Determination ................. ................. .................. .............. 50

(C) SAP AG

6

Configuring SAP Transportation Management for Order Integration ........................................ 53 Defining Text Schemas .......................................................................................................... 54 Defining Text Types ............................................................................................................... 55 Setting Up SAPconnect E-Mail .................................................................................................. 56 Configuring SAP Transportation Management for ERP Shipment Integration .......................... 57 Configuring Inbound Integration of Shipments ....................................................................... 58 Configuring Outbound Integration of Shipments .................................................................... 59

(C) SAP AG

7

Basic Settings for SAP Transportation Management This guide provides information about the settings that you must configure in SAP Transportation Management (SAP TM) to enable integration with SAP ERP. Change History Version

Date

Description

1.0

December 2010

Initial version

1.1

April 2011

Harmonized configuration and master data; scenarios based on IDES 



1.2

Updates to:

o

Defining Subcategory Codes [Page 46]

o

Defining Charge Type Codes [Page 47]

Added sections:

o

Defining Schedule Types [Page 35]

o

Defining Number Range Intervals for Schedules [External]

o

Defining Stage Type Sequence for Movement Types [Page 32]

o

Defining Default Agreement Party Roles for Stages [External]

o

Displaying SAP TM-Specific User Menu [Page 34]

o

Configuring Inbound Integration of Shipments [Page 58]

November 2011

2.0

September 2012

Update for SAP TM 9.0

Important SAP Notes You must read the following SAP Notes before you start using this test scenario. These SAP Notes contain the most recent corrections required to test the scenario. Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at http://service.sap.com/notes . SAP Note Number

Description

Valid with Release

1561162

 Address data not possible in Event Message reporting profile

SAP TM 8.1

1581944

Image Source does not work in Link to Action in

SAP TM 8.1

(C) SAP AG

8

SAP Note Number

Description

Valid with Release

FPM_TREE_UIBB 1620298

Port data incorrectly copied to referencing gateway schedule

SAP TM 8.1

1599238

Credit Segment information FWSD outbound structure

SAP TM 8.1

1624325

Empty lines appear in the beginning of a list UIBB

SAP TM 8.1

1622146

FBI: Action usages changed in Exit class not considered

SAP TM 8.1

1623764

FUB: error in message inbound

SAP TM 8.1

1634207

Error when trying to insert a schedule within Trans.Cockpit

SAP TM 8.1

1629698

/SCMTMS/XPRA_101_TC_RATES: usage of number range for scales

SAP TM 8.1

1634568

Event with reason code from EM is not propagated to TM

SAP TM 8.1

1679921

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

SAP TM 9.0

1729082

 Actual Route data cleared when saving FW O

SAP TM 9.0 SP01

1736290

 Authorization not working for wa ybill stock

SAP TM 9.0 SP01

1739767

Times not taken over from schedule

SAP TM 9.0 SP01

1736359

Misleading Error message in Freight Order Type customizing

SAP TM 9.0 SP01

Prerequisites You have set up the system landscape as follows: 

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



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



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



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



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

(C) SAP AG

9



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



You have configured Adobe Document Services.



You have completed e-mail setup.

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

SAP NetWeaver Process Integration installation documentation on SAP Service Marketplace at http://service.sap.com/instguides SAP NetWeaver  SAP NetWeaver PI 7.1



SAP Library for SAP NetWeaver 7.0 Including Enhancement Package 2 at http://help.sap.com/netweaver . In SAP Library, choose SAP NetWeaver  Technology Consultant's Guide Business Process Management  Configuration of Usage Type Process Integration (PI) . In particular, see General Setup of Integration Engine and Configuration of Business Systems with an Integration Engine sections.

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

SAP Library for SAP Supply Chain Management at http://help.sap.com/scm . In SAP Library, choose SAP Advanced Planning and Optimization (SAP APO) Integration via Core Interface (CIF) . In particular, see the section Checklist for Setting Up the System Infrastructure under Technical Integration Core Interface (CIF) Setting Up the System Infrastructure



.

Best practices document on SAP Service Marketplace at http://service.sap.com  Application Life-Cycle Management  Methodologies Run SAP  Best Practice Documents Manage APO Core Interface in SAP APO (3.x) / SAP SCM (4.x, 5.x)

For information about setting up Adobe Document Services, see SAP Library for SAP NetWeaver 7.0 Including Enhancement Package 2 at http://help.sap.com/netweaver . In SAP Library, choose SAP NetWeaver  Technology Consultant's Guide Business Task Management   Adobe Document Services (Configuration) . For information about setting up e-mail in an SAP NetWeaver system, see SAP Library for SAP NetWeaver 7.0 Including Enhancement Package 2 at http://help.sap.com/netweaver . In SAP Library, choose SAP NetWeaver  SAP NetWeaver by Key Capability   Application Platform by Key Capability  Platform-Wide Services Connectivity  Communication Interfaces for Mail and Telephony  SAPconnect (BC-SRV-COM) SMTP Config Guide . See also the following SAP Notes: 

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



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



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

For information about integrating SMC , see SAP Note 1636870.

(C) SAP AG

10

Technical Settings

(C) SAP AG

11

Naming Logical Systems for the Connection to SAP ERP and SAP TM You use this Customizing activity to name the logical system used in the remote function call (RFC) connection to SAP TM.

Procedure 1.

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

This is a cross client-activity. 2.

Define the logical system for SAP ERP, for example, ERPCLNT001. The standard naming >CLNT< client no.>, for example, QV5CLNT750. convention is CLNT< client no.>, for example, B1TCLNT750. convention is CLNT. If so, no system and your SAP TM system in the format  (for example, QV5750 for your SAP and client as
View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF