Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 249
Message text: Cond. record and statistics data record contain different points units
Only a single points unit is defined in the R/3 System. However, the
system has come up against a condition record with the unit &V1& and a
statistics data record with the unit &V2&.
The error occurred in function module &V3&. This may have been called
up with inadmissible data. The condition record concerned is &V4&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Contact your system administrator.
Error message extract from SAP system. Copyright SAP SE.
MN249
- Cond. record and statistics data record contain different points units ?The SAP error message MN249 indicates that there is a mismatch between the units of measure in the condition record and the statistics data record for a material. This typically occurs in the context of pricing and inventory management, where the system expects consistent units of measure for calculations and reporting.
Cause: Unit of Measure Mismatch: The most common cause of this error is that the condition record (which may pertain to pricing, discounts, etc.) is defined in one unit of measure (e.g., kilograms), while the statistics data record (which tracks inventory or sales data) is defined in another unit of measure (e.g., grams).
Configuration Issues: There may be configuration issues in the material master or pricing conditions that lead to this inconsistency. Data Entry Errors: Manual data entry errors can also lead to discrepancies in the units of measure.
Solution: Check Condition Records: Go to the transaction code VK13 (Display Condition) to check the condition
Get instant SAP help. Sign up for our Free Essentials Plan.
MN248
Business volume data not available for all condition records
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN247
Acct. key for provisions missing for cond. type &, settlement schema &
What causes this issue? For settlement accounting in respect of rebate arrangement &V3&, provisions for accrued income have to be dissolved (...
MN250
No supplier business volume data available for this condition record
What causes this issue? No cumulative business volume exists for the condition record processed by you as at the current date. This means no invoice ...
MN251
Condition basis cannot be projected to higher scale levels
What causes this issue? To forecast rebate income at higher scale levels, the program must project the condition basis from the existing actual value...
Click on this link to search all SAP messages.