How To Fix FVD_DEBTTR030 - Payment splitting data is defined for the loan

FVD_DEBTTR030 - Overview

• Message type: E = Error

• Message class: FVD_DEBTTR - Borrower Change Without Capital Transfer

• Message number: 030

• Message text: Payment splitting data is defined for the loan

What causes this issue?

Payment splitting data is defined for the loan. Within this data, the
system deletes the entries for the main borrower, with the exception of
value-date adjustment. Depending on whether the <ZK>Keep Alternative
Payer</> indicator is set, the system deletes the payment splitting
data completely.

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 whether the payment splitting data is needed for anything other
than the automatic conversion.

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 FVD_DEBTTR030 - Payment splitting data is defined for the loan ?

  The SAP error message FVD_DEBTTR030 indicates that payment splitting data is defined for a loan, which typically means that the system is expecting a specific payment distribution across different components of the loan (such as principal, interest, fees, etc.) but is encountering an issue when processing a payment.
  
  Cause:
  
  Payment Splitting Configuration: The payment splitting data may not be correctly configured in the system. This could be due to missing or incorrect entries in the payment splitting settings for the loan.
  Payment Amount: The payment amount being processed may not align with the expected distribution defined in the payment splitting data.
  Loan Status: The loan may be in a status that does not allow for payment processing, such as being closed or in a non-active state.
  Data Inconsistency: There may be inconsistencies in the data related to the loan or the payment that is being processed.
  
  
  Solution:
  
  
  Check Payment Splitting Configuration:
  
  Navigate to the payment splitting configuration in