/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PublicSymptom
In our efforts to keep out customer with the most modern landscape. SAP ia performing a datacenter migration which will affect DC23 customers to GCP platform.
As a result of this migrations, customers are required to perform a series of steps to keep a smooth transition.
The below KBA compiles a checklist of all points customers needs to be aware and take action.
Resolution
|
Phase |
Activity |
Description |
Complete By |
Reference Doc |
|
Pre-Migration |
Customer to create a cloud foundry subaccount for ECSC under your global account |
The customer is requested to create a subaccount for ECSC, so that customer can do the migration from neo to cloud foundry. |
T-30 days | |
|
Pre-Migration |
Customer to provide the subdomain of subaccount |
The customer is requested to share the subdomain of the created subaccount to SuccessFactors via the inbox (SAP_Cloud_Technology_EMEA@sap.com) to create a route in the service provider’s subaccount which including environment info, DC info and subdomain(please don’t use any special character in subdomain and it’s better to control sundomain’s length under 10). |
T-30 days |
|
|
Pre-Migration |
Document all integrations and use cases necessary for validating the target instance after migration |
Customer to document all relevant integrations and associated use cases that will be essential to validate the functionality, performance. This should include third-party system connections, and any critical business scenarios that must be tested to ensure a successful transition |
T-15 days |
|
|
Post-Migration |
Connect SAP SuccessFactors to SAP BTP and trigger registration in SAP SuccessFactors company |
Part of ECSC migration |
T-0 days | |
|
Post-Migration |
Establish trust between SAP SuccessFactors and SAP BTP |
Part of ECSC migration |
T-0 days | |
|
Post-Migration |
Register the Assertion Consumer Service of the Subaccount in SAP BTP in SAP SuccessFactors |
Part of ECSC migration |
T-0 days | |
|
Post-Migration |
Use OAuth Client with SAML Bearer Assertion Authentication to build Bizx Odata destination |
Part of ECSC migration |
T-0 days | |
|
Post-Migration |
Integrate with C4C |
Part of ECSC migration |
T-0 days |
Configuring Destinations on SAP Business Technology Platform |
|
Post-Migration |
Integrate with 3rd party external system |
Customer may need to integrate with workzone/sharepoint/qualtrics per their requirements |
T-0 days |
Work Zone KB configuration: https://me.sap.com/notes/3638833/E For other systems, please refer to NEO help doc as the configuration steps are the same: |
|
Post-Migration |
Mobile integration |
Customer may need to do mobile intergration per their requirements |
T-0 days |
Configuring Ask HR Application on Mobile Devices after KSA migration |
|
Post-Migration |
Subscribe to the AskHR Saas App |
Part of ECSC migration |
T-0 days | |
|
Post-Migration |
Change the URL in the provisioning for ECSC |
Part of ECSC migration |
T-0 days | |
|
Post-Migration |
Functional testing |
It is essential for customers to perform functional testing to ensure their business processes and integrations continue to work as expected in the new environment. |
T-0 days |
|
See Also
3633157 - Basic Guideline for ECSC Migration for NEO to Cloud Foundry (KSA customers ONLY)
3638836 - Reconfiguring your NEO ECSC instance after KSA Migration (KSA customers Only)
3642257 - Reconfiguring your Cloud Foundry ECSC instance after KSA Migration (KSA customers Only)
Keywords
KBA , LOD-SF-INT-AHR , Ask HR - Employee Central Service Center (ECSC) , How To
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)