How To Fix PG642 - Entries for infotype &1 are contradictory

SAP Error Message - Details

• Message type: E = Error

• Message class: PG - Error Messages for Master Data Programs

• Message number: 642

• Message text: Entries for infotype &1 are contradictory

What causes this issue?

Two contradictory entries exist in the "Infotypes - Country-Specific
Settings" table (T582L) for infotype &V1&. One entry defines the status
for all country groupings and all subtypes, while the other entry
defines the status for a specific country grouping or subtype. This
does not make sense, as it is not clear which status should be used for
special cases.
Example
Infty,,Infotype text,,Type,,Name,,CGrpg,,Name,,Status
9000 ,,Test,,* ,,all subt.,,* ,,all CGrpg ,,not permitted
9000 ,,Test,,* ,,all subt.,,01 ,,German.,,permitted
The first entry locks infotype 9000 for all subtypes and all country
groupings. However, the second entry means that infotype 9000 can be
used for the Germany country grouping (01). This is the contradiction.

How to fix this error?

Correct the entries accordingly. In the above example, you must delete
the second entry, if infotype 9000 is not to be used any more. If the
infotype must be available for certain country groupings, you must
delete the first entry.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PG642 - Entries for infotype &1 are contradictory ?

  The SAP error message PG642, which states "Entries for infotype &1 are contradictory," typically occurs when there are conflicting entries in the infotype specified (where &1 is the infotype number). This can happen in various contexts, such as when maintaining employee data in the Human Capital Management (HCM) module.
  Cause:
  The error is usually caused by one of the following issues:
  
  Overlapping Time Periods: There are multiple records for the same infotype that have overlapping validity periods. For example, if two records for the same employee exist for the same infotype with different data but overlapping dates, SAP will flag this as contradictory.
  Inconsistent Data: The data entered in the infotype may be inconsistent or contradictory. For example, if one record states that an employee is active while another states they are inactive for the same period.
  Incorrect Configuration: There may be issues with the configuration of the infotype or the way it is set up in the system.
  
  Solution:
  To resolve the PG642 error, you can take the following steps:
  
  
  Check Existing Records:
  
  Use transaction code PA20 (Display HR Master Data) or PA30 (Maintain HR Master Data) to review the entries for the specified infotype.
  Look for overlapping validity periods or contradictory data entries.
  
  
  
  Correct Overlapping Entries:
  
  If you find overlapping records, you will need to adjust the validity periods so that they do not overlap. This may involve deleting or changing the dates of one of the records.
  
  
  
  Ensure Data Consistency:
  
  Make sure that the data entered in the infotype is consistent. For example, if one record indicates an employee's status as "active," ensure that there are no other records indicating a different status for the same period.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to the specific infotype to understand its requirements and constraints.
  
  
  
  Check Configuration:
  
  If the issue persists, consult with your SAP HR configuration team to ensure that the infotype is configured correctly and that there are no underlying issues with the setup.
  
  
  
  Testing:
  
  After making the necessary corrections, test the changes by trying to save the infotype again to ensure that the error no longer appears.
  
  
  
  Related Information:
  
  Infotypes: Infotypes are data structures in SAP HCM that store specific types of employee-related information (e.g., personal data, organizational assignment, payroll data).
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA20, PA30, and PA40 (for actions) to manage HR data effectively.
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific infotype you are working with.
  
  If you continue to experience issues after following these steps, it may be beneficial to reach out to your SAP support team or consult with an SAP expert for further assistance.