How To Fix MDG_BP_WORKFLOW001 - Table DT_USER_AGT_GRP_BP2P1 does not exist in this client

MDG_BP_WORKFLOW001 - Overview

• Message type: E = Error

• Message class: MDG_BP_WORKFLOW - MDG-BP: Workflow

• Message number: 001

• Message text: Table DT_USER_AGT_GRP_BP2P1 does not exist in this client

What causes this issue?

The decision table DT_USER_AGT_GRP_BP2P1 to assign processors to
workflow step numbers does not exist in the current client.

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?

Procedure for System Administrators

The predefined BRF+ catalog USMD_SSW_CATA_BP2P1 as well as application,
function, decision tables, and content of decision tables is delivered
in the client 000.
Export from client 000:
In the client 000 run transaction BRF+.
On the <ZK>Catalog </>tab, choose <ZK>Select Catalog</>.
On the result list mark the catalog USMD_SSW_CATA_BP2P1 and choose OK.
Double-click the catalog.
Choose <ZK>Tools </>-> <ZK>XML Export</>.
Mark the first line (USMD_00O2TO89O12ZWW2K5W05TVF3V.) and choose
<ZK>Export XML</> -> <ZK>Export XML for Entire Application</>. The
system creates an XML file.
Download the XML file on your PC.
Import to the MDG main client:
RESET N1
In the MDG main client run transaction BRF+ and choose <ZK>Tools </>->
<ZK>XML Import</>.
Select the XML file and choose <ZK>Upload XML File</>.
You can also assign the XML file to a transport request or run a
check-import first.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MDG_BP_WORKFLOW001 - Table DT_USER_AGT_GRP_BP2P1 does not exist in this client ?

  The SAP error message MDG_BP_WORKFLOW001 indicating that the table DT_USER_AGT_GRP_BP2P1 does not exist in the current client typically arises in the context of SAP Master Data Governance (MDG) workflows, particularly when dealing with business partner (BP) data.
  
  Cause:
  
  
  Missing Table: The error suggests that the specified table does not exist in the database for the current client. This could be due to:
  
  The table not being created or activated in the client.
  The table being part of a specific configuration or installation that has not been completed.
  A transport issue where the table definition was not transported to the current client.
  
  
  
  Client-Specific Configuration: The table might be client-specific and may not have been set up correctly during the configuration of the MDG system.
  
  
  Version Mismatch: If there are discrepancies between the versions of the MDG components or if the system has not been properly updated, it could lead to missing tables.
  
  
  
  Solution:
  
  
  Check Table Existence: Use transaction code SE11