How To Fix WRMA_FI032 - Condition type &1 in schema &2 differs from FI update cond. type &3

WRMA_FI032 - Overview

• Message type: E = Error

• Message class: WRMA_FI - Messages for RMA

• Message number: 032

• Message text: Condition type &1 in schema &2 differs from FI update cond. type &3

What causes this issue?

Condition type &V1& in calculation schema &V2& does not agree with FI
update condition type &V3&.

You have to flag the non-statistical condition types in the calculation
schema as FI update condition types in Customizing. However, you only
flag one condition type as an FI update condition type for each
condition meaning.

System Response

Processing is canceled.

How to fix this error?

Correct calculation schema &V2&.

<DS:SIMG.SIMG_CFMENUOLMEOMER5>Define Calculation Schema</>

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.

WRMA_FI032 - Details

• The SAP error message:
  WRMA_FI032 Condition type &1 in schema &2 differs from FI update cond. type &3
  typically occurs during the pricing or billing process, especially when integrating SD (Sales and Distribution) with FI (Financial Accounting). It indicates a mismatch between the condition type defined in the pricing procedure/schema and the condition type expected or configured for FI update.
  
  Cause
  
  The condition type used in the pricing procedure (schema &2) is different from the condition type assigned for FI update (&3).
  This mismatch means that the system cannot correctly post the accounting document because the condition type in the pricing procedure does not correspond to the condition type expected in FI.
  Usually, this happens when:
  The condition type in the pricing procedure is not maintained or incorrectly maintained in the FI condition type configuration.
  The condition type used in the pricing procedure is not assigned to the correct account key or posting key.
  There is inconsistency between SD