Ansicht
Dokumentation
OALE_HRDST_PATRV_03 - Travel Mgt (Prior to Rel. 4.5A), Accounting (as of 4.5A)
CPI1466 during Backup ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
This section explains the settings needed for the scenario Transfer of Travel Accounting results to Accounting if Travel Accounting (FI-TV, formerly HR-TRV) is in an SAP system with a release lower than 4.5A (but at least 3.1G) and Accounting (FI/CO) is in an SAP system with at least Release 4.5A.
Prerequisites
- Accounting and all of its components are in a central system.
- The master data of Accounting that you use in this scenario must be distributed in the Travel Management System; for example, cost centers for account assignments you want to make. This is, however, only true if Travel Management has a release lower than 4.0A.
I. Procedure in the Travel Management System: Sender system
- You start Initial account assignment program RPRFIN00, after selecting the program parameter 'Transfer work file with ALE'. An IDoc is then created in the Travel Management System.
- On the basis of your entries in the distribution model, the system determines which logical system should receive the IDoc.
- The data is automatically transferred via the ALE layer to the receiver system.
II. Procedure in the Accounting System: Receiver system
- Automatic inbound processing of the received IDoc takes place. From the received IDoc data, the Accounting System creates a sequential work file in the global directory of the receiver system. You already specified the file name in the sender system as a parameter in the initial account assignment program. If your Travel Management System has Release 3.1G or 3.1H, please see note 85179.
- Now start the Posting document program RPRIRB00_30. You can change the name of the work file (please keep the path of the global directory). This program creates a posting run from the data in the work file. Posting runs are managed via transaction PRRW. They are checked, posted or rejected there. The transaction is found via the Travel menu: Edit -> Posting.
- Post the Travel Accounting results by posting the posting run.
Maintaining the distribution model
To guarantee communication between the systems during distribution, in the step
'Maintain distribution model', the following entries must be made via Create message type:
| Sender: | Travel Management System |
| Receiver: | Accounting System |
| Message type: | HRTRVL |
As of Release 4.0A, account assignment objects can be validated in different systems during data entry or accounting of a trip. For this to function, in the step
'Maintain distribution model' the following entries must be made via Create method. Enter the following as sender and receiver systems:
- Sender/Client: Travel Management System (at least Release 4.0A)
- Receiver/Server: Accounting System
| Object name | Method | Meaning |
|---|---|---|
| AcctngServices | CheckAccountAssignment | |
| Account assignment validation | ||
| for trip data entry and | ||
| Travel Accounting |
The use of filter objects is not intended. Do not reset field content and do not filter segments.
The setting of partner profiles can be generated from the distribution model. Please read step 'Generate partner profiles' of this implementation guide.
Further notes
Supported releases:
- Travel Management System 3.1G - Accounting System at least 4.5A
- Travel Management System 3.1H - Accounting System at least 4.5A
- Travel Management System 4.0A - Accounting System at least 4.5A
- Travel Management System 4.0B - Accounting System at least 4.5A
General Material Data Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 5011 Date: 20240523 Time: 190403 sap01-206 ( 66 ms )
