How To Fix RQ219 - Customizing error in intermediate accounts

RQ219 - Overview

• Message type: E = Error

• Message class: RQ - Messages for Cash Management and Forecast

• Message number: 219

• Message text: Customizing error in intermediate accounts

What causes this issue?

The program is caught in an endless loop. Presumably an interim account
has been wrongly maintained in view V_T018C.
Example:
Bank account 4711 has interim account 4712.
Bank account 4712 has interim account 4711.

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?

Check all the accounts in grouping &V1& (view V_T038), then go to view
V_T018C and correct any interim account(s) which is/are wrongly set.

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 RQ219 - Customizing error in intermediate accounts ?

  The SAP error message RQ219, which indicates a "Customizing error in intermediate accounts," typically arises in the context of the SAP system's configuration for financial accounting, particularly when dealing with account determination for various transactions. This error can occur in scenarios such as invoice processing, payment processing, or during the execution of certain financial transactions.
  
  Cause:
  The error is usually caused by one of the following issues:
  
  Missing Configuration: The intermediate accounts (such as clearing accounts or suspense accounts) required for the transaction are not properly configured in the system.
  Incorrect Account Assignment: The account determination settings may not be correctly assigned to the relevant transaction types or document types.
  Inconsistent Data: There may be inconsistencies in the master data or transaction data that lead to the system being unable to determine the correct accounts.
  Missing or Incorrect Account Groups: The account groups associated with the relevant transaction may not be set up correctly.
  
  
  Solution:
  To resolve the