Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MB (Package) Application development R/3 inventory management
Basic Data
| Data Element | MB_NO045 |
| Short Description | No error messages for unrealistic total values |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Without045 |
| Medium | 15 | Without 045 |
| Long | 36 | No error messages of type 045 |
| Heading | 33 | No error messages of type 045 |
Documentation
Definition
Using the "No Unrealistic Prices" checkbox, you can deactivate error message 045, "Unrealistic Total Value".
Use
Error 045 is displayed if the actual price (total value divided by total quantity) differs slightly from the standard price. When you post a quantity that is smaller than the price unit, the actual price changes due to rounding errors.
Since this error message occurs because of rounding differences and may not be critical, you have the option of deactivating it in order to improve the overview in the output list.
If you want to remove these discrepancies, you must re-calculate the material value from the quantity and the price. To do so, proceed as follows:
1. Note the current price of the material in question:
2. In transaction MR21, post a price change for the material. For example, you can increase the price by 1.
3. Then post a second price change with MR21 to recreate the original price.
For more information on error message 045 and a correction example, see SAP Note 1026379.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in | 606 |
