Posting to AC Systems < 4.0 (SAP Library

Posting to AC Systems < 4.0

Use

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 is in an R/2 system.

When posting to Accounting, only the functions available in both release statuses are supported. The most important functions and restrictions are named in the following:

You can repeat 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), the system can perform a summarized posting 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 system does not post to the substitute cost center.

Prerequisites

Accounting is located 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.

Posting Using a File Transfer

Steps in the HR System (Sending System)

Perform the step creating a posting run. We recommend that you only create live posting runs even if this is not absolutely necessary in the current constellation. If you want to use the revision information, set the indicator Revision help Export R/3 3.x. 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.

Start the report Transfer to Accounting: Import from R/2 or R/3 < 4.0 (RPCIPX00).

The HR system creates another TemSe file.

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.

Steps in the AC System (Receiving System)

To further process the file created by the HR system, start the report Posting to Accounting: Transfer Program for RPCIPX00 and RPCIPI00 (RPCIPT00).

The AC system creates a TemSe file.

Start the report Transfer to Accounting: Import from R/2 or R/3 < 4.0 (RPCIPI00).

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.

Post the payroll results by processing the batch input session.

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

Be aware of the following special feature in this step: You must not manually set the posting run to posted if posting documents and the TemSe file exist for this posting run, as the company codes exist in another AC system with release status 4.0A or higher. In this case, you must release the posting documents in the HR system and finally post.

Posting Using an ALE Business Process

Steps in the HR System (Sending System)

Perform the step creating 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. If you want to use the revision information, set the indicator Revision help Export R/3 3.x. 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.

Start the report Transfer to Accounting: Import from R/2 or R/3 < 4.0 (RPCIPX00).

The HR system creates a master Idoc from the TemSe file.
The HR system uses 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 here. When doing so, the AC system creates a TemSe file from the data in the Idoc it has received.

Steps in the AC System (Receiving System)

Start the report Transfer to Accounting: Import from R/2 or R/3 < 4.0 (RPCIPI00).

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

Post the payroll results by processing the batch input session.
Select the posting run created in the overview of posting runs in the HR system. Choose Edit ® In old releases ® Manually set to posted.

Be aware of the following special feature of this step: You must not manually set the posting run to posted if posting documents and the TemSe file exist for this posting run, as the company codes are in another AC system with release status 4.0A or higher. In this case, you must release the posting documents in the HR system and finally post.

Bear in mind 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 the system is unable to distribute all the account assignment objects using ALE applies for ALE scenarios.

Result

The payroll results were transferred and posted to the Accounting components.