Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MCE (Package) R/3 application development: Purchasing Information System
Basic Data
| Data Element | MC_BSPRS |
| Short Description | Purchase order price |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WERTV8 | |
| Data Type | CURR | Currency field, stored as DEC |
| Length | 15 | |
| Decimal Places | 2 | |
| Output Length | 21 | |
| 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 | PO price |
| Medium | 15 | PO price |
| Long | 19 | Purchase ord. price |
| Heading | 11 | P.O. price |
Documentation
Definition
The average order price is calculated from the quotients of the effective order value (value of the purchase order including discounts, <surcharge>surcharges. delivery costs, cash discounts) and amount of purchase order (amount of the ordered materials).
Use
In the standard system, the Purchasing Information System calculates key figure during the vendor, material group or material analysis. For this reason the key figure is not saved in any information structure.
The effective order value and the amount of the order are updated when a scheduling agreement is created and changed.
Dependencies
Note that the calculation of the order price can only occur on an aggregated level (for example for material groups or purchasing organizations) if values of the same currency and amounts are cumulated with the same unit.
History
| Last changed by/on | SAP | 20010221 |
| SAP Release Created in |
