GRACUSER table in blank after Rep/User sync job

[plaban_sahoo]

Hi All,

GRC 12

i have the parameters 1022 and 1046 filled up with Connector group of S4 HANA. And User data source is also filled with up S4 HANA connector. However, Rep. sync job does not fill up the GRACUSER table. but fills up the GRACUSERCONN table

Please suggest of this is the normal behavior

Regards

Plaban

[shivam_agarwal1]

Hi Plaban

Yes, if XYZ id exists in both tables(irrespective of same connector) then it should be searchable.

You can try running full repository sync for that connector. If still it doesn't show, please raise OSS message and update me with number. We might have to check that in your system w.r.t code

Thanks

Shivam

[plaban_sahoo]

Hi Shivam,

Full rep sync job also did not result in id showing up in User search

regards

Plaban

[plaban_sahoo]

Hi Shivam,

As GRACUSER does not contain ids from S4, this means the same ids has been pulled up from diff. connectors.

With this being the case and GRACUSERCONN being filled with the same ids from S4, as per your comments(...join from GRACUSER and GRACUSERCONN ...) should reflect the ids in user search. Btu it has not

Regards

Plaban

[shivam_agarwal1]

Hi Plaban

This is done in join from GRACUSER and GRACUSERCONN both. Entries should be consistent in these tables for user search to work correctly in GRC frontend screens.

Thanks

Shivam

[shivam_agarwal1]

Hi Plaban

GRACUSER is a header table. It will only contain one entry for user (lowercase and uppercase each). So, if there is entry already exist for XYZ user in uppercase for a particluar connector then it will not insert new record in table if new entry is also in uppercase and vice-versa. Though GRACUSERCONN will have multiple entries for XYZ user against each connector.

Thanks

Shivam

[plaban_sahoo]

Hi Shubham,

the features of GRACUSER is already known to us.

can you suggest from which table are the users fetched when we do a user search in a foreground risk analysis for a part. system,

regrads

Plaban