How To Fix EDEREG_INV686 - Clearing lock &1 set in document &2

SAP Error Message - Details

• Message type: E = Error

• Message class: EDEREG_INV - Error Messages for Payment Management in a Deregulated Env.

• Message number: 686

• Message text: Clearing lock &1 set in document &2

What causes this issue?

The clearing lock &V1& has been set for all document items of document
&V2&.

System Response

A special case has occurred during creation of the aggregated incoming
bill which means that the posted uncleared FI-CA document must be
checked before clearing takes place. Therefore, the clearing lock &V1&
has been set for all document items of document &V2&.

How to fix this error?

Check, for example, whether a special case exists where a tax correction
posting takes place that only requires a correction to the tax amount.
With this combination of data, the situation can arise that the paid
budget billing payments exactly match the bill amount, but there is a
minor difference (due to rounding difficulties) between the individual
posted budget billing bills and the posted bill amount in the total.
However, the combination of data result in major differences and you may
no longer be able to remove the clearing lock because the document item
has already cleared itself (self-clearing due to zero amount).
Check document &V2&. If you do not find any errors, and self-clearing
has not occurred, use transaction FPE2 (Change Document) to remove the
clearing lock &V1& for all document items that have not cleared
themselves.
Self-clearing is only permitted if the maximum limit (&V3&) is not
exceeded for the following special cases:
Gross amount equal to tax base amount equal to zero, but tax amount not
equal to zero
Tax base amount and tax amount have different +/- signs
Gross amount and tax amount not equal to zero, but tax base amount equal
to zero
If an error occurs, contact your system administrator.

Procedure for System Administrators

In the event of an error, and based on the correction or release status
of your system, you can use a report to reverse the document for the
aggregated incoming bill. To do this, create a problem message.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EDEREG_INV686 - Clearing lock &1 set in document &2 ?

  The SAP error message EDEREG_INV686, which states "Clearing lock &1 set in document &2," typically occurs in the context of financial document processing, particularly when dealing with clearing operations in accounts receivable or accounts payable. This error indicates that a lock is set on a document that is preventing the current operation from proceeding.
  Cause:
  
  Document Locking: The document referenced in the error message is currently locked by another user or process. This can happen if another transaction is being processed on the same document, such as a clearing or posting operation.
  Long-running Transactions: If a transaction takes too long to complete, it may hold a lock on the document longer than expected.
  Batch Jobs: Background jobs or batch processes that are running and accessing the same document can also lead to this locking issue.
  Inconsistent Data: Sometimes, inconsistencies in the database or issues with the application logic can lead to unexpected locks.
  
  Solution:
  
  Wait and Retry: If the lock is temporary, waiting for a few moments and then retrying the operation may resolve the issue.
  Identify the Lock: Use transaction codes like SM12 (to view and manage locks) to identify which user or process is holding the lock on the document. You can then communicate with the user or check the process to see if it can be released.
  Check Background Jobs: If there are background jobs running, check their status and see if they can be stopped or if they are taking longer than expected.
  Transaction Monitoring: Use transaction codes like SM21 (system log) or ST22 (dump analysis) to check for any related errors or issues that might be causing the lock.
  Database Consistency Check: If the issue persists, consider running a database consistency check or consulting with your SAP Basis team to ensure that there are no underlying database issues.
  Contact SAP Support: If the problem cannot be resolved through the above steps, it may be necessary to contact SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12, SM21, ST22, and SE11 (for data dictionary) to help diagnose and resolve the issue.
  User Communication: If multiple users are working on the same document, ensure that there is clear communication to avoid conflicts.
  Documentation: Review SAP documentation or notes related to document locking and clearing processes for additional insights and best practices.
  
  By following these steps, you should be able to diagnose and resolve the EDEREG_INV686 error effectively.