Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 363
Message text: The condition basis is zero (please check update data)
Translation: In part identical to MN362
The
<DS:GLOS.3526C799AFAB52B9E10000009B38F974>condition basis</> of the
<DS:GLOS.3526C79FAFAB52B9E10000009B38F974>condition record</> that
results from the update of business volume data from the documents
(purchase orders, goods receipts, invoices, supplier billing documents,
settlement documents) is zero.
As the
<DS:GLOS.352A1FB41F085BF7E10000009B38F974>scale basis</> is not zero,
an error may have occurred in the updating of business volumes.
Possible causes:
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The volume, points score etc. are missing in the documents, in theThe system may determine incorrect update data (business volumes).
Check the business volume data that the system determines.
If this is not correct, check the documents concerned.
If there is an error here, the data updated for settlement in the
Logistics Information System is incorrect too.
Check the settlement accounting already performed.
If necessary, contact your system administrator.
The document concerned (price determination) has the number &V1&, item
&V2&. For the number of the document (update) please see the list
output.
The condition record has (internal) number &V3&.
Error message extract from SAP system. Copyright SAP SE.
MN363
- The condition basis is zero (please check update data) ?The SAP error message MN363, which states "The condition basis is zero (please check update data)," typically occurs in the context of pricing and condition records in SAP. This error indicates that the system is unable to determine a valid condition basis for a pricing condition, which means that the calculation for pricing cannot be completed.
Causes:
- Missing Condition Records: The condition records for the pricing procedure may not be maintained or are incomplete.
- Incorrect Condition Type: The condition type being used may not be set up correctly or may not be applicable for the transaction.
- Zero Value in Condition Basis: The condition basis (the value used to calculate the condition) is zero, which means that there is no valid data to calculate the pricing.
- Incorrect Master Data: Issues with master data (like customer master, material master, etc.) can lead to the absence of necessary condition records.
- Pricing Procedure Configuration: The pricing procedure may not be configured correctly, leading to the inability to derive the condition basis.
Solutions:
Check Condition Records:
- Go to transaction code
VK11
orVK12
to check if the condition records for the relevant condition type are maintained correctly.- Ensure that the condition records are valid for the specific combination of customer, material, and other relevant fields.
Review Pricing Procedure:
- Use transaction code
V/08
to review the pricing procedure and ensure that the condition types are correctly configured and assigned.- Check if the condition type is included in the pricing procedure and that it is set up to derive the condition basis correctly.
Validate Master Data:
- Check the customer and material master data to ensure that all necessary fields are filled out correctly and that there are no missing or incorrect entries.
Analyze the Sales Document:
- Review the sales document (like sales order or quotation) to ensure that all necessary data is entered and that there are no inconsistencies.
Debugging:
- If the issue persists, consider debugging the pricing procedure to identify where the condition basis is being set to zero. This may require technical expertise.
Consult Documentation:
- Refer to SAP documentation or consult with your SAP support team for specific guidance related to your configuration and setup.
Related Information:
VK11
/ VK12
- Create/Change Condition RecordsV/08
- Maintain Pricing ProceduresVA01
/ VA02
- Create/Change Sales OrdersBy following these steps, you should be able to identify the root cause of the MN363 error and implement the necessary corrections to resolve it.
Get instant SAP help. Start your 7-day free trial now.
MN362
The scale basis is zero (please check update data)
What causes this issue? Translation: In part identical to MN362 The <DS:GLOS.352A1FB41F085BF7E10000009B38F974>scale basis</> of the <D...
MN361
Purchasing documents already exist for a condition record
What causes this issue? Purchasing documents already exist for a condition record. When a purchase order is created, the system logs all transactions...
MN364
The scale basis is zero (please check update data)
What causes this issue? Translation: In part identical to MN362 The <DS:GLOS.352A1FB41F085BF7E10000009B38F974>scale basis</> of the <D...
MN365
The condition basis is zero (please check update data)
What causes this issue? The condition basis of the condition record in the statistics update data is zero. Since the scale basis is not zero, an erro...
Click on this link to search all SAP messages.