SAP Knowledge Base Article - Public

3638836 - Reconfiguring your NEO ECSC instance after KSA Migration (KSA customers Only)

Symptom

In our efforts to modernize our landscape, SAP is performing a DC migration moving customers from DC 23 to DCs 82 and 84.

As a result of this migration, to these customers will be given an option to migrate their ECSC subscriptions from NEO to Cloud Foundry.

In cases where you decide not to migrate from NEO to CF, same yet, some reconfiguration steps needs to be performed in order to keep the connectivity with your instance and the below KBA addresses those steps.

Environment

  • ECSC customers located in DC23

Resolution

Prerequisites

  • On the BTP side:
    • You have a global account in SAP BTP.
    • You have an S-user or P-user. See User and Member Management.
    • You are an administrator of the global account where you want to register your SAP SuccessFactors system.
    • You have enabled the Cloud Foundry capabilities for your subaccount in SAP BTP.
  • On the SAP SuccessFactors side:

Reconfigure Steps 

  1. Recreate the integration token for SAP SuccessFactors in BTP Neo. Refer to: Creating an SAP SuccessFactors Extension
  2. Reconfigure the API key for Bizx_Odata destination (Client key field and Additional Properties assertionIssuer). Refer to: Configuring Destinations on SAP Business Technology Platform
  3. Reconfigure BTP Cloud Portal Service. Refer to: Enabling HR Services on the SAP SuccessFactors Home Page

Keywords

KBA , LOD-SF-INT-AHR , Ask HR - Employee Central Service Center (ECSC) , How To

Product

SAP SuccessFactors HCM Suite all versions