4/19/2022

SAP Integrated Business Planning for Supply Chain

Generated on: 2022-04-19 04:51:17 GMT+0000

SAP Integrated Business Planning for Supply Chain | 2202

PUBLIC

Original content: https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/feae3cea3cc549aaa9d9de7d363a83e6?

locale=en-US&state=PRODUCTION&version=2202

Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product documentation. The
information included in custom documentation may not reflect the arrangement of topics in the SAP Help Portal, and may be missing
important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

Setting Up Driver-Based Planning

Setting up driver-based planning involves making enhancements to your planning area, giving the right authorizations to the corresponding
business users, and creating planning views for the planners.

Enhancements to the Planning Area

We recommend that your configuration expert enhances your planning area with the required model entities that are used for driver-based
planning, which are specific master data types, planning levels, and key figures. The relevant model entities are available in the SAPIBP1
sample planning area. Note that they are specifically designed for managing risks and opportunities. For a list of the model entities and
additional details, see Model Entities for Driver-Based Planning.

After the required model entities have been added to your planning area, your configuration expert or administrator needs to load master data
for the master data types and any check master data types. For example, master data types such as Product and Customer and check master
data types like Risk/Opp Type. This can either be done using the IBP Excel add-in or the Data Integration Jobs app. Only if master data has
been uploaded for these master data types can planners select this data from the value help for the attributes of the driver type or of the
planning level attributes in the driver-planning view.

Creating Your Own Master Data Types for Driver-Based Planning

Please note the following when you create your own master data types:

You can only select master data types that have a single key attribute.
The key attribute and the required attributes of the master data type can only be of type NVARCHAR, INTEGER, or DECIMAL. You
cannot use attributes of type TIMESTAMP as key attribute or as required attributes.
The optional attributes of a master data type can be of type NVARCHAR, INTEGER, DECIMAL, or TIMESTAMP. However, note
that for attributes with timestamp data, planners can only select the date for the timestamp. The time cannot be selected. If the attribute
value is maintained in the Driver-Based Planning app, the time is shown as 00:00:00.000 in UTC by default. An exact time can only be
added if the attribute value is maintained outside of the Driver-Based Planning app. For example, if it is maintained using data
integration or master data maintenance in the IBP Excel add-in.

Authorizations
Driver-Based Planning App

To make the Driver-Based Planning app available on the launchpad, you need to assign the SAP_IBP_BC_DBP_PC business catalog to the
relevant business user role in the Manage Business User Roles app.

Creating Driver Planning Views and Drivers

You can allow users to create driver planning views and drivers by enabling the corresponding functionality for the user’s role. The following
checkboxes need to be selected in the Administration Functions restriction field of the General restriction area:

For creating driver planning views: DPBVIEWS (Driver Planning View)

For creating drivers: DPBOBJ (Driver)

We recommend that you give the write authorization to create driver planning views only to users who are responsible for planning views.

Creating, Deleting, and Editing Planning Objects

This is custom documentation. For more information, please visit the SAP Help Portal 1
 4/19/2022
You can flexibly define if users can create, delete, or edit planning objects for drivers. This is useful if you want to enable only certain
activities for users. For example, you can define that users can create planning objects but not delete them.

You enable the corresponding functionality for the user’s business role. The following checkboxes need to be selected in the Planning Object
Operation Type restriction field of the General restriction area:

For creating and copying drivers: CREATE (Create)

For deleting drivers: DELETE (Delete)

For editing drivers: CREATE (Create) and DELETE (Delete)

If any of the functions is disabled in the restriction type, users will be notified by a message in the Driver-Based Planning app.

Setting this restriction is optional.

Dynamic Selection of Attribute Values

By default, 100,000 attribute values are displayed in the value help. If there are more than 100,000 values for a master data attribute, then
users can search for the attribute value they’re looking for and the system will read those values dynamically from the database. You have the
option to restrict the number of attribute values that are read. This can decrease the loading time and can therefore help improve
performance. You can define how many attribute values the system reads using the MAX_DIM_MEMBERS global configuration parameter
in the PLAN_VIEW parameter group.

For more information, see Dynamic Selection of Values of Master Data Attributes.

Creating Planning Views for Planners

The users in your organization who take care of planning views can create planning views in the Driver-Based Planning app and share those
views with individual planners or groups of planners. This way planners who create drivers can work with specific driver planning views that
are centrally created and managed.

Recommendations and Important Things to Note

Keep the following in mind when you set up driver-based planning and create driver-planning views:

Important Things to Note

Driver Types

You can only select driver types that are single-key master data types.

Key Figures

Time profile level and base planning level: When you select a key figure for the driver planning view, make sure that the lowest
time profile level of the key figure’s base planning level is equal to or smaller than the time period you choose for the driver
planning view. In addition, the key figure’s base planning level must include the time period of the driver planning level.

For example, you can select a key figure with technical weeks as the lowest time profile level if your driver planning view uses
monthly time periods, as long as the time profile of the key figure’s base planning level also contains a monthly time profile
level. However, you cannot choose a key figure that has a monthly time profile level as the lowest time profile level if your
driver planning view uses technical weeks as time periods.

Key figure properties: You can use stored editable key figures and calculated key figures. The base planning level of the key
figure you select for the planning view must include the attributes of the driver master data type and the planning level.

Adding Key Figures to an Existing Driver Planning View: If you add additional key figures with a different base planning level
to an existing driver planning view, planners need to create a new driver first before they can edit the value of the new key
figure. This creates the planning objects that are required for linking the value of the new key figure with the driver.

Replacing a Driver

When a planner replaces a driver, the system deletes the driver and completely recreates it including the planner’s changes.

Caution

The replace function is not a delta edit function. When a planner replaces a driver, only the data for the driver that is visible to them in
the object view and that they have write permission for is actually saved. Any data (related master data, planning objects, or key figure
data) that exists for the driver in the system but that is not visible to the user is deleted. Any related data is also deleted from all
versions. Planners should use the Replace function with caution.

If planners want to change attributes or key figure data for a driver, we recommend that they change this data in the summary view.

Effects of Filters when Replacing a Driver

This is custom documentation. For more information, please visit the SAP Help Portal 2
 4/19/2022
When a planner changes the default planning filter for a driver planning view and replaces a driver, any attribute values that belong to
the driver but are not visible to the planner because of the applied filter are deleted. This means that planners can accidentally delete
more data than they intended. Please make users aware of the effects that changing a planning filter before replacing a driver may
have.

For the same reason, make sure that the planners you share the driver planning view with have the same permission filters assigned to
their user.

For an example, see the information for planners under Driver-Based Planning

Recommendation for Key Figures

We recommend that you select key figures for the driver planning view with a base planning level that is close to the planning level attributes
that you have selected for the driver planning view. Otherwise, the system needs to create a large amount of planning objects for the driver at
the key figure’s base planning level. This can affect performance.

Example

If the driver planning view has the planning level attributes PRDFAM – CUSTREG, we recommend that you select a key figure whose base
planning level is at the same or a lower level, like PRDSUBFAM – CUSTGRP. However, it is not recommended to select a more granular
planning level such as PRD – CUST, because the more granular the planning level, the more planning objects the system needs to create for
the planning level.

For more information, see Limitation of Planning Objects for Drivers.

For an example of model entities for driver-based planning in SAPIBP1, see Model Entities for Driver-Based Planning.

Note that there are also some restrictions that planners should keep in mind when working with the app. For more information, see Driver-
Based Planning.

Model Entities for Driver-Based Planning

You can use the SAPIBP1 sample planning area as a starting point for your implementation of driver-based planning.

The SAPIBP1 sample planning area contains a sample configuration that you can adapt to create your own driver-based planning project for
risks and opportunities. The following master data types, attributes, planning levels, and key figures are available:

Master Data Types

The following table lists the master data types that are used for driver-based planning:

Master Data Type ID Usage Settings

IBPRISKOPP This master data type represents the driver Master data type: Simple
that can influence your supply chain plan, in
this case, a risk or an opportunity. Key: ROPID
IBPROPTYPE Represents the type of driver, in this case, Master data type: Simple
risks or opportunities.
Key: ROPTYPEID
IBPPRIORITY Represents the priority of the driver, for Master data type: Simple
example high, medium, or low.
Key: PRIORITYID
IBPASSUMPTIONCATEGORY Represents the assumption category for the Master data type: Simple
driver, for example, competition, market
growth, weather, or others. Key: ASSUMPTIONCATID

Attributes of master data type IBPRISKOPP:

Attribute ID Attribute Key Required Data Type Referenced Attribute Comment

Description (X) (X) (Length)
ROPID Risk/Opp ID X X NVARCHAR(20) ID of your risk or opportunity.
ROPDESCR Risk/Opportunity X NVARCHAR(150) Description of your risk or
Descr opportunity.
ROPTYPEID Risk/Opp Type X NVARCHAR(20) ROPTYPE Type of your driver. For
example, risk or opportunity.
PRIORITYID Priority ID NVARCHAR(20) PRIORITY You can use this attribute to
specify how you want to
prioritize the risk or opportunity.
For example, high, medium, or
low.

This is custom documentation. For more information, please visit the SAP Help Portal 3
 4/19/2022
Attribute ID Attribute Key Required Data Type Referenced Attribute Comment
Description (X) (X) (Length)
ASSUMPTIONCATID Assumption NVARCHAR(20) ASSUMPTIONCATEGORYID You can assign an assumption
Category ID category for your risk or
opportunity. Values for this
attribute can be defined in the
IBPASSUMPTIONCATEGORY
master data type. Possible
values are competition, market
growth, weather, or others.
PLANNINGCYCLE Planning Cycle NVARCHAR(60) You can specify a planning
cycle for which the driver is
applicable, for example, “March
2019” or “S&OP Process April
2019”.
BUDGETED Budgeted Y/N NVARCHAR(10) With the value Y (Yes) or N
(No) you can specify if the risk
or opportunity is budgeted. For
example, the opportunity of
launching a new product may
require a marketing campaign
for which the costs need to be
budgeted and approved. If the
budget is approved, you can
enter Y here.
INCLUDEINPLAN Include in Plan INTEGER You can use this attribute to
mark the risk or opportunity that
affects your planning results as
relevant for the supply chain
plan.

In the SAPIBP1 sample

planning area, this attribute is
used in the key figure
calculation for the
CONSENSUSCALCROQTY
key figure, which enables you to
see the effect of the included
risks and opportunities to your
consensus demand plan.

Attributes of master data type IBPROPTYPE:

Attribute ID Attribute Description Key (X) Required (X) Data Type (Length)
ROPTYPEID Risk/Opp Type X X NVARCHAR(20)
ROPTYPEDESCR Risk/Opp Type Descr NVARCHAR(20)

Attributes of master data type IBPPRIORITY:

Attribute ID Attribute Description Key (X) Required (X) Data Type (Length)
PRIORITYID Priority ID X X NVARCHAR(20)
PRIORITYDESCR Priority Desc NVARCHAR(20)

Attributes of master data type IBPASSUMPTIONCATEGORY:

Attribute ID Attribute Description Key (X) Required (X) Data Type (Length)
ASSUMPTIONCATID Assumption Category ID X X NVARCHAR(20)
ASSUMPTIONCATDESCR Assumption Category NVARCHAR(60)

Planning Levels
The following table lists the planning levels that are delivered for driver-based planning:

Planning Level Description Comment

MTHPRODLOCCUST Monthly | Product | Location | Customer Planning level at which the Consensus
Demand Plan Qty key figure is defined.
MTHRO Month | RiskOpp -
MTHROPRDFAMCUSTREG Agg Level: Month | RiskOpp | Product Family -
| Customer Region
WKROPRODLOCCUST Weekly | RiskOpp | Product | Location | -
Customer
This is custom documentation. For more information, please visit the SAP Help Portal 4
 4/19/2022

Key Figures
The following table lists the key figures that are delivered for driver-based planning:

Key Figure Type Base Planning Level Comment

ROAGGSLSQTY (RO Agg Sales Stored key figure MTHROPRDFAMCUSTREG This is the key figure for which
Quantity) you enter the value for the risk or
opportunity in the Driver-Based
Planning app.
ROCALCSALESQTY (RO Calc Calculated key figure WKROPRODLOCCUST Used to view the impact of each
Sales Qty) risk or opportunity at the level of
the Consensus Demand Qty key
figure. This key figure uses a split
factor calculation to calculate the
ROAGGSLSQTY key figure at
the MTHROPRODLOCCUST
planning level.
CONSENSUSCALCROQTY Calculated key figure WKPRODLOCCUST Shows the Consensus Demand
(Consensus Demand Qty with Qty key figure considering risks
RiskOpp) and opportunities that are included
in the plan.

This is custom documentation. For more information, please visit the SAP Help Portal 5