Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
ML (Package) R/3 services management
Basic Data
| Data Element | COMMITMENT |
| Short Description | Expected Value of Overall Limit |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WERT7 | |
| Data Type | CURR | Currency field, stored as DEC |
| Length | 13 | |
| Decimal Places | 2 | |
| Output Length | 16 | |
| 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 | Exp. Value |
| Medium | 15 | Expected Value |
| Long | 20 | Expected Value |
| Heading | 16 | Expected Value |
Documentation
Definition
Value that the unplanned services (or the material) covered by this item are not expected to exceed.
Use
The expected value is included in the net price of the item. If the document contains services in addition to the limit, the expected value is totalled up with the overall value of the services to arrive at the net price. If the document contains only a limit, the expected value is the net price. In this case, specification of an expected value is mandatory. This guarantees that the net price of an item, especially a purchase order item, cannot amount to "0".
The expected value need not be equal to the value of the overall limit. In follow-on processes and documents, the expected value can be exceeded. In the process of cost control, though, you can use it for comparison with the overall limit.
Dependencies
- CO Controlling adopts the expected value in the commitment for the document.
- If you use the release (approval) procedure for purchasing documents, the expected value serves as the basis for the application of a release strategy.
- The expected value is included in the release order statistics for contracts.
Example
History
| Last changed by/on | SAP | 19980218 |
| SAP Release Created in |
