How To Fix FZ368 - Vendor & &: No payment due to delete flag or posting block

SAP Error Message - Details

• Message type: E = Error

• Message class: FZ - Payment Transactions

• Message number: 368

• Message text: Vendor & &: No payment due to delete flag or posting block

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 FZ368 - Vendor & &: No payment due to delete flag or posting block ?

  The SAP error message FZ368 indicates that a vendor has a delete flag or a posting block, which prevents any payments from being processed for that vendor. This error typically arises in the context of accounts payable when attempting to make a payment to a vendor who is either marked for deletion or has a posting block set in their vendor master data.
  Causes:
  
  Delete Flag: The vendor master record has been marked for deletion. This means that the vendor is no longer active and should not be used for transactions.
  Posting Block: The vendor has a posting block set, which can be due to various reasons such as:
  
  The vendor is under review.
  The vendor has outstanding issues that need to be resolved.
  The vendor is inactive or has been flagged for some compliance or audit reasons.
  
  
  
  Solutions:
  
  
  Check Vendor Master Data:
  
  Go to the vendor master data (transaction code XK03 for general data or FK03 for company code data).
  Check if the delete flag is set. If it is, you may need to remove the delete flag if the vendor is still active and should be used for payments.
  If the vendor is no longer needed, consider whether to keep the delete flag or to archive the vendor properly.
  
  
  
  Review Posting Block:
  
  In the vendor master data, check if there is a posting block set. If there is, determine the reason for the block.
  If the posting block is no longer applicable, you can remove it. This may require appropriate authorization depending on your organization's policies.
  
  
  
  Consult with Relevant Departments:
  
  If you are unsure about the status of the vendor or the implications of removing the delete flag or posting block, consult with your finance or procurement department for guidance.
  
  
  
  Documentation and Compliance:
  
  Ensure that any changes made to the vendor master data are documented and comply with your organization's policies and procedures.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  XK03: Display Vendor Master Data
  FK03: Display Vendor Master Data for Company Code
  XK02: Change Vendor Master Data
  FK02: Change Vendor Master Data for Company Code
  
  
  
  User Authorizations: Ensure that you have the necessary authorizations to make changes to vendor master data.
  
  
  Audit Trail: Keep in mind that changes to vendor master data may be subject to audit, so maintain a clear record of any modifications made.
  
  
  By addressing the delete flag or posting block appropriately, you should be able to resolve the FZ368 error and proceed with the payment to the vendor.