Payroll Accounting and Travel Management are installed in different logical systems (for example, in different R/3 Systems or in one R/3 System in different clients). Business trips should only be processed in Travel Management.
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 Accounting, data inconsistencies result between cluster TE in the logical system of Travel Management and the logical system of Payroll Accounting. These inconsistencies have serious consequences, for example for transfer of trip accounting results to Financial Accounting. For that reason, the Travel Management functions and procedures in the logical system of Payroll Accounting must be locked and execution prevented. The report RPCLSTTE or transaction PRTE can always be used to check the transferred trip data in the Payroll Accounting system.
For this purpose the report RPRTLOCK is available. The Travel Management functions and processes can be unlocked via the report RPRTULOC . The lock can only be performed at the transaction level and is, therefore, effective for all clients in an R/3 System.
The report RPRTLOCK (for all clients) camnot be used if the logical systems of Travel Management and Payroll Accounting are installed in different clients of the same R/3 System. The Travel Management functions and processes can, in this case, only be locked in the logical system of Payroll Accounting by means of authorization checks.