Known Issues and Workarounds

7 Known Issues and Workarounds

This chapter provides solutions to the commonly encountered issues associated with the S4HANA connector:

The delete operation is not supported by S4HANA APIs. So, revoking the S4HANA account results in locking user account and shrinking validity period in target.
Reconciling revoked account in OIM will result in creating new account in Disabled state. Due to above reason.
Lock indicator (Lock) field can’t be set while creating user. Even though you set it it’ll not reflect in target.
On User Enable, Start and End date will be set to today’s date and 31-12-9999 respectively. Same will not reflect in Account details until reconciled.
On User Disable, End date will be set to today’s date. Same will not reflect in Account details until reconciled.
Locking user account or user validity in past date will restrict user to login to S4HANA Cloud,
Accounts created thru reconciliation will not populate fields like Gender, Worker Type, Company name, or attributes which are not part of S4HANA Cloud Web Service response.
In target, Start and End Date will only be updated on Employee page while user creation and not thereafter.
In target, End date will be set as ’31-12-9999’ even if value is provided during user creation. It’s a target limitation. To sync it with OIM user attribute, update on user is created