It is still possible to post to Accounting if Human Resources is in an R/3 system with a release status of 4.0A or above and Accounting is in an R/3 system with a release status lower than 4.0A or 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:

· You can repeat the creation of the TemSe file. To do so, you must delete live posting runs. If you manually set the status of the posting run to posted in the HR system, in the last step, it is not possible to repeat the creation of the TemSe file.

· It is possible to post to fixed cost centers; however, it is not possible to post using the business area as a basis.

· In Financial Accounting (FI), a summarized posting can be performed if the AC system has a release status of 3.0A or above. For this purpose, you must specify the clearing cost center in the AC system in Payroll Customizing under Transfer to FI/CO ® Concluding Activities ® Maintain Clearing Cost Centers. Before starting the report Transfer to Accounting: Import from R/2 or R/3 < 4.0 (RPCIPI00), set the Assign clearing cost center indicator.

· In the case of closed cost centers, the substitute cost center is not posted to.

Prerequisites

· Accounting is situated in a central system, along with all the components.

· You have specified the company codes that are in the AC system with a release status below 4.0 in Payroll Customizing, under Reporting for Posting Payroll Results to Accounting ® Special Scenarios ® Posting in Previous Releases ® Set Up Export to R/2 System or R/3 System < 4.0.

· The Accounting master data (for example, the cost centers to which you want to post) must be available in the HR system.

Procedure

To post to AC systems with a release status lower than 4.0A, you must create a batch-input session after completing payroll in the AC system.

If the AC system has a release status of 3.1G or above, you have two options for performing the posting.

· Using an ALE business process (using IDocs in the HR system)

· Using a file transfer

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. Perform the step Create a Posting Run.. We recommend that you only create live posting runs even if this is not absolutely necessary in the current constellation. Set the indicator Revision help Export R/3 3.x, if you want to use the revision information. If you enter a text for the posting run, the first ten characters of this text form the last ten characters of the name of the TemSe file. If you do not enter a text for the posting run, a number is generated for the last ten characters of the name of the TemSe file.

The HR system evaluates the payroll results and writes the posting-relevant information to a TemSe file.

The AC system creates batch-input sessions from the data in the TemSe file for the transaction Post Document (FB01) and for the transaction Enter Reposting of Primary Costs (KB11), if required.

6. Post the payroll results by processing the batch input session.

7. Select the posting run created in the overview of posting runs in the HR system. Choose Edit ® In old releases ® Manually set to posted.

Consider the following special feature in this step: If there were posting documents as well as the TemSe file for this posting run because company codes are in another AC system with release status 4.0A or higher, you must not manually set the posting run to posted. In this case, you must release the posting documents in the HR system and then post them.

Posting Using an ALE Business Process

Steps in the HR System (Sending System)

...

1. Perform the step Create a Posting Run.. We recommend that you only post live posting runs even if it is possible to post simulation runs in the current constellation. Set the indicator Revision help Export R/3 3.x, if you want to use the revision information. If you enter a text for the posting run, the first ten characters of this text form the last ten characters of the name of the TemSe file. If you do not enter a text for the posting run, a number is generated for the last ten characters of the name of the TemSe file.

The HR system evaluates the payroll results and writes the posting-relevant information to a TemSe file.

The AC system creates batch-input sessions from the data in the TemSe file for the transaction Post Document (FB01) and for the transaction Enter Reposting of Primary Costs (KB11), if required.

4. Post the payroll results by processing the batch input session.

5. Select the posting run created in the overview of posting runs in the HR system. Choose Edit ® In old releases ® Manually set to posted.

Consider the following special feature in this step: If there were posting documents as well as the TemSe file for this posting run because company codes are in another AC system with release status 4.0A or higher, you must not manually set the posting run to posted. In this case, you must release the posting documents in the HR system and finally post.

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