How To Fix MDG_TR085 - Field &1 is new in target table &2

MDG_TR085 - Overview

• Message type: E = Error

• Message class: MDG_TR - MDG: Transport Tool

• Message number: 085

• Message text: Field &1 is new in target table &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 MDG_TR085 - Field &1 is new in target table &2 ?

  The SAP error message MDG_TR085, which states "Field &1 is new in target table &2," typically occurs in the context of SAP Master Data Governance (MDG) when there is a discrepancy between the source and target data structures during a data transfer or replication process. This error indicates that a field (denoted as &1) has been added to the target table (denoted as &2) but is not present in the source data structure.
  
  Cause:
  
  Schema Changes: The target table has been modified to include new fields that are not present in the source data structure. This can happen due to updates in the data model or changes in business requirements.
  Data Model Mismatch: The data model in the source system may not be aligned with the target system, leading to missing fields.
  
  Configuration Issues: There may be configuration issues in the MDG setup that do not account for the new fields in the target