Do you have any question about this error?
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)
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.
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.
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.
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) orM/08
(for MM) to access the pricing procedure configuration.- Identify the pricing procedure that is being used for the transaction and check the steps defined in it.
Define Missing Subtotals:
- Ensure that all required subtotals are defined in the pricing procedure. You can do this by adding the necessary subtotal in the relevant step of the pricing procedure.
- Make sure that the subtotal is correctly assigned to the appropriate condition types.
Review Condition Types:
- Check the condition types that are being used in the transaction. Ensure that they are correctly configured and that they are set to generate the required subtotals.
- Verify that the condition types are active and correctly linked to the pricing procedure.
Testing:
- After making the necessary changes, test the pricing procedure again to ensure that the error is resolved.
Related Information:
Transaction Codes:
V/08
: Maintain Pricing Procedures (SD)M/08
: Maintain Pricing Procedures (MM)V/06
: Maintain Condition Types (SD)M/06
: Maintain Condition Types (MM)Documentation: Refer to SAP Help documentation for detailed information on pricing procedures and condition types.
SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
Support: If the issue persists after checking the configuration, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
By following these steps, you should be able to resolve the MN372 error and ensure that your pricing procedure is correctly configured.
Get instant SAP help. Start your 7-day free trial now.
MN371
No list output generated (internal error)
What causes this issue? Although &V1& rebate arrangements satisfy the selection criteria, no list output has been generated.System Response ...
MN370
PO history (invoice verification) has no tax code
What causes this issue? The purchase order history for purchasing document &V1&, item &V2&, for invoice verification document &V3...
MN373
Error importing calculation schema & (see long text)
What causes this issue? At least one error has occurred during the importing of calculation schema &V1&, usage &V2&, application &...
MN374
Condition type & not maintained in calculation schema &
What causes this issue? Condition type &V1& has not been entered in calculation schema &V2&, usage &V3&, application &V4&...
Click on this link to search all SAP messages.