Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MG (Package) Application development R/3 material master prior to 3.0
Basic Data
| Data Element | DZPLPR |
| Short Description | Future planned price |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WERT11 | |
| Data Type | CURR | Currency field, stored as DEC |
| Length | 11 | |
| Decimal Places | 2 | |
| Output Length | 14 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | FUTURE_STANDARD_PRICE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Plnd price |
| Medium | 15 | Fut. plnd price |
| Long | 20 | Future planned price |
| Heading | 14 | Fut.plnd price |
Documentation
Definition
Price from a marked standard cost estimate.
Use
If you create and mark a standard cost estimate for the material, the results of this cost estimate are copied to this field.
Dependencies
If you later release the standard cost estimate for this material, the price entered here is updated as the current planned price and as the current standard price.
If you do not release the marked standard cost estimate, but create a new one for the material, you can remark the results. You can keep remarking the results until you release the cost estimate.
Note
If no marked standard cost estimate exists, you can enter a price in this field manually. This makes it possible for the system to find a price when costing an assembly via the valuation strategy, even if no standard cost estimate with status KA (correct) exists for a BOM material (such as a raw material or semifinished product).
If you subsequently create and flag a cost estimate for this material, the results of this cost estimate are adopted as the future planned price, and the manual entry overwritten. It can then no longer be changed. Therefore, you are recommended to use the Planned price 1, Planned price 2, and Planned price 3 fields to maintain the planned prices of material components and to define them in the valuation strategy.
History
| Last changed by/on | SAP | 20020124 |
| SAP Release Created in |
