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 | SIMG_OHR0280A | Organizational Requirements for Transfer |
| Transaction Code | S_AHR_61000742 | IMG Activity: SIMG_OHR0280A |
| Created on | 19981221 | |
| Customizing Attributes | SIMG_OHR0280A | Organizational requirements for transfer |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_OHR0280A |
Payroll and Travel Management are located in different logical systems (such as in different SAP systems, or in one SAP system in different clients). Business trips should only be processed in Travel Management.
General Problem Description
As a rule, it is technically possible to process trips in both logical systems. If trips are also processed in the logical system of Payroll, there will be data inconsistencies between cluster TE in the logical system of Travel Management and the logical system of Payroll. Such inconsistencies have serious negative effects, such as on the transfer of trip accounting results to Financial Accounting. For this reason, the Travel Management functions and procedures in the logical system of Payroll must be locked against execution. Program RPCLSTTE or transaction PRTE can always be used to check the transferred trip data in the Payroll system.
Solution for Logical Systems in Separate SAP Systems
The program RPRTLOCK is available for this purpose. The Travel Management functions and processes can be unlocked with the program RPRTULOC. The lock can only be applied to the transaction level and is therefore effective for all clients in a SAP system.
Solution for Logical Systems at Client Level
The program RPRTLOCK (for all clients) cannot be used if the logical systems of Travel Management and Payroll are located in different clients of the same SAP system. In this case the Travel Management functions and processes can only be locked in the logical system of Payroll by means of authorization checks.
Example
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 | SIMG_OHR0280A | 0 | AHR0000302 | Integration With Payroll |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19981221 |
| SAP Release Created in |
