Integration Add-on 3.0 for SAP HCM and SuccessFactors: Service Package 2

[lukemarson]

The second service package for the third packaged integration for integrating SAP HCM and SuccessFactors – Integration Add-on for SAP ERP Human Capital Management and SuccessFactors Business Execution 3.0 Service Package 2.0 – was released on SAP Service Marketplace on February 2^nd 2015. The packaged integration introduced onboarding process integration between SuccessFactors Onboarding and SAP ERP HCM, the second and final part of the variable pay integration between SuccessFactors Variable Pay and SAP ERP HCM (the first part was released in Add-on 3.0 SP1), and introduced SAP PI content for the qualifications integration between SuccessFactors HCM suite/SuccessFactors Learning and SAP ERP HCM that was released in Add-on 3.0 and was previously only available on SAP HANA Cloud Integration (HCI). A brief overview of all of the packages and the strategy for integration can be found in my blog SAP HCM and SuccessFactors Integration Packages: a brief overview.

The Package

The packaged integration enables:

• New Hire data to be transferred from SuccessFactors Onboarding to SAP ERP HCM and for a Hiring Action to be launched (in a similar way to the Recruiting packaged integration)
• The full Variable Pay process to be completed (employee history and changes to employee history to be transferred from SAP ERP HCM to SuccessFactors Variable Pay and variable pay process results transferred back to SAP ERP HCM so they can be processed in Payroll)
• Qualification process integration to be performed using SAP PI as the middleware

The figures below demonstrate the Onboarding and Variable Pay process and data flows for this scenario. Refer to the blog on Add-on 3.0 for the qualification integration process and data flows.

I will now cover the package contents, configuration, and use of each process separately. First off, I’ll look at Onboarding. Onboarding is fairly similar in its setup and operation to the Recruiting process integration introduced in add-on 2.0.

SuccessFactors Onboarding integration

The add-on includes a number of new features and functionality for Onboarding:

• Report RH_SFI_IMPORT_ONBOARDING_DDIC and transaction HRSFI_SYNCH_ONB_META to import a data dictionary XML from SuccessFactors Onboarding
• Report RH_SFI_IMPORT_ONBOARDING_DATA and transaction HRSFI_ONB_DATA_IMP to extract new hire data from SuccessFactors Onboarding
• Report RH_SFI_ONBOARDING_PROCESS and transaction HRSFI_ONB_HIRE to process new hire data and launch a Hiring action
• BAdI implementation for deletion of personnel numbers from the Variable Pay Log Tables (implementation of HRSFI_DEL_ONB_STGING of BAdI HRPAYXX_DELETE_PERNR) for use with report RPUDELPP
• Middleware content for SAP PI
• Authorization role SAP_HR_SFI_ONBOARDING
• New IMG entries under the Integration Scenario for Onboarding Data node in the Integration Add-On for SAP ERP HCM and SuccessFactors BizX node

The screenshot below shows the selection screen for transaction HRSFI_ONB_DATA_IMP (report RH_SFI_IMPORT_ONBOARDING_DATA).

The screenshot below shows the selection screen for transaction HRSFI_ONB_HIRE (report RH_SFI_ONBOARDING_PROCESS).

Configuration in SAP is performed within the IMG under Personnel Management > Integration Add-On for SAP ERP HCM and SuccessFactors BizX > Integration Scenario For Onboarding Data. The nodes can be seen in the screenshot below.

Prior to the first step, a data dictionary must be created in SuccessFactors Onboarding and exported as an XML file. This XML file is then uploaded in the first step.

The following customizing activities need to be performed:

1. Import metadata from SuccessFactors Onboarding in customizing activity Import Metadata from SuccessFactors Onboarding
2. Maintain the SuccessFactors system details (Company ID, username, and password) in customizing activity Store Credentials for Transferring Onboarding to Secure Storage
3. Map the Onboarding template ID to a fieldset in customizing activity Assign SuccessFactors HCM Suite Objects to Field Sets *
4. Map SAP ERP HCM fields to SuccessFactors Onboarding fields in customizing activity Map SuccessFactors HCM Suite Fields and SAP ERP HCM Fields *
5. Configure BAdI for mapping SuccessFactors Onboarding fields to SAP ERP in customizing activity BAdI: Mapping of SuccessFactors Fields to SAP ERP Infotype Fields
6. Configure BAdI for field mapping derivation in customizing activity BAdI: Change of Mapping Result
7. Configure BAdI to determine additional data to be retrieved from SuccessFactors Onboarding in customizing activity BAdI: Determination of Further Data for Onboarding from SuccessFactors
8. Configure BAdI to determine personnel number and SuccessFactors User ID in customizing activity BAdI: Determination of SAP ERP Personnel Number and SuccessFactors User ID

*Note that this activity is not transportable

Once this configuration has been completed then the add-on is ready to use. To use the add-on:

1. Run and/or schedule report RH_SFI_IMPORT_ONBOARDING_DATA (also accessible via transaction HRSFI_ONB_DATA_IMP) to import new hire data (this data is stored in Log Table HRSFI_D_ONB_IMP)
2. Once the onboarding data has been imported from SuccessFactors Onboarding then run transaction HRSFI_ONB_HIRE (report RH_SFI_ONBOARDING_PROCESS) to view imported employees and launch a Hiring Action for employees

Employees need not to be sent over to SuccessFactors as this is handled by the standard employee data packaged integration. Report RPUDELPP can be run to delete employee data from the Onboarding Log Tables.

SuccessFactors Variable Pay integration

The add-on includes a number of new features and functionality for Variable Pay:

• Report RH_SFI_IMPORT_VARPY_DATA and transaction HRSFI_VP_IMP_DATA to import variable pay process data for employees from SuccessFactors Variable Pay
• Report RH_SFI_ACTIVATE_VARPY_DATA and transaction HRSFI_VP_ACT_DATA to activate imported variable pay process data for employees
• BAdI implementation for activation of Variable Pay data (HRSFI_B_VARPY_DATA_ACTIVATION)
• BAdI implementation for customizing field mapping derivation (HRSFI_B_VARPY_ACTIVATION_CUST)
• BAdI implementation for deletion of personnel numbers from the Variable Pay Log Tables (implementation of HRSFI_DEL_VARPAY_LOG of BAdI HRPAYXX_DELETE_PERNR) for use with report RPUDELPP
• Middleware content for SAP PI
• Additional authorizations for authorization role SAP_HR_SFI_VARIABLE_PAY
• Web Dynpro application HRSFI_MONITORING_VARPAY
• New IMG entries under the Integration Scenario for Variable Pay Data node in the Integration Add-On for SAP ERP HCM and SuccessFactors BizX node

The screenshot below shows the selection screen for transaction HRSFI_VP_IMP_DATA (report RH_SFI_IMPORT_VARPY_DATA).

The screenshot below shows the selection screen for transaction HRSFI_VP_ACT_DATA (report RH_SFI_ACTIVATE_VARPY_DATA).

Configuration in SAP is performed within the IMG under Personnel Management > Integration Add-On for SAP ERP HCM and SuccessFactors BizX > Integration Scenario For Variable Pay Data. The nodes can be seen in the screenshot below.

The following customizing activities need to be performed:

1. Configure details of the variable pay program and ad-hoc report template ID in customizing activity Maintain Variable Pay Program Information
2. Import metadata from SuccessFactors Variable Pay in customizing activity Import Metadata from SuccessFactors HCM Suite
3. Map the Variable Pay template ID to a fieldset in customizing activity Assign SuccessFactors HCM Suite Objects to Field Sets – this can be done multiple times if there are more than one Variable Pay template ID and is done against an activation type *
4. Map SAP ERP HCM fields to SuccessFactors Variable Pay fields in customizing activity Map SuccessFactors HCM Suite Fields and SAP ERP HCM Fields *
5. Configure BAdI for activating Variable Pay data in customizing activity BAdI: Activation of Variable Pay Data Imported from SuccessFactors
6. Configure BAdI for field mapping derivation in customizing activity BAdI: Customizing Field Mapping
7. Map SuccessFactors Variable Pay fields to SAP ERP HCM fields (for import) in customizing activity Map Fields for Importing Variable Pay Data

*Note that this activity is not transportable

Once this configuration has been completed then the add-on is ready to use. To use the add-on:

1. Run or schedule report RH_SFI_SYNCH_VAR_PAY_DATA (also accessible via transaction HRSFI_VARPAY_DATA) to export employee history data (this data is stored in Log Table HRSFI_D_VARPY_EX)
2. Once the variable pay process has been completed in SuccessFactors Variable Pay then transaction HRSFI_VP_IMP_DATA (report RH_SFI_IMPORT_VARPY_DATA) should be run to import the variable pay process data from SuccessFactors Variable Pay (this data is stored in Log Table HRSFI_D_VARPY_IM)
3. After import, run transaction HRSFI_VP_ACT_DATA (report RH_SFI_ACTIVATE_VARPY_DATA) to activate variable pay data into the payroll infotypes (infotype 0015)

Transaction HRSFI_VP_CLN_IMP (report RH_SFI_CLEANUP_VAR_IMP) or RPUDELPP can be run to delete employee data from the Variable Pay Log Tables.

Prerequisites and Notes

There are several prerequisites and notes regarding the operation of the integration:

• SAP PI version 7.11 SP12 or above is required for variable pay
• SAP PI version 7.31 SP14 or above is required for qualifications and onboarding integration
• SAP PI connectivity add-on 1.0 SP01 or above is also required
• SFIHCM01 SP9 and SFIHCM02 SP4 are required
• SAP Gateway 2.0 SP07 is optional

Further Information

Further information can be found in the Administration Guide and in the Application help provided at http://help.sap.com/erp_sfi_addon30/. Partners can access Rapid Knowledge Transfer (RKT) documents via the SAP Jam group SAP SuccessFactors Integration for Partners.

Summary

The latest support package adds the first half of process integration to the packaged integrations for SAP ERP HCM customers who want to perform onboarding activities in SuccessFactors. Although it is only one half, it does provide the majority of the functionality required. This packaged also completes the variable pay process and also allows customers to finally leverage SAP PI for qualifications integration.

[Muniyappan]

Dear Luke,

Do we need to use SFSF adapter for on boarding scenarios along with soap adapter? or it can be managed with soap adapter itself.

as of now i am using only soap adapter with axis protocol for Employee,recruiting,compensation scenarios.

i have imported software component SFIHCM03 600. one of the interface SFSFOnboardingCandidateInfo_Out is having sfsf adapter on the receiver side. does this mean there is no soap service for this interface?

Regards,

Muni

[lukemarson]

Hi Muni,

Onboarding data comes through a SOAP API and an OData API, so you need both.

All the best,

Luke

[Muniyappan]

Thank you Luke.

i have installed SFSF adapter and it is able to get the Candidate info by calling OData API.

Configurations are yet to be done in ECC and SF for on boarding module.

I should be coming back to you with more questions.

Regards,

Muni

[Former Member]

Dear Luke,

we have some doubts about this integration, the scenario is that  we have already implemented the integration of RCM SFSF and SAP and now we want to implement the SFSF Onboarding solution. Now we are using the reports:

RH_SFI_IMPORT_RECRUITING_DATA to export the Candidate information from SFSF to SAP and the transaction HRSFI_RCT_HIRE to hire the employee.

And the report RH_SFI_SYNCHRONIZE_EMPL_DATA to export the information from SAP to SFSF.

The question is if it's mandatory to use Onboarding integration if you implement Onboarding Solution or we can continue using this RCM integration?

Regards,

Jose

[lukemarson]

Hi Jose,

Yes you will need to use it, although you might no longer need recruiting integration to send candidate info from RCM to SAP ERP HCM, since you would might send data from RCM to Onboarding and then Onboarding to SAP ERP HCM.

Best regards,

Luke

[Former Member]

Hi Luke,

thanks for your prompt response. We have only some emloyees who go through onboarding process, the rest of the employees are not send to onboarding. In this case, we should have two different integrations with SAP? One with Onboarding-SAP and the other one with RCM-SAP?

Regards

Jose

[prasad_ulagappan2]

Hi Luke,

We have successfully integrated our SAP HCM System with Sucessfactor. We dont see any issues over there.

We are also trying to build some custom interfaces like education details, previous employment details, etc. For this we need to pass SFSF User id to SF for each interface. How to get SFSF user id in HCM while we pass our data in HCM to Sucessfactor? When I saw the standard interfaces, it is returning SFSF User id parameter as its response. But we are not sure where exactly this is stored in our HCM system. Any idea how to get SFSF User id in our HCM system.

Regards

Prasad U

[lukemarson]

Hi Prasad,

Usually the User Id is sent from SAP. Typically it would be the PERNR. Check your configuration in the IMG as it will be defined there.

All the best,

Luke

[former_member216586]

Hi Luke,

We implemented Employee Import and now we are doing Onboarding using SAP ECC->PO->SF, the program  RH_SFI_IMPORT_ONBOARDING_DATA seems to be working fine and the end I can read the log saying 83 employees updated succesfully

but when I go to the program RH_SFI_ONBOARDING_PROCESS  the screen comes back empty and there is nothing on it, so what can we do? Seems that I missing a step.

Thanks,

Miguel Padilla

[Balaji_Ponnam]

Thanks for the info,

[lukemarson]

Hi Miguel,

I'm sorry, but I've not come across this error. Did you raise a ticket with SAP Support through the SAP ONE Support Launchpad?

Best regards,

Luke

[Former Member]

Hi Luke,

Thanks for the great Blog !

From an Integration add-on perspective if we are implementing RCM Module and also Onboarding . Can you help in understand the difference between below 3 reports .

1.HRSFI_ONB_DATA_IMP - Import Onboarding Data

2.HRSFI_ONB_HIRE-Process Onboarding Data

3.HRSFI_ONB_TRIGGER - Process Onboarding Data

Also when should we use below Operation mapping scenario's

a.SFSFOnboardingCandidateInfo_Out_to_SFSFOnboardingCandidateInfo_In

I am assuming this should be used to import applicant details from  RCM to SAP HCM .

b.SFSFOnboardingGetNewHireRecord_Out_to_SFSFOnboardingGetNewHireRecord_In .

The same way I assume when we have RCM->Onboarding integration we can ignore the "a" and directly use "b" to get the ready for Hired records from Onboarding to SAP HCM .

Would you be able confirm on this please .

Thank You.

Regards,

Kishore.S

 

 

 

[lukemarson]

For the three reports:

• HRSFI_ONB_DATA_IMP is used to import the data from SAP SuccessFactors Onboarding.


• HRSFI_ONB_HIRE is used to hire candidates in SAP ERP HCM that were imported from SAP SuccessFactors Onboarding.


• HRSFI_ONB_TRIGGER is used to trigger onboarding in SAP SuccessFactors Onboarding for an employee already hired in the SAP ERP HCM system.

The web services are used by these reports for communication between the systems.

[Former Member]

Hi Luke ,

Thank you for the response and helped a lot . Will let you know for any questions .

 

Regards,

Kishore.S

[ec1]

Hi Miguel,

 

I know this is an old thread but I just want to share with anyone who come to this page because of this issue.

In my scenario, this can be fixed by implementing BAdI HRSFI_B_AUTHORITY_CHECK and change implementation in method CHECK_SUPER_USER to allow current user to view the data.

 

Regards,

Stevanic

[dyasser]

Hi Luke,

How do you know that SAP Gateway 2.0 SP07 is an optional component? 

Looking at https://help.sap.com/viewer/7db8496809b3485790e6cbde6330ba18/3.0%20SP06/en-US/4dfa56f95b4f487098dc4f... makes my think it is mandatory.

Dmitry

[Former Member]

Hi,

I am new in here. And I am following this document. How to do mapping for SF ONB with SAP HCM by using a simple table to map the fields? I want to use simple mapping not complex mapping(BADI Implementation).

Please tell me the step by step process for this.

Thanks
Monalisa

[former_member551450]

Hi Luke,

i'll be working soon on this kind of integration and I'm wondering if you can share the details about the right Add-on version to be installed on the OnPremise system taking into account that the SAP ERP release will be migrated soon to the latest Enhancement Package 8.

Thanks in advance.

BR, Luca

[former_member216586]

Hi Stevanic,

 

I raised a ticket with SAP and they told how to fixed. You are right there are some BADI's that I have to implemented including the BAdI HRSFI_B_AUTHORITY_CHECK  but in my case I change the rules for the Personnel area, if you go to the next method the Personnel Area is mandatory so the client asked us to removed that from the program so I comment out that check. But thanks for your answer.

 

Miguel Padilla

 

[lukemarson]

Hi Luca,

Always use the latest version and latest support package.

Best regards,

Luke

[lukemarson]

Hi Monalisa,

You only have the options available as outlined in the blog.

Best regards,

Luke

[lukemarson]

SAP Gateway is required for OData communication.

[dyasser]

In fact this is not correct. SAP Gateway is only required when qualification data integration is used. SAP Gateway enables you to expose OData APIs that import and export qualification data from SAP ECC HCM.

For any other integrations, such as employee data, recruiting data, onboarding data, SAP Gateway is not required.

Dmitry

[lukemarson]

So which part of "SAP Gateway is required for OData communication" is incorrect based on your comment that "SAP Gateway enables you to expose OData APIs"? You said yourself that qualifications integration needs OData...

[Shanker17]

Hi Luke,

Thanks so much for this blog,

We have onboarding 1.0 integration with SAP HCM via SAP PI/PO,

I am following the standard implementation guide and Onboarding and Offboarding API guides.

We have standard configurations in place, but still, we could not make the connections between Successfactors with SAP PI/PO. We get a page not found (404) error while we used the url:https:onboarding12preview.sapsf.eu/Services/HRDataServiceEx.asmx

with service login credentials as configured in provisioning.

provisioning config for KMS web services

Is there any step by step guide with samples that we can follow? Appreciate your input

[lukemarson]

Hi Shanker,

Unfortunately there is no guide for this. However, the configuration looks ok. You might want to raise an SAP Support ticket if you haven't resolved it yet.

Good luck!

Luke