Posting from HR Systems < 4.0
Use
It is still possible to post to Accounting if Accounting is in an R/3 system with a release status of 4.0A or above and Payroll is in an R/3 system with a release status below 4.0A or is in an R/2 system.
When posting to Accounting, only the functions available in both release statuses are supported. In the following, the most important functions and restrictions are named:
· In Financial Accounting (FI) you have the option of summarized posting.
· When posting to fixed cost centers, you can specify the fixed cost center for each business area.
· In the case of CO account assignments, which cannot be posted to, the system posts to the substitute cost center. Substitution takes place using the substitute cost center and not the master cost center. The master cost center is not provided in this constellation of the HR system.
Prerequisites
· Accounting is situated in a central system, along with all the components.
· The Accounting master data (for example, cost centers to which you want to post) must be available in the HR system.
Procedure
In order to post from HR systems with a release status lower than 4.0A, you must create a TemSe file, from which posting documents are created, after completing payroll in the Accounting system (AC-system). You have two options for creating this TemSe file:
· Using a file transfer
· Using an ALE business process (using IDocs in the HR system)
If you want to use ALE technology for this purpose, you must make the relevant settings in ALE Customizing.
If the HR system has a release status lower than 3.1G, you can only post using a file transfer.
You can display the content of the TemSe files, created with the following programs, using program RPCIPL00 (Transfer FI/CO: Display TemSe Object). For more information, see the report documentation.
Posting Using a File Transfer
Steps in the HR System (Sending System)
...
1. Start the report Payroll program <Country> (RPCALCx0) with the payroll schema x500.
The HR system evaluates the payroll results and writes the posting-relevant information to a TemSe file.
2. Start the report Transfer to Accounting: Export to R/2 or R/3 Release < 4.0 (RPCIPX00).
The HR system creates a second modified TemSe file from the first TemSe file.
3. Start the report Posting to Accounting: Transfer Program for RPCIPX00 and RPCIPI00 (RPCIPT00).
The HR system creates a work file on the presentation or application server from the second TemSe file.
Steps in the AC System (Receiving System)
4. Start the report Posting to Accounting: Transfer Program for RPCIPX00 and RPCIPI00 (RPCIPT00), to further process the file created by the HR system.
The AC system creates a TemSe file.
5. Start the report Transfer to Accounting: Import from R/2 or R/3 < 4.0 (RPCIPI00).
The AC system creates posting documents from the data for the TemSe file. These documents are grouped together in one posting run.
7. Check the posting documents
During this procedure, consider that revision information is not available in this constellation. For more information, see using revision information.
8. Release the posting documents.
Posting Using an ALE Business Process
Steps in the HR System (Sending System)
...
1. Start the report Payroll program <Country> (RPCALCx0) with the payroll schema x500.
The HR system evaluates the payroll results and writes the posting-relevant information to a TemSe file.
2. Start the report Transfer to Accounting: Export to R/2 or R/3 Release <4.0 (RPCIPX00).
- The HR system creates a master Idoc from the TemSe file.
- The HR system uses the Customizing for the distribution model to determine from which logical system the Idoc should be received.
- The data is transferred to the AC system via the ALE layer. Inbound processing takes place there. When doing so, the AC system creates a TemSe file from the data in the Idoc received.
Steps in the AC System (Receiving System)
3. Start the report Transfer to Accounting: Import from R/2 or R/3 < 4.0 (RPCIPI00).
The AC system creates posting documents from the data for the TemSe file. These documents are grouped together in one posting run.
5. Check the posting documents
During this procedure, consider that revision information is not available in this constellation. For more information, see using revision information.
6. Release the posting documents.
Consider that this ALE business process has the following restrictions:
· The TemSe objects created are not defined as application objects. For this reason, the system does not update links between the TemSe object and the Idoc.
· The system does not support serialization.
· In connection with the prerequisite already mentioned, that the Accounting master data must be available in the HR system, the restriction that not all account assignment objects can be distributed using ALE applies for ALE scenarios.
Result
The payroll results were transferred and posted to the Accounting components.