Technical Articles
Configuring the SAP SuccessFactors Employee Master Data and Organizational Assignments from Employee Central to SAP ERP HCM
Hello SAP community,
We would like to share one working sample of the SAP SuccessFactors Employee Central connecting with the SAP HCM ERP using the SAP Cloud Platform Integration (CPI) + SAP Cloud Connector (SCC).
The ERP used was one S/4HANA OnPremise (running PA_SE_IN SP 26 and EA_HR 608 SP 65).
Objective:
Help our customers and partners completing the configuration in your local environments/projects.
The handbook used during this set up is:
- Replicating Employee Master Data and Organizational Assignments from Employee Central to SAP ERP HCM – (Q4 2019 – 2020-02-04)
- the handbook link includes the “/latest” in the URL, so in future, this handbook might have some different procedures or minor changes not documented in this blog post.
All the images and data used here was taken from SuccessFactors SalesDemo instance, local CPI tenant, local ERP OnPremise installation, so we are using dummy data.
Let’s start with one picture of the landscape.
We are assuming that you already have the PA_SE_IN SP installed in your ERP. This blog post will not cover all these steps, for more info you can refer the implementation guide mentioned earlier.
1. Download the CPI package named SAP SuccessFactors Employee Central to ERP Employee and Organizational Data from the Discover menu.
The configuration will start in the artifact SAP SuccessFactors Employee Central to ERP Employee Data and Organizational Assignment
Actions > Configure:
In the Sender tab, you can maintain the default configuration with the address:
/EC_to_ERP_Master_Data_And_Org_Query
This address will be used later in your SOAMANAGER consumer proxy configuration.
In the Receiver tab, change in the dropdown for Employee_Central.
The Address field should be selected according your SF instance datacenter, you can find all the URLs here 2215682 – SAP Successfactors API URLs for different Data Centers.
The Credential Name field you can type any text, but this needs to be created prior in the monitor view > Security Material, with your SF company ID, your username and your password (we call this one as API user).
The permissions that this API user will need in the SF side are described in the handbook chapter 3.3.1 Granting Permissions to API User.
If you are not familiar creating SAP SuccessFactors API username, you can follow also the instructions of this guided answers here.
In the Receiver tab, change in the dropdown for ERP_Response
The “ERP_Response“, “ERP_Notification…” and “ERP_Exceptions…” share the same config. You can apply the same values for all these.
In the Address, your URL will end with:
http://MASKED.com/sap/bc/srt/scs/sap/eemasterdataandorgassbndlreq?sap-client=200
(the value 200 in the end of the URL is your ERP client number)
The initial part of the URL at this point is still unknown, because we need to set up the SAP Cloud Connector first. We will go back here later. Just type some valid HTTP web address like the sample above.
The Credential Name needs to be created prior in the monitor view > Security Material, with your ERP admin technical username. The permissions that this user will need in the ERP side can be seen in the handbook chapters 3.3.2 and 3.3.3.
The Proxy Type here was used On-Premise because later we will configure the SAP Cloud Connector.
After doing similar configs according above, please Save/Deploy your artifact.
Now go to Monitor > Manage Integration Content > search for the SAP SuccessFactors Employee Central to ERP Employee Data and Organizational Assignment and find your endpoint URL ready to be consumed.
In my scenario, the URL is:
https://MASKED-iflmap.hcisbt.br1.hana.ondemand.com/cxf/EC_to_ERP_Master_Data_And_Org_Query
2. Now let’s start with SOAMANAGER config in your ERP.
Access the Web Service Configuration in browser.
Type in the Search bar the object name CO_ECPAOX_EE_MD_ORGAS_BNDL_QRY.
Create one Manual configuration for this consumer proxy.
In this sample we will use User ID / Password.
The User Name is your CPI S-USER. You can configure with Client Certificate too in your side if you prefer.
The Messaging tab must have these exact set up.
- RM Protocol = SAP RM
- Message ID Protocol = Suppress ID Transfer
- Data transfer scope = Enhanced Data Transfer
- Transfer protocol = Transfer via SOAP header
In the Transport Settings tab, we are going to use the URL that we got from the CPI > Overview > manage integration content (the same we have in the step 1).
Sample = https://MASKED-iflmap.hcisbt.br1.hana.ondemand.com/cxf/EC_to_ERP_Master_Data_And_Org_Query
The next tabs leave the default values (no changes are needed) and save 🙂
The last step (very important) is marking the Logical Port is Default = true. This is needed otherwise the messages can be in the Wait for Scheduler status in the SRTUTIL transaction later.
You now can run one Ping Web Service. The expected message is:
Web service ping successful for LP ‘REPLICATION_S4A’, proxy ‘CO_ECPAOX_EE_MD_ORGAS_BNDL_QRY’.
If your ping did not worked, don’t be sad. It can be due the certificates (step 3) or due another reason.
Sometimes the ping fails and this is the expected result. As per KBAs 1947516 and 1711486, it is always recommended to test Web Services in SE80, because pinging it in SOAMANAGER, testing it in a browser or using transaction SICF do not send POST method, which is mandatory for the SOAP service. This could result in empty pages or various HTTP error codes depending on the release. Another alternative to test the service is using one of the methods mentioned on the following Wiki: https://wiki.scn.sap.com/wiki/x/GAIhF
My suggestion if your ping failed = ignore this for now because later we will run the program to sync data and the real “testing” will be done.
3. We need to set up the certificates.
Why? Because we just configured HTTPS connection between 2 systems and certificates are part of the handshake process.
Type the CPI endpoint URL generated in the step 1 in your browser, sample below:
https://MASKED-iflmap.hcisbt.br1.hana.ondemand.com/cxf/EC_to_ERP_Master_Data_And_Org_Query
I am using Mac OS and the things are little different from Microsoft Windows in the browsers Google Chrome and Firefox.
After typing the URL in the browser, click in the lock icon and navigate until you see the certificates.
We need to download the TOP certificate (the one that expires in very future, like year 2038), not the middle/intermediate certificate and not the leaf certificate (expires usually in 1 year).
In Mac OS and Google Chrome, we just need to drag and drop the gold box to some folder in Finder.
This action generate the file like “DigiCert Global Root G2.cer”.
Now we need to install this file inside the ERP STRUST transaction.
Please install under the nodes:
- SSL client SSL Client (Standard)
- SSL client SSL Client (Anonymous)
Please be aware that importing the leaf and intermediate certificate is not required for CPI, you can import only the root certificate, and this will avoid to renewal the certs every year. That’s why I just recommended you to export 1 certificate (not the complete chain of 3 certificates of the URL).
After installing, Save, restart ICM (for older versions, this is done in the SMICM transaction). For recent versions, we do not need the ICM restart.
4. Let’s configure another web service / package.
Download from CPI discover menu the package = ERP to SAP SuccessFactors Employee Central Confirmation v2
After installed, Go to Design > Actions > Configure.
In the Sender tab, leave the default config with the Address /ERP_to_EC_EmployeeMasterDataReplicationConfirmation
In the Receiver tab,
Select the Address of the datacenter of your SF company ID (same URL as the step 1 of this blog post).
Select the Credential Name created in the step 1 of this blog post.
In the More tab (no changes needed).
After doing similar configs according above, please Save/Deploy your artifact.
Now go to Monitor > Manage Integration Content > search for the ERP to SAP SuccessFactors Employee Central Confirmation v2 and find your endpoint URL ready to be consumed.
In my scenario, the URL is:
https://MASKED-iflmap.hcisbt.br1.hana.ondemand.com/cxf/ERP_to_EC_EmployeeMasterDataReplicationConfirmation
5. Let’s configure again the SOAMANAGER in your ERP. This time for the confirmation webservice of the step 4.
Access the Web Service Configuration in browser.
Type in the Search bar the object name CO_PAOCF_EC_EMPLOYEE_MASTER_DA.
Create one Manual configuration for this consumer proxy.
In this sample we will use User ID / Password. The User Name is your CPI S-USER.
You can configure with Client Certificate too in your side if you prefer.
The Messaging tab must have these exact set up.
- RM Protocol = SAP RM
- Message ID Protocol = Suppress ID Transfer
- Data transfer scope = Enhanced Data Transfer
- Transfer protocol = Transfer via SOAP header
In the Transport Settings tab, we are going to use the URL that we got from the CPI > Overview > manage integration content (the same we have in the step 4).
Sample = https://MASKED-iflmap.hcisbt.br1.hana.ondemand.com:443/cxf/ERP_to_EC_EmployeeMasterDataReplicationConfirmation
The next tabs leave the default values (no changes are needed) and save 🙂
The last step is marking the Logical Port is Default = true.
You can run now run one Ping Web Service. The expected message is:
Web service ping successful for LP ‘CONFIRMATION_S4A’, proxy ‘CO_PAOCF_EC_EMPLOYEE_MASTER_DA’.
If your ping did not worked, find the reasons/same explanation done earlier in the step 2.
6. Let’s configure another webservice required for this process.
Access the SOAMANAGER and go to Simplified Web Service Configuration.
Type the Search Pattern = EEMASTERDATAANDORGASSBNDLREQ
Select the checkbox of User Name/Password (Basic) and Save.
Click in the Show Details button.
You will see the technical details according sample below:
|
|||||||||
|
The URL above is masked, but you will need to copy and paste your URL and type in browser.
After loading the WSDL page in browser, scroll down until the end.
and copy the last URL.
Sample:
http://brMASKED.sap/sap/bc/srt/scs/sap/eemasterdataandorgassbndlreq?sap-client=200
This URL is your ERP webservice inbound URL that needs to be configured in SCC, because probably this URL is exposed only in the local network.
The SCC will convert the internal URL to the cloud exposed URL to be configured in CPI.
I will explain more in the next step.
7. At this point, the ERP SOAMANAGER work is 100% done and the CPI work is 95% done.
Now, starting with the SAP Cloud Connector installation/configuration to allow your CPI connecting with your SAP HCM ERP On Premise.
Download and install the SCC in your local environment / local server.
Link to download the software.
Link of the SAP Cloud Connector (SCC) handbook/help.
Access your SAP Cloud Platform (SCP) account and find the Technical Name of your subaccount.
Configure your SCC to connect with your SAP Cloud Platform (SCP) subaccount (using the Technical Name).
In this sample, the Location ID used was brazil_2.
After that, create your Cloud To On-Premise configuration
In my sample, we are using:
- Virtual Host = s4a.erp.sap:8080 (HTTP port)
- Internal Host = brMASKED.sap:4430 (HTTPS port) > depends of your SMICM config in your ERP.
- URL Path = /sap/bc/srt/
- Access Policy = Path and all sub-paths (otherwise you may receive HTTP 403 error).
This configuration above allows your Virtual host that will be used in CPI to connect in your destination Internal Host (the webservice URL that we configured in the step 6).
We used the SCC in this landscape, because the URL of the step 6 is not exposed directly in the internet (most common scenario of SAP HCM ERP On Premise in customers).
When the setup above is ready, you will be able see the connected environments in the SAP Cloud Platform (SCP) > Connectivity > Cloud Connectors:
You can also run one test in the SAP Cloud Platform Integration (CPI) in the Overview > Test Connectivity > Cloud connector > type your Location ID and hit Send button:
If the connectivity is good, you will receive the message = Successfully reached Cloud Connector.
8. Completing the CPI work, I wrote one comment in red in the step 1 and we need to revisit that point of the configuration.
We need to go back to CPI configuration and type again the URL just generated in the Cloud connector in the Receiver tab.
Find below the config ready.
The field Address have now the SCC URL (Virtual host + combined with the path, webservice and client ID).
Your configuration of SCC, CPI and ERP webservices are 100% done.
After your SAP HCM functional team completes the SPRO customizing (path Personnel Management > Integration with SuccessFactors Employee Central > Business Integration Builder ) in the ERP side described in the handbook, you will be able to run the following program:
SE38 > ECPAO_EE_ORG_REPL_QUERY with your transformation template.
Then, you will be able to see the payloads and webservices working in CPI Overview > Monitor Message Processing:
- SAP SuccessFactors Employee Central to ERP Employee Data and Organizational Assignment
- ERP to SAP SuccessFactors Employee Central Confirmation v2
Similar logs will be visible in the Data Replication Monitor in the SuccessFactors side or the SRTUTIL (Message Monitor) and SLG1 transactions in ERP side.
The webservices involved are:
- getEmployeeMasterDataAndOrgAssignmentBundleReplicationQuery_Out (Consumer)
- EmployeeMasterDataAndOrgAssignmentBundleReplicationRequest_In (provider)
- EmployeeMasterDataReplicationConfirmation_Out (Consumer)
In the SLG1, you can filter by the Object text = ECPAO_IN
Just FYI, after one execution, the last successful run date/parameter is stored in the table ECPAO_QRY_ADM (fields QRY_LSTMOD_DT_TM or NXT_LSTMOD_DT_DM). These timestamps stored there will be used to control de Delta executions.
If you have errors like Wait for Scheduler under the SRTUTIL or SRT_MONI, please check this master KBA:
All set 🙂
Happy implementation.
Conclusion:
Using the instructions of this blog post, you will be able to set up the SAP Cloud Platform Integration (CPI) packages, the ERP webservices required in the SAP SuccessFactors Employee central Master Data and Organizational assignment to SAP ERP HCM with the latest version Builder integration Builder (BIB). This knowledge also can be used when your team apply system refresh in ERP side or instance refresh in SF side, because similar work needs to be done reconnecting all the systems. The SAP Cloud Connector (SCC) instructions part was summarized, but you can get the complete installation procedures in the handbook shared.
I hope this blog post can help your team doing the same implementation faster.
If you find this blog post helpful – please press like button 🙂
Best Regards from Brazil,
Soliman
Hi Soliman
Thanks for the detailed inputs, One question , this is only relevant from integration with on-premise SAP -HCM instance, right ?
I'm asking because for ECP (Employee Central Payroll) , we use PTP (Point to Point replication). I just wanted to make sure that these 2 are mutually exclusive.
Regards
Prem
Hello Premarajan Makkal Kesavan
Yes, this blog post is designed for on-premise SF vs SAP ERP HCM setup.
In the Employee central Payroll, there is no middleware because both systems are in SF Cloud and the config is simpler.
The PTP handbook config is described in the chapter 9.7 Set up the Connection to Employee Central.
Thanks,
Soliman
Very detailed Soliman, Excellent
Very detailed explanation.
One question : In the Package : SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: Employee and Organizational Data
there is another Iflow by name -->Replicate Organizational Objects from SAP SuccessFactors Employee Central to SAP ERP or SAP S4HANA. what is the purpose and when this is used?
Thanks
Mohan Babu GS
Hello Mohanbabu Gargisugur
We have several different packages in the CPI, the link for all implementation handbooks is:
https://help.sap.com/viewer/p/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL_INTEGRATION_TO_SAP_BUSINESS_SUITE
--------
Recently (2 days ago - April 11 2020), the packages were renamed in the CPI discover menu.
Inside the package that you mentioned:
SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: Employee and Organizational Data
We have two artifacts:
The 1st is the same explained in this blog posting.
The 2nd is regarding SF replication to SAP HCM organizational objects (OM module in ERP side). The configuration of this 2nd was not covered in this blog posting, but it is very similar.
Thanks 🙂
Hello Guilherme,
Thanks for your response. I need to configure the 2nd Iflow for organizational objects from SF to S4Hana. Can you please tell me the SOAManager configuration for this. As you explained to use CO_ECPAOX_EE_MD_ORGAS_BNDL_QRY.
Can you tell me similar objects which are relevant for this 2nd case.
Thanks
Mohan Babu
Hello Mohanbabu Gargisugur
The 2nd iFlow for Org Objects uses the webservices:
SOAMANAGER
Simplified Web Service Configuration
And also uses:
SOAMANAGER
Web Service Configuration
webservice /cxf/ EC_to_ERP_Generic_Object_Query (consumer proxy):
Thanks!
Thanks you very much for your support.
I have configured the proxy CO_SFIOMX_ORG_OBJECT_REPL_QRY as well as Simplified Web Service Configuration for both objects ORGANISATIONALOBJECTREPLICATIO and ORGOBJREPLNOTIFICATION and configured the 2nd Iflow for replication endpoint and notification endpoints.
Can I have your email ID?
Thanks
Mohan Babu
Amazing summary Guilherme!! I know that I could review the Implementation Guide but this summary is an excellent starting point.
Congratz!
Regards,
Ramiro
Well explained.
Is this configuration also applicable if we have several On Premise HCM with one EC using only one deployment I’d the IFlow ? If not Via SCC or customization ?
Thanks Ricardo
Hello Ricardo Soares
Thanks.
If you have several HCM On Premise and one EC, you can create multiple Replication Target Systems in EC side, deploy the same CPI artifact more than once in different tenants or in the same, install multiple SCCs or one if you prefer, and also use the field Location ID to configure your one to many EC to ERP setup for each CPI > ERP call.
Regards,
Soliman
Hi Guilherme/Ricardo,
Well explained and thanks for the question/answer. We are in the same situation... my question is around min requirements for On Premise HCM System... we are upgrading to
ERP6 EHP8 SPS stack 15 we upgrade to:
SAP NW 750 SP19
SAP HR 608 SP83
EA-HR 608 SP83
and we are seeing only the following add-on not the Integration add-on for SAP ERP HCM and SAP SuccessFactors Employee Central is PA_SE_IN 100 SP30 ( as mentioned in Page 27 for Do you meet the minimum setup for SAP ERP HCM systems? section 3.1 )
SUCCESSFACTORS HCM INTEGR 3.0.
So should we go with the above add-on??
When I looked up on PA_SE_IN - it seems to be available in SF ECP but we are still on ERP HCM.
Appreciate your response.
Thanks
AS
Hello AS,
Your set up is okay with:
But you also need to install the PA_SE_IN 100 (install the latest SP level instead of minimum required) to run this integration. This is not only for ECP, it works in ERP HCM too.
Cheers
I must say it's amazing article Soliman.
However i can see configurations from SAP ERP, CPI and SCC and nothing from SuccessFactors. Just wondering if SuccessFactors configurations aren't covered (or) there aren't any configurations itself? Ignore my lack of knowledge in SF area.
I believe successfactors and CPI are on cloud and SAP ERP, SCC are installed on prem. Please correct me understanding here.
Thanks.
Regards,
Santosh
Hello Santhosh ReddyKolanu
Thanks for your feedback.
All the SuccessFactors configurations for this process are covered with more details in the handbook.
In this blog posting I added some details of the SF configurations tasks in the points below of the step 1)
Regarding your other comments, you are corret:
Thanks!
Soliman
Hi Soliman,
For S4HANA > CPI > SF, we have an integration to replicate payslip from S4 > CPI> SF.
We will receive it in pdf file etc and we have to send this to EC. Do you have any idea on this or leads which i can refer for my knowledge.
Thanks,
Santosh
Hello Santosh Reddy
If you want to publish the PDF files (with your payslip) inside the SF application, please consider using the OData Attachment entity. This is descrived in the chapter 5.1 Attachment the handbook https://help.sap.com/doc/74597e67f54d4f448252bad4c2b601c9/latest/en-US/SF_HCM_OData_API_REF_en.pdf
Thanks
Hi Soliman,
This is a great article well detailed.
Few questions:
Appreciate your response
Thanks,
Krishna
Hello Krishna Kallakuri
Thanks.
Thanks for your Response. Found that SCC is a free software.
Hi Soliman,
Can you provide info about Authorization required for SAP user credentials.
Couldnt find the erp endppoint url of ERP receiver in SICF
/sap/bc/srt/scs/sap/eemasterdataandorgassbndlreq
Anything else need to activated.
Thanks,
Krishna
Hello Krishna kallakuri
Regarding the eemasterdataandorgassbndlreq, you can activate this under SOAMANAGER > Simplified Web Service Configuration > using the instructions of the chapter 5.3.3.1 of the handbook.
Regarding the SAP roles for the users we can see in the chapter 3.3.2:
Thank you!
Soliman
Very detailed blogs Soliman.
Thanks for this .
Does activating Best Practice content required for this on-premise setup?
Could you please let us know or we could also proceed without the best practice content?
Hi!
I sent one email for you asking more details about your question 🙂 Thanks
Hello Guilherme, congratulations for the post.
How do I place a bulk change from infotype (0008) from HCM (S4) to SF-EC?
Hello Alan Neves da Silva
Thanks for your feedback.
Your question is related with the migration scenario (HCM to SF). This blog posting is for the connectivity in the opposite way (SF to HCM).
For mass update in the SF-EC, usually HR team uses the Admin center > Import Employee Data (CSV file upload). You can prepare one file from the IT 0008 extracting the changes in the ERP side and manually upload these in the EC portlets like Compensation and others (recurrent / non recurrent).
You can also use the Migration scenario documented in the handbook:
link - Replicating Employee Data from SAP ERP HCM to Employee Central Using SAP Cloud Platform Integration as the Middleware
This handbook above shares the steps how you can connect HCM to SF, creating transformation templates that can generate CSV or use OData upserts (webservices) in the SF-EC entities.
I hope this message can help you 🙂
Soliman
Hello Guilherme Soliman,
Its a Very detailed blogs and really helpful Thanks for writing.
I have followed the same configuration step but getting below message in CPI Payload ERP Query cloud you please let me where i have done wrong .
Problem during invoking SuccessFactors Web service. SOAP faultCode ns2:Server, faultString SFAPI Domain Error!, errorCode INVALID_SFQL, errorMessage:
Invalid SFQL! Error: “person” must be specified in the SELECT clause
<QueryString>SELECT associated_employee_information from CompoundEmployee WHERE replicationTargetSystem = ‘GSDCLNT200’ AND replicationContentType IN (‘EMPLOYEE_MASTER_DATA’,’EMPLOYEE_ORG_ASSIGNMENT’) AND person_id_external IN (‘98000009’) AND company IN (‘gopaljeediD’) AND selectFromDate = to_date(‘1989-01-01′,’yyyy-MM-dd’) AND isContingentWorker IN (‘0’) AND effective_end_date >= to_date(‘1989-01-01’) AND hiringNotCompleted = ‘false'</QueryString>
Hello Neeraj Gupta
Thanks for your message 🙂
The error that you faced is because your ERP transformation template still do not have the WS_2 (PerPerson) entity, so the "person" segment is not being selected in the SELECT clause of the CompoundEmployee.
Please use this path below the complete the ERP customizing:
SPRO > Personnel Management > Integration with SuccessFactors Employee Central > Business Integration Builder > Employee Data Integration > Define Field Mapping for Employee Data > select your transformation template group and double click in the "Transformation template". In this list, you need to add other mandatory segments like the EC Entity WS_2.
Thanks
Hi I would like to know which data the org assignments flow bringing?
Hi Varun,
The org assignments uses the same SFAPI CompoundEmployee payload of the master data.
Inside this payload, we have the data to build the infotype IT0001 (PA0001 and HRP1001 tables), like department, position, division of the employees.
Thanks
Hi Guilherme,
The post is very informative and I followed the steps prescribed in the post for SF to SAP Employee Master Data Replication.
While activating the webservice CO_ECPAOX_EE_MD_ORGAS_BNDL_QRY in SOAMANAGER, I'm getting Connection to Partner Broken error.
Also, when I tried running the program ECPAO_EE_ORG_REPL_QUERY in SE38, I'm receiving Connection to server broken (ICMP_HTTP_CONNECTIO.N_BROKEN) in Error Category Communication.
Could you suggest how to overcome this error?
Regards
Srishti Gupta
Hello Srishti Gupta
Thank you 🙂
“connection to partner broken” error message while pressing the “Ping Web Service” button in SOAMANAGER is expected in some scenarios.
The expert component for that is the BC-ESI-WS-ABA and colleagues shared with us that this error message in some cases does not mean the webservice is not working.
As per KBAs 1947516 and 1711486, it is always recommended to test Web Services in SE80, because pinging it in SOAMANAGER, testing it in a browser or using transaction SICF do not send POST method, which is mandatory for the SOAP service. This could result in empty pages or various HTTP error codes depending on the release.
In that case, please ignore the error and continue with the setup.
Thank you!
Dear Customers/Partners,
I would like to share one additional information that might help in some business.
When there is some mass change in the EC the records starts to be replicated to ERP.
Big changes like 100k employee records at same time or more are similar to “full load”.
If your replications are scheduled too often (like 5 mins interval), the replications delivered in SRTUTIL don’t have time to be completed until the next replication happens, and you might will see the Admin center > Data Replication Monitor with status “In Progress”, because have one overlap of the replications/confirmations being delivered/received.
If this scenario is happening in your company, in few words, our suggestion would be:
These recommendations above are for recovery scenario / delta stuck in the past datetime.
just FYI, the table ECPAO_QRY_ADM has two fields:
- QRY_LSTMOD_DT_TM, which stores the timestamp of last time when the query was launched.
- NXT_LSTMOD_DT_TM, which stores the timestamp of when the processing of the employees finishes.
When you execute a new delta query, the field used in the query is NXT_LSTMOD_DT_TM. This value is then updated to QRY_LSTMOD_DT_TM.
When the processing of the employees finishes, the field NXT_LSTMOD_DT_TM is updated with the current timestamp.
-----
One approach to avoid such scenario is stopping replications before HR team apply huge mass changes in EC.
I hope this can help
Thanks
Soliman
Hi Soliman,
How are you? The table ECPAO_QRY_ADM doesn't have a Table maintenance dialog. How do we change the values in fields QRY_LSTMOD_DT_TM and NXT_LSTMOD_DT_DM?
~Suresh
Dear Suresh,
Just to register here that we spoke about your question in one email. Thank you!
Olá pessoas!
Tenho uma dúvida para configurar o Push Employee Master Data do SAP SuccessFactors Employee Central para SAP ERP ou SAP S4HANA artefato.
Minha dúvida é como ficará o link do endereço do endpoint conforme mostrado na imagem.
Pode me ajudar?
PUSH_NOTIFICATION
Obrigado!
Oi Luciano!
Na configuração do Push Replication, a URL será assim:
http://MASKED.com/sap/bc/srt/scs/sap/eemasterdataandorgasspushnoti?sap-client=200
Existe também um KBA que pode te auxiliar nesse processo 2341986 – How to Enable PUSH Event Replication – SuccessFactors HXM Suite. Recomendo que dê uma olhada nos arquivos anexos desse KBA, onde possui um arquivo com o passo a passo desta configuração.
Abraço!
Marcel Schenk
Hi Luciano,
On Push Replication, the URL will be like this:
http://MASKED.com/sap/bc/srt/scs/sap/eemasterdataandorgasspushnoti?sap-client=200
There is also a KBA that might assist you on configuring this process, which can be seen here: 2341986 – How to Enable PUSH Event Replication – SuccessFactors HXM Suite. You may have a look at the attachments on this KBA which have a step-by-step on the configuration of it.
Thanks!
Hi Guillherme,
Thank you for your help!
Have a great day!
Luciano
Hi @Guilherme Soliman,
This is very precious blog i read.
Currently i am newbie in integration between SF to SAP ERP HCM but i am looking for guidance about :
a. SF Employee Profile integration with SAP ERP HCM using SAP CPI Neo.
There is no Employee Central in client SF but there is SAP CPI Neo version purchased
b. SF integration with other party by utilizing SAP CPI ( other option there is SFTP used but incase SAP CPI can be utilized then how can we establish this )
How can we do the integration in both case ?
Thank you for your advice,
Maya Ang
Hello Maya Anggraeni
For SAP SuccessFactors EP (Employee Profile) and SAP HCM ERP integration, you can use the Talent Addon via SAP CPI and SF OData API.
Talent addon help guides are here = SAP Help Portal
There is also one Rapid deployment docs here (Transfer of SAP ERP HCM basic employee data to SuccessFactors (SF7)) = SAP Best Practices Explorer
Cheers!
Hi Guilherme Soliman , in this case i have SAP CPI Neo, is this sufficient to do integration scenario with SAP ERP HCM ?
Also to do integration to 3rd party, example for one of Podcast product, they are using REST API and need to send data to SAP SF, is this possible to use SAP CPI or any work around tools with consideration that SSO is required.
Thank you very much.
Hello!
The documentations that I shared for SF and HCM talent addon are using SAP CPI, these are the standard packages I know.
For 3rd Party integrations, you can build custom applications in SAP CPI or any other middleware/application solution connecting with REST APIs. In the SF side, even if you have SSO enabled, the REST authentication would be Basic Auth (deprecated) or OAuth2 (recommended one).
Hi Guilherme, thank you very much for your help!
We can set SSO in SF side, but another problem in 3rd party side, how do they know if SF is using UserID for Login authentication because in 3rd party side public login only using email address. This is the final concern, do you have similar experience perhaps ?
Hello Maya Anggraeni
The SF SSO topic is something that my colleagues in Platform area are the experts. I work more in the integrations side (APIs, webservices, middle-wares etc). Kindly raise one incident to LOD-SF-PLT and they will assist you with SSO related topics.
Happy Friday and Cheers!
Thank you very much for your solution Guilherme Soliman , have a wonderfull week end.
Hello Guilherme,
Thank you for the very informative blog. I have a question regarding the BIB employee replication. With SP27 of PA_SE_IN, an enhancement was made to react to the new CompoundEmployee API parameter hiringNotCompleted.
We are in the process of implementing SF Onboarding 2.0. Employees who have started in the Onboarding process but have not been through Manage Pending Hires have a value of hiringNotCompleted = true. It appears as though the BIB employee replication will only replicate employees where hiringNotCompleted = false.
Is it possible to configure employee replication to also replicate employees with hiringNotCompleted = true? I have looked in SPRO at 'Define Parameters for Employee Master Data and Org. Assignment Query' and I don't see any options for the hiringNotCompleted parameter.
Thank you in advance.
Karen
Hello Karen Thompson
I was checking and by default the parameter hiringNotCompleted = ''false' is fixed in the SE24 > CL_ECPAO_EE_MD_ORGAS_QRY method DETERMINE_FILTER_LIST.
This is the place I saw in my internal system with PA_SE_IN SP 0030.
Maybe you dev/abap team can evaluate some enhancement. In case additional info is needed, kindly raise one support incident with the component LOD-EC-INT-EE.
Hope this can help your team.
Cheers
Soliman
Hi Guilherme Please help me, do you know the date that indicates the beginning of the integration of EC to HCM? Is there any way that this date will not be informed or mandatory? For example: I set this date as a golive measure, then in the register is the record with a measure to indicate the admission data, and another to indicate the golive data. Only now I need to rollout a new company, which will start using EC. and golvie's date is just now. Is there a way to indicate this date by company?Hello Luciano, all good?
You can define different go live dates in the same transformation template (we call in BIB as FTSD = full transmission start date) for each country/region. Example, Brazil 01.01.2020 and Argentina 01.01.2021.
Please check the handbook chapter 3.3.2 Configuring County/RegionSpecific Full Transmission Start Dates
Cheers
Hi Everyone,
Hi! Check if this is MDF Picklist or Legacy (are they still used???). If MDF, then in SF, Import and Export -> Picklist-Value.csv. Also, in ERP, set up the respective Constant in SPRO.
Seems like the file is incorrect. But might be the constant incorrect.
Hello Vladimir,
Thank you for response.
In SPRO, I have maintained constant as Y for Mode of picklist file.
I can see that picklist file is MDF.
Can you please check and suggest me how to proceed further,
Regards
Ramya
Hello Guilherme,
Thank you so much for your great material, let me ask one question:
We are considering not using SCC for our project, but the Service EEMASTERDATAANDORGASSBNDLREQ is returning a link beginning with HTTP instead of HTTPS, seems like we did the same procedure you mention here, but it is for cases using SCC, right?
How should I proceed in case of not using SCC to obtain a HTTPS link from the services?
Thank you again for your support and for sharing your knowledge!
Abraço!
Dear Marcus,
thanks!
This integration scenario can be achieved without SCC or also using other tools like SAP web dispatcher, etc., but for that your ERP basis team need to work exposing your SAP webservices endpoints over the internet (HTTPS).
In this sample ERP, my basis colleagues have both enabled (HTTP and HTTPS), so I preferred to use SCC because this is the most common scenario for new customers implementation.
If your SOAMANAGER browser page opened already with HTTP url, it can means your team still did not published the SAP webservices into HTTPS protocol. If you want to explore this path, ask your ERP basis colleagues to help you.
Find below some materials:
Configuring Reverse Proxies - SAP Help Portal
ABAP Connectivity - Web Services ABAP - ABAP Connectivity - Community Wiki (sap.com)
If help for such activity is still needed, your team can raise one incident to BC-ESI-WS-ABA component.
Cheers
Dear Guilherme,
Thank you so much for your quick and complete response!
I will surely do that!
Best regards!
Dear Guilherme,
I cant thank you enough for your support!
We were able to configure the SCC and got it working!
But now when we trigger replication we get the following error message on SCPI.
Sorry for bothering again, but do you have any idea of what is wrong?
We have also opened a ticket with SAP but they are taking a while to get back to us.
PS: I am currently working in Japan, and SAP is lacking experienced people here to support us!
Obrigado!
Dear Marcus,
Greetings. I found one incident reported by you, but there the latest error message shared was different:
Error DetailsInbound processing in endpoint at /Japan_EC_to_ERP_Master_Data_And_Org_Query failed with message "Fault:Sequential processing failed for number 0. Exchange[ID-vsa9273613-1642828427383-106-7]. Caused by: [org.apache.cxf.interceptor.Fault - Could not send Message.]", caused by "UnknownHostException:MASKED_DATA
I saw your attachment XLSX with screenshots and I noticed you tried connecting with Proxy Type = "Internet".
If you want to use SCC, we should change for "On Premise".
I don't see the screenshots of your SCC config inside the incident and also you still did not shared the CPI tenant URL.
Let's continue the work under the incident reported. I will help you over there.
Cheers
Soliman
SAP Product Support
Dear Guilherme,
I have just updated the ticket, and sorry but I should have given you more details there, actually I was in a hurry and didn't link your last name to you.
You were perfect on your points, I went over the guide again and observed that, after configuring the SCC we forgot to change the proxy type to "On Premise".
We have finalized the configuration and it is working perfectly now.
I can't thank you enough for your support! It had a great impact on avoiding our project delay.
Best regards,
Marcus Varjao
Hi Soliman,
Thanks for the blog. Quite informative.
I wanted to know in this iflow is it possible to have customer exits? Or this is not a possibility in the standard Iflow provided?
Appreciate your feedback,
Regards,
Ankur Parab
Hi Soliman,
Thank you for the detailed information, Let me ask one question.
I have followed the same configuration steps but getting below dump error message while running the Query( ECPAO_EE_ORG_REPL_QUERY) in Transaction SE38.
Note: Getting "500 internal server error" when we run the ping webservice in "Webservice configuration" in SOAMANAGER transaction.
Please help me on this to proceed further.
Hi Guilherme,
your blog has really helped me a lot.
When replicating from EC to ERP, no error messages appear. Not in the report, SLG1 or SRT_Moni.
We have indirect valuation in info type 0008 runs great. Since EC is the leading system, I tested the following:
2 more wage types were created for IT0008 in EC (no indirect valuation). During replication, the wage types are displayed as the indirect valuation under the LGA01 in SLG1. However, the wage types do not appear in IT 0008. Only the indirect valuation is displayed. There is no problem with personnel numbers without indirect valuation. All settings to be made for LGA01, LGA02 etc. are set.
Do you have any idea what the problem could be?
Many greetings
Tina