How To Fix MDG_BS_SUPPL_BOLUI006 - Company code &1 uses the extended withholding tax maintenance

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_BS_SUPPL_BOLUI - MDG: messages for Supplier UI related issues

• Message number: 006

• Message text: Company code &1 uses the extended withholding tax maintenance

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_BS_SUPPL_BOLUI006 - Company code &1 uses the extended withholding tax maintenance ?

  The SAP error message MDG_BS_SUPPL_BOLUI006 indicates that the company code specified (represented by &1) is using the extended withholding tax maintenance feature. This error typically arises in the context of Master Data Governance (MDG) for suppliers when there is an issue related to the withholding tax configuration for a specific company code.
  Cause:
  
  Extended Withholding Tax Configuration: The company code is set up to use extended withholding tax features, which may require additional data or settings that are not properly configured.
  Missing Data: Required withholding tax data for the supplier or company code may be missing or incomplete.
  Incompatibility: The transaction or operation being performed may not be compatible with the extended withholding tax settings.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for withholding tax in the SAP system.
  Ensure that the extended withholding tax settings are correctly configured for the company code in question.
  
  
  
  Review Supplier Data:
  
  Check the supplier master data to ensure that all necessary withholding tax information is filled out correctly.
  Make sure that the supplier is assigned to the correct company code and that the withholding tax types are properly maintained.
  
  
  
  Transaction Compatibility:
  
  Verify that the transaction you are trying to execute is compatible with the extended withholding tax maintenance. Some transactions may not support this feature.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on extended withholding tax maintenance and any prerequisites or dependencies that need to be addressed.
  
  
  
  Testing:
  
  If changes are made, test the process again to ensure that the error does not reoccur.
  
  
  
  Seek Support:
  
  If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert who can provide more tailored assistance based on your specific configuration and requirements.
  
  
  
  Related Information:
  
  Withholding Tax Types: Understand the different types of withholding taxes that can be configured in SAP and how they apply to your business processes.
  Master Data Governance (MDG): Familiarize yourself with the MDG framework and how it manages supplier data, including the implications of extended features like withholding tax.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide patches related to this error message.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.