SAP ABAP IMG Activity OALE_HRDST_16_3 ('HR Rel.earlier than 4.0A and Acctg Rel. from 4.0A' 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_16_3 'HR Rel.earlier than 4.0A and Acctg Rel. from 4.0A' scenario  
Transaction Code S_AHR_61000399   IMG Activity: OALE_HRDST_16_3 
Created on 19981221    
Customizing Attributes OALE_HRDST_16_3   HR Release Earlier Than 4.0A and Accounting Release as of 4.0A 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OALE_HRDST_16_3    

In this step, you make the settings for the scenario Reporting for Posting Payroll Results to Accounting (known also as posting to Accounting) if Human Resources (HR) is in an R/3 System lower than 4.0A or in a R/2 System, and Accounting (AC) in an R/3 System in Release 4.0A or higher.

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

The following outlines the posting procedure in previous releases with reference to the relevant settings in Customizing. The process 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 accounting system.
  • 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. Run the report RPCALx0 using schema x500. This transfers relevant posting information to a TemSe file.
  2. Run the report Interface Payroll / Accounting EXPORT (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 automatically the data to the receiving system.

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 (RPCIPI00). The Accounting System uses data stored in the TemSe file to create posting documents.
  2. Post the documents to Accounting

Maintaining the Customer Distribution Model (Variant A)

To enable communication between distributed systems, you must make the following entries in Customizing under Basis -> 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 Payroll application is in a release before 4.0A, and you have not maintained the distribution model.

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

  1. Run report RPCALC x0 using schema x500. This transfers information relevant to posting 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 report RPCIPT00. The AC system creates a TemSe file.
  2. Run the report <lsInterface Payroll / Accounting IMPORT (RPCIPI00). The AC system uses data in the TemSe file to create posting documents.
  3. Post the payroll results to Accounting.

Further notes

For Release 4.0A, the naming convention for symbolic accounts was changed. The code that identifies an account, which is stored in the table T030, is now composed of four characters instead of two. This means that in the constellations described in this step, there are different keys in the HR and AC Systems. The code in the AC System is composed of the two character country grouping and the two character code in the HR System. For example, if the code of a symbolic account is 13 in the HR System, the code for the same account in the AC System for the country grouping Germany is 0113.

For Release 4.0A, the naming convention for the employee grouping for account determination (Feature PPMOD) was changed. The code for the employee grouping for account determination , which from Release 4.0A is stored in the table T52EM, is now composed of three characters instead of one. This means that in the constellations described in this step, there are different codes in the HR and AC Systems. The code 1 for the employee grouping for account determination becomes 1__ in the HR System (single character code from the HR System plus two spaces).

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_16_3 0 (HLA0100670  
SIMG OALE_HRDST_16_3 1 A HLB0006330  
SIMG OALE_HRDST_16_3 2 A HLA0009200) O  
SIMG OALE_HRDST_16_3 3 (HLA0100670  
SIMG OALE_HRDST_16_3 4 A HLB0006330  
SIMG OALE_HRDST_16_3 5 A HLA0009209)  
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19981221 
SAP Release Created in