Kontakt

Ansicht
Dokumentation

OALE_HRDST_PCPCO - Configure Scenario 'HR or Accounting With Release Earlier Than 4.6A'

OALE_HRDST_PCPCO - Configure Scenario 'HR or Accounting With Release Earlier Than 4.6A'

Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

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. Here we assume that at least one system is release 4.6A.

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.

In distributed systems, all the read, write and validation checks take place in the CO system, therefore, before each cross-system operation, the HR system determines the recipient system based on your entries in the distribution model.

Functions in the HR System

  1. Release a plan scenario for CO. As a result of this, the system defines the appropriate fiscal year.

Functions in the CO System

  1. The transfer of the planned personnel costs for a released plan scenario is started.
  2. The system formats the time-dependent personnel costs to fit into the corresponding CO periods and sends them synchronously via RFC (no IDoc is sent) and posts them 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.

The sending and receiving system assignment is as follows:

  • Sender: ,,,,,,CO System
  • Receiver: ,,,,,,HR System
Message type Meaning
HRCPRQ Personnel Cost Planning - Request from CO to HR for
data transfer

SAP does not support the use of filter objects.

  • Client: ,,,,,,HR System
  • Server: ,,,,,,CO System
Object name Method Meaning
ControllingArea GetPeriod Determine posting period from fiscal year;
Controls the fiscal years involved when a
plan is released

If your CO System is release 3.1 or lower, do not make the settings for the ControllingArea object.

Partner Profiles

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

The following message types have been defined:

Message Type Meaning
HRCPRQ Personnel Cost Planning - Request from CO to HR

This message type has the following partner profiles:

  • Outbound: Central Accounting (CO)
  • Inbound: ------

In the CO system for the HR partner system, define the outbound parameters for the message type HRCPRQ. Use the basis IDoc type SYNCHRON. You do not have to define any parameters for the message type in the HR system.

Settings in the CO System

HRCPRQ

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.

HRCPRQ

To release a Personnel Cost Planning plan scenario, you must determine the fiscal year variant. If the CO system has a lower release than 4.0, you must transfer the customizing data for the fiscal year variant into the HR system. In this instance, you cannot maintain the object method ControllingArea.Getperiod in the distribution model. The table contents are normally copied by the transport system.

Activities

  1. Check to see whether the communication flow for the logical message type HRCPRQ and the method GETPERIOD for the object CONTROLLINGAREA has been maintained in your customer distribution model
  2. Check to see whether a partner profile has been defined for the message type
  3. Make sure that the necessary CO master data has been distributed to the HR System

Further notes

The following releases are supported:

  • CO System 4.0/4.5 - HR System 4.0/4.5:
    Use the above documentation in this instance
  • CO System 3.1 - HR System 4.0/4.5:
    Use the 3.1 Personnel Cost Planning scenario documentation. Make sure you take the special features with regards the fiscal year variant into account.





BAL_S_LOG - Application Log: Log header data   General Material Data  
This documentation is copyright by SAP AG.

Length: 5860 Date: 20240523 Time: 215546     sap01-206 ( 84 ms )