How To Fix 5C101 - Date of birth key &1 differs from AHV number. Proposal: &2.

5C101 - Overview

• Message type: E = Error

• Message class: 5C - HR: Messages for Switzerland

• Message number: 101

• Message text: Date of birth key &1 differs from AHV number. Proposal: &2.

What causes this issue?

The date of birth code (the seventh and eighth digit of the AHV number)
is calculated as follows:
XX = (31 * Mx) + day of birth.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Mx refers to the month's position in the quarter (M1, M2, M3).
Quarter ,,M1,,M2,,M3
1,,0 (January) ,,1 (February) ,,2 (March)
2,,0 (April) ,,1 (May) ,,2 (June)
3,,0 (July) ,,1 (August) ,,2 (September)
4,,0 (October) ,,1 (November) ,,2 (December)
<ZH>&example&</>
Birthday (01.01.1980): XX = 01 (Mx = 0)
Birthday (15.05.1980): XX = 46 (Mx = 1)
Birthday (30.12.1980): XX = 92 (Mx = 2)

System Response

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 5C101 - Date of birth key &1 differs from AHV number. Proposal: &2. ?

  The SAP error message 5C101, which states "Date of birth key &1 differs from AHV number. Proposal: &2," typically occurs in the context of employee data management, particularly when dealing with social security or pension-related information in Switzerland (AHV stands for "Alters- und Hinterlassenenversicherung," which is the Swiss old-age and survivors' insurance).
  
  Cause:
  This error arises when there is a mismatch between the date of birth associated with an employee's record and the date of birth derived from their AHV number. The AHV number is a unique identifier for individuals in the Swiss social security system, and it includes encoded information, including the date of birth. If the date of birth in the employee's master data does not match the date of birth derived from the AHV number, the system generates this error.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Verify Employee Data: Check the employee's master data in SAP to ensure