How To Fix 5G103 - A primary car record already exists for this person for period & - &

5G103 - Overview

• Message type: E = Error

• Message class: 5G - HR: Messages for Britain

• Message number: 103

• Message text: A primary car record already exists for this person for period & - &

What causes this issue?

A primary car record has already been created for this person for the
period &V1& - &V2&. Although a person may have the use of more than one
company car, he or she may only have one primary car at any one time.
For the purpose of calculating Class 1A National Insurance
contributions, the company car with the highest business mileage should
be treated as the primary car.

System Response

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

How to fix this error?

If the company car involved here is to be treated as a secondary car,
create this record for a secondary car.
However, if this car should be treated as the primary car, delimit the
original primary car record and then create this record for a primary
car.

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 5G103 - A primary car record already exists for this person for period & - & ?

  The SAP error message 5G103 indicates that there is an issue with the personnel records in the system. Specifically, it means that a primary car (or "primary assignment") record already exists for the specified person for the given period. This typically occurs in the context of personnel administration or employee management within SAP.
  
  Cause:
  
  Duplicate Records: The error usually arises when there is an attempt to create a new primary assignment for an employee who already has an existing primary assignment for the same time period.
  Incorrect Date Range: The date range specified for the new record overlaps with an existing primary record.
  Data Entry Errors: Mistakes in data entry, such as incorrect personnel numbers or dates, can lead to this error.
  
  
  Solution:
  
  
  Check Existing Records: 
  
  Navigate to the relevant infotype (e.g., IT0001 for Organizational Assignment) and check if there is already a primary assignment for the employee in question for the specified period.
  If a primary