How To Fix WTADDI215 - Sales and Distribution document & currently blocked

SAP Error Message - Details

• Message type: E = Error

• Message class: WTADDI - Additionals: Messages

• Message number: 215

• Message text: Sales and Distribution document & currently blocked

What causes this issue?

You wish to have the system generate or change a purchase order for an
<DS:GLOS.additional>additional</> automatically. In order for this to
be possible, <DS:GLOS.delivery>delivery</> &V1&, to which the
additionals document is assigned, must be blocked. However, this
document is currently being processed.
No follow-on purchase order is generated, as processing the delivery
could result in changes being made to the additionals document. For
example, if you made changes now to the <DS:DE.LFIMG>delivery quantity
</> or <DS:DE.WADAK>planned goods issue date</> in an item in delivery
&V1&, this would lead to changes in the additionals document.

System Response

The purchase order for the additional is not generated/changed.

How to fix this error?

Try again later.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WTADDI215 - Sales and Distribution document & currently blocked ?

  Certainly! Here's a detailed explanation for the SAP error message WTADDI215: Sales and Distribution document & currently blocked:
  
  Error Message
  WTADDI215: Sales and Distribution document & currently blocked
  
  Cause
  This error occurs when you try to perform a Warehouse Management (WM) activity (such as creating or changing a transfer order, posting goods movement, or confirming a warehouse task) that involves a Sales and Distribution (SD) document which is currently blocked in the system.
  The block on the SD document can be due to several reasons, such as:
  
  The SD document is locked by another user or process.
  The SD document is in a status that prevents further processing (e.g., delivery blocked, billing blocked).
  The document is undergoing a change or update in another transaction.
  There is a lock entry in the system (enqueue lock) on the SD document.
  
  
  Solution
  To resolve this error, you can take the following steps:
  
  
  Check Document Lock:
  
  Use transaction SM12 to check for lock entries on the SD document number.
  If a lock exists and is no longer needed (e.g., a user session was terminated abnormally), you can delete the lock entry carefully after confirming no active process is using it.
  
  
  
  Check Document Status:
  
  Review the status of the SD document (e.g., delivery document, sales order).
  Ensure that the document is not blocked for delivery or billing.
  If blocked, investigate the reason for the block and remove it if appropriate.
  
  
  
  Wait or Coordinate:
  
  If the document is being processed by another user or batch job, wait until the process completes.
  Coordinate with other users or departments to avoid simultaneous changes.
  
  
  
  Check for Incomplete or Inconsistent Data:
  
  Sometimes, inconsistencies between SD and WM can cause blocks.
  Run consistency checks or use transaction LT24 (Display Transfer Orders) or VL02N (Change Outbound Delivery) to verify the document status.
  
  
  
  System Restart or Support:
  
  If locks persist and cannot be removed, a system restart or support from the SAP Basis team may be required.
  
  
  
  
  Related Information
  
  
  Transactions to check locks:  
  
  SM12 – Display and delete lock entries  
  VL02N – Change Outbound Delivery  
  VA02 – Change Sales Order  
  LT24 – Display Transfer Orders
  
  
  
  Common scenarios causing this error:  
  
  Simultaneous access to the same SD document by multiple users.  
  Background jobs updating the document while a user tries to process it.  
  Incomplete or failed warehouse tasks or transfer orders linked to the SD document.
  
  
  
  SAP Notes and Documentation:  
  
  Check SAP Notes related to WM and SD integration for any known issues.  
  Review SAP Help Portal documentation on Warehouse Management and Sales and Distribution integration.
  
  
  
  
  If you provide the exact transaction or process where this error occurs, I can help with more specific troubleshooting steps.