How To Fix FIEU_SAFT134 - Vendor &1 blocked in document &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FIEU_SAFT - FIEU_SAFT

• Message number: 134

• Message text: Vendor &1 blocked in document &2

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 FIEU_SAFT134 - Vendor &1 blocked in document &2 ?

  The SAP error message FIEU_SAFT134 indicates that a vendor (identified by &1) is blocked in a specific document (identified by &2). This error typically arises in the context of financial transactions, such as invoice processing or payment runs, where the system checks the status of the vendor involved in the transaction.
  Cause:
  
  
  Vendor Blocked: The vendor is blocked for certain transactions, which could be due to various reasons such as:
  
  The vendor has been marked as blocked in the vendor master data.
  The vendor is blocked for specific purchasing or payment activities.
  There may be a temporary block due to compliance checks or other internal policies.
  
  
  
  Document Type Restrictions: The document type being processed may have restrictions that prevent transactions with blocked vendors.
  
  
  Configuration Issues: There may be configuration settings in the system that enforce vendor blocking under certain conditions.
  
  
  Solution:
  
  
  Check Vendor Status:
  
  Go to the vendor master data (transaction code XK03 or MK03) and check the status of the vendor. Look for any blocks that may be in place.
  If the vendor is blocked, determine the reason for the block and whether it can be lifted.
  
  
  
  Unblock Vendor:
  
  If appropriate, unblock the vendor by editing the vendor master data (transaction code XK02 or MK02). Ensure that you have the necessary authorizations to make changes.
  
  
  
  Review Document Type:
  
  Check the document type being used in the transaction. Ensure that it allows transactions with the vendor in question.
  
  
  
  Consult with Compliance/Finance Team:
  
  If the vendor is blocked for compliance reasons, consult with the relevant department to understand the implications of unblocking the vendor.
  
  
  
  Error Handling:
  
  If the block is valid and should remain, you may need to find an alternative vendor or adjust the transaction accordingly.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  XK03: Display Vendor
  XK02: Change Vendor
  MK03: Display Vendor (Purchasing)
  MK02: Change Vendor (Purchasing)
  
  
  
  Vendor Master Data: Understanding how vendor master data is structured and maintained in SAP is crucial. This includes knowing the different views (general, purchasing, accounting) and the implications of blocking a vendor.
  
  
  SAP Notes: Check for any relevant SAP Notes or documentation that may provide additional context or solutions for this specific error message.
  
  
  Authorization: Ensure that you have the necessary authorizations to view and modify vendor data, as well as to process the relevant documents.
  
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.