Message type: E = Error
Message class: MDG_BP_WORKFLOW - MDG-BP: Workflow
Message number: 003
Message text: Table DT_USER_AGT_GRP_BP6P1 does not exist in this client
The decision table DT_USER_AGT_GRP_BP6P1 to assign processors to
workflow step numbers does not exist in the current client.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The predefined BRF+ catalog USMD_SSW_CATA_BP1P1 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_BP1P1 and choose
<ZK>OK</>.
Double-click the catalog.
Choose <ZK>Tools </>-> <ZK>XML Export</>.
Mark the first line (USMD_00O2TO89O12ZWW2L5OGOV9QW7) 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.
MDG_BP_WORKFLOW003
- Table DT_USER_AGT_GRP_BP6P1 does not exist in this client ?The SAP error message MDG_BP_WORKFLOW003 indicates that the system is unable to find the specified table DT_USER_AGT_GRP_BP6P1 in the current client. This error typically occurs in the context of Master Data Governance (MDG) workflows, particularly when dealing with business partner data.
Cause: Table Not Created: The table DT_USER_AGT_GRP_BP6P1 may not have been created in the current client. This can happen if the necessary configuration or activation steps were not completed. Client-Specific Data: The table might exist in another client (e.g., development or quality assurance) but not in the production client. Transport Issues: If the table was created in a different client and not transported correctly to the current client, it may not exist. Authorization Issues: There may be authorization issues preventing access to the table, although this is less likely to result in a "does not exist" error.
Solution: Check Table Existence: Use transaction code SE11 (Data Dictionary) to check if the table DT_USER_AGT_GRP_BP6P1 exists in the
Get instant SAP help. Sign up for our Free Essentials Plan.
MDG_BP_WORKFLOW002
Table DT_USER_AGT_GRP_BP5P1 does not exist in this client
What causes this issue? The decision table DT_USER_AGT_GRP_BP5P1 to assign processors to workflow step numbers does not exist in the current client.S...
MDG_BP_WORKFLOW001
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.S...
MDG_BS_ACS_ADDR_SCR000
Address screening: &1&2&3&4
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MDG_BS_ACS_ADDR_SCR001
Address screening not possible without name. Check address: &1&2&3&4
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.