HRSD utilizing only ITSM tables

[eli_noble1]

What are the merits and demerits of only using itsm tables for an hrsd subscription? The client is adamant on using only sys_user, sys_user_group, and sys_user_grmember for its users.

Your answers are greatly appreciated.

[Robbie]

Hi @eli_noble1,

Can you provide any context on the 'why' from the client's perspective, please? Is this a subscription and ultimately a billing concern?

What are the objectives of only using these tables and not wanting to leverage the 'HR Profile' table for example? (Is this a table that the client has said they do not want to use or are you/someone proposing having separate tables?)

As I'm sure you're aware, these are not 'ITSM tables', they are core platform tables that ITSM processes as well as other applications such as HRSD use and leverage for good reason. 

What has been the proposed use case for not using these core tables? Don't forget, just because a user record exists within one of these tables, it doesn't mean said user or access to data is exposed. 

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.

Thanks, Robbie

[eli_noble1]

Thanks for your reply.
Sorry for the confusion and wrong use of terms.

I am not sure if it was an billing concern but i think it's related to time constraints.
They want to GO-Live in the earliest time.

So they want to import data on the mentioned table and not use hr profile.
Is it a must to use HR Profile while accessing HR Services?
If we are to disable the OOB to automatically create HR Profile when users access HR Services?
Would that be okay? Will it have implications on the HR subscription?
We are weighing the advantages and disadvantages of using only the core table as is.

Thanks!

[Sandeep Rajput · Accepted solution]

@eli_noble1 I doubt if you will be able to create cases for the subject persons without having their corresponding profile in the HR Profile table. HR Profile is one of the integral constituents of the HR Applications and without it the Case creation would simply not work.There are several fields which are specific to the HR profile table and not available on the User table. 

[eli_noble1]

Thanks Sandeep!
We were thinking of this too. Since OOB, an HR Profile will be generated for the user when filing a case.