How To Fix EDOCUMENT_ES_SII059 - Blocked business partner selected; processing aborted

SAP Error Message - Details

• Message type: E = Error

• Message class: EDOCUMENT_ES_SII - Messages for eDocuments SII Spain

• Message number: 059

• Message text: Blocked business partner selected; processing aborted

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 EDOCUMENT_ES_SII059 - Blocked business partner selected; processing aborted ?

  The SAP error message EDOCUMENT_ES_SII059 indicates that a business partner (BP) has been blocked, which prevents further processing of electronic documents related to that partner. This error is commonly encountered in the context of the SII (Suministro Inmediato de Información) reporting in Spain, where businesses are required to submit VAT information in real-time.
  Cause:
  The error occurs when:
  
  The business partner has been marked as "blocked" in the SAP system.
  The blocking could be due to various reasons, such as compliance issues, credit risks, or internal company policies.
  The system is configured to prevent processing of documents for blocked business partners to ensure compliance and data integrity.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Business Partner Status:
  
  Navigate to the Business Partner (BP) transaction in SAP (usually via transaction code BP).
  Search for the specific business partner that is causing the error.
  Check the status of the business partner to confirm if it is indeed blocked.
  
  
  
  Unblock the Business Partner:
  
  If the business partner is blocked and you have the necessary permissions, you can unblock it by editing the business partner details.
  Remove the block status and save the changes.
  
  
  
  Consult with Relevant Departments:
  
  If you do not have the authority to unblock the business partner, consult with your finance or compliance department to understand why the partner was blocked and whether it is appropriate to unblock them.
  
  
  
  Review Configuration Settings:
  
  Ensure that the configuration settings for business partner blocking are aligned with your company’s policies and compliance requirements.
  
  
  
  Retry Processing:
  
  After unblocking the business partner, retry processing the electronic document that was previously aborted.
  
  
  
  Related Information:
  
  Documentation: Refer to SAP Help documentation for more details on managing business partners and handling electronic documents.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as BP for business partner management and SII for SII-related transactions.
  User Roles: Ensure that users have the appropriate roles and authorizations to manage business partner statuses.
  Audit Trail: Keep an audit trail of changes made to business partner statuses for compliance and reporting purposes.
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP support team or refer to SAP Notes for any known issues or patches related to this error message.