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

SAP Error Message - Details

• 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.

Smart SAP Assistant

• What is the cause and solution for SAP error message WRMA_FI032 - Condition type &1 in schema &2 differs from FI update cond. type &3 ?

  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 pricing condition types and FI condition types.
  
  
  
  
  Solution
  
  
  Check the Pricing Procedure:
  
  Go to transaction V/08 (Pricing Procedure) and verify the condition types used.
  Identify the condition type &1 mentioned in the error.
  
  
  
  Check FI Condition Type Configuration:
  
  Use transaction OBQ1 to check the FI condition types.
  Verify the condition type &3 mentioned in the error message.
  Ensure that the condition type &1 in the pricing procedure corresponds to the FI condition type &3.
  
  
  
  Maintain or Correct the Condition Type Mapping:
  
  In transaction V/06 (Assign Condition Types to Account Keys), check if the condition type &1 is assigned to the correct account key.
  In transaction OBQ2 (Assign Account Keys to G/L Accounts), verify the account key mapping.
  Ensure that the condition type &1 in SD is correctly linked to the FI condition type &3.
  
  
  
  Adjust the Pricing Procedure or FI Configuration:
  
  If the condition type in the pricing procedure is incorrect, replace it with the correct one.
  If the FI condition type is incorrect or missing, create or adjust it to match the pricing condition type.
  
  
  
  Check for Customizing Inconsistencies:
  
  Sometimes, custom condition types or custom schemas cause this error if not properly maintained.
  Review any custom developments or user exits that might affect condition types.
  
  
  
  Test the Billing Document:
  
  After corrections, try to create or post the billing document again to verify the error is resolved.
  
  
  
  
  Related Information
  
  
  Transactions:
  
  V/08 – Pricing Procedure
  V/06 – Assign Condition Types to Account Keys
  OBQ1 – FI Condition Types
  OBQ2 – Assign Account Keys to G/L Accounts
  
  
  
  Notes and SAP Help:
  
  Check SAP Notes related to FI update and pricing condition types.
  Refer to SAP SD-FI integration documentation for condition type mapping.
  
  
  
  Common Scenario:
  
  This error often appears when a new condition type is introduced in SD but not properly configured in FI.
  Also common when migrating or copying pricing procedures without adjusting FI condition types.
  
  
  
  
  If you provide the exact values of &1, &2, and &3, I can help you with more specific guidance.