R/3 Travel Management (TRV) can be used

1. in combination with R/3 Human Resources (HR) and R/3 Accounting (AC)
2. in combination with HR and separate from AC
3. in combination with AC and separate from HR
4. separate from HR and AC

Depending on the configuration Support Packages (SP) and HR Support Packages (HR SP) have to be imported into the respective systems.

• No need for distribution of:

• HR master data
• Travel expense results to Payroll
• CO receivers

• Validation of CO receivers is carried out locally
• Synchronous posting of travel expense results to Accounting

• Human Resources, Accounting and Travel Management have to have the same release status
• Lack of flexibility

• Possible capacity problems

• No distribution of travel expense results for Payroll
• Travel Management and Accounting can have a different release status
• Existing accounting systems can be connected

• Remote validation of CO receivers in Accounting via ALE
• CO receivers have to be replicated in the Travel Management system to provide a correct input help for CO receivers
• To create person-related vendors automatically, the HR master data (Infotypes 0000, 0001, 0002, 0003, 0006, 0009, 0017, 0105) has to be replicated in the Accounting system via ALE.
• Asynchronous posting of travel expense results to Accounting via ALE. To guarantee a successful posting to the Accounting system in this case, the posting run has to be validated before it is sent.

• No distribution of CO receivers is required
• CO receivers are validated locally
• Human Resources and Travel Management can have a different release status
• Synchronous posting of travel expense results to Accounting. In this case documents in a posting run containing errors can be rejected

• HR master data (Infotypes 0000, 0001, 0002, 0003, 0006, 0009, 0017, 0105) has to be replicated via ALE
• Travel expense results for Payroll have to be replicated via ALE
• Both the Support Packages and the HR Support Packages have to be imported into the Travel Management/Accounting systems.

• Human Resources, Travel Management and Accounting can all have a different release status
• Maximum flexibility
• Existing Accounting and HR systems can be connected

• HR master data (infotypes 0000, 0001, 0002, 0003, 0006, 0009, 0017, 0105) has to be replicated in the Travel Management system via ALE
• To create person-related vendor master records in Accounting automatically, the HR master data (infotypes 0000, 0001, 0002, 0003, 0006, 0009, 0017, 0105) has to be replicated in the Accounting system via ALE.
• Travel expense results for Payroll have to be replicated via ALE
• Remote validation of CO receivers
• CO receivers have to be replicated in the Travel Management system to provide a correct input help for CO receivers
• Asynchronous posting of travel expense results to Accounting via ALE. To guarantee a successful posting to the Accounting system in this case, the posting run has to be validated before it is sent.

For more information on setting up ALE scenarios, see, for example, the implementation guide (IMG) for Basis under Application Link Enabling (ALE) ® Modeling and Implementing Business Processes ® Predefined ALE Business Processes ®

• Human Resources ® HR <-> HR ® Set Distribution of Trip Accounting Results
• Human Resources ® HR <-> AC ® Set up Trip Costs Transfer
• Human Resources ® HR <-> AC ® Set Up Integration of Travel Management and Funds Management