How To Fix VVSCSOLL136 - Clearing restriction U lifted for the following amount:

VVSCSOLL136 - Overview

• Message type: E = Error

• Message class: VVSCSOLL - Debit Entry as Part of Payment Plan

• Message number: 136

• Message text: Clearing restriction U lifted for the following amount:

What causes this issue?

An incoming payment was made, and then offset with target premiums, on
a contract that was flagged with the 'Reserve and record payment on
account' indicator. As the incoming payment amount exceeded the target
premiums, a remaining credit was set.

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?

To offset the remaining credit, delete the clearing restriction U.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VVSCSOLL136 - Clearing restriction U lifted for the following amount: ?

  The SAP error message VVSCSOLL136, which indicates "Clearing restriction U lifted for the following amount," typically relates to issues in the clearing process of financial transactions. This error can occur in various contexts, such as during the clearing of accounts receivable or accounts payable.
  
  Cause:
  
  
  Clearing Restrictions: The error suggests that there is a restriction on clearing transactions, which may be due to various reasons such as:
  
  The amount being cleared exceeds the allowed limit.
  The transaction is not eligible for clearing due to its status (e.g., blocked, not fully posted).
  There are open items that need to be addressed before clearing can occur.
  
  
  
  
  Configuration Issues: There may be configuration settings in the SAP system that restrict certain types of transactions from being cleared.
  
  
  Data Integrity Issues: There could be inconsistencies in the data, such as missing or incorrect entries that prevent the clearing process.
  
  
  
  Solution:
  
  
  Review Transaction Details: Check the specific transaction that is causing the error. Ensure