Hierarchy
EA-RETAIL (Software Component) SAP Enterprise Extension Retail⤷
LO-MD-PPW (Application Component) Price Planning Workbench⤷
WRF_PPW_CUST (Package) Price Planning Workbench - Customizing
IMG Activity
| ID | W_PPW_BADI_0009 | Define Budget Status for Budgets in the Budget Monitor in the PPW |
| Transaction Code | S_AEN_10000213 | (empty) |
| Created on | 20041222 | |
| Customizing Attributes | W_PPW_BADI | BAdI Enhancements (PPW) |
| Customizing Activity | W_PPW_BADI_0009 | Define Budget Status for Budgets in the Budget Monitor in the PPW |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | WRF_PPW_X_BG_STAT_E |
Use
You can use this BAdI to set the:
1) Overall budget status in the budget monitor overview using BAdI method DET_BG_INFO_STAT
2) Status of the differences between the remaining budget and the planning levels using BAdI method DET_BG_DET_SUM_STAT
3) Order of the individual budget statuses using BAdI method DET_BG_STAT_ORDER
The budget status is indicated by a traffic light icon both in the budget overview and in the detailed view.
There is a default implementation of the BAdI for all three methods.
Requirements
Standard settings
In the standard system, a tolerance-dependent definition of the budget status or status order is implemented and the definition of the status order is directly related to the definition of the budget status.
The implementations are subject to the following logic:
Status
If there is an absolute tolerance of XXX MU (monetary units) and a budget of YYY MU currently available, the overall 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)
Status order
In the standard system, the status order represents the highest planning level that is 'primarily' responsible for the status of a budget. (See below for an example)
General logic for determining the status order (default implementation of the BAdI)
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.
Activities
Example
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 therefore 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 there is a fixed tolerance value of 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) <> overall 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
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20050425 |
| SAP Release Created in | 600 |
