How To Fix MDG_BS_BP000 - Method &1 of access class &2 is obsolete

MDG_BS_BP000 - Overview

• Message type: E = Error

• Message class: MDG_BS_BP - MDG BP: general messages

• Message number: 000

• Message text: Method &1 of access class &2 is obsolete

What causes this issue?

The system called a method that must not be used anymore. As of SAP
enhancement package 6 for SAP ERP 6.0 (MDG_APPL 606), functionality is
moved from the old MDG access classes into MDG handler classes. In the
old access classes, the SAP coding of public and protected methods is
commented and the system displayes this warning. Private methods are
deleted.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Do not use the old MDG access classes as of EHP6. Use the related
handler classes instead. The list below shows the old access classes and
their related new access and handler classes.
CL_MDG_BS_BP_ACCESS -> CL_MDG_BS_FND_ACCESS and CL_MDG_BS_BP_HANDLER
CL_MDG_BS_SUPPL_ACCESS -> CL_MDG_BS_ECC_ACCESS and
CL_MDG_BS_SUPPL_HANDLER

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

MDG_BS_BP000 - Details

• The SAP error message MDG_BS_BP000 with the description "Method &1 of access class &2 is obsolete" typically occurs in the context of SAP Master Data Governance (MDG) for Business Partners (BP). This error indicates that a method being called in the specified access class is no longer valid or has been deprecated.
  
  Cause:
  
  Obsolete Method: The method being referenced in the error message has been marked as obsolete in the SAP system. This can happen due to updates or changes in the underlying SAP framework or business logic.
  Version Mismatch: If you are using a version of SAP that is not compatible with the method being called, it may lead to this error.
  Custom Code: If there are custom implementations or enhancements that reference the obsolete method, this can trigger the error.
  
  
  Solution:
  
  Check SAP Notes: Look for any relevant SAP Notes that address this specific error. SAP frequently releases notes that provide fixes or workarounds