How To Fix 5E675 - Keep control date in infotype 0041

SAP Error Message - Details

• Message type: E = Error

• Message class: 5E - Error messages for Spanish infotypes module pools

• Message number: 675

• Message text: Keep control date in infotype 0041

What causes this issue?

Report <LS>SLD: Bases file</> (<DS:TRAN.PC00_M04_CRETA_BASES>
RPC_PAYES_CRETA_BASES</>) has generated a file for a supplementary
payment due to backpay (L02), but has not been able to find the start
and end validity dates in the HR attributes or in the report selection
screen.

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?

INCLUDE NA_SYSADMIN1 OBJECT DOKU ID TX

Procedure for System Administrators

The judgment date or the settlement agreement date L02 uses the same
date type mechanisms to indicate different reasons for reporting payment
L03 for different employees. See Customizing activity
<DS:SIMG.PAY_ES_CRETA_BASES04>Associate L03 reporting reasons to date
type</>.
Follow these steps:
In infotype <LS>schedule data</> (0041), verify if there is a date
corresponding to the judgment or settlement agreement date L02.
In view variant VV_T799HRAT_ES_L03, confirm the parameterization of a
date type for infotype <LS>Date Specifications</> (0041) in one of the
following HR attributes:
AT_SLD_I54_1
AT_SLD_I54_2
AT_SLD_I54_3
AT_SLD_I54_4
AT_SLD_I54_5
If there is no parameterization in the HR attributes, the report uses
the date in field <DS:DE.PES_FEDACN>Check date</> of the report
selection screen. Make sure that this field is populated.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 5E675 - Keep control date in infotype 0041 ?

  The SAP error message 5E675, which states "Keep control date in infotype 0041," typically occurs in the context of personnel administration when there is an issue with the control date in Infotype 0041 (Date Specifications). This infotype is used to manage various date-related information for employees, such as the start and end dates of specific events or statuses.
  Cause:
  The error usually arises due to one of the following reasons:
  
  Missing Control Date: The control date in Infotype 0041 is not maintained or is incorrectly set.
  Incorrect Date Format: The date format may not be consistent with the expected format in the system.
  Data Inconsistency: There may be inconsistencies in the data entered in Infotype 0041, such as overlapping dates or invalid date ranges.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Infotype 0041:
  
  Go to the transaction code PA30 (Maintain HR Master Data).
  Enter the employee's personnel number and select Infotype 0041.
  Verify that the control date is correctly maintained. If it is missing, enter the appropriate control date.
  
  
  
  Correct Date Format:
  
  Ensure that the date is entered in the correct format as per your system's configuration (e.g., DD.MM.YYYY).
  
  
  
  Review Date Entries:
  
  Check for any overlapping or conflicting date entries in Infotype 0041. Make sure that the dates do not conflict with other infotypes or entries.
  
  
  
  Consult Documentation:
  
  If you are unsure about the correct control date or how to maintain it, refer to your organization's SAP documentation or consult with your HR or SAP support team.
  
  
  
  Testing:
  
  After making the necessary changes, try to save the infotype again to see if the error persists.
  
  
  
  Related Information:
  
  Infotype 0041: This infotype is part of the SAP HR module and is used to manage various date specifications for employees.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA30 (Maintain HR Master Data) and PA20 (Display HR Master Data) for managing employee data.
  SAP Notes: Check SAP Notes for any specific patches or updates related to this error message, as there may be known issues or fixes provided by SAP.
  
  If the problem persists after following these steps, it may be necessary to involve your SAP support team or consult with SAP documentation for further troubleshooting.