How To Fix IDGT_LC139 - &1 records are verified; &2 records are not verified

SAP Error Message - Details

• Message type: E = Error

• Message class: IDGT_LC -

• Message number: 139

• Message text: &1 records are verified; &2 records are not verified

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 IDGT_LC139 - &1 records are verified; &2 records are not verified ?

  The SAP error message IDGT_LC139 indicates that during a data verification process, a certain number of records were successfully verified, while others were not. The message format typically looks like this: "&1 records are verified; &2 records are not verified." 
  Cause:
  This error usually arises in the context of data migration, data validation, or during the execution of a specific transaction that involves checking the integrity of data records. The reasons for records not being verified can include:
  
  
  Data Quality Issues: The records that are not verified may contain invalid data, such as incorrect formats, missing mandatory fields, or values that do not meet the defined business rules.
  
  
  Configuration Issues: There may be configuration settings in the system that are not aligned with the data being processed, leading to verification failures.
  
  
  Authorization Issues: The user executing the transaction may not have the necessary authorizations to access or verify certain records.
  
  
  Technical Errors: There could be underlying technical issues, such as database connectivity problems or issues with the verification logic itself.
  
  
  Solution:
  To resolve the IDGT_LC139 error, you can follow these steps:
  
  
  Review the Logs: Check the detailed logs or messages associated with the verification process to identify which specific records failed and why.
  
  
  Data Validation: Examine the records that were not verified. Look for common issues such as:
  
  Missing or incorrect data fields.
  Data types that do not match expected formats.
  Values that violate business rules or constraints.
  
  
  
  Correct Data Issues: Once you identify the problematic records, correct the data issues. This may involve updating records in the database or correcting data entry errors.
  
  
  Check Configuration: Ensure that the system configuration aligns with the data being processed. This may involve reviewing settings in the relevant modules or transaction codes.
  
  
  User Authorizations: Verify that the user has the necessary permissions to access and verify the records in question.
  
  
  Re-run the Verification: After making the necessary corrections, re-run the verification process to see if the issue is resolved.
  
  
  Consult Documentation: If the problem persists, consult SAP documentation or support resources for further guidance specific to the context in which the error occurred.
  
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may be using specific transaction codes related to data migration or validation (e.g., LSMW, LTMC).
  SAP Notes: Check for any relevant SAP Notes that may address known issues related to this error message.
  Support Community: Engage with the SAP Community or forums for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.