SAP ABAP IMG Activity OALE_HRDST_PCPCO_02 (Szenario 'HR und RW mit Release ab 4.6A' einstellen)
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_PCPCO_02 Szenario 'HR und RW mit Release ab 4.6A' einstellen  
Transaction Code S_AHR_61012647   (empty) 
Created on 19990225    
Customizing Attributes OALE_HRDST_PCPCO_02   Szenario 'HR und RW mit Release ab 4.6A' einstellen 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OALE_HRDST_PCPCO_02    

This section explains which settings you need to maintain for the scenario Transferring Personnel Cost Planning Results to CO when the Personnel Cost Planning component and the Controlling component are in different systems but both are of release 4.6A or higher.

Process

The Personnel Cost Planning online documentation describes the general integration with CO process.

For information on how to set up the integration between the Personnel Cost Planning component and the Controlling component when they are not in distributed systems, see Set Up Integration with Controlling in the Compensation Management Implementation Guide.

The following describes the integration set up when they are in distributed systems.

Functions in the HR System: Sender System (Server)

When you release a plan scenario and transfer the personnel cost planning results to Controlling, the system adjusts the time-related personnel costs to fit in the corresponding CO periods. The system then posts the results to CO. In distributed systems, all the read, write and validation checks take place in the CO system, therfore, before each cross-system operation, the HR system determines the recipient system based on your entries in the distribtion model.

  1. Once you have released the plan scenario and the system has formatted the personnel costs into periods, the system then uses a BAPI to read the different types of data in the CO system.
  2. As soon as the posting of the planning data has been triggered, the following takes place:
    1. The system validates the posting data against the CO data using a synchronous BAPI.
    2. The system transfers the data to the recipient system asynchronously via the ALE layer.

Functions in the CO System: Recipient System (Client)

  1. The system posts the data in the CO system.

Maintaining the Distribution Model

To ensure the communication flow between the two systems, you need to specify a message type and/or an object complete with method when you maintain the distribution model. Enter the following as the sender and recipient system:

o Sender/Client: HR System

o Recipient/Server: CO System

Object Name Method Meaning

ControllingArea GetPeriod Determines posting period from

fiscal year; controls the

fiscal years involved when a

plan is released

ControllingArea GetPeriodLimits Determines validity periods

for the posting periods

PlanDataTransferCO GetSourceInfos Determines the CO posting

parameter

PlanDataTransferCO CheckPrimaryCosts Validates the Personnel Cost

Planning posting data in CO

PlanDataTransferCO PostPrimaryCosts Posts the Personnel Cost

Planning data in CO

The following message types are used:

Object Method Message Type

PlanDataTransferCO.PostPrimaryCosts PDTCO_POSTPRIMARY

You can use the controlling area as a filter object.

Partner Profiles

You can generate the partner profiles from the distribution model. For information on how to do this, read the documentation on Generating Partner Profiles in this implementation guide.

Settings in the CO System

Master Data for the HR System

To transfer Personnel Cost Planning results, you must distribute the following master data from CO:

  • Cost centers
  • Cost elements (validation and possible entries)

The Master Data Distribution section in the ALE IMG explains how to send the relevant CO master data from the CO system to the HR system.

Activities

  1. Check to see whether the communication flow for the objects ControllingArea and PlanDataTransferCO for the methods given have been maintained in your customer distribution model.
  2. Make sure that the necessary CO master data has been distributed into the HR system.

Further notes

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-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_PCPCO_02 0 HLB0006330 A  
SIMG OALE_HRDST_PCPCO_02 1 HLA0009709 A  
SIMG OALE_HRDST_PCPCO_02 2 HLA0009400 Controlling 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19990225 
SAP Release Created in