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_BUDG_STATUS_ORDER |
| Short Description | Status Order of a Budget |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | BgStatOrd. |
| Medium | 15 | Budg.Stat.Ord. |
| Long | 20 | Budget Status Order |
| Heading | 10 | BgStatOrd. |
Documentation
Definition
In the standard system the status order represents the highest planning level that is 'primarily' responsible for the overall status of a budget.
The status order is determined by the default implementation of BAdI WRF_PPW_X_BG_STAT_E, method DET_BG_STAT_ORDER. The customer can influence the status order themselves by implementing their own BAdI.
Default Implementation of the Status Order
General logic for determining the status order
To determine the status order, the values of the planning levels are subtracted from the remaining budget successively and in descending order, that is, from planning level 3 to planning level 1. The status of each difference value is compared with the overall status of the budget. As soon as both statuses match, the current planning level used for the calculation defines the status order of the budget.
Special case - Overall budget status "ok"
If the overal budget status is "ok" (green traffic light), then in addition to the logic above, the system checks whether a price plan really exists in the relevant planning level. The planning level can only be used to determine the status order if there is a price plan. The status order is determined by the highest planning level in which there is a price plan. In the event that none of the price levels are assigned a price plan, the status order is given the value 'X'. This can happen, for example, at the start of a period when price plans have not yet been created for a budget. Another example, is if all price plans have already been activated and consequently do not correspond to any planning levels, but the overall budget status is still "ok".
Special case - Negative remaining budget
In the event that the remaining budget already has a negative value, the status order is given the value 'X' by default. This can, for example, occur when the exhausted budget from the previous period significantly exceeds the new budget value available for planning in the current period.
At this point, see the detailed documentation for the BAdI WRF_PPW_X_BG_STAT_E.
Use
Dependencies
In the standard system, the definition of the status order is directly linked to the definition of the budget status. This is determined by the BAdI WRF_PPW_X_BG_STAT_E, method DET_BG_INFO_STAT.
The status is determined according to the default implementation as follows:
If there is an absolute tolerance of XXX MU (monetary units) and an available budget of YYY MU, the overal budget status is:
1) "ok" (green traffic light), provided YYY >= 0MU
2) "ok with restrictions" (yellow traffic light), provided YYY < 0MU and 0MU < ABS(YYY) <= XXX
3) "Critical" (red traffic light) if YYY< 0 and 0 <= XXX < ABS(YYY)
Example
The following example is based on the determination of the status or status order delivered in the standard system (see above).
Status
If there is a fixed tolerance value of 10,000 MU (monetary units), then according to the default implementation, the following status rules apply to the available budget:
Overall budget status = "ok", provided available budget >= 0MU
Overall budget status = "ok with restrictions", provided -10,000MU <= available budget < 0MU
Overall budget status = "critical" if available budget < -10,000 MU
If there was an available budget of -60,000MU, the status would be "critical" and would be shown by a red traffic light.
Status order
We know there is an available budget of -60,000 MU (monetary units) with overall status "critical", if the fixed tolerance value is 10,000 MU. In addition:
Remaining budget = 100,000 MU
Total value planning level 3 = 80,000 MU
Total value planning level 2 = 50,000 MU
Total value planning level 1 = 30,000 MU
Procedure to determine status order
Step 1
Remaining budget - planning level 3 = 100,000 MU - 80,000 MU = 20,000 MU > 0 MU
=> Status (remaining budget - planning level 3) = "ok"
=> Status (remaining budget - planning level 3) <> overal status
=> Status order <> 3
Step 2
Remaining budget - planning level 3 - planning level 2
= 100,000 MU - 80,000 MU - 50,000MU
= - 30,000 MU < -10,000 MU
=> Status (remaining budget - planning level 3 - planning level 2) = "Critical"
=> Status (remaining budget - planning level 3 - planning level 2) = overall status
=> Status order = 2
History
| Last changed by/on | SAP | 20050411 |
| SAP Release Created in | 600 |
