How To Fix GPD2042 - DB inconsistency in Purchase order &1 &2, between MDBS and EKKN

GPD2042 - Overview

• Message type: E = Error

• Message class: GPD2 - GPD for DIMP4.71 uses message class GPD & GPD2

• Message number: 042

• Message text: DB inconsistency in Purchase order &1 &2, between MDBS and EKKN

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 GPD2042 - DB inconsistency in Purchase order &1 &2, between MDBS and EKKN ?

  The SAP error message GPD2042 indicates a database inconsistency in a Purchase Order (PO) between the Material Document Database (MDBS) and the Purchase Order Item Accounting (EKKN) table. This inconsistency can arise due to various reasons, such as data corruption, incomplete updates, or issues during data migration.
  
  Cause:
  
  Data Corruption: This can occur due to system crashes, improper updates, or other unforeseen issues that affect the integrity of the database.
  Incomplete Transactions: If a transaction involving the purchase order was not completed successfully, it may lead to inconsistencies between the MDBS and EKKN tables.
  Custom Developments: Custom programs or enhancements that manipulate purchase order data may inadvertently cause inconsistencies.
  Data Migration Issues: If data was migrated from another system or during an upgrade, inconsistencies may arise if the migration process did not handle all dependencies correctly.
  
  
  Solution:
  
  Check for Inconsistencies: Use transaction codes like SE16 or SE11 to check the MDBS and EKKN tables for the specific