How To Fix HRPADBR99013 - Country modifier &1 not present in date &2

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPADBR99 - General Messages (Master Data)

• Message number: 013

• Message text: Country modifier &1 not present in date &2

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPADBR99013 - Country modifier &1 not present in date &2 ?

  The SAP error message HRPADBR99013, which states "Country modifier &1 not present in date &2," typically occurs in the context of HR (Human Resources) and payroll processing, particularly in the Brazilian localization of SAP. This error indicates that the system is unable to find a specific country modifier for a given date, which is essential for processing payroll or HR-related functions.
  Cause:
  
  Missing Country Modifier: The country modifier specified in the error message is not defined in the system for the date mentioned. This could happen if the country modifier was not set up correctly in the configuration or if it was deleted or not maintained for the specified date.
  Incorrect Date: The date provided in the error message may not correspond to a valid period where the country modifier is applicable.
  Configuration Issues: There may be issues in the configuration of the payroll schema or the country-specific settings that lead to this error.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for the country-specific payroll (in this case, Brazil) and verify that the country modifier is correctly defined for the relevant date.
  Ensure that the country modifier is maintained in the relevant infotypes (e.g., Infotype 0001 for Organizational Assignment).
  
  
  
  Maintain Country Modifiers:
  
  If the country modifier is missing, you may need to create or maintain it in the system. This can typically be done in the customizing settings under the payroll area for Brazil.
  Use transaction codes like SPRO to access the configuration settings and navigate to the relevant sections for country modifiers.
  
  
  
  Check Validity Dates:
  
  Ensure that the date in question is within the valid range for the country modifier. If the date is outside the range, you may need to adjust the date or modify the validity of the country modifier.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to HR and payroll for Brazil to ensure that all necessary configurations are in place.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test run of the payroll or HR process to ensure that the error is resolved.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on configuring country modifiers.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it involves complex configurations or customizations.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.