Hierarchy
EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR⤷
FI-TV-COS (Application Component) Travel Expenses⤷
PTRC (Package) Customizing for Travel Management
IMG Activity
| ID | OALE_HRDST_PATRV_04 | Configure Integration of Travel Management and Funds Management |
| Transaction Code | S_AHR_61000354 | IMG Activity: OALE_HRDST_PATRV_04 |
| Created on | 19981221 | |
| Customizing Attributes | OALE_HRDST_PATRV_04 | Set Integration of Travel Management and Funds Management |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OALE_HRDST_PATRV_04 |
This section explains the settings needed for the scenario Integration of Travel Management and Funds Management.
Prerequisites
- The Travel Management system has release 4.5A or higher.
- The Funds Management system has release 4.5A or higher.
I. Procedure for Creating or Changing a Trip
Procedure in the Travel Management system: sender system (server)
When a trip is created or changed, the anticipated expenses are determined by means of simulated travel accounting.
The anticipated expenses are used to check whether business trip commitments can be created on the commitment items, funds centers and funds specified in the trip or in HR master data. For distributed systems, this is a remote, cross-system check.
If business trip commitments can be created, the data necessary for this is transferred to the receiver system asynchronously across the ALE layer.
Procedure in Funds Management system: receiver system (client)
The data for business trip commitments is posted to the Funds Management system.
II. Procedure for Transferring Travel Expenses to Accounting
Procedure in the Travel Management system: sender system (server)
During the process of transferring travel expenses to accounting, the information that is relevant for posting is evaluated, collected, and then transferred to Accounting and more specifically to Funds Management. With distributed systems, the read, write and validation operations in the Accounting system are cross-system operations. Before each cross-system operation, therefore, the Travel Management system determines the receiver system on the basis of your entries in the distribution model. This means:
- During creation of trip transfer documents, various data is read synchronously in Accounting via BAPIs.
- When the trip transfer documents are posted, each document is transferred asynchronously to the receiver system via the ALE layer.
Procedure in Funds Management system: receiver system (client)
The data is posted in the Accounting system. This posting cancels the business trip commitments and debits the travel budget.
Maintaining the Distribution Model
To enable communication between the systems during distribution, enter the relevant method for the objects of the following table in the step Maintain Distribution Model with Create Method. Enter the following for the sender and receiver system:
- Sender/client: the Travel Management system
- Receiver/server: the Funds Management system
Object Name Method Meaning
AcctngTravelExpenses Check Validation of document for
creating commitment
AcctngTravelExpenses Post Posting of document for
creating commitment
The following message type is used:
Object Method Message Type
AcctngTravelExpenses.Post ACC_TRAVEL
The company code can be used as a filter object.
Note
All settings for the ALE scenario Transfer Travel Expenses to Accounting in the distribution model must be made as well.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OALE_HRDST_PATRV_04 | 0 | HLA0009705 A HLA0009200 A HLB0006330 |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20050628 |
| SAP Release Created in |
