SAP HCM BAPI Integration: Updates Not Reflected When Changing VALIDITYBEGIN and VALIDITYEND

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

Hello everyone,

While working on an integration between SailPoint and SAP HCM using BAPI calls, we’ve encountered an issue where updates are not reflected in SAP when modifying the VALIDITYBEGIN and VALIDITYEND date fields.

When submitting BAPI requests to update user attributes:

  • If we change VALIDITYBEGIN and/or VALIDITYEND, the request is successfully sent from SailPoint, processed by SAP without any errors, but the updated date values are not reflected in SAP after aggregation.
  • If we do NOT modify these date fields, other attribute updates (like email) are correctly reflected in SAP.

For Example :

  • Scenario 1 – Successful Update (Without Date Change):

  • Action: Updated the user’s email (e.g., example.user1@domain.com) without modifying VALIDITYBEGIN and VALIDITYEND.

  • Result: The update was processed successfully, and the changes were correctly reflected in SAP after aggregation.

  • Scenario 2 – Failed Update (With Date Change):

  • Action: Updated the user’s email (e.g., example.user2@domain.com) and modified VALIDITYBEGIN to today’s date.

  • Result: The request was processed without any errors from SAP, but the changes to VALIDITYBEGIN were NOT reflected in SAP after aggregation.

  • The issue consistently occurs when VALIDITYBEGIN and/or VALIDITYEND are modified.

  • When these fields are left unchanged, other attribute updates are applied successfully.

  • No errors are returned from SAP, and logs indicate successful execution of the update request.

**

  1. Has anyone faced similar issues with BAPI-based integrations, where updates to date fields are processed but not reflected in SAP?
  2. Are there any known constraints or validation rules in SAP that could silently block updates to VALIDITYBEGIN/VALIDITYEND without returning errors?
  3. Is there a way to enable more detailed SAP-side tracing to identify if these updates are being rejected internally?
  4. Do updates to these date fields require additional flags or parameters to be set in the BAPI request for SAP to process them correctly?

Any insights, troubleshooting suggestions, or experiences would be greatly appreciated.

Thank you in advance!

2

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.