How To Fix MN372 - Subtotal missing in calculation schema &, step & (see long text)

MN372 - Overview

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 372

• Message text: Subtotal missing in calculation schema &, step & (see long text)

What causes this issue?

No valid subtotal could be determined for step &V2& of calculation
schema &V1&, usage &V3&, application &V4&.
To permit updating of the supplier business volume value with respect to
a condition record, a subtotal must be entered during maintenance of the
calculation schema. This entry must be made in the reference step "from"
to which the entry for the condition type for "subsequent settlement"
relates.

How can this happen?

Step Ctr. CTy. Description Fr. ... Subtotal
20 0 Net val. incl. disc. 7
37 1 A001 Volume rebate 20 ...
Line 37 relates to line 20 of the schema. You must enter a valid
subtotal in line 20 (e.g. 7 = transfer of value to KONP-BONBA). Further
permissible subtotals are the values 1 - 6, provided that these are not
already used elswhere.

System Response

Updating of the cumulative money supplier business volume cannot be
assured without the entry of a suitable subtotal.
The function you requested was either terminated or - if justifiable -
continued with incorrect data.
&WHAT_TO_DO& (system administrator)
Check calculation schema &V1&.

<DS:SIMG.SIMGCFMENUOLMEOMER5>Define calculation schema</>
ENDIF&

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN372 - Subtotal missing in calculation schema &, step & (see long text) ?

  The SAP error message MN372 indicates that there is a missing subtotal in the calculation schema for a specific step in the pricing procedure. This error typically occurs during the pricing determination process in sales and distribution (SD) or materials management (MM) when the system expects a subtotal to be defined but cannot find it.
  
  Cause:
  
  Missing Subtotal Definition: The most common cause of this error is that the subtotal required for the calculation schema is not defined in the pricing procedure.
  Incorrect Configuration: The pricing procedure may not be correctly configured to include the necessary subtotals for the specific condition types being used.
  Condition Type Issues: The condition types that are supposed to generate subtotals may not be properly assigned or activated in the pricing procedure.
  
  
  Solution:
  
  
  Check Pricing Procedure:
  
  Go to the transaction code V/08 (for SD) or M/08 (for MM) to access the pricing procedure configuration.
  Identify the pricing procedure that is being used for