SAP ABAP Data Element WRF_PPW_BUDGET_VP (Planned Budget for an Item in Price Planning)
Hierarchy
EA-RETAIL (Software Component) SAP Enterprise Extension Retail
   LO-MD-PPW (Application Component) Price Planning Workbench
     WRF_PPW_DDIC (Package) Price Planning Workbench - DDIC
Basic Data
Data Element WRF_PPW_BUDGET_VP
Short Description Planned Budget for an Item in Price Planning  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type WRF_PPW_BUDGET    
Data Type CURR   Currency field, stored as DEC 
Length 13    
Decimal Places 2    
Output Length 17    
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 Plan.Budg. 
Medium 15 Planned Budget 
Long 20 Planned Budget 
Heading 10 Plan.Budg. 
Documentation

Definition

Budget value for a budget key that comes from the price planning data of a planning item.

Use

The committed budget for a price planning item can be displayed in the work area of the Price Planning Workbench. The committed budget is calculated in aggregated form for article items and in detail for the underlying organizational levels.

When postprocessing a promotion price plan, the committed budget is calculated on the basis of the changes to the planning parameters compared with the values at the time of activation.

Dependencies

When aggregating the committed budget for the price planning items, a distinction has to be made between "normal" price planning and postprocessing. In normal price planning, the sum of the committed budget for the price plan items for each budget key gives the total committed budget for a price plan. When postprocessing promotion price plans, the sum of the committed budget for the postprocessed price plan items gives the total budget for a price plan that has been committed through postprocessing.

Example

History
Last changed by/on SAP  20050411 
SAP Release Created in 111