How To Fix 5Y858 - & & - Table MDTYPE inconsistent. Personnel No. rejected

5Y858 - Overview

• Message type: E = Error

• Message class: 5Y - Error messages for info-type Italian module pools

• Message number: 858

• Message text: & & - Table MDTYPE inconsistent. Personnel No. rejected

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 5Y858 - & & - Table MDTYPE inconsistent. Personnel No. rejected ?

  The SAP error message 5Y858 with the description "Table MDTYPE inconsistent. Personnel No. rejected" typically indicates an inconsistency in the data related to the personnel number in the context of the MDTYPE table, which is used for managing personnel data types in SAP.
  
  Cause:
  
  
  Data Inconsistency: The error usually arises when there is a mismatch or inconsistency in the data stored in the MDTYPE table for the specified personnel number. This could be due to:
  
  Missing entries in the MDTYPE table for the personnel number.
  Incorrect or corrupted data entries.
  Changes in the personnel data that have not been properly updated in the MDTYPE table.
  
  
  
  
  Configuration Issues: There may be issues with the configuration settings related to personnel management or the specific data types being used.
  
  
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access or modify the data related to the personnel number.
  
  
  
  Solution:
  
  
  Check MDTYPE Table: 
  
  Use transaction code SE11 or SE16 to