How To Fix WS354 - Not all documents could be blocked (see long text)

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 354

• Message text: Not all documents could be blocked (see long text)

What causes this issue?

One or more documents are blocked by another user.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

You can execute the program run if you deselect the <LS>Block all
documents</> indicator. Then, documents are not blocked together, but
individually during processing. However, documents which cannot be
blocked are excluded from processing (error message).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WS354 - Not all documents could be blocked (see long text) ?

  SAP Error Message:
  
  WS354 - Not all documents could be blocked (see long text)
  
  Cause:
  This error occurs when you attempt to block multiple documents (such as invoices, purchase orders, or accounting documents) for payment or processing, but some of the documents cannot be blocked due to certain conditions or inconsistencies. The system tries to block all selected documents, but some fail the blocking criteria.
  Common reasons include:  
  
  The document is already blocked or cleared.  
  The document is in a status that does not allow blocking (e.g., already paid, reversed, or locked by another process).  
  Missing or incorrect data in the document that prevents blocking.  
  Authorization issues where the user does not have permission to block certain documents.  
  Document is part of a payment run or locked by another user/process.
  
  
  Solution:
  
  
  Check the Long Text:
  
  The long text of the error message usually provides details about which documents could not be blocked and why. Review it carefully to identify the problematic documents.
  
  
  Verify Document Status:  
  
  Check if the documents are already blocked or cleared.  
  Ensure the documents are not part of an ongoing payment run or locked by another user.
  
  
  
  Review Document Data:  
  
  Verify that all required fields and conditions for blocking are met.  
  Correct any inconsistencies or missing data.
  
  
  
  Authorization Check:  
  
  Confirm that you have the necessary authorizations to block the documents.
  
  
  
  Retry Blocking Individually:  
  
  Try blocking the documents one by one to isolate which document(s) cause the issue.
  
  
  
  Use Transaction Codes:  
  
  For blocking invoices: Use transaction F110 (Automatic Payment Transactions) or FB02 (Change Document) to manually block documents.  
  For purchase orders or other documents, use the relevant transaction to block or change the document status.
  
  
  
  Check for Locks:  
  
  Use transaction SM12 to check if the document is locked by another user or process.
  
  
  
  Consult SAP Notes:  
  
  Search SAP Support Portal for notes related to WS354 for any known bugs or patches.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:  
  
  F110 – Automatic Payment Transactions (blocking/unblocking invoices)  
  FB02 – Change Document (block/unblock accounting documents)  
  SM12 – Display and delete locks  
  ME22N – Change Purchase Order (block/unblock PO)  
  
  
  
  SAP Help and Documentation:  
  
  Refer to SAP Help Portal for payment block procedures and document status management.  
  Check SAP Notes and Knowledge Base Articles for specific scenarios related to WS354.
  
  
  
  Common SAP Tables:  
  
  BKPF – Accounting Document Header  
  BSEG – Accounting Document Segment  
  RBKP – Invoice Document Header  
  EKPO – Purchasing Document Item  
  
  
  
  
  Summary:
  WS354 indicates that not all selected documents could be blocked due to various reasons such as document status, locks, missing data, or authorization issues. The key to resolving this error is to review the detailed long text, identify problematic documents, verify their status and data, and then take corrective action accordingly.
  
  If you provide the exact context (e.g., transaction used, document type), I can help with more specific troubleshooting steps.