HR Administration: COE, HR Service, Topic Detail and Topic Category

[shweta khemani]

Hi All,

Based on my study I understand it is always recommended to use OOTB COEs and not create new COEs based on the flexible data model designed and we also have 57 OOB system delivered HR Services but still we can create new HR Services and then work on creating Topic details and topic category [COE data model structure].

My query is-

1. Shouldn't we prefer to use the delivered set of HR Services often? But not sure in that case why topic detail pushes to create New HR Service and not use existing one. I understand for many org. the requirement will vary and 57 alone might not serve [this follows my next Q.]

2. Do we have any inter-related list of COEs corresponding to specific HR Services? This way we can avoid multiple HR requests, redundant data and even smoothen the flow. If we any such list or guide please share.

I reason I urge to ask this question is because I see multiple new HR services getting created under 1 header: eg- Leave so HR service like leave benefit, leave assistance, leave policy, leave of absence, parental leave, leave process benefits, return to work from leave..etc. 

Hope I am communicate my point. Please share your inputs. Thanks

[Sandeep Rajput · Accepted solution]

@shweta khemani We should try to utilise the OOTB services if they fulfil the need as they can save a lot of time in terms of configuration and maintenance. However, if those 57 services do not match the need then custom HR services can be built,

On HR Service list, you can group by using COEs and find which HR services are part of specific COEs and if there are any redundancies around them,

Hope this helps.

[shweta khemani]

Awesome Sandeep Ji! Really appreciate, thanks for understanding my point and providing the most appropriate feasible solution. 😊

[Sandeep Rajput]

Happy to help 🙂