There’s a lot to see in the latest release of SAP Integrated Business Planning (IBP) 1905. Here’s my comprehensive breakdown on the biggest changes and what they can do for your organization:
1) DDMRP – all phases. The last steps of Demand Driven Replenishment Planning have been added to IBP in this release. DDMRP is too broad to cover here but you can find out what it is and whether it may be right for you.
2) Driver Based Planning – Also new to IBP (sort of). Previously, if you wanted to keep track of risks and opportunities and rate them for possible inclusion in your forecast, you had to do this with a bunch of key figures, calculations and planning operators. SAP had built a web based application to record, rank and include/exclude in your demand plan.
Record your risks and opportunities
Maintain the details
Once you’ve elected to include in plan, the value will be stored in the chosen key figure that can then be part of your consensus planning.
3) Planning areas app – powerful key figure search. You can now search beyond name and description for key figures. For instance, you can search for key figures that are inputs to the supply planning algorithm. It can be sensitive to the words you use. Entering “Supply Input” will not return any results. Entering “Input for supply” will. Here is a screenshot of the help and the accompanying text for the search options.
You can search for the characteristics that are available in the Key Figures table, except for the content of the Key Figures, the Created On, and the Changed On columns. To see all the characteristics that are available for search, go to the Settings of the Key Figures table. The search works in every language that the user interface supports. You can use only one search term at once, you can’t combine multiple search terms.
In general, the search returns results in two ways:
It finds items that start with the search term in the columns that have either a predefined set of values, like Edit Allowed, or yes and no, like Planning Notes, as values.
It finds items that contain the search term in the rest of the columns, where the values are not predefined, like IDor Convert Using.
You can use the search in the following ways:
- Use the name of the characteristic to find out if the key figure is enabled for that characteristic, for example, planning note or change history.
- Use one of the predefined values of a certain characteristic, like Not Editable, to get a list of key figures with this value in the Edit Allowed column.
- If the values are represented by icons in the column, use the tooltip text.
- Use the specified value, for example, DAYWEIGHT, to see if any of the key figures use it as a period weight factor.
- If you want to combine search criteria, use filters on the table. If you provide the same filter more than once with different values, the search results you get contain either one value or the other. If you provide several different filters, the search returns key figures that meet all the criteria.
4) You can now use the IBP_CAGGRfunction to specify cumulative aggregation (such as projected stock, or year-to-date calculations). This one is pretty big. This opens up a wide range of options with key figures that, previously, were only possible through L-Script. For instance, you can now write your own projected stock and projected periods of coverage calculations! SAP plans to continue releasing functions like this in an effort to simplify key figure calculations. Here are some screenshots with explanations and examples for the cumulative aggregation function (a former colleague provided the below information which, I believe, came from a SAP workshop in Waldorf).
Today SAP IBP offers SUM, MIN, MAX, AVG aggregation modes on calculation level. A new function is introduced to realize cross period aggregations. It is named as IBP_CAGGR and has the following 5 parameters;
OUTPUTKF@OUTPUTPL = IBP_CAGGR ( “INPUTKF@INPUTPL” , ‘‘SUM’’ , ‘‘FORWARD’’ , ‘‘PASTCURRENT’’, 6 )
The first parameter is the input key figure. The modeling expert can configure the key figure to be aggregated to the output key figure taken from the any time period. This key figure must match to the input of the calculation definition (i.e. the key figure selected on the pop-up must be the same as in the expression). The input and the output planning levels must have the same root and non-root attributes. The input and the output planning level must have a time dimension root attribute. All other key figure and planning level related rules are valid.
The aggregation mode is the second parameter, with the following possible values: MIN, MAX, SUM, AVG. This parameter defines what sort of aggregation is in use, with other words what to do in relation to the output key figure coming from the any time period(s) and the input key figure.
The third parameter defines the direction of cumulative aggregation. It must be FORWARD or BACKWARD. The typical direction is FORWARD, but year-to-go calculations require to use BACKWARD aggregation.
The fourth parameter defines the calculation horizon. It must be set to one of the following values; PAST, CURRENT, FUTURE, PASTCURRENT, PASTCURRENTFUTURE and CURRENTFUTURE. When the modeling expert has decided about the design of the aggregated key figure (i.e.: if one key figure is used to show past, present and future values at the same line, or separate key figures are introduced for past and for present and future values) then this parameter can help to filter the data and this manner to improve runtime performance.
The fifth parameter is optional and defines when to restart the aggregation. The restart frequency can be configured by selecting a time profile level. At the change of the selected time profile level, the aggregation will restart from 0. It can be missed out when no restart is needed, otherwise it can have any values that represent a time profile level (that was configured in the time profile assigned to the planning area). It needs to be validated at check and activation time, if the restart parameter exists in the time profile. The configured time profile level must be either on the input or on the output planning level.
The result of the cumulative aggregation is written to the output key figure. It cannot be used to create a request level calculation.
A missing time period would disarrange the aggregation logic, therefore the missing buckets for all combinations have to be filled at integration with NULL values.
The parameters have a fixed order, they cannot be missed out and no default values are provided.
Cumulative aggregation simplifies the modeling of several key figure calculations. Some examples with the proposed use cases are listed below, however the use of this function is not restricted to any of the presented examples.
Cumulative aggregation with periodical restart
Cumulative aggregation with periodical restart using MAX aggregation method
Cumulative aggregation when time periods are missing
Year-to-date and year-to-go calculations
Projected stock calculation that goes below zero and carries over negative values
Projected stock calculation that does not go below zero (no values are carried over)
5) You can now configure recurrence for realignment project runs. The recurrent execution of realignment projects allows you to regularly adjust master data or key figure values as part of a business process. Prior to this release, realignment runs were created as projects and run once to realign the data. The problem with that is that data doesn’t always play nice. You might realign sales data only to have new pesky orders show up in prior months due to returns, interface changes that include or exclude new sales order types. Now you can set the job to rerun and sweep for any new or changed data.
6) You can now add different versions to your planning view in the Web-Based Planning. This allows you to work on multiple versions simultaneously. You can view and compare key figure data from different versions and make changes to this key figure data.
7) Forecast consumption mode consumption direction – forward/backward or forward only. Determines where the algorithm starts and finishes. This new feature gives you alittle more control over consumption logic. The big driver was customer requests to SAP to make IBP behave like APO did. They were comfortable with that logic and wanted to have it in IBP. The standard/default logic is left to right and right to left. That means the algorithm starts from the left and moves right with sales orders executing the consumption logic. It then starts righ and moves left. It will take the results and use the one that consumed the highest amount of forecast. APO is a left to right only algorithm. SAP has introduced left to right as an option. If you want to use this, you need to have the SALESORDERSEQUENCEID in you forecast consumption master data type.
8) A new check for the check mode algorithm that tells you how many isolated customer and location products you have, so you can locate and delete them.
While this may seem like quite a few new features, there are still many more enhancements that I haven’t even touched on… feel free to reach out or connect with me and I’d be happy to chat/message with you about those or any I’ve listed above.
I hope you were able to find some useful information that will help you on your IBP journey!