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

**URL:** <https://developer.sailpoint.com/discuss/t/sap-hcm-bapi-integration-updates-not-reflected-when-changing-validitybegin-and-validityend/100648>\
**Category:** SHF Discussion and Questions\
**Tags:** connectors, provisioning, identity-security-cloud, rules\
**Created:** [February 11, 2025, 8:09am UTC](https://developer.sailpoint.com/discuss/t/sap-hcm-bapi-integration-updates-not-reflected-when-changing-validitybegin-and-validityend/100648 "2025-02-11T08:09:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![krunal\_sshah](https://avatars.discourse-cdn.com/v4/letter/k/90db22/32.png) [@krunal\_sshah](https://developer.sailpoint.com/discuss/u/krunal_sshah)\
**Post date:** [February 11, 2025, 8:09am UTC](https://developer.sailpoint.com/discuss/t/sap-hcm-bapi-integration-updates-not-reflected-when-changing-validitybegin-and-validityend/100648/1 "2025-02-11T08:09:12Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [April 12, 2025, 8:09am UTC](https://developer.sailpoint.com/discuss/t/sap-hcm-bapi-integration-updates-not-reflected-when-changing-validitybegin-and-validityend/100648/2 "2025-04-12T08:09:14Z")

</div>

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