Professional Documents
Culture Documents
Travel MGT Businscen8a TM 46cv2
Travel MGT Businscen8a TM 46cv2
6c
Version 2
March 2001
English
Configuration Guide
One-step Travel Management
SAP AG
Neurottstr. 16
69190 Walldorf
Germany
Copyright
© Copyright 2001 SAP AG. All rights reserved.
No part of this brochure 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®, NT®, EXCEL®, Word® and SQL Server® are registered trademarks of
Microsoft Corporation.
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,
AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
ORACLE® is a registered trademark of ORACLE Corporation, California, USA.
INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM are registered trademarks of Informix
Soft-ware Incorporated.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of Technology, 545
Technology Square, Cambridge, MA 02139.
JAVA® is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto, CA
94303 USA.
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology
in-vented and implemented by Netscape.
SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com
Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAP Business
Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit, SEM, are
trademarks or reg-istered trademarks of SAP AG in Germany and in several other countries all over the
world. All other prod-ucts mentioned are trademarks or registered trademarks of their respective
companies.
Contents
1 Purpose ............................................................................................................................................. 5
2 Basic Information ............................................................................................................................... 6
2.1 Create Trip Number Ranges ...................................................................................................... 6
2.2 Set up Feature TRVCP for Travel Planning ............................................................................... 6
2.3 Define Price and Availability Strategies...................................................................................... 7
3. Amadeus ........................................................................................................................................ 9
3.1 Create Connection to Amadeus ................................................................................................. 9
3.2 Define Sales Office................................................................................................................... 11
3.3 Define Resubmission for Ticket Issue Queue .......................................................................... 11
3.4 Define API Access Parameters ................................................................................................ 12
3.5 Define User Groups.................................................................................................................. 12
3.6 Define API Access Parameters for User Groups ..................................................................... 13
3.7 Define User Group-specific Travel Service Categories............................................................ 13
4. ALE .............................................................................................................................................. 14
4.1 Define Logical System.............................................................................................................. 14
4.2 Assign Client to Logical System ............................................................................................... 14
4.3 Define Target System for RFC Calls (SP)................................................................................ 15
4.4 Define Target System for RFC Calls (TM) ............................................................................... 16
4.5 Determine RFC Destinations for Method Calls ........................................................................ 17
4.6 Maintain Distribution Model and Distribute Views .................................................................... 18
5. Planning Information .................................................................................................................... 19
5.1 Flights ....................................................................................................................................... 19
5.1.1 Define Trip Rules for Flight ............................................................................................... 19
5.1.2 Define allowed Entries for Flight Trip Rules...................................................................... 20
5.1.3 Define Class Rules for Flight............................................................................................. 21
5.1.4 Define allowed Entries for Flight Class Rules ................................................................... 22
5.1.5 Define Airlines ................................................................................................................... 22
5.1.6 Define Customer Programs of Airlines.............................................................................. 23
5.1.7 Define Enterprise-specific Airfare Rates ........................................................................... 24
5.1.8 Define Enterprise-specific Airfare Discounts..................................................................... 24
5.2 Hotel ......................................................................................................................................... 25
5.2.1 Define Trip Rules for Hotel................................................................................................ 25
5.2.2 Define allowed Entries for Hotel Trip Rules ...................................................................... 25
5.2.3 Define Class Rules for Hotel ............................................................................................. 26
5.2.4 Define Allowed Entries for Hotel Class Rules ................................................................... 26
5.2.5 Define Hotel Chains .......................................................................................................... 27
1 Purpose
This document describes configuration of One-step Travel Management.
Limitations:
1) If you are running Travel Planning in one SAP system (and in one client) you do NOT need to
set up the ALE scenarios as described in 4.
2) If you choose to use the Amadeus connection, you will require authorization. The settings are
for the practice training environment of Amadeus; you do not make real bookings when
running the One-step Travel Management scenario.
3) For hosting by a travel agency, use ALE settings.
4) Travel Agencies hosting Travel Management must set up ALE connectivity.
2 Basic Information
2.1 Create Trip Number Ranges
The travel system assigns a stored trip a trip number.
Personnel Area S300 must be set up.
SAP recommends that you only use internal trip number assignment.
Set up an internal number range for every personnel area under the number range 01 (mandatory
allocation) and / or an external number range under the number range 02 (mandatory allocation).
• Define the Number Range by choosing in IMG:
Financial Accounting→Travel Management→Set Up Trip number ranges
The feature TRVCP is structured as a decision tree and is used to assign employees specific travel
profiles in Travel Planning. The feature is only active if no travel profile is stored for the employee in
infotype '0470' (travel profile).
The standard Set-up for “Otherwise” has changed from Standard to SAP_ALL. Some settings of the
standard delivery will not work when using Best Practices for mySAP Service Providers.
However, to have a better control over the Demo script, it is recommended that you add SAP_ALL in
the infotype 0470 of the personnel record.
• Define by choosing in IMG:
Financial Accounting→Travel Management→ Travel Planning→Dialog and Planning
Control→Travel Planning Control→Set up feature TRVCP for Travel Planning
Flight strategy
Flights, which correspond to the requested data, are valuated by the system according to the preset
travel profile. You receive a list of flights sorted by priorities, which were assigned in the travel profile.
If you choose a neutral setting, the system does not valuate the flights according to the assigned
travel profile and the flights offered, are not listed according to their priorities.
Using Price-controlled availability, you control the function of the Best-price flight pushbutton in
the Planning manager
For the choice of departure and return flights you can specify a certain rule that the user is to comply
with (e.g., same airline for departure and return flights).
An automatic rebooking without considering the travel profile makes sense, for example, if a travel
profile is interpreted very narrowly and therefore no rebooking options into another flight category are
offered by the system, which correspond to the request data and the travel profile.
Hotel strategy:
To maintain company-internal trip provisions, you can limit the availability query using different
criteria.
Car rental strategy:
See Hotel strategy above.
3. Amadeus
To carry out online bookings via AMADEUS the following is required:
• Your enterprise must have a contractual agreement with AMADEUS regarding interface
usage and be a registered user with AMADEUS.
The example shown in the next chapters reflects entries for an office in Frankfurt (Germany). Please
enter your own data here, delivered by AMADEUS.
To use Travel Planning without GDS (Global Distribution System), enter the Parameter
TRV_NO_CRS with value “X” in the parameter list of your user-id (using transaction SU01).
By defining the RFC destination, the connection between Amadeus and SAP is established.
You must set up an SAP Gateway and an Amadeus Gateway.
• Define the Connection by choosing in IMG:
Financial Accounting→Travel Management→Travel Planning→Master Data→Control
Parameters for Travel Planning→Setup RFC Destination for Travel Planning
4. ALE
Refer to section 1 to decide whether ALE must be set up.
The screen pictured below is an example of naming convention and does not reflect actual or
required settings.
• Define the Target System for RFC by choosing in IMG:
Basis Components→Application Link Enabling (ALE) →Sending and Receiving
Systems→Systems in Network→Define Target System for RFC Call
The maintenance of the RFC destination is not a part of the automatic Change and Transport
System. Therefore the setting has to be made manually on all systems.
The distribution model consists of separate model views in which all the associated, cross-system
message flows in your organization can be defined. These views must be distributed to the receiving
systems.
In the individual message flows you can define filters to determine which data is to be transferred to
which receiving systems. The distribution model controls this distribution.
After maintaining the distribution model you have to generate this model in the receiving system.
• Maintain by choosing in IMG:
Basis Components→Application Link Enabling (ALE) →Modeling and Implementing Business
Processes →Maintain Distribution Model and Distribute Views
5. Planning Information
5.1 Flights
5.1.1 Define Trip Rules for Flight
• Define the Trip rules by choosing in IMG:
5.2 Hotel
5.2.1 Define Trip Rules for Hotel
• Define the trip rules by choosing in IMG:
Financial Accounting→Travel Management→Travel Planning→Trip Rules and Profiles→Trip
Rules→Trip and Class Rules for Hotels→Define trip rules for Hotels
6. Travel Profiles
6.1 Define Travel Profiles
A travel profile is defined in R/3 Travel Planning via assignment of the following factors:
• Trip activity type
• Travel service category
• Trip rule and its priority
• Class rule of the respective travel service category
If the personnel profile is not maintained, the organizational profile controlled by feature TRVCP is
automatically applied. Then the employee's organizational assignment in the company is used as the
basis for considering travel policy.
You can specify the travel profiles for the respective employees in infotype '0470' (Travel Profile).
Feature TRVCP: for example, members of the board of directors are given special flight rules
(booking of first class only).
• Define the travel profile by choosing in IMG:
Financial Accounting→Travel Management→ Travel Planning →Trip Rules and
Profiles→Travel Profiles →Define travel profiles