0% found this document useful (0 votes)
2K views311 pages

IBP - Help For Standard Keyfigures PDF

The document summarizes changes made in SAPIBP1 Planning Model Template in SAP IBP 2002. Key changes include adding new attributes for inventory optimization, migrating disaggregation operators to new copy operator profiles, adding a key figure for customer forecasting via web-based planning, and changes to align planning levels for inventory optimization attributes. Change point detection was also added to forecast automation profiles.

Uploaded by

Saurabh Kulkarni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2K views311 pages

IBP - Help For Standard Keyfigures PDF

The document summarizes changes made in SAPIBP1 Planning Model Template in SAP IBP 2002. Key changes include adding new attributes for inventory optimization, migrating disaggregation operators to new copy operator profiles, adding a key figure for customer forecasting via web-based planning, and changes to align planning levels for inventory optimization attributes. Change point detection was also added to forecast automation profiles.

Uploaded by

Saurabh Kulkarni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 311

SAP Integrated Business Planning 2002

IBP 2002 for Cross Topics:


SAPIBP1 Planning Model Template

PUBLIC
Agenda

• SAPIBP1: What's new in 2002

• SAPIBP1: General Remarks

• SAPIBP1: Key Figure Overview

• SAPIBP1: Master Data Type Overview

• SAPIBP1: Planning Level Overview

• SAPIBP1: General Planning Area Settings

• SAPIBP1: Changes in earlier releases

2
2002 Summary of Changes in SAPIBP1

• Change of master data type Production Source Validity

• New attributes Transportation Lot Size Periods of Coverage (TLOTSIZECOVERAGE) and


Production Lot Size Periods of Coverage (PLOTSIZECOVERAGE) for Inventory Optimization

• New attribute Non-Stocking Allocation Horizon (NONSTOCKALLOCATIONHORIZON) for


Inventory Optimization

• New attribute IO Network ID (NETWORKID) for Inventory Optimization

• Removal of key figure Demand Value (node) (NODEDEMANDVAL) from Inventory Optimization

• Added Change Point Detection to the Forecast Automation Profile

• New key figure Customer Forecast (CUSTOMERFORECAST) for customer collaboration via
Web-based Planning

3
2002 Summary of Changes in SAPIBP1

• Align Planning Levels with regards to IO attributes Stocking Node Type Indicator
(STOCKINGNODETYPE), Service Level Type Indicator (SERVICELEVELTYPE), Distribution
Type (G or N) (DISTRIBUTIONTYPE)

• Migrate Disaggregation operators to new Copy Operator Profiles

• New key figure Demand Sensing: Weeks to Exclude from Learning


(SENSEDDEMANDEXCLUDE) for Demand Sensing

• When copying the unified planning area (SAPIBP1) using the create new with dependencies
option, it‘s possible to select the Copy Analytics and Alerts option to copy sample analytics and
alerts.

• Change various supply key figures to "Output for Supply Planning"

• Change supply key figure Adjusted Production Receipts (ADJUSTEDPRODUCTION)

• Change supply Key figure Production Receipts (PRODUCTION)


4
Change of master data type Production Source Validity

Reason for Change:


-Removed PRDID and LOCID from SOURCEPRODUCTIONVALIDITY : Remove unnecessary
attributes from Production Source Validity.

5
Changes related to New attributes Transportation Lot Size Periods of
Coverage (TLOTSIZECOVERAGE) and Production Lot Size Periods of
Coverage (PLOTSIZECOVERAGE) for Inventory Optimization
Reason for Change:
PLOTSIZECOVERAGE is the weeks of production lot size coverage for PBR.
TLOTSIZECOVERAGE is the weeks of transportation lot size coverage for PBR

New Attributes : PLOTSIZECOVERAGE and TLOTSIZECOVERAGE


Assignment to MDT :
• Assign PLOTSIZECOVERAGE to MDT SOURCEPRODUCTION
• Assign TLOTSIZECOVERAGE to MDT SOURCELOCATION
Assign the above two attributes to Planning Area as Attribute as Key Figures
Create new Key Figures: PLOTSIZECOVERAGE and TLOTSIZECOVERAGE

6
Changes related to New attribute Non-Stocking Allocation Horizon
(NONSTOCKALLOCATIONHORIZON) and NETWORKID for Inventory
Optimization
Reason for Change:
• NONSTOCKALLOCATIONHORIZON is the number of periods (weeks) used to allocate lot
size inputs from a non-stocking node to multiple nodes downstream.
• NETWORKID is an output attribute of the multistage operator that shows which product-
locations are in the same network (linked by sourcing or bill of materials)

New Attribute : NONSTOCKALLOCATIONHORIZON


Assignment to MDT : Assign NONSTOCKALLOCATIONHORIZON to MDT LOCATIONPRODUCT
Assign attributes NONSTOCKALLOCATIONHORIZON and NETWORKID to Planning Area

7
Changes related to New attribute Non-Stocking Allocation Horizon
(NONSTOCKALLOCATIONHORIZON) and NETWORKID for Inventory
Optimization
Assign Attributes NONSTOCKALLOCATIONHORIZON and NETWORKID to the following
Planning Levels
CALWKPRODLOCCUST WKPRODLOCCUSTGROUP
CALWKPRODLOCCUSTGROUP WKPRODLOCCUSTGROUP2
CALWKPRODLOCCUSTGROUPLAG WKPRODLOCCUSTGROUP3
CALWKPRODLOCCUSTLAG WKPRODLOCCUSTGROUPLAG
CALWKPRODLOCCUSTUOMTO WKPRODLOCCUSTGROUPLAGUOMTO
DAYDELIVERY WKPRODLOCCUSTGROUPUOMTO
DAYDELIVERYUOMTO WKPRODLOCCUSTLAG
DAYPRODLOC WKPRODLOCCUSTLAGUOMTO
DAYPRODLOCCUST WKPRODLOCCUSTUOMTO
DAYPRODLOCCUSTUOMTO
WKPRODLOCLOCFR
DAYPRODLOCLOCFR
DAYPRODLOCNOUOMTO
WKPRODLOCLOCFRCURR
DAYPRODLOCUOMTO WKPRODLOCLOCFRCURRCURRTO
PRODCUSTLOC WKPRODLOCLOCFRUOMTO
PRODLOCCUSTGROUP WKPRODLOCNOCURRCURRTO
PRODLOCCUSTGROUPLAG WKPRODLOCNOUOMTO
WKPRODLOC WKPRODLOCSRC
WKPRODLOCCOMPSRC WKPRODLOCSRCUOMTO
WKPRODLOCCOMPSRCUOMTO WKPRODLOCUOMTO
WKPRODLOCCURR WKROPRODLOCCUST
WKPRODLOCCURRCURRTO MTHPRODLOCCUSTLAG
WKPRODLOCCURRCURRTOUOMTO MTHPRODLOCCUSTLAGUOMTO
WKPRODLOCCUST
WKPRODLOCCUSTCURR
WKPRODLOCCUSTCURRCURRTO 8
WKPRODLOCCUSTCURRCURRTOUOMTO
Changes related to removal of key figure Demand Value (node)
(NODEDEMANDVAL) from Inventory Optimization

Reason for Change: This Key Figure is not needed anymore

Delete Key Figure: NODEDEMANDVAL from Planning Area

9
Changes related to adding Change Point Detection to the Forecast
Automation Profile
Reason for Change: Change point detection functionality is now used in the IBP for demand –
time-series analysis (34Y) scope item to search for significant changes with long-term effects in
the time series. For this reason, the Forecast Automation Profile SAPIBP1 has been updated
with the rules for change point detection.

Planning Operator Type : Forecast Automation; Planning Operator ID : SAPIBP1


Setup the rules for change point detection:
- Calculation Levels = Product ID - Location ID - Customer ID - Week
- Minimum Interval Between Change Points = 6
- Minimum Level Shift (%) = 20%
- Minimum Trend Change (%) = 10%

10
Changes related to New key figure Customer Forecast
(CUSTOMERFORECAST) for customer collaboration via Web-based Planning
Reason for Change: Introduced KF CUSTOMERFORECAST to be used by customers to enter
customer forecast via Web based planning - Customer app.

Create new stored Key Figure CUSTOMERFORECAST at TechWk|Prod|Loc|Cust level

11
Changes related to aligning Planning Levels with regards to IO attributes
Stocking Node Type Indicator (STOCKINGNODETYPE), Service Level Type
Indicator (SERVICELEVELTYPE) and Distribution Type (G or N)
(DISTRIBUTIONTYPE)
Reason for Change: Sync IO attributes among planning levels

Planning Level Configuration Changes


DAYSALESORDER remove SERVICELEVELTYPE, STOCKINGNODETYPE
DAYSALESORDERUOMTO remove SERVICELEVELTYPE, STOCKINGNODETYPE
MTHPRODLOCCUST remove DISTRIBUTIONTYPE,SERVICELEVELTYPE, STOCKINGNODETYPE
WKPRODLOCCUSTOFFSET remove DISTRIBUTIONTYPE,SERVICELEVELTYPE, STOCKINGNODETYPE
WKPRODLOCCUSTOFFSETUOMTO remove DISTRIBUTIONTYPE,SERVICELEVELTYPE, STOCKINGNODETYPE
CALWKPRODLOCCUSTGROUP add SERVICELEVELTYPE, STOCKINGNODETYPE
WKPRODLOCCOMPSRC add SERVICELEVELTYPE, STOCKINGNODETYPE
WKPRODLOCCOMPSRCUOMTO add SERVICELEVELTYPE, STOCKINGNODETYPE
12
Changes related to migrating Disaggregation Operators to new Copy
Operator Profiles
Reason for Change:
Old Disaggregate operators were migrated to the new PPF framework and removed from
SAPIBP1 model. Copy Operator Profiles are now maintained for the new Copy and
Disaggregate Key Figures operators (COP).

The following Planning Operators of type DISAGG have been unassigned from Planning Area

Copy to Global Demand (SOP) (105)


Copy to Consensus Demand (106)
Copy to Safety Stock (SOP) (107)
Copy to Consensus Dmd Final (108)
Copy to Demand Forecast (IO) (109)
Copy to Safety Stock LC (IO) (110)
Copy to Consensus Demand (FC) (116)

13
Changes related to Migrating Disaggregation operators to new Copy
Operator Profiles

New Copy Operator Profiles are created in app “Manage Copy Operator Profiles” and assigned to the
planning area

Copy to Global Demand (SOP) (105)


Copy to Consensus Demand (106)
Copy to Safety Stock (SOP) (107)
Copy to Consensus Dmd Final (108)
Copy to Demand Forecast (IO) (109)
Copy to Safety Stock LC (IO) (110)
Copy to Consensus Demand (FC) (116)

14
Changes related to new key figure Demand Sensing: Weeks to Exclude from
Learning (SENSEDDEMANDEXCLUDE) for Demand Sensing
Reason for Change:
Planner knows that a certain week is exceptional somehow and would negatively impact the Demand
Sensing planning results. This KF SENSEDDEMANDEXCLUDE is used to Exclude a certain week
from the Demand Sensing learning.

Allowed values of this key figure:


• 0 / NULL: Business as usual – DS uses data
in these weeks in the learning process. No
exclusion.
• 1: Exclude from / treat as outlier in the weekly
learning process (e.g. do not learn from data
in this week for bias adjustment, open order
adjustment, and any extra demand signal
adjustment – if there are any in the forecast
model)

15
New Feature related to Partial Copy of Unified Planning Area : Option to
Copy Analytics and Alerts

When copying the unified planning area (SAPIBP1) using the create new with dependencies option,
it‘s possible to select the Copy Analytics and Alerts option to copy sample analytics and alerts.
The following content types are copied:
• Sample dashboards (12)
• Sample analytics charts (65)
• Sample supply chain network charts (2)
• Sample alert definitions (3)
• Sample alert subscriptions (9)
• Sample alert overviews (2)

16
Changes related to Supply Key Figures which are “Output for Supply Planning”
Reason for Change:
With the introduction of the new app "Settings for TS Supply Planning", the settings for supply-
related key figures were streamlined. This required to change Key Figures in Supply Planning
from "Input/Output for Supply Planning" to "Output for Supply Planning".
Note: The supply operator works with either settings. It is not required for customers who
deployed their planning area before 2002 to adjust these settings.

Change Key Figure Setting from “Input and Output for Supply Planning” to “Output for Supply
Planning” for the following Key Figures

CAPADEMAND DEPENDENTPRODUCTIONDEMAND RECEIPT


CAPAUSAGE DEPENDENTPRODUCTIONDEMANDDS SHORTAGE
CONSTRAINEDDEMAND INDEPENDENTDEMANDSUPPLY SUPPLY
CONSTRAINEDDEMANDDS INTRANSIT TCAPADEMAND
DEFICIT INTRANSITCUSTOMER TCAPAUSAGE
DEPENDENTCUSTOMERDEMAND INTRANSITDS TOTALCONSTRAINEDDEMAND
DEPENDENTCUSTOMERDEMANDDS IPUPRODUCTION TOTALINDEPDEMANDSUPPLY
DEPENDENTDEMAND IPUPRODUCTIONCOMPONENTDS TOTALRECEIPT
DEPENDENTLOCATIONDEMAND PCAPADEMAND TRANSPORTRECEIPTSHIPTO
DEPENDENTLOCATIONDEMANDDS PCAPAUSAGE
17
Changes related to Supply Key Figures: Adjusted Production Receipts
(ADJUSTEDPRODUCTION) and Production Receipts (PRODUCTION)
Reason for Change:
Key Figure PRODUCTION: application-side change required that this key figure is changed to
"Output for Supply Planning"

Change KF Settings :
ADJUSTEDPRODUCTION:
1. Switch from "Input for Supply Planning" to "Input and Output for Supply Planning"
2. Switch from "Calculated" to "Stored and Calculated“

PRODUCTION:
Switch from "Input and Output for Supply Planning" to "Output for Supply Planning"

18
Agenda

• SAPIBP1: What's New in 2002

• SAPIBP1: General Remarks

• SAPIBP1: Key Figure Overview

• SAPIBP1: Master Data Type Overview

• SAPIBP1: Planning Level Overview

• SAPIBP1: General Planning Area Settings

• SAPIBP1: Changes in earlier releases

19
SAPIBP1 – General Remarks
SAPIBP1: General Remarks

• SAPIBP1 is a unified planning area delivered with IBP supporting an overall business
process that includes the following IBP applications:
• IBP for Sales & Operations
• IBP for Supply (w/o Response)
• IBP for Inventory
• IBP for Demand
• SAP Supply Chain Control Tower

• SAPIBP1 delivers an out-of-the-box reference integration scenario across the different IBP
applications

• SAPIBP1 is designed to work as a sample or starting point for the customers to jump-start an
implementation project: customers may use a copy of SAPIBP1 and make changes to it as
needed

• Use partial copy capability to slice only the required modules of SAPIBP1 e.g. S&OP and IO
slice
21
Agenda

• SAPIBP1: What's New in 2002

• SAPIBP1: General Remarks

• SAPIBP1: Key Figure Overview

• SAPIBP1: Master Data Type Overview

• SAPIBP1: Planning Level Overview

• SAPIBP1: General Planning Area Settings

• SAPIBP1: Changes in earlier releases

22
SAPIBP1 – Key Figure Overview
SAPIBP1: Key Figure Overview

• Several key figures of SAPIBP1 are used by more than one IBP application

• On the following slides we assigned key figures to one “main” component in order to provide a
grouping concept and a better overview

24
SAPIBP1: Key Figure Overview

• Key figures used for sales & operations


• Key figures used for supply
• Key figures used for inventory
• Key figures used for demand
• Key figures used for Control Tower
• Key figures related to order data
• Key figures related to Forecast Error Calculation
• Key figures related to Risk & Opportunities
• Special key figures
• „Integration“ key figures
25
Key Figures Copied from Demand Planning and Inventory Optimization
at the Beginning of the S&OP Planning Cycle

• SOPDEMANDPLANNINGQTY: Represents the last Global Demand Plan Quantity that was agreed and is used as a
stable information within the S&OP process to build the Consensus Demand Plan. To avoid considering ongoing changes
on Global Demand Plan Quantity, SOPDEMANDPLANNINGQTY is copied from DEMANDPLANNINGQTY via a copy
operator at the beginning of the S&OP process.

• SOPDEMANDPLANNINGREV: Used to calculate the Global Demand Plan Revenue to be used within the S&OP process
to build the Consensus Demand Plan. Calculated as SOPDEMANDPLANNINGQTY * PLANNEDPRICE

• SOPSAFETYSTOCK: Copied from FINALIOSAFETYSTOCK via copy operator at the beginning of the Supply review
phase in the S&OP process. It represents the Safety stock calculated during the last Inventory Optimization run and is
used as a stable input to the Supply algorithm.

26
Key Figures Used for Annual Operation Plan - Imported from External Tool

• AOPQTY: Integration key figure, used to store the monthly sales quantities at product and customer level from the Annual
Operation Plan managed in external systems. Used in the S&OP process as an input to build the Consensus demand
plan.

• AOPREV: Integration key figure, used to store the monthly sales revenues at product and customer level from the Annual
Operation Plan managed in external systems. Used in the S&OP process as an input to build the Consensus demand
plan.

• AOPPRICE: Used to calculate the monthly sales price at product and customer level from the Annual Operation Plan
managed in external systems; calculated as AOPREV / HAOPQTY. Used in the S&OP process as an input to build the
Consensus demand plan.

• AOPPROFIT: Integration key figure, used to store the monthly sales profit at product and customer level from the Annual
Operation Plan managed in external systems. Used in the S&OP process as an input to build the Consensus demand
plan.

27
Key Figures Related to Sales Forecast - Imported from External Sales Planning Tool

• SALESFORECASTQTY: Integration key figure used to store the sales forecast quantity at product-location-customer level from sales
planning external tool. Used in the S&OP process as an input to build the Consensus demand plan.

• SALESFORECASTREV: Used to calculate the sales forecast revenue at product-location-customer level; calculated as
SALESFORECASTQTY * PLANNEDPRICE. Used in the S&OP process as an input to build the Consensus demand plan.

• SALESFORECASTACCURACYPCT: Used to calculate the sales forecast accuracy percentage at product-location-customer level;
calculated using SALESFORECASTQTY and ACTUALSQTY.

The above key figures can be used in a simplified sales planning process in IBP, whenever an external sales planning tool is not in use.

28
Key Figures Related to Marketing Forecast - Imported from External Planning Tool

• MARKETINGFORECASTQTY: Integration key figure, used to store the marketing forecast quantity at product-customer
level from marketing planning external tool. Used in the S&OP process as an input to build the Consensus demand plan.
• MARKETINGFORECASTREV: Used to calculate the marketing forecast revenue at product-customer level; calculated as
MARKETINGFORECASTQTY * PLANNEDPRICE. Used in the S&OP process as an input to build the Consensus demand
plan.
• MARKETSIZEREV: Used to store the market size revenue at product-customer level.
• MARKETSHAREPCT: Used to calculate the market share percentage at product-customer level. Calculated as
CONSENSUSDEMANDREV / MARKETSIZEREV.

29
Key Figures Related to Open Orders and Opportunities

• OPENORDERSQTY: Integration key figure, used to store the Total open order quantity of sales orders managed in
external systems. Used in the S&OP process as an input to build the Consensus demand plan and as reference for the
Downside version of Consensus Demand Plan Qty.
• OPENORDERSREV: Integration key figure, used to store Open orders revenue of sales orders managed in external
systems. Used in the S&OP process as an input to build the Consensus demand plan.
• OPPORTUNITIESQTY: Integration key figure, used to store the Opportunity quantity managed in external customer
relationship system. Used in the S&OP process as a reference for the Upside version of Consensus Demand Plan Qty.
• OPPORTUNITIESREV: Integration key figure, used to store the Opportunity revenue managed in external customer
relationship system.

30
Key Figures Related to Consensus Finding

• CONSENSUSDEMAND: Used as input to the Supply algorithm; copied via copy operator from
CONSENSUSDEMANDQTY (technical restriction on name to be used as input key figure).
• CONSENSUSDEMANDREV: Used to calculate the consensus demand plan revenue as a result of the Demand review
phase of the S&OP process; calculated as CONSENSUSDEMANDQTY * PLANNEDPRICE.
• CONSENSUSDEMANDCOST: Used to calculate the consensus demand plan cost as a result of the Demand review
phase of the S&OP process; calculated as CONSENSUSDEMANDQTY * COSTPERUNIT.
• CONSENSUSDEMANDPROFIT: Used to calculate the consensus demand plan profit as a result of the Demand review
phase of the S&OP process; calculated as CONSENSUSDEMANDREV – CONSENSUDEMANDCOST.
• CONSENSUSDEMANDQTY: Used to store the consensus demand plan quantity as a result of the interactive planning
process in the Demand review phase of the S&OP process. Copied to CONSENSUSDEMAND via copy operator.
• FINALCONSENSUSDEMANDQTY: Used to store the customer receipt (CONSTRAINEDDEMAND) at the end of the
entire S&OP monthly process. Used as the CONSTRAINEDDEMAND referenced value of the last S&OP planning cycle,
whenever ongoing changes to it do not have to be taken into account. Copied from CONSTRAINEDDEMAND via copy
operator.

31
Key Figures Related to Accuracy of Approved Plan

• CONSENSUSACCURACYPCT: Used to calculate Consensus Demand Plan Quantity Accuracy Percentage. Calculated as
(1 – ABS(CONSENSUSDEMANDQTY – ACTUALSQTY) / ACTUALSQTY).

32
Key Figures Used for Profit and Loss Comparison

• OPERATINGPROFIT: Used to calculate the operating profit at product-customer level. Calculated as GROSSPROFIT –
INDIRECTCOSTS.

• INDIRECTCOSTS: Used to store indirect costs at product-customer level.


• GROSSPROFIT: Used to calculate gross profit; optionally used to support decisions in the Pre-S&OP Review phase of the
S&OP process. Calculated as CONSTRAINEDDEMANDREV – HGROSSCOSTS.

• CONSTRAINEDDEMANDREV: Used to calculate constrained demand revenue to support decisions in the Pre-S&OP
Review. Calculated as PLANNEDPRICE * CONSTRAINEDDEMAND.

• HGROSSCOSTS: Used to calculate gross cost. Calculated as COSTPERUNIT * CONSTRAINEDDEMAND.

• COSTPERUNIT: Integration key figure, used to store at Product-Location level the unit cost managed in external systems.
Used to calculate various key figures representing values.

33
Key Figures Used for Simplified Sales Planning (1/2)

The current end-to-end process definition of SAPIBP1 does not include a simplified sales planning sub-process, but
the following key figures can be used to perform a sales planning within SAPIBP1.

• SALESMGRFORECASTQTY: Used to store the sales manager forecast quantity at product-location-customer level.
• SALESMGRFORECASTREV: Used to calculate the sales manager forecast revenue at product-location-customer level.
Calculated as SALESMGRFORECASTQTY * PLANNEDPRICE.

34
Key Figures Used for Simplified Sales Planning (2/2)

Current end-to-end process definition of SAPIBP1 does not include a simplified sales planning sub-process, but the following key
figures can be used to perform a sales planning within SAPIBP1.

• FINANCEPLANQTY: Integration key figure, used to store the monthly sales quantities at customer region and product
family level from the Financial plan managed in external systems.

• FINANCEPLANREV: Integration key figure, used to store the monthly sales revenues at customer region and product
family level from the Financial plan managed in external systems.

35
Key Figures Used for Demand & Supply Review

Demand Review Supply Review

Copy from CONSENSUSDEMANDQTY

FINANCEPLANQTY
CONSENSUSDEMAND

AOPQTY
Copy from RECOMMENDEDSAFETYSTOCK

SALESFORECASTQTY
SOPSAFETYSTOCK ADJUSTEDSOPSAFETYSTOCK

MARKETINGFORECASTQTY

INVENTORYTARGET
Copy from DEMANDPLANNINGQTY

SOPDEMANDPLANNINGQTY
Output from Supply Algorithm

CONSTRAINEDDEMAND
CONSENSUSDEMANDQTY

Copy from CONSTRAINEDDEMAND

FINALCONSENSUSDEMANDQTY
36
SAPIBP1: Key Figure Overview

• Key figures used for sales & operations


• Key figures used for supply
• Key figures used for inventory
• Key figures used for demand
• Key figures used for Control Tower
• Key figures related to order data
• Key figures related to Forecast Error Calculation
• Key figures related to Risk & Opportunities
• Special key figures
• „Integration“ key figures
37
Additional Input Key Figures

• In addition to the master data and key figures used to define the Supply Chain
Network the following key figures are used as inputs:

• Consensus demand
• Technical Name: CONSENSUSDEMAND
• Key: PRDID,CUSTID
• Customer Demand is an input key figure for supply planning. This key figure is
not changed by the planning algorithms.
• This key figure defines the requested or forecasted demand of a customer for
a certain product for each period of the planning horizon.

38
Additional Input Key Figures

• Inventory target
• Technical Name: INVENTORYTARGET
• Key: PRDID,LOCID

• This input key figure defines the target inventory for the end of each period.

• Initial inventory
• Technical Name: INITIALINVENTORY
• Key: PRDID,LOCID

• This key figure contains the available quantity of the product at the given location at the beginning of the
first period, which is the period of the current time when the planning algorithm is run.
• Relevant only for the bucket corresponding to the current time.

39
Additional Input Key Figures

• Customer sourcing ratio


• Technical Name: CUSTOMERRATIO
• Key: PRDID,CUSTID,LOCID
• This input key figure contains the quotas for sourcing customer demand for a product from various ship-from
locations.
• For instance, if a customer demand is satisfied by 40% from distribution center 1 and the remaining 60%
from distribution center 2 these ratios are defined by the customer sourcing quota.

• Location sourcing ratio


• Technical Name: LOCATIONRATIO
• Key: PRDID,LOCID,LOCFR

− This input key figure defines the quotas according to which a Net Demand for a location product should
be sourced from various locations via stock transfers.

40
Additional Input Key Figures

• Independent demand
• Technical Name: INDEPENDENTDEMAND
• Key: PRDID,LOCID

• Via the input Independent Demand key figure a user can specify an additional, anonymous demand for
location products.
• The SCM Planning Operator takes the sum of the Dependent Demand and Independent Demand to
compute the Net Demand for each location product (in each period).
• Location sourcing ratio
• Technical Name: INITIALINTRANSIT
• Key: PRDID,LOCID,LOCFR

• The start value for In Transit is specified by a new key figure ‘Initial In Transit’.
• This key figure has a value for one time period only, which is the planning period corresponding to the
current time.

41
Additional Input Key Figures

• Capacity consumption rate of production resource


• Technical Name: PCAPACONSUMPTION
• Key: RESID,PRDID,LOCID

• “Capacity Consumption Rate of Production Resource” defines how much capacity is consumed per unit of
the product produced. The consumption rate is related to a production or assembly process and the
consumption rate is per produced / assembled piece.
• Capacity consumption rate for handling resource
• Technical Name: CAPACONSUMPTION
• Key: RESID,LOCID,PRDID,SOURCEID
• This key figure defines the capacity which is consumed on a handling resource by the receipt of one unit of a
location-product.
• Example: We assume that the Capacity Consumption Rate for product P1 on (handling) resource R1 in location L1
is 0.2 hours per piece. If the Net Demand for P1 at L1 is 100, the resulting Capacity Demand is as follows:
Capacity Demand = 100 [pieces] * 0.2 [hours/piece] = 20 [hours]

42
Additional Input Key Figures

• Capacity consumption rate for transportation resource


• Technical Name: TCAPACONSUMPTION
• Key: RESID,LOCID,PRDID,LOCFR

• This key figure specifies the capacity of a resource that is consumed when a product is transported. The consumption rate is defined for
each unit consumed when a product is transported. It can be used to calculate the capacity demand for a transportation resource.
• Example: We assume that the Capacity Consumption Rate for transportation resource R1 in location L1 is 0.2 hours per piece for product
P1. If the Net Demand for P1 at L1 is 100, the resulting Capacity Demand is:
Capacity Demand = 100 [pieces] * 0.2 [hours/piece] = 20 [hours]

• Capacity Supply Expansion of Production and Storage Resource


• Technical Name: CAPASUPPLYEXPANSION
• Key: RESID,LOCID

• “Capacity Supply Expansion” defines how much additional capacity is available beyond Normal Capacity

43
Additional Input Key Figures

• Number of sub-periods
• Technical Name: SUBPERIODNUM
• Key: PRDID,LOCID

• Used to logically divide each planning period of the planning horizon into sub-periods.
• Example: if a planning period covers a month and if SUBPERIODNUM is set to 30, a sub-period models a
day (for that planning period).

• Sub-period of supply
• Technical Name: SUBPERIODSOFSUPPLY
• Key: PRDID,LOCID
• Used to specify the target periods of coverage

• Sub-period first production


• Technical Name: SUBPERIODFIRSTPRODUCTION
• Key: PRDID,LOCID,SOURCEID
• Used to specify the first production period when used with Production Periods of Coverage
44
Additional Input Key Figures

• Inter-sub-network non-delivery cost rate


• Technical Name: IPUNONDELIVERYCOSTRATE
• Key: PRDID,LOCTO
• Used to store intra company sales or procurement prices, i.e. the company internal prices that define the prices (per unit
of measure - piece or ton) according to which goods are sold / bought from one upstream PU to / by another downstream
sub-network.

• Inter-sub-network receipts costs


• Technical Name: IPURECEIPTCOSTRATE
• Key: PRDID,LOCID
• IPU Receipts Cost Rate key figure is used to model intra company procurement costs for goods which are supplied by
another (upstream) sub-network.

45
Additional Input Key Figures

• Inter-sub-network transport receipt


• Technical Name: IPUTRANSPORT
• Key: PRDID,LOCID,LOCFR
• This is both an input and output key figure.
• It is editable.
• If it is an input to the SCM Planning Operator and in case the parameter “Compute Expected Supply” is used, the operator
writes computed supply into it that’s why it is an output key figure too.

• Inter-sub-network dependent location demand downstream


• Technical Name: IPUDEPENDENTLOCATIONDEMANDDS
• Key: PRDID,LOCID

• This is both an input and output key figure.

• It is editable.

• The user can enter values into the key figure. However, it is blanked out if the related arc becomes an inner border arc.

46
Additional Input Key Figures

• Inter-sub-network Production receipt


• Technical Name: IPUPRODUCTION
• Key: SOURCEID, PRDID,LOCID
• This is both an input and output key figure.
• It is editable.

• Inter-sub-network Production Component Usage


• Technical Name: IPUPRODUCTIONCOMPONENTDS
• Key: PRDTO,LOCID,PRDID,SOURCEID

• This is both an input and output key figure.

• It is editable.

• The user can enter values into the key figure. However, it is blanked out if the related arc becomes an inner border arc
of the planning unit

47
Additional Input Key Figures

• Dynamic periods of supply with safety stock


• Technical Name: SUBPERIODSOFSUPPLYSAFESTOCK
• Key: PRDID,LOCID
• This is an input key figure. It enables you to define a second coverage time span in which to build up safety stock.
• It combines the advantages of both the static and the dynamic periods of supply lot-sizing procedures in that it not only minimizes the
number of production or transportation events (by planning production and transport receipts only in periods where there's a demand), but it
also builds up safety stock in each period.
• The planning algorithms first calculate an increased inventory target for each period, which is the maximum of the inventory target of the
period and the sum of the dependent demand within the coverage time span. As a result, net demand is increased so the resulting projected
inventories cover the dependent demands within the coverage time span, and also cover the increased inventory target in each period of
the coverage time span. The algorithms perform their calculations based on this increased inventory target, not on the Inventory Target input
key figure.
• Only the supply planning and supply propagation heuristics support dynamic periods of supply with safety stock. You can't use this lot-sizing
procedure with the optimizer or the shelf life planning heuristic.
• To use the dynamic periods of supply lot-sizing procedure, set the LOTSIZEPOLICY attribute to 5 on location product level.

48
Optimizer Input Key Figures

In addition to the key figures described, optimizer requires the following penalty cost key
figures as inputs:

• Price or non-delivery cost rate


• Production cost (fixed and per unit rate)
• Transportation cost (fixed and per unit rate)
• External procurement cost (fixed and per unit rate)
• Inventory holding cost (per unit rate)
• Safety-stock violation cost (per unit rate)

49
Optimizer Input Key Figures

• Customer sourcing ratio


• Technical Name: NONDELIVERYCOSTRATE
• Key: PRDID,CUSTID

• This key figure defines the costs per unit of a Customer Demand quantity per period that
is not met by the supply plan stored in key figure Total Customer Receipt.
• The cost incurred is proportional to the difference between Customer demand and Total
Customer Receipt.

50
Optimizer Input Key Figures

• Fixed customer transportation cost


• Technical Name: FIXEDCUSTOMERTRANSPORTATIONCOST
• Key: PRDID,CUSTID,LOCID

• This key figure models a fixed cost per period for each period where customer receipts for a
product, customer and (ship-from) location are non-zero.

• Customer transportation cost rate


• Technical Name: CUSTOMERTRANSPORTATIONCOSTRATE
• Key: PRDID,CUSTID,LOCID

• This key figure stores all costs which are proportional to the transport quantity of a product from a
location to a customer. The transportation costs are defined per unit of product and period for
customer receipts.

51
Optimizer Input Key Figures

• Fixed production cost


• Technical Name: FIXEDTRANSPORTATIONCOST
• Key: PRDID,LOCID,LOCTO

• This key figure models a fixed cost per period for each period where transport receipts for a
product, location and ship-from location are non-zero.

• Production cost rate


• Technical Name: TRANSPORTATIONCOSTRATE
• Key: PRDID,LOCID,LOCTO

• This cost rate defines cost per quantity unit of product and period for Transport Receipts between
two locations.

52
Optimizer Input Key Figures

• Fixed production cost


• Technical Name: FIXEDPRODUCTIONCOST
• Key: PRDID,LOCID,SOURCEID

• This key figure models a fixed cost per period for each period where production receipts for a
product in a location are non-zero.

• Production cost rate


• Technical Name: PRODUCTIONCOSTRATE
• Key: PRDID,LOCID,SOURCEID

• This key figure models the cost per quantity unit of product and period for Production Receipts.

53
Optimizer Input Key Figures

• Fixed external receipt cost


• Technical Name: FIXEDEXTERNALRECEIPTCOST
• Key: PRDID,LOCID

• This key figure models a fixed cost per period for each period where External Receipts for a
location-product are non-zero.

• External receipt cost rate


• Technical Name: EXTERNALRECEIPTCOSTRATE
• Key: PRDID,LOCID

• This key figure models a cost per quantity unit of product and period for External Receipts for a
location-product.

54
Optimizer Input Key Figures

• Inventory holding cost rate


• Technical Name: INVENTORYHOLDINGCOSTRATE
• Key: PRDID,LOCID

• This key figure defines the cost for inventory holding per quantity unit of product and period and is
related to the key figure Projected Stock.

• Inventory target violation cost rate


• Technical Name: INVENTORYTARGETVIOLATIONCOSTRATE
• Key: PRDID,LOCID

• This key figure contains the costs per quantity unit of product and per period that the Projected
Stock is below the safety stock. These costs are typically not directly related to real costs but they
are entered as penalty costs.

55
Optimizer Input Key Figures

• Maximum inventory violation cost rate


• Technical Name: MAXINVENTORYVIOLATIONCOSTRATE
• Key: PRDID,LOCID

• This key figure contains the costs per quantity unit of product and per period that the
Projected Stock is above the Maximum Inventory which is defined in the master data.
• These costs are typically not directly related to real costs but they are entered as
penalty costs.

56
Optimizer Input Key Figures

• Capacity supply expansion cost rate


• Technical Name: CAPASUPPLYEXPANSIONCOSTRATE
• Key: RESID,LOCID

• This key figure is modeled as a soft constraint, that is, it can be violated, but any
violation adds penalty costs to the optimizer’s objective function.
• This key figure contains the penalty costs incurred for utilizing the additional capacity
beyond Normal Capacity. Additional Capacity and Normal Capacity are specified in
CAPASUPPLYEXPANSION and CAPASUPPLY key figures respectively.

57
Optimizer Input Key Figures

• Component substitution cost rate


• Technical Name: COMPONENTSUBSTCOSTRATE
• Key: SPRDFR, PRDFR, LOCID, SOURCEID

• This key figure is used to define a substitution cost rate for each unit of the original
component that is replaced by the substitution product.

58
Supply Planning Output Key Figures

• There are several output key figures which are populated to represent the supply plan as a
result of Supply planning algorithms, i.e. the supply and dependent demands computed by the
Unconstrained Heuristic and Optimizer.
• It is possible for a few key figures to describe how to compute them by a mathematical formula,
for example the key figure Projected Inventory.
• In the following section the different output key figures are described.

59
Customer Demand Output Key Figures

• Total customer receipts

• Technical name: TOTALCONSTRAINEDDEMAND


• Key: PRDID,CUSTID
• This output key figure contains the computed supply for customer-product combination per
period. It is also called Constrained Demand because it reflects a demand that can actually
be supplied by the network.

60
Customer Demand Output Key Figures

• Consensus Demand Delivered Late

• Technical name: CONSDEMDELIVEREDLATE


• Key: PRDID,CUSTID
• This output key figure contains the amount of demand which is delivered late for a particular
period

• Average Demand Delay of Customer Demand

• Technical name: CONSDEMDELIVEREDLATEAVG


• Key: PRDID,CUSTID
• This output key figure contains the average number of periods in which customer demand is
delivered late

61
Customer to Location Node Output Key Figures

• Outbound dependent customer demand

• Technical name: DEPENDENTCUSTOMERDEMAND


• Key: PRDID,CUSTID,LOCID

• This output key figure contains the demand that is propagated from customer demand to
locations, i.e. distribution centers and/or plants which are locations belonging to the company’s
supply chain network.

• Outbound dependent customer demand

• Technical name: DEPENDENTCUSTOMERDEMANDDS


• Key: PRDID,CUSTID,LOCID
• As a downstream key figure, the dependent customer demand belongs to the downstream side of location-
products.

62
Customer to Location Node Output Key Figures

• Customer receipts

• Technical name: CONSTRAINEDDEMAND


• Key: PRDID,CUSTID,LOCID

• This output key figure contains the demand that is propagated from customer demand to
locations, i.e. distribution centers and/or plants which are locations belonging to the company’s
supply chain network.
• Customer supply

• Technical name: CONSTRAINEDDEMANDDS


• Key: PRDID,CUSTID,LOCID

• Downstream key figure customer supply which corresponds to customer receipts. Customer
receipts describes the transports starting at an own location towards a customer.

63
Customer to Location Node Output Key Figures

64
Customer to Location Node Output Key Figures

• Customer receipts

• Technical name: INTRANSITCUSTOMER


• Key: PRDID,CUSTID,LOCID
• This output key figure contains the In Transit Customer Receipts which are on their way from
a location to a customer. It is an output key figure of the S&OP Planning Operator (heuristic
or optimizer).

65
Node-Related Output Key Figures

• Node-related key figures belong to a node of the network, i.e. a product-location combination.

• Dependent demand

• Technical name: DEPENDENTDEMAND


• Key: PRDID,LOCID
• This output key figure stores the sum of all dependent demands
including
− Outbound Customer Demand
− Outbound Location Demand
− Outbound Production Demand

for location-product.

66
Node-Related Output Key Figures
• Net demand requirement

• Technical name: NETDEMAND


• Key: PRDID,LOCID

• Net demand is the demand that needs to be sourced for a location-product.


• Computed based on several other key figures:
− Dependent Demand
− Stock on-hand / Projected Stock of previous period
− Lot size parameters
− Planning algorithm

used to compute supply plan.


• Net Demand is computed only by heuristic, but not by the optimizer. Net Demand is just set equal to
key figure Receipts after the optimizer computed a supply plan.

67
Node-Related Output Key Figures
• Receipt

• Technical name: TOTALRECEIPT


• Key: PRDID,LOCID
• This is an output key figure which equals (for each period) the sum of all receipts - everything
that is received (coming in) at a location for a product. The various receipts types are:
− Production receipts, via a production sourcing rule (source type P)
− Transport receipts, via a transport sourcing rule (source type T)
− External receipts via an “unspecified” sourcing rule (source type U)
• Supply

• Technical name: SUPPLY


• Key: PRDID,LOCID

• Sum of all supplies - everything that leaves a location. These are quantities that are transported
to another location or transported to a customer or are consumed in a production process.
68
Node-Related Output Key Figures
• Projected inventory

• Technical name: PROJECTEDSTOCK


• Key: PRDID,LOCID
• This output key figure contains the quantity in inventory; i.e. the planned stock on-hand for a location product at the end
of each period. The formula used to compute Projected Inventory PI(t) in period t is:
PI(1) = Inventory on-hand + Receipts(1) – Supply(1)
where period 1 is assumed to be the planning period corresponding to the current time.
PI(t) = MAX { PI(t-1); 0 } + Receipts(t) – Supply(t) for t = 2, 3, …, T.
 The term “Max { PI(t-1); 0 }” means that if the Projected Inventory in period (t-1) is negative the SCM Planning Operator assumes an
inventory at the end of period (t-1) of zero in order to compute the Net Demand in period t.
 The values of Projected Inventory can be negative - after a heuristic run only. The optimizer will never compute a supply plan leading to
negative Projected Inventory.

69
Node-Related Output Key Figures
Deficit

• Technical name: DEFICIT Key: PRDID,LOCID


• Output key figure Deficit is the non-cumulative difference between the Net Demand and Receipts for a location-product for each period. It is
computed according to the following formula:
Deficit(t) = Max { (Net Demand(t) – Receipts(t) ) ; 0 } for t = 1, …, T.
• Key figure Deficit always equals zero after a plan was computed by the optimizer.
Shortage

• Technical name: SHORTAGE Key: PRDID,LOCID


• Output key figure Shortage stores the non-cumulative difference between Dependent Demand and Supply for a location-product. It is
computed according to the following formula:
Shortage(t) = Max { (Dependent Demand(t) – Supply(t) ) ; 0 } for t = 1, …, T.
• Key figure Shortage always equals zero when a plan was computed by the optimizer.
• When using the S&OP heuristic “Infinite without Shortages” key figure, Shortage will also be zero in all buckets. The reason for the strategy
of this heuristic is to supply always the requested Dependent Demand which can result in a negative Projected Stock.

70
Node-Related Output Key Figures
External receipt

• Technical name: RECEIPT


• Key: PRDID,LOCID

• Used to model receipts at the boundary of the supply chain. If, for instance, the supply network
terminates at a location product where components are purchased.
• This is the task of the so-called U-rules where U stands for “unspecified”.

Independent demand supply

• Technical name: INDEPENDENTDEMANDSUPPLY


• Key: PRDID,LOCID

• This key figure contains the computed supply for Independent Demand in the output key figure.

71
Node-Related Output Key Figures
Projected coverage

• Technical name: COVERAGE


• Key: PRDID,LOCID

• Output key figure Coverage returns for each period t the number of future periods for which the
Dependent Demand can be satisfied by the Projected Stock of period t.
• This key figure stores for each period the range of the Projected Inventory.

72
Node-Related Output Key Figures
Additional Lot-Size Procedure Demand

• Technical name: ADDITIONALLOTSIZEDEMAND


• Key: PRDID,LOCID

• This output key figure returns the amount of demand which is added by the heuristic to the net demand as a
consequence of the usage of a lot size policy defined for the corresponding location product
• For lot size policy = 0 this key figure returns zero in all buckets.
• For lot size policies 1 (Static Periods of Supply) , 2 (Dynamic Periods of Supply) and 3 (Periods of
Coverage) it returns the amount of additional demand which is caused compared to the net demand

73
Location-to-Location or Arc Output Key Figures

There are arc-related key figures that are used to describe the flow of goods between locations.

Outbound location demand

• Technical name: DEPENDENTLOCATIONDEMAND


• Key: PRDID,LOCID, LOCFR

• This output key figure describes the net demand which is propagated from the receiving location
to the ship-from location which is requested to satisfy a Net Demand.
Dependent location demand

• Technical name: DEPENDENTLOCATIONDEMANDDS


• Key: PRDID,LOCID, LOCTO

• This is the downstream key figure corresponding to the upstream key figure outbound location
demand.

74
Location-to-Location or Arc Output Key Figures

There are arc-related key figures that are used to describe the flow of goods between locations.
Transport receipts

• Technical name: TRANSPORT


• Key: PRDID,LOCID, LOCFR

• This output key figure describes the net demand which is propagated from the receiving location
to the ship-from location which is requested to satisfy a Net Demand.
Transport supply

• Technical name: TRANSPORTDS


• Key: PRDID,LOCID, LOCTO

• The downstream key figure transport supply corresponds to the upstream key figure Transport
receipts.

75
Location-to-Location or Arc Output Key Figures

Transport receipt ship-to

• Technical name: TRANSPORTRECEIPTSHIPTO


• Key: PRDID,LOCID, LOCTO
• Transportation costs are to be incurred at shipping location but for the period in which a
transport arrives at its destination, i.e. at delivery / arrival time.
• In order to achieve this, IBP offers key figure transport receipts ship-to.

76
Location-to-Location or Arc Output Key Figures

There are arc-related key figures that are used to describe the flow of goods between locations.
Intransit receipts

• Technical name: INTRANSIT


• Key: PRDID,LOCID, LOCFR
• Key figure INTRANSIT receipts describes the in transit quantities which are on their way from one location to
another location (not the customer).

Intransit supply

• Technical name: INTRANSITDS


• Key: PRDID,LOCID, LOCTO
• This downstream key figure corresponds to the upstream key figure In Transit.
• The only difference to INTRANSIT is the key structure – the numbers are the same.

77
Production Output Key Figures
Outbound production demand

• Technical name: DEPENDENTPRODUCTIONDEMAND


• Key: PRDID,LOCID,PRDFR,SOURCEID

• This key figure is related to a production process. It stores the demand for components (input
products) which is derived from the Net Demand of a finished or semi-finished product.
Component usage

• Technical name: PRODUCTIONCOMPONENT


• Key: PRDID,LOCID,PRDFR,SOURCEID

• This key figure stores the quantity of a component which is produced (according to a Production
Source) and supplied for a production or assembly process requested by a previous node of the
network.

78
Production Output Key Figures
Component usage downstream

• Technical name: PRODUCTIONCOMPONENTDS


• Key: PRDTO,LOCID,PRDID,SOURCEID

• This key figure introduces downstream key figure component supply which corresponds to the
upstream key figure component usage.
Production receipts

• Technical name: PRODUCTION


• Key: PRDID,LOCID,SOURCEID

• It models the receipts of a product which are supplied for the corresponding production process.

79
Production Output Key Figures

80
Production Output Key Figures
Component usage downstream

• Technical name: COMPONENTWIP


• Key: PRDID,LOCID,PRDFR,SOURCEID

• The output key figure Component Work In Progress (COMPONENTWIP) specifies, for each period, how
much of a component is assigned to ongoing production processes and isn’t yet part of a finished product.
• A component’s work in progress is increased by the corresponding component usage in the period in which
the component is consumed by, or assigned to, the production process, that is, in the consumption period
determined by the component offset.
• A component’s work in progress is decreased by the corresponding component usage in the last period of
the production process, that is, in the period in which the output product is available.

81
Capacity Output Key Figures
Capacity demand of production resource

• Technical name: PCAPADEMAND


• Key: PRDID,LOCID,RESID,SOURCEID

• Describes the amount of capacity which is needed to produce the portion of the Net Demand of a
location-product which is sourced via a P-rule to a Production Source.
Capacity demand of handling resource

• Technical name: CAPADEMAND


• Key: PRDID,LOCID,RESID

• The Capacity demand of a handling resource describes the amount of capacity which is needed
to handle the entire Net Demand of a location-product.

82
Capacity Output Key Figures
Capacity usage of production resource

• Technical name: PCAPAUSAGE


• Key: PRDID,LOCID,RESID,SOURCEID

• Describes the amount of capacity which is actually consumed to produce the portion of the Net
Demand of a location-product which is sourced via a P-rule to a Production Source.
• The capacity usage of production resource can easily be computed by this formula (for production
resources):
Capacity Usage(t) = Production Receipts(t) * Capacity Consumption Rate of Production Resource(t)

Capacity usage of handling resource

• Technical name: CAPAUSAGE


• Key: PRDID,LOCID,RESID

• This output key figure is analogous to the capacity usage of production resource.

83
Capacity Output Key Figures
Capacity demand of transportation resource

• Technical name: TCAPADEMAND


• Key: PRDID,LOCID,LOCFR,RESID
• Describes the capacity requirements for transport (location source of supply). Capacity is consumed with each unit of product that is
transported. It is calculated by multiplying the net demand propagated to one transportation source by the corresponding Capacity
Consumption Rate of Transportation Resource (TCAPACONSUMPTION) key figure.

Capacity usage of transportation resource

• Technical name: TCAPAUSAGE


• Key: PRDID,LOCID,LOCFR,RESID
• This output key figure shows how much of a resource's capacity is consumed by the transportation of a product. If the capacity is sufficient to
satisfy the capacity demand of all products, this key figure is equal to the Capacity Demand of Transportation Resource (TCAPADEMAND)
key figure. If the capacity is insufficient and the supply plan is calculated using a finite planning algorithm, this key figure is generally smaller
than the Capacity Demand of Transportation Resource (TCAPADEMAND) key figure.
• The Capacity Usage of Transportation Resource (TCAPAUSAGE) key figure can be calculated as follows:

Capacity Usage (t) = Transport Receipts (t) * Capacity Consumption Rate of Transportation Resource (t)
84
Alert Key Figures Used for Supply

• ALRTCAPACITYOVERLOAD: Alert key figure used in Supply Planning view to highlight a capacity overload on a
Resource in a specific Location; alert is activated if UTILIZATIONPCT (Utilization percentage) of a resource is greater than
a threshold (see below). Used in conjunction with ALRTCAPACITYOVERLOADTHRESHOLD.

• ALRTCAPACITYOVERLOADTHRESHOLD: Used to store a threshold value for the utilization percentage of a Resource
in a specific Location. Used in conjunction with ALRTCAPACITYOVERLOAD.

• UTILIZATIONPCT: Used to calculate the Utilization Percentage for the resource at a particular location. Used in
conjunction with ALRTCAPACITYOVERLOAD.

85
Adjusted Key Figures
Adjusted outbound customer demand

• Technical name: ADJDEPENDENTCUSTOMERDEMAND


• Key: PRDID,LOCID,CUSTID
• Non-initial values in input key figure Adjusted Outbound Customer Demand do have a different impact on the behavior of the heuristic and
the Optimizer.
• For the heuristic it changes the Outbound Customer Demand to be propagated along the corresponding customer sourcing rule (C-rule).
• For the S&OP Optimizer it changes the demand to be sourced to a Sub-Network (see documentation about Planning Units) by over-ruling
the quota-calculated contribution for a specific customer sourcing rule.

Adjusted outbound customer demand downstream

• Technical name: ADJDEPENDENTCUSTOMERDEMANDDS


• Key: PRDID,LOCID,CUSTID
• Input key figure Adjusted Dependent Customer Demand is the Downstream Key Figure corresponding to the Upstream
Key Figure Adjusted Outbound Customer Demand.

86
Adjusted Key Figures
Adjusted customer receipts

• Technical name: ADJUSTEDCONSTRAINEDDEMAND


• Key: PRDID,LOCID,CUSTID

• This key figure allows manual adjustments to key figure Customer Receipts, i.e. to transports
from own locations to customers.
• A user can overwrite the computed supply for one or several periods.
Adjusted customer supply

• Technical name: ADJUSTEDCONSTRAINEDDEMANDDS


• Key: PRDID,LOCID,CUSTID

• Adjusted Customer Supply is a Downstream Key Figure corresponding to the Upstream Key
Figure Adjusted Customer Receipts.

87
Adjusted Key Figures
Adjusted production

• Technical name: ADJUSTEDPRODUCTION


• Key: PRDID,LOCID,SOURCEID

• This key figure allows manual adjustments to key figure Production Receipts.
• If the adjusted values are non-initial the planning algorithms take the given values instead of
computing the corresponding production quantities itself.
Adjusted production interactive

• Technical name: ADJUSTEDPRODUCTIONRECEIPT


• Key: PRDID,LOCID,SOURCEID

• This is an indirect input key figure for Supply planning Algorithms which allows to manually
overwrite Production Receipts.

88
Adjusted Key Figures

Adjusted demand

• Technical name: ADJUSTEDDEMAND


• Key: PRDID,LOCID
• Adjusted Demand enables the user to fix the values of the key figure Dependent Demand for any location-product.

Adjusted receipt

• Technical name: ADJUSTEDRECEIPT


• Key: PRDID,LOCID
• Adjusted Receipt enables the user to fix the quantities sourced via a U-sourcing instead of having an unspecified supply
of any quantity.

89
Adjusted Key Figures

Adjusted transport receipts

• Technical name: ADJUSTEDTRANSPORT


• Key: PRDID,LOCID,LOCFR
• Adjusted Transport Receipt enables a user to fix the Transport Receipts sourced via a transportation source.
• This means that the Transport Receipts delivered via this arc are fixed to the given adjusted values.

Adjusted transport supply

• Technical name: ADJUSTEDTRANSPORTDS


• Key: PRDID,LOCID,LOCTO
• Adjusted Transport Supply is a Downstream Key Figure corresponding to the Upstream Key Figure Adjusted Transport
Receipts.

90
Minimum Key Figures

• The Minimum key figures can be used by a planner directly for manual input to set a lower bound to the planned supply.
• The Minimum key figures are in addition to the Adjusted key figures. The difference is that Adjusted key figures fix a supply
value to an absolute value while Minimum key figures only set a lower bound.
• Besides the externally planned supply that has to be considered as minimum supply by the SCM planning algorithms, these
key figures can also be used by a planner directly for manual input to set a lower bound to the planned supply.
• The heuristic respects Minimum key figures as follows: an initial value in a Minimum key figure has no effect. A non-initial
value is compared with the value computed by the heuristic for the corresponding output key figure. (Transport Receipts, for
instance, is the corresponding output key figure to Minimum Transport Receipts.)
• If the minimum value is lesser than the computed value, the heuristic takes the value which was computed by the heuristic.
• If the computed value is lesser than the minimum value, the minimum value is taken.
• Optimizer treats Minimum key figures as constraints.
• When treating Minimum key figures as a hard constraint such minimum values might over-constrain the optimization
problem so that the problem might be unsolvable.

91
Minimum Customer Receipts and Minimum Customer Supply

Minimum customer receipts


• Technical name: MINCONSTRAINEDDEMAND
• Key: PRDID,LOCID,CUSTID
• This key figure is related to supply key figure Customer Receipts. It allows defining minimum transport
quantities to customers. Lead times between customer locations and own locations are respected.

Minimum customer supply


• Technical name: MINCONSTRAINEDDEMANDDS
• Key: PRDID,LOCID,CUSTID
• This key figure is a downstream key figure corresponding to the upstream key figure Minimum
customer receipts.

92
Minimum Key Figures - Minimum External Receipts

Minimum external receipts


• Technical name: MINRECEIPT
• Key: PRDID,LOCID
• A non-initial value in key figure Minimum external receipts ensures that the SCM planning algorithms plan a
minimum External Receipt.
• As an example: if the Net Demand to be sourced via a U sourcing rule is 8 units, the SCM planning algorithms would set a
receipt in exactly that quantity.
• If the user has defined a Minimum External Receipt of 10 units, the planning algorithms would respect this by having a
receipt of 10 units. As this is more than needed, normally this will build-up inventory which is in this example 2 units.
• In case the Minimum External Receipt was 7 and not 10, the SCM planning operator would still source a receipt of 8.
• A value given in key figure Adjusted External Receipts, in contrast, would define a fixed value which has to be respected
by the planning algorithms. If in the example above, the user enters an Adjusted Receipt of 7, the planning algorithms
would take this value without any change.

93
Minimum Key Figures - Minimum Production Receipts and Maximum Inventory

Minimum production receipts


• Technical name: MINPRODUCTION
• Key: PRDID,LOCID,SOURCEID
• Minimum production receipts are related to the supply key figure Production receipts and they define
minimum production quantities which are set, either manually by a user or received during an upload
process. This means that with such a minimum value S&OP can plan an even higher, but not a lower
production quantity.

94
Minimum Key Figures - Minimum Transport Receipts

Minimum transport receipts


• Technical name: MINTRANSPORT
• Key: PRDID,LOCID,LOCFR
• It is quite natural that things do not happen exactly as they have been planned. So, for instance, even if a
lead time of two periods is defined between two locations, transports might take longer or might need less
time.
• Key figure Minimum Transport Receipts stores those quantities which do arrive in the corresponding period.
Minimum transport supply
• Technical name: MINTRANSPORTDS
• Key: PRDID,LOCID,LOCTO
• This key figure is related to the supply key figure Minimum Transport Receipts.

95
Maximum Key Figures - Maximum Customer Receipts and Supply

Maximum customer receipts


• Technical name: MAXCONSTRAINEDDEMAND
• Key: PRDID,LOCID,CUSTID
• This key figure is related to supply key figure Customer receipts. It allows limiting transport quantities to
customers to the specified value.
• Only respected by the optimizer.

Maximum customer supply


 Technical name: MAXCONSTRAINEDDEMANDDS
 Key: PRDID,LOCID,CUSTID
 This key figure is a Downstream Key Figure corresponding to the Upstream Key Figure Maximum Customer
Receipts.
 Only respected by the optimizer.

96
Maximum Key Figures - Maximum External and Production Receipts

Maximum external receipts


 Technical name: MAXRECEIPT
 Key: PRDID,LOCID
 A non-initial value in key figure Maximum external receipts limits the output key figure External receipts.

Maximum production receipts


 Technical name: MAXPRODUCTION
 Key: PRDID,LOCID,SOURCEID
 Maximum Production receipts are related to the supply key figure Production receipts.
 This key figure limits the output key figure Production Receipts.

97
Maximum Key Figures - Maximum Inventory

Maximum inventory
• Technical name: MAXINVENTORY
• Key: PRDID,LOCID
• The purpose of this key figure is to define a constraint for the optimizer, which is the maximum inventory
level for a location-product.
• The optimizer respects this constraint by limiting the production, the purchase or the transport of this
location-product so that the Projected inventory remains at or below the value stored in key figure in
each period.

98
Maximum Key Figures - Maximum Transport Receipts

Maximum transport receipts


• Technical name: MAXTRANSPORT
• Key: PRDID,LOCID,LOCFR
• This key figure limits the output key figure Transport receipts.

Maximum transport supply


• Technical name: MAXNTRANSPORTDS
• Key: PRDID,LOCID,LOCTO
• This key figure is the corresponding downstream key figure to key figure Maximum customer receipts.
• It limits the quantities computed by the optimizer for key figure Customer supply.

99
Computed Quota Key Figures

There are four output key figures which return the computed cost-optimal quotas after the SCM
Planning Operator was called in the appropriate mode. These key figures are the following:
Computed customer sourcing quota

• Technical name: CUSTOMERRATIOCOMP


• Key: PRDID,LOCID,CUSTID
• This key figure returns the computed quotas for Customer Sourcing (C-) rules.

Computed location sourcing quota

• Technical name: LOCATIONRATIOCOMP


• Key: PRDID,LOCID,LOCFR
• This key figure returns the computed quotas for Transportation Sourcing (T-) rules.

100
Computed Quota Key Figures

Computed production sourcing quota


• Technical name: PRODUCTIONRATIOCOMP
• Key: PRDID,LOCID,SOURCEID
• This key figure returns the computed quotas for Production Sourcing (P-) rules.

101
Aggregated Constraints Key Figures

• Aggregated constraint key figures enable you to model optimizer constraints at any aggregate level of product,
customer, location or resource attribute.

• For example, you can specify minimum demand for the combination of product family and customer region. The
following new aggregated constraint key figures are delivered in the standard system:

• By default, aggregated constraints are modeled as hard constraints. If required, you can model minimum
aggregated constraints as pseudo-hard constraints by making the necessary settings in the optimizer profile
(see Optimizer Profile).

• The conditions defined by aggregated constraint key figures are evaluated on the underlying basic master data
entities and their key figure values, so that the optimizer can add the relevant constraints.

• Unlike other key figures, aggregated constraint key figure values are only stored at the aggregate level (that is,
the level where you entered them in the Excel planning view) and there is no disaggregation

• Aggregated constraints can exist on multiple planning levels in parallel for the same key figure.

102
Aggregated Constraints Key Figures

Minimum Aggregate Constrained Demand (MINAGGDEMAND)

Base planning level: Period – Product – Location – Customer

You can use this input key figure to specify the minimum constrained demand in a defined period for any
combination of product, location, and customer. For example, you can specify a minimum constrained demand for
the combination of product family and customer region. The optimizer ships at least the specified amount of the
corresponding products to these customers.

Maximum Aggregate Constrained Demand (MAXAGGDEMAND)

Base planning level: Period – Product – Location – Customer

You can use this input key figure to specify the maximum constrained demand in a defined period for any
combination of product, location, and customer. For example, you can specify a maximum constrained demand for
the combination of product family and customer region. The optimizer ships at most the specified amount of the
corresponding products to these customers.

103
Aggregated Constraints Key Figures

Minimum Aggregate Production (MINAGGPRODUCTION)

Base planning level: Period – Product – Location – Production Source of Supply

You can use this input key figure to specify the minimum amount in a defined period for any combination of
product, location, and production source of supply. For example, you can specify the minimum production amount
for several products of a specific color at defined plants. If you specify a minimum amount of 50, at least 50 such
products are produced using the defined production sources of supply.

Maximum Aggregate Production (MAXAGGPRODUCTION)

Base planning level: Period – Product – Location – Production Source of Supply

You can use this input key figure to specify a maximum amount in a defined period for any combination of product,
location, and production source of supply. For example, you can specify the maximum production amount for
several products of a specific color at defined plants. If you specify a maximum amount of 100, at most 100 such
products are produced using the defined production sources of supply.

104
Aggregated Constraints Key Figures

Minimum Aggregate Transport (MINAGGTRANSPORT)

Base planning level: Period – Product – Location – Ship-From Location

You can use this input key figure to specify the minimum quantity to be transported in a defined period for any
combination of product, location, and ship-from location. For example, you can specify the minimum quantity
of a product family to be transported from a group of ship-from locations to another group of locations

Maximum Aggregate Transport (MAXAGGTRANSPORT)

Base planning level: Period – Product – Location – Ship-From Location

You can use this input key figure to specify the maximum quantity to be transported in a defined period for any
combination of product, location, and ship-from location. For example, you can specify the maximum quantity
of a product family to be transported from a group of ship-from locations to another group of locations.

105
Aggregated Constraints Key Figures

Minimum Aggregate Demand DS (MINAGGDEMANDDS)

Base planning level: Period – Product – Location – Customer

This key figure corresponds to the upstream key figure Minimum Aggregate Constrained
Demand (MINAGGDEMAND).

Maximum Aggregate Demand DS (MAXAGGDEMANDDS)

Base planning level: Period – Product – Location – Customer

This key figure corresponds to the upstream key figure Maximum Aggregate Constrained
Demand (MAXAGGDEMAND).

106
Aggregated Constraints Key Figures

Minimum Aggregate Transport DS (MINAGGTRANSPORTDS)

Base planning level: Period – Product – Ship-To Location – Location

This key figure corresponds to the upstream key figure Minimum Aggregate
Transport (MINAGGTRANSPORT).

Maximum Aggregate Transport DS (MAXAGGTRANSPORTDS)

Base planning level: Period – Product – Ship-To Location – Location

This key figure corresponds to the upstream key figure Maximum Aggregate
Transport (MAXAGGTRANSPORT).

107
Aggregated Constraints Key Figures
Aggregated Constraints Using Conversion Factors for Production

For example, you may want to ensure that specific high grade products are manufactured on a specific
production line, but you don't know in advance how long it takes to manufacture them.
To ensure they're produced, you can allocate a certain number of hours on the production line for them,
defined as a production capacity usage aggregated constraint.
You can also specify the period to which this production capacity usage aggregated constraint applies.
Minimum Aggregate Production Capacity Usage (MINAGGPCAPAUSAGE)
Base planning level: Cal Week | Product | Location | Resource | Source | Aggregation
You can use this key figure to allocate minimum resource utilization or consumption at an aggregate level for
production resources.

Maximum Aggregate Production Capacity Usage (MAXAGGPCAPAUSAGE)


Base planning level: Cal Week | Product | Location | Resource | Source | Aggregation
You can use this key figure to allocate maximum resource utilization or consumption at an aggregate level for
production resources.

108
Aggregated Constraints Key Figures
Aggregated Constraints Using Conversion Factors for Transportation
For example, you can add the capacity consumption rate of the mode of transport as a conversion
factor to this aggregated constraint so that adequate capacity is reserved for transportation.

Minimum Aggregate Transportation Capacity Usage (MINAGGTCAPAUSAGE)


Base planning level: Cal Week | Product | Location | Ship-From Location | Transportation Resource |
Aggregation
You can use this key figure to allocate minimum consumption rate at an aggregate level for
transportation resources.

Maximum Aggregate Transportation Capacity Usage (MAXAGGTCAPAUSAGE)


Base planning level: Cal Week | Product | Location | Ship-From Location | Transportation Resource |
Aggregation
You can use this key figure to allocate maximum consumption rate at an aggregate level for
transportation resources.

109
Inventory Correction Key Figures

Inventory Correction (INVENTORYCORRECTION)

Base planning level: Product – Location

You can use the Inventory Correction key figure to influence the calculation of the projected stock. If the value of
the Inventory Correction key figure is not initial, the planning operator adds this value to the projected stock as
follows:

PS(1) = Stock on Hand + Receipts(1) – Supply(1) + Inventory Correction(1)

In this case, period 1 is assumed to be the first period within the planning horizon and the key figure Stock on
Hand stores the available stock at the beginning of period 1.

PS(t) = MAX { PS(t-1); 0 } + Receipts(t) – Supply(t) + Inventory Correction(t)

for t = 2, 3, …, T.

You can enter positive or negative values in the Inventory Correction key figure.

110
Inventory Correction Key Figures

Inventory Correction Violated (INVENTORYCORRECTIONVIOLATED)

Base planning level: Product – Location

Inventory corrections are modeled as “pseudo-hard” constraints, meaning that very high penalty costs guide the optimizer to
adhere to these constraints. However, if no other feasible solution can be found, the optimizer may violate these pseudo-hard
constraints. The Inventory Correction Violated output key figure is set to zero if the constraints can be adhered to. Otherwise, it
returns the sum or difference between the value in the Inventory Correction key figure and the actual quantity calculated by the
optimizer.

Example If a negative inventory correction is entered but the quantity cannot be completely supplied, the Inventory Correction
Violated key figure returns the sum of the requested value and the actual value. If you enter -100 units as the inventory correction
but only 80 units can be delivered, the Inventory Correction Violated key figure would contain -100 + 80 = -20.

If a positive inventory correction is entered but the quantity cannot be completely accepted (received) by a location, the Inventory
Correction Violated key figure returns the difference between the requested value and the actual value. If you enter +60 units as
the inventory correction but the optimizer only accepts 10 units, the Inventory Correction Violated key figure would contain 60 - 10
= 50. However, because the maximum inventory level is modeled as a soft constraint, this case should never occur. The Inventory
Correction Violated key figure should usually only contain negative values or zero.

111
Late Delivery Key Figures

The optimizer can calculate a supply plan in which customer demands are fulfilled later than requested, that is, delivery takes
place either partially or completely in one or more periods after the requested period.

By default, the optimizer attempts to satisfy all customer demands on time. In other words, the optimizer tries to
plan customer receipts that match the corresponding customer demands in all periods and for each customer
product. If it can't generate a supply plan that meets these requirements, any non-delivered quantities are
considered to be lost sales because they are not transferred to a subsequent period.

If you want to change the default behavior of the optimizer so that non-delivered quantities are carried over to a
subsequent period, you can do so using the key figures below.

Late Delivery Maximum Periods (CONSDEMLATEDELIVMAX)

Base planning level: Customer – Product

You can use this input key figure to specify the maximum number of periods that a customer demand, or part of a
customer demand, can be delivered late.

112
Late Delivery Key Figures

Late Delivery Cost Rate (CONSDEMLATEDELIVCOSTRATE)

Base planning level: Customer – Product

You can use this input key figure to specify the cost rate for late deliveries (per unit of measure and period). These
costs are incurred for any amounts that are delivered late in each period.

To avoid unnecessary late deliveries, you must fill this key figure accordingly. It is multiplied with the number of
periods and the quantities that are delivered late to return the cost of the late deliveries.

Total Delivered (CONSDEMDELIVERED)

Base planning level: Customer – Product

This output key figure specifies the total customer demand that is delivered on time or late (that is, the demand
that is satisfied in any period).

113
Minimum Resource Consumption

For business reasons, your organization may want use of a specific resource to be equal to, or more than, a
certain minimum. If so, you can use the minimum resource consumption feature to ensure that the S&OP
optimizer creates a supply plan that increases production receipts to this minimum consumption value, even if
fewer production quantities would be sufficient to satisfy the relevant customer demands.

You specify a minimum consumption value for a resource in each period using the key figure MINCAPAUSAGE.
Minimum resource consumption is modeled as a soft constraint, that is, it can be violated, but any violation adds
penalty costs to the optimizer’s objective function. You define the amount of these penalty costs in the key
figure MINCAPAUSAGEVIOLCOSTRATE.

If you define minimum consumption for a resource, you may end up producing more than required to fulfil
customer or independent demands. If this happens, you can use the amount left over in the following ways:
• Add it to stock at the location where it was produced.
• Transport it to other locations and add it to stock there.
• Use it in other production processes.

114
Minimum Resource Capacity

Minimum Resource Capacity Usage (MINCAPAUSAGE)

Base planning level: Resource – Location

You can use this input key figure to specify the minimum consumption for a resource in a defined period at a specified location.
This value can be violated, but any violation adds penalty costs, which you define in the key
figure MINCAPAUSAGEVIOLCOSTRATE.

This key figure is not supported for handling and storage resources.

Minimum Resource Capacity Violation Cost Rate (MINCAPAUSAGEVIOLCOSTRATE)

Base planning level: Resource – Location

You can use this input key figure to specify the cost per unit that applies if the actual consumption is below the specified
minimum consumption value for a resource in a defined period at a specified location.

This key figure is not supported for handling and storage resources.

115
SAPIBP1: Key Figure Overview

• Key figures used for sales & operations


• Key figures used for supply
• Key figures used for inventory
• Key figures used for demand
• Key figures used for Control Tower
• Key figures related to order data
• Key figures related to Forecast Error Calculation
• Key figures related to Risk & Opportunities
• Special key figures
• „Integration“ key figures
116
Key Figures Used for Inventory

• IOFORECAST: Input key figure, result of the demand planning process, used to calculate the safety stock levels across
the whole network.

• IOFORECASTERRORCV: Input key figure, needs to be sourced externally. Used to calculate the safety stock levels
across the whole network.

• TARGETSERVICELEVEL: Input key figure, contains the desired target service level (non stock-out probability or fill-rate)
for each customer group, product, location combination.

• INVENTORYHOLDINGCOSTRATE: This is the holding cost rate (not percentage) for each product-location combination.
This in an input to the IO Algorithm and Supply module. The algorithm tends to push safety stock at locations where
holding costs are lower.

The holding costs are not assigned to any currency so these costs may be related to real costs or not, e.g. abstract
penalty costs to enforce a certain behavior.

Please note the inventory optimization will take only the first period into account.

117
Key Figures Used for Inventory

• LOCATIONRATIO: In case of multi-sourcing for a location, this key figure defines the fraction of the total demand that is
sourced for each period. This key figure is only used if the indicator is set in the corresponding SOURCELOCATION
record.
• PRODUCTIONRATIO: In case of alternative bill of materials or suppliers, this key figure defines the fraction of the total
demand that is sourced for each period. This key figure is only used if the indicator is set in the corresponding
SOURCEPRODUCTION record.
• PBR: Used to define the periods between replenishments for product-locations. Please note that this is an attribute as a
key figure.
• TLEADTIME: Defined as attribute as a key figure of a source-location combination.
• TLEADTIMEVARIABILITY: Defined as attribute as a key figure of a source-location combination.
• TINCLOTSIZE: Defined as attribute as a key figure of a source-location combination.
• TMINLOTSIZE: Defined as attribute as a key figure of a source-location combination.
• PLEADTIME: Defined as attribute as a key figure of a source-production combination.
• PLEADTIMEVARIABILITY: Defined as attribute as a key figure of a source-production combination.
• PINCLOTSIZE: Defined as attribute as a key figure of a source-production combination.
• PMINLOTSIZE: Defined as attribute as a key figure of a source-production combination.
• IOMAXINVENTORY: Used to specify maximum expected on-hand level at the stocking point

118
Key Figures Used for Inventory
• RECOMMENDEDSAFETYSTOCK: This key figure describes the quantity that should be in stock as safety stock per product and location. It
is the quantity where the desired (for customer-facing nodes) or calculated non stock-out probability / fill-rate is reached.
• TARGETINVENTORYPOSITION: The TARGETINVENTORYPOSITION (TIP) is derived from the safety stock level. TIP is considered as
upper level of a (s,S) policy. It is the safety stock increased by the expected demand during the exposure period (sum of PBR and lead
time).
• AVAILABLEINFULL: This key figure contains the probability that the demand can be fulfilled = probability that the demand within a period is
equal or lower than the recommended safety stock level.
• For customer-facing nodes, this is equal to the weighted sum of all service levels requested by the connected demand stream (=input).
• For internal nodes, the key figure contains the result of the optimization (=output).
• LOSTCUSTOMERDEMANDMEAN: This key figure contains the probability that the demand cannot be fulfilled weighted with the quantity
that is lost. The probability for a stock out is 100% - AVAILABLEINFULL. This probability weighted with the difference between the quantity
and the safety stock level is the expected lost demand mean (fill-rate). For non-stockout probability the total quantity lost is used for
weighting.
• AVGEXPEDITEVAL: This key figure contains the monetary value of the lost customer demand mean. The quantity is weighted with the
costs per unit and if required converted to another currency.
• ABCSERVICELEVEL: This key figure contains the user specified target service level for each ABC segmentaion.
• AVERAGESERVICELEVEL: This key figure contains the calculated service level to the downstream stocking nodes by the inventory
optimization algorithm for the given service level type.
• MAXINTERNALSERVICELEVEL: This key figure contains user specified upper bound for internal service level calculated by the inventory
optimization algorithm.
• MININTERNALSERVICELEVEL: This key figure contains user specified lower bound for internal service level calculated by the inventory
optimization algorithm.
119
Flow Through Lead Time and Lot Size Key Figures Used for inventory

The following key figures are used to account for impact of lead time and lot size at upstream flow-through nodes

Key Figure ID Key Figure Description

CALCTINCLOTSIZE Flow-through Transportation Incremental Lot Size

CALCTLEADTIME Flow-through Transportation Lead Time

CALCTLEADTIMEVARIABILITY Flow-through Transportation Lead Time Error CV

CALCTMINLOTSIZE Flow-through Transportation Minimum Lot Size

CALCPINCLOTSIZE Flow-through Production Incremental Lot Size

CALCPLEADTIME Flow-through Production Lead Time

CALCPLEADTIMEVARIABILITY Flow-through Production Lead Time Error CV

CALCPMINLOTSIZE Flow-through Production Minimum Lot Size

120
Key Figures Used for Inventory

The following key figures are used to report all components of inventory

Key Figure ID Key Figure Description


IOMINSTOCKREQUIREMENT Input minimum stock requirement

IOTARGETCYCLESTOCK Target cycle stock

IOAVGCYCLESTOCK Average cycle stock

IOTARGETPIPELINESTOCK Target pipeline stock

IOAVGPIPELINESTOCK Average pipeline stock

IOTARGETINPROCESSSTOCK Target in process stock

IOAVGINPROCESSSTOCK Average in process stock

IOTARGETVENDORTRANSITSTOCK Target vendor in transit stock

IOAVGVENDORTRANSITSTOCK Average vendor in transit stock

IOMERCHANDISINGSTOCK Merchandising stock

121
Key Figures Used for Inventory

The following key figures are used to report all components of inventory (continued)

Key Figure ID Key Figure Description


IOTARGETONHANDSTOCK Target on-hand stock

IOAVGONHANDSTOCK Average on-hand stock

IOENDONHANDSTOCK Ending on-hand stock

ROP Reorder point

IOAVGINVENTORYPOSITION Average inventory position

IOTGTONHANDDAYSOFSUPPLY Target on-hand stock in days of supply

IOAVGONHANDDAYSOFSUPPLY Average on-hand stock in days of supply

IOENDONHANDDAYSOFSUPPLY Ending on-hand stock in days of supply

IOSAFETYSTOCKDAYSOFSUPPLY Safety stock in days of supply

122
Key Figures Used for Inventory

Key Figure ID Key Figure Description


IOMINSTOCKREQUIREMENTVAL Contains monetary value of input minimum stock requirement
IOTARGETCYCLESTOCKVAL Contains monetary value of target cycle stock
IOAVGCYCLESTOCKVAL Contains monetary value of average cycle stock
IOTARGETPIPELINESTOCKVAL Contains monetary value of target pipeline stock
IOAVGPIPELINESTOCKVAL Contains monetary value of average pipeline stock
IOTARGETINPROCESSSTOCKVAL Contains monetary value of target in process stock
IOAVGINPROCESSSTOCKVAL Contains monetary value of average in process stock
IOTARGETVENDORTRANSITSTOCKVAL Contains monetary value of target vendor in transit stock
IOAVGVENDORTRANSITSTOCKVAL Contains monetary value of average vendor in transit stock
IOMERCHANDISINGSTOCKVAL Contains monetary value of merchandising stock
IOTARGETONHANDSTOCKVAL Contains monetary value of target on-hand stock
IOAVGONHANDSTOCKVAL Contains monetary value of average on-hand stock
IOAVGWORKINGCAPITAL Contains monetary value of average inventory position
IOTARGETWORKINGCAPITAL Contains monetary value of target inventory position
123
Key Figures used for inventory

Safety stock drivers

• SAFETYSTOCKDEMANDVAR: This key figure represents the safety stock component driven by demand variability in the
recommended safety stock

• SAFETYSTOCKSUPPLYVAR: This key figure represents the safety stock component driven by supply variability in the
recommended safety stock

• SAFETYSTOCKSERVICEVAR: This key figure represents the safety stock component driven by upstream supply
variability in the recommended safety stock

• SAFETYSTOCKLOTSIZE: This key figure represents the safety stock reduction driven by minimum/incremental lot size
input.

124
Key Figures Used for Inventory

• FINALIOSAFETYSTOCK: This key figure contains the final safety stock. The value is then released to APO/ERP and
overwrites the key figure with the values from the last planning cycle.

• ADJUSTEDIOSAFETYSTOCK: This can be used for manually overwrite the recommended safety stock. If the user
manually maintained this key figure, this value is stored in FINALIOSAFETYSTOCK, otherwise recommended safety stock
is stored in FINALIOSAFETYSTOCK.

• FINALIOSAFETYSTOCKLASTCYCLE: Stores the values of the key figure FINALIOSAFETYSTOCK from the previous
planning run.

• SAFETYSTOCKDELTA: Stores the delta between the key figure FINALIOSAFETYSTOCK and the key figure
FINALIOSAFETYSTOCKLASTCYCLE

• RECOMMENDEDSAFETYSTOCKVAL: Contains the monetary value of the recommended safety stock. The quantity is
weighted with the costs per unit and if required converted to another currency.

• IOAVGHISTDEMAND/VIOAVGHISTDEMAND: Contains the average historical demand

• IOAVGHISTDEMANDCV/VIOAVGHISTDEMANDCV: Contains the coefficient of variation for the historical demand


125
Key Figures Used for Inventory

The following key figures are internal ones, which are the result of an
inventory optimization. They are used for analysis and show the
internal demand between the different supply chain stages.
DEPENDENTCUSTOMERDEMANDMEAN
In addition to these key figures the information on the standard (Independent Demand Mean)
deviation also exists (… STDDEV).
DEPENDENTLOCATIONDEMANDMEAN
(Dependent Demand Mean)

DEPENDENTSRCTOLOCDEMANDMEAN
(Upstream Source Demand Mean)

DEPENDENTLOCTOPRDDEMANDMEAND PROPAGATEDDEMAND
(Dependent Demand Mean – Component) (Propagated Demand)

NODEDEMANDVAL: contains the monetary value of the propagated demand mean. The quantity is
weighted with the costs per unit and if required converted to another currency.

126
Key Figures Used for Inventory

• The following key figures are internal ones, which are the result of
an inventory optimization. They are used for analysis. They show
the internal and customer-facing service level.
• Technically all key figures follow the same logic as explained for
AVAILABLEINFULL before.

AVAILABLEINFULL
(Non-Stockout Probability
Service Level)

INTERNALAVAILABLEINFULL
(Internal Non-Stockout Probability)

INTERNALLOCTOPRDAIF
(Component Non-Stockout Probability)

127
Key Figures Used for Inventory

The following key figures are internal ones, which are the result of an
inventory optimization. They are used for analysis.
The backlog can be found in these key figures with the mean and also
the standard deviation (… STDDEV).
Technically all key figures follow the same logic as explained for
LOSTCUSTOMERDEMANDMEAN before.

LOSTCUSTOMERDEMANDMEAN
(Average Expedites)

OUTGOINGBACKLOGMEAN
(Internal Backorder Mean)

OUTGOINGSRCTOLOCBACKLOGMEAN
(Production Backorder Mean)

128
Inventory - Key Figure Overview

All inventory key figures with the suffix …MEAN


exist also with the standard deviation (suffix …STDDEV).

129
SAPIBP1: Key Figure Overview

• Key figures used for sales & operations


• Key figures used for supply
• Key figures used for inventory
• Key figures used for demand
• Key figures used for Control Tower
• Key figures related to order data
• Key figures related to Forecast Error Calculation
• Key figures related to Risk & Opportunities
• Special key figures
• „Integration“ key figures
130
Key Figures Used for Demand

• IBP for demand covers classical mid-term and long-term demand planning as well as Demand
sensing/Short term forecasting.

• IBP for demand “shares” several key figures with S&OP. A clear split of key figures is not always
possible. In this presentation you may find some demand-related key figure listed under S&OP.

131
Demand-Related Quantity Key Figures

• STATISTICALFORECASTQTY: Used to store results of statistical forecasting. Output from Statistical Output from Demand
Forecast Algorithm Sensing Algorithm
• LOCALDEMANDPLANQTY: To be used by local Demand Planners
• Equals to STATISTICALFORECASTQTY as long as not overwritten manually.
STATISTICAL- SENSED-
• Local Demand Planners can manually enter their forecast and with that overwrite the statistical forecast.
FORECASTQTY DEMANDQTY
• DEMANDPLANNINGQTY: To be used by Global/Regional Demand Planner.
• Equals to LOCALDEMANDPLANQTY as long as not overwritten manually.
• Global/Regional Demand Planner can manually enter their Demand numbers and with that overrule the
LOCALDEMAND- ADJSENSED-
plan of Local Demand Planners.
PLANQTY DEMANDQTY
• SENSEDDEMANDQTY: Used to store results of Demand Sensing algorithm.
• ADJSENSEDDEMANDQTY: To be used by (local) Demand Planner.
• Demand planner can optionally overrule the system generated SENSEDDEMANDQTY by manually DEMAND- FINALSENSED-
entering new numbers. PLANNINGQTY DEMANDQTY
• FINALSENSEDDEMANDQTY: To be used as final Demand Sensing qty.
• Final Sensed Demand as calculated by the algorithm taking into account manual overwriting of the
Demand Planner in key figure ADJSENSEDDEMANDQTY.

• COMBINEDFINALDEMAND: Calculated key figure.


• Equals to FINALSENSEDDEMANDQTY if there is date, otherwise equals to DEMANDPLANNINGQTY
=> Equals to FINALSENSEDDEMANDQTY in the past and near future (depending on how many future COMBINED-
periods are generated with Demand Sensing) and to the mid-/long-term plan afterwards. FINALDEMAND

Input to S&OP Input to Inventory Optimization

SOPDEMAND- IOFORECAST
PLANNINGQTY

132
Key Figures for Mid-term to Long-term Demand Planning
Statistical Key Figures

• STATISTICALFORECASTQTY: Used to store results of statistical forecasting.


• STATISTICALEXPOSTFORECASTQTY: Used to store ex-post forecast.

• FORECASTMAPE: Used to store


values of the MAPE error measures
(model fit error).
• Time-independent Key Figure

• FORECASTMASE: Used to store


values of the MASE error measure
(model fit error).
• Time-independent Key Figure

133
Key Figures for Mid-term to Long-term Demand Planning
Value / Price Key Figures

• DEMANDPLANNINGREV: Calculated Revenue:


DEMANDPLANNINGQTY * PLANNEDPRICE
• Currency dependent => currency conversion modelled

134
Key figures used for cleaning Sales History

• MEANACTUALSQTY: Mean of Actuals Qty


• Stored key figure used to store the Mean of key figure Actuals Qty
• Filled by running the sample forecast model StdDevActualsQty
• STDDEVACTUALSQTY : Standard Dev of Actuals Qty
• Stored key figure used to store the Standard Deviation of key figure Actuals Qty
• Filled by running the sample forecast model StdDevActualsQty

• STDDEVACTUALSQTYTS : Standard Dev of Actuals Qty (Time Serie)


• Calculated key figure used to show the time independent key figure STDDEVACTUALSQTY in Excel
Idea is to use these key figures for outlier detection within manual historical data cleanse activities. Example see Planning
Sheet Template “DP110 Historical Data Cleanse” of the IBP RDS.

135
Demand Sensing Key Figures

• Demand sensing requires many key figures that are used by the algorithms internally, but that are
typically not visible to or used by a Demand planner.

• There are certain naming conventions with regards to Demand sensing key figures. Demand
sensing can only be used if these naming conventions are fulfilled!

 Key figure definition of SAPIBP1 reflects this

136
Key Figures for Demand Sensing
Main Key Figures

• SENSEDDEMANDQTY: Output of the demand sensing algorithm SENSEDDEMANDQTY

• ADJSENSEDDEMANDQTY: To be used by the demand planner


• Optionally, the demand planner can manually enter data in order to overwrite the ADJSENSEDDEMANDQTY
SENSEDDEMANDQTY calculated by the system

• FINALSENSEDDEMANDQTY: To be used by follow-up


processes
• Final sensed demand – as calculated by the algorithm, taking into account manual overwrites
FINALSENSEDDEMANDQTY
of the demand planner

• DEMANDPLANNINGQTYSNAPSHOT: Used within the Demand


Sensing algorithm
• Contains weekly Snapshots of key figure DEMANDPLANNINGQTY

137
Key Figure Naming Conventions for Demand Sensing Algorithms (1)

• Mandatory naming convention for key figure IDs:


When demand sensing is used, the planning area must include the following key figure IDs:
FORECASTBIAS
FCTBIASMAPEIMPROV
FCTBIASWEIGHT0
FCTBIASWEIGHT1
FCTBIASWEIGHT2
FCTBIASWEIGHT3
FCTBIASWEIGHT4*
FCTBIASWEIGHT5*
FCTBIASWEIGHT6**
FCTBIASWEIGHT7**
FCTBIASWEIGHT8**
TOTALMAPEIMPROV

* In general optional key figures. When using Bias Horizon 5 + 6 (new with IBP 6.1) in the forecast model then these key
figures are mandatory as well.

** In general optional key figures. But when using “End of Quarter Handling” (new with 1705) these key figures are mandatory
as well
138
Key Figure Naming Conventions for Demand Sensing Algorithms (2)

Key figure ID conventions: Key figure IDs in SAPIBP1:


<forecast signal> = DEMANDPLANNINGQTY

<forecast signal> DEMANDPLANNINGQTY

<forecast signal>PROFILEWEIGHT DEMANDPLANNINGQTYPROFILEWEIGHT

<forecast signal>PROFILE0 DEMANDPLANNINGQTYPROFILE0

<forecast signal>PROFILE1 DEMANDPLANNINGQTYPROFILE1

<forecast signal>PROFILE2 DEMANDPLANNINGQTYPROFILE2

<forecast signal>PROFILE3 DEMANDPLANNINGQTYPROFILE3

<forecast signal>PROFILE4 DEMANDPLANNINGQTYPROFILE4

<forecast signal>PROFILE5 DEMANDPLANNINGQTYPROFILE5

<forecast signal>PROFILE6 DEMANDPLANNINGQTYPROFILE6

139
Key Figure Naming Conventions for Demand Sensing Algorithms (3)

Key figure ID conventions: Key figure IDs in SAPIBP1:


<open orders signal> = FUTUREORDEREDQTY

<open orders signal> FUTUREORDEREDQTYWEIGHT


<open orders signal>WEIGHT FUTUREORDEREDQTYINPUTFCTWGHT
<open orders signal>INPUTFCTWGHT FUTUREORDEREDQTYFCTADJUSTMENT
<open orders signal>FCTADJUSTMENT FUTUREORDEREDQTYMAPEIMPROV
<open orders signal>MAPEIMPROV FUTUREORDEREDQTYPROFILEWEIGHT
<open orders signal>PROFILEWEIGHT FUTUREORDEREDQTYPROFILE0
<open orders signal>PROFILE0 FUTUREORDEREDQTYPROFILE1
<open orders signal>PROFILE1 FUTUREORDEREDQTYPROFILE2
<open orders signal>PROFILE2 FUTUREORDEREDQTYPROFILE3
<open orders signal>PROFILE3 FUTUREORDEREDQTYPROFILE4
<open orders signal>PROFILE4 FUTUREORDEREDQTYPROFILE5
<open orders signal>PROFILE5 FUTUREORDEREDQTYPROFILE6
<open orders signal>PROFILE6

140
Key Figure Naming Conventions for Demand Sensing Algorithms (4)

Key figure ID conventions: Key figure IDs in SAPIBP1:


<sales signal> = ADJUSTEDDELIVQTY

<sales signal> ADJUSTEDDELIVQTY

<sales signal>PROFILE0 ADJUSTEDDELIVQTYPROFILE0

<sales signal>PROFILE1 ADJUSTEDDELIVQTYPROFILE1

<sales signal>PROFILE2 ADJUSTEDDELIVQTYPROFILE2

<sales signal>PROFILE3 ADJUSTEDDELIVQTYPROFILE3

<sales signal>PROFILE4 ADJUSTEDDELIVQTYPROFILE4

<sales signal>PROFILE5 ADJUSTEDDELIVQTYPROFILE5

<sales signal>PROFILE6 ADJUSTEDDELIVQTYPROFILE6

<sales signal>PROFILEWEIGHT ADJUSTEDDELIVQTYPROFILEWEIGHT

141
SAPIBP1: Key Figure Overview

• Key figures used for sales & operations


• Key figures used for supply
• Key figures used for inventory
• Key figures used for demand
• Key figures used for Control Tower
• Key figures related to order data
• Key figures related to Forecast Error Calculation
• Key figures related to Risk & Opportunities
• Special key figures
• „Integration“ key figures
142
Supply Chain Control Tower Key Figures

The key figures for Control Tower in SAPIBP1 include the following:
• SCM:10 KPIs • SCOR Cash to Cash: 8 KPIs
KPI: Target Stock Overage (Absolute) Inventory Value
KPI: Target Stock Overage (% of Location Products) Inventory Days of Supply based on Annual COGS
KPI: Target Stock Overage(Number of Location Products)
Inventory Turnover Ratio (based on Annualized COGS)
KPI: Safety Stock Deficit (Absolute)
KPI: Safety Stock Deficit (Number of Location Products) Cost of Goods Sold
KPI: Safety Stock Deficit (% of Location Products) Inventory Carrying Cost
KPI: Supply Shortage (ABS) Annual Average Inventory Cost Rate
KPI: Supply Shortage (Number of Location Products) Annualized COGS
KPI: Supply Shortage (% of Total Demand) Safety Days of Supply
KPI: Supply Shortage (% of Location Products)

• Inventory key figures based on stock types


• Valuation of all demand, supply, and inventory key figures
• Plan Adherence key figures

143
Control Tower KPIs Related to Supply Shortage
SUPPLYSHORTAGEABS: The supply shortage (ABS) KPI indicates the absolute value of the missing supply quantity for all location-products
and periods.
• Inputs: SHORTAGE
Calculation:

144
Control Tower KPIs Related to Supply Shortage
SUPPLYSHORTAGECOUNT: The supply shortage (Num Prod Loc) KPI indicates the total number of combinations with supply shortage for all
location-products and periods. Input: SUPPLYSHORTAGE.

Calculation:

145
Control Tower KPIs Related to Supply Shortage
SUPPLYSHORTAGEOCCPCT: The supply shortage (%Prod Loc) KPI indicates the percentage of combinations with supply shortage for all
location-products and periods.

Calculation:

146
Control Tower KPIs Related to Supply Shortage
SUPPLYSHORTAGEDEMANDPCT: The supply shortage (% of total demand) KPI indicates the percentage of the missing supply quantity
compared to the total demand for all location-products and periods.
This is a Request Level calculation based on inputs DEPENDENTDEMAND and SHORTAGE.

Calculation:

147
Control Tower KPIs Related to Inventory Target Overage or Stock Above Target
INVENTORYTARGETOVERAGEQTY: The target stock overage (ABS) KPI indicates the absolute value of the projected inventory above target
for all location-products and periods. Time aggregation: Average
Inputs: PROJECTEDINVENTORY, INVENTORYTARGET

Calculation:

148
Control Tower KPIs Related to Inventory Target Overage or Stock Above Target
INVENTORYTARGETOVERAGECOUNT: The target stock overage (Num Prod Loc) KPI indicates the total number of combinations with
Projected inventory over target for all location-products and periods. Time aggregation equals 1 if Target Stock Overage Count = 1 for any period, 0
otherwise.
Inputs: PROJECTEDINVENTORY, INVENTORYTARGET

Calculation:

149
Control Tower KPIs Related to Inventory Target Overage or Stock Above Target
INVENTORYTARGETOVERAGEOCCPCT: The target stock overage (%Prod Loc) KPI indicates the percentage of combinations with projected
inventory over target for all location-products and periods. Time aggregation: Average.
Inputs: PROJECTEDINVENTORY , INVENTORYTARGET

Calculation:

150
Control Tower KPIs Related to Safety Stock Deficit or
Stock Below Recommended Safety Stock

The safety stock deficit calculations are similar to target stock deficit with inputs to the calculation as projected inventory and recommended
safety stock.

1. Safety stock deficit (ABS)


The safety stock deficit (ABS) KPI indicates the absolute value of the projected inventory below safety stock for all location-products and
periods. Time aggregation: Average
ID: SAFETYSTOCKDEFICIT
2. Safety stock deficit (Num Prod Loc)
The safety stock deficit (Num Prod Loc) KPI indicates the total number of combinations with projected inventory below safety stock for all
location-products and periods. Time aggregation equals 1 if safety stock overage count = 1 for any period, 0 otherwise.
ID: SAFETYSTOCKDEFICITCOUNT
3. Safety stock deficit (% Prod Loc)
The safety stock (%Prod Loc) KPI indicates the percentage of combinations with projected inventory below safety stock for all location-
products and periods. Time aggregation: Average.
ID:SAFETYSTOCKDEFICITOCCPCT

151
Control Tower SCOR Cash to Cash KPIs
COGS: Cost of goods sold is the cost for a company to deliver goods sold to customers. This data is input from source system SAP ECC
calculated from direct material cost, direct labor cost, and indirect cost related to production.
AVGANNUALCOGS: Annualized COGS calculated as rolling value of cost of goods sold for past 1 year starting from current period.

INITIALINVENTORYVAL: Total inventory value is the valuated cost of all items held in inventory for the company. Raw material inventory
value + WIP inventory value + finished goods inventory value.
Calculation : INITIALINVENTORY * COSTPERUNIT

AVGANNUALTOTALINVENTORYVAL: Average Annual Inventory is the Rolling Average Value of Inventory for past 1 year starting from
Current Period.

152
Control Tower SCOR Cash to Cash KPIs
INVENTORYTURNOVERRATIO Inventory turnover ratio is the number of times the inventory must be replaced during a given year.
Calculation : Annualized COGS / Average annual inventory; calculated for current and future periods

INVENTORYDAYSOFSUPPLYCOGS: Inventory days of supply (based on Annualized COGS) indicates how many days it takes to sell the
inventory.
Calculation : 365 / Inventory turnover ratio; calculated for current and future periods

SAFETYDAYSSUPPLY: Days of supply is an attribute as key figure which gets filled with attribute value of SAFETYDAYSSUPPLY in
PRODUCTLOCATION master data type. Base planning level is day, product, and location. This key figure is used in many Control Tower relevant
key figure calculations to bring a weekly key figure to a daily value.
Eg. PROJECTEDINVENTORY@DAYPRODLOC = PROJECTEDINVENTORY@WKPRODLOC with Input KF :
SAFETYDAYSSUPPLY@DAYPRODLOC

153
Control Tower SCOR Cash to Cash KPIs
INVENTORYCARRYINGCOST: Inventory carrying cost is a stored key figure imported from ERP and is the total cost of holding inventory, e.g
Opportunity cost, obsolescence cost, shrinkage costs, taxes and insurance costs, and other warehousing costs.

INVENTORYCARRYINGCOSTRATE. Inventory carrying cost rate is a request level calculation based on key figures: Total inventory value / Inventory
carrying cost

ANNUALAVGINVENTORYCOSTRATE. Average annual inventory cost rate is the rolling average value of inventory carrying cost rate for past 1 year
starting from current time period.

154
Control Tower Key Figures Related to Consignment

• CONSIGNQMINVENTORYQTY: Consignment quantity – Inspection stock quantity. Imported key figure at day, product-
location level from ERP.

• CONSIGNRESTRICTEDINVENTORYQTY. Restricted-use consignment stock. Imported key figure at day, product-


location level from ERP.

• CONSIGNUNRESTRICTINVENTORYQTY . Unrestricted-use consignment stock. Imported key figure at day, product-


location level from ERP.

155
Control Tower – Inventory Key Figures

QMINVENTORYQTY – Quality inspection stock quantity. Imported key figure at day, product-location level from ERP.

QMINVENTORYVAL – Valuation of quality inspection stock quantity. Calculated as QMINVENTORYQTY * COSTPERUNIT.

RESTRICTEDINVENTORYQTY – Restricted stock quantity (includes the blocked stock). Imported key figure at day, product-location level from
ERP.

UNRESTRICTEDINVENTORYQTY – Unrestricted stock quantity. Imported key figure at day, product-location level from ERP.

UNRESTRICTEDINVENTORYVAL – Valuation of unrestricted stock quantity. Calculated as UNRESTRICTEDINVENTORYQTY * COSTPERUNIT.

AVGPROJECTEDINVENTORYQTY – When aggregated on time periods, this key figure returns the average value of the
PROJECTEDINVENTORY key figure instead of the last period aggregation.

AVGPROJECTEDINVENTORYVAL – Valuation of average projected inventory qty. Calculated as AVGPROJECTEDINVENTORYQTY *


COSTPERUNIT.

PROJECTEDINVENTORYCOST – contains the monetary value of the projected inventory. The quantity is weighted with the costs per unit and if
required converted to another currency

156
Control Tower – Other Supply Chain Management Costs Key Figures

TOTALDEMANDVAL – Valuation of dependent demand quantity at day, product, and location level. Calculated as DEPENDENTDEMAND *
COSTPERUNIT

TOTALPRODUCTIONVAL – Valuation of Total Production at Day, Product and Location Level. Calculated as PRODUCTION * COSTPERUNIT

TOTALRECEIPTSVAL – Valuation of total receipts quantity at day, product, and location level. Calculated as TOTALRECEIPT * COSTPERUNIT.

INTRANSITINVENTORYVAL – Valuation of in-transit receipts at day, product, and location level. Calculated as INTRANSIT * COSTPERUNIT.

INVENTORYSHORTAGEVAL – Valuation of supply shortage at day, product, and location level. Calculated as SHORTAGE * COSTPERUNIT.

INVENTORYTARGETVAL – Valuation of inventory target at day, product, and location level. Calculated as INVENTORYTARGET *
COSTPERUNIT.

PROJECTEDINVENTORYVAL – Valuation of Projected Inventory at day, product, and location level. Calculated as PROJECTEDINVENTORY *
COSTPERUNIT.

157
Control Tower Key Figures for Plan Adherence
• ACTUALSPRODUCTION. Actual production qty imported from ERP at day, product, location level. Used in the calculation of production accuracy key figure.

• ACTUALSTOCKTRANSFERS: Actual stock transfer qty imported from ERP at day, product, location, location-from level. Used in the calculation of Stock Transfer
Accuracy key figure.

• PRODUCTIONACCURACY. Used to calculate the production accuracy at day product, location level based on ACTUALSPRODUCTION and PRODUCTION key
figures.

• STOCKTRANSFERACCURACY: Used to calculate the production accuracy at day product, location, location-from level based on ACTUALSSTOCKTRANSFER
and TRANSPORT key figures.

• INVENTORYACCURACY: Used to calculate the inventory accuracy at day product, location level based on INITIALINVENTORY and PROJECTEDINVENTORY
key figures.

• SOPSUPPLYACCURACY: Used to calculate the inventory accuracy at day product, location level based on TOTALRECEIPT and its actuals key figures.

158
SAPIBP1: Key Figure Overview

• Key figures used for sales & operations


• Key figures used for supply
• Key figures used for inventory
• Key figures used for demand
• Key figures used for Control Tower
• Key figures related to order data
• Key figures related to Forecast Error Calculation
• Key figures related to Risk & Opportunities
• Special key figures
• „Integration“ key figures
159
Key Figures Related to Sales History

• DELIVQTY@DAYDELIVERY(base planning level): Imported key figure (from


ERP), order-based, delivered quantity at date of goods issue, history only.
• Delivery item level
• Used for demand sensing only Import Order Data Import Time Series Data
• ADJUSTEDDELIVQTY@DAYPRODLOCCUST: Stores adjustments to
delivered quantity to remove outliers.
• Can be used to “correct” the delivered quantity manually or by algorithm (outlier correction,
missing value substitution). DELIVQTY@DAY ACTUALSQTY@WK
ACTUALSREV
• Used for demand sensing only DELIVERY PRODLOCCUST
• ACTUALSQTY@WKPRODLOCCUST: imported key figure (from ERP),
delivered quantity at date of goods issue; history only.
• Used as sales history to compare against old/new demand plans in S&OP. ADJUSTEDDELIVQTY ADJUSTEDACTUALSQTY
• ADJUSTEDACTUALSQTY@WKPRODLOCCUST: Stores adjustments to @DAYPRODLOCCUST @WKPRODLOCCUST
actuals quantity to remove outliers.
• ACTUALSREV@WKPRODLOCCUSTCURR: Imported key figure (from
ERP), based on time series, actuals revenue at date of goods issue.
• Used in year-to-date analysis in demand planning.
• ACTUALSPRICE@WKPRODLOCCUSTCURR: Calculated key figure ACTUALSPRICE
representing the actuals price at product-location-customer level.
• Calculated as ACTUALSREV / ACTUALSQTY
• HACTUALSQTY: helper key figure to calculate ACTUALSPRICE
• ACTUALSQTYPRIORYEAR@WKPRODLOCCUST: Calculated key figure
representing actuals quantity of previous year shifted by 12 months.
• Used as sales history to compare against old/new demand plans in S&OP.

160
Other Order-Related Key Figures

• CONFQTY@DAYSALESORDER(base planning level): Imported key figure (from ERP), confirmed sales
orders = confirmed quantity at material availability date, history + future
Import Order Data
• Order Schedule line level
• Used for demand sensing
• HCONVCONFQTY CONFQTY REQQTY

• FUTUREORDEREDQTY@DAYPRODLOCCUST: Calculated key figure representing confirmed quantity with


future material availability date
• Aggregates CONFQTY to time series (product-location-customer) for future periods FUTUREORDER
• Used for demand sensing EDQTY
• HCONVFUTUREORDEREDQTY

• REQQTY@DAYSALESORDER: Imported key figure (from ERP), sales orders = requested quantity at
material availability date, history + future.
• Order Schedule line level
• May be used instead of CONFQTY (if required for demand sensing, manual adjustment to key figure
FUTUREORDEREDQTY need to be made)
• HCONVREQQTY

• OPENORDERSQTY@WKPRODLOCCUST: Imported key figure (from ERP), sales orders = requested


quantity at delivery date, history + future.
• Order item level
• Used for downside scenario evaluation in S&OP Import Time Series Data
• OPENORDERSREV@WKPRODLOCCUSTCURR: Imported key figure (from ERP), sales revenue at delivery
date, history + future
• Used in year-to-date analysis in demand planning OPENORDERS OPENORDERS
QTY REV

161
Field Mapping Between ECC Orders and IBP Master Data Types

MDT IBPSALESORDER: MDT IBPDELIVERY:


IBP attributes ECC Source ECC FIELD IBP attributes ECC Source ECC FIELD

SALESDOC 2LIS_11_VASCL VBELN DELIVERY 2LIS_12_VCITM VBELN


SALESITEM 2LIS_11_VASCL POSNR DELIVERYITEM 2LIS_12_VCITM POSNR
SCHLINE 2LIS_11_VASCL ETENR SOLDTO 2LIS_12_VCITM KUNAG
SOLDTO 2LIS_11_VASCL KUNNR ACTMOVEDATE 2LIS_12_VCITM WADAT_IST
ORDERCREATEDATE 2LIS_11_VASCL ERDAT DELIVQTY 2LIS_12_VCITM LGMNG
MATAVAILDATE 2LIS_11_VASCL MBDAT CUSTID 2LIS_12_VCITM KUNAG
CONFQTY 2LIS_11_VASCL BMENG LOCID 2LIS_12_VCITM WERKS
REQQTY 2LIS_11_VASCL WMENG PRDID 2LIS_12_VCITM MATNR
CUSTID 2LIS_11_VASCL KUNNR UOMID 2LIS_12_VCITM MEINS
LOCID 2LIS_11_VASCL WERKS
PRDID 2LIS_11_VASCL MATNR
UOMID 2LIS_11_VASCL MEINS

MDT = Master Data Type

162
SAPIBP1: Key Figure Overview

• Key figures used for sales & operations


• Key figures used for supply
• Key figures used for inventory
• Key figures used for demand
• Key figures used for Control Tower
• Key figures related to order data
• Key figures related to Forecast Error Calculation
• Key figures related to Risk & Opportunities
• Special key figures
• „Integration“ key figures
163
Key Figures Related to Forecast Error Calculation
General Remarks

From business point of view there are several possibilities which forecast errors are calculated on
which level and for which lags. Within SAPIBP1 the following assumptions are made:
• For Demand and S&OP purposes:
• Forecast Accuracy is measured for Statistical Forecast Qty, Consensus Demand Plan Qty, Consensus Demand
Final and Combined Final Demand
• Forecast Error is calculated and stored in monthly buckets for 1 Month and 3 Months Lag
• Beside of the forecast error the corresponding forecast bias are calculated and stored as well
• All these calculations are done on Product/Location/Customer-Level
• Exactly one forecast error measure is used (e.g. MAPE)
• For IO purposes:
• Forecast Accuracy is measured for key figure Demand Forecast
• Forecast Error is calculated time independent – means Lag = 0
• Beside of the forecast error the corresponding forecast bias are calculated and stored as well
• All these calculations are done on Product/Location/CustomerGroup-Level
• Exactly one forecast error measure is used. For IO this is typically Coefficient of Variation (CV)

 SAPIBP1 is build up based on these assumptions


 In case there are other requirements, changes to the planning area setup are needed
164
Key Figures Related to Forecast Error Calculation
Demand & S&OP: Key Figure Description

Statistical Forecast Qty:


• STATISTICALFORECASTQTYLAG: Lag-specific key figure, means “LAG” is used as root. Used to store the snapshots of key figure
STATISTICALFORECASTQTY for all relevant monthly lags (in our example 1M lag + 3M lag).
• STATISTICALFORECASTQTYERROR: Contains the calculated Statistical Forecast Qty Error per month and by lag (in our example 1M lag +
3M lag)
• STATISTICALFORECASTQTYBIAS: Contains the calculated Statistical Forecast Qty Bias per month and by lag (in our example 1M lag + 3M
lag)

Consensus Demand Plan Qty:


• CONSENSUSDEMANDQTYLAG: Lag-specific key figure, means “LAG” is used as root. Used to store the snapshots of key figure
CONSENSUSDEMANDQTY for all relevant monthly lags (in our example 1M lag + 3M lag).
• CONSENSUSDEMANDQTYERROR: Contains the calculated Consensus Demand Qty Error per month and by lag (in our example 1M lag + 3M
lag)
• CONSENSUSDEMANDQTYBIAS: Contains the calculated Consensus Demand Qty Bias per month and by lag (in our example 1M lag + 3M
lag)

165
Key Figures Related to Forecast Error Calculation
Demand & S&OP: Key Figure Description

Consensus Demand Final:


• FINALCONSENSUSDEMANDQTYLAG: Lag-specific key figure, means “LAG” is used as root. Used to store the snapshots of key figure
FINALCONSENSUSDEMANDQTY for all relevant monthly lags (in our example 1M lag + 3M lag).
• FINALCONSENSUSDEMANDQTYERROR: Contains the calculated Consensus Demand Final Error per month and by lag (in our example 1M
lag + 3M lag)
• FINALCONSENSUSDEMANDQTYBIAS: Contains the calculated Consensus Demand Final Bias per month and by lag (in our example 1M lag
+ 3M lag)

Combined Final Demand:


• COMBINEDFINALDEMANDLAG: Lag-specific key figure, means “LAG” is used as root. Used to store the snapshots of key figure
COMBINEDFINALDEMAND for all relevant monthly lags (in our example 1M lag + 3M lag).
• COMBINEDFINALDEMANDERROR: Contains the calculated Combined Final Demand Error per month and by lag (in our example 1M lag + 3M
lag)
• COMBINEDFINALDEMANDBIAS: Contains the calculated Combined Final Demand Bias per month and by lag (in our example 1M lag + 3M
lag)

166
Key Figures Related to Forecast Error Calculation
Demand & S&OP: How to Retrieve the Lag-Specific Key Figure Data

Illustration how the STATISTICALFCSTQTYLAG data is retrieved from STATISTICALFCSTQTY by using the Lag Based Snapshot operator.
LAG = 1:

STATISTICALFCSTQTYLAG, LAG = 1
STATISTICALFCSTQTYLAG, LAG = 3

167
Key Figures Related to Forecast Error Calculation
Demand & S&OP: How to Retrieve the Lag-Specific Key Figure Data

Illustration how the STATISTICALFCSTQTYLAG data is retrieved from STATISTICALFCSTQTY by using the Lag Based Snapshot operator.
LAG = 3:
:

STATISTICALFCSTQTYLAG, LAG = 1
STATISTICALFCSTQTYLAG, LAG = 3

168
Key Figures Related to Forecast Error Calculation
Demand & S&OP: Forecast Error and Bias Calculation

The picture below illustrates how the 3M Lag Statistical Forecast Qty Error + Bias is calculated:
• Input key figures:
• STATISTICALFORECASTQTYLAG, LAG = 3: Historical created 3M Lag forecast as illustrated in the slide before
• ADJDELIVQTY: representing the Sales History
• Output key figures:
• STATISTICALFORECASTQTYERROR: calculate forecast error per month is stored in this key figure for Lag = 3
• STATISTICALFORECASTQTYBIAS: calculate forecast bias per month is stored in this key figure for Lag = 3

STATISTICALFORECASTQTYLAG, LAG = 3 ADJDELIVQTY


Statistical Forecast Qty Snap Shot Delivered Qty Adjusted

Calculation as defined in the Forecast Error Profile

STATISTICALFORECASTQTYERROR, LAG = 3
Statistical Forecast Error (%)

STATISTICALFORECASTQTYBIAS, LAG = 3
Statistical Forecast Bias (%)

169
Key Figures Related to Forecast Error Calculation
Demand & S&OP: Key Figure Overview

Key Figure ID Stored Calculated System UoM Lag Specific Lowest Time
Editable Conversion Storage Granularity

STATISTICALFORECASTQTYLAG X X X X Month

STATISTICALFORECASTQTYBIAS X X X Month

STATISTICALFORECASTQTYERROR X X X Month

CONSENSUSDEMANDQTYLAG X X X X Month

CONSENSUSDEMANDQTYBIAS X X X Month

CONSENSUSDEMANDQTYERROR X X X Month

FINALCONSENSUSDEMANDQTYLAG X X X X Month

FINALCONSENSUSDEMANDQTYBIAS X X X Month

FINALCONSENSUSDEMANDQTYERROR X X X Month

COMBINEDFINALDEMANDLAG X X X X Month

COMBINEDFINALDEMANDBIAS X X X Month

COMBINEDFINALDEMANDERROR X X X Month

170
Key Figures Related to Forecast Error Calculation
Demand & S&OP: Forecast Error Calculation Process Example

The process steps of creating a new statistical forecast,


create snapshot data and calculate the forecast error
could look like this example:
Batch Job with several steps:
• Run statistical forecast job: New Statistical forecast is
created
• Create 1M and 3M Lag snapshot: run Lag-Based Snapshot
operator with settings like this:
• Calculate new Statistical Forecast Error + Bias

There are several options to schedule these steps in a certain


order. Important to mention is that this can be automatized to a
large extend.

171
Key Figures Related to Forecast Error Calculation
IO: Key Figure Description

• IOCV: Contains the latest calculated forecast error on product-location-customer group level
• Time independent key figure used to store the error calculated by the algorithm

• IOFORECASTERRORCV: Can be used to manually overwrite the system calculated forecast error or to load the forecast error from an
external data source

• IOFCSTBIASCALCULATED: Contains the latest calculated forecast bias on product-location-customer group level
• Time independent key figure used to store the bias calculated by the algorithm

• IOFCSTBIASUSED: Contains the forecast bias that is used to adjust historical forecasts and calculate the forecast error. It can be different
than the IOFCSTBIASCALCULATED which is calculated by the algorithm. For example, if user only wants to adjust forecast when there is
positive forecast bias in the calculation of forecast error (this is configurable in the forecast error profile), IOFCSTBIASUSED will be zero
when IOFCSTBIASCALCULATED is negative
• Time independent key figure used to store the error calculated by the algorithm

172
Key Figures Related to Forecast Error Calculation
IO: Key Figure Overview

Key Figure ID Stored Calculated Editable UoM Lag Specific Lowest Time
Conversion Storage Granularity

IOCV X X n.a.
IOFORECASTERRORCV X X X Technical week
IOFCSTBIASCALCULATED X X n.a.
IOFCSTBIASUSED X X n.a.

173
Key Figures Related to Forecast Error Calculation
Profiles for Forecast Error Calculation
Four profiles for creating create new lag-based snapshot are shipped together with SAPIBP1. As soon as you make a copy
of SAPIBP1 and activate the new planning area you can see these four profiles:
• “Manage Lag-Based Snapshots” App:
• “STATISTICALFORECASTQTYLAG“
• “CONSENSUSDEMANDQTYLAG”
• “FINALCONSENSUSDEMANDQTYLAG”
• “COMBINEDFINALDEMANDLAG”

Three profiles for Forecast Error Calculation are shipped together with SAPIBP1. As soon as you make a copy of SAPIBP1
and activate the new planning area you can see these three profiles:
• Two profiles in the “Forecast Error Calculations for Demand Planning” App (used for Demand & S&OP):
• Profile “DP_Forecast_Error“
• Profile “SOP_Forecast_Error“

• One profile in the “Forecast Error Calculations for Inventory Optimization” App (used for IO):
• Profile “IO_ForecastErrorCV“

These profiles are examples for SAPIBP1 and can be used as they are shipped or modified/copied as needed.

174
SAPIBP1: Key Figure Overview

• Key figures used for sales & operations


• Key figures used for supply
• Key figures used for inventory
• Key figures used for demand
• Key figures used for Control Tower
• Key figures related to order data
• Key figures related to Forecast Error Calculation
• Key figures related to Risk & Opportunities
• Special key figures
• „Integration“ key figures
175
Key Figures Related to “Risks and Opportunities”
• New key figures:
• ROAGGSLSQT “RO Agg Sales Quantity”: This is the key figure for which you enter the value for the risk or opportunity
in the Driver-Based Planning app.
Added to UPSIDE and DOWENSIDE version
• ROCALCSALESQTY “RO Calc Sales Qty”: Used to view the impact of each risk or opportunity at the level of
the Consensus Demand Qty key figure. This key figure uses a split factor calculation to calculate
the ROAGGSALESQTY key figure at the MTHROPRODLOCCUST planning level. Added to UPSIDE and DOWNSIDE
version
• CONSENSUSCALCROQTY “Consensus Demand Qty with RiskOpp”: Shows the Consensus Demand Qty key figure
considering risks and opportunities that are included in the plan
Added to UPSIDE and DOWENSIDE version

• New helper key figures: These are used to perform a split factor based calculation to bring a Risk/Opp
defined at an aggregate planning level to the level of the forecast key figure and include the approved risks
and opportunities to the Consensus Demand Plan
• HCONSENSUSDEMANDQTYRO
• HAGGCONSENSUSDEMANDQTYRO
• HDEMANDRATIO
• HROSALESQTYINPLAN
176
SAPIBP1: Key Figure Overview

• Key figures used for sales & operations


• Key figures used for supply
• Key figures used for inventory
• Key figures used for demand
• Key figures used for Control Tower
• Key figures related to order data
• Key figures related to Forecast Error Calculation
• Key figures related to Risk & Opportunities
• Special key figures
• „Integration“ key figures
177
Special Key Figures - Conversions

Two “Attributes as Key Figures” are used for


Unit of Measure (UoM) and currency conversion of
several other key figures:
• UOMCONVERSIONFACTOR
• EXCHANGERATE

“Attributes as Key Figure” means:


• Key figure is modelled as attribute with data type
“Decimal” as part of a master data type (MDT)
• When assigning this MDT and attribute to the
planning area, you need to assign a planning level
and a key figure is created by the system
• Key figure is showing up as normal key figure in the
planning area
• Key figure values are time-independent
• Key figures can be used for calculations: same value
is used in each time bucket
• Key figure data can be filled during upload of the
corresponding master data type

178
Special Key Figures - Conversions

The calculated key figure EXCHANGERATEUOMCONVERSION is needed to define the UoM and currency
conversion for key figure COSTPERUNIT.

179
Special Key Figures - Conversions

Several helper key figures are needed to support UoM conversion for demand sensing algorithms.
These helper key figures are only used by the system internally when executing demand sensing
algorithms and are not relevant for the users.

• The 5 helper key figures are following the naming


convention “HCONV” + <key figured ID of
converted key figure>.

• The following helper key figures are needed for all


input key figures of the used demand sensing
forecast model:
Helper Key Figure used to convert…
HCONVADJUSTEDDELIVQTY ADJUSTEDDELIVQTY
HCONVCONFQTY CONFQTY
HCONVDEMANDPLANNINGQTY DEMANDPLANNINGQTY
HCONVREQQTY REQQTY
HCONVFUTUREORDEREDQTY FUTUREORDEREDQTY
HCONVDEMANDPLANNINGQTYSNAP DEMANDPLANNINGQTYSNAP

180
Special Key Figures - Conversions

Several helper key figures are needed to support UoM conversion for the “Manage Lag-Based Snapshot”
app.

• The helper key figures are following the naming convention


“HCONV” + <key figured ID of converted key figure>.

• The following helper key figures are needed for all source
key figures of the Manage Lag-Based Snapshot calculation:
Helper Key Figure used to convert…
HCONVSTATISTICALFORECASTQTY STATISTICALFORECASTQTY
HCONVCOMBINEDFINALDEMAND COMBINEDFINALDEMAND
HCONVCONSENSUSDEMANDQTY CONSENSUSDEMANDQTY
HCONVFINALCONSENSUSDEMANDQTY FINALCONSENSUSDEMANDQTY

181
Special Key Figures

ADJUSTEDDELIVQTYHELPER
• It is required for enabling to manually overwrite data for ADJUSETEDDELIVQTY.
• It has no business meaning and is only needed for modelling purposes.
• Uses the Advanced Simulation Planning Operator (ADVSIM) in order to have stored values that can be used for disaggregation of
ADJUSTEDDELIVQTY.
• ADJUSTEDDELIVQTY is calculated based on the key figure DELIVQTY, which is stored on another level. Such values cannot be used
for disaggregation via Excel. Therefore, you need a stored “helper” key figure, in our example this is ADJUSTEDDELIVQTYHELPER,
used for the disaggregation.

182
Special Key Figures

The fixing functionality is activated for key figure LOCALDEMANDPLANQTY. With that, two
technical key figures are created by the system automatically during planning area activation.
These technical key figures are used internally only and are not relevant for other purposes:

183
Special Key Figures

PERIODID1 refers to Yearly time period. The Attribute Transformation of PERIODID1 offsets the time period by 1
year for the input Key Figure ACTUALQTYPRIORYEAR@WKPRODLOCCUST.

184
Special Key Figures

PERIODID2 refers to Quarterly time period. The Attribute Transformation of PERIODID2 offsets the time period by
4 quarters (that is, 1 yr) for the input Key Figure ACTUALQTYPRIORYEAR@WKPRODLOCCUST.

185
Special Key Figures

PERIODID3 refers to Monthly time period. The Attribute Transformation of PERIODID3 offsets the time period by
12 months for the input Key Figure ACTUALQTYPRIORYEAR@WKPRODLOCCUST

186
Special Key Figures

PERIODID4 refers to Weekly time period. The attribute transformation of PERIODID4 offsets the time period by 52 weeks (i.e. 1
yr) for the input Key Figure ACTUALQTYPRIORYEAR@WKPRODLOCCUST.

187
Special Key Figures

PERIODID refers to technical week time period. The Attribute Transformation of PERIODID5 offsets the time
period by 62 technical weeks for the input Key Figure ACTUALQTYPRIORYEAR@WKPRODLOCCUST

188
Helper Key Figures Supporting the Calculation of Other Key Figures

• HACTUALSQTY – Used in weighted average calculation of ACTUALSPRICE


• HGROSSCOSTS – Used in gross profit key figure to calculate gross costs
• HINVTARGETDEFICITCOUNT – Used in stock below target KPI for intermediate calculations
• HINVTARGETDEFICITPERC – Used in stock below target KPI for intermediate calculations
• HINVTARGETOVERAGECOUNT – Used in stock over target KPI for intermediate calculations
• HINVTARGETOVERAGEOCCPCT – Used in stock over target KPI for intermediate calculations
• HINVTARGETOVERAGEQT – Used in stock below over KPI for intermediate calculations
• HPCAPAUSAGE – Used in UTILIZATIONPCT key figure to bring input key figures at request level to same planning level

189
Helper Key Figures Supporting the Calculation of Other Key Figures

• HPSAFETYSTOCKOVERAGECOUNT – Used in stock over safety KPI for intermediate calculations


• HSAFETYSTOCKDEFICIT – Used in stock below safety KPI for intermediate calculations
• HSAFETYSTOCKDEFICITCOUNT – Used in stock below safety KPI for intermediate calculations
• HSAFETYSTOCKDEFICITOCCPCT – Used in stock below safety KPI for intermediate calculations
• HSAFETYSTOCKOVERAGEQTY – Used in stock below safety KPI for intermediate calculations
• HSUPPLYSHORTAGEDEMANDPCT – Used in supply shortage KPI intermediate calculations
• HSUPPLYSHORTAGEDEMANDPERC – Used in supply shortage KPI intermediate calculations

190
New Helper Key Figures

for UOM Conversion in Inventory Optimization Key Figures (IBP 1911)

Key Figure ID Configuration Changes


HCONVRECOMMENDEDSAFETYSTOCK HCONVDEPENDENTLOCTOPRDDEMANDMEAN

HCONVIOMAXINVENTORY HCONVDEPENDENTLOCTOPRDDEMANDSTDD

HCONVIOMINSTOCKREQUIREMENT HCONVDEPENDENTSRCTOLOCDEMANDMEAN

HCONVIOFORECAST HCONVDEPENDENTSRCTOLOCDEMANDSTDD

HCONVIOSALES HCONVOUTGOINGSRCTOLOCBACKLOGMEAN

HCONVTMINLOTSIZE HCONVOUTGOINGSRCTOLOCBACKLOGSTDD

HCONVTINCLOTSIZE HCONVCALCPMINLOTSIZE

HCONVPMINLOTSIZE

HCONVPINCLOTSIZE

191
SAPIBP1: Key Figure Overview

• Key figures used for sales & operations


• Key figures used for supply
• Key figures used for inventory
• Key figures used for demand
• Key figures used for Control Tower
• Key figures related to order data
• Key figures related to Forecast Error Calculation
• Key figures related to Risk & Opportunities
• Special key figures
• „Integration“ key figures
192
Integration Key Figures

Input key figures from other IBP applications Output key figures to other IBP applications

• SOPDEMANDPLANNINGQTY (copy of last cycle DEMANDPLANNINGQTY) • CONSENSUSDEMANDQTY


S&OP • FINALCONSENSUSDEMANDQTY

• SOPSAFETYSTOCK (copy of last cycle FINALIOSAFETYSTOCK) • CONSTRAINEDDEMAND


• CONSENSUSDEMAND (copy from CONSENSUSDEMANDQTY)

Supply

• FINALCONSENSUSDEMANDQTY • DEMANDPLANNINGQTY
Demand • FINALSENSEDDEMANDQTY
• COMBINEDFINALDEMAND

• IOFORECAST (defaults to COMBINEDFINALDEMAND) • FINALIOSAFETYSTOCK


Inventory

• COMBINEDFINALDEMAND (copy Combined Final Demand from SAPIBP1 to • FORECASTCONSTR (copy Forecast Constrained from SAP74 to
Order-Based SAP74) SAPIBP1)
Planning

193
Integration Key Figures from External Systems to IBP

IBP Input key figures IBP Input key figures


components components
S&OP, DP, IO EXCHANGERATE@MTHCURRCURRTO DP FUTUREORDEREDQTY@DAYPRODLOCCUST
S&OP, DP ACTUALSQTY@DAYPRODLOCCUST DP, DS CONFQTY@DAYSALESORDER (Master Data)
S&OP, DP ACTUALSREV@WKPRODLOCCUSTCURR DP, DS DELIVQTY@DAYDELIVERY (Master Data)
S&OP, DP AOPQTY@MTHPRODCUST S&OP INITIALINVENTORY@WKPRODLOC
S&OP, DP AOPREV@MTHPRODCUSTCURR S&OP, IO INVENTORYHOLDINGCOSTRATE@WKPRODLOC
S&OP, DP AOPPROFIT@MTHPRODCUSTCURR S&OP EXTERNALRECEIPTCOSTRATE@WKPRODLOC
S&OP, DP SALESFORECASTQTY@WKPRODLOCCUST S&OP INVENTORYTARGETVIOLATIONCOSTRATE@WKPRODLOC
S&OP, DP PLANNEDPRICE@WKPRODCUSTCURR IO IOFORECASTERRORCV@WKPRODLOCCUSTGROUP
S&OP MARKETINGFORECASTQTY@WKPRODCUST IO TARGETSERVICELEVEL@WKPRODLOCCUSTGROUP
S&OP MARKETSIZEREV@WKPRODCUSTCURR IO COSTPERUNIT@WKPRODLOCCURR
S&OP OPPORTUNITIESQTY@WKPRODCUST
S&OP OPPORTUNITIESREV@WKPRODCUSTCURR
• These are all key figures which hold data extracted from
S&OP OPENORDERSQTY@WKPRODLOCCUST external systems
S&OP OPENORDERSREV@WKPRODLOCCUSTCURR • All of these key figures are required to execute the end-to-end
process as defined for the planning area
S&OP NONDELIVERYCOSTRATE@WKPRODCUST • SAP HANA Integrated Business Planning rapid-deployment
S&OP INDIRECTCOSTS@WKPRODCUSTCURR solution provides CSV files with sample data for all of these
S&OP CUSTOMERRATIO@WKPRODLOCCUST input key figures and for all required master data

S&OP CUSTOMERTRANSPORTATIONCOSTRATE@WKPRODLOC
CUST
S&OP PRODUCTIONCOSTRATE@WKPRODLOCSRC
IBP components:
S&OP CAPASUPPLY@WKRESLOC DP: IBP for demand – demand planning
DS: IBP for demand – demand sensing
S&OP ALRTCAPACITYOVERLOADTHRESHOLD@WKRESLOC IO: IBP for inventory
S&OP: IBP for sales and operations
S&OP PCAPACONSUMPTION@WKRESPRODLOCSRC

194
Output Key Figures from IBP to External Systems

IBP components Output key figures

S&OP FINALCONSENSUSDEMANDQTY@WKPRODLOCCUST

DP DEMANDPLANNINGQTY@WKPRODLOCCUST

DS FINALSENSEDDEMANDQTY@DAYPRODLOCCUST

DP+DS COMBINEDFINALDEMAND@WKPRODLOCCUST

IO IOINVENTORYTARGET@WKPRODLOC

• These key figures contain the results of the IBP planning applications included in this planning area
• They can be extracted to other planning and operational systems

IBP components:
DP: IBP for demand – demand planning
DS: IBP for demand – demand sensing
IO: IBP for inventory
S&OP: IBP for sales and operations

195
Agenda

• SAPIBP1: What's New in 2002

• SAPIBP1: General Remarks

• SAPIBP1: Key Figure Overview

• SAPIBP1: Master Data Overview

• SAPIBP1: Planning Level Overview

• SAPIBP1: General Planning Area Settings

• SAPIBP1: Changes in earlier releases

196
SAPIBP1 – Master Data
Overview
SAPIBP1: Master Data Types

Master data types, used in SAPIBP1 (Prefix: IBP…):


Master Data Type Used for modeling of…

IBPPRODUCT Product-related attributes

IBPLOCATION Location-related attributes

IBPCUSTOMER Customer-related attributes

IBPCOMPONENT Definition of a component for bill of materials

IBPCURRENCY Available currencies (currency from)

IBPCURRENCYTO Available currencies (currency to)

IBPCUSTOMERPRODUCT Customer-Product specific attribute values

IBPDELIVERY Order data

IBPEXCHANGERATE Currency conversion factors

IBPLAG Counter for Lag in weeks (0, 1, 2, …)

IBPLOCATIONFR Starting location for transport relations

IBPLOCATIONPRODUCT Location-Product specific attribute values

IBPLOCATIONPRODUCTCURRENCY Location-Product specific costs

IBPLOCATIONTO Ship-to related attributes

IBPPLANNINGUNIT Sub-Network

198
SAPIBP1: Master Data Types
Master Data Type Used for modeling of…

IBPPRODUCTIONRESOURCE Capacity Consumption Rate for Production Resources

IBPPRODUCTIONSOURCEITM Maintaining BOM

IBPPRODUCTSUBSTITUTION Product Substitution for mapping products

IBPPRODUCTTO Output product. Modeled as reference to Product

IBPRESOURCE Resources

IBPRESOURCELOCATION Available Capacity or Capacity Supply at Resource Location level

IBPRESOURCELOCATIONPRODUCT Capacity Consumption Rate for Handling Resources

IBPSALESORDER Order data

IBPSERVICELEVELCLASS IO Target Service Level based on ABC Segmentation

IBPSOURCECUSTOMER Sourcing location for customers

IBPSOURCECUSTOMERGROUP Defines demand stream for inventory target calculation

IBPSOURCELOCATION Defines the transport relation between two locations

IBPSOURCEPRODUCTION Defines the sourcing (production or external procurement)

IBPUOMCONVERSIONFACTOR UoM conversion factor

IBPUOMTO Available units of measure

IBPAGGCONSTRAINT Aggregated constraints

IBPPRODUCTIONSOURCEITMSUB Production Source Item Substitution

IBPPRODUCTIONSOURCEITMR Production Source Item Reference

199
SAPIBP1: Master Data Types
Master Data Type Used for modeling of…

IBPTRANSPORTATIONRESOURCE Consumption of the transportation resource

IBPFORECASTCONSUMPTIONMODE Forecast Consumption Mode

IBPPRIORITY Priority

IBPRISKOPP Risk / Opportunity

IBPASSUMPTIONCATEGORY Assumption Category

IBPROPTYPE Risk / Opportunity Type

200
IBPPRODUCT Master Data Type

Remarks
• MDT “Simple”
• Key: PRDID
• Defines the common properties of a product,
e.g. the family etc.
• In IBP for supply the product ID corresponds
to a material number in ERP
• Mandatory attributes:
• PRDID

201
IBPLOCATION Master Data Type

Remarks
• MDT “Simple”
• Key: LOCID
• A location is often a physical place
where products are stored, produced,
shipped to or shipped from (via a
transport).
• The locations can be of type distribution
centers, manufacturing plants
• Two additional master data types ship-
from location (IBPLOCATIONFR) and
ship-to (IBPLOCATIONTO) are
required. These are modeled as
reference master data types.

202
IBPLOCATIONFR, IBPLOCATIONTO Master Data Types

IBPLOCATIONFR IBPLOCATIONTO

Remarks Remarks
• MDT “Reference”. Referring to MDT • MDT “Reference”. Referring to MDT IBPLOCATION
IBPLOCATION
• Key: LOCTO
• Key: LOCFR

• Defines the starting point for transport relations


between two locations

203
IBPCUSTOMER Master Data Type

Remarks
• MDT “Simple”
• Key: CUSTID
• Products are sold to and shipped to
customers.
• Mandatory attributes:
• CUSTID
• CUSTGROUP
− mandatory for inventory optimization
− Defines the customer group (demand
channel) a customer belongs to
− The properties of this customer are
defined by the
SOURCECUSTGROUP.
There you can e.g. define the target
service level for inventory
optimization.
204
Master data type IBPCOMPONENT

Remarks

• MDT “Reference”. Referring to MDT IBPPRODUCT

• Key: PRDFR

• Components are products that are used as inputs in the


production process

205
IBPCURRENCY, IBPCURRENCYTO, IBPEXCHANGERATE Master Data Types

Remarks
3 different MDTs used for
currency conversion
• IBPCURRENCY (MDT Simple)

• IBPCURRENCYTO (MDT Reference)

• IBPEXCHANGERATE (MDT Compound)

206
IBPCUSTOMERPRODUCT Master Data Type

Remarks
• MDT “Compound”
• Key: CUSTID, PRDID

207
IBPLAG Master Data Type

Remarks
• MDT “Simple”
• Key: LAG
• Mandatory attribute LAG with data
type Integer
• Used for lag information (in weeks)
within IBP for demand (demand
sensing)
• Used for lag information (in months)
for forecast error calculations

208
IBPUOMTO and IBPUOMCONVERSIONFACTOR Master Data Types

Remarks
• 2 different MDTs used for Unit of Measure conversion
(simple and compound)
• IBPUOMCONVERSIONFACTOR has PRDID as key
 Link to product-specific Unit of Measure modelled within MDT
IBPPRODUCT
209
IBPSALESORDER, IBPDELIVERY Master Data Types

Remarks
• 2 different MDTs used for order modeling

210
IBPLOCATIONPRODUCT Master Data Type Remarks
• MDT “Compound”
• Key: LOCID, PRDID

New Attributes in 1911:


- IGNOREPDEPLOCDEM (Ignore Dependent Location Demand)
- IGNOREDEPPRODDEM (Ignore Dependent Production Demand)
211
IBPPLANNINGUNIT Master Data Type

Remarks
• MDT “Simple”
• Used for defining the sub-networks in the customer supply chain network

212
IBPPRODUCTIONRESOURCE Master Data Type

Remarks

• MDT “Simple”, Key RESID, SOURCEID

• Production resource master data defines the


resource consumption of production resource

• It is the amount of capacity consumed per unit of


product produced

• Can be modeled as time-independent or time-


dependent key figure

213
IBPPRODUCTSUBSTITUTION Master Data Type

Remarks

• MDT “Compound” Key PRDID, SPRDID

• Used for maintaining the substitution relationship for customer demand

214
IBPPRODUCTTO Master Data Type

Remarks

• MDT “Reference”

• Used for modeling the output product in


production process

215
IBPRESOURCE Master Data Type

Remarks

• MDT “Simple”

• KEY: RESID

• In IBP for supply two types of resources can be modeled: production and handling resources.

• Production resources model a production or assembly process. Their capacity is consumed per produced or assembled
unit of product.

• Handling resources apply to all goods receipts at a location in the sense that each arriving unit of a product consumes a
certain capacity unit of the resource.
216
IBPRESOURCELOCATION Master Data Type

Remarks
• MDT “Compound”
• KEY: LOCID, RESID
• Available capacity or capacity supply is defined
at resource-location level
• Can be modeled as time-dependent key figure
(CAPASUPPLYTS) or time-independent attribute
‘CAPASUPPLY’
• Resources can be modeled as finite or infinite.
Constraint Type ‘F’ is finite. Blank is infinite.

217
IBPRESOURCELOCATIONPRODUCT Master Data Type

Remarks
• MDT “Compound”
• Mandatory attributes: PRDID, LOCID,
RESID?
• Used for modeling capacity consumption
rate of handling resources

218
IBPSERVICELEVELCLASS Master Data Type

Remarks
• MDT “Simple”
• Service level classes define target service level for each ABC segmentation

219
IBPSOURCECUSTOMER Master Data Type

Remarks
• MDT “Compound”
• Sourcing rules define how a demand for customer or at a certain location has to be satisfied.
• IBP for supply distinguishes between sourcing rules for customer demand (Customer Ratio or C-Rule), for transportation (Transportation Ratio or T-Rule),
production (P-Rule), and unspecified (U-Rule).
• Source customer master data defines how the customer demand is satisfied.
220
IBPSOURCECUSTOMER Master Data Type (cont.)

Customer source (C-Rule):


• Defines from which location (distribution center, plant or supplier) of the supply network a customer demand has to be
satisfied in what percentage.
• Customer sourcing can be maintained as time-dependent or time-independent.
• It also describes the lead time for shipping to the customer.

Master data key figure – Customer sourcing quota:


• This input key figure contains the quotas for sourcing customer demand for a product from various ship-from locations.
• These quotas are respected by the heuristics but not by the optimizer.

221
IBPSOURCECUSTGROUP Master Data Type

Remarks
• MDT “Simple”
• Key: CUSTGROUP, PRDID, LOCID
• Connects the customers via the CUSTGROUP to a
product and a location
• Mandatory attributes: TARGETSERVICELEVEL

222
IBPSOURCELOCATION Master Data Type

Remarks
• MDT “Compound”
• Key: LOCID, LOCFR, PRDID
• Source Location master data
defines how a product is sourced
for a location via a transport from
another location (the ship-from
locations).
• To connect two warehouses define
the connection with
SOURCELOCATION between
LOCFRID and LOCID for a certain
product PRDID.

223
IBPSOURCELOCATION Master Data Type (cont.)

Remarks
• Min. and incr. transportation lot sizes can be modeled.
• The delivery type can be C (crossover order delivery) or S (sequential order delivery).
• Lead time variability can be modeled via TLEADTIME (mean value) and TLEADTIMEVARIABILITY (coefficient
of variance).
• If a warehouse is sourced from more than one location then this can be defined using TRATIO.
• If the sourcing is time-dependent then set RATIOTS to “X” and use the key figure LOCATIONRATIO.
• Transportation shipment frequency and its impact on cycle stock can be modeled.

224
IBPSOURCELOCATION Master Data Type (cont.)

Transportation source (T-Rule):


• To plan supply through stock transfer from another location one has to specify a suitable transport sourcing
rule (T-rule).
• Transport sourcing can be maintained as time-dependent or time-independent key figure
• This includes the lead time and lot size information.
• Quota is only used by Unconstrained Heuristic.

Master data key figure – Location sourcing quota


• This input key figure contains the quotas for sourcing customer demand for a product from various ship-from
locations.
• These quotas are respected by the heuristics but not by the optimizer.

225
IBPPRODUCTIONSOURCEITM Master Data Type

Remarks

• MDT “Simple”

• Key: PRDID, SOURCEID

• Mandatory attributes:

• SOURCEITMID

• Source production is an Item table and


describes components and the component
co-efficient.

• Component coefficient quantity, that is,


quantity of component in a bill of material
(BOM).

• The resulting product is the SOURCEITMID

• COMPONENTCOEFFICIENTTS can be set


to “Y” if the coefficient is time dependent.

• Can be modeled as time-independent or


time-dependent as key figure.

226
IBPSOURCEPRODUCTION Master Data Type

Remarks
• MDT “Simple”
• Key: SOURCEID, LOCID, PRDID
• Source production is a Header table and describes
products and co-products, where the quantities of
co-product and product are related by the output
coefficients.
• SOURCEPRODUCTION defines an entry point for
new material – either through production or
procurement. Source Type = U (external vendor) or
P (production).
• SOURCEID is a unique ID that either describes the
supplier record or the bill of material ID. Please
note that the same SOURCEID can be used for
different products and locations (e.g. for the same
supplier or the same BoM in different locations).
• The connection to the components of a BoM is
defined in PRODUCTIONSOURCEITM using the
SOURCEID.
• The delivery type can be C (crossover order
delivery) or S (sequential order delivery).

227
IBPSOURCEPRODUCTION Master Data Type (cont.)

Production source (P-Rule):


• To plan supply through Production one has to specify a suitable Production sourcing.
• Source Type ‘P’ is used to specify a P-Rule. The meaning of a production sourcing rule is that Product is produced at the
location where the demand for Product exists.
• The main output product carries lot size information, which also applies to the co-product (via the output coefficient
relationship).
• PMINLOTSIZE is minimum lot size and PMAXLOTSIZE is maximum lot size.
• Production ratio can be maintained as time-dependent or time-independent. P-ratio is only used by Unconstrained
Heuristic.
• Output coefficient defines the base production quantity. It can be modeled as time-dependent as key figure or time-
independent via attribute.

Unspecified sourcing (U-Rule):


• U sourcing role is specified when the source of supply to meet the demand is not required to be modeled explicitly.
• If, for instance, the supply network terminates at a location product where components are purchased and the supply
chain of the supplier should not be taken into account one needs sourcing rules indicating the planning algorithms to stop
the network propagation but to make supply available. This is the task of unspecified sourcing; Source Type “U” stands for
“unspecified”.
• U sources do not have a sourcing quota. There can only be one U rule per product-location.
228
IBPSOURCEPRODUCTION Master Data Type (cont.)

SOURCEPRODUCTION • Min. and incr. product lot sizes can


Attributes Description be modeled.
• The lead time can be modeled as a
PMINLOTSIZE Minimum production lot size
static value or with uncertainty
PINCLOTSIZE Production incremental lot size (using the variability = CV).
• The OUTPUTCOEFFICIENT defines
PLEADTIME Production Lead Time
the number of products produced
PLEADTIMEVARIABILITY Production Lead Time CV (currently only 1 is supported).
• If a product can be produced or
Indicator if procured by more than one
OUTPUTCOEFFICIENTTS OUTPUTCOEFFICIENT is static SOURCEID, the same mechanism
or defined as a key figure as with TRATIO applies here for
PRATIO and PRATIOTS (the key
OUTPUTCOEFFICIENT Output Product Coefficient figure is PRODUCTIONRATIO).

PRATIO Production Ratio


Indicator if PRATIO is static or
PRATIOTS
defined as a key figure

PSHIPMENTFREQUENCY Production Shipment Frequency

229
IBPAGGCONSTRAINT – Aggregate Constraint

230
IBPPRODUCTIONSOURCEITMR – Production Source Item Reference

231
IBPPRODUCTIONSOURCEITMSUB – Production Source Item Sub

232
IBPTRANSPORTATIONRESOURCE – Transportation Resource

233
IBPRISKOPP – Risks and Opportunities

234
IBPASSUMPTIONCATEGORY – Assumption Category

235
IBPPRIORITY – Priority

236
IBPROPTYPE – Risk and Opportunity Type

237
Planning Area Configuration - Multi Level BoM Example

• To configure a multi-level PHONE_BOX SOURCEPRODUCTION


BOX
BoM, you need to use two MANUAL SOURCEID LOCID PRDID SOURCETYPE
POWER_SUPPLY
types of master data: PHONE
PHONE_BOX_CDC
PHONE_PLANT
CDC
PLANT
PHONE_BOX
PHONE
P
P
CPU SUPPLIER CDC BOX U
BOARD SUPPLIER CDC MANUAL U
DISPLAY SUPPLIER CDC POWER_SUPPLY U

• SOURCEPRODUCTION 2x MEMORY

• PRODUCTIONSOURCEITM PRODUCTIONSOURCEITM

PRDID SOURCEITMID SOURCEID COMPONENTCOEFFICIENT


BOX PHONE_BOX PHONE_BOX_CDC 1

• The kitting of the phone MANUAL


POWER_SUPPLY
PHONE_BOX
PHONE_BOX
PHONE_BOX_CDC
PHONE_BOX_CDC
1
1
PHONE PHONE_BOX PHONE_BOX_CDC 1
happens in the CDC and all CPU PHONE PHONE_PLANT 1

components except for the BOARD


DISPLAY
PHONE
PHONE
PHONE_PLANT
PHONE_PLANT
1
1

phone are purchased. MEMORY PHONE PHONE_PLANT 2

238
Agenda

• SAPIBP1: What's New in 2002

• SAPIBP1: General Remarks

• SAPIBP1: Key Figure Overview

• SAPIBP1: Master Data Overview

• SAPIBP1: Planning Level Overview

• SAPIBP1: General Planning Area Settings

• SAPIBP1: Changes in earlier releases

239
SAPIBP1 – Planning Level
Overview
Planning Level Overview

Naming convention of planning levels:


• Name of the planning level indicates the used root attributes
• Example: WKPRODLOCCUSTGROUP
− Root attributes are: Week, PRDID, LOCID, CUSTGROUP

• Planning level name starts with the time dimension (if time is used at all):
• DAY = day, MTH = month, WK = week ; YEAR

• Planning levels ending with …CURR are used as base planning level for key figures which are
currency dependent

• Planning levels ending with …CURRTO are used for currency conversion

• Planning levels ending with …UOMTO are used for UoM conversion

241
Planning Levels
Weekly Planning Levels
WK… = technical weeks
CALWK… = Calendar weeks

242
Planning Levels

Monthly Planning Levels Yearly Planning Levels Other Planning Levels

243
Planning Levels

To support storing and calculating results across different time granularity and attributes, SAPIBP1 uses the
following Planning Levels:
Daily Planning Levels

244
Agenda

• SAPIBP1: What's New in 2002

• SAPIBP1: General Remarks

• SAPIBP1: Key Figure Overview

• SAPIBP1: Master Data Overview

• SAPIBP1: Planning Level Overview

• SAPIBP1: General Planning Area Settings

• SAPIBP1: Changes in earlier releases

245
SAPIBP1 – General Planning
Area Settings
Time Profile Settings

• SAPIBP1 planning area has Time Profile ID 12 assigned with default Storage Time
Profile Level set to Daily.

• SAP Delivered Time Profile ID 12 W2M SPA D TW W M Q Y has time profile date starting Jan 1, 2011 to Dec 31
2025. This can be extended in implementation project
• Planning Horizons of the Time Profile Levels assigned to SAPIBP1 are as follows:

247
SAPIBP1: General Planning Area Settings - Planning Operators

Planning operators
• General definition: A planning operator uses an algorithm to compute large amounts of key figure data inside a
planning session. You can schedule a planning operator to be processed in the background.

• Planning operators used within SAPIBP1 (default settings):


• Inventory optimization (IO)
− Single stage inventory opt – starts a local inventory optimization for all customer facing nodes
− Multistage inventory opt – starts a multistage inventory optimization across the whole network. Besides the main output key figures the
internal key figures related to demand and service level are calculated (not for lost demand, see next planning operator)
− Expected demand loss – calculates the expected loss (which depends also on the type of service level), the output key figures for lost
demand are filled.
− Calculate inventory components – calculates the additional components of inventory including cycle stock, pipeline stock, etc.
• Demand
− IBPFORECAST: Pre-requisite when doing forecasting
− ADVSIM: Used for enable saving manual overwrites to ADJDELIVQTY

248
SAPIBP1: General Planning Area Settings - Planning Operators

Planning operators used within SAPIBP1 (default settings):


• Supply
• Unconstrained D/S (No Shortage): Unconstrained demand and supply (No Shortage)
• Optimizer: Optimizer
• Profit Optimizer: Profit Optimizer

• DISAGG operators
• Copy to Global Demand (SOP) Copy Demand Planning Qty to Global Demand Plan Qty (SOP)
• Copy to Consensus Demand Copy Consensus Demand Plan Qty to Consensus Demand
• Copy to Safety Stock (SOP) Copy Final Safety Stock (for IO) to Safety Stock (for SOP)
• Copy to Consensus Dmd Final Copy Customer Receipts to Consensus Demand Final
• Copy to Demand Forecast (IO) Copy Combined Final Demand to Demand Forecast (IO)
• Copy to Safety Stock LC (IO) Copy Final Safety Stock (for IO) to Final Safety Stock Last Cycle (for IO)

249
SAPIBP1: General Planning Area Settings - Planning Operators

Planning operators used within SAPIBP1 (default settings):

• KPI_PROFILE: Required for calculation of forecast error

• SEGMENTATION: Used fur executing ABC/XYZ segmentation

250
SAPIBP1: General Planning Area Settings
Change History and Supply Planning Operator

Change History: “Planning Area Enabled” checkbox must be selected


Snapshot key figures can only be defined for planning areas with change history enabled

Supply Planning Enabled must be selected (Default Setting) for SAPIBP1 Planning Area

251
Agenda

• SAPIBP1: What's new in 2002

• SAPIBP1: General Remarks

• SAPIBP1: Key Figure Overview

• SAPIBP1: Master Data Type Overview

• SAPIBP1: Planning Level Overview

• SAPIBP1: General Planning Area Settings

• SAPIBP1: Changes in earlier releases

252
Changes with 1911
1911 Summary of Changes in SAPIBP1

• Elimination of warning messages in SAPIBP1 Planning Area activation log

• Add UOM conversion to Inventory Optimization Key Figures. Note: all quantity-based key figures
must have the same base unit of measure inputs.

• Further align SAPIBP1 with SAP3 Planning Area

• Bugfixes
• In Forecast Model "BestFit" for Considering Product Lifecycle Information
• Inventory Optimization Planning Levels
• Supply Key Figures for INVENTORYTARGET

• Added attributes to Master Data Type LOCATIONPRODUCT to enhance Lot Sizing Procedures
in Supply Planning

254
Changes related to elimination of Warning messages in Activation Log
Key Figure Configuration Change

INTRANSITINVENTORYVALPCT Key Figure removed

ACTUALSPURCHASE Deleted ACTUALSPURCHASE@WKPRODLOC calculation

TARGETSERVICELEVEL Calculation TARGETSERVICELEVEL@CALWKPRODLOCCUSTGROUP is removed

Adapt the calculation for ACTUALSREV in order to eliminate the warning message in the
ACTUALSREV activation log

AOPREV Adapt the calculation for AOPREV in order to eliminate the warning message in the activation log

Change the calculation at request level in order to eliminate the warning message in the
HPCAPAUSAGE activation log

CONSENSUSDEMANDREV Add one calculation @WKPRODCUSTCURRCURRTO

HCONSENSUSDEMANDREV New helper key figure for calculation MARKETSHAREPCT

MARKETSHAREPCT Adapt the calculation by using the new helper key figure HCONSENSUSDEMANDREV
255
Changes related to elimination of Warning messages in Activation Log

Planning Area Settings

• For Attribute as Key Figure UOMCONVERSIONFACTOR, remove From Period and


To Period setting
• Remove 'PLANNER' from MDT LOCATIONPRODUCT assignment to Planning Area

256
Changes related to adding UOM Conversion to Inventory Optimization Key Figures

Key Figure ID Configuration Changes


1. add UOMCONVERSIONFACTOR to Convert Using
DEPENDENTCUSTOMERDEMANDMEAN 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
DEPENDENTCUSTOMERDEMANDSTDDEV 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
DEPENDENTLOCATIONDEMANDMEAN 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
DEPENDENTLOCATIONDEMANDSTDDEV 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
DEPENDENTLOCTOPRDDEMANDMEAN 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
DEPENDENTLOCTOPRDDEMANDSTDDEV 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
DEPENDENTSRCTOLOCDEMANDMEAN 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
DEPENDENTSRCTOLOCDEMANDSTDDEV 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOAVGCYCLESTOCK 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOAVGINVENTORYPOSITION 2. add UOM calculation in Calculation Definition

257
Changes related to adding UOM Conversion to Inventory Optimization Key Figures

Key Figure ID Configuration Changes


1. add UOMCONVERSIONFACTOR to Convert Using
IOAVGONHANDSTOCK 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOAVGPIPELINESTOCK 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
2. add UOM calculation in Calculation Definition
3. add calcualtion to base planning level (syn with
SAP3,IOFORECAST@WKPRODLOCCUSTGROUP =
IF(ISNULL("IOFORECAST@WKPRODLOCCUSTGROUP"),0,IF("IOFORECAST@WKPRODLOCCU
STGROUP" < 0,0,"IOFORECAST@WKPRODLOCCUSTGROUP"))
IOFORECAST )
1. add UOMCONVERSIONFACTOR to Convert Using
IOMERCHANDISINGSTOCK 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOMINSTOCKREQUIREMENT 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOSALES 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOTARGETCYCLESTOCK 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOTARGETONHANDSTOCK 2. add UOM calculation in Calculation Definition
258
Changes related to adding UOM Conversion to Inventory Optimization Key Figures

Key Figure ID Configuration Changes


1. add UOMCONVERSIONFACTOR to Convert Using
IOTARGETPIPELINESTOCK 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
LOSTCUSTOMERDEMANDMEAN 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
OUTGOINGBACKLOGMEAN 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
OUTGOINGBACKLOGSTDDEV 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
OUTGOINGSRCTOLOCBACKLOGMEAN 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
OUTGOINGSRCTOLOCBACKLOGSTDDEV 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
PINCLOTSIZE 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
PMINLOTSIZE 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
PROPAGATEDDEMANDMEAN 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
PROPAGATEDDEMANDSTDDEV 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
RECOMMENDEDSAFETYSTOCK 2. add UOM calculation in Calculation Definition 259
Changes related to adding UOM Conversion to Inventory Optimization Key Figures

Key Figure ID Configuration Changes


1. add UOMCONVERSIONFACTOR to Convert Using
ROP 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
SAFETYSTOCKDEMANDVAR 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
SAFETYSTOCKLOTSIZE 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
SAFETYSTOCKSERVICEVAR 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
SAFETYSTOCKSUPPLYVAR 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
TARGETINVENTORYPOSITION 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
TINCLOTSIZE 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
TMINLOTSIZE 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOAVGINPROCESSSTOCK 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOTARGETINPROCESSSTOCK 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOAVGVENDORTRANSITSTOCK 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOTARGETVENDORTRANSITSTOCK 2. add UOM calculation in Calculation Definition 260
Changes related to adding UOM Conversion to Inventory Optimization Key Figures

Key Figure ID Configuration Changes


1. add UOMCONVERSIONFACTOR to Convert Using
IOENDONHANDSTOCK 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
CALCTINCLOTSIZE 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
CALCTMINLOTSIZE 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
CALCPINCLOTSIZE 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
CALCPMINLOTSIZE 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
IOMAXINVENTORY 2. add UOM calculation in Calculation Definition
1. add UOMCONVERSIONFACTOR to Convert Using
ADJUSTEDIOSAFETYSTOCK 2. add UOM calculation in Calculation Definition

FINALIOSAFETYSTOCKLASTCYCLE add UOM calculation in Calculation Definition

SAFETYSTOCKDELTA add UOM calculation in Calculation Definition

261
Changes related to adding UOM Conversion to Inventory Optimization Key Figures -
New Helper Key Figures

Key Figure ID Configuration Changes


HCONVRECOMMENDEDSAFETYSTOCK HCONVDEPENDENTLOCTOPRDDEMANDMEAN

HCONVIOMAXINVENTORY HCONVDEPENDENTLOCTOPRDDEMANDSTDD

HCONVIOMINSTOCKREQUIREMENT HCONVDEPENDENTSRCTOLOCDEMANDMEAN

HCONVIOFORECAST HCONVDEPENDENTSRCTOLOCDEMANDSTDD

HCONVIOSALES HCONVOUTGOINGSRCTOLOCBACKLOGMEAN

HCONVTMINLOTSIZE HCONVOUTGOINGSRCTOLOCBACKLOGSTDD

HCONVTINCLOTSIZE HCONVCALCPMINLOTSIZE

HCONVPMINLOTSIZE

HCONVPINCLOTSIZE

262
Changes related to aligning SAPIBP1 with SAP3 Planning Area

New Planning Levels:


PRODLOCCUSTGROUP
WKPRODLOCCUSTGROUPLAGUOMTO

Planning Level removed:


WKPRODLOCNO

Key Figures:
UOMCONVERSIONFACTOR – Change to Non-Editable

263
Changes Related to Bug Fixes
1. Forecast Model “BestFit” for considering Product LifeCycle Information : The flag "Consider
Product Lifecycle Information" was moved from tab "Forecasting Steps" to tab "General". This required
an update of the BestFit Forecast Model.

2. Inventory Optimization

The non-root attribute SOURCETYPE was removed from

• WKPRODTOLOCPRODSRC

• WKPRODTOLOCPRODSRCUOMTO

Reason:In planning levels WKPRODTOLOCPRODSRC and WKPRODTOLOCPRODSRCUOMTO,


customers must not assign any other (non-root) attributes from SOURCEPRODUCTION MDT in order
to avoid problems due to attribute mismatches (PRDID in the planning levels is the component
whereas the PRDID in the SOURCEPRODUCTION MDT is the header product).

3. Time Series Supply : INVENTORYTARGET Key Figures - mark as "Input for Supply"

264
Changes Related to Time Series Supply Planning - Enhancements in Lot Size Procedures

You can now exclude dependent location demand and dependent production demand when using
the static and dynamic periods of supply lot-sizing procedures. You do this by setting the
IGNOREDEPLOCDEM (Ignore Dependent Location Demand) attribute or the
IGNOREDEPPRODDEM (Ignore Dependent Production Demand) attribute (as appropriate) in the
Location Product master data type to 1.

For this two new attributes have been added to the LOCATIONPRODUCT MDT:

- IGNOREPDEPLOCDEM (Ignore Dependent Location Demand)

- IGNOREDEPPRODDEM (Ignore Dependent Production Demand)

See IBP help for further information:

265
Changes with 1908
Changes related to Last Period Aggregation Remodeling (1/3)

The following Planning Levels are removed: The following Planning Levels are newly added:
• PER • DAYPRODLOCNOUOMTO
• PER1 • WKPRODLOCNO
• PERPRODLOC1 • WKPRODLOCNOCURRCURRTO
• PERPRODLOC2 • WKPRODLOCNOUOMTO
• PERPRODLOCCURRCURRTO1
• PERPRODLOCCURRCURRTO2
• PERPRODLOCUOMTO1
• PERPRODLOCUOMTO2
• PER1DAY
• PERDAY
• PERPRODLOCUOMTO2DAY
• WKPRODLOCLPA
• DAYPRODLOCLPA

267
Changes related to Last Period Aggregation Remodeling (2/3)

The following Key Figures are removed:


• HKFPER • HFINALIOSAFETYSTOCK
• HFINALIOSAFETYSTOCKLC
• INPUTKFWK • HINITIALINVENTORY
• HKFPERDAY • HINVENTORYTARGET
• INPUTKFDAY • HMAXINVENTORY
• HPROJECTEDINVENTORY
• PERIODID
• HSAFETYSTOCKDELTA
• HRECOMMENDEDSAFETYSTOCK • HSOPSAFETYSTOCK
• HFINALIOSAFETYSTOCKVAL • HCONSIGNQMINVENTORYQTY
• HINITIALINVENTORYVAL • HCONSIGNRESTRICTEDINVENTORYQTY
• HCONSIGNUNRESTRICTINVENTORYQTY
• HINVENTORYTARGETVAL
• HQMINVENTORYQTY
• HPROJECTEDINVENTORYVAL • HRESTRICTEDINVENTORYQTY
• HRECOMMENDEDSAFETYSTOCKVAL • HUNRESTRICTEDINVENTORYQTY
• HSAFETYSTOCKDELTAVAL
• HADJUSTEDIOSAFETYSTOCK
• HADJUSTEDSOPSAFETYSTOCK
268
Changes related to Last Period Aggregation Remodeling (3/3)
The following Key Figures are adjusted for Last Period Aggregation (LPA) to use the new IBP_LPA function.
Beyond the changes required for LPA the KFs have been adjusted with the changes in column 2:

Key Figure Additional changes (beyond the changes needed for LPA)
RECOMMENDEDSAFETYSTOCK Change aggregation mode from SUM to AVG
FINALIOSAFETYSTOCKVAL n.a.
INVENTORYTARGETVAL n.a.
PROJECTEDINVENTORYVAL n.a.
RECOMMENDEDSAFETYSTOCKVAL n.a.
SAFETYSTOCKDELTAVAL n.a.
ADJUSTEDIOSAFETYSTOCK Change aggregation mode from SUM to AVG
ADJUSTEDSOPSAFETYSTOCK Change aggregation mode from SUM to AVG
FINALIOSAFETYSTOCK n.a.
FINALIOSAFETYSTOCKLASTCYCLE n.a.
INVENTORYTARGET Remove setting for “convert using”
MAXINVENTORY Change aggregation mode from SUM to MAX
PROJECTEDINVENTORY Change from “system editable” to “Non-editable”, remove “Convert using”
SAFETYSTOCKDELTA n.a.
SOPSAFETYSTOCK Change from “system editable” to “Non-editable”
CONSIGNQMINVENTORYQTY Change from “system editable” to “Non-editable”
CONSIGNRESTRICTEDINVENTORYQTY Change from “system editable” to “Non-editable”
CONSIGNUNRESTRICTINVENTORYQTY Change from “system editable” to “Non-editable”
QMINVENTORYQTY Change from “system editable” to “Non-editable”
RESTRICTEDINVENTORYQTY Change from “system editable” to “Non-editable”
UNRESTRICTEDINVENTORYQTY Change from “system editable” to “Non-editable”
INITIALINVENTORY LPA function is removed. Change Disaggregation Mode to “Equal Distribution”
INITIALINVENTORYVAL LPA function is removed
269
Changes related to Shelf Life LCODE removal (1/2)

Configuration related to Shelf Life LCODE has been removed from SAPIBP1:

Following Attributes have been removed: Following Master Data Types have been removed:
• BATCHID • IBPBATCH
• IBPBATCHPRODUCT
• BATCHDESCR
• EXPIRYDATE
• MFGDATE
Changes to Planning Area Attribute Assignment
• INITLRMNSHLFLIFE
• Unassign MDT IBPBATCH from planning area
Following Planning Levels have been removed • Unassign MDT IBPBATCHPRODUCT from planning
• WKPRODBATCH area
• WKPRODLOCBATCH • Unassign attribute MINRQDSHELFLIFE from MDT
• WKPRODLOCCUSTBATCH IBPCUSTOMERPRODUCT

270
Changes related to Shelf Life LCODE removal (2/2)
Following LCODE Key Figures have been removed.
• SLREMBATCHQTY
• LSLWASTAGEQTY
• SLFULFILLEDDMNDQTY

Following further Key Figures have been removed:


• SLREMBATCHQTYPLB
• SLFULFILLEDDMNDQTYPLB
• LSLWASTAGEQTYPLB
• LSLMINREQDSHELFLIFE
• LSLREMSHELFLIFE
• LSLBATCHQTY
• LSLCONSENSUSDEMANDQTY
• SLBATCHQTY
• REMSHELFLIFE

All Key Figures listed on this page also have beenremoved from BASELINE, UPSIDE and DOWNSIDE
versions.
271
Changes related to alignment with Supply Planning SAP4 (1/3)

In the area of Supply Planning there have been certain deviations between SAP4 and SAPIBP1. To
further align the two models, the changes listed below have been made in SAPIBP1.

Lot-Size Rounding Value for Customer Receipts


• New attribute CROUNDING created
• Assigned this attribute to IBPSOURCECUSTOMER Master Data Type

Aggregated constraints using a conversion factor of capacity consumption


▪ New Planning Levels:
• CALWKPRODLOCLOCFRRESAGG
• CALWKPRODLOCRESSRCAGG
▪ New Key Figures
• MINAGGPCAPAUSAGE
• MAXAGGPCAPAUSAGE
• MINAGGTCAPAUSAGE
• MAXAGGTCAPAUSAGE

272
Changes related to alignment with Supply Planning SAP4 (2/3)
Key Figure Configuration Changes
TCAPACONSUMPTION change Agg/Disagg mode to 'Avg/copy'
MINCAPAUSAGE change to 'sum / proportional / weekweight'
INTRANSIT change to 'avg / not editable', calculation @request to avg, remove 'convert using'
INTRANSITDS change to 'avg / not editable', calculation @request to avg, remove 'convert using'
INTRANSITCUSTOMER change to 'avg / not editable', calculation @request to avg, remove 'convert using'
COMPONENTWIP change to 'avg / not editable', calculation @request to avg
COMPONENTWIPDS change to 'avg / not editable', calculation @request to avg
INTRANSITINVENTORYVAL change to 'avg', calculation @request to avg, remove 'convert using'
ADDITONALLOTSIZEDEMAND change to 'not editable', then disaggregation mode and proportionality is not relevant
CAPADEMAND change to 'not editable', then disaggregation mode and proportionality is not relevant
CAPAUSAGE change to 'not editable', then disaggregation mode and proportionality is not relevant
CONSDEMDELIVERED change to 'not editable', then disaggregation mode and proportionality is not relevant
CONSDEMDELIVEREDLATE change to 'not editable', then disaggregation mode and proportionality is not relevant
CONSDEMDELIVEREDLATEAVG change to 'not editable', then disaggregation mode and proportionality is not relevant
CONSTRAINEDDEMAND change to 'not editable', then disaggregation mode and proportionality is not relevant
CONSTRAINEDDEMANDDS change to 'not editable', then disaggregation mode and proportionality is not relevant
DEPENDENTCUSTOMERDEMAND change to 'not editable', then disaggregation mode and proportionality is not relevant
DEPENDENTCUSTOMERDEMANDDS change to 'not editable', then disaggregation mode and proportionality is not relevant
change to 'not editable', then disaggregation mode and proportionality is not relevant,
DEPENDENTDEMAND remove 'converting using'
change to 'not editable', then disaggregation mode and proportionality is not relevant,
DEPENDENTLOCATIONDEMAND remove 'converting using'
change to 'not editable', then disaggregation mode and proportionality is not relevant,
DEPENDENTLOCATIONDEMANDDS remove 'converting using'
273
Changes related to alignment with Supply Planning SAP4 (3/3)
Key Figure Configuration Changes
DEPENDENTPRODUCTIONDEMAND change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
DEPENDENTPRODUCTIONDEMANDDS change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
INDEPDEMDELIVEREDLATE change to 'not editable', then disaggregation mode and proportionality is not relevant
INVENTORYCORRECTIONVIOLATED change to 'not editable', then disaggregation mode and proportionality is not relevant
IPUPRODUCTION change to 'not editable', then disaggregation mode and proportionality is not relevant
IPUPRODUCTIONCOMPONENTDS change to 'not editable', then disaggregation mode and proportionality is not relevant
NETDEMAND change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
PCAPADEMAND change to 'not editable', then disaggregation mode and proportionality is not relevant
PCAPAUSAGE change to 'not editable', then disaggregation mode and proportionality is not relevant
PRODUCTION change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
PRODUCTIONCOMPONENT change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
PRODUCTIONCOMPONENTDS change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
RECEIPT change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
SUPPLY change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
TOTALCONSTRAINEDDEMAND change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
TOTALRECEIPT change to 'not editable', then disaggregation mode and proportionality is not relevant
TRANSPORT change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
TRANSPORTDS change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
TRANSPORTRECEIPTSHIPTO change to 'not editable', then disaggregation mode and proportionality is not relevant, remove 'converting using'
SHORTAGE change from 'system editable' to 'not editable', remove 'convert using'
274
Changes related to alignment with Inventory Optimization SAP3
Direct unit of measure (UOM) conversion is not supported on several key figures used by IBP for inventory. This required a
bugfix on IO Key Figures used in IO Operators.

Removal of UOM Conversion calculations for IO Key Figures:


• PROPAGATEDDEMANDMEAN • SAFETYSTOCKSUPPLYVAR
• PROPAGATEDDEMANDSTDDEV • SAFETYSTOCKSERVICEVAR
• IOTARGETCYCLESTOCK • SAFETYSTOCKLOTSIZE
• IOAVGCYCLESTOCK • IOENDONHANDSTOCK
• IOTARGETPIPELINESTOCK • DEPENDENTCUSTOMERDEMANDMEAN
• IOAVGPIPELINESTOCK • DEPENDENTCUSTOMERDEMANDSTDDEV
• IOMERCHANDISINGSTOCK • LOSTCUSTOMERDEMANDMEAN
• IOTARGETONHANDSTOCK • ADJUSTEDIOSAFETYSTOCK
• IOAVGONHANDSTOCK • FINALIOSAFETYSTOCKLASTCYCLE
• ROP • SAFETYSTOCKDELTA
• IOAVGINVENTORYPOSITION
• SAFETYSTOCKDEMANDVAR

Beside this the “Convert Using” setting has been removed from key figure FINALIOSAFETYSTOCKLASTCYCLE.
275
Miscellaneous Changes
Changes related to BestFit Forecasting Model:
• In the Forecast Model “BestFit” the flag "Consider Time Series Properties” is flagged
• Use Case: If you select the Choose Best Forecast method for utilizing multiple forecasts, you can set the system to
check the time series properties that were identified by the most recent forecast automation job for the selected planning
objects, and use them to filter out the algorithms that are not expected to calculate an appropriate forecast.
Such algorithms are not run before the comparison and are therefore excluded from the selection, which leads to
reduced processing time and more robust forecasting results.

Adjustment related to validation check:


• Planning Area activation log showed two warnings:
• W - COSTPERUNIT: Attribute CURRID in planning level MTHCURRCURRTOPRODUOMTO must be conversion source.
• W - COSTPERUNIT: Attribute PRDID in planning level MTHCURRCURRTOPRODUOMTO must be conversion source.
• To remove these warnings the following changes had to be done
• Planning Level MTHCURRCURRTOPRODUOMTO: Select conversion source for Attributes CURRID and PRDID

Adjusted Calculation for HCONVFINALCONSENSUSDEMANDQTY (Bugfix):


• HCONVFINALCONSENSUSDEMANDQTY@WKPRODLOCCUST
= "FINALCONSENSUSDEMANDQTY@WKPRODLOCCUST"
276
Changes with 1905
Changes related to Forecast Error Calculation (1/4)

SAPIBP1 has the following example modelling related to forecast accuracy calculation:

• Statistical Forecast Qty Error: 1 Month and 3 Months Lag

• Combined Final Demand Error: 1 Month and 3 Months Lag

• Consensus Demand Plan Qty Error: 1 Month and 3 Months Lag

• Consensus Demand Final Error: 1 Month and 3 Months Lag

Lag 1 and Lag 3 was picked as an example. This may be different in reality.

Up to IBP 1902 a separate snapshot key figure for each lag was modelled to keep the necessary lag
information.

With IBP 1905 the key figure modelling was changed so that the number of required key figures for the
snapshots is independent of the number of lags ( e.g. Lag1, Lag3, Lag6, Lag12).

More details see chapter “Key Figures Related to Forecast Error Calculation” later in this document
278
Changes related to Forecast Error Calculation (2/4)

• 4 new lag-based snapshot key figures:


• STATISTICALFORECASTQTYLAG
• COMBINEDFINALDEMANDLAG
• CONSENSUSDEMANDQTYLAG
• FINALCONSENSUSDEMANDQTYLAG
These 4 key figures have “Lag” as additional root attribute and are used to store the snapshot data. Each
key figure can store all required lags.

• 4 new helper key figures:


• HCONVSTATISTICALFORECASTQTY
• HCONVCOMBINEDFINALDEMAND
• HCONVCONSENSUSDEMANDQTY
• HCONVFINALCONSENSUSDEMANDQTY
These 4 helper key figures are used by the system when generating the snapshot data via the “Lag-based
Snap Shot” Operator (more details see chapter “Key Figures Related to Forecast Error Calculation” later in
this document)
279
Changes related to Forecast Error Calculation (3/4)

• Deleted Key Figures:


• STATISTICALFORECASTQTY1MLAG
• STATISTICALFORECASTQTY3MLAG
• COMBINEDFINALDEMAND1MLAG
• COMBINEDFINALDEMAND3MLAG
• CONSENSUSDEMANDQTY1MLAG
• CONSENSUSDEMANDQTY3MLAG
• FINALCONSENSUSDEMANDQTY1MLAG
• FINALCONSENSUSDEMANDQTY3MLAG
These key figures are replaced by the 4 new lag-based key figures mentioned the page before

• New planning level:


• MTHPRODLOCCUSTLAGUOMTO

280
Changes related to Forecast Error Calculation (4/4)

The following planning operators were removed from SAPIBP1 planning area:
• S&OP Fcst Error: 1M Lag
• S&OP Fcst Error: 3M Lag
• DP Fcst Error: 1M Lag
• DP Fcst Error: 3M Lag

The following two Forecast Error Calculation profiles are shipped together with SAPIBP1:
• Profile “DP_Forecast_Error“
• Profile “SOP_Forecast_Error”
These two profiles are changed with IBP 1905 so that they use the new lag-based snapshot key figures as
input now.
More details see chapter “Key Figures Related to Forecast Error Calculation” later in this document

281
Changes related to Alignment with SAP4 (1/3)

The Sample Planning Areas SAPIBP1 and SAP4 were differing in some aspects. The following
changes were done to further align SAPIBP1:

• New key figure TARGETPERIODCUSTDEMAND: Target Period for Customer Demand


• This lot-sizing procedure enables you to use lot sizing on all supply chain levels, with the heuristic
considering only direct customer demands at a location to build safety stock
• Added to UPSIDE and DOWNSIDE version

• Set attribute category to "Calculated" for PLUNITID1


and PLUNITID2
• Subnetwork-specific segmentation of planning objects
improves the performance of the time-series-based planning
algorithms because it optimizes the reading of the planning
data. It can also significantly reduce the amount of memory
the planning algorithms consume.
282
Changes related to Alignment with SAP4 (2/3)

• Add MDT to planning area SAPIBP1


• Add IBPPRODUCTIONSOURCEITMR to planning area SAPIBP1,
• Add attribute IBPPRODUCTIONSOURCEITMR - COMPONENTCOEFFICIENTTS as mandatory attribute to planning area.

• Add attribute to planning area


• Add attribute MATTRSOURCEPRODUCTION as mandatory attributes to the planning area.

• Changed planning levels:


• WKPRODLOCCOMPSRC: add attribute IBPPRODUCTIONSOURCEITMR – COMPONENTCOEFFICIENTTS
• WKPRODLOCCOMPSRCUOMTO: add attribute IBPPRODUCTIONSOURCEITMR – COMPONENTCOEFFICIENTTS
• WKPRODLOCLOCFR: add attribute IBPSOURCELOCATION – MATTRSOURCELOCATION
• WKPRODLOCLOCFRUOMTO: add attribute IBPSOURCELOCATION – MATTRSOURCELOCATION
• WKPRODLOCLOCFRCURR: add attribute IBPSOURCELOCATION – MATTRSOURCELOCATION
• WKPRODLOCLOCFRCURRCURRTO: add attribute IBPSOURCELOCATION – MATTRSOURCELOCATION
• DAYPRODLOCLOCFR: add attribute IBPSOURCELOCATION – MATTRSOURCELOCATION
• WKPRODLOCSRC: add attribute IBPSOURCEPRODUCTION – MATTRSOURCEPRODUCTION
• WKPRODLOCSRCUOMTO: add attribute IBPSOURCEPRODUCTION – MATTRSOURCEPRODUCTION

283
Changes related to Alignment with SAP4 (3/3)

• New helper key figures:


• HCMPCOEFFCOUNT • HCRATIOCOUNT • HLRATIOCOUNT
• HCMPCOEFFSUM • HCRATIOSUM • HLRATIOSUM
• HPRATIOCOUNT • HPRATIOSUM

• Changed key figures:


• CUSTOMERRATIO: change the calculation at request level, change to aggregation mode “Custom” and disaggregation mode “Copy Value”
• LOCATIONRATIO: change the calculation at request level, change to aggregation mode “Custom” and disaggregation mode “Copy Value”
• PRODUCTIONRATIO: change the calculation at request level, change to aggregation mode “Custom” and disaggregation mode “Copy Value”
• COMPONENTCOEFFICIENT: change the calculation at request level, change to aggregation mode “Custom” and disaggregation mode
“Copy Value”
• ADJUSTEDPRODUCTION: change aggregation mode from “Custom” to “Sum”
• INDEPDEMDELIVEREDLATE: change to “System editable”, agg. mode to “Sum”, and disaggregation mode to “Proportional, equal”, Period
Weight Factor to “WEEKWEIGHT”
• CONSDEMDELIVEREDLATE: change agg. mode to “Sum”, disagg. mode to “Proportional, equal”, Period Weight Factor to “WEEKWEIGHT”

284
Changes related to Alignment with SAP3 (1/4)

The Sample Planning Areas SAPIBP1 and SAP3 were differing in some aspects. The following
changes were done to further align SAPIBP1:

• New planning level WKPRODLOCCUSTGROUPLAG

• Delete planning level TRANSFORMATIONHELPER

• Change the key figure name to same as the description for the following key figures:
• CALCPINCLOTSIZE
• CALCPLEADTIME
• CALCPLEADTIMEVARIABILITY
• CALCPMINLOTSIZE
• CALCTINCLOTSIZE
• CALCTLEADTIME
• CALCTLEADTIMEVARIABILITY
• CALCTMINLOTSIZE

285
Changes related to Alignment with SAP3 (2/4)

• Change the key figure name and description of the following key figures:
• IOFCSTMAD: Name & Description = “IO Historical Forecast MAD”
• IOFCSTMAPE : Name & Description = “IO Historical Forecast MAPE”
• IOFCSTTIMINGACCURACY : Name & Description = “IO Forecast Timing Accuracy”

• Change the following key figures:


• PBR: add a defaulting calculation
• PINCLOTSIZE: add a defaulting calculation
• PLEADTIME: add a defaulting calculation, change aggregation mode from 'max' to 'avg'
• PLEADTIMEVARIABILITY: add a defaulting calculation
• PMINLOTSIZE: add a defaulting calculation
• TINCLOTSIZE: add a defaulting calculation
• TLEADTIME: add a defaulting calculation, change aggregation mode from 'max' to 'avg'
• TLEADTIMEVARIABILITY: add a defaulting calculation
• TMINLOTSIZE: add a defaulting calculation
286
Changes related to Alignment with SAP3 (3/4)

• Delete the following key figures:


• VIOAVGHISTDEMAND
• VIOAVGHISTDEMANDCV
• VIOCV
• VIOFCSTBIASCALCULATED
• VIOFCSTBIASUSED

• Change the following key figures:


• IOFORECASTERRORCV : because VIOCV is deleted, adjust the calculation to use IOCV instead of
VIOCV
• PERIODID4: remove calculation PERIODID4@TRANSFORMATIONHELPER = $$PERIODID4CU$$ +
LAG

287
Changes related to Alignment with SAP3 (4/4)

• Change the following key figures:


• IOAVGDMDINTVL: change the calculation in request level, and add a new calculation on time level
• IOAVGHISTDEMAND: change the calculation in request level, and add a new calculation on time level
• IOAVGHISTDEMANDCV: change the calculation in request level, and add a new calculation on time level
• IOCV : change the calculation in request level, and add a new calculation on time level, add calculation
@wkprodloccustgroup to be used in IOFORECASTERRORCV
• IOFCSTBIASCALCULATED: change the calculation in request level, and add a new calculation on time level
• IOFCSTBIASUSED: change the calculation in request level, and add a new calculation on time level
• IOFCSTMAD: change the calculation in request level, and add a new calculation on time level
• IOFCSTMAPE: change the calculation in request level, and add a new calculation on time level
• IOFCSTTIMINGACCURACY: change the calculation in request level, and add a new calculation on time level
• IOSWITCHINGRATIO: change the calculation in request level, and add a new calculation on time level

288
Changes related to the “Fair-Share Distribution”

The new S&OP Operator Profile for Fair-Share Distribution


was added to SAPIBP1:

• The SOP Operator Profile 104 was added: “Time-Series-


Based Supply Planning Optimizer (W2M)-Fair Share”

289
Changes related to stricter Planning Area Validation Check
Planning Levels were adjusted to a stricter validation check in planning area activation: "Raise Error for Planning Levels with ambiguous configuration". Before 1905 it
was possible to configure multiple planning levels with Identical roots AND Non-indentical non-roots.
This is a configuration „error” that can cause issues with data integration. The planning levels would generate identical planning level filters, while the attributes would be
filled differently depending on the order of creating the PLANOBJECT table entries.

• WKPRODLOCLOCFR: add attribute LOCATIONPRODUCT - SERVICELEVELTYPE • PRODLOCCUSTGROUPLAG:


• WKPRODLOCLOCFRUOMTO: add attribute LOCATIONPRODUCT – SERVICELEVELTYPE • add attribute LOCATIONPRODUCT – SERVICELEVELTYPE
• CALWKPRODLOCCUST: • add attribute LOCATIONPRODUCT – STOCKINGNODETYPE
• add attribute LOCATIONPRODUCT – STOCKINGNODETYPE • add attribute LOCATIONPRODUCT - DISTRIBUTIONTYPE
• add attribute LOCATIONPRODUCT - SERVICELEVELTYPE • CALWKPRODLOCCUSTLAG:
• PRODCUSTLOC: • add attribute LOCATIONPRODUCT – SERVICELEVELTYPE

• add attribute LOCATIONPRODUCT – SERVICELEVELTYPE • add attribute LOCATIONPRODUCT – STOCKINGNODETYPE


• add attribute CUSTOMERPRODUCT - MINRQDSHLFLIFE
• add attribute LOCATIONPRODUCT – STOCKINGNODETYPE
• MTHPRODLOCCUSTLAG :
• add attribute LOCATIONPRODUCT - DISTRIBUTIONTYPE
• add attribute LOCATIONPRODUCT – SERVICELEVELTYPE
• CALWKPRODLOCCUSTUOMTO:
• add attribute LOCATIONPRODUCT – STOCKINGNODETYPE
• add attribute LOCATIONPRODUCT – SERVICELEVELTYPE
• add attribute LOCATIONPRODUCT - DISTRIBUTIONTYPE
• add attribute LOCATIONPRODUCT – STOCKINGNODETYPE • MTHPRODLOCCUSTLAGUOMTO:
• CALWKPRODLOCCUSTGROUPLAG: • add attribute LOCATIONPRODUCT – SERVICELEVELTYPE
• add attribute LOCATIONPRODUCT – SERVICELEVELTYPE • add attribute LOCATIONPRODUCT – STOCKINGNODETYPE
• add attribute LOCATIONPRODUCT - STOCKINGNODETYPE • add attribute LOCATIONPRODUCT - DISTRIBUTIONTYPE

290
Changes in the area of Time-Series Based Supply Planning (1/10)

Overview of changes:
• New model entities in Production Source Item Substitution: Substitution is now enabled on
component level, you can replace components by alternative ones in time-series-based supply
planning.
• New model entities in Transportation Resources: Transportation resource is used to model
transportation capacity consumption, that is, the amount of capacity consumed per unit of
product transported.
• Forecast Consumption: Define the sequence of sales order processing
• New key figure for Dynamic Periods of Supply with Safety Stock

291
Changes in the area of Time-Series Based Supply Planning (2/10)

New attributes:
• SPRDFR: “Substitute Component Product ID”.
• ISALTITEM: “Is Substitute Component”.
• TCAPACONSPOLICY: “Trans Capacity Consumption Policy”.
• TCAPACONSSTART: “Start Period of Capacity Consumption”.
• TCAPACONSEND: “End Period of Capacity Consumption”.
• TCAPACONSUMPTION: “Trans Capacity Consumption Rate”.
• TCONSUMPTIONTS: „Trans Capacity Consumption Time Series Indicator“.
• SALESORDERSEQUENCEID: “Sales Order Consumption Sequence”. Describes the sequence
in which sales orders are processed.
• MATTRPRODUCTIONSOURCEITM: “Mandatory Attribute for Production Source Item”.

292
Changes in the area of Time-Series Based Supply Planning (3/10)

New master data type IBPPRODUCTIONSOURCEITMSUB: “Production Source Item Sub“


• Substitution is now enabled on component level. With the new function, you can replace
components by alternative ones in time-series-based supply planning.

293
Changes in the area of Time-Series Based Supply Planning (4/10)

New master data type IBPTRANSPORTATIONRESOURCE: “Transportation Resource“


• Transportation resource is used to model transportation capacity consumption, that is, the
amount of capacity consumed per unit of product transported.

294
Changes in the area of Time-Series Based Supply Planning (5/10)

Change Master Data Type:


• Add attribute ISALTITEM to MDT IBPPRODUCTIONSOURCEITM
• Add attribute MATTRPRODUCTIONSOURCEITM to MDT IBPPRODUCTIONSOURCEITM
• Add attribute SALESORDERSEQUENCEID to MDT IBPFORECASTCONSUMPTIONMODE
• Add attribute TCAPACONSPOLICY to MDT IBPSOURCELOCATION
• Change description of MDT IBPPRODUCTIONSOURCEITMR to „Production Source Item
Reference“

295
Changes in the area of Time-Series Based Supply Planning (6/10)

Assign attributes to the planning area:


• Add attribute MANDATTRSUB from master data type IBPPRODUCTIONSOURCEITMSUB and
mark it as mandatory
• Add attribute SPRDFR from master data type IBPPRODUCTIONSOURCEITMSUB
• Add attribute MANDATTRTRANSPORTATIONRESOURCE from master data type
IBPTRANSPORTATIONRESOURCE and mark it as mandatory
• Add attribute MATTRPRODUCTIONSOURCEITM from master data type
IBPPRODUCTIONSOURCEITM and mark it as mandatory

296
Changes in the area of Time-Series Based Supply Planning (7/10)

New planning levels:


• WKCOMPALTCOMPSRC:

297
Changes in the area of Time-Series Based Supply Planning (8/10)

New planning levels:


• WKPRODLOCLOCFRRES

298
Changes in the area of Time-Series Based Supply Planning (9/10)

Change planning levels:


• WKPRODTOLOCPRODSRC: add
MATTRPRODUCTIONSOURCEITM attribute to planning level

• WKPRODTOLOCPRODSRCUOMTO: add
MATTRPRODUCTIONSOURCEITM attribute to planning level

299
Changes in the area of Time-Series Based Supply Planning (10/10)

New key figures:


• COMPONENTSUBSTCOSTRATE: “Component Substitution Cost Rate”. You can use this key figure to
define a substitution cost rate for each unit of the original component that is replaced by the substitution
product.
• TCAPACONSUMPTION: “Capacity Consumption Rate of Transportation Resource”. Added to UPSIDE and
DOWNSIDE version.
• TCAPADEMAND: “Capacity Demand of Transportation Resource”. Added to UPSIDE and DOWNSIDE
version.
• TCAPAUSAGE: “Capacity Usage of Transportation Resource”. Added to UPSIDE and DOWNSIDE version.
• SUBPERIODSOFSUPPLYSAFESTOCK: “Dynamic Sub-Periods of Supply with Safety Stock”

300
Changes related to “Risks and Opportunities” (1/8)

With SAP IBP 1905 the new functionality “Driver Based Planning” was introduced. In SAPIBP1 this
new feature was incorporated for modelling of risks & opportunities.

Driver-based planning supports you in capturing business drivers such as risks or opportunities,
evaluating their likely effects, expressing those effects in key figure values, and considering the
drivers in your supply chain plan. It captures both qualitative and quantitative information about a
business driver

301
Changes related to “Risks and Opportunities” (2/8)
The following changes were done:
• New attributes:
Attribute ID Attribute Description Comment
ROPID Risk/Opp ID ID of your risk or opportunity.
ROPDESCR Risk/Opportunity Descr Description of your risk or opportunity.
ROPTYPEID Risk/Opp Type Type of your driver. For example, risk or opportunity.
PRIORITYID Priority ID You can use this attribute to specify how you want to prioritize the risk or opportunity.
For example, high, medium, or low.
ASSUMPTIONCATID Assumption Category ID You can assign an assumption 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 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 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 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.

302
Changes related to “Risks and Opportunities” (3/8)

• New MDTs:
• IBPRISKOPP: “Risks and Opportunities“
• All attributes of this MDT are assigned to
SAPIBP1
• This master data type represents the
driver that can influence your supply
chain plan, in this case, risks and
opportunities.
• This master data types has attribute
checks to
IBPASSUMPTIONCATEGORY.
IBPPRIORITY and IBPROPTYPE
master data types

303
Changes related to “Risks and Opportunities” (4/8)

• New MDTs:
• IBPASSUMPTIONCATEGORY: “Assumption Category“
• Assign attribute ASSUMTIONCATDESCR to SAPIBP1
• Represents the Assumption Categories for the driver. Possible values are competition, market
growth, weather, or others.

304
Changes related to “Risks and Opportunities” (5/8)

• New MDTs:
• IBPPRIORITY: “Priority“
• Attribute PRIORITYDESCR is assigned to SAPIBP1
• Represents the priority of the driver, for example high, medium, or low.

305
Changes related to “Risks and Opportunities” (6/8)

• New MDTs:
• IBPROPTYPE: “Risk and Opportunity Type“
• Attribute ROPTYPEDESCR is assigned to SAPIBP1
• Represents the type of driver, in this case, risks and opportunities.

306
Changes related to “Risks and Opportunities” (7/8)

• New planning levels:


• MTHROPRDFAMCUSTREG. Base Planning level of the Key Figure ROAGGSLSQT for a
Risk/Opportunity. This key figure is defined at an aggregated planning level.
• WKROPRODLOCCUST. Planning Level at which the impact of Risk/Opportunity is distributed t
the level of the Consensus Demand Plan Qty
• MTHRO. Planning level used for intermediate key figure calculations.

307
Changes related to “Risks and Opportunities” (8/8)
• New key figures:
• ROAGGSLSQT “RO Agg Sales Quantity”: This is the key figure for which you enter the value for the risk or opportunity
in the Driver-Based Planning app. Added to UPSIDE and DOWENSIDE version.
• ROCALCSALESQTY “RO Calc Sales Qty”: Used to view the impact of each risk or opportunity at the level of
the Consensus Demand Qty key figure. This key figure uses a split factor calculation to calculate
the ROAGGSALESQTY key figure at the MTHROPRODLOCCUST planning level. Added to UPSIDE and DOWNSIDE
version.
• CONSENSUSCALCROQTY “Consensus Demand Qty with RiskOpp”: Shows the Consensus Demand Qty key figure
considering risks and opportunities that are included in the plan. Added to UPSIDE and DOWENSIDE version

• New helper key figures: These are used to perform a split factor based calculation to bring a Risk/Opp
defined at an aggregate planning level to the level of the forecast key figure and include the approved risks
and opportunities to the Consensus Demand Plan:
• HCONSENSUSDEMANDQTYRO
• HAGGCONSENSUSDEMANDQTYRO
• HDEMANDRATIO
• HROSALESQTYINPLAN

308
Changes related to Forecasting

Changes to forecasting model “BestFit”:


• Under “General” settings of the forecast profile:
• Error Measure Calculation Horizon = 52
• Historical Periods = 156
• Under "Forecasting Steps" of the forecast profile:
• Add "Gradient Boosting of Decision Trees" algorithm
• Test Phase Periods = 26

Changes to forecast automation profile “TimeSeriesAnalysis”:


• Historical Periods = 156 weeks
• Minimum Required Data Points = 10

Extended planning horizon of SAPIBP:


• Longer historical planning horizon fitting to the longer historical horizon used within forecast
model “BestFit”

309
Changes related to Planning Notes

With SAP IBP 1905 it is possible to use planning notes on higher level than the corresponding key
figure.
For performance and data volume reasons, this new setting was applied to key figure
CONSENSUSDEMANDQTY:

310
Other Changes
• Change key figures IPUTRANSPORT, IPUDEPENDENTLOCATIONDEMANDDS from
‘System editable' to 'Editable in current or future period’.
• Forecast Profile “StdDevActualsQty” was changed to use 156 historical periods
• Remove attributes LEADTIMERANK and VARIABILITYRANK from
IBPLOCATIONPRODUCT (not required anymore)
• Change the aggregation and disaggregation mode for fixed cost key figures:
• FIXEDCUSTOMERTRANSPORTATIONCOST: Agg mode to Avg, disagg mode to Copy
• FIXEDEXTERNALRECEIPTCOST: Agg mode to Avg, disagg mode to Copy
• FIXEDPRODUCTIONCOST: Agg mode to Avg, disagg mode to Copy
• FIXEDTRANSPORTATIONCOST: Agg mode to Avg, disagg mode to Copy
• Improve data consistency checks by setting attribute “Category” to “Mandatory” for
DELIVERY - ACTMOVEDATE and SALESORDER - MATAVAILDATE

311

You might also like