SAP ABAP IMG Activity OALE_HRDST_PAPAY ('HR Rel. 4.0A and Acctg Release Earlier than 4.0' Scenario)
Hierarchy
☛ SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR
   ⤷ PA-OS (Application Component) Organizational Structure
     ⤷ PP0C (Package) Organization and Planning - Customizing
IMG Activity
ID OALE_HRDST_PAPAY 'HR Rel. 4.0A and Acctg Release Earlier than 4.0' Scenario  
Transaction Code S_AHR_61000397   IMG Activity: OALE_HRDST_PAPAY 
Created on 19981221    
Customizing Attributes OALE_HRDST_PAPAY   HR Release 4.0A and Accounting Release Earlier Than 4.0 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OALE_HRDST_PAPAY    

This step explains the settings required for the scenario Reporting of Payroll Results for Posting to Accounting, known also as posting to Accounting if Human Resources (HR) is in an R/3 System with a release in or above 4.0A and Accounting (AC) in an R/3 System in a release lower than 4.0A, or in an R/2 System.

For information on the procedure for posting to Accounting in previous releases, refer to the SAP Library, under Payroll -> country -> Subsequent Activities -> Posting to Accounting -> Steps in Posting to Accounting -> Posting in Previous Releases. This also provides information on the functions that are available in the system constellations described and what restrictions apply.

The following outlines the posting procedure in previous releases with reference to the relevant settings in Customizing. The procedure distinguishes between two variants (A and B).

  • If Payroll is in Release 3.1G or higher, but below 4.0A, you can use either variant A or B for posting to Accounting.
  • If Payroll is in a release lower than 3.1G, you must use variant B.

Prerequisites for Both Variants

  • All Accounting components are located in a central system.
  • In Customizing, under Payroll -> <country> -> 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 , you have specified the company code that is in an AC System with a lower release than 4.0.
  • Accounting master data used in this scenario must be distributed in the HR system (for example, cost centers to which you want to assign accounts).

Variant A

The following procedure applies if your Payroll application is in Release 3.1G or higher, but lower than 4.0A, and if you want to use ALE in this scenario.

I. Procedure in the HR System: Sending System (Variant A)

  1. If you have carried out the step Create Posting Run (Report RPCIPE00), the posting-relevant information is written to a TemSe file.
  2. Run the report Interface Payroll/Accounting EXPORT (report RPCIPX00).
    • This creates a master IDoc in the HR System.
    • The system uses data entered in the distribution model to determine which logical system should receive the IDoc.
    • The ALE layer is used to transfer the data to the receiving system automatically.

II. Procedure in the AC System: Receiving System (Variant A)

Inbound processing of the IDoc received takes place automatically. The system uses data from the received IDoc to create a TemSe file.

  1. Run the report Interface Payroll /Accounting IMPORT (report RPCIPI00). The Accounting System uses data stored in the TemSe file to create posting documents. From the data in the TemSe file, the AC System creates batch input sessions for the transaction Post document (FB01) and, if necessary, for the transaction Repost primary costs (KB11).
  2. Post the documents to Accounting by starting the batch input session.

Maintaining the Customer Distribution Model (Variant A)

To enable communication between distributed systems, you must make the following entries in Customizing for ALE, under Basis -> Distribution (ALE) -> Modeling and Implementing Business Processes -> Maintain Distribution Model -> Add Method :

Sender:     HR System

Receiver:     AC System

Message type:     HRPAYP

Standard task:    HRPAYP_ERROR

This procedure does not use filter objects. You do not need to convert field objects or to filter segments.

Partner profiles (Variant A)

The settings for the partner profiles can be generated from the distribution system. For more information, refer to the step Generate Partner Profiles in this Implementation Guide.

Further notes

(For Variant A)

  • The TemSe objects created via this ALE scenario are not defined as application objects. For this reason, the system does not update links between TemSe objects and IDocs.
  • The ALE scenario does not support serialization.
  • In line with the requirement that AC master data must be available in the HR System, the following restriction applies to ALE scenarios: Not all account assignment objects can be distributed using ALE.

Variant B

The following procedure applies if your Accounting System has a lower release than 4.0, and you want to post using file transfer.

I. Procedure in the HR System: Sending System (Variant B)

  1. If you have carried out the step Create Posting Run (Report RPCIPE00), the information relevant for posting is written to a TemSe file.       
  2. Run report Interface Payroll /Accounting EXPORT (RPCIPX00). This creates another TemSe file.
  3. Run report RPCIPT00 for Posting to Accounting. This creates a file on either the presentation or application server.

II. Procedure in the AC System: Receiving System (Variant B)

  1. Run the report RPCIPT00. The AC System creates a new TemSe file.
  2. Run the report Interface Payroll/Accounting IMPORT (report RPCIPI00). The AC System creates batch input sessions from the TemSe file for the transaction Post document (FB01) and, if necessary, for the transaction Repost primary costs (KB11).
  3. Post the payroll results by processing the batch input sessions.

Further notes

(for both variants)

If you use an HR System with release 4.0A or higher, and you want to carry out posting in the constellations described here, you cannot use the symbolic accounts in the standard system becasue from release 4.0A, the codes for symbolic accounts have four instead of two characters. In the constellations described here, only the last two characters are posted to the AC System. This is addressed in an HR system upgrade to release 4.0A or higher, but is not reflected in the sample Customizing of a new HR System in release 4.0A or higher.

For Release 4.0A, the length of the codes for employee groupings for account determination (Feature PPMOD) was changed. The code for employee grouping for account determination, which, from Release 4.0A, is stored in table T52EM, is now composed of three characters instead of one. Consequently, there are different codes in the HR and AC Systems. The key 123 for employee grouping for account determination in the HR System appears as 1 in the AC System (only the first character is considered).

The assignment of symbolic accounts in HR to accounts in Accounting usually takes place in table T030 in the AC System. If you want to carry out cost planning in the AC System for the constellations described in this step using report RPCIPE00, you must make entries in the table T030 in both HR and AC Systems.

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 OALE_HRDST_PAPAY 0 ( HLA0009706 A HLA0009200  
SIMG OALE_HRDST_PAPAY 1 A HLA0009200 ) O  
SIMG OALE_HRDST_PAPAY 2 ( HLA0009706 A HLA0009200  
SIMG OALE_HRDST_PAPAY 3 A HLA0009400 )  
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19981221 
SAP Release Created in