Skip to Content
avatar image
Former Member

HR Renewal Configuration in Central Hub Deployment

We are planning to implement HR Renewal 2.0 FP5  for one of our client and we are planning for a Central Hub deployment for Gateway services.

We would like to understand the recommended approach for configuration

My recommended Option 1

Configuration in ECC system – activation of SICF services, LPD_CUST, PFCG role, ESS UI5 , MSS UI5, Enhancing UIBB’s HR Renewal Landing page configuration and settings etc.

Configuration in Gateway server – activation of Odata services and ICF services, RFC connection

Technical team Option 2 is (They are implementing Fiori for Simple Finance and for this most of the configurations are in Gateway)

Configuration in ECC system –, ESS UI5 , MSS UI5, Enhancing UIBB’s

Configuration in Gateway server – activation of Odata services and ICF services, RFC connection, activation of SICF services, LPD_CUST, PFCG role, HR Renewal Landing page configuration and settings

Technical team is implementing Fiori for Simple Finance and for this most of the configurations are in Gateway and there question is why not HR Renewal configurations cannot be similar way

What is the SAP recommended approach?

Appreciate your thoughts.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Nov 04, 2015 at 04:46 AM

    HR renewal also has WD ABAP screens and data and configuration all comes from ECC HCM

    We keep Odata services typically on gateway, you had raised another similar thread.

    option 1 is usually the way to go

    Add comment
    10|10000 characters needed characters exceeded