July 19, 2016 2 minute read

EC Payroll Point to Point Integration (PTP)

EC Payroll initially came with a middleware as explained earlier in the Blog Successfactors Employee Central Payroll or On premise Payroll

Now with 1605, Net New customers no longer need a middleware such as Boomi or HCI to integrate EC with Employee Central Payroll (ECPay)

As explained the architecture for a Typical EC Payroll before release 1605 was as below, Note for EC on Premise Payroll customers the below diagram is still valid.

After 1605 Release, No HCI or BOOMI Skills are required and it eases further in System set up and provisioning

Important Point :

Employee Central payroll employee master data replication service does not support the creation of the Organizational unit.

And the well known PA-PD integration is not allowed in Employee Central payroll in general (only a few older customers are allowed to use it which are still using PA_SE_IN and which make use of the corresponding org data replication enterprise service for on Premise customers). PA-PD integration in general is only allowed for the OnPremise customers.

In case of Employee Central payroll it is only supported to transfer the texts of jobs and positions from EC to ECP.

You can check further here

You could fill it with the BAdI HRSFEC_B_CE_CHANGE_IT0001 of enhancement point HRSFEC_CE_MASTER_DATA_REPL.

You would need to map your Employee Central Department/Division ID to one of the valid Organizational Unit IDs you have saved in Employee Central payroll database table T527X. In case that the text of your EC org unit does not exist in table T527X you would need to fill it manually by means of view V_T527X and transaction sm30.

The Architecture looks as below

As you can see there is no middleware wherein making the replication faster. Also, with this approach No need to keep track on applying latest Boomi integration pack to get new functionality etc. All other functionality like EC TimeSheet Integration is released on PTP only henceforth from 1605 release.

One more important thing to remember there is no Integration Add on PA SE IN to be installed for this functionality as point-to-point replication is based on software component EA-HRRXX.

These are the typical configuration needs to be done

Setup system connectivity
Setup replication configuration
Setup employee replication
Setup EC Time Off replication
Setup EC Timesheet replication

For existing Payroll Customers ie based on middleware replication :

Immediate migration is not mandatory
Future functionality such as new countries or EC Timesheet integration (1605) will only be available with P2P
Customers who want to make use of new functionality have to migrate to P2P
A set of tools is provided to automate migration and reduce errors and efforts

For the Migration Steps :

Please refer the SAP NOTE 2321421 – How to migrate from PA_SE_IN to EA-HR/PTP?

Refer the Customisation Steps here

SAP Customizing Implementation Guide > Personnel Management > Integration Settings for SuccessFactors Employee Central Payroll

P.S : For further details please see implementation guide on: http://help.sap.com/hr_ecpayroll

33 Comments

You must be Logged on to comment or reply to a post.

Former Member

July 19, 2016 at 6:15 pm

good update

Siddharth Rajora

Blog Post Author

July 20, 2016 at 12:47 am

Thanks Jwala

Manoj Sharma

February 15, 2018 at 11:03 am

Hi,

i am new to integration , however after reading your blog i feel like you might have answer to my query on SAP S/4 HANA 1709 integration with SF EC .

my client has not purchased any middle ware and looking for a integration between SAP S/4 HANA 1709 integration with SF EC i am looking for a answer to following question ;

1) do i need to to install any add-on in SAP HANA 1709 as prequiste for flat file integration with SAP SF

if yes then what are the add-ons details pls share?

2) Do i need a SFTP server for Flat file integration between SAP HANA 1709 & SF ?

3) What are the required configuration step in in SAP HANA for integration .. pls let me know if their is any online course avilable in leraning hub or kindly share link if any ?

4) Required configuration step in SF - in case any course is avilable on learning hub please share details or in case you have any document pls share ?

can you assist me with your guidelines ?

Regards,

Siddharth Rajora

Blog Post Author

February 28, 2018 at 3:20 pm

1) do i need to to install any add-on in SAP HANA 1709 as prequiste for flat file integration with SAP SF

if yes then what are the add-ons details pls share?

PA SE IN is the add on

2) Do i need a SFTP server for Flat file integration between SAP HANA 1709 & SF ?

its recommended to use HCI as we provide standard integration content and support for it

3) What are the required configuration step in in SAP HANA for integration .. pls let me know if their is any online course avilable in leraning hub or kindly share link if any ?

help.sap.com > Employee central integration https://help.sap.com/viewer/p/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL_INTEGRATION_TO_SAP_BUSINESS_SUITE

4) Required configuration step in SF – in case any course is avilable on learning hub please share details or in case you have any document pls share ?

You can search for Employee central integration

Manoj Sharma

March 6, 2018 at 8:35 am

Thanks for clearing my doubts.

Venkata Prathapa Reddy

July 4, 2022 at 12:12 pm

Hello Siddharth,

I have few questions could you please clarify me.

Is HCI/CPI nothing but BIB? If both are different can you please elaborate a little bit.
Without buying ECP license will the node "Integration Settings for SuccessFactors Employee Central Payroll" available in SPRO? If this is available can we use it for replication for SF EC, Time-off and Time-sheet to SAP HCM?
Can we replicate SF time-off and time-sheet using BIB?

Thank you,

Akhil

Siddharth Rajora

Blog Post Author

July 4, 2022 at 2:11 pm

Is HCI/CPI nothing but BIB? If both are different can you please elaborate a little bit.

HCI is separate and its middleware, BIB Is in ECC or S4HANA system to do the mapping

Without buying ECP license will the node "Integration Settings for SuccessFactors Employee Central Payroll" available in SPRO? If this is available can we use it for replication for SF EC, Time-off and Time-sheet to SAP HCM?

ECP and BIB are different.

yes it can be used once you have license to integrate ie EC

Can we replicate SF time-off and time-sheet using BIB?

BIB is for master data and org

use this below

https://help.sap.com/docs/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL_INTEGRATION_TO_SAP_BUSINESS_SUITE/575b902ecbbc4a9e9f61085a22a6ba02/6356389965e14fca8df1fc92536acb87.html

Venkata Prathapa Reddy

July 5, 2022 at 5:22 am

Hello Siddharth,

Thank you for the clarifications.

But still something to understand, I am clear the without ECP license we can't use PTP Integration.

My Concern is I'm unaware my client has ECP license or not, but I could see spro path "Integration Settings for SuccessFactors Employee Central Payroll" but I could not see spro path "Payroll control center".

That means is my client has ECP license? If not can I just use "Integration Settings for SuccessFactors Employee Central Payroll" for integration and run payroll on HCM directly as I do not have Payroll control center in spro?

Thank you,

Siddharth Rajora

Blog Post Author

July 5, 2022 at 2:12 pm

yes you can see the ECP SPRO path. But you need to have ECP system to make it work

You need to look at Employee central integration with add on PA SE IN, if you are using On premise system.

Payroll Control Center switch should be activated in SFW5

Activating Configuration Workbench for Payroll Control Center | SAP Help Portal

Former Member

July 26, 2016 at 6:59 am

Good Info...Thanks Siddharth...

Siddharth Rajora

Blog Post Author

July 26, 2016 at 2:47 pm

Thanks Sathya

Former Member

July 26, 2016 at 7:14 pm

Thanks for the update on P2P.

Utkarsh M parikh

July 27, 2016 at 8:22 am

Hi Sidhharth,

Few questions on data replication from EC to EC Payroll:

New starter, replicates to payroll. Payroll not yet run for first period. Hire date changed on EC. Again replication is ran, Will this change the hiring action in ECPY?
New starter, replicates to payroll. Payroll run for first period. Hire date changed on EC. Again replication is ran, Will this change the hiring action in ECPY?
Leaver, replicates to payroll. Payroll not yet run for the pay period. Leaving date changed on EC. Again replication is ran, Will this change the leaving action in ECPY?
Leaver, replicates to payroll. Payroll run for the pay period. Leaving date changed on EC. Again replication is ran, Will this change the leaving action in ECPY?

Regards,

Utkarsh

Siddharth Rajora

Blog Post Author

July 27, 2016 at 3:54 pm

yes it would be in all cases, Please note EC Payroll or SAP HCM system is in sync or needs to be in sync with Master ie Employee Central which is the system for doing all master data changes and should be replication back to HCM system for running payroll with upto date information

Utkarsh M parikh

July 28, 2016 at 5:56 am

Thank you Siddharth.

Siddharth Rajora

Blog Post Author

August 11, 2016 at 7:05 pm

Its same as before, Please refer here

SRTUTIL or SLG1, API audit log Or Data replication Monitor

Successfactors Employee Central Payroll or On premise Payroll

https://websmp104.sap-ag.de/~sapidb/012002523100007691112016E

Former Member

January 10, 2017 at 11:26 pm

Hi Sidharth,

I was wondering during the start of the project, do we need conversions to replicate data related to additional/recurring payment (infotype 14/15), Savings plan(167) and Benefits info(171) from EC to ECP or it will be handled by the replication configuration.

Was looking from the historical data perspective.

Regards,
Manu

Siddharth Rajora

Blog Post Author

January 13, 2017 at 10:58 pm

Manu
Typically after Data Migration ie current data only to SFSF, all historical data is delimited in HCM.
We try to transfer which data is necessary in SFSF. ie important history items and then these are replicated to HCM. SFSF is is your Master system and any changes should be there

Let me know if you have additional queries on this

Manu Bhutani

April 18, 2017 at 6:12 pm

Hi Siddharth,

I was going through the PTP handbook and it talks about the FTSD(Full trnasmission start date). I understand that this is configured in the middleware like HCI but how to go about it for PTP.

Regards,

Siddharth Rajora

Blog Post Author

April 19, 2017 at 4:12 pm

You set in table T77SFEC_PTP_CONF

also, you decide also when you split or delimit the infotypes during data migration and that is being used also your FTSD.

Manu Bhutani

April 22, 2017 at 7:05 am

Thx for the response Siddharth. We have just started with the implementation.

Is the logic of FTSD is same for EC->ERP and EC->ECP i.e. records valid on or after FTSD are replicated?
I understand that no changes should be made in ED where effective date is before FTSD, in case it is done(with end date 12/31/9999, shouldn't this be sent to ERP?
Is it necessary to split records in ERP on go-live date, can't we by-pass this so that only changes move from the first run
If we can't by-pass then won't the first run overwrite the record in ERP with same details. for ex go-live date is 01/01/2018, after executing conversion action top of record in erp will be 01/01/2018 - 12/31/9999, same will be the case in EC. if we go by definition of ftsd top of stack record from EC will be replicated which is not required.
Does the middleware start sending changes automatically after first run i.e. last_change_timestamp will be populated in middleware or we need to configure something.

Siddharth Rajora

Blog Post Author

April 25, 2017 at 9:00 pm

Thx for the response Siddharth. We have just started with the implementation.

Is the logic of FTSD is same for EC->ERP and EC->ECP i.e. records valid on or after FTSD are replicated?

Yes orrect

I understand that no changes should be made in ED where effective date is before FTSD, in case it is done(with end date 12/31/9999, shouldn’t this be sent to ERP?

data wont be sent if the date is prior to FTSD, ie start date

Is it necessary to split records in ERP on go-live date, can’t we by-pass this so that only changes move from the first run

It depends upon the requirement, if you take all data from ERP to EC, if only subset of data is sent then splitting is required then top of stack etc, its there is guide

If we can’t by-pass then won’t the first run overwrite the record in ERP with same details. for ex go-live date is 01/01/2018, after executing conversion action top of record in erp will be 01/01/2018 – 12/31/9999, same will be the case in EC. if we go by definition of ftsd top of stack record from EC will be replicated which is not required.

no it wont overwrite as we do different action reason and we delimit the records in SAP and start a new hiring action and date from data replicated from EC to erp

Does the middleware start sending changes automatically after first run i.e. last_change_timestamp will be populated in middleware or we need to configure something. Yes that's correct

Manu Bhutani

April 26, 2017 at 3:47 pm

Thx Siddharth,

my 4th ques was related to replication from EC->ERP (on premise which will not be system of record from go-live but integrations will continue) . Wouldn't it overwrite conversion(split) record in ERP going by the definition of ftsd (record valid on FTSD and begin date >= FTSD), plz have a look on the dates i gave....or is there something in middleware by which we can start sending delta from the very first run

I believe you answered considering EC->ECP replication where FTSD will be one day before the go-live date to bring the hiring record from EC to ECP (Not bringing history in EC but loading hire record on go-live date - 1 and latest record on go-live date)

Siddharth Rajora

Blog Post Author

April 30, 2017 at 8:17 am

even in On premise its the same approach it wont overwrite as you are splitting the data and only transferring current record from the Go live date

Siddharth Rajora

Blog Post Author

May 2, 2017 at 10:18 am

that data wont be in HCM it should be a new record in EC with Go live date! and then transfer it using different event reason to avoid overwrite, this is how it is done. In the guide it explains like this and step by step, i do understand your question,

Split of the records of all PA infotypes (employee master data) in the SAP ERP HCM system that are within the migration scope is required.
All relevant infotype records need to be split in a way that the old record ends on the day before the cutoff date and a new record starts on the cutoff date.

Bhaskar Tripathi

May 24, 2017 at 10:00 pm

Hi Siddharth,

Good to see your post.

My question is more generic related to integration. The impression that is given to me by some "integration" folks is that PTP integrations are not preferred and we should use middleware. Core integration is not my expert area so I don't argue. But whats your thought on this? I can understand that in EC payroll case it makes sense to have PTP as SAP wants to make the new HR solution seamless, but what about in general?

Cheers!

Bhaskar

Siddharth Rajora

Blog Post Author

May 29, 2017 at 6:24 pm

if you are using ECP, We only offer P2P, there is no other way ie no integration for master data it should be p2p

But if you have ERP or own HR On premise system you have to use integration based on HCI (recommended) , we have to use integration here and cant use P2P, P2P is only for ECP

Former Member

June 15, 2017 at 5:07 pm

Hi Siddharth,

In table T77SFEC_CVMAPC we can do one to one mapping of event reasons but standard action reason code is same for a couple of actions, ex action reason 01 is there for HIRE as well as for Org reassignment in ECP. How can we map event reasons for this ex.

Do we need to create custom action/action and action reasons reasons in ECP so that one to one mapping can be done or SAP takes care by taking into consideration how events are mapped.

Regards,

Manu

Siddharth Rajora

Blog Post Author

June 21, 2017 at 1:49 am

In EC we deliver standard ones and yes in ECC HCM you can interpret them as differently

also

Per default following events are mapped to a personnel action massn
as defined by table T77SFEC_CVMAPS:
event     massn
26        10
3         10
EGA       10
GA        01
H         01
R         12

Here the main events are
26 = termination
H = hire
R = rehire
GA = start of global assignment
EGA = end of global assignment

.
You can overrule the default settings as described in the implementation guide.

Per default delivery each employee central event reason is mapped to a space value for the
personnel action reason massg.

Events or event reasons which are not mapped are filtered out.

Baskar Deivasigamani

September 18, 2020 at 1:40 am

P2P integration is possible for on-premise payroll?. The post from EPI USE states only it is possible for ECP. Thanks

Siddharth Rajora

Blog Post Author

September 25, 2020 at 6:52 pm

P2P is only for EC and ECP

BIB is used for EC to ERP or S4HANA ie with middleware/

Shilpa Wadatkar

October 7, 2020 at 11:04 am

Hi Siddharth,

If SF as standalone system and in that EC payroll to be added up?

Client don't have SAP HCM on premise and I only to go for SF EC payroll how can we do that?

Regards

Puja

Siddharth Rajora

Blog Post Author

October 9, 2020 at 7:25 pm

yes it can be, you dont ECC, you can directly link ECP

there ll be proviosioning of ECP by SAP PY OPS TEAM

you can start here

https://help.sap.com/viewer/product/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL_PAYROLL/2011/en-US?task=discover_task

EC Payroll Point to Point Integration (PTP)

Assigned Tags