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_33 | Set Distribution of Trip Accounting Results |
| Transaction Code | S_AHR_61000390 | IMG Activity: OALE_HRDST_33 |
| Created on | 19981221 | |
| Customizing Attributes | OALE_HRDST_33 | Set Distribution of Trip Accounting Results |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OALE_HRDST_33 |
Procedure
If you use Travel Management in a logical system other than payroll accounting, Travel Management offers the option to transfer the trips from the Travel Management system to payroll accounting as a partial copy.
A retroactive accounting date or adjustment indicator can, of course, be set in Infotype 0003 for the relevant personnel numbers. The payroll accounting program RPCALCX0 can then run the same as it would if the systems were integrated.
In this situation, the travel accounting period of the travel accounting program or of the transfer program in the payroll accounting control record (in the payroll accounting system) is defaulted or checked against.
Procedure in the Travel Management System: Sender System
- The report RPRPAY00 collects all trips to be transferred to a payroll accounting system and places them in an IDoc.
Procedure in the Payroll Accounting System: Receiver System
- Inbound processing of the incoming IDocs (BAPI PayrollTravelExpnsesPost) is triggered automatically. Inbound processing writes the data from the IDoc trip by trip as TE clusters to the database PCL1 or the transparent tables PTRV_HEAD and PTRV_PERIO.
- A retroactive accounting date or a revision indicator may be set in infotype 0003 for the relevant personnel number.
Maintenance of the Distribution Model
To guarantee the communication between systems during a distribution, the following entries must be made in the step Maintain distribution model:
- Client: Travel Management System
- Server: HR Payroll Accounting System
- Object: PayrollTravelExpnses (BUS7001)
- Method: Post
Note: the client is the system in which the BAPI is called (sender system), the server is the system on which it is executed (receiver system).
The object method PayrollTravelExpnses.Post is based on the message type HRTRPR.
All existing segments must be transferred, otherwise the information transferred to the HR Payroll Accounting System is incomplete.
Partner Profiles
The setup of partner profiles can be generated from the distribution model. For more information, read the section Generate partner profiles in this implementation guide.
Settings in the Travel Management System
Make sure that the L+G entry in Feature TRVPA is coded with 1, 2 or 3. This activity must be checked in the section Travel Management -> Dialog and Accounting Control -> Accounting Control -> Set Up Feature TRVPA for Trip Costs Parameter in the Travel Management IMG.
Settings in the HR Payroll Accounting System
Lock Travel Management Transactions
As a rule, it is technically possible to edit trips in both logical systems. If trips are also edited in the logical system of payroll accounting, data inconsistencies occur between the cluster TE of the logical system of Travel Management and that of the payroll accounting system. These data inconsistencies have a severe effect, for example, on transferring of trip costs accounting results to financial accounting. Consequently, the functions and procedures of Travel Management in the logical system of payroll accounting must be locked against execution. You can always use the report RPCLSTTE or transaction PRTE to check the transferred travel data in the payroll accounting system.
Solution for logical systems in separate SAP systems:
For this purpose, there is the report RPRTLOCK. The Travel Management functions and processes can be unlocked again via the report RPRTULOC. Locking can only take place at the transaction level and, therefore, is effective for all clients in an SAP system.
Solution for logical systems at the client level:
The trans-client report RPRTLOCK cannot be used if the logical systems of Travel Management and Payroll Accounting were installed in different clients of the same SAP system. The locking of Travel Management functions and processes in the payroll accounting logical system must, in this case, be set up via an authorization check.
Check of Feature TRVPA
Check also in the HR Payroll Accounting System to be sure that the L+G entry in feature TRVPA is coded with 1, 2, or 3. This activity must be checked in the section Travel Management -> Dialog and Accounting Control -> Accounting Control -> Set Up Feature TRVPA for Trip Costs Parameters in the Travel Management IMG.
Requirements
Standard settings
Recommendation
Activities
Further notes
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_33 | 0 | HLB0006330 A HLA0009705 A HLA0009706 |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20050419 |
| SAP Release Created in |
