SAP HCM HREmployee_Active Distinct() incorrectly selects future records over current records (4383599)

SAP HCM sync silently picks future-dated infotype records instead of current records when both exist for the same employee. Results in wrong values (often 000000 placeholders) being synchronized.

Steps to reproduce:

• Configure SAP HCM connector with HREmployee_Active schema type
  In SAP, create an employee with:
  Current record: BEGDA=2024-01-01, ENDDA=2025-07-31, ORGEH=123456
  Future record: BEGDA=2025-08-01, ENDDA=9999-12-31, ORGEH=000000
• Run Identity Manager synchronization
• Check the employee's organizational assignment in Identity Manager

Expected result:

Employee should have ORGEH=123456 (the currently active value)

Actual result:

Employee may have ORGEH=000000 (the future placeholder value)

This is a product defect (712999).

WORKAROUND:

Change the schema type from HREmployee_Active to HREmployee_CurrentActive in the sync project. This filters out future-dated records and ensures only currently-valid data is synced.

STATUS:

This will be fixed in a future release of the product. If you require this immediately corrected, please contact support for a hotfix referencing the defect ID 712999.
.