09/27/2022 03:41 AM
Hi Team,
We have a Single Thread Account Import Job that ends with this error.
Error Saving data from TEMPACCOUNT_ENTITLEMENTS1 -
INSERT INTO ACCOUNT_ENTITLEMENTS1
The connection is an SAP Based connection.
The Accounts import failed on certain days in the past but recently seems to be working fine.
The SAP Connection has the tables updated.
The connection history shows no change done on the particular days where the import failed with the above failure.
Please do let us know by any suggestions or by default if the SAP Import is implemented via any File or any other details we need to check to troubleshoot this error.
The connection did not contain of the keywords mentioned in this error.
Thank you and Regards,
Jegathalayan T
Solved! Go to Solution.
09/27/2022 04:04 AM
Does your SAP version Upgraded?
Can you share tables you are trying to import
10/06/2022 12:29 AM
Hi Rushikesh,
Thank you for responding, There was No SAP Upgrade and the tables we import from SAP are USR02,AGR_USERS and 2 More for this particular endpoint and this error occurred in a particular date in the past.
Now the Import Job seems to be working fine and we are trying to find the root cause of this error.
Please do advise if this is a known issue
Thank you and Regards,
Jegathalayan T
10/06/2022 04:55 AM
This can be possible due to wsretry & import job ran at same time
02/15/2023 12:04 PM
Did you ever figure out the root cause? This just happened to me two days in a row. Looking to see if I need to raise a FD ticket or not.
02/15/2023 10:15 PM
We found that Saviynt and SAP were not in sync, if you have a Full import job and incremental Job please make sure their connection details are correct and ensure the Roles, Accounts and accesses are all in sync in both Saviynt and SAP. If needed run them accordingly and more often if needed.
it was a matter of running the Full Import Jobs more that ensured we did not get this error.
So Roles, Accounts and Accesses has to be same in Saviynt and SAP to avoid this issue.
If you have an SAP resource/team contact available you can even cross verify with them if the data you have in Saviynt is the same in SAP using some checks, then this error will not occur again.
02/15/2023 10:27 PM
It seems issue you reported vs finding are contractdicating.
It seems on details you are running sod thats why you need data to be same in both instances hence account import.
initial problem you mentioned import is not running but solution you saying data not in sync . Why is still not clear.
if you’re using sod then data needs to be sync because those are sent from saviynt to external grc system (hierarchy)