How To Fix EPS536 - Desired change to payment scheme category is not possible (table TE638)

EPS536 - Overview

• Message type: E = Error

• Message class: EPS - Payment Scheme

• Message number: 536

• Message text: Desired change to payment scheme category is not possible (table TE638)

What causes this issue?

You want to change the category of a payment scheme. However, the change
you want to make cannot be executed. A possible reason for this can be
that the original payment has been classified as 'not modifiable' (field
<ZH>No PSCatCh</> is selected), or that lines cannot be generated for
the original payment scheme category in online mode (field
<ZH>NoReq.Onl.</> is selected) but they can be generated
for the new category.

System Response

Processing is terminated.

How to fix this error?

Select a valid payment scheme category.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

EPS536 - Details

• The SAP error message EPS536 indicates that there is an issue with changing the payment scheme category in the system, specifically related to the configuration in table TE638. This error typically arises when there is an attempt to modify a payment scheme that is not allowed due to existing constraints or settings in the system.
  
  Cause:
  
  Configuration Restrictions: The payment scheme category you are trying to change may have restrictions based on the current configuration in table TE638. This table defines the payment scheme categories and their associated settings.
  Existing Transactions: If there are existing transactions or documents that are already using the payment scheme, the system may prevent changes to ensure data integrity.
  Authorization Issues: The user may not have the necessary authorizations to make changes to the payment scheme category.
  Inconsistent Data: There may be inconsistencies in the data that prevent the change from being processed.
  
  
  Solution:
  
  Check Configuration: Review the configuration in table TE638