Setting up Payroll Processing with SAP SuccessFactors Employee Central Payroll (Point-to-point integration) (Part 2)

[RubaElhafiz]

Introduction:

This blog will describe the technical setup that must be carried out to enable the integration of SAP SuccessFactors Employee Central Payroll with SAP S/4HANA. In the first part, the steps from the S/4HANA side were detailed and in this part, the steps from the ECP side will be described.

 

The document used during this setup is:

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/2c158dc83732454cb8830b3010e2c322/42228068f0434d1799a...

 

ECP:

Step (1):

This step is usually carried out by the functional consultant.

Tcode: sale> Idoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Process > Global Organizational Units > Cross-System Company Codes

Double click on (Cross-System Company Codes)

Choose (New Entities) and write the global CoCde for your company in this example it will be GLCC01

Save and go back, then double-click on (Assign Cross-System Company Code to Chart of Accounts)

Add the Target ChtAccts next to the Global CoCde.

Save and go back, then double-click on (Assign Company Code to Cross-System Company Code)

In this step make sure that you write the Global CoCde that you identified earlier in the raw that contains your Company Name

Save. 

Step (2)

This step is usually carried out by the functional consultant

Tcode: sale> Idoc Interface / Application Link Enabling (ALE) >   Modelling and Implementing Business Process >   Global Organizational Units >   Cross-System Business Areas

Double-click on (Cross-system business area)

Through (New Entries), add the X-syst.business area and the Description, they can be added in bulk by pasting the values directly in the table

Save and go back, then double-click on (Assign Business Area to Cross-System Business Area)

Add X-SysBusAr for the Business area that you added before

Save.

Step (3)

Tcode: sale > Idoc Interface / Application Link Enabling (ALE) > Basic Settings > Logical Systems > Define Logical System

OR Directly

Tcod: BD54

Then, choose (New Entries)

In the New Entries screen make sure that the Log. System is exactly like the one in S/4HANA, in this case, it will be QI1CLNT600

Step (4)

Tcode: sale > Modelling and Implementing Business Processes > Maintain Distribution Model and Distribute Views

OR Directly

Tcode: BD64

Switch to edit view using (the pain and glasses) symbol.

Select the model view (HR < -- > FI Scenario), then choose (Add BAPI)

We will do the following step 8 times, where:

• Model View: HRFICOUPLI


• Sender: ECP system, in this example: X01CLNT100


• Receiver: S/4HANA system, in this example: QI1CLNT600

Object name	Method
AcctngEmplyeeExpnses	Check
AcctngEmplyeeExpnses	Post
AcctngEmplyeeRcvbles	Check
AcctngEmplyeeRcvbles	Post
AcctngEmplyeePaybles	Check
AcctngEmplyeePaybles	Post
AcctngServices	PreCheckPayrollAccountAssign
PayrollAccDocument	Display_Acc

Then, press (Add BAPI) but this time the entries will be as follows:

• Model View: HRFICOUPLI


• Sender: S/4HANA system, in this example: QI1CLNT600


• Receiver: ECP system, in this example: X01CLNT100


• Object Name: PayrollAccDocument


• Method: Display_Acc

Save

Step (5)

From the menu choose (Environment) and then (Generate Partner Profile)

In the Generate Partner Profile, fill the following:

• Model View: HRFICOUPLI


• Partner System: S/4HANA logical system, in this example: QI1CLNT600

Execute

Step (6)

Tcode: SM59

In the Technical Setting tab, fill:

• RFC Destination: same as the S/4HANA logical system, in this example: QI1CLNT600


• Connection Type: 3, APAB Connection


• Target Host: of the S/4HANA system


• Instance: of the S/4HANA system

The target host string depends on the data center, and it should be like the following:

Datacenter	RFC from SAP Payroll System to Customer ABAP Systems
DC55	/H/payroll55-osk.sapsf.eu/S/3299/H/<Customer SAProuter>/S/3299/H/<ABAP server to be connected>
DC56	/H/payroll56.sapsf.eu/S/3299/H/<Customer SAProuter>/S/3299/H/<ABAP server to be connected>
DC64	/H/payroll64-osk.sapsf.com/S/3299/H/<Customer SAProuter>/S/3299/H/<ABAP server to be connected>
DC66	/H/payroll66-osk.sapsf.com/S/3299/H/<Customer SAProuter>/S/3299/H/<ABAP server to be connected>
DC22	/H/payroll22-osk.sapsf.com/S/3299/H/<Customer SAProuter>/S/3299/H/<ABAP server to be connected>
DC23	/H/payroll23-osk.sapsf.com/S/3299/H/<Customer SAProuter>/S/3299/H/<ABAP server to be connected>

In the Logon & Security tab

Fill out the Logon Procedure:

• Language: EN


• Client: the client of your S/4HANA in this example 600


• User: this user should be a S/4HAN user that has the needed authorities, in this example: XYZ


• Password: the password of the S/4HANA user

Save, then press (Connection test) to verify that it is working

Step (7)

Tcode: WE21

Choose Transactional RFC then Create

You can choose to (Generate port name), or you can choose the name you want using (own port name), in this example the name: QI1CLNT600

Choose the RFC destination that we created in the previous step, and select (IDoc record types SAP Release 4.x)

Save

Step (8)

Tcode: WE20

Choose partner type LS and Create

Fill:

• The (Partner No.) as the name of the logical system of the S/4HANA in this example: QI1CLNT600


• The (Partn. Type): LS


• Ty.: US (User)


• Agent: the name of a user that has authority over the ECP system in this example ZYX


• Lang.: EN

Save

Then Create an outbound parameter by choosing under the outbound table

Fill:

• Message Type: ACC_EMPLOYEE_EXP


• Basic Type: ACC_EMPLOYEE_EXP01 OR ACC_EMPLOYEE_EXP02


• Receiver Port: use the receiver port that we created in the previous step in this example: QI1CLNT600

Select:

• Transfer IDoc Immed.


• Cancel Processing After Syntax Error

Then, create another outbound parameter by choosing  under the outbound table

Fill:

• Message Type: ACC_EMPLOYEE_REC


• Basic Type: ACC_EMPLOYEE_REC01 OR ACC_EMPLOYEE_REC02


• Receiver Port: use the receiver port that we created in the previous step in this example: QI1CLNT600

Select:

• Transfer IDoc Immed.


• Cancel Processing After Syntax Error

Then, create the last outbound parameter by choosing under the outbound table

Fill:

• Message Type: ACC_EMPLOYEE_PAY


• Basic Type: ACC_EMPLOYEE_PAY01 OR ACC_EMPLOYEE_PAY02


• Receiver Port: use the receiver port that we created in the previous step in this example: QI1CLNT600

Select:

• Transfer IDoc Immed.


• Cancel Processing After Syntax Error

Save

Then Create an inbound parameter by choosing under the inbound table

Fill:

• Message Type: COSMAS


• Process Code: COSM

Select:

• Cancel Processing After Syntax Error


• Trigger Immediately

Save

The Partner profile should look like this

Step (9)

Tcode: sale > IDOC Interface/ALE -> Communication -> Determine RFC destinations for Method calls

OR Directly

Tcode: BD97

Choose the logical system for S/4HANA, in this example: QI1CLNT600

Choose (Standard BAPI destination), and assign the RFC destination that you created in step (6)

Step (10)

Tcode: SE38

Fill Program: RBDAPP01

Execute

In the IDoc Selection screen, make the following entries:

• IDoc Status: 64


• Message Type: COSMAS


• Package Size: 100

Save

In the Variant Attribute screen, enter:

• Variant name: for example, COSMAS,


• Description field: provide a valid description, for example, IDoc Processing.

Save

Step (11)

Tcode: SM36

In the screen of Define Background Job, enter:

• Job Name: for example, CC_S4


• Job Class: A

choose Start Condition

In the Start Condition screen, choose (Immediate). Check the Periodic Job and choose Period Values

In the Period Values screen select (Hourly)

Save the period value and then save the start time

Then Choose (Step)

• ABAP Program Name, and enter the name as RBDAPP01


• Variant field, select the variant that you created, for example, COSMAS

Save

The ECP configuration is completed

Now the configuration is completed 😊