For SAP Integrated Business Planning 1702 - SAP Help · PDF fileFor SAP Integrated Business...

Configuration Guide CUSTOMER

Document Version: 1.8 – 2017-06-30

Model Configuration GuideFor SAP Integrated Business Planning 1702

Content

1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

3 Planning Models in SAP Integrated Business Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.1 Sample Planning Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4 Model Configuration Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5 Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175.1 Creating Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175.2 Attribute Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185.3 Attribute Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195.4 Deleting an Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6 Master Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226.1 Description Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.2 Copy Options for Master Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246.3 Creating Simple Master Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246.4 Creating Compound Master Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266.5 Creating External Master Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276.6 Creating Reference Master Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286.7 Creating Virtual Master Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306.8 Master Data Type Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.9 Change of a Master Data Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326.10 Deleting a Master Data Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

7 Time Profiles and Time Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367.1 Creating Time Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377.2 PERIODID and PERIODID(n) Attributes in Time Profile Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397.3 Creating Time Periods from Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397.4 Creating Time Periods for a Time Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407.5 Changing and Deleting Time Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

8 Planning Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448.1 Creating Planning Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .458.2 Validate Master Data for New Planning Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488.3 Replacing the Time Profile in an Active Planning Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

9 Planning Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

2 C U S T O M E RModel Configuration Guide

Content

9.1 Creating Planning Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549.2 Change and Deletion of Planning Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .569.3 Examples of Planning Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

10 Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6110.1 Types of Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6110.2 Creating Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6310.3 Copying Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6810.4 Changing Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6910.5 Display Options for Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6910.6 Creating External Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7010.7 Key Figure Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Adding Calculations to Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Stored Key Figure Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Calculations at Request Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Calculations Across Different Planning Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Commonly Used Functions and Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Defaulting to Another Key Figure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Using Attributes in Key Figure Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Using Time Periods in Key Figure Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

10.8 Decimal Places in Key Figure Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

11 Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8711.1 Creating Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

12 Planning Operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8912.1 Creating a Planning Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9012.2 Assigning a Planning Operator to a Planning Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9112.3 Advanced Simulation (ADVSIM) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Example: Setting Up the ADVSIM Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9412.4 Copy (COPY) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

Example: Setting Up the Copy Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9912.5 Delete Abandoned Combinations (DELABNDNCOMBOS) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . .10112.6 Snapshot (SNAPSHOT) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10212.7 Redo Snapshot (SNAPSHOTREDO) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10212.8 Statistical Forecasting (IBPFORECAST) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Running the IBPFORECAST and DISAGG Operators in Batch Mode with UOM Conversion. . . . . . . . 10312.9 Disaggregation (DISAGG) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Example: Setting Up the Disaggregation Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10712.10 Group (GROUP) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Example: Setting Up a Group Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11012.11 Inventory Optimization (IO) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Model Configuration GuideContent C U S T O M E R 3

12.12 Purge Change History (PCH) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11512.13 S&OP (SCM) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11612.14 Purge Key Figure Data (PURGE) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11712.15 ABC Classification (ABC) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118

Example: Setting Up the ABC Classification Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12012.16 Forecast Error (KPI_PROFILE) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12312.17 Segmentation (SEGMENTATION) Operator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

13 Snapshots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12513.1 Configuring Snapshots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

14 Activating Planning Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12814.1 Statuses of Model Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Example: Changing Model Entities That Are Dependent on Each Other. . . . . . . . . . . . . . . . . . . . . . 131Example: Deleting an Attribute from an Active Master Data Type and Active Planning Area. . . . . . . 135

14.2 Activating Time Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13814.3 Activating Master Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13914.4 Activating Planning Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14014.5 Troubleshooting for Model Activation Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Activation of Time Profiles: Checks and Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Activation of Master Data Types: Checks and Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143Error: Ensure .... is included in the generated calculation graph.. . . . . . . . . . . . . . . . . . . . . . . . . . . 145Error: Check that key figure ID has a calculation at REQUEST Level. . . . . . . . . . . . . . . . . . . . . . . . 147Error: Expression is not valid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Errors relating to key figures with calculations at different planning levels. . . . . . . . . . . . . . . . . . . 148

14.6 Deleting Active Objects (Active Deletion). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14914.7 Troubleshooting for Active Deletion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

15 Copy Options for Planning Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15315.1 Simple Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15415.2 Advanced Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15515.3 Copying an SAP Sample Planning Area with Advanced Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

16 Transporting Model Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15816.1 Exporting a Model Entity from the Source System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15916.2 Importing a Model Entity into the Target System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15916.3 Best Practices for Transporting Planning Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16016.4 Model Transport in a 2-Phase Configuration Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

17 Emergency Access to Production System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

18 Miscellaneous Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17018.1 Reason Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Creating Reason Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170


Content

18.2 Managing Global Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Creating a Global Configuration Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Global Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

18.3 Configuration History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

19 Advanced Modeling Topics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18919.1 Aggregation and Disaggregation of Data Across Different Time Levels. . . . . . . . . . . . . . . . . . . . . . . . 18919.2 Extending the Length of an Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19219.3 Example: Defining an Attribute as a Key Figure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19319.4 Time-Independent Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19519.5 Example: Configuring Currency Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19619.6 Example: Configuring Unit of Measure Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19819.7 Example: Attribute Transformations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20019.8 Example: Weighted Average Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20119.9 Configuring Price and Cost for Currency and UoM Conversions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20319.10 Example: Split Factor Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20519.11 Enabling Change History for Key Figures and Planning Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20619.12 Period To Period Comparisons using Time Profile Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

20 Reserved Names and Naming Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Model Configuration GuideContent C U S T O M E R 5

1 Document History

CautionBefore you start the implementation, make sure you have the latest version of this document. You can find the latest version at http://help.sap.com/ibp1702.

The following table provides an overview of the most important document changes.

Table 1:

Version Date Description

1.0 2017-02-14 Initial version

1.1 2017-03-17 Information added about fixed technical IDs for master data types, attributes, and key figures used in conjunction with demand sensing.

Further information added about attributes as key figures.

1.2 2017-03-31 New chapter: Replacing the Time Profile in an Active Planning Area.

1.3 2017-04-21 Information added about deactivating change history.

1.4 2017-05-12 List of global configuration parameters updated.

1.5 2017-05-19 Explanation of copy operator behavior updated

Information about the default value of the global configuration parameter MAX_DIM_MEMBERS added.

1.6 2017-06-02 Further information added to the Replacing the Time Profile in an Active Planning Area chapter.

1.7 2017-06-16 Information about visibility filters added to the Inventory Optimization (IO) Operator section.


Document History

http://help.sap.com/ibp1702

Version Date Description

1.8 2017-06-30 Information added about planning levels that have identical root attributes to the Creating Planning Levels and to the Creating Key Figures chapters.

Model Configuration GuideDocument History C U S T O M E R 7

2 About This Guide

SAP Integrated Business Planning provides extensive functions for creating, updating, and capturing information in a plan, which is configured using a planning model.

This model configuration guide is aimed at expert business users, consultants, and others who are creating, changing, or extending a company planning model. Based on the Web user interface that is used to configure the planning model, the guide provides task-based information to help you carry out common modeling tasks, such as:

● Creating master data types and attributes, time profiles, planning areas, planning levels, key figures (including calculations), versions, and planning operators

● Activating, copying, and transporting a planning model● Managing reason codes and global configuration parameters

The guide also introduces some advanced modeling concepts, such as modeling for currency conversion and for unit of measure conversion and for attribute transformations.

NoteThe guide contains many examples to illustrate modeling tasks and concepts. To make it easier for you to follow the examples, they have been based, wherever possible, on the SAP2 sample planning area, which is delivered with SAP Integrated Business Planning.

Based on your planning model, you can create planning views and work on your data using the SAP Integrated Business Planning, add-in for Microsoft Excel . For more information, see the SAP Help Portal at http://help.sap.com/ibp , under Application Help Planning with Microsoft Excel .


About This Guide

http://help.sap.com/disclaimer?site=http://help.sap.com/ibp

http://help.sap.com/disclaimer?site=http://help.sap.com/ibp

3 Planning Models in SAP Integrated Business Planning

A planning model describes the structure of your plan in terms of data and calculations. It defines how data is stored, calculated, and aggregated in the system. From a technical perspective, a planning model is a collection of master data and time series data that is organized in dimensions and enhanced with specific calculations. All models are based on the following entities:

● Attributes● Master data types● Time profiles● Planning areas● Planning levels● Key figures (including snapshots)● Calculations● Versions● Miscellaneous additional entities such as global configuration parameters, planning operators, and reason

codes.

The figure below shows an entity relationship diagram and illustrates the relationship between the main configuration entities.

Model Configuration GuidePlanning Models in SAP Integrated Business Planning C U S T O M E R 9

Figure 1: Entities of a Planning Model

The entities shown in the figure are explained in the following table:

Table 2:

Entity Color Entities Explanation

Light Blue Planning area, planning area dimension, planning level, version, key figure, key figure calculation, key figure calculation input, calculation, calculation exit (L-code), operator for planning area

Entities that define the structure and properties of key figures. A set of key figures is bundled under the main entity of a planning area.

NoteThe planning area is often referred to as a “planning model”, because the key figures represent the most important constituents of a planning model.


Planning Models in SAP Integrated Business Planning

Entity Color Entities Explanation

Darker Blue Master data type, attribute, attribute as key figure, reference master data type, compound master data type.

Planning object types that are used to model master data and order data types for the Supply Chain Control Tower.

NoteIn this guide, the term “master data type” is used.

Green Time profile, time profile level, time profile attribute

Time profiles that are used for the time periods of time series.

Orange Attributes Elemental building blocks that describe an individual field and data type that is used in the planning model.

Pink Planning operators Functions that are associated with a planning area. An important example of a planning operator is the S&OP operator. In SAP Integrated Business Planning, you can model and plan an arbitrarily deep network of supply-chain-related locations and production steps, using master data such as sourcing rules, resources, bills of material, and time series and data such as consensus demand, production numbers or capacities. This master data is modeled using master data types, and the time series are defined as key figures in a planning area.

SAP Integrated Business Planning allows you to configure and customize your own planning models to address your unique business requirements. The Configuration app, which you can access from the launchpad, includes all features that enable you to configure a model from scratch, and activate it on the Configuration tab. Many model entities (planning areas, master data types, and time profiles) can also be copied and modified. (You cannot, however, copy attributes or planning operators.)

3.1 Sample Planning Areas

The SAP Integrated Business Planning web client provides display access to sample SAP planning areas, which are shipped with SAP Integrated Business Planning. You can use sample planning areas as a basis for creating your own planning areas. You can copy one of the planning areas and extend it as necessary to meet your particular business needs. You can add your own master data types, key figures, calculations, and attributes. The following table lists the planning areas that are available:


Table 3:

Sample Planning Area Applications Represented

SAP2 Sales and operations and supply (S&OP algorithms)

SAP3 Inventory

SAP4 Supply (S&OP algorithms)

SAP5 SAP Supply Chain Control Tower

SAP6 Demand

SAP7 Response management

SAP74 Response management and supply (S&OP algorithms)

SAPIBP1 The unified planning area is a comprehensive sample planning area that supports an integrated planning process covering all of the following:

● Demand planning● Demand sensing● Inventory optimization● Supply planning (S&OP algorithms)● Sales and operations planning● SAP Supply Chain Control Tower

You can use the unified planning area SAPIBP1 to jump-start the implementation in case your business process requires integration across different IBP applications. Just like any other sample planning area, this planning area delivers an out-of-the-box integration scenario which you can customize to fit your unique requirements.

NoteFor more information about an integrated planning process using the unified planning area, see the application help on the SAP Help Portal at

http://help.sap.com/ibp under SAP Integrated Business Planning

Example: Integrated Planning Process with Unified Planning Area .

For the integrated planning process based on the unified planning area, the SAP HANA Integrated Business Planning rapid-deployment solution provides sample data, planning view templates, predefined dashboards, configuration guides, test scripts and more. Customer test tenants and IBP Starter Edition instances include an activated copy of the unified planning area with the sample content.

You can also download the content directly from SAP Service Marketplace at http://service.sap.com/public/rds-ibp by choosing

Download package .

The following table shows the scope of the sample planning areas:



http://help.sap.com/ibp

http://help.sap.com/disclaimer?site=http://service.sap.com/public/rds-ibp

Table 4:

Model contents

SAP2 SAP3 SAP4 SAP5 SAP6 SAP7 SAP74 SAPIBP1

Complete demand model example

Yes No No No Yes No No Yes

Statistical forecasting

Yes No No No Yes No No Yes

Supply planning optimization (S&OP optimizer)

Yes No Yes No No No Yes Yes

Multi-level supply planning

Yes Yes No Yes No No No Yes

Financial and sales planning

Limited No No (only optimizer costs)

No No No No Limited

Inventory planning and optimization

No Yes (only optimize inventory targets)

No No No No No Yes

Response Planning

No No No No No Yes Yes No

SAP Supply Chain Control Tower

No No No Yes No No No Yes

To access these planning areas, launch the Configuration app and click Planning Area and Details in the top menu. You can select a planning area by choosing Display SAP Sample from the Edit Active and Inactive drop down.

As well as these planning areas, small sample planning areas with examples of advanced configuration to meet different business requirements are provided in SAP Notes, together with information on how to request L-code if configuration can't meet your requirements. The SAP Notes are listed in the following table:

Table 5:

SAP Note Title

2347105 Master Note for the Configuration of Sample Models

2240170 Rolling Sum of the Last Three Periods


http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2347105


SAP Note Title

2240173 Calculation of Average and Weighted Value of Price Key Figures (Including Unit of Measure and Currency Conversion)

2240178 View Monthly Key Figures at Weekly Level Based on Number of Weeks in the Month

2286684 Last Period Aggregation for Key Figures

2288329 Time as a Dimension (Year-To-Date and Quarter-To-Date Aggregations)

2289248 Time-Independent Unit of Measure Conversion

2289617 Aggregation of Last n Periods in Current and Future Periods

2289651 Last Period Aggregation with Unit of Measure Conversion

2298382 Requesting L-Code from SAP

2319165 Triggering an Alert on First Occurrence












4 Model Configuration Process

Context

Configuring the SAP Integrated Business Planning model entails following a specific, sequential process. (Of course, to refine and enhance a model, you will revisit individual topics repeatedly, but master data has to exist before you can use it in a planning area.)

Prerequisites

To be able to configure a planning model, the Planning Model business catalog must be assigned to a business role that is assigned to your user.

Before configuring your planning model, SAP recommends that you create a blueprint based on customer requirements to map the business processes to a planning model. A blueprint outlines the key business functions and the required scope and identifies the master data types, attributes, data integration, key figures, and calculations that need to be modeled in the system.

Steps

1. Define a model. Define the following in the order given:1. Attributes2. Master data types3. Time profiles4. Planning areas5. Planning levels6. Key figures7. Planning operators

2. Activate the model. Check the integrity of the defined model and activate it. This generates the underlying database artifacts. Activate the model in the following order:1. Activate time profile2. Activate master data types3. Activate planning area

3. Load data.Import time profile data, master data, and key figures data into the model.

CautionTo run the inventory operators and S&OP operators, you have to use specific technical IDs defined by SAP for the relevant master data types, attributes, and key figures. For demand sensing, the same applies to certain key figures and master data attributes. For more information, see the documentation of the relevant planning operator in this guide and the respective chapter of the application help.

Model Configuration GuideModel Configuration Process C U S T O M E R 15

RecommendationIf you want to change your planning model later, SAP recommends that you create a new entity (for example, an attribute or a time profile), and use it in your model, instead of changing the existing entity that has already been in use in an active model.

SAP recommends that you try out any changes to your planning model in a test environment (including activating the model and testing the results) before you make changes in the production system.


Model Configuration Process

5 Attributes

Attributes are characteristics of master data types, for example, an attribute of the customer master data type might be country or region. Attributes can be either numeric or non-numeric.

The following data types are supported for attributes:

● nvarchar● decimal● integer● timestamp

NoteYou can only use decimal attributes as key figures in the planning area, and not as planning area dimension attributes.

5.1 Creating Attributes

Context

You can create the attributes you need for planning in the Configuration or Attributes app. You can view and edit the attributes in your system in either app, regardless of where you created them.

Procedure

1. Open the Attributes app.2. Create a new attribute.3. In the New Attribute dialog provide the details for the attribute.

To create the product ID attribute, you could enter the following:○ Attribute ID: S2PRDID

CautionTo run the iinventory operators and S&OP operators, you have to use specific technical IDs defined by SAP for the relevant master data types and attributes, and also for key figures. For demand sensing, the same applies to certain master data attributes and key figures. For more information, see the documentation of the relevant planning operator in this guide and the respective chapter of the application help.

Model Configuration GuideAttributes C U S T O M E R 17

○ Description: Product ID○ Data Type: NVARCHAR○ Length: 40

CautionMake sure that the ID you specify for the attribute does not exist in any of the SAP sample planning areas. An attribute with the same ID as an attribute in an SAP sample planning area can be overwritten if you copy the SAP sample planning area.

4. Save your entries.

Related Information

Attribute Configurations [page 18]Creating Simple Master Data Types [page 24]Creating Compound Master Data Types [page 26]Creating Reference Master Data Types [page 28]Attributes [page 17]

5.2 Attribute Configurations

Specific settings for creating attributes.

Table 6: Attribute Configurations

ID Description Data Type Length

S2CURRID Currency ID NVARCHAR 5

S2CURRDESC Currency Description NVARCHAR 60

S2CURRTOID Currency To ID NVARCHAR 5

S2CURRTODESC Currency To Description NVARCHAR 60

S2CUSTDESC Customer Description NVARCHAR 60

S2CUSTID Customer ID NVARCHAR 20

S2DISCTCHANNEL Distribution Channel NVARCHAR 2

S2LOCDESC Location Description NVARCHAR 60

S2LOCID Location ID NVARCHAR 20


Attributes

ID Description Data Type Length

S2LOCTYPE Location Type NVARCHAR 10

S2ORDERQTY Cumulative Order Quantity in Sales Units

DECIMAL(18,6) -

S2PRDDESC Product Description NVARCHAR 60

S2PRDID Product ID NVARCHAR 40

S2SALESDOC Sales Order NVARCHAR 10

S2SALESITEM Sales Order Item NVARCHAR 10

Related Information

Creating Attributes [page 17]Attributes [page 17]

5.3 Attribute Change

You may want to change an attribute. However, you’ll find that not all fields of an attribute are available for editing. The changes you can do depend on the following factors:

● If the status of the attribute: active or inactive● If the attribute is used in higher-level entities, for example, in master data types, and planning areas● If master data records exists for one or more master data types that use the attribute

You can change any field of an attribute that you have never activated (that is, only an inactive instance of the attribute exists). You can also delete the attribute.

If an attribute has already been activated with a master data type (even if the attribute currently has an inactive instance), certain rules apply for which fields or parameters you can change or delete.

NoteYou can check which master data types, planning areas, and time profiles use an attribute in the Attributes app.


Changes to an Attribute

DescriptionYou can change the description of an attribute any time. Changing the description will not change the status of the attribute from active to inactive

Data TypeYou can change the data type of an attribute only if the attribute has never been activated, and it is not used anywhere.

You can't change the data type of an attribute in the following cases:

● If the attribute has already been activated (by activating a time profile, a master data type, or a planning area that use the attribute)

● If the attribute is specified as a referenced attribute in a reference or in a virtual master data type● You cannot change the data type to decimal for an attribute that is assigned to a planning area or to a time

profile.● You cannot change the data type from decimal for an attribute that is used in a planning area as an attribute

as key figure.

LengthYou can specify the length of an attribute only if its data type is NVARCHAR. All other data types have fixed length.

You can't reduce the length of an attribute if the attribute has already been activated.

You can extend the length of an attribute. In this case, you must activate all master data types, time profiles, and planning areas that use the attribute again for the changes to take effect, to keep the database consistent, and to prevent runtime errors.

NoteYou cannot extend the length if the attribute is used as a referenced attribute in a reference master data type or in a virtual master data type.

Related Information

Extending the Length of an Attribute [page 192]

5.4 Deleting an Attribute

Context

You want to delete an attribute that is used in one or more planning areas, master data types, or time profiles.


Attributes

If the attribute is used in higher-level entities, you must work top down to remove the attribute from each model entity that uses the attribute before you can delete the attribute.

NoteIf an attribute is not used in any other model entity, you can simply delete it.

Procedure

1. Remove the attribute from the planning area by active deletion.

Mark the attribute for deletion, save your changes, then activate the planning area.

Repeat this for all planning areas where the attribute is used.2. Remove the attribute from the master data type by active deletion.

Mark the attribute for deletion, save your changes, then activate the master data type.

Repeat this for all master data types where the attribute is used.

CautionIf you remove an attribute from a master data type, the already existing data for this attribute is deleted from the master data.

Other master data types that use the same attribute are not affected.

3. Remove the attribute from the time profile, then activate the time profile.

Repeat this for all time profiles where the attribute is used.4. Delete the attribute.

Related Information

Deleting Active Objects (Active Deletion) [page 149]Example: Deleting an Attribute from an Active Master Data Type and Active Planning Area [page 135]


6 Master Data Types

Master data types represent categories of information, for example, customer, location, product, or resource. You use master data types to segment planning data. A typical example of their use would be a consumer goods company that wants to understand sales data based on the product, customer, and location master data types.

Every master data type has one or more attributes, for example, the S2CUSTOMER master data type has S2CUSTID as an attribute.

In the Types of Master Data Types table you can find a description of the types of master data types available in the system.

NoteYou cannot change the type of an active master data type.

Table 7: Types of Master Data Types

Type of Master Data Type Description

Simple master data type For example, product, customer or location.

Compound master data type Combines two or more master data types to represent a valid combination of the component master data types.

For example, you use the product and the customer master data types. As not all products are sold to all customers, to represent the valid combinations of products and customers, you create the customer product compound master data type. When a key figure data containing the keys product ID and customer ID is loaded, the system checks against the compound master data type for valid combinations, and stores data only for those.

Reference master data type References another master data type so that you do not have to upload the same data more than once. For example, you can create the currency master data type as a reference master data type that uses the currency to master data type.

NoteYou cannot load data into a reference master data type.


Master Data Types

Type of Master Data Type Description

External master data type Makes it possible for SAP Integrated Business Planning to handle and integrate master data when the content comes from an external database. Before you can use the external master data types, the database tables they retrieve their content from have to be integrated from SAP ERP to SAP HANA database tables inside SAP Integrated Business Planning. When you set up your planning model, you define an external master data type referring to a table that contains the predefined content. The integration runs in batch mode, so the external master data entries are updated on a regular basis from SAP ERP according to your set preferences. There is no need for manual data upload.

NoteYou cannot load data into an external master data type.

Virtual master data type Enables you to create joins between two or more master data types that otherwise have no connection to each other. The join conditions you define between these referenced master data types determine the set of data the virtual master data type uses. By combining master data types this way, you can avoid the duplication of data in your database.

NoteYou cannot load data into a virtual master data type. Make sure you load data into the referenced master data types that the virtual master data type is based on.

Related Information

Creating Simple Master Data Types [page 24]Creating Compound Master Data Types [page 26]Creating External Master Data Types [page 27]Creating Reference Master Data Types [page 28]Creating Virtual Master Data Types [page 30]

6.1 Description AttributesWhen you define a master data type, you can link a description attribute to its corresponding ID attribute. This can be beneficial for the performance of the IBP Excel add-in. When you link the description and ID attributes, during

Model Configuration GuideMaster Data Types C U S T O M E R 23

logon, the IBP Excel add-in downloads the master data of one attribute for both the ID and the description, instead of two separate attributes. This reduces the data volume in the IBP Excel add-in. After you have linked them in configuration, both the description and ID attributes are displayed in the IBP Excel add-in, but not in all other apps in SAP Integrated Business Planning.

CautionIf you have linked the description and ID attributes in configuration, and the description attributes are not assigned to the planning area, you will not be able to use the dynamic attribute value selection in the IBP Excel add-in. For more information about the dynamic attribute value selection, see SAP Help Portal at https://help.sap.com/ibp, under Application Help User Interface Planning with Microsoft Excel Information for Administrators Planning Views Dynamic Selection of Values of Master Data Attributes .

6.2 Copy Options for Master Data Types

You have the following three options when copying master data types:

● NewYou can create a master data type that contains exactly the same configuration as the source with a new ID.

● MergeYou can create a combination of the configuration available in two master data types, that is, keep all the configuration in the target master data type and add everything new from the source master data type. The resulting master data type has the ID of the target master data type and the name and description of the source master data type. The source and the target master data types must be of the same type.

● Overwrite Existing (Replace)You can create an exact copy of the source master data type into an existing target master data type, that is, delete configuration in the target master data type that is not included in the source master data type, add new configuration from the source master data type, and update existing configuration in the target master data type based on the source master data type. The resulting master data type has the ID of the target master data type and the name and description of the source master data type. The source and the target master data types must be of the same type.

The source and target master data types can be active or inactive.

6.3 Creating Simple Master Data Types

Prerequisites

Make sure you have created the attributes you want to use in your simple master data type.


Master Data Types

https://help.sap.com/ibp


Context

You can create the simple master data types you need for planning in the Configuration or Master Data Types app. You can view and edit the simple master data types in your system in either app, regardless of where you created them.

Procedure

1. Open the Master Data Types app.2. Choose New and then Simple.3. On the New Simple Master Data Type screen, provide the details for the simple master data type.

RecommendationSAP recommends that you define a two-letter or three-letter prefix for the IDs of the master data types; for example, ABC or XYZ (as in ABCPRODUCT or XYZPRODUCT). One suggestion could be to use your company's ticker symbol as a prefix. The sample planning areas delivered with SAP Integrated Business Planning use the IBP prefix in the master data type IDs.

To create the product master data type, you could enter the following:○ ID: S2PRODUCT○ Name: Product○ Description: Product

4. In the Assigned Attributes screen area, add at least one attribute to your master data type.

You could add attributes like product ID (S2PRDID) and product description (S2PRDDESC).

CautionTo run the inventory operators and S&OP operators, you have to use specific technical IDs defined by SAP for the relevant master data types and also for attributes and key figures. For demand sensing, the same applies to certain master data attributes and key figures. For more information, see the documentation of the relevant planning operator in this guide and the respective chapter of the application help.

5. Specify at least one key attribute for the master data type.

Select the Key checkbox for S2PRDID.

6. Optional: Link the description attribute to the corresponding ID attribute using the Description Attribute field.

Select S2PRDDESC as description attribute for S2PRDID.


Related Information

Creating Attributes [page 17]


Master Data Type Configurations [page 31]Master Data Types [page 22]Description Attributes [page 23]

6.4 Creating Compound Master Data Types

Prerequisites

Make sure you have created the following:

● Attributes that you want to use in your compound master data type.● Master data types you want to add as components.

Context

You can create the compound master data types you need for planning in the Configuration or Master Data Types app. You can view and edit the compound master data types in your system in either app, regardless of where you created them.

Procedure

1. Open the Master Data Types app.2. Choose New and then Compound.3. On the New Compound Master Data Type screen, enter the details for the compound master data type.

To create the customer product master data type, you could enter the following:○ ID: S2CUSTOMERPRODUCT○ Name: Customer Product○ Description: Customer Product

4. Add at least two master data types as components.

You can specify simple, compound, reference, and external master data types as component master data types. Also, make sure that the status of the master data type you select is active or inactive.

For the S2CUSTOMERPRODUCT compound master data type, add S2CUSTOMER and S2PRODUCT.

The key attributes of the component master data types you selected are automatically added as key attributes under Assigned Attributes.

5. Optional: Assign more attributes to the compound master data type.

Add S2CUSTDESC and S2PRODDESC.


Master Data Types


Select S2PRDDESC as description attribute for S2PRDID.


Related Information

Creating Attributes [page 17]Creating Simple Master Data Types [page 24]Description Attributes [page 23]Master Data Types [page 22]

6.5 Creating External Master Data Types

Use the Master Data Types app to create external master data types.

Prerequisites

Make sure your SAP Integrated Business Planning system has been integrated with the system you would like to provide master data for your external master data types, for example, SAP ERP.

Make sure you have created the attributes you want to use in your external master data type.

Context

You can create the external master data types you need for planning in the Configuration or Master Data Types app. You can view and edit the external master data types in your system in either app, regardless of where you created them.

Procedure

1. Open the Master Data Types app.2. Choose New and then External.3. On the New External Master Data Type screen, provide the details for the external master data type.

To create the location external master data type, you could enter the following:


○ ID: S2LOCATIONEXT○ Name: Location External○ Description: Location External

4. Specify an external data source.

Select SMD_LOC from the External Data Sources list.

5. Add at least one attribute to your master data type.

Add the following attributes:○ Location ID (S2LOCID)○ Location Description (S2LOCDESC)○ Location Type (S2LOCTYPE)

6. Assign the attributes to the corresponding data source columns using the Referenced Column.

Make sure to use all key columns of the external data source as referenced column. The data type of the assigned attribute and the column of the external data source you specify as referenced column for this assigned attribute must be compatible with each other.

Specify LOCATION_NUMBER as referenced column for the S2LOCID assigned attribute. For S2LOCTYPE specify LOCATION_TYPE_CODE as referenced column. For S2LOCDESC add LOCATION_DESCRIPTION.

The Key checkbox is automatically selected for S2LOCID and S2LOCTYPE.


Select S2LOCDESC as a description attribute for S2LOCID.


Related Information

Creating Attributes [page 17]Master Data Types [page 22]Description Attributes [page 23]

6.6 Creating Reference Master Data Types

Use the Master Data Types app to create reference master data types.

Prerequisites

Make sure you have created the attributes and the master data type you want to use in your reference master data type.


Master Data Types

Context

You can create the reference master data types you need for planning in the Configuration or Master Data Types app. You can view and edit the reference master data types in your system in either app, regardless of where you created them.

Procedure

1. Open the Master Data Types app.2. Choose New and then Reference.3. On the New Reference Master Data Type screen, provide the details for the reference master data type.

To create the currency to master data type, you could enter the following:○ ID: S2CURRENCYTO○ Name: Currency To○ Description: Currency To

4. Specify a referenced master data type.

You can specify a simple, a compound or an external master data type as a referenced master data type. Also, make sure that the status of the master data type you select is active or inactive.

You could create and select the S2CURRENCY master data type here.

The attributes of the selected referenced master data type are automatically listed in the Referenced Attributes section.

5. Select the attributes you want to assign to the master data type.

Add the Currency To ID (S2CURRTOID) and Currency To Description (S2CURRTODESC) attributes.

6. Specify a referenced attribute for each assigned attribute.

Make sure that the assigned attribute and the referenced attribute have the same data type, and that the length of the assigned attribute is greater than or equal to the length of the referenced attribute.

Specify S2CURRID as a referenced attribute of S2CURRTOID and S2CURRDESC as a referenced attribute of S2CURRTODESC.


Select S2CURRTODESC as a description attribute for S2CURRTOID.


Related Information

Creating Attributes [page 17]Creating Simple Master Data Types [page 24]Master Data Types [page 22]Description Attributes [page 23]


6.7 Creating Virtual Master Data Types

Use the Master Data Types app to create virtual master data types.

Prerequisites

Make sure you have created the attributes and master data types you want to use in your virtual master data type.

Context

You can create the virtual master data types you need for planning in the Configuration or Master Data Types app. You can view and edit the virtual master data types in your system in either app, regardless of where you created them.

NoteThe example below is a simplified version of one of the virtual master data types that are delivered with SAP Integrated Business Planning. For a more complex version, see the IBPVSALESHDRITEMPRODLOC sample master data type.

Procedure

1. Open the Master Data Types app.2. Choose New and then Virtual.3. On the New Virtual Master Data Type screen, provide the details for the virtual master data type.

To create the S2SALESHDRITEMPRODLOC master data type, you could enter the following:○ ID: S2SALESHDRITEMPRODLOC ○ Name: Virtual Sales Order Item○ Description: Virtual Sales Order Item

4. Add at least two referenced master data types.

You can specify simple, compound, reference, and external master data types as referenced master data types. Also make sure that the status of the master data type you select is active or inactive.

Add the following master data types as referenced master data types:○ S2SALESORDERITEM○ S2SALESORDERHDR○ S2LOCATION○ S2PRODUCT


Master Data Types

The system automatically adds the key attributes of the master data types you added as referenced master data types in the Assigned Attributes section.

5. Add at least one join condition.

Make sure to use every referenced master data type in a join condition and make sure that the join conditions form a chain. You need at least two referenced master data types and one join condition.

In the Add Join Condition dialog, define the join conditions listed in the table.

Table 8:

Master Data Types Attributes Master Data Types Attributes

S2SALESORDERITEM S2SALESDOC Equals S2SALESORDERHDR S2SALESDOC

S2SALESORDERITEM S2LOCID Equals S2LOCATION S2LOCID

S2SALESORDERITEM S2PRDID Equals S2PRODUCT S2PRDID

6. Optional: Under Assigned Attributes, you may change the values of the Referenced Attribute and Referenced Master Data Type fields or assign more attributes and define the referenced attribute and referenced master data type for the attributes you added.


Related Information

Creating Attributes [page 17]Creating Simple Master Data Types [page 24]Master Data Types [page 22]

6.8 Master Data Type Configurations

Specific settings for creating simple master data types.

Table 9: Simple Master Data Type Configurations

ID Name Assigned Attributes Key

S2CURRENCY Currency S2CURRID

S2CURRDESC

S2CURRID

S2CUSTOMER Customer S2CUSTID

S2CUSTDESC

S2CUSTID


ID Name Assigned Attributes Key

S2LOCATION Location S2LOCID

S2LOCDESC

S2LOCID

S2PRODUCT Product S2PRDID

S2PRDDESC

S2PRDID

S2SALESORDERITEM Sales Order Item S2SALESDOC

S2SALESITEM

S2LOCID

S2PRDID

S2ORDERQTY

S2SALESDOC

S2SALESITEM

S2SALESORDERHDR Sales Order Header S2SALESDOC

S2DISCTCHANNEL

S2SALESDOC

Related Information

Creating Simple Master Data Types [page 24]Master Data Types [page 22]

6.9 Change of a Master Data Type

You may want to change a master data type. However, you’ll find that not all fields of a master data type are available for editing. The changes you can do depend on the following factors:

● If the status of the master data type is active or inactive● If the master data type is assigned to planning areas, or used in other master data types, or not● If data has already been uploaded for the master data type

NoteYou can change any parameter (except for its ID) of a master data type that you have never activated (that is, only an inactive instance of the master data type exists). You can also delete the master data type.

If a master data type has already been activated (even if it currently has an inactive instance), certain rules apply for what changes you can make.


Master Data Types

General Data

You can change the name and the description of a master data type any time.

Once you activated a reference master data type, you can’t change the master data type your reference master data type is built on.

Once you activated an external master data type, or used it in a planning area, you can’t change its external data source.

Component and Referenced Master Data Types

A compound master data type must have at least two components. A virtual master data type must have at least two referenced master data types.

If you add or remove components, you must reflect the changes in the set of the key attributes of the compound master data type as well.

In case master data records exists for a compound master data type, you can’t add or remove components. You can add referenced master data types to or remove them from a virtual master data type even if data exists for the components.

Assignment of Attributes to Master Data Types

Adding Additional Attributes to a Master Data TypeYou can add additional attributes to a master data type. If you want to use the newly added attribute in a planning area or in a master data type built on the master data type you changed, you must select it explicitly for the planning area, or for the master data type. Given they were already active, you must activate the master data type and all other entities that use the changed master data type (planning areas, other master data types) for the changes to take effect.

If master data records already existed for the master data type you added an attribute to, the already existing records of the changed master data type will have an empty value for the new attribute. You can decide to upload the master data, enriched with the new attribute, again.

Removing Attributes from a Master Data TypeYou can’t remove all attributes from a master data type. A master data type must have at least one attribute assigned.

You can’t remove an attribute from a master data type if the attribute is used in a planning area, or in a master data type that is built on the master data type you want to change.

CautionIf you remove an attribute from a master data type, the already existing data for this attribute is deleted from the master data records.

Other master data types that use the same attribute are not affected.


Key Attributes

In case of a simple master data type, you can specify additional attributes as key attributes. However, if master data records already existed for the master data type before you set an additional attribute to key, the attribute cannot be empty in any of the master data records.

The master data type must have at least one key attribute. You can change a key attribute to a non-key attribute if the remaining key combination still has only unique values for all existing master data records.

Compound master data types contain all key attributes of the component master data types, and cannot have any other key attributes. The component master data types cannot have the same key attributes. If you change the key attributes in a component of a compound master data type, you must update the keys of the compound master data type as well.

A virtual master data type doesn’t have key attributes.

Reference master data types must use all key attributes of the referenced master data type as key. Each key attribute of the referenced master data type must be used as a referenced attribute in the reference master data type that is built on it.

If you change the key attribute of the master data type the reference master data type is built on, you must update the key of the reference master data type as well.

An external master data type must contain all the keys of the external data source.

You must activate the master data type and all other entities that use the master data type (planning areas, other master data types) for the changes to take effect.

Required Attributes

Each key attribute of a master data type is a required attribute. You can specify additional attributes as required, or you can change a non-key required attribute to not required at any time. However, if master data records already existed for the master data type when you set an additional attribute to required, make sure that the master data records for this attribute do not contain empty or null values.

You must activate the master data type for the changes to take effect.

6.10 Deleting a Master Data Type

Context

If a master data type is not assigned to any other model entity, and has never been activated, you can delete it.

You must work top down to remove the master data type you want to delete from each model entity that uses it if any of the following applies:

● The master data type is assigned to a planning area.● The master data type is used as a component in a compound master data type, or in a virtual master data

type.● The master data type is used as a reference in a reference master data type.


Master Data Types

Procedure

1. If a master data type to be deleted is used in a planning area, delete the master data type from the planning area by marking it for deletion, then activate the planning area.

Repeat this for all planning areas where the master data type is used.2. If a master data type to be deleted is used in a compound master data type, delete it from the compound

master data type. Activate the compound master data type.

NoteYou can delete a component from a compound master data type only if no data exists for the compound master data type.

Repeat this for all compound master data types where the master data type to be deleted is used.3. If a master data type to be deleted is used in a virtual master data type, delete it from the virtual master data

type. Activate the virtual master data type.

Repeat this for all virtual master data types where the master data type to be deleted is used.4. If a master data type to be deleted is used in a reference master data type, delete the reference master data

type by using active deletion.

NoteYou can delete a reference master data type only if it is not used in any higher-level entities, such as a planning area, or other master data types. Before deletion, you must delete it from all planning areas and master data types.

5. Now use active deletion to delete the master data type you originally wanted to delete.


7 Time Profiles and Time Periods

A time profile is made up of time profile levels (for example, months, quarters, or years). Each level is made up of periods, which are identified by a number, and describe the start and end time of the time period in question.

If you want to perform aggregation or disaggregation along time, then the periods on different levels need to form a hierarchy. In this hierarchy, time profile levels can have multiple parents, and there can be time profile levels without a parent level. For more information about setting up your planning model for aggregating and disaggregating data across different time levels, see Aggregation and Disaggregation of Data Across Different Time Levels [page 189].

ExampleIn the following example, the time profile consists of the following three levels:

● Year● Quarter● Month

Figure 2: Time Profile with Three Time Levels


Time Profiles and Time Periods

The sample models delivered with IBP also provide time profile definitions, for example:

Table 10:

Time Profile ID Description Levels Planning Areas

1 7 Year M, Q, Y Month, Quarter, Year SAP2, SAP4

5 CT DWMQY Day, Week, Month, Quarter, Year

SAP5

7 SAP7 DW Day, Week SAP7

12 W2M SPA D TW W M Q Y Day, Technical Week, Week, Month, Quarter, Year

SAPIBP1

66 SAP6 D W CW M Q Y Day, Technical Week, Week, Month, Quarter, Year

SAP6

74 SAP 74 Day, Technical Week, Week, Month

SAP74

100 4 Years - TW, W, M, Q, Y

Technical Week, Week, Month, Quarter, Year

SAP3

RecommendationSAP recommends that you either create your own time profile or that you copy one of the supplied time profiles to a customer time profile ID, for example, you could copy time profile "1" to time profile "1000".

After creating and activating a time profile, you must load a time profile data file, or schedule an application job to create the time periods.

7.1 Creating Time Profiles

To create a time profile, choose Manage Time Profiles on the initial screen of the Configuration app, or click Time Profiles in the top menu.

Steps

The following example illustrates how to create a time profile with start and end dates and multiple time profile levels, for example, monthly, quarterly, and yearly.

1. Click the New icon.2. Enter a unique time profile ID, for example, 201. Note that the time profile ID is always an integer (of up to 9

digits in length).

Model Configuration GuideTime Profiles and Time Periods C U S T O M E R 37

3. Click OK.4. Enter a description, for example: S2 Time Profile.5. Select the start date, for example, the first day in January, four years in the past.6. Select the end date, for example, the last day in December, two years in the future.7. Click Add Level to add new levels (Monthly, Quarterly, and Yearly) one by one, as shown in the table below.8. Enter level details and horizon values.

For base level, enter the level that is the child in this relationship. For example, for the quarter time profile level, you can enter month as the base level.Specify the period type as well. You can choose from the following period types: day, technical week, week, month, quarter, year, custom (empty value). The time profile levels must form a sequence based on the period type. For example, a time profile level that has the period type “day” must come before the one that has “month” set, and “month” must come before “quarter”.

NoteDay and calendar week refer to the Gregorian calendar.

The default display horizon you set for a time profile level determines the default from-to date range in a planning view in the IBP Excel add-in. The values in the default display horizon fields are relative values compared to the current period. For example, if the current period is May 2016, and you set -3 for default display horizon - past, and 6 for default display horizon - future, then the planning view will offer the time frame from February 2016 to November 2016 as the default.When creating levels, you can enter data values directly in the table rows. For an example, see the table below.

Table 11: Time Profile Levels

Level Name Base Level Period Type Default Display Horizon - Past

Default Display Horizon - Future

1 Monthly Month -6 18

2 Quarterly 1 Quarter -2 6

3 Yearly 2 Year -1 2

9. Save your changes.

NoteWhen you choose Assign Attributes, you can assign any attribute to that level, except for attributes that have the DECIMAL data type.

If the External Time Series flag is enabled for your planning area, do not assign an attribute DATE to a time profile level as it will not be propagated into calculation scenarios.



7.2 PERIODID and PERIODID(n) Attributes in Time Profile Levels

The PERIODID and PERIODID(n) attributes are technical attributes. The PERIODID(n) attribute is the hierarchy level ID for the time period. The PERIODID attribute identifies a specific time period, and not a time profile level. For example, 25503 is the PERIODID for May 2016 as a time period, and 25504 for June 2016. You won't find these attributes on the Time Profiles screen, but you may need them when defining calculations for key figures or attribute transformations.

The assignment of PERIODID(n) attributes varies according to the time profile ID and levels that have been defined. PERIODID0 represents the lowest level of time granularity. If the time profile has multiple time profile levels, then PERIODID1 represents the highest level. The next PERIODID(n) value represents the next highest level of time granularity.

For example, if a time profile is defined with the levels "Day", "Technical Week", "Week", "Month", and "Year", the assignment is as follows:

● PERIODID0: Daily periods● PERIODID1: Yearly periods● PERIODID2: Monthly periods● PERIODID3: Weekly periods● PERIODID4: Technical weekly periods

7.3 Creating Time Periods from Template

You can create time periods from templates in the Data Integration Jobs app. We recommend that you use this option because in the comma-separated values (CSV) file, you can modify the period description if needed, and if you use time profile attributes, you can fill the attributes with data before loading the time periods for the time profile into the system.

Procedure

1. In the Data Integration Jobs app, click Download Template.2. Select Time Periods as the data type.3. Select the time profile from the dropdown list and specify whether you want to prefill the template with new or

existing time periods.○ If you leave the Prefill Template dropdown blank, the template doesn’t contain any time profiles.○ If you select With New Time Periods, the template contains the time periods in accordance with the value

in the Time Profile field. Note that if periods already exist, this option is grayed out.○ If you select With Existing Time Periods, the template contains time periods that already exist in the

system for the time profile, for example, because they have been uploaded at a previous point in time.


4. Click Download.

Results

A file is generated for you to use as a template with the correct, comma separated headers for your data type. You can now fill out the template with the correct values, save it, and use it to upload data to the system.

Next Steps

Upload the time periods.

7.4 Creating Time Periods for a Time Profile

Use an application job to generate time periods for the time profile specified.

To generate the time periods for a time profile, you use an application job.

NoteYou can also create time periods in the following ways:

● In the Data Integration Jobs app by uploading them from a CSV file● By uploading them from SAP HANA Cloud Platform, integration service

For more information, see Data Integration Jobs in the application help.

We recommend that you use the above options if you are working with complex time profiles, that is, time profiles that contain time profile levels of the custom period type, or if you have assigned attributes to time profile levels.



Time periods are generated for days, (technical) weeks, months, quarters, and years. The start and end dates for the time periods are taken from the selected time profile. The following table illustrates how technical weeks work:

Figure 3: Grouping of Days into Technical Weeks

Setting Up the Application Job

1. From the Fiori launchpad, under Administrator, select the Application Jobs tile.The Application Jobs screen appears.

2. To create a new application job, select New.3. Under Job Details, from Job Template, choose the Create Time Periods for Time Profile template.4. Under Time Profile, enter the ID for the time profile for which you want to generate time periods.5. Choose Schedule.

Analyzing the Results

1. To view the results of the job, go to the Application Jobs screen, where all the jobs are listed.2. To see the log messages, select the Information icon in the Job column of the finished job.

7.5 Changing and Deleting Time Profiles

You may want to change a time profile. However, you’ll find that not all fields on the time profile screen are available for editing. The changes you can do depend on the following factors:

● The status of the time profile: active or inactive● If the time profile is assigned to planning areas or not● If time periods have already been created for the time profile

NoteIf you have created and saved a time profile, but have not activated it yet (that is, only an inactive instance of the time profile exists), you can change any parameters of the time profile. You can also delete the time profile.


If a time profile has already been activated (even if it currently has an inactive instance), certain rules apply for which fields or parameters you can change or delete.

Changing a Time Profile

Description

You can change the description of a time profile any time.

Start Date and End Date

If the time profile is not used in any planning area, you can change the start date and end date of a time profile at any time.

You have to activate the time profile for the changes to take effect.

NoteIf changing the start and end date of the time profile extends the entire validity period of the time profile, in other words, if the new start date is earlier than the old start date or the new end date is later than the old end date, no time periods will exist for these parts of the time profile. In such a case, you need to create the missing time periods by either uploading them, or by using the application job for creating time periods.

CautionIf the time profile is already used in a planning area and transactional data exists, changing the time profile dates is not recommended as it may cause issues.

RecommendationWe recommend that you define the start and end date of the time profile so that no changes to the dates are needed. For example, define the end date many years in the future.

Time Profile Levels

You can’t delete time profile levels.

You can change the base level, the period type, and the default display horizon of time profile levels.

If time periods already exist for the time profile, even if the time profile isn’t assigned to any planning areas, and you add a new time profile level, you’ll have to upload the time periods again.

If the time profile is already assigned to a planning area, you can’t add new time profile levels.


Attributes Assigned to Time Profile Levels

You can assign additional attributes to a time profile level any time. Keep in mind that you can assign an attribute to one time profile level only. If you have assigned an attribute to a planning area, you can't assign the same attribute to a time profile level.



To set an attribute to required, you must have data uploaded for the attribute for each time period. You can activate the time profile only if all time periods are uploaded with a value for this attribute (empty values are not allowed).

If time periods already exist for a time profile, you can add a new required attribute in two steps. First, assign the attribute to the time profile level without setting it to required. Activate the time profile, then upload the time periods with this attribute filled out. Make sure that you don’t change any other data for the already existing time periods. As the last step, in the time profile definition, mark the attribute as required.

You can remove an assigned attribute from a time profile level only if the given attribute is not used in any planning levels.


Deleting a Time Profile

You can delete a time profile only if it is not assigned to any planning areas. You delete an active time profile in two steps, using the active deletion.

First, when you choose Active deletion, the system creates a new instance of the time profile, which has the pending deletion status. When you activate the time profile, the system carries out the deletion: both instances (active and pending deletion) are deleted.

If you delete a time profile, the time periods that belong to the given time profile are deleted as well.


8 Planning Areas

A planning area is a model entity that defines the structure and forms the backbone of the planning process. A planning area consists of its assigned time profile, attributes of master data types, planning levels, key figures, and versions. You could compare this to SAP APO or SAP ERP, where tables, table values, and configuration are defined to support the planning process.

Planning areas can contain multiple planning data sets, that is, a base version data set and additional version data sets. The versions are for alternative plans for all or part of what is in the base version and need to be configured and activated. Versions can share master data with the base version or can be based on independent sets of version-specific master data. Scenarios defined by users also exist, which lie on top of the versions (including the base version).

A company can have multiple planning areas to enable the processes of SAP Integrated Business Planning in different business units.

NoteAs you can use the SAP Integrated Business Planning, add-in for Microsoft Excel for only one planning area at a time, there are limitations to this use case.

Separate planning areas are also used for configuration work to separate on-going configuration activities from end-user testing, for example, or to separate the work from different project phases. See Best Practices for Transporting Planning Models [page 160].

A planning area consists of the following settings and model entities:

● Name, for example, ABC● Description, for example,: ABC’s planning area● Time Profile: time profile ID (160)● Storage Time Profile Level (for example, weekly or monthly)● Planning horizon● List of selected attributes, and the master data types they originate from, for example:

Table 12:

Attribute Master Data Type

CUSTTYPE CUSTOMER

LOCTYPE LOCATION

PRDID PRODUCT

PRDDESC PRODUCT

MKTSGMNT CUSTOMERPRODUCT


Planning Areas

Attribute Master Data Type

CMPNTID COMPONENT

● Planning levels● Key figures● Versions (optional)● Assigned planning operators (optional)● Additional parameters, such as the enablement of the planning area for supply planning or for change history

8.1 Creating Planning Areas

Create a planning area to group and structure your model entites, and to configure which processes of SAP Integrated Business Planning are enabled.

Context

The following example illustrates how to create a planning area by entering header data and then assigning master data types, attributes, a time profile, and by defining planning levels, key figures, and versions.

Steps

Imagine that you want to create a planning area ABC.

1. Navigate to Planning Area and Details in the Configuration app.2. Click New, and enter a Name: ABC.3. Click OK.4. Enter the following details:

Table 13:

Field Entries

Description ABC

Time Profile Select a time profile, for example, “201”.

Storage Time Profile Level Select the lowest level of granularity of the assigned time profile. This defaults to Monthly level of time profile “201”.

Model Configuration GuidePlanning Areas C U S T O M E R 45

Field Entries

Current Period Offset NoteCurrent period offset allows you to shift your planning period. For example, -1means the current period starts from the previous period of the lowest time profile level. In this example, with time profile “201”, the current period starts from the previous month.

5. Click the Planning Horizons icon and enter from and to values for the planning horizon for each time profile level. For example, for Month, enter the following values:

Table 14:

Field Entries

Planning Horizon From -6

Planning Horizon To 18

6. Click OK.7. To assign planning operators, such as inventory optimization or forecasting, to the planning area, click the

Planning Operator icon, and select the planning operators you want to use in the planning area.8. Click OK.9. Select the Available Attributes dropdown.

NoteTo make it easier to find master data types and attributes, you can set a filter, for example, filter by the prefix “ABC”.

10. Select the attributes to be assigned to planning area ABC. By selecting an attribute, you also assign the master data type using that attribute to the planning area. With that, you define how you want to segment planning data.

ExampleYou want to analyze sales data based on the product, location, and customer dimensions. To achieve this, select attributes of the master data types representing the product, the location, and the customer.

The attributes you select here for the planning area will be available for creating planning levels. In SAP Integrated Business Planning, add-in for Microsoft Excel, you can use the attributes you assigned to a planning area when you create a planning view.

Note○ Selecting a master data type automatically selects all attributes that are part of that master data type.

You can verify this by expanding the master data type.○ In case multiple master data types use an attribute, you must assign the attribute to the planning area

only once.


Planning Areas

○ Make sure that you use each attribute assigned to the planning area in one or more planning levels.○ If you assign a compound master data type to a planning area, make sure you also assign its

component master data types. Similarly, if you assign a reference master data type or a virtual master data type to a planning area, assign their referenced master data types as well.

○ Make sure you do not select the key attributes of a compound master data type. Instead, select the key attributes from the simple master data types that are the components of the compound master data type.

○ If the ID attribute of a master data type is linked to a description attribute, you only need to include the ID in the planning area. The description is then included via the link. For more information about linking ID and description attributes, see Description Attributes [page 23].

○ The Time Reference Attribute, From Period, and To Period fields are relevant for attributes defined as key figures.○ If you don't specify a value in either of the Time Reference Attribute, From Period, and To Period

fields, the value of the attribute is copied to the key figure for the entire calendar, which is determined by the time profile assigned to the planning area.

○ If you specify an attribute in the Time Reference Attribute field, the value of the attribute defined as a key figure is copied over to the key figure only for the period determined by the time reference attribute. The key figure values for other periods are cleared. The attribute specified for time reference attribute must have the TIMESTAMP data type.

○ You can specify a start period (From Period) and an end period (To Period) to restrict the time interval for which the value of the attribute is copied over to the key figure. The values you provide here are relative values, on the basis of the current period, determined by the base planning level of the key figure. In this case, the attribute value is copied over for the specified time interval, or for the subset of the specified time interval that is available in the time profile.

RecommendationTo improve the performance of your SAP Integrated Business Planning system, and reduce memory consumption, SAP recommends specifying exact values for From Period and To Period

You can specify either or both of these values, but you can't specify a Time Reference Attribute for the same attribute as key figure.

For more information about setting up an attribute as key figure, see Example: Defining an Attribute as a Key Figure [page 193].

○ You cannot specify attributes as key figures for reference or virtual master data types.

11. Make other settings as needed.The following table contains information about the additional fields for a planning area:

Table 15:

Property Description

Supply Planning Enabled If supply planning is enabled for a planning area, users can invoke advanced supply planning functions, such as heuristics and optimizers.

External Time Series Enabled Enables the configuration for the usage of external key figures.



Change History, Planning Area Enabled Enables change history for planning areas.

CautionIf you select the Change History, Planning Area Enabled checkbox, and later decide to unselect it, the previously recorded change history of the planning area will be deleted upon the next activation of the planning area.

Business Meaning Provides a semantic connection between the attribute ID or key figure ID that you specify and the code, letting the system know for what purpose you want to use a certain key figure or attribute.

Attribute Category See Validate Master Data for New Planning Objects [page 48].

Filter Setting You can choose from the available options: Display, Auto-Open in Explorer, and Do Not Display.

Group By Setting You can choose from the available options: Display and Do Not Display.


8.2 Validate Master Data for New Planning Objects

In the Configuration app, on the Planning Area and Details screen, you can assign an attribute category to a planning area attribute to specify whether master data has to exist for the attribute when new planning objects are added in the IBP Excel add-in or during data integration.

By default, all attributes have the category NULL (optional).

Table 16:

Attribute Category Explanation Relevant for Data Integration

Relevant for New Planning Objects

Mandatory The attribute value must be found, although the value itself might be NULL. That is, master data must exist.

Yes

Key figure records for which no attribute value is found (that is, where the master data is missing) are rejected.

Yes

If no attribute value is found (that is, the master data is missing), the planning object is omitted from the new set of planning objects.


Planning Areas

Attribute Category Explanation Relevant for Data Integration

Relevant for New Planning Objects

Optional (default value) An attribute value does not have to be found. That is, master data does not necessarily have to exist.

Yes

No attribute value is found (master data missing). The planning level attribute value is set to NULL, and the key figure record(s) are processed for that planning object.

Attribute value is found (master data available) The planning level attribute value is set to fetched value, and the key figure record(s) are processed for that planning object.

Yes

Irrespective of whether an attribute value is found (master data missing or available), that planning object stays in the set of new planning objects, and attribute value is set to found value or NULL respectively.

Calculated The attribute value must be found, although the value itself might be NULL. That is, master data must exist.

As this indicator is not relevant for either data integration or for new planning objects, select value NULL in both cases. Values for such attributes will be calculated using an operator of some description and must not be overwritten by data integration.

No No

ExampleFor the Customer-Product master data type the Market Segment attribute is defined with the following records:

Table 17:

Product Customer Market Segment

P1 C1 Small

P2 C2 Medium

P3 C3 Large


Product Customer Market Segment

P4 C4

The following list shows the effect of assigning the different attribute categories to planning area attribute Market Segment:

● MandatoryIn this case you can only import a key figure or create a new planning object for the records that exist in the CustomerProduct table. The value for Market Segment from the master data is populated. Null values for attribute are allowed.If you try to import data for the planning object, for example, P1/C2, the record is rejected.

● OptionalIn this case you can import data in a key figure or create a new planning object irrespective of whether the master data exists in the CustomerProduct table.If you try to import data for the planning object, for example, P1/C2, the record is processed. The value for Market Segment is set to null in the planning object.

● CalculatedIn this case you can only import key figure or create a new planning object for the records that exist in the CustomerProduct table. The value for Market Segment from master data is not considered.If you try to import data for the planning object, for example, P1/C2, the record is rejected.

8.3 Replacing the Time Profile in an Active Planning Area

Choose a different time profile for a planning area, and perform additional required configuration steps.

Context

To adhere to business requirements, you want to change the time granularity at which planning data is stored and aggregated in your planning model, so you assign a different time profile to the planning area.

You have to perform additional configuration steps and data integration tasks - including the deletion and reupload of key figure values if key figure values already exist in the planning area - to keep the planning model consistent and be able to activate the planning area after you have replaced the time profile.

CautionReplacing the time profile in an active planning area is a critical configuration task that cannot be standardized, and may result in invalid planning data.

SAP recommends that you do a thorough test – including all the additional configuration and data integration tasks described below – in a test environment before you make this change in the productive environment.

SAP recommends that you consider creating a new planning area instead of replacing the time profile in a planning area that is already in use, and contains key figure values.


Planning Areas

Procedure

1. Replace the time profile in the planning area.2. Specify the planning horizons for each time profile level.

If the Planning Horizons table is filled out, overwrite the values in the From and To columns.3. Check, and if needed, update the planning levels.

A planning level is a combination of attributes. As for time, the system uses the PERIODIDn attribute, but displays the name of the time profile level that belongs to a specific PERIODIDn attribute. For more information, see PERIODID and PERIODID(n) Attributes in Time Profile Levels [page 39].

The assigned PERIODIDn attribute to a time profile level may be different for each time profile.

For example, both the old and new time profiles have month as a time profile level, but in the old time profile, month was assigned PERIODID2, and in the new time profile, PERIODID1. When using the old time profile, PERIODID2 corresponded to month, but in the new time profile, it represents the technical week.

Check each planning level if they have to be updated because a time profile level is not available in the new time profile, or because the assignment of the PERIODIDn attribute is different.

4. If an attribute is assigned to one or more time profile levels of the old time profile, make sure that you carry over the attribute if it’s used in the new profile as well, or remove its usage, if it’s not needed anymore before you activate the planning area.

CautionReplacing the time profile in an active planning area marks the assignment of an attribute to a time profile level for deletion.

If the same attribute is assigned to a time profile level in the new time profile, revoke the pending deletion of the assignment of the attribute for each planning level that uses the attribute.

In the Configuration app, on the Planning Levels screen, choose the Active Deletion button, deselect the Mark for Deletion checkbox, and save the planning area.

If the attribute is not assigned to any time profile levels of the new time profile, make sure that the attribute is not used anywhere in the planning area. With the next activation of the planning area, the attribute is removed from the affected planning levels. If necessary, in the Configuration app, on the Key Figures screen, update the disaggregation expressions of key figures so that they don’t use the attribute anymore.

5. For key figures using planning levels that have been changed: Update the base planning level and the affected calculations to reflect these changes.

6. Update attribute transformations, if any is used in the planning area, so that the time offset remains correct, and no attributes are used that were assigned to a time profile level in the old time profile only.

7. If you use L-code in key figure calculations, create a customer incident to request the update of the L script.8. Create periods for the new time profile, if they don't exist yet.9. If key figure values already exist in the planning area, delete them.

Key figure values are stored per time period (per the ID of a unique time period, such as April 2017). In a different time profile, the same period ID may point to a different period, which would make the data inconsistent.

10. Activate the planning area.


11. Upload the key figure values.12. If the planning area includes an attribute as a key figure, upload the master data records for the master data

type that contains the attribute used as key figure.

Related Information

Creating Planning Areas [page 45]PERIODID and PERIODID(n) Attributes in Time Profile Levels [page 39]Change and Deletion of Planning Levels [page 56]Example: Attribute Transformations [page 200]Creating Time Periods for a Time Profile [page 40]Activating Planning Areas [page 140]SAP Note 2238382


Planning Areas


9 Planning Levels

A “planning level” is a set of attributes that identify and label key figure values, and forms part of the definition of a planning area. The attributes you have assigned to the planning area are available to form planning levels, as well as the time profile levels, and the attributes assigned to the time profile levels.

A planning level enables you to analyze and plan at a specific aggregation level, for example, at the planning level period-product-customer. Key figures in SAP Integrated Business Planning are calculated or stored at specific planning levels. Depending on the planning level – that is, the specific set of attributes that is used in a key figure query – different calculation and/or aggregation steps are performed to compute the key figure numbers at that level. These calculation/aggregation steps are defined by specifying key figure calculations.

We differentiate between “root attributes” and “non-root attributes” of a planning level:

● Root attributes are necessary as keys to identify (find) individual key figure values. They define the independent dimensions in which the key figure values exist. The root attributes are often also the keys of master data types but this is not a necessary condition.

● Non-root attributes are also associated with the key figure values but don’t on their own uniquely identify what the key figure value is for. They can be thought of as labels (sometimes hierarchies) to aggregate key figure values.

NoteA key figure SALESFORECAST might depend on the following attributes:

Table 18:

Attribute Description Root Attribute (X)

PRDID Product ID X

CUSTID Customer ID X

REGION Sales Region

PRDGRP Product Group

PRDFAM Product Family

MARKET Market Segment

PERIODID0 Month X

Let’s assume that the attributes PRDID, CUSTID, and PERIODID0 are the root attributes. Let’s call this set of attributes the planning level PRDCUST. (You could choose any name for the planning level.)

The implication is that every stored key figure value for SALESFORECAST depends on a value for PRDID, CUSTID, and PERIOIDID, that is, on a value for a Product ID, a Customer ID and a Month. For example, the forecast for sales (SALESFORECAST) of product P1 to customer C1 in 2015/12 might be “100”.

Model Configuration GuidePlanning Levels C U S T O M E R 53

The key figure value also depends on the other attributes. For example, you could ask about the SALESFORECAST for the market segment “M1”. MARKET might, for example, be an attribute of customer or customer product: You specify the origin of the attributes in the planning area.

When key figure data is loaded, the system determines all attribute values based on the given root attributes of the planning level. If these values cannot be uniquely determined, the data set contains an error.

Related Information

Creating Planning Areas [page 45]Creating Key Figures [page 63]Key Figure Calculations [page 71]

9.1 Creating Planning Levels

Create a planning level that you use to store, calculate, query and analyze planning data at a specific granularity.

Prerequisites

The following modeling tasks have already been carried out:

● A time profile has been created.● Attributes and master data types have been created.● A planning area has been created.● A time profile and attributes from master data types have been assigned to the planning area.

Context

A planning level is a set of attributes that enables you to store and analyze planning data at a specific granularity. You use the planning level you create here for defining key figures and their calculations, and for querying key figure values.

The following example illustrates how to create the required planning levels for a planning area.

ExampleImagine that you want to create the planning level PERPRODCUST, which has Month, PRDID and CUSTID as root attributes, as well as other attributes of the master data types S2PRODUCT and S2CUSTOMER.


Planning Levels

Procedure

1. Choose Manage Planning Levels on the initial screen of the Configuration app, or click Planning Levels in the top menu.

At the top of the screen, make sure that the planning area selected is your planning area.2. Click New, and enter a Name: PERPRODCUST.

3. Click OK.4. Enter a description: Period/Product/Customer.

5. Select the time attribute from the time profile.6. Select the master data types and attributes you want to include in the planning level. You can select the

attributes and master data types that you have previously assigned to the planning area on the Planning Area and Details screen.

Example○ S2PRODUCT○ S2CUSTOMER

All attributes of the master data type to be included in the planning level are selected along with the root attributes.

NoteYou cannot assign time profile attributes to planning levels from the Configuration app.

If the ID attribute of a master data type is linked to the description attribute, you only need to include the ID in the planning level. The description is then included via the link. For more information about linking ID and description attributes, see Master Data Types [page 22].

7. Validate that the root attributes are selected, as in the table below.

Table 19:

Planning Level Description Master Data Root Attribute

PERPRODCUST Period/Product/Customer Time Profile

S2PRODUCT

S2CUSTOMER

1-Monthly

PRDID

CUSTID

NoteA planning level can include root attributes that are not keys of a master data type. For example, in the SAP2 model, the planning level PERPRODFMLCUSTRGN includes PRDFAMILY and CUSTREGION as root attributes, though PRDFAMILY is not a key attribute of master data type IBPPRODUCT.

You cannot set multiple time profile levels as root attributes of a planning level.


If multiple planning levels will be used as the base planning level of stored key figures, and these planning levels have identical root attributes (not taking the time attribute into consideration), ensure to set identical non-root attributes as well.

Make sure that you use all attributes you assigned to the planning area in one or more planning levels.

For information about additional fields on the Planning Levels screen, see the table below:

Table 20:


Conversion Source Indicates that an attribute is used as a source unit for conversion purposes.

Conversion Target Indicates that an attribute is used as a target unit for conversion purposes.


Results

The planning level is saved as an inactive planning level.

Next Steps

Activate the planning area to activate the planning level you created. You cannot activate a planning level directly.

9.2 Change and Deletion of Planning Levels

The changes you can make to a planning level depends on if the planning level is used in key figures, and if values exist for those key figures. For certain changes, and for the deletion of a planning level, you must perform several configuration steps in a given order.

You create the planning levels to use them in key figure definitions (as the base planning level of a key figure) and in key figure calculations.

Whether you can change a planning level or not depends on if the planning level is used in key figures, and if data (key figure values) already exists for the key figures that use the given planning level. The Used in Key Figures field shows you if the selected planning level is already used in key figure definitions or calculations.


Planning Levels

Description

You can change the description of a planning level any time.

NoteYou cannot change the ID of a planning level.

Attributes

You can add an additional non-root attribute to a planning level.

You can remove a non-root attribute from a planning level only if the attribute is not used in any key figure calculations.

To remove a non-root attribute that is used in key figure calculations, first edit the key figure calculations so that none of them includes the attribute. Only then can you remove the attribute from the planning level.

NoteA planning level must have at least one attribute.

Root Attributes

CautionChanging the root attribute of a planning model may result in inconsistency between the planning model and the already existing data.

SAP Integrated Business Planning is designed to preserve the consistency of the planning model and the planning data. If such a change is made that would break the consistency, IBP keeps the planning data intact, and rejects the change of the model by making the next activation of the planning model fail.

You can set an additional attribute to root if the planning level is not used in any key figures, or if the key figures that use the given planning level as their base planning level do not have key figure values.

If the planning level is not used, or if the key figures that use a given planning level as their base planning level do not have key figure values, you can set a root attribute to non-root.

If key figure values exist (by upload or by manual edit of data in the planning view), you must follow this procedure if you want to set a root attribute to non-root:

1. Delete the values of the stored key figures that use the planning level.To do this, in the IBP Excel add-in, delete all values of all stored key figures that use the planning level. The cells of key figure values must be empty. Then delete the planning objects by choosing Delete Planning Objects.


2. In the Configuration app, set the root attribute to non-root.

NoteA planning level must have at least one root attribute.

Deletion of a Planning Level

You can delete a planning level if it is not used in any key figures.

To delete a planning level that is in use, to keep your data consistent, you must follow this procedure:

1. Delete the values of the stored key figures that use the planning level.To do this, in the IBP Excel add-in, delete all values of all stored key figures that use the planning level. The cells of key figure values must be empty. Then delete the planning objects by choosing Delete Planning Objects.

2. In the Configuration app, delete all key figures (definitions) that use the planning level to be deleted.3. In the Configuration app, delete the planning level.

CautionIf you delete all stored key figure definitions that use a given base planning level, you must delete their key figure values first to keep your data consistent.

9.3 Examples of Planning Levels

The following are examples of planning levels from the SAP2 sample planning area:

● Planning Level PERPRODFMLCUSTRGN○ Dimensions: time, product, customer○ Root attributes: Monthly, Product Family, Customer Region○ Base planning level for the Finance Qty key figure. That is, data for Finance Qty is loaded at the granularity

level of date, product family, and customer group. Product Family is an attribute of the master data type Customer. Attributes of planning level PERPRODFMLCUSTRGN cannot have a granularity level lower than Product Family. For example, Product ID is not a valid attribute for planning level PERPRODFMLCUSTRGN.


Planning Levels

Figure 4: Planning Level PERPRODFMLCUSTRGN● Planning Level PERLOCRES

○ Dimensions: time, product, customer○ Root attributes: Monthly, Location, and Resource○ Base planning level for capacity key figures, for example, Capacity Overload Alert, Available Capacity,

Handling Capacity Load, and Utilization Pct

Figure 5: Planning Level PERLOCRES● Planning Level PERPRODLOC

○ Dimensions: time, product, location○ Root attributes: Monthly, Product, and Location.○ Base planning level for inventory-related key figures (amongst other things), including Initial Inventory,

Inventory Target, and Inventory Target Cost


Figure 6: Planning Level PERPRODLOC● Planning Level PERPRODCUSTCURRCURRTO

○ Dimensions: time, product, customer, source currency, target currency○ Root attributes: Monthly, Product, Customer, Currency, and Currency To○ Planning level for the Target Revenue key figure

At this planning level, we perform currency conversion by multiplying exchange rate by a currency key figure such as Target Revenue. This planning level is used purely for calculation, and there are no stored key figures.

Figure 7: Planning Level PERPRODCUSTCURRCURRTO


Planning Levels

10 Key Figures

Key figures are series of numbers over time, where each number corresponds to a particular time period value.

Key figures have a business context: In SAP Integrated Business Planning, end users view and use key figures in the planning views or in Analytics. Every key figure has a base planning level.

Key figures are associated with a key, which is a combination of attributes from one or more master data objects.

Key figures represent variables that are associated with attributes (master data types), and can be imported into the SAP Integrated Business Planning system, calculated, and/or manually edited.

ExampleExamples of key figures are Sales Forecast, Marketing Forecast, Consensus Demand Plan, Projected Inventory, Capacity Plans or actual data such as Sales Orders and Shipment History.

Once you have created your attributes, master data types, time profiles, and planning areas and levels, you define the key figures you want to include in your planning model.

For more information, see Creating Key Figures [page 63].

CautionTo run the inventory operators and S&OP operators, you have to use specific technical IDs defined by SAP for the relevant key figures and also for master data types and attributes. For demand sensing, the same applies to certain key figures and master data attributes. For more information, see the documentation of the relevant planning operator in this guide and the respective chapter of the application help.

10.1 Types of Key Figures

When you create key figures, you can select between the following:

Table 21:

Type Explanation

Key figure The key figures that end users view in the planning views or in Analytics.

Model Configuration GuideKey Figures C U S T O M E R 61

Type Explanation

Helper key figure Helper key figures are typically used for results of intermediate calculations in a regular key figure or else in another helper key figure. For example, they can be used to break down a large calculation into manageable subcalculations.

Helper key figures that are not visible to the end user and do not have a base planning level. They can be used at request level or at any other planning level. They are used in calculations that have more than 3 inputs at different planning levels.

Helper key figures are primarily used in ratio calculations, last period aggregation, and in cost calculations. You can also use them in cases where the same key figure would otherwise occur twice in a single calculation. (You cannot use the same key figure name twice in one calculation.)

As they are used only in calculations, helper key figures do not have key figure properties such as “stored”, “editable”, “aggregation”, and “disaggregation”.

For ease of identification, helper key figures are usually prefixed “H”.

Attribute Transformations Attributes of master data types that are assigned to a planning level can be transformed to a different value based on certain conditions, for example, Period ID can be transformed to calculate lead time offset.

For more information, see Example: Attribute Transformations [page 200].

Attributes as Key Figures As well as creating key figures, you can define attributes as key figures: You can assign attributes of a master data type as a key figure. For example, unit price is an attribute of CUSTOMERPRODUCT, that is, it has a single value for a unique customer and product combination. This attribute can be defined as a key figure such that the same unit price value can be repeated across the specified time periods of the customer and product combination.

For more information, see Example: Defining an Attribute as a Key Figure [page 193].


Key Figures

NoteNote the following guidelines with respect to key figures:

Table 22:

Key Figures Affected Guideline

Supply Planning input and output key figures Must be stored key figures

Input key figures added via data integration Mark as Stored. If you need to edit such a key figure, mark it as Editable.

Quantity and value key figures Typically set to aggregation mode SUM, MIN, or MAX. If such key figures are defined as Editable, Disaggregation Mode is set to Proportional if aggregated value is not zero; otherwise, equal distribution.

Ratio, price, cost, and percentage key figures Typically set to aggregation mode Custom, Min, Max, or Avg. If Editable, typically set to Proportional if aggregated value is not zero; otherwise, Copy Value To or Copy Value.

Such key figures generally have request level calculations.

More Information

Creating Key Figures [page 63]

Example: Defining an Attribute as a Key Figure [page 193]

10.2 Creating Key Figures

Context

Once you have created your attributes, master data types, time profiles, and planning areas and levels, you define the key figures you want to include in your planning model.

Steps

1. Choose Manage Key Figures on the initial screen of the Configuration app, or click Key Figures in the top menu.

2. Select the Key Figure radio button.


3. Enter an ID for the key figure, for example, SALESFORECASTQTY.4. Select the desired base planning level from the drop-drown menu (for example, PERPRODCUST).

NoteNote the following regarding the key figures within a planning area:

Key figures may have different base planning levels. However, if multiple planning levels that are used as the base planning level of stored key figures have identical root attributes (not taking the time attribute into consideration), ensure to set identical non-root attributes as well.

5. Fill out the header data as required:

Table 23:

Field Label Explanation

Display Settings Determines how the key figure is displayed in Analytics. (Note that Microsoft Excel and add-in formatting mechanisms are used to display key figure data in the Excel Add-In.):

Decimal Places: Specify the number of decimal places required. The default setting is 6 decimal places.

Display as Percentage: Select to display the key figure as a percentage.

Base Planning Level Shows the planning level you selected earlier.

Aggregation Mode SUM (default value), MIN, MAX, AVG, CUSTOM

You use aggregation mode CUSTOM in the following cases:

● When key figures have complex calculations at request level, for example, Unit Price, which has inputs at request level.

● When the base planning level is different from the planning level used in the request level calculation, for example, in unit of measure or currency conversions.

Disaggregation Mode Disaggregation mode is available only for key figures for which Edit Allowed is selected. Select from the following:

● Proportional if aggregated value is not zero; otherwise, equal distribution. Typically used for quantity and revenue key figures.

● Copy Value● Equal Distribution● Proportional if aggregated value is not zero; otherwise,

copy value to Typically used for price and cost key figures, for example, CONSENSUSDEMANDPRICE and COSTPERUNIT.


Key Figures


Disaggregation Expression Used to enter a disaggregation expression, that is, a mathematical expression that disaggregates the values entered for the key figure that is defined using other attributes and key figures. The following conditions apply to disaggregation expressions:

● All the key figures in the expression must be stored and must have the same base planning level as the key figure for which the expression is defined.

● All the attributes must be from the base planning level of the key figure for which the expression is defined

You can enter a disaggregation expression only when Edit Allowed has been selected.

Examples of values in Disaggregation Expression:

● "KEYFIGURE1"● "KEYFIGURE1" + "KEYFIGURE2"● "KEYFIGURE1" + "ATTRIBUTE"● (IF(ISNULL("ADJUSTEDACTUALSQTY"),"ACTUALSQTY

","ADJUSTEDACTUALSQTY"))

NoteYou must enter key figure IDs and attribute IDs in uppercase, and place them in double quotation marks.

ExampleA demand planner has a product family PF1 with only two products, P1 and P2. These products have the following values at the base planning level:

Table 24:

Product Customer

Month Marketing Forecast Qty

Actuals Qty 12 Months Offset

P1 C1 Jan 100

P2 C1 Jan 200



At the aggregated level, the values for the product family are as follows:

Table 25:

Product Family

Customer



PF1 C1 Jan 300

The demand planner would now like to disaggregate the marketing forecast quantity to individual products in the product family proportionally based on the key figure Actuals Qty 12 Months Offset.

If, at the aggregated level, the demand planner enters 330 for Marketing Forecast Qty without the expression in the Disaggregate Expression box, the quantity would be distributed equally between the two lower levels as 165 and 165. Now, with the disaggregation expression, the values are disaggregated based on values in reference key figure Actuals Qty 12 Months Offset as follows:

Table 26:

Product Customer



P1 C1 Jan 110 100

P2 C1 Jan 220 200

Snapshot Key Figure By default, this field is grayed out. However, if the key figure was created from the Manage Snapshot window, then the Snapshot Key Figure in the Key Figure window is enabled.

Note that snapshot key figures are system generated and are always stored.


Key Figures


Alert Key Figure Calculated key figures with user-defined criteria that monitor and manage the execution of business plans. Alert key figures must be calculated. They cannot be stored or edited.

Alert key figures can only have the values" 0" or "1", meaning that the alert itself is either ON or OFF. Alerts typically check conditions on other key figures, such as TargetRev vs. ConsensusRev > 10%.

Stored Indicates a key figure in which data is stored at a defined base planning level.

Note that all edited key figures are designated as Stored. However, an imported key figure can be designated Not editable. (For example, Actuals Qty must not be changed.)

NoteSelect both Stored and Calculated only.for key figures that are configured to default to another key figure. See Defaulting to Another Key Figure.

Edit Allowed Select from the following:

● Not Editable● System Editable● Editable in the Current or Future● Editable in the Past● All Editable

Calculated Key figures in which values are always calculated based on user-defined formulae (for example, Revenue = Qty * Price).

This type of key figure is usually not editable. However, to support use cases such as defaulting, a key figure can be both editable and stored. For more information about defaulting, see Defaulting to Another Key Figure [page 81].

Key figure calculations (calculated key figures) are made at a defined planning level, which can be different from the level on which a user requests to view the key figure. An IBP planning area typically includes key figures from multiple planning levels, which can be linked with calculations that often result in key figures at additional planning levels..



I/O for Supply Planning Indicates an input and/or output key figure for supply planning. If the planning area is enabled for supply planning, this field determines whether the key figure is used as an I/O for supply planning.

NoteTo enable a planning area for supply planning, navigate to Planning Area and Details in the Configuration user interface, select your planning area, and select Supply Planning Enabled.)

Convert Using Used for disaggregation of conversion key figures. Required only for key figures that are editable. Select the key figure that you want to use to convert the current key figure.

NoteThis key figure must be a stored key figure and not a calculated one, as calculation rules are not executed.

Change History Enabled Indicates that changes to the key figure will be tracked. For more information, see Enabling Change History for Key Figures [page 206]

10.3 Copying Key Figures

Context

Note the following with respect to copying key figures:

● The associated planning area must have the status Active or Inactive.● You can copy key figures only within the same planning area.● The planning area must be within the customer space.● When you copy a key figure, the new key figure has the same type (for example, when you copy a helper key

figure, the new key figure is also a helper key figure).

Steps

1. Choose Manage Key Figures on the initial screen of the Configuration app or click Key Figures in the top menu.2. In the dropdown menu on the top right of the screen, select Edit Active and Inactive3. In the list of key figures on the left of the screen, select the key figure that you want to copy.4. Choose Copy.


Key Figures

5. Enter the ID for your new key figure.6. Choose Copy.

The source key figure is copied to the new key figure.7. Review the new key figure and adjust the properties as required, adapt calculations, and remove any

calculations that you do not need.

10.4 Changing Key Figures

Context

You can change all properties of a key figure except the key figure ID.

You can change the key figure name and description of an active key figure. For all other changes, the key figure must be inactive.

10.5 Display Options for Key Figures

Context

You have the following display options for key figures in the Key Figures screen of the Configuration app:

Table 27:

Left-Hand Panel

Search this view Search for key figures in the planning area

Toggle Key Figure ID/Key Figure ID and Name Toggle between listing only the IDs of the key figures and both the IDs and the names of the key figures.

Toggle Key Figures/Planning Levels Toggle between the key figures and the planning levels associated with the key figures.

Expand All Expand the list to display both key figures and the associated planning views.

Collapse All Collapse the list. You can see only key figures or planning levels (according to which list you are viewing).


Left-Hand Panel

Formula/Graph View Toggle between the calculation expression for a key figure and the calculation graph

NoteThe calculation graph for a key figure does not show a complete graph when one of the input key figures has an attribute transformation.

Table 28:

Dropdown Menu on Top Right

Edit Active and Inactive List active and inactive elements

Display Active Only List active elements only

Display SAP Sample List the elements for the SAP sample model you select

10.6 Creating External Key Figures

Context

External key figures enable SAP Integrated Business Planning to work with special stored key figures where the actual time series content comes from an external database. To use external key figures, the application-relevant orders, for example, sales orders or purchase orders, have to be aggregated and integrated from ERP to an SAP HANA database table inside the Integrated Business Planning system using a near real-time integration mechanism. When you set up your planning model, you have to define an external key figure or key figures referring to this table. Since the integration is continuous, the reference key figure data always contains the latest aggregated entries from SAP ERP. Therefore, there is no need for manual update.

Steps

To create external key figures you have to do the following:

1. Go to the Planning Area and Details screen by choosing Define Planning Area on the initial screen of the Configuration app or click Planning Area and Details in the top menu.

2. Select the External Time Series Enabled checkbox.3. Click Save.4. Navigate to the Planning Levels screen and select an entry from Data Source for External Key Figure Definition.


Key Figures

NoteMake sure that a value has been selected for Data Source for External Key Figure Definition. Otherwise, the planning level does not support external key figures on this base level.

5. Assign a reference column to each root attribute using the Reference Column.6. Click Save.7. Navigate to the Key Figures Screen.8. Select the Stored checkbox.9. Choose a reference column in the External Key Figure Quantity drop down which contains the time series data

for this key figure.10. Click Save.

10.7 Key Figure Calculations

Context

Once you have created a key figure, you can add calculations to it. Note the following:

● All key figures that an end user is able to query from the user interface must have a calculation at request level, because the system determines how to calculate the key figure starting from this calculation

● You can additionally define calculations that aggregate the key figure data from a lower base planning level using an operator such as SUM, MIN, or MAX.

● You can also define calculations across key figures, for example, KF1 plus KF2.● All key figure calculations have calculation inputs, which can be marked as stored or non-stored. The

calculation chain for every key figure must result in a stored key figure.

ExampleKF1@PL1 = KF2@PL1 plus KF3@PL1 , Key figure 2 (KF2) is a stored input key figure and key figure 3 (KF3) is a calculated input key figure. The calculated chain for key figure 3 (KF3) must finish with a stored key figure (such as KF3@PL1 = SUM(KF4@PL2), where KF4@PL2 is a stored key figure).

10.7.1 Adding Calculations to Key Figures

NoteYou can copy or delete key figures with L-Code, but for modification please contact SAP.

1. Choose Manage Key Figures on the initial screen of the Configuration app or click Key Figures in the top menu.2. Select the key figure to which you want to add a calculation.3. Click the Add Calculation button.


4. Select the planning level for the left side of the calculation. This can be request level (“@REQUEST”) or another planning level.

5. Place the cursor on the expression editor (to the right of the “=” sign) and type your calculation expression. When you enter the “”character (double quotes), a dropdown menu appears from which you can select the desired key figure. For example, enter the following: SUM(““SALESFORECASTQTY@PERPRODCUS””).

NoteFor calculation expressions, a maximum of 2 input planning levels is supported. If there are more than 2 input planning levels, you can use helper key figures to break down the calculation expressions.

6. Once you have entered the expression, click Validate Calculation and verify that the correct inputs have been selected by the system.The system automatically marks the Key Figures @ planning level that are used in the expression as inputs in the Input Key Figures dialog box.

7. Click OK.If your expression is correct, it will change color from black to green (planning level) and blue (key figure). This indicates that it is validated. Otherwise, you receive an error message.

8. Once your expressions are correct, save your changes.When you save your entries, the system creates a request level calculation by default.

ExampleThis example illustrates how to create a calculation for SALESFORECASTQTY. At request level, the calculation expression aggregates (SUMS) the stored SALESFORECASTQTY.

The system creates a request level calculation when a key figure is created. The following procedure shows how to add the above calculation for SALESFORECASTQTY:

1. Click the Add Calculation button.2. Select the planning level for the left side of the calculation. This can be REQUEST or another planning

level. Choose REQUEST.3. Place the cursor on the expression editor (to the right of the “=” sign) and type your calculation

expression. When you enter the “ character (double quotes), a dropdown menu appears from which you can select the desired key figure. For example, enter the following: SUM("SALESFORECASTQTY@PERPRODCUST").

4. Once you have entered the expression, click Validate Calculation and verify that the correct inputs have been selected by the system.The system automatically marks the Key Figures @ planning level that are used in the expression as inputs in the Input Key Figuresdialog box.

5. Define the Input key figures as shown in the table below.

Table 29:

Input Key Figure Stored

SALESFORECASTQTY@PERPRODCUST X

6. Click OK.If your expression is correct, it will change color from black to green (planning level) and blue (key figure). This indicates that it is validated. Otherwise, you receive an error message.


Key Figures

7. Once your expressions are correct, save your changes.

10.7.2 Stored Key Figure Calculation

Context

Stored key figures refer to key figures that are stored in the underlying database tables and that are either imported from a source system or else are entered manually in an Excel planning view.

Examples include SALESFORECASTQTY and ACTUALSQTY.

The following apply to stored key figure calculations:

● The associated key figure is marked as Stored (and can also be set to Editable)● The key figure has only one request level calculation, but can also have some other calculations.● The input key figure for the calculation is the same key figure at base planning level.

Example: Calculation Definition for Actuals Qty from SAP2 Sample Model

ACTUALSQTY@REQUEST = “SUM(ACTUALSQTY@PERPRODCUST)”

Note that the inputs for this calculation have ACTUALSQTY as a stored value:

Table 30:

Key Figure Select as Input Stored Value

ACTUALSQTY@PERPRODCUST √ √

10.7.3 Calculations at Request Level

Context

In request level calculations, the inputs for the calculation are also at request level. (“Request level”) is a built-in planning level that represents the level at which a user looks at the data [in the Microsoft Excel client or in Analytics].) When a key figure of this type is called at request level, the key figures in the calculation are first calculated at request level. The results are then returned to the key figure calculation. Request level calculations


are typically used for calculation of ratios, prices, and cost. The following example shows the calculation of sales forecast price, which is a weighted average calculation:

ExampleRequest Level Calculation: Sales Forecast Price: SALESFORECASTPRICE@REQUEST = IF(“SALESFORECASTQTY@REQUEST”=0,0,“SALESFORECASTREV@REQUEST”/“SALESFORECASTQTY@REQUEST”)

Note the following:

● Request level calculations must have aggregation mode Custom.● Aggregation methods such as SUM and MIN are not allowed for request level calculations. Only request level

inputs are allowed.● The inputs for request level calculations are not stored.

Input Key Figures: Request Level Calculation Sales Forecast Price

Table 31:

Key Figure Select as Input Stored Value

SALESFORECASTREV@REQUEST √

SALESFORECASTQTY@REQEST √

10.7.4 Calculations Across Different Planning Levels

In SAP Integrated Business Planning, you can easily perform calculations across different planning levels. In the SAP sample planning areas, calculations are done in real time. Based on changes to the sales forecast or to consensus demand, calculations are done for the complete supply side and for finance.

CautionWhen a key figure contains calculations at different planning levels, the attributes of the output planning level must match the union of all the attributes of the input planning levels.


Key Figures

ExampleThe following figure shows an example for the constrained demand plan revenue key figure from the SAP2 sample planning area:

Figure 8: Constrained Demand Plan Revenue

CONSTRAINEDDEMANDPLANREV@PERPRODLOCCUST is calculated from CONSTRAINEDDEMAND@PERPRODLOCCUST and NONDELIVERYCOSTRATE@PERPRODCUST.

For the calculation shown below, the same attributes must have been defined for the planning level PERPRODLOCCUST as for the planning levels PERPRODCUST and PERPRODLOCCUST combined.

Calculation of Constrained Demand Plan Revenue

CONSTRAINEDDEMANDPLANREV@REQUEST = SUM("CONSTRAINDDEMANDPLANREV@PERPRODLUCCUST")

CONSTRAINDDEMANDPLANREV@PERPRODLUCCUST = "CONSTRAINEDDEMAND@PERPRODLOCCUST" * "NONDELIVERYCOSTRATE@PERPRODCUST")

CONSTRAINEDDEMANDPLANREV@PERPRODCUST = SUM("CONSTRAINEDDEMANDPLANREV@PERPRODLOCCUST")


Input Key Figures for Calculation of Capacity Demand

● Calculation CONSTRAINEDDEMANDPLANREV@REQUEST = SUM("CONSTRAINDDEMANDPLANREV@PERPRODLUCCUST")

Table 32:

Key Figures Stored Value

CONSTRAINEDDEMANDPLANREV@REQUEST

● Calculation CONSTRAINDDEMANDPLANREV@PERPRODLUCCUST = "CONSTRAINEDDEMAND@PERPRODLOCCUST" * "NONDELIVERYCOSTRATE@PERPRODCUST")

Table 33:


NONDELIVERYCOSTRATE@PERPRODCUST Yes

CONSTRAINEDDEMAND@PERPRODLOCCUST Yes

● Calculation CONSTRAINEDDEMANDPLANREV@PERPRODCUST = SUM("CONSTRAINEDDEMANDPLANREV@PERPRODLOCCUST")

Table 34:


CONSTRAINEDDEMANDPLANREV@PERPRODLOCCUST

10.7.5 Commonly Used Functions and Expressions

Operators

The following operators are available:

+, -, *, /, >, <, =, >=, <=, !=, **, %, AND, OR, NOT

Table 35:

Operator Details Example

% Modulus operator. Returns the remainder, for example, 17%5 = 2.

KF1@PERPRODLOC % KF2@PERPRODLOC


Key Figures

Operator Details Example

** Power operator KF@PERPRODLOC = KF1@PERPRODLOC * ((1/KF2@PERPRODLOC)**0.5 )

AND Boolean operator that returns a value of TRUE if both its operands are true, and FALSE otherwise.

KF1@PERPRODLOC = 0 AND KF2@PERPRODLOC = 0

OR Boolean operator that returns a value of TRUE if any of its operands are TRUE, and FALSE otherwise.

KF1@PERPRODLOC = 0 OR KF2@PERPRODLOC = 0

Aggregation Methods

The following aggregation methods are available:

SUM, MIN, MAX, AVG

Table 36:

Syntax Details Example

IF(intarg , arg2, arg3) Return arg2 if intarg is considered true (not equal to zero), else return arg3.

CAPACITYOVERLOADS@PERLOCRES = IF(“CAPADEMANDUTILPCT@PERLOCRES”> 1,1,0)

ISNULL(arg1) Return 1 (= true), if arg1 is set to null. MARKETINGFORECASTQTY@PERPRODCUST = IF(ISNULL(MARKETINGFORECASTQTY@PERPRODCUST), SALESFORECASTQTY@PERPRODCUST, MARKETINGFORECASTQTY@PERPRODCUST)

CASE(arg1, default)

CASE(arg1, cmp1, value1, cmp2, value2, ..., default)

Return value1 if arg1 == cmp1, value2 if arg1 == cmp2, and so on, default if there is no match.

CASE(SELECTEDOPTION@PERPROD, 1, KF1@PERPROD, 2, KF2@PERRPROD,KF@PERPROD)


Syntax Details Example

ABS(arg) Returns arg, if arg is positive or zero, else –arg.

IF(ABS(SUPPLYREV@PERPRODFML - CONSENSUSDEMANDREV@PERPRODFML)/CONSENSUSDEMANDREV@PERPRODFML > 0.2,1,0)

ROUND(double, int) ROUND(123.456, 0) = 123

ROUND(123.456, 1) = 123.5

ROUND(-123.456, 1) = -123.5

ROUND(123.456, -1) = 120

KF1@PERPRODLOCSRC = ROUND(KF@ PERPRODLOCSRC, 0)

ROUNDDOWN(double, int) ROUNDDOWN(123.456, -1) = 120

ROUNDDOWN(-123.456, -1) = -130

KF1@PERPRODLOCSRC = ROUNDDOWN(KF@ PERPRODLOCSRC, 0)

FLOOR(double) FLOOR(35.1) = 35 KF1@PERPRODLOC = FLOOR(KF@ PERPRODLOC)

CEIL(double) CEIL(35.1) = 36 KF1@PERPRODLOC = CEIL(KF@ PERPRODLOC)

LTRIM(string)

LTRIM(string,string)

Remove a whitespace prefix from a string. The whitespace characters may be specified in an optional argument.

RTIM(string)

RTIM(string,string)

Remove trailing whitespace from a string. The whitespace characters may be specified in an optional argument.

TRIM(string)

TRIM(string,string)

Remove whitespace from the beginning and end of a string.

The following example shows a sample configuration for aggregation of standard deviation:

ExampleTake the sum of the squares; then calculate the square root of the total:

1. Calculate the squares:1. Square the values:

HKF1@PL = PROPAGATEDDEMANDSTDEV@PL ** 22. Sum the squares:

HKF1@REQUEST = SUM(HKF1@PL)


Key Figures

2. Calculate the square root of the total:PROPAGATEDDEMANDSTDEV@REQUEST= HKF1@REQUEST ** 0.5

ExampleISNULL

The ISNULL condition works only when an underlying time series record exists for the planning object.

Imagine that Sales Forecasting and Marketing Forecast Quantity are the stored key figures for planning level PERPROD.

Table 37:

Planning Object Period Key Figure: Sales Forecast Qty

Key Figure: Marketing Forecast Qty

P1 Jan 2015 100

P1 Mar 2015 100

With the above data, IF(ISNULL(SALESFCSTQTY),1,0) exhibits the following behavior:

Table 38:

Period ISNULL Value Notes

Jan 2015 1 January 2015 has the value “100”.

Feb 2015 Not evaluated The planning object for the time period February 2015 does not exist.

Mar 2015 0 Though there is no value for Sales Forecast Qty, the Marketing Qty key figure (for the same planning level) has a valid value. Therefore, a record exists in the time series for this planning object.

Sample Expressions

Table 39:

Key Figure Calculation Expression

Actuals Price ACTUALSPRICE@REQUEST = IF(“ACTUALSQTY@REQUEST”=0,0, “ACTUALSREV@REQUEST”/“ACTUALSQTY@REQUEST”)


Key Figure Calculation Expression

Capacity Overloads CAPACITYOVERLOADS@PERLOCRES = IF(“CAPADEMANDUTILPCT@PERLOCRES”> 1,1,0)

Capacity Usage CAPAUSAGE@PERPRODLOCRES = “CAPADEMAND@PERPRODLOCRES”*“(IF(CAPASUPPLYPERDEMAND@PERLOCRES”>1,1, “CAPASUPPLYPERDEMAND@PERLOCRES”))

Marketing Forecast Profit MARKETINGFORECASTPROFIT@PERPRODCUST = “MARKETINGFORECASTREV@PERPRODCUST”- “HMARKETINGFORECASTCOST@PERPRODCUST”

Marketing Forecast Quantity MARKETINGFORECASTQTY@PERPRODCUST = IF(ISNULL("MARKETINGFORECASTQTY@PERPRODCUST"), "SALESFORECASTQTY@PERPRODCUST", "MARKETINGFORECASTQTY@PERPRODCUST")

Constrained Versus Consensus Demand Revenue CONSTRAINEDVSCONSENSUSREV@PERPRODFML = IF(ISNULL("CONSENSUSDEMANDREV@PERPRODFML")OR "CONSENSUSDEMANDREV@PERPRODFML"=0,0, IF(ABS("SUPPLYREV@PERPRODFML" - "CONSENSUSDEMANDREV@PERPRODFML")/"CONSENSUSDEMANDREV@PERPRODFML" > 0,2,1,0))

Supply Quantity SUPPLYQTY@PERPRODLOC = IF("HPROJECTEDINVENTORYQTY@PERPRODLOC">=0, "DEPENDENTDEMANDQTY@PERPRODLOC", "DEPENDENTDEMANDQTY@PERPRODLOC"+ "HPROJECTEDINVENTORYQTY@PERPRODLOC")

Bill Cost per Area BILL_COST_PER_AREA@BSCIRTRSCFRCTOUFRUTO2L3AVG_A = IF(isnull("ASSETAREA5@BSCIRTRSCFRCTOUFRUTO2L3AVG_A") or "ASSETAREA5@BSCIRTRSCFRCTOUFRUTO2L3AVG_A"=0,0,"BILL_COST5@BSCIRTRSCFRCTOUFRUTO2L3AVG_A"/"ASSETAREA5@BSCIRT


Key Figures

10.7.6 Defaulting to Another Key Figure

Context

You can configure key figures in such a way that a key figure calculation defaults to another key figure value based on a condition. You can also define a chain of key figures, where a key figure defaults to another defaulting key figure.

NoteChaining is not restricted to defaulting. As all definitions of key figure are iterative, you can define a chain for any calculations.

ExampleIn this example, the key figure Sales Forecast Qty is defined as defaulting key figure for the key figure Consensus Demand Qty. If the data value for Consensus Demand Qty is null or empty, the system defaults to Sales Forecast Qty.

As there is no stored value for Consensus Demand Qty, the value defaults to the value for Sales Forecast Qty: 2000.


Figure 9: Example

Note the following:

● If there is no stored data value for Consensus Demand Qty, then the value “2000” from Sales Forecast Qty is used.

● If you enter a value, such as “1000” for Consensus Demand Qty or save a value from planning views, this new value will override the default value.

● To revert to a calculated value, simply set the value to null (empty) in the planning view and save your entries.

Steps

1. Create a key figure, for example, CONSENSUSDEMANDQTY at base planning level PERPRODCUST2. Mark the key figure as Stored, Editable, and Calculated.3. Define a request level calculation and a calculation for the base planning level:

○ Request level calculation:CONSENSUSDEMANDQTY@REQUEST = SUM(“CONSENSUSDEMANDQTY@PERPRODCUST”)

○ Calculation for the base planning level:CONSENSUSDEMANDQTY@PERPRODCUST = IF(ISNULL(“CONSENSUSDEMANDQTY@PERPRODCUST”“DEMANDPLANNINGQTY@PERPRODCUST”, “CONSENSUSDEMANDQTY@PERPRODCUST”)


Key Figures

NoteNote that the input key figure can be either a stored or a calculated key figure. In this example, both inputs are stored key figures:

Table 40:

Key Figure Selected as Input Stored Value

CONSENSUSDEMAND@PERPRODCUST √ √

DEMANDPLANNINGQTY@PERPRODCUST √ √

NoteSince the key figure is marked as both stored and calculated, on activation, the system generates a defaulting expression as follows:

IF(ISNULL(“CONSENSUSDEMANDQTY@PERPRODCUST”), “DEMANDPLANNINGQTY@PERPRODCUST”, “CONSENSUSDEMANDQTY@PERPRODCUST”)

The system generates this expression provided the inputs for the calculation are stored key figures that are at the same base planning level as the Key figure itself.

10.7.7 Using Attributes in Key Figure Calculations

You can use attributes in both conditional expressions and in calculation expressions.

ExampleExamples of using attributes in expressions:

● KEYFIGURE1 = IF(ATTRIBUTE = “VALUE”, KEYFIGURE * 2, KEYFIGURE, * 3)● KEYFIGURE1 = KEYFIGURE2 + ATTRIBUTE● ATTRIBUTE = ATTRIBUTE + 2● ATTRIBUTE = “VALUE”

Note the following:

● An attribute that is used in a calculation must belong to the planning level of at least one of the inputs to the calculation.

● An attribute cannot be used in a calculation if all the inputs are specified at request planning level.● If you use a constant in an expression, you must use two (!) single quotation marks before the attribute value

and two (!) single quotation marks after the attribute value (for example, ''constant'').

NoteThis is a single quotation mark: '


CautionPlease note that a dobule quotation mark (") won't work, event though it looks similar to a combination of two single quotation marks.

10.7.8 Using Time Periods in Key Figure Calculations

You may sometimes need to define calculations that are based on criteria relating to time periods.

For example, imagine that for key figure Sales Forecast Qty, you want to show the Actuals Qty for time periods that lie in the past:

Actuals Qty Shown for Sales Forecast Qty in Past Time Periods

Table 41:

Key Figure Current Time Period -2

Current Time Period -1

Current Time Period

Current Time Period +1

Current Time Period +2

Prod1/Cust1 Actuals Qty 100 120

Sales Forecast Qty

100 120 150 175 100

To achieve this, define the following calculation expression:

SALESFCSTQTY@BASEPLANNINGLEVEL = IF(PERIODIDn >=$$PERIODIDCUn$$, SALESFCSTQTY@BASEPLANNINGLEVEL,ACTUALSQTY@BASEPLANNINGLEVEL)

NoteIf you have key figures at different planning levels (Week, Month, Quarter, Year), you might want to use PERIODIDn.:

● $$PERIODIDCUn$$: Fixed variable for the current period.● PERIODIDn: Time period attribute

"n" refers to the time period level. For example, in a planning area where the time profile has the levels "Week", "Month", "Quarter", and "Year", the period IDs would be as follows:

Table 42:

Period ID Time Period Level

PERIODID0 Week

PERIODID1 Year


Key Figures

Period ID Time Period Level

PERIODID2 Quarter

PERIODID3 Month

If Sales Forecast Qty is defined at the base planning level with Month as the root, then PERIODIDn would be replaced by PERIODID3.

10.8 Decimal Places in Key Figure Values

In the Configuration app, you can define the number of decimal places you want to be displayed for each key figure. If the number of decimal places is not specified, the maximum possible value is used, which is 6 decimal places.

This setting affects disaggregation only for key figures that have aggregation mode SUM or AVG. The information provided here refers only to such key figures.

When a user enters a key figure value in a planning view, or executes a batch process which involves disaggregation, the system manages the values as follows:

● The disaggregated key figure values at the base planning level are always rounded to the configured number of decimal places.

● The aggregation of the base planning level values is a key figure value that is also always rounded to the configured number of decimals (when not taking conversion into account).

● The aggregation of the base planning level values is the same as the number entered by the user (provided the number entered does not exceed the number configured).

ExampleYou entered 2 decimal places for a key figure Demand.

Product group PG has 3 products: A, B, and C.

You enter a value of 10 for Demand at the aggregated planning level PG.

Result: After disaggregation, the key figure values at the base planning level are 3.33, 3.33, and 3.34 for the 3 products A, B, and C. The system arbitrarily decides which product gets 3.34.

You enter 12.456 for Demand at the aggregated planning level PG.

Result: After disaggregation, the key figure values at the base planning level are 4.15, 4.15, and 4.16 for the 3 products A, B, and C. This aggregates to 12.46 according to the configuration setting of 2 decimal places for the key figure.

ExampleYou entered 4 decimal places for a key figure Supply.

Product group PG has 3 products: A, B, and C.


You enter a value of 12.456 for Supply at the aggregated planning level PG.

Result: After disaggregation, the key figure values at the base planning level are 4.152, 4.152, and 4.152 for the 3 products A, B, and C.

NoteIn some circumstances, taking the number of decimal places into account during disaggregation can affect performance. So if you do not need this feature for a particular key figure, you can deactivate it by setting the number of decimal places for the key figure to null in the Configuration app.


Key Figures

11 Versions

Versions (before Release 4.0 FP 01 referred to as “scenarios”) are used to manage alternate plans. They can be defined using all or subsets of the key figures of the planning area, including calculated key figures. Versions can contain references to the base version key figures, so that these can be used in calculations within the version.

Versions can have version-specific master data. The versions that do not have version-specific master data share the master date with the base version.

You can copy key figures and/or master data (where applicable) between versions.

Besides versions, you can also create “scenarios”.

The following table gives an overview of the difference between “versions and scenarios”:

Table 43:

Object Type Version Scenario

Purpose Alternate plans maintained over time. On-the-fly “what if” scenarios

Created By Administration user at time of configuration. (The number of versions is defined during configuration.)

Planner or end user (dynamically when using the system)

Created From Configuration app, by choosing Versions, and then Create New.

Microsoft Excel add-in by choosing Create in the Scenarios group.

Change Method Copy

Customers copy data between versions. As a result, a version is based on a copy (or an overlay of multiple copies) and not on a collection of deltas. Changes to the base version (or to another version that you copied from) do not automatically “shine through” in the target version of the copy.

Delta

The system keeps track of all changes to key-figure values as delta records inside the scenario. If, at the same time, changes are made in the base version, these are visible in the scenarios, unless there are conflicting scenario deltas, in which case those take precedence. This change method could be thought of as “shine-through” logic.

For more information about scenarios, see http://help.sap.com/ibp. Choose Application Help English SAP Integrated Business Planning Planning with Microsoft Excel Information for End Users Working with Planning Views Simulating the Effect of Data Changes Creating Scenarios .

Model Configuration GuideVersions C U S T O M E R 87


11.1 Creating Versions

Context

To create a version, choose Manage Versions on the initial screen of the Configuration app or click Versions in the top menu.

The following example illustrates how to create an upside version:

Example

Steps

1. Verify that your planning area is selected.2. Click New and enter an ID for the new version (for example, UPSIDE).3. Enter a name and description:

○ Name: Upside○ Description: Upside version

4. Select the Version-Specific Key Figures (in the case of the basic S&OP Model, you can select all).5. Save the version.


Versions

12 Planning Operators

A planning operator uses an algorithm to compute large amounts of key figure data within a planning session. You can schedule a planning operator to be processed in the background.

SAP delivers the following planning operator types:

Table 44:

Planning Operator Type Name Use

ABC ABC Classification Categorize the set of attributes into the categories A, B, or C.

ADVSIM Advanced Simulation Preprocessing and postprocessing operations for simulation

COPY Copy Key Figure Data Copy values of source key figures to target key figures in the same version (base or other) of a planning area.

DELABNDNCOMBOS Delete Abandoned Combinations Delete obsolete planning combinations and the associated transaction data for which no master data values exist.

For example, let's assume that PRDFAMILY is a root attribute of base planning level PERPRDFMLYCUST and that planning combinations exist for the product families “X Phone” and “Y Phone”. If “X Phone” is completely replaced by “Y Phone”, then this planning operator deletes the obsolete “X Phone” combinations.

DISAGG Copy and Disaggregate Key Figure Data

Copy and disaggregate values of source key figures to target key figures in the same version (base or other) of a planning area.

IBPFORECAST Statistical Forecasting Run statistical forecasting for a selection of your data.

GROUP Group Run a group of planning operators in a single batch job in a defined sequence.

A group operator can be run automatically after importing key figure values and manually from the Excel add-in (batch mode only).

Model Configuration GuidePlanning Operators C U S T O M E R 89

Planning Operator Type Name Use

IO Inventory Optimization Run inventory optimization for a given supply chain network.

PCH Purge Change History Delete all change history data that is older than a specified number of days.

PURGE Purge Key Figure Data Delete all key figure data that is older than a specified time period.

SCM S&OP Run global supply planning across your supply chain network. This planning operator type offers different algorithms (for example, heuristic and optimizer).

SNAPSHOT Snapshot Take a snapshot of a predefined set of key figures in a batch process.

SNAPSHOTREDO Redo Snapshot Overwrite the most recent snapshot with a new snapshot of a predefined set of key figures in a batch process.

KPI_PROFILE Forecast Error Set up forecast error calculations for a selection of your data.

SEGMENTATION Segmentation Schedule and start ABC/XYZ segmentation jobs.

12.1 Creating a Planning Operator

Procedure

1. On the initial screen of the Configuration app select Manage Planning Operators.2. Select a planning operator type from the list of planning operator types on the left side of the screen.3. Select + (Add Planning Operators).

You can specify the following pieces of information for your planning operator:○ Planning operator name and description○ Required modes (one or more): interactive, batch, or filter mode○ Planning operator parameters

For more information, see the following table:


Planning Operators

Table 45:

Field Description

Interactive Mode Specifies whether the user can run the planning operator interactively in the current planning session in IBP Excel add-in (by choosing Simulate and then the operator name).

Batch Mode Specifies whether the user can schedule the planning operator to run in the background (either immediately or as a scheduled job).

Filter Mode Specifies whether the user can use filters when running or scheduling the planning operator in IBP Excel add-in.

For example, if you activate the filter mode for the planning operator type SNAPSHOT, the user can use a stored filter or create an ad-hoc filter when taking the snapshot from IBP Excel add-in. Only the data that satisfies the filter is included in the snapshot.

Define Parameters Parameters that are relevant for the planning operator (parameter name and parameter value).


Next Steps

Once you created and defined your planning operators, assign them to a planning area. For more information see Assigning a Planning Operator to a Planning Area [page 91].

12.2 Assigning a Planning Operator to a Planning Area

Prerequisites

Make sure you have already created planning operators for the planning operator types available in the system. For more information see Creating a Planning Operator [page 90].

Procedure

1. On the initial screen of the Configuration app select Define Planning Area or choose Planning Area and Details in the top menu.


2. Select your planning area from the list of planning areas on the left side of the screen.3. Choose Planning Operators.

The Assign Planning Operators dialog appears.4. Select the planning operators you want to assign to your planning area and choose OK.

You can assign planning operators one by one, or you can assign all planning operators associated with a certain planning operator type by selecting the planning operator type.

5. Save your changes.6. Activate your planning area.

12.3 Advanced Simulation (ADVSIM) Operator

The Advanced Simulation (ADVSIM) operator copies key figure values from source key figures to target key figures during simulation. The ADVSIM operator supports disaggregation based on calculated key figures.

RecommendationThe ADVSIM operator is a workaround for disaggregation with reference to a calculated key figure whose values changed during a previous simulation. SAP recommends that you use this operator only when absolutely necessary because it may affect performance during simulation or during saving and because it requires a stored key figure. If the value of the referenced calculated key figure does not change frequently, it is advisable to copy the calculated key figure to a stored key figure using a regularly scheduled copy operator job and to use the stored key figure as a reference.

The following are sample use cases for the ADVSIM operator:

● Disaggregate the sales forecast quantity based on the last 12 months of sales history.● Perform a complex calculation based on key figures at different planning levels before disaggregation.

The operator supports the following operations:

● Pre-Copy: Copies configured source key figure values to target key figure values before disaggregation● Post-Copy: Copies configured source key figures to target key figures after disaggregation● Disaggregation Key Figures: Whenever a change is made to a key figure defined as a disaggregation key figure,

the advanced simulation operator is triggered.

When a key figure is configured in an ADVSIM operator as a disaggregation key figure and its value is subsequently changed or simulated in a planning view, the ADVSIM operator is triggered and does the following for the changed cells only:

1. Pre-copy2. Regular disaggregation of the key figure3. Post-copy

Before calculated key figures can be used for disaggregation, the value of the calculated key figure must be stored in another stored key figure at the same base planning level as the key figure that is being disaggregated. This is done in the Pre-copy or the Post-copy operations of the ADVSIM operator.


Planning Operators

The following table lists the configuration settings for the ADVSIM operator:

Table 46:

Parameter Explanation Mandatory/Optional

PRE_SOURCE_KFIDnm Source key figure ID. “n” is a number starting from “1”.

Optional

PRE_TARGET_KFIDnm Target key figure ID. “n” is a number starting from “1”

Optional

POST_SOURCE_KFIDn Source key figure ID.“n” is a number starting from “1”

Optional

POST_TARGET_KFIDnm Target key figure ID. “n” is a number starting from “1”.

Optional

DISAGG_KFIDnm Key figures that invoke that ADVSIM operator when their values change.

Mandatory

NoteNote the following with respect to the parameter IDs:

● "n" represents the sequence or order of a key figure for disaggregation. For example, if a user updates 2 or more key figures as part of a simulation and a calculation dependency exists between the key figures, "n" indicates the order in which the key figures are to be disaggregated. As this disaggregation sequence is not yet supported, "n" must always have the value "1".

● "m" represents the key figure pair for source and target key figures. You configure it as follows:PRE_SOURCE_KFID11 = KF1, PRE_TARGET_KFID11 = KF2;PRE_SOURCE_KFID12 = KF3, PRE_SOURCE_KFID12 = KF4KF1 is then copied to KF2, and KF3 is copied to KF4 as part of pre-copy, allowing copying of multiple key figures in a single operator call.

Other important conditions for the ADVSIM operator are as follows:

● If a source key figure ID is set to NULL, then the corresponding target key figure ID will be filled with null values, for example:PRE_SOURCE_KFID11 = NULL, PRE_TARGET_KFID11 = KF5

● Like any other simulation, the ADVSIM operator uses the filters from the planning view and applicable for changed cell values of the DISAGG_KFID key figure.

● The DISAGG_KFID key figure must have the same base planning level and must be a stored key figure.● The source key figure for the copy operation can be either stored or calculated. The source key figures are

queried and then copied at the base planning level of the target key figures. The attributes available at request level for the source key figure must be a superset of the base planning level of the target key figure.

● The target key figure for Pre-copy and Post-copy must be a stored key figure and must have the same base planning level as the DISAGG_KFID key figure.

For more information, see the SAP Help Portal at http://help.sap.com/ibp, under Application Help for SAP Integrated Business Planning User Interface Planning with Microsoft Excel .


http://help.sap.com/ibp1608

12.3.1 Example: Setting Up the ADVSIM Operator

The ADVSIM planning operator type is delivered as part of the standard SAP content for planning operators. In this example, an ADVSIM operator is created to copy the calculated value of ACTUALSQTY offset by 12 months (ACTUALQTYOFFSET) to a stored key figure ACTUALSQTYOFFSETSTORED.

1. Choose Manage Planning Operators on the initial screen of the Configuration app.2. To create a new operator for ADVSIM, click "+".3. Enter Name enter COPYACTUALOFFSET and the description enter Copy Actuals Offset.4. Choose Define Parameters.5. Add the parameters for the COPYACTUALOFFSET operator as follows:

Table 47:

Parameter Name Parameter Value

DISAGG_KFID11 SALEFCSTQTY

PRE_SOURCE_KFID11 ACTUALQTY12OFFSET

PRE_TARGET_KFID11 ACTUALSQTYOFFSETSTORED

6. Assign the operator to your planning area.

Result

When SALESFCSTQTY is simulated or saved, the following takes place:

1. ACTUALQTY12OFFSET is calculated and copied to ACTUALSQTYOFFSETSTORED.2. The disaggregation is performed on SALESFCSTQTY based on ACTUALSQTYOFFSETSTORED.


Planning Operators

Note that SALESFCSTQTY is configured as follows with ACTUALSQTYOFFSETSTORED in the disaggregation expression:

Figure 10: SALESFCSTQTY

12.4 Copy (COPY) Operator

The copy (COPY) operator copies calculated values of one key figure to another key figure in the same version (base or other) of a planning area. In addition, the copy operator can create the missing time periods for the target key figure and assign these periods an empty value.

The copy operator calculates values of the source key figure at the base planning level of the target key figure for all possible combinations, and updates the target key figure values. Values are calculated based on the calculation configuration.

ExampleKF1 is a stored key figure with base planning level PRODLOCCUST, and KF2 is a stored key figure at PRODLOC base planning level.

If you define a COPY operator to copy KF1 to KF2, the operator calculates values of KF1 for all possible combinations of Prod-Loc and stores the result in KF2.


Note● The source key figure can be calculated or stored, but the target key figure must be stored.● Copy works only if the source key figure can be calculated at the base planning level of the target key

figure.● If copy is used for version key figures, both source and target key figures must be added to the version.● The copy operator does not work if the source key figure has unit of measure conversion configured.

You can configure this operator in a similar way to other batch operators (for example, Forecasting) and can make it available in the IBP Excel add-in by adding it to the roles.

CautionIn some cases, a user may have a role that grants unlimited read access but restricted write access. The restriction may be based on a visibility filter or may be set for specific key figures. If this user runs the copy operator, it will copy values of the key figure for all possible attribute combinations from the source to the target without considering the user's authorizations.

To prevent this, define the restrictions at read level of the source key figure.

For more information, see SAP Note 2445262 .

Parameters

Table 48:


SOURCE_KFIDn Source key figure ID. n is a number starting from 1

Mandatory for copy

Optional if you only want to create the missing time periods for the target key figure For more information, see the CREATE_TIMEPERIODS parameter below.

TARGET_KFIDn Target key figure ID. n is a number starting from 1.

NoteDefine source and target key figures in pairs. For example, SOURCE_KFID1 is copied to TARGET_KFID1, SOURCE_KFID2 is copied to TARGET_KFID2, and so on. This allows execution of multiple key figure copies in a single operator call.

Mandatory


Planning Operators



PERIOD_OFFSET Offset relative to the current period. If this parameter isn’t specified, it defaults to 0 in which case only values in future buckets are copied. If you want to copy values in the past, specify a negative offset.

To apply the offset following steps are followed:

1. Determine the current bucket at the most granular level of the time profile.

2. Determine the current bucket at the granularity specified in the base planning level of the target key figure.

3. Apply the offset to the current bucket determined in step 2.

ExampleIf the time profile has week, month, quarter, and year, and the base planning level of the target key figure is month:

1. Determine the current week.2. Determine the month that con

tains the current week.3. Add the offset to the current

month to determine the beginning of the month to which the data will be copied.

Optional



DURATION Number of periods to be copied starting from the offset defined in PERIOD_OFFSET. Can be used with PERIOD_OFFSET to restrict the copy to specific range of time buckets.

If not specified or specified as 0, it is considered to be until the end of the horizon.

ExampleIf you want to copy values from the past and future , for example 12 months in the past and 12 months in the future, then you define the following: PERIOD_OFFSET: -12 and DURATION: 25.

Optional (Mandatory if PERIOD_OFFSET is specified.)

<Attribute>_VALUEn Configured filter

Note the following:

● <Attribute> is the name of an attribute.

● n is a number starting from 1 for each attribute, which enumerates the allowed values.

● You can specify multiple values for a single attribute.

● You can specify multiple attributes.● This configured filter is applied for

every COPY operation. It cannot be overridden from the IBP Excel add-in, but users can specify a user filter when scheduling the operator to restrict it further. The system considers the intersection of configured filter and user-specified filter.

Optional


Planning Operators


CREATE_TIMEPERIODS Creates the missing periods for the target key figure and assigns these periods an empty value. The parameters listed above are taken into account.

If you activate this parameter (by setting the parameter value to X), the copy operator does the following:

● If you have specified a source key figure, the copy operator copies the source key figure to the target key figure and creates the missing periods.

● If you have not specified a source key figure, the copy operator only fills in the missing time periods for the target key figure.

Optional

PERIOD_SHIFT Number of periods by which the source key figure values are shifted.

Optional

12.4.1 Example: Setting Up the Copy Operator

Context

To set up the Copy operator, choose Manage Planning Operators on the initial screen of the Configuration app.

NoteTo configure planning operators, the Planning Model business catalog must be assigned to a business role assigned to your user.

The following example illustrates how to set up the Copy operator.

Steps

1. Choose COPY from the list of planning operator types on the left side of the screen.2. Select + (Add Planning Operators).


Make the following entries:

Table 49:

Field Entry

Name COPY_STORED

Description Copy from Stored KFs to Stored KFs

Interactive Mode No

Batch Mode Yes

Filter Mode Select or deselect according to whether you want the user to use filters when running or scheduling the operator in IBP Excel add-in.

Define parameters as follows:

Table 50:

Parameter Name Parameter Value Stored/Calculated Base Planning Level

DURATION 5

PERIOD_OFFSET 0

SOURCE_KFID1 FINANCEPLANPROFIT Stored PERPRODFMLCUSTREG

SOURCE_KFID2 FINANCEPLANQTY Stored PERPRODFMLCUSTREG

TARGET_KFID1 FINANCEPLANREV Stored PERPRODFMLCUSTREG

TARGET_KFID2 CMPAVAILABLEQTY Stored PERPRODLOC

SM1PRDID_VALUE1 x101 Phone

SM1PRDID_VALUE2 x101 Media Player

3. Add a second planning operator.Make the following entries:

Table 51:

Field Name

Name COPY_CALCULATED

Description Copy from Calculated KFs to Stored KFs

Interactive Mode No

Batch Mode Yes


Planning Operators

Field Name

Filter Mode Yes

Define parameters as follows:

Table 52:


DURATION 100

PERIOD_OFFSET 0

SOURCE_KFID1 FINANCEPLANPRICE Calculated PERPRODFMLCUSTREG

SOURCE_KFID2 INVENTORYTARGETCOST Calculated PERPRODFMLCUSTREG

TARGET_KFID1 FINANCEPLANREV Stored PERPRODFMLCUSTREG

TARGET_KFID2 FINANCEPLANPROFIT Stored PERPRODLOC

4. Save your entries.5. Assign the planning operator to the relevant planning area. For more information see Assigning a Planning

Operator to a Planning Area [page 91].

12.5 Delete Abandoned Combinations (DELABNDNCOMBOS) Operator

The Delete Abandoned Combinations (DELABNDNCOMBOS) planning operator allows you to delete obsolete (non-conforming) data from a planning area. This data may arise over time as the result of continuous use. It is not used in any planning functions but its presence may cause interference or a deterioration in performance.

RecommendationRun this operator whenever you make key changes to master data or planning levels that are used for stored key figures in your planning area. You can also run it if your planning view doesn’t show any key figure values or shows incorrect key figure values, or if you receive a “refresh” error in the planning view due to an invalid member.

You can run this operator from the IBP Excel add-in. It runs for the planning area to which you are logged on.

The operator runs in batch mode only. It does not accept any filter.

For more information, see SAP Note 2305209 .



12.6 Snapshot (SNAPSHOT) Operator

The snapshot (SNAPSHOT) planning operator type allows you to define snapshots on the Manage Snapshot Configurations screen of the Configuration app. Once you have defined a snapshot, the system automatically creates a planning operator for it.

Planning operators of this type cannot be edited and cannot be added to a group operator.

For more information, see the Snapshots section of the current guide.

12.7 Redo Snapshot (SNAPSHOTREDO) Operator

The redo snapshot (SNAPSHOTREDO) planning operator type allows you to retake a snapshot in the IBP Add-In for Microsoft Excel in case there are errors in the data. The operator overwrites the most recent snapshot with a new snapshot for the same set of key figures in a batch process.

Planning operators of this type are not editable and cannot be added to a group operator.

For more information, see the Snapshots section of the current guide.

12.8 Statistical Forecasting (IBPFORECAST) Operator

The statistical forecasting (IBPFORECAST) operator allows you perform statistical forecasting by making the following features available in Excel:

● Run and schedule statistical forecasting● Simulate statistical forecasting

The following settings are defined by the system for the IBPFORECAST operator:

● Interactive mode: Yes● Batch mode: Yes● Filter mode: Yes

Note that the IBPFORECAST operator type does not have planning operators that can be added to a group operator, since it uses the concept of forecast models for configuring forecasting. Background forecasting is done by defining a job and specifying the forecast model, the aggregation level, and a filter to be used.

For the same reason, you cannot specify any parameters for a forecasting operator.


Planning Operators

12.8.1 Running the IBPFORECAST and DISAGG Operators in Batch Mode with UOM Conversion

When you want to execute the IBPFORECAST or DISAGG planning operator in batch mode (mass disaggregation) with a key figure A that contains a unit of measure (UoM) conversion, you must make sure that all root attributes of the conversion key figure B are contained as root attributes in the base planning level of key figure A, with the exception of the (UoM) conversion target attribute.

Table 53: Example

Root Attributes of Key Figure A Root Attributes of Key Figure B Supported

PRDID, LOCID, Technical Week UOMTOID, PRDID, Technical Week Yes

UOMTOID, PRDID Yes

UOMTOID, PRDID, Day No

UOMTOID, PRDID, Calendar Week No

UOMTOID, PRDID, CUSTID No

12.9 Disaggregation (DISAGG) Operator

The disaggregation (DISAGG) operator copies and disaggregates calculated values of one key figure to another key figure in the same version (base or other) of a planning area. In addition, the disaggregation operator can create the missing time periods for the target key figure, and assign these periods an empty value. However, the disaggregation operator does not create new planning objects.

The disaggregation operator can read values of the source key figure at a higher level than the base planning level of the target key figure (at the aggregation level). The operator then copies the values from the source key figure to the target key figure, disaggregating the values to the base planning level of the target key figure.

ExampleKF1 is a stored key figure with base planning level product-customer, and KF2 is a stored key figure with base planning level product-location.

If you define a DISAGG operator to copy and disaggregate the values from KF1 to KF2 at the aggregation level of PRDID, then the DISAGG operator reads the key figures values of KF1 at the aggregation level of product, then disaggregates and writes the values to KF2 at product-location level.

Note● The source key figure can be calculated or stored, but the target key figure must be stored.● Disaggregation works even if the source key figure cannot be calculated at the base planning level of the

target key figure.


● If the disaggregation operator is used for version key figures, both source and target key figures must be added to the version.

You can configure this operator in a similar way to other batch operators (for example, Forecasting) and can make it available in the IBP add-in for Microsoft Excel by adding it to the roles. The disaggregation operator works in batch mode only.

NoteThe DISAGG operator cannot be used in a GROUP operator.

Parameters

When you define a new planning operator of the DISAGG planning operator type, specify values for the following parameters:

Table 54:


ATTRIBUTEn The aggregation level is the level at which the source key figure is read and copied to the target key figure (before disaggregation takes place).

ExampleYou want to read the source key figure data at product-customer level. Specify the root attributes of the respective master data types, such as PRDID and CUSTID , as ATTRIBUTE1, and ATTRIBUTE2.

Mandatory to specify at least one attribute for the aggregation level.

DURATION The number of periods to be copied and disaggregated starting from the offset defined in PERIOD_OFFSET. Can be used with PERIOD_OFFSET to restrict the copy and disaggregation to a specific range of time buckets.

If you have not specified DURATION and PERIOD_OFFSET, the operator processes the key figure values in the whole planning horizon.

Optional

Mandatory if PERIOD_OFFSET is specified


Planning Operators


FILTER_ATTRIBUTEn The attribute for the configured filter.

You can define multiple filter attributes.

Optional

FILTER_VALUEn The value for the corresponding filter attribute that you have specified.

NoteThis configured filter is applied for every DISAGG operation. It cannot be overridden with a filter defined in the IBP add-in for Microsoft Excel, but users can specify a user filter when scheduling the operator to restrict it further. The system takes this combination of configured and user-specified filters into account.

Optional

PERIODID Technical ID of the time level (for example, PERIODID1).

NoteThe PERIODID does not correspond to the number of the time level.

Either PERIODID or PERIODNAME is mandatory. Specify only one of them.

PERIODNAME The name of the time level at which you want to read and disaggregate the data as defined in the time profile of your planning area (for example, Monthly).

Either PERIODID or PERIODNAME is mandatory. Specify only one of them.



PERIODSHIFT The period shift is the source key figure value from period n copied and disaggregated to target key figure value in period n plus the value defined for the PERIODSHIFT parameter.

ExampleYou specify Yearly for PERIODNAME. In this case, the value 1 for the PERIODSHIFT parameter means that the values of the source key figure are copied and disaggregated to the next year period of the target key figure.

Optional

PERIOD_OFFSET Offset relative to the current period.

If you have specified a value for DURATION, the default value for PERIOD_OFFSET is 0.

Optional.

SEQUENTIAL If you have multiple pairs of source and target key figures, you can specify that the system processes them sequentially. With sequential processing, the system includes the result of a key figure copy and disaggregation in the subsequent copy and disaggregation.

For an example about the use of this parameter, see Example: Setting Up the Disaggregation Operator [page 107].

Optional

SOURCE_KFIDn Source key figure ID. n is a number starting from 1.

Mandatory to define at least one source key figure.


Planning Operators


TARGET_KFIDn Target key figure ID. n is a number starting from 1.

NoteDefine source and target key figures in pairs. For example, SOURCE_KFID1 is copied to TARGET_KFID1, SOURCE_KFID2 is copied to TARGET_KFID2, and so on. This enables the execution of multiple key figure copies and disaggregations in a single operator call.

Mandatory to define at least one target key figure.

Do not select Interactive Mode, but select Batch Mode. Select Filter Mode if you want to use filters when you schedule a job for this planning operator in the IBP add-in for Microsoft Excel.

Handling Conversion-Relevant Key Figures

If either the source or the target key figure in the disaggregation process is relevant for conversion, (for example, currency or unit of measure conversion), you must specify a conversion-to attribute, for example CURRENCYTO, or UOMTO, in one of the following ways:

● as a filter in the planning operator definition● as a filter in the Run or Schedule dialog box in the IBP Excel add-in

12.9.1 Example: Setting Up the Disaggregation Operator

Context

The DISAGG planning operator type is delivered as part of the standard SAP content for planning operators. In this example, a DISAGG_PROMO operator is created to read values of the PROMOUPLIFT key figure at product-customer level, and to disaggregate the key figure values to the PROMOSPLITALL key figure at product-location-customer level.

To set up the disaggregation operator, choose Manage Planning Operators on the initial screen of the Configuration app.


The following example illustrates how to set up a disaggregation operator.


Steps

1. Choose DISAGG from the list of planning operator types on the left side of the screen.2. To add a planning operator, select the + (Add Planning Operators) button.


Table 55:

Field Entry

Name DISAGG_PROMO

Description Disaggregation for Promotion

Interactive Mode No

Batch Mode Yes

Filter Mode Select or deselect according to whether you want the user to use filters when running or scheduling the operator in the IBP add-in for Microsoft Excel.

3. Choose Define Parameters, and enter the following parameters:

Table 56:


ATTRIBUTE1 PRDID

ATTRIBUTE2 CUSTID

DURATION 156

PERIODNAME Weekly

PERIOD_OFFSET -104

SOURCE_KFID1 PROMOUPLIFT Stored PERPRODCUST

TARGET_KFID1 PROMOSPLITALL Stored PERPRODLOCCUST

4. Save your entries.5. Assign the planning operator to the relevant planning area. For more information see Assigning a Planning

Operator to a Planning Area [page 91].

ExampleUsing the SEQUENTIAL Parameter

You can use the SEQUENTIAL parameter to control whether the system takes the result of one key figure copy and disaggregation into consideration when performing the subsequent key figure copy and disaggregation.

Study this example about the use of the SEQUENTIAL parameter. To keep the example simple, all key figures have the same base planning level.


Planning Operators

Table 57:

Parameter Initial Key Figure Value for a Given Period

Key Figure Value After DISAGG Run

SEQUENTIAL Parameter not Set

Key Figure Value After DISAGG Run

SEQUENTIAL Parameter Value = X

SOURCE_KFID1 = MARKETINGFCSTQTY

100 100 100

TARGET_KFID1 = DEMANDPLANNINGQTY

50 100 100

SOURCE_KFID2 = DEMANDPLANNINGQTY

50 100 100

TARGET_KFID2 = CONSENSUSDEMANDPLAN

50 100

12.10 Group (GROUP) Operator

The group (GROUP) operator allows you to define a group of planning operators that are executed in a single batch job in a defined sequence. Since a group operator can be run in batch mode only, all planning operators that you assign to a group operator must also be configured to run in batch mode.

A group operator can be triggered as follows:

● Automatically after importing key figure dataFor example, to update key figure calculations immediately after the data import, you can define a group of copy operators for the relevant key figures.To run a group operator automatically, you must specify the key figure IDs in the group operator settings.

● Manually in Excel (batch mode only)For example, if you always want a copy job to be run before supply planning, you can define a group operator that contains the relevant copy operator and S&OP operator. By using the group operator, the sequence of the jobs is always guaranteed and one batch job can be scheduled in Excel instead of two separate batch jobs.

Each individual planning operator in a group operator is run based on its own configuration settings, which cannot be changed by the settings in the group operator (for example, copy operator settings for copying key figures). However, if the user specifies a filter when he or she schedules the group operator in Excel, the filter applies to all planning operators assigned to the group operator.

Note that the group operator and the assigned planning operators must belong to the same planning area.


Table 58: Parameters


OPERATOR_TYPEn Operator type (for example, COPY or SCM)

n is a number starting from 1 (the same applies to the other parameters).

The operator type and ID must be defined in pairs.

Mandatory

OPERATOR_IDn Planning operator ID Mandatory

DI_KFIDn Key figure ID

You can enter as many key figures as required. If you enter key figures, the group operator is triggered automatically when the key figure values are uploaded using the data import functions.

Optional

STOPONERROR Stops execution of a group operator if any of the included operators returns an error. For example, if 5 operators have been defined and operator 3 returns an error, then operators 4 and 5 will not be executed.

NoteThe parameter stops execution of the group operator if a validation error is returned (for example, as a result of incorrect input) or if there is a runtime exception, but not when functional errors occur (such as when no record is copied).

Optional

NoteThe DISAGG operator cannot be used in a GROUP operator.

12.10.1 Example: Setting Up a Group Operator

The following example illustrates how to set up a group operator for a group of copy operators.


Planning Operators


Steps

1. Select Manage Planning Operators on the initial screen of the Configuration app.2. Choose the GROUP planning operator type from the list of planning operator types on the left side of the

screen.3. Select + (Add Planning Operators).


Table 59:

Field Entry

Name Group1

Description Group Operator for Copy Operators

Interactive Mode No

This mode is not allowed for the group operator.

Batch Mode Yes

Filter Mode Select or deselect according to whether you want the user to use filters when running or scheduling the operator in the IBP Excel add-in.

4. Choose Define Parameters, and enter the following parameters:

Table 60:

Parameter Name Parameter Value

OPERATOR_TYPE1 COPY

OPERATOR_ID1 10002

OPERATOR_TYPE2 COPY

OPERATOR_ID2 10003

DI_KFID1 TARGETREV

5. Assign the operator to the relevant planning area (see Assigning a Planning Operator to a Planning Area [page 91]).


Result

When key figure values are imported into the system, the copy operators assigned to the group operator will be run automatically for the key figure TARGETREV. In addition, the user can run the group operator in batch mode in the IBP Excel add-in.

12.11 Inventory Optimization (IO) Operator

The Inventory Optimization (IO) planning operator allows you to run inventory optimization for a given supply chain network.

CautionTo run the inventory operators, specific technical IDs defined by SAP must be used for the relevant master data types, attributes, and key figures. If these technical IDs are not used, the inventory operators will fail. For more information, see http://help.sap.com/ibp. Choose SAP Integrated Business Planning Application Help for SAP Integrated Business Planning English SAP Integrated Business Planning Advanced PlanningInventory Optimization Sample Planning Area for Inventory Optimization Master Data for Inventory Optimization and SAP Integrated Business Planning Application Help for SAP Integrated Business Planning English SAP Integrated Business Planning Advanced Planning Inventory OptimizationSample Planning Area for Inventory Optimization Key Figures in Inventory .

Operators

You can define the following inventory operators:


Planning Operators


Table 61:

Inventory Operator Algorithm Type Parameter Name in Excel Add-In

Explanation

Single-Stage Inventory Opt SINGLE STAGE IO Decomposed (single-stage) inventory optimization

Optimizes recommended safety stock locally for each customer-facing product-location combination in a decomposed manner. Ideal for running simulations where you want to determine the impact on recommended safety stock of local changes to the input key figures after multistage inventory optimization has been run.

Multi-Stage Inventory Opt MULTI STAGE IO Global (multi-stage) inventory optimization

Optimizes recommended safety stock globally across all products and locations of the supply chain. Minimizes total safety stock holding cost while ensuring that all customer service level targets are met.

Expected Demand Loss LOST SALES IO Expected lost demand Calculates the expected lost demand quantity under given inventory plans and demand distribution.

Forecast Error CV Calculator FORECAST_ERROR Calculate Forecast Error CV Calculates the forecast error coefficient of variation, that is, the difference between forecasted and actual demand. Forecast error is a statistical measure of forecast accuracy used to estimate the variability of the underlying demand.

Calculate Inventory Components

IO_DETERMINISTIC Calculate Target Inventory Components

Calculates Inventory components, that is, the types of inventory that comprise the total inventory for a given item. By delineating what type of inventory exists in the supply chain, more granular inventory optimization calculations can be made.


NoteThe Multi-Stage Inventory Opt operator and the Calculate Inventory Components operator calculate outputs for all demand streams, and therefore do not take visibility filter settings into consideration during calculations.

The operators Single-Stage Inventory Opt, Expected Demand Loss, and Forecast Error CV Calculator do take visibility filtering into consideration when calculating outputs.

Parameters for Forecast Error CV Calculator

To tune the output of the Forecast Error algorithm, you can set the following parameters for the Forecast Error CV Calculator:

Table 62:

Parameter Description

ADJUSTFORBIAS Adjust forecast error for bias tendencies, whether for all tendencies (ADJUSTALL), positive tendencies only (ADJUSTPOSITIVE), negative tendencies only (ADJUSTNEGATIVE), or no adjustment to the forecast (ADJUSTNONE).

The default parameter uses ADJUSTPOSITIVE as a conservative input to generate higher safety stock recommendations.

BIASCONFIDENCEINTERVAL Confidence interval used for the forecast error bias, ranging between 0 and 1 (actual maximum is 0.9999).

Default value = 0.99.

CVCAP Non-negative number limiting the value of the coefficient of variance.

Default value = 3.

CVDEFAULT Non-negative default value of the coefficient of variance in absence of an input value.

Default value = 1.

ERRORMEASURE Type of error measure, either MAPE (Mean Absolute Percent Error) or MAD (Mean Absolute Deviation).

Default is MAD

PECAP Non-negative number limiting the value of the percent error.

Default value = CVCAP/1.25 (or 3/1.25)


Planning Operators

Parameter Description

PEDEFAULT Non-negative default value of percent error in absence of input value.

Default value = CVDEFAULT/1.25 (or 1/1.25).

Example: Adjust for All Bias in Forecast Error Calculations

The following example illustrates how to set up a forecast error operator that adjusts for all bias:

Steps1. Navigate to Manage Planning Operators on the Configuration UI.2. Select the IO planning operator type and click the “+” button to add a planning operator.


Table 63:

Field Entry

Name Forecast Error Calculator

Description Calculate Forecast Error

Interactive Mode No

Batch Mode Yes

Filter Mode Yes

3. Choose Define parameters and enter the ADJUSTFORBIAS parameter with ADJUSTALL as the parameter value.

4. Assign the operator to the relevant planning area (see Assigning a Planning Operator to a Planning Area [page 91]).

ResultThe user can run the planning operator in the IBP add-in for Microsoft Excel in simulation mode and batch mode.

12.12 Purge Change History (PCH) Operator

CautionThis operator will be discontinued with the next release of SAP Integrated Business Planning. We strongly recommend that you use the Purge Change History Data application job template instead.


If you have previously scheduled recurring jobs that use this operator type, cancel or delete them and schedule new application jobs using the Purge Change History Data application job template.

If you have any job chains that contain the Purge Change History Operator job, replace the job with the Purge Change History Data job.

The Purge Change History (PCH) operator deletes all change history data that is older than a specified number of days. It can be run in batch mode only.

Table 64:


DAY_OFFSET Offset in days relative to the current date.

For example, if you enter 100, the operator deletes all change history data that is older than 100 days.

Mandatory

PLAREA Planning area for which the change history is to be purged

Mandatory

When you define a PCH operator, you must make the following mode settings:

● Interactive mode: No● Batch mode: Yes● Filter mode: Select or deselect according to whether you want the user to use filters when running or

scheduling the operator in Microsoft Excel.

12.13 S&OP (SCM) OperatorYou use the S&OP (SCM) operator type to define planning operators that allow users to do the following:

● Perform demand and supply planning across the supply chain network using the S&OP heuristic and optimizer algorithms.

● Check the consistency of planning data.● Perform local updates of basic key figures (for example, projected stock, deficit, and shortage) without

recalculating a new supply plan.

Each planning operator has an algorithm and, in most cases, additional parameters. The S&OP (SCM) operator type and the related algorithms and parameters are delivered in the standard system.

For more information, see S&OP Operators (System Administrator) in the application help.

CautionTo run the S&OP operators, specific technical IDs defined by SAP must be used for the relevant master data types, attributes, and key figures. If these technical IDs are not used, the S&OP operators will fail. For more information, see Planning with S&OP Algorithms in the application help on SAP Help Portal at http://help.sap.com/ibp, under Master Data and Key Figures.


Planning Operators



12.14 Purge Key Figure Data (PURGE) Operator

The Purge Key Figure Data operator allows you to delete key figure values from a planning area.

CautionThis operator will be discontinued with the next release of SAP Integrated Business Planning. We strongly recommend that you use the Purge Key Figure Data application job template instead.

If you have previously scheduled recurring jobs that use this operator type, cancel or delete them and schedule new application jobs using the Purge Key Figure Data application job template.

If you have any job chains that contain the Purge Key Figure Data Operator job, replace the job with the Purge Key Figure Data job.

The Purge Key Figure Data (PURGE) operator allows you to delete all key figure data that is older than a specified time period. It can be run in batch mode only.

Table 65:


PERIOD_OFFSET Period offset relative to the current time period.

You must specify the offset as a number of time periods, based on the Storage Time Profile Level of the planning area.

For example, you have a planning area for which the storage time profile level is monthly. If you set 12 as the period offset and the current period is August 2016, the operator deletes all key figure data older than August 2015.

Mandatory

PLAREA Planning area for which the key figure data is to be purged.

Mandatory



PLEVELn Base planning level of a stored key figure.

With this parameter, you can restrict at which base planning level you want to purge the key figure data. You can specify multiple instances of the parameter. For example, you can specify values for PLEVEL1, PLEVEL2, and PLEVEL3. If a key figure does not exist at any of the specified base planning level, its data isn’t purged.

If you don’t add a PLEVELn to your PURGE operator, the operator deletes all key figure data that is older than the time period you specified with the PERIOD_OFFSET parameter.

Optional

When you define a PURGE operator, you must make the following mode settings:

● Interactive mode: No● Batch mode: Yes● Filter mode: Select or deselect according to whether you want the user to use filters when running or

scheduling the operator in Microsoft Excel.

12.15 ABC Classification (ABC) Operator

The ABC Classification operator allows you to categorize the values of a set of planning objects into A, B or C categories based on the values of a key figure defined on those attributes. For example, you may want to categorize the product attribute based on the revenue key figure. You can also choose to categorize the product family attribute or the combination of product and customer. Attribute combinations are called planning objects in SAP Integrated Business Planning.

NoteSAP recommends that you use the new Manage ABC/XYZ Segmentation Rules app and the SEGMENTATION planning operator instead of the ABC planning operator.

The system can perform the classification in four different ways, meaning that there are four classification types. In all of these types the planning objects are sorted in decreasing order of key figure values. What is different is how the top tier, middle tier, and bottom tier are determined.

The classification types are illustrated by the table below, in which “Product” is used as the planning object and “Revenue” as the key figure that the classification is based on.


Planning Operators

Table 66:

Product Revenue Cumulative Revenue

% of Total Revenue

Cumulative %

Class. Type 1

Class. Type 2

Class. Type 3

Class. Type 4

A: 70%

B: 20%

C: 10%

A: 100,000

B: 50,000

A: 20%

B: 50%

A: 3

B: 4

PROD10 51550 51550 34% 34% A A A A

PROD9 43888 95438 29% 62% A A A A

PROD8 19480 114918 13% 75% A A B A

PROD7 15100 130018 10% 85% B B B B

PROD6 9146 139164 6% 91% B B B B

PROD5 6075 145239 4% 95% C B B B

PROD4 4160 149399 3% 98% C B B B

PROD3 3362 152761 2% 100% C B C C

PROD2 108 152869 0% 100% C C C C

PROD1 100 152969 0% 100% C C C C

Classification Types

Classification Type 1: By Contribution to the Total Revenue in Percentage

In this classification type, the products assigned to the A, B, or C classes account for specific percentages of the total revenue. In the example above, the limit for class A is set to include the products with the top 70% contribution. PROD10 and PROD9 are the two top grossing products in that order, but the cumulative percentage of revenue they contribute is only 62%, so they do not pass the limit. PROD10, PROD9, and PROD8 are therefore all classified as A as together they contribute 75%, which is over the 70% limit. Further products could be included as well if their key figure values were identical with that of a product already included.

The limit for class B is set to 20%, which equals to a cumulative limit of 90% (70% for class A and 20% for class B). In the example above, class A contributes 75%, which is complemented by PROD7 and PROD6 to pass the limit with a cumulative 91%. Therefore, PROD7 and PROD6 are assigned to class B and the rest of the products to class C.

Classification Type 2: By Contribution to the Total Revenue in Absolute Value

In this classification type, the products assigned to the A, B, or C classes account for specific amounts of the total revenue. In the example above, the limit for class A is set to include the products with the top 100,000 contribution. PROD10 and PROD9 are the two top grossing products in that order, but the cumulative amount of


revenue they contribute is only 95,438, so they do not pass the limit. PROD10, PROD9, and PROD8 are therefore all classified as A as together they contribute 114,918, which is over the 100,000 limit.

The limit for class B is set to 50,000, which equals to a cumulative limit of 150,000 (100,000 for class A and 50,000). In the example above, class A contributes 114,918, which is complemented by PROD7, PROD6, PROD5, PROD4, and PROD3 to pass the limit with a cumulative 152,761. Therefore, these products are assigned to class B and the rest of the products to class C.

Classification Type 3: By the Number of Revenue Grossing Products in PercentageIn this classification type, the products assigned to the A, B, or C classes account for specific percentages of the revenue grossing products. In the example above, the limit for class A is set to include the first 20% of all products ordered by revenue. There are 10 products in total, so the first 20% equals to 2. Therefore, PROD10 and PROD9 are assigned to class A as those 2 of products that bring in the most revenue.

In the example above, PROD8, PROD7, PROD6, PROD5, and PROD4 are those 50% of all products that bring in the most revenue after the products in class A. Therefore, these products are assigned to class B and the rest of the products to class C.

Classification Type 4: By the Number of Revenue Grossing Products in Absolute ValueIn this classification type, the products assigned to the A, B, or C classes account for specific numbers of products ordered by revenue. In the example above, the limit for class A is set to include the first 3 of all products ordered by revenue. Therefore, PROD10, PROD9, and PROD8 are assigned to class A as those 3 products that bring in the most revenue.

The limit for class B is set to 4. In the example above, PROD7, PROD6, PROD5, and PROD4 are those 4 products that bring in the most revenue after the products in class A. Therefore, these products are assigned to class B and the rest of the products to class C.

12.15.1 Example: Setting Up the ABC Classification Operator

The ABC Classification planning operator type is delivered as part of the standard SAP content for planning operators. In this example, an ABC Classification operator is created to classify the Product attribute combination (PRODID - PRODDESCR - PRODFAMILY) by the values of the CONSENSUSDEMANDREVENUE key figure.

The attribute combination you classify must be a subset of the attributes in the planning level of the key figure you classify by. If you use the PRDID attribute for the product dimension, create a planning level, for example, PRD, with PRDID as the only the attribute. In general, create a planning level with the exact attribute combination that you want to classify. Such a planning level typically does not have any attribute from the time dimension unless you want to classify the month into high, moderate, and low selling month.

1. On the Manage Attributes screen of the Configuration app, create new attribute, ABCCODE with data type NVARCHAR and length 1, to hold the ABC classification value.Optionally, you can also create an ABCLOCKED attribute that prevents the values of the ABCCODE attribute from being updated. The data type of this attribute is INTEGER and its value 1.

2. On the Manage Master Data Types screen, add the new attribute to the master data type that contains the Product attribute combination that you want to classify. Activate the product master data.

3. Upload a planning view from the IBP add-in for Excel with the ABCCODE attribute set for each attribute combination as A, B, and C.


Planning Operators

Table 67:

PRODID PRODDESCR PRODFAMILY ABCCODE

x100 x100 Phone x Phone B

x101 x101 Phone x Phone C

x102 x102 Phone x Phone A

x103 x103 Phone x Phone B

4. On the Define Planning Area screen, include the ABCCODE attribute in the planning area and mark it as calculated.

5. On the Manage Planning Levels screen, add the ABCCODE attribute to the planning levels that contain all the attributes of the combination that is to be classified, in this case PRDID. This ensures that every time a key figure is displayed in the planning view in the IBP add-in for Excel, the ABC code is also displayed with it.

NoteThe attributes must not be added to the planning level created in step 2, which is to contain only the attribute combination you are classifying.

6. Create the ABC Classification Operator type on the Manage Planning Operators screen of the Configuration UI. Enter the following○ Add Job Procedure: "/IBP/CL_SAP_SFND_SOPAPI=>SOPAPI_OPERATOR_SCHED_JOB_ADD"○ Schedule Procedure: "/IBP/CL_SAP_SFND_SOPAPI_SCHED=>SOPAPI_EXEC_SCHEDULER_ABC_JOB"

7. Create an operator of type ABC and name it, for example, TXXABC. Select Batch Mode and if you want to allow the users to specify a filter while scheduling the ABC operator, then also select Filter Mode.The following are mandatory parameters of the operator type:

Table 68:

Parameter Name Example Value Comment

ABCCODE_ATTR AAAABCCODE The attribute where the ABC code is stored. Replace AAA in the parameter value by your group ID.

PLEVEL PRD The planning level that contains only the attribute combination to be classified.

INPUT_KFID CONSENSUSDEMANDREVENUE Key figure ID by which to classify.



A 0.2 Defines which values belong to class A. Specified in percentage or absolute value depending on the classification type you choose for parameter B (both must be the same). If it is a percentage, enter it as decimal. For example 20% as 0.2.

B 0.5 Defines which values belong to class B. Specified in percentage or absolute value depending on the classification type you choose for parameter A (both must be the same). If it is a percentage, enter it as decimal. For example 50% as 0.5.

The conversion attributes are also mandatory if the key figure specified in the parameterINPUT_KFID is conversion-relevant, such as the unit of measure (UoM) or currency. For example, if the key figure has UoM, and the attribute that is marked as conversion target is UOMTOID, then specify UOMTOID as the parameter name and a UoM such as Kg as the parameter value.The following are optional parameters of the operator type:

Table 69:


ABCCODE_ATTR_FIX ABCLOCKED Indicates whether the classification is locked for certain attribute value combination.

CLEAR_ABC Yes Clears the previously calculated ABC code. If set to 'yes', the other parameters except for MASTERDATA_UPDATE should not be set. MASTERDATA_UPDATE is optional.

CLASSIFICATION_TYPE 1 Can be 1, 2, 3, or 4. If not specified, the default value is 1.


Planning Operators


DURATION 2 An integer value larger than 1. If not set, it is assumed to be 1. The key figure values are aggregated for each attribute value combination and the duration selected. The aggregation depends on the key figure configuration. The value of the key figure thus calculated for each attribute combination value will be used for classification. Duration will be assumed to be specified in the smallest time bucket that the key figure is defined on. If the smallest time bucket on which the key figure is defined is month, then the duration will be assumed to be in month.

PERIOD_START_OFFSET_REL_CURRENT

4 An integer value. If not set, it is assumed to be 0. The period that is considered to calculate the key figure values begins at the current period plus the offset, and ends at the current period plus the offset plus one less the duration.PERIOD_START_OFFSET_REL_CURRENT is assumed to be specified in the smallest time bucket that the key figure is defined on.

MASTERDATA_UPDATE Yes If set to Yes, it updates the master data type from where the ABC Code attribute was assigned to the planning area. In this case the master data type must also contain all the attributes of the planning level specified in the parameter PLEVEL, and it must be a simple or compound master data type.

8. Assign the ABC classification operator to the planning area.9. Run the ABC Classification operator in the IBP add-in for Excel. Once the job is completed, refresh the view to

see the results.

12.16 Forecast Error (KPI_PROFILE) Operator

The Forecast Error (KPI_PROFILE) operator allows you to perform forecast error calculations.


You can define the following:

● Interactive mode: Yes or No● Batch mode: Yes● Filter mode: Yes

There are no other parameters for this operator.

For more information, see Setting Up Forecast Error Calculations in the application help on SAP Help Portal at http://help.sap.com/ibp.

12.17 Segmentation (SEGMENTATION) Operator

The Segmentation (SEGMENTATION) operator allows you to schedule and run ABC/XYZ segmentation jobs in the Application Jobs app if you have assigned it to the planning area you are using.

There are no editable parameters for this operator.


Planning Operators


13 Snapshots

A snapshot takes a copy of a key figure at a particular point in time. To check how key figures have evolved over time, you can compare multiple snapshots. The Redo Snapshot function in the IBP Excel add-in lets you re-take a snapshot if there are errors or incorrect data.

To avoid having to capture too much data, the system does not always take a snapshot of the actual key figure, but rather of the inputs used to calculate it. A snapshot is taken only if a snapshot operator is run (by a user from the IBP Excel add-in or scheduled as a background job).

NoteUnlike snapshots that capture key figure values at a particular point in time, the change history automatically keeps track of all changes to key figures (that are enabled for this feature) without the need for a planning operator. See also Enabling Change History for Key Figures [page 206].

However, you can still set up a snapshot operator as type Change History. This is required if you want to use the operator to create historical forecast snapshots for demand sensing purposes. In all other cases, choose Original for the snapshot type.

You can create up to 9 time snapshots at periodic intervals, producing a time-elapsed view of your data. The most recent snapshot is numbered 1. When a new snapshot is created, the number of the previous snapshot is increased by 1. You can also configure the snapshot to run periodically in the background. Once you have created a snapshot, activate the planning area to make the snapshot available in the system.

Note● You cannot modify definitions for snapshot key figures. This means that you cannot modify the following:

○ Input key figures○ Number of snapshots○ From-to time period settings

● You cannot define snapshots for figures that include a helper key figure with attribute transformation.● You cannot include snapshots in a group operator.● The change history is not supported for snapshots.

13.1 Configuring SnapshotsYou configure snapshots at the level of a planning area.

NoteYou cannot change a snapshot definition once the snapshot has been created. It is not possible, for example, to choose different key figures or change the maximum number of snapshots stored in the system. If you need different settings, create a new snapshot definition.

Model Configuration GuideSnapshots C U S T O M E R 125

Steps

1. Launch the Configuration app by clicking the corresponding tile on the launchpad.2. If it is not already selected, click Start Here under Overview.3. Under Miscellaneous Settings, select Manage Snapshot Configuration.

From this screen you can add, edit, or delete snapshot definitions.4. Select your planning area.5. Choose Create New.

The following table explains the snapshot settings:

Table 70:

Field Explanation Example Entry

Name Short descriptive name for the snapshot

ABCSALESFORECASTSN

Description Longer description of the snapshot Sales Forecast Snapshot

Snapshot Type Type of the snapshot: Original or Change History. Choose Change History only if you are defining a snapshot of the consensus demand for demand sensing purposes.

Original

Input Key Figures Key figures to include in the snapshot FORECAST, HISTORY, SALESFORECAST

Key Figure ID Suffix Suffix that identifies the object as a snapshot key figure. The naming convention is $KFNAME$_$suffix$_snapshotnumber

SN

From The first time period in your snapshot time period range. Periods are defined in the time storage level of the key figure’s planning area.

-6

To The last time period in your snapshot time period range. Periods are defined in the time storage level of the key figure’s planning area.

6


Snapshots

Field Explanation Example Entry

Max Number of Stored Snapshots The maximum number of elapse photos you can take of a key figure. The most recent snapshot is numbered 1, the previous 2, and so on. When the maximum number is reached, the oldest snapshot is deleted to make room for the new one. The maximum allowed number of snapshots is 9.

9

6. Save your entriesTo check that the snapshot is correctly assigned to the snapshot planning operators, go to your planning area and click Planning Operators: The snapshot definition you have just created is listed (and selected) under the snapshot operator.

7. Activate your planning area.The new snapshots are created as key figures.These snapshots are also created in the relevant Key Figure window. Based on the maximum number of stored snapshots selected, that number of snapshots will be created in the Key Figures window.

Model Configuration GuideSnapshots C U S T O M E R 127

14 Activating Planning Models

Before you can use the data you have set up in the application, you have to activate your planning model. When the model is activated, the infrastructure to store and access planning data is created based on the metadata of the custom model you created.

RecommendationSAP recommends that you perform model activation in isolation when no other concurrent activations are running.

You must activate your model entities in the following order:

1. Time profiles2. Master data types3. Planning areas

You can also activate a planning model in one step, by activating a planning area together with its related time profile and related master data types.

Once you have activated your planning model, you can copy it, and perform active deletion of model entities if needed.

14.1 Statuses of Model Entities

The background information provided in this chapter can help you better understand how modeling and activation in SAP Integrated Business Planning works.

Model Entities and Their Activation

In SAP Integrated Business Planning, planning models are based on the following model entities:

● Attributes● Master data types● Time profiles● Planning areas● Planning levels● Key figures● Versions● Miscellaneous additional entities: planning operators, global configuration parameters, and reason codes


Activating Planning Models

Activating Model EntitiesOut of these entities, you can perform activation for the following ones:

● Master data typesThe activation of a master data type will activate all attributes assigned to the master data type as well.

● Time profilesThe activation of a time profile will activate all attributes assigned to the time profile as well.

● Planning areaThe activation of a planning area will activate all attributes assigned to the planning area, the key figures, planning levels and versions as well.You can also include the master data types used in the planning area (and with them, the attributes they include) in the activation.

Other entities can be activated only together with the higher-level entity that includes them.

Statuses of a Model Entity

A time profile, a master data type, and a planning area can have the following statuses:

● InactiveAn entity has the inactive status either when it’s created and first saved, or when the active entity is changed and saved.

● ActiveAn entity has the active status after it has been activated, either directly or indirectly (together with a higher-level entity).

● Pending deletionIf an active entity is marked for deletion, it has the pending deletion status. Actual deletion takes place with the next activation of the entity. Until then, you can revert the pending deletion status to active.

NotePlanning levels, key figures, and versions can have the same three statuses. However, you can't activate these model entities on their own, only via the planning area that includes them.

Attributes are a special case. An attribute has a status on its own, but you can activate it only as part of the activation of a higher level entity (master data type, time profile, planning area). An attribute can have the following statuses:

● InactiveAn attribute has the inactive status either when it’s created and first saved, or when the active attribute is changed and saved.

● ActiveAn attribute has the active status after it has been activated (together with a master data type, a time profile, or a planning area).

Model Configuration GuideActivating Planning Models C U S T O M E R 129

Instances of a Model Entity

Along with statuses, entity instances are also a key concept in model activation. An instance is a saved state of a model entity, and it is classified by the status.

One or two instances – which have different statuses – of a model entity can exist at the same time:

● InactiveThe entity is created and first saved, but not activated yet.

● ActiveThe entity has been activated, and has not been changed since the last activation.

● Active and inactiveThe entity has been activated (active instance), and changed since the last activation (inactive instance).

● Active and pending deletionThe entity has been activated (active instance), and marked for deletion since the last activation (pending deletion instance).

In the Configuration app, you can choose to display the most recent instance of the model entity (Edit Active and Inactive), or the active instance (Display Active Only).

NoteThe inactive instance of a higher-level entity refers to the latest instance of the dependent entity, be it active or inactive.

For example, if both an attribute and a master data type that uses the attribute have inactive and active instances, the active instance of the master data type uses the active instance of the attribute, while the inactive instance of the master data type uses the inactive instance of the attribute.

Status Changes of a Model Entity

The life cycle of a model entity starts with the inactive status, after the entity has been created and saved. The entity can get into the active status by activation.

Changing an Active EntityWhen an active entity is changed, but not activated yet, the active instance of the entity stays unchanged, and an inactive instance is created, which stores the changes.

The active instance is used throughout SAP Integrated Business Planning, for example, in the IBP Excel add-in, in planning operators, and in data integration. Once the entity is activated again, the changes take effect, and the inactive instance becomes the active (and, until the next changes, the only) instance of the entity.

NoteIf you have activated an entity, you cannot restore the previous active instance.

Deleting an EntityYou can use active deletion to delete active master data types, planning levels, key figures, planning areas, and time profiles. For more information, see Deleting Active Objects (Active Deletion) [page 149].



With active deletion, the inactive instance of the entity is immediately deleted. If there is an active instance of the entity, the active instance remains unchanged, and a pending deletion instance is created. These two instances exist in parallel until the next activation of the entity.

Until the next activation, the active instance of the entity is used throughout SAP Integrated Business Planning, for example, in the IBP Excel add-in, in planning operators, and in data integration. The next activation will delete the entity (both the active and the pending deletion instances), and the data that has been uploaded for the given entity.

If the entity has only an inactive instance, it is immediately deleted if you choose Delete (active deletion is not available in this case).

14.1.1 Example: Changing Model Entities That Are Dependent on Each Other

In this example, we start with 3 attributes (A1, A2, and A3), which are used in a master data type (MDT1), which is then used in a planning area (PA1).

We then create a new attribute, A4, add it to the MDT1 master data type, and activate the master data type. After it, we assign the A4 attribute to the PA1 planning area, and activate the PA1 planning area.

The next step is creating a new attribute, A5, and adding it to the MDT1 master data type, without activating the master data type.

As the last step, we change the period offset in the PA1 planning area (this change does not have any effect on attributes or master data types).

Starting Point

Table 71:

Entity Uses Instance Comment

Attribute A1 Used in MDT1 and in PA1 Active



Master data type MDT1 Used in PA1

Uses A1, A2, A3

Active

Planning area PA1 Uses A1, A2, A3, and MDT1 Active


Step 1: Creating the A4 Attribute, and Adding it to the MDT1 Master Data Type

Table 72:





Attribute A4 Selected for use in MDT1 Inactive The A4 attribute is saved, and included in the MDT1 master data type.

Until MDT1 is activated, only the inactive instance of A4 exists.


Uses A1, A2, A3

Active Until MDT1 is activated again, the active instance is unchanged.

Used in PA1

Uses A1, A2, A3, A4

Inactive The inactive instance of MDT1 is created to store the changes - in this case, the A4 attribute added to MDT1.


The IBP Excel add-in, the data integration, and other functions of IBP continue using the active instance of the MDT1 master data type.

In the Configuration app, if you display the inactive entities as well, you can assign the newly added A4 attribute to the PA1 planning area.

Step 2: Activating the MDT1 Master Data Type

Table 73:








Attribute A4 Used in MDT1 Active The A4 attribute becomes active when the MDT1 master data type is activated.

The inactive instance of A4 does not exist any longer.


Uses A1, A2, A3, A4

Active The previously inactive instance of MDT1 becomes the active - and only - instance of MDT1.

There is no inactive instance of MDT1.

Planning area PA1 Uses A1, A2, A3, and MDT1 Active Activating the MDT1 master data type has no effect on the PA1 planning area. It still has one active version, which is unchanged

Step 3: Assigning the A4 Attribute in the PA1 Planning Area and Activating the PA1 Planning Area

Table 74:





Attribute A4 Used in MDT1 and in PA1 Active The A4 attribute is now used in the PA1 planning area as well.


Uses A1, A2, A3, A4

Active



Planning area PA1 Uses A1, A2, A3, A4, and MDT1 Active The active instance of the PA1 planning area now also includes the A4 attribute.

The new active instance of PA1 overwrites the previous active instance.

Step 4: Creating the A5 Attribute, and Adding it to the MDT1 Master Data Type

Table 75:






Attribute A5 Used in MDT1 Inactive The A5 attribute has been saved, and included in the MDT1 master data type. Until MDT1 is activated, only the inactive instance of A5 exists.


Uses A1, A2, A3, A4

Active As no activation has happened, the active instance of MDT1 is unchanged.

Used in PA1

Uses A1, A2, A3, A4, A5

Inactive Adding A5 to MDT1 results in an inactive instance of MDT1.

Planning area PA1 Uses A1, A2, A3, A4, and MDT1 Active

The IBP Excel add-in, the data integration, and other functions of IBP continue using the active instance of the MDT1 master data type.

In the Configuration app, if you display the inactive entities as well, you can assign the newly added A5 attribute to the PA1 planning area.



Step 5: Changing the Period Offset of the PA1 Planning Area

Changing the period offset affects the planning area only, and not the master data types and attributes the planning area uses.

Table 76:






Attribute A5 Used in MDT1 Inactive


Uses A1, A2, A3, A4

Active

Used in PA1

Uses A1, A2, A3, A4, A5

Inactive

Planning area PA1 Uses A1, A2, A3, A4, and MDT1 Active The active instance of PA1 still refers to the active instance of MDT1.

Uses A1, A2, A3, A4, A5, and MDT1

Inactive The inactive instance of PA1 still refers to the inactive instance of MDT1.

NoteIn such cases, when an inactive instance of a planning area refers to an inactive instance of a master data type, you should either activate the master data type before you activate the planning area, or activate the planning area with the Include Related Time Profile and Master Data Types option selected.

14.1.2 Example: Deleting an Attribute from an Active Master Data Type and Active Planning Area

In this example, we start with 3 attributes (A1, A2, and A3), which are used in a master data type (MDT1), which is then used in a planning area (PA1). Our goal is to delete the A3 attribute.

To delete the A3 attribute, which is used in a master data type, which is then used in a planning area, you must work top down. First, remove the attribute from the planning area, then from the master data type.


Starting Point

Table 77:






Uses A1, A2, A3

Active


NoteMake sure that the A3 attribute is not used in any planning levels. You cannot delete an attribute if it is used in higher-level entities.

Step 1: Mark the A3 Attribute for Deletion in the PA1 Planning Area

Table 78:






Uses A1, A2, A3

Active


Uses A1, A2, and MDT1 Inactive The inactive instance of the PA1 planning area does not include the A3 attribute.



Step 2: Activating the PA1 Planning Area

Table 79:




Attribute A3 Used in MDT1 Active The attribute is not used in the PA1 planning area anymore


Uses A1, A2, A3

Active

Planning area PA1 Uses A1, A2, and MDT1 Active The PA1 planning area has an active instance only, which does not include the A3 attribute.

Step 3: Mark the A3 Attribute Pending Deletion in the MDT1 Master Data Type

Table 80:




Attribute A3 Used in MDT1 Active


Uses A1, A2, A3

Active The active instance is unchanged, it still includes the A3 attribute.

Used in PA1

Uses A1, A2

Inactive An inactive instance of the MDT1 master data type has been created, which does not include the A3 attribute.

Planning area PA1 Uses A1, A2, and MDT1 Active

An attribute does not have a pending deletion status, so the active instance of the attribute is unchanged. The A3 attribute is pending deletion in relation to the MDT1 master data type only. If, unlike this example, other maser data types also use the A3 attribute, A3 is still available to them.


Step 4: Activating the MDT1 Master Data Type

Table 81:




Attribute A3 No uses Active The A3 attribute is not used in any higher-level entities.

The active instance of the attribute is unchanged.


Uses A1, A2

Active The active instance now does not include the A3 attribute.

Planning area PA1 Uses A1, A2, and MDT1 Active

14.2 Activating Time Profiles

Context

CautionMake sure that you activate a time profile before the planning areas that use the time profile.

Alternatively, when you activate a planning area, you can select to activate it together with the related time profile and the related master data types in one activation run.

Procedure

1. In the Configuration app, navigate to Time Profiles, select the time profile you want to activate, and choose Check.

The system executes three types of checks:○ Validating the definition of the time profile○ Validating the dependencies and connections of the time profile, for example, connections to planning

areas○ Checking if the changed time profile is still consistent with the already existing time periods

You can display and study the check result in the log.



NoteThere are checks that can be executed only during activation. Thus, activation of a time profile might fail even if the previously executed checks were successful.

2. Select the time profile you want to activate from the list on the left, and choose Activate. In the dialog box that appears, make sure you have selected the time profile you want to activate, and choose Activate.

If all the activation was successful, the time profile is active.

You can check the activation status and steps in the log.

Related Information

Time Profile Activation: Checks and Errors [page 142]

14.3 Activating Master Data Types

Prerequisites

Make sure that you activate the master data types only after you have activated the relevant time profiles, or you activate them together when you activate a planning area..

Procedure

1. In the Master Data Types app, select one or more master data types you want to activate.

Alternatively, you can use the Master Data Types screen in the Configuration app.2. Choose Check.

By default, the system checks the consistency of the master data types you selected together with their dependent master data types. To check only the master data types you selected, choose Check Without Dependencies.

If you are using the Configuration app, navigate to Master Data Types, and select the master data type you want to check, then choose Check. You can choose to check the dependent master data types as well.

In both cases, the system performs the following three types of checks:○ Checking the definition of the master data type○ Checking the dependencies and connections of the master data type, for example, connections to other

master data types, to planning areas, or the existence of attributes.○ Checking if the changed master data type is still consistent with the already existing data.


You can see the status of the check and the steps performed in the log in the Application Logs app or within the Configuration app.

If there are errors in the check log, correct them before you activate the master data types.

NoteThere are checks that run only during activation. Thus, activation of a master data type might fail even if the previous checks were successful.

3. After a successful check, choose Activate.

By default, the system activates the master data types you selected together with their dependent master data types. To activate only the master data types you selected, choose Activate Without Dependencies.

If you are using the Configuration app, navigate to Master Data Types, and select a master data type you want to activate. In the dialog box that appears, you can select multiple master data types to activate, and you can choose to activate the dependent master data types as well. Then choose Activate.

If all the activation was successful, the master data types are active.

When you activate a master data type, the attributes the master data type uses are activated as well. You can't activate an attribute separately.

Next Steps

You can check the activation status and steps in the log within the Configuration app, or in the Application Logs app.

14.4 Activating Planning Areas

Activate the planning area to be able to upload data into it, and to perform planning tasks.

Prerequisites

Make sure that you activate a planning area either only after you have activated the time profile and the master data types that are assigned to the planning area, or you activate the planning area together with its related time profile and related master data types.

Procedure

1. In the Configuration app, navigate to Planning Area and Details, select the planning area you want to activate.



2. Choose Check Planning Area.

The system validates the following:○ The definition of the planning area, of the versions and planning levels of the planning area, and the

definitions and calculations of the key figures in the planning area.○ The dependencies and connections of the planning area, for example, connection to a time profile, or the

existence of the assigned attributes

You can see the status of the check and the steps performed in the log within the Configuration app.

If there are errors in the check log, correct them before you activate the planning area.

NoteThere are checks that run only during activation. Thus, activation of a planning area might fail even if the previous checks were successful.

3. After a successful check, choose Activate.

In the Activate dialog box, you have the option to activate the related time profile and the related master data types.

NoteMake sure you activate all related master data types first, or you select the Include Related Time Profile and Master Data Types checkbox when you activate the planning area.

If all the activation was successful, the planning area is active.

You can check the activation status and steps in the log within the Configuration app.

Results

If you activate a planning area, all attributes assigned to the planning area, the key figures, planning levels and versions will be activated as well. You can’t activate these model entities directly.

If you have selected the Include Related Time Profile and Master Data Types option, the time profile that is assigned to the planning area, and the master data types used in the planning area (and with them, the attributes they include) are also activated.

Related Information

Activation of Time Profiles: Checks and Errors [page 142]Activation of Master Data Types: Checks and Errors [page 143]


14.5 Troubleshooting for Model Activation Errors

The errors listed below are the most common errors that can occur during activation.

14.5.1 Activation of Time Profiles: Checks and Errors

Consistency Checks for Time Profiles

When you start the consistency check or the activation of a time profile, the system performs the following checks:

● Checking the definition of the time profile○ A description must exist for the time profile.○ A start date and an end date must be specified.○ The end date must be later than the start date.○ At least one time profile level must exist.○ All time profile levels must have a description.○ Time profile levels must form a sequence based on the period type. That is, a lower time profile level must

have lower granularity than the higher ones.For example, a time profile level with the period type “Day” must come before the one that has “Month” for period type.

○ The base level of a time profile level must be a time profile level that has lower granularity.○ If attributes are assigned to a time profile level, they must not be of the DECIMAL data type.○ If an attribute of NVARCHAR data type is assigned to a time profile level, the length of the attribute must be

between 1 and 5000.● Checking the dependencies and connections of the time profile

○ It is not allowed to add or delete a time profile level if the time profile is assigned to any planning areas.○ It is not allowed to remove an attribute assigned to a time profile level if the attribute is used in a planning

level of an active planning area that uses the time profile.○ It is not allowed to use active deletion on a time profile that is assigned to any planning areas.

● Checking the time profile against the already existing time periods○ If time periods already exist for the time profile, you cannot add an additional required attribute.

Help for Error Analysis

Study the check log and the activation log to learn what made the check or the activation fail. The messages you find in the log provide you with information about the errors.

For certain messages, which originate from complex situations, you'll find additional information in the table below.



Table 82:

Message Text Reason and What to Do

Cannot lock time profile &1. Another activation may be running.

Try activating the time profile later.

Cannot add &1 as required attribute to a not empty table (&2). You assigned a new required attribute to a time profile level, while time periods already exist for the time profile.

Assign the attribute as optional attribute. Upload the time periods again. Each time period must have a value for this attribute. As a last step, select the required checkbox for the attribute. For more information, see Changing and Deleting Time Profiles [page 41].

Inconsistent period types (TP level &1 must not be before level &2)

In the definition of the time profile, a time profile level with a period type of a lower granularity must come before a time profile level that has a higher-level period type. For example, the time profile level for months must come before the one for quarters.

Attribute &1 is already used in PA &2. It cannot be removed from TP.

The attribute you wanted to remove from the time profile is in use in a planning area. Remove the attribute from the all planning levels that use it, then you can remove it from the time profile.

Attribute &1 is already used in PA &2. It cannot be added to TP.

The attribute you wanted to assign to a time profile level is in use in a planning area, via the assignment to a master data type.

Based on your modeling decision, remove the attribute from the planning area first, then you can assign it to the time profile level. Or, you can create a new attribute, and assign this attribute to the time profile level.

Uploading time periods needed as number of TP levels in TP &1 changed.

This is an information message. You get this message if you change the time profile for which you have already created the time periods.

You must upload the time periods again.

14.5.2 Activation of Master Data Types: Checks and Errors

Consistency Checks for Master Data Types

When you start the activation of a master data type, the system performs the following checks:

● Checking the definition of the master data type○ A name must exist for the master data type.


○ The master data type must have at least one attribute.○ Except for a virtual master data type, the master data type must have at least one key attribute.○ If a description attribute is assigned to an attribute of the master data type, the description attribute must

exist.○ For compound master data types

○ A compound master data type must have at least two components, and all components must be active.

○ Virtual master data types cannot be used as a component of a compound master data type.○ A compound master data type must have all the key attributes of the component master data types

must be set to key, and it mustn't have any additional key attributes.○ For reference master data types

○ A reference master data type must refer to an active master data type.○ Virtual master data types and reference master data types are not allowed to be used in a reference

master data type.○ A referenced attribute must be set for each attribute of the reference master data type.○ An attribute of a reference master data type must have the same data type as its referenced

attribute.○ A reference master data type must have exactly the same keys as the master data type it refers to.○ The length of an attribute of the reference master data type must be equal to or longer than its

reference master data type.○ For virtual master data types

○ A virtual master data type must have at least two referenced master data types, and all of them must be active.

○ Virtual master data types are not allowed to be used as a referenced master data type of a virtual master data type.

○ An attribute of a virtual master data type must have the same data type as its reference attribute.○ A virtual master data type must contain all attributes of the component master data types, and it

cannot contain any more attributes.○ The length of an attribute of the virtual master data type must be equal to or longer than its reference

master data type.○ In the join conditions, the data types of the attributes must match.○ The join conditions must form a chain.

○ For external master data types○ The external data source must exist.○ For each attribute of the external master data type, the referenced column of the external data

source must be set.○ The external master data type must have exactly the same keys as the external data source.○ The length of an attribute of the reference master data type must be equal to or longer than its

referenced column.● Checking the dependencies and connections of the master data type

○ It is not allowed to delete a master data type if it is used in a different master data type or in a planning area.

○ The key attributes of a compound master data type must not be selected for any planning area.● Checking the master data type against the already existing master data records

○ It is not allowed to add or remove components to a compound master data type if data already exists for the master data type.



○ If an additional attribute is set to key, the attribute cannot be empty in any of the master data records.○ If a key attribute is changed to a non-key attribute, the remaining key combination must have unique

values for all existing master data records.

Help for Error Analysis

Study the activation log to learn what made the activation fail. The messages you find in the log provide you with information about the errors. For certain messages, which originate from complex situations, you'll find additional information in the table below.

Table 83:

Message Text Reason and What to Do

Cannot lock attribute &1. Another activation may be running.

Try activating the master data type later.

Cannot lock master data type &1. Another activation may be running.

Try activating the master data type later.

Cannot add attribute &1 as key attribute. Data already exists for the master data type. The attribute contains empty values, so it cannot be a key attribute.

Attribute set &1 cannot be the key for master data type &2. Data already exists for the master data type. The attribute set you selected as the key contains not only unique values.

Cannot add attribute &1 and set it to required in one step. Add the attribute to the master data type as an optional attribute, and activate the master data type. In the next step, change the master data type by setting the attribute to required. Activate the master data type again.

Cannot set attribute &1 to required. Empty value exists for the attribute

Data already exists for the master data type. The attribute contains empty values, so it cannot be set to required.

14.5.3 Error: Ensure .... is included in the generated calculation graph.

E – Ensure that calculation 4 | TXXACTUALSQTY@REQEST is included in the generated calculation graph.

Analysis

The text “Ensure … is included in the calculation graph” indicates that the calculation graph is incomplete. The “calculation graph” shows all the calculations for a key figure. To view the calculation graph for a key figure, select


the key figure and click the Formula/Graph View button. In the graph, the calculation nodes are colored blue and the stored inputs are colored green. Every key figure calculation graph must end with a stored key figure (marked in green):

Figure 11: Calculation Graph

In the calculation graph shown above, TXXCONSENSUDEMANDQTY ends with a stored key figure TXXSALESFORECASTQTY and TXXCONSENSUDEMANDQTY. Note that the above calculation is an example of defaulting.

The original error E – Ensure that calculation 4 | TXXACTUALSQTY@REQEST is included in the generated calculation graph. Indicates that TXXACTUALSQTY does not result in a stored key figure. That is, TXXACTUALSQTY is a stored key figure, but is not marked as such in the Input Key Figures dialog.



Figure 12: Key Figure Not Selected as Stored Value

Solution

Select Stored Value for the input key figure and activate the planning area.

14.5.4 Error: Check that key figure ID has a calculation at REQUEST Level

E – Check that key figure TXXINVENTORTARGETQTY has a calculation defined at the REQUEST level.

Analysis

No request level calculation exists for this key figure. When you look at the key figure definition, you see that no calculations have been defined.


Solution

Add a request level calculation to the key figure as follows:

1. Click Add Calculation (on the right of the screen above Calculation Definitions).2. Add an expression.3. Click Validate.4. Click Input Key Figures and make sure that TXXINVENTORYQTY is selected as a stored value.

14.5.5 Error: Expression is not valid

E – Expression is not valid.

Analysis

You might, for example, see a detailed error such as the following:

Exception raised from InternalError: dberror(PreparedStatement.execute): 2048 - column store error: fail to create scenario: [34011] Inconsistent calculation model;CalculationNode (9_53) -> attributes -> calculatedAttribute (CAPDEMANDUTILPCT) -> expression:Expression is not valid: Evaluator: syntax error in expression string;expected TK_RPAREN,parsing 'fixed(IF(ISNULL(“T10CAPASUPPLY”) OR “T10CAPASUPPLY”=0,0, “HCAPADEMAND”/“T10CAPASUPPLY, 12, 6)[here]”at ptime/query/plan_executor/trex_wrapper/trex_wrapper_body/trex_metadata.cc:1965 The above error text indicates that there is a syntax problem in the calculation expression and that the expression is invalid or incomplete. In this case a closing bracket “)” is missing.

Solution

Add the closing bracket (or other syntax element that is missing from your expression) and activate the planning area.

14.5.6 Errors relating to key figures with calculations at different planning levels

The following errors relate to key figures with calculations at different planning levels:

● Error: E - In calculation 16 | TXXDEPENDENTDEMANDQTY@TXXPERPRODLOCCUST, ensure that the granularity of the output key figure planning level is in sync with the input key figure(s) planning level

● Error: Union of attributes of all input planning levels should be equal to all attributes of output planning level



● Error: E In calculation 15 | TXXDEPENDENTDEMANDQTY@TXXPERPRODLOC, ensure that the output key figure planning level is a subset of the input key figure(s) planning level

Analysis

When a key figure contains calculations at different planning levels, the output planning level attributes must match the union of all the input planning levels. That is, the output planning level must have the same attributes as the combined attributes of the input planning levels.

Solution

Compare the attributes for the input and output planning levels. Add any missing attributes to the planning levels and activate the planning area.

14.6 Deleting Active Objects (Active Deletion)

SAP Integrated Business Planning allows you to delete active master data types, planning levels, key figures, and planning areas. You can also delete active time profiles, provided the time profile is not associated with any planning areas.

With active deletion, you change the status of objects to Pending Deletion. The objects are then deleted the next time they are activated.

When performing active deletion, observe the following sequence:

1. Delete key figures from the version and activate the planning area.2. Delete all key figures from any and all calculations, and delete all key figures that are assigned to any planning

level containing the attributes you want to delete.3. Activate the planning area.4. Delete all planning levels that contain the attributes that you want to delete, and activate the planning area.5. Delete all attributes of the master data type from the planning area, and activate the planning area.6. Delete the master data type and then activate the master data type.7. Delete the relevant time profiles and then activate the time profiles.

NoteVirtual and compound master data types: If you select the component or referenced master data types for deletion, the join conditions and all the attributes associated with those master data types are also marked Pending Deletion. You can independently mark for deletion the assigned attributes and join conditions associated with the master data types.


Steps

1. Select the specific object (for example, master data type or key figure) that you want to delete.2. Click the active deletion button.3. Click the Delete button.4. The Delete dialog appears.5. Click Yes. The status of the object changes to Pending Deletion.6. Select the object you want to delete.7. Click the Activate button.

Result

Once activation is complete, the object you deleted no longer appears in the list of objects.

14.7 Troubleshooting for Active Deletion

If you receive any of the error messages listed below during active deletion of objects, refer to the Solution column for information about how to proceed.

Deleting Active Master Data Types

Table 84:

Error Message Solution

The selected items are still assigned to one or more planning areas. Unassign the items first and then delete them.

Before deleting the active master data types, delete them from the planning areas with Active Deletion.

Deleting Master Data Types (and Attributes) from an Active Planning Area

Table 85:


The planning area attribute is used in the configuration of planning levels. The deletion may affect calculations. Do you want to continue?

Before removing the master data types (and associated attributes) from the planning area, remove the attributes from each active planning level to which they are assigned.



Deleting Attributes from an Active Planning Level

Table 86:


This planning level attribute is used in the configuration of key figures or attribute transformation. The deletion may affect calculations. Do you want to continue?

Before deleting the attribute (or planning level), remove all key figures from the planning level.

This planning level attribute is used in the configuration of key figures or attribute transformation. The deletion may affect calculations. You need to re-import the data for the affected key figures. Do you want to continue?

Check whether this action makes sense.

Deleting an Active Key Figure

Table 87:


Key Figure is being used in (key figure) (version) and cannot be deleted.

The key figure you are trying to delete is being used in an active version. Before you can delete the key figure, remove it from the version with Active Deletion.

Key Figure is being used in (key figure) and cannot be deleted. The key figure you are trying to delete is being used in the calculation of other key figures (as indicated in the Used in Key Figures field). Before you can delete the key figure, you must delete it from all the calculations it is being used in.


Active Deletion Sequence Error

Table 88:


I: Activation Running You have activated objects in the incorrect sequence. Proceed as follows (in the sequence given):

● Delete key figures from the version and activate the planning area.

● Delete all key figures from any and all calculations, and delete all key figures that are assigned to any planning level containing the attributes you want to delete.

● Activate the planning area.● Delete all planning levels that contain the attributes you

want to delete, and activate the planning area.● Delete all attributes of the master data type from the

planning area, and activate the planning area.● Delete the master data type and then activate the master

data type.



15 Copy Options for Planning Areas

SAP Integrated Business Planning offers you both simple and advanced copy options within the planning area. With the simple copy, master data types, time profiles, and attributes associated with a planning area are not copied. To copy these entities, you must use the advanced copy function.

You cannot use the copy functions to copy favorites, templates, and user-defined filters.

To access the copy functions, select Define Planning Area on the initial screen of the Configuration app, or choose Planning Area and Details in the top menu, select your planning area, choose Copy and then Simple Copy or Advanced Copy as required.

The Overview of Simple Copy and Advanced Copy table contains a high-level overview of the configuration objects that you can copy using simple copy and advanced copy. For more information, see Simple Copy [page 154] and Advanced Copy [page 155] respectively.

Table 89: Overview of Simple Copy and Advanced Copy

Simple Copy Advanced Copy of SAP Sample Planning Area

Advanced Copy of Own Planning Area

Planning area details Yes Yes Yes

Planning area–time profile assignments Yes Yes Yes

Time profile used in the planning area No Yes Yes

Planning area–attribute assignments Yes Yes Yes

Attributes used in the planning area No Yes No

Master data type–attribute assignments No Yes Yes

Master data types used in the planning area No Yes Yes

Planning levels used in the planning area Yes Yes Yes

Planning level–attribute assignments Yes Yes Yes

Key figures used in the planning area Yes Yes Yes

Attributes as key figures used in the planning area Yes Yes Yes

Versions and scenarios used in the planning area Yes Yes Yes

Snapshots used in the planning area Yes Yes Yes

Planning area–planning operator assignments Yes Yes Yes

Forecast models Yes Yes Yes

Model Configuration GuideCopy Options for Planning Areas C U S T O M E R 153

Simple Copy Advanced Copy of SAP Sample Planning Area

Advanced Copy of Own Planning Area

Planning profiles Yes Yes Yes

15.1 Simple Copy

The simple copy allows you to create a new planning area by copying the following configuration from the source planning area:

● Planning area details● Planning area–time profile assignments● Planning area–attribute assignments● Planning levels used in the planning area● Planning level–attribute assignments● Attributes as key figures used in the planning area● Key figures used in the planning area● Versions and scenarios used in the planning area● Snapshots used in the planning area● Planning area–planning operator assignments● Forecast models● Planning profiles

Master data types, time profiles, and attributes associated with the planning area are not copied.

Simple copy also enables you to copy your planning area into an existing planning area by copying the configuration listed above in the following ways:

● You can use Merge to keep all the configuration in the target planning area and add everything new from the source planning area.

● You can use Overwrite Existing (Replace) to create an exact copy of the source planning area into the existing target planning area, that is, delete configuration in the target planning area that is not included in the source planning area, add new configuration from the source planning area and update existing configuration in the target planning area based on the source planning area.

NoteIf you copy attributes as key figures using Overwrite Existing (Replace), the result is the same as if you had used Merge. You have to manually remove unused configuration for attributes as key figures.

Changes take effect when you activate the target planning area.


Copy Options for Planning Areas

15.2 Advanced Copy

The advanced copy allows you to copy master data types, time profiles, and attributes associated with a planning area. You can use advanced copy to copy both your own content and SAP sample planning areas to your work area.

NoteIf you change an attribute that you copied from an SAP sample planning area using advanced copy and then copy the same SAP sample planning area with advanced copy again, the changes you made to the attribute will be overwritten. However, if you have extended the length of an attribute that originates from an SAP sample planning area, a subsequent advanced copy of the same SAP sample planning area will not overwrite the changed length. For more information see Extending the Length of an Attribute [page 192].

The advanced copy enables you to create a new planning area by copying the following configuration from the source planning area:

● Planning area details● Time profile used in the planning area● Attributes used in the planning area

NoteWhen you copy an SAP sample planning area using advanced copy, the attributes are copied with the ID that they have in the source planning area. When you copy a planning area that you created using advanced copy, the attributes are not copied.

● Master data types used in the planning area● Planning levels used in the planning area● Planning level–attribute assignments● Attributes as key figures used in the planning area● Key figures used in the planning area● Versions and scenarios used in the planning area● Snapshots used in the planning area● Planning area–planning operator assignments● Forecast models● Planning profiles

When you copy a planning area using advanced copy, you have the following options for copying the master data types in the planning area:

● Copy the source master data type “as is”

NoteThis option is only available when copying an SAP sample planning area.

● Replace the prefix in the master data type name● Add a prefix to the master data type name● Remove the prefix from the master data type name


Advanced copy also enables you to copy configuration associated with a planning area into an existing planning area. You use advanced copy with replace to create an exact copy of the source planning area in an existing target planning area, that is, delete configuration in the target planning area that is not included in the source planning area, add new configuration from the source planning area, and update existing configuration in the target planning area based on the source planning area. When using advanced copy with replace, both the source and target planning areas can be active or inactive.

The partial copy option is available for the unified planning area SAPIBP1. You can use the partial copy option to create a subset of the key figures available in the unified planning area by applying one or a combination of the following filters:

● Supply Chain Control Tower● Demand planning● Demand sensing● Inventory optimization● Sales and operations planning and supply planning

NoteThe content of the filters is predefined and cannot be changed.

To use the partial copy option, select Planning Area and Details in the Configuration app, choose the SAPIBP1 planning area in the Display SAP Sample view, select the Advanced Copy option and choose a filter for partial copy.

NoteAfter you created a partial copy of the unified planning area that does not include supply planning, that is, you did not apply the sales and operations planning and supply planning filter, make sure you deselect the Supply Planning Enabled checkbox on the Planning Area and Details screen.

15.3 Copying an SAP Sample Planning Area with Advanced Copy

Procedure

1. On the initial screen of the Configuration app, select Define Planning Area or choose Planning Area and Details in the top menu.

2. From the dropdown list in the top right corner of the screen choose Display SAP Sample.3. Select the sample planning area you want to copy and choose Copy.

For example, copy the SAP6 sample planning area.

4. Select Advanced Copy and create a new planning area.5. Enter an ID for the target planning area.


Copy Options for Planning Areas

Use an ID that is up to 10 characters long, contains alphanumeric characters, and starts with an alphabetic character, for example, ABCMODEL2. When copying an SAP sample planning area, you can keep the ID of the source planning area, or you can use a different ID of your choice.

6. Enter an ID for the new time profile.

Use an ID that is up to nine characters long and only contains numeric characters.

NoteMake sure that the ID you select for the time profile does not already exist.

7. Enter the source prefix of the master data types.

For example, when you copy the SAP6 sample planning area, you enter IBP as source prefix.

You can leave the source prefix field empty if you would like to add another prefix in front of the one that already exists.

8. Enter a target prefix for the master data types.

A prefix must only contain alphanumeric characters and can be up to three characters long. The prefix must start with an alphabetic character.

Depending on what the desired end result is, you have the following options when specifying the source and target prefixes:○ To copy the master data types “as is”, leave both the source prefix and the target prefix empty.

NoteThis option is only available when copying SAP sample planning areas.

○ To replace the master data type prefix, enter the source prefix and a target prefix.○ To add another prefix to the master data type, leave the source prefix empty and enter a target prefix.○ To remove the master data type prefix, enter the source prefix and leave the target prefix empty.

9. Copy the planning area.

Results

A new planning area and time profile with the IDs you selected are created in your work area. The new planning area contains master data types with names corresponding to your selection. The names of the attributes, key figures, and planning levels remain unchanged.


16 Transporting Model Entities

Prerequisites

Transporting model entities is based on the Change and Transport System in Application Server ABAP. Make sure that the following settings are made in your systems:

1. You have set up a transport route between the two SAP Integrated Business Planning systems involved.2. Both in the source and the target systems, check, and if required, change the values of the ATTRIBUTES and

TARGET_GROUP parameters of the TRANSPORT parameter group. To do so, launch the Configuration app by clicking the corresponding tile on the launchpad, and choose Manage Global Configurations.○ TARGET_GROUP

Defines the transport layer. The default value is /IBP_DMT/. In case you use a different transport layer, enter it as the value for the TARGET_GROUP parameter.

○ ATTRIBUTESTransport requests may require one or more attributes, depending on the setup of your system.Define the attribute in the source system by entering a value for the ATTRIBUTES parameter. Use the following syntax: <attribute1>="<value1>";<attribute2>="<value2>". The default value of this parameter is ADD-ON=”SCMIBP”.

Transportable Model Entities

You can transport the following model entities:

● A complete planning model (a planning area with all its dependent entities):○ Planning area○ Attributes○ Master data types○ Time profiles○ Planning levels○ Key figure definitions○ Planning versions○ Planning operators

● A master data type with its attributes● A forecast model● A visibility filter


Transporting Model Entities

16.1 Exporting a Model Entity from the Source System

Prerequisites

You have been assigned the required authorization for creating, releasing, locking, and editing transport requests and tasks.

The planning model and the master data type that you want to transport must be active. There is no such requirement for forecast models, and for visibility filters.

Steps

1. Log on to SAP Integrated Business Planning in the source system.2. Launch the Transport Model Entities app by clicking the corresponding tile on the launchpad.3. Select the model entity you want to transport. If you want to transport a complete planning model, you select

it by selecting the planning area.4. Choose Export.

The system creates and releases a transport request that contains the entity you selected, and, if applicable, the dependent entities of that entity. For example, if you select a master data type, its attributes are also included in the transport request.Once a transport request has been created, you can check the export information, including the logs, by choosing the Exports icon.In case errors occurred before or during the creation of the transport request, the system displays an error message, and does not create the transport request.

16.2 Importing a Model Entity into the Target System

Steps

1. The import of the transport request takes place according to the configuration of your system (automatically or manually, using the Change and Transport System of the Application Server ABAP)

2. To check the status of the import, log on to the launchpad of the target SAP Integrated Business Planning system

3. Launch the Transport Model Entities app. Look for the model entity you previously exported from the source system. Select the entity type, then the model entity, then choose the Imports icon to display the list of previous imports. You can also display the log information for the completed imports.

4. After a successful import, activate the planning area.

Model Configuration GuideTransporting Model Entities C U S T O M E R 159

16.3 Best Practices for Transporting Planning Models

RecommendationSAP recommends the following approach for setting up planning areas and moving them from the test system to the production system.

Carry out configuration tasks and user testing in the test system. For these activities, you require at least two planning areas in the test system:

● Configuration planning area for ongoing configuration work● Consolidation planning area for consolidating the configuration changes and for initial integration and unit

testing (which is typically performed by consultants and expert business users)

Figure 13: Planning Areas in the Test System

Provided that no major changes are expected to the master data structure, these planning areas can share master data types.

The consolidation planning area typically has a smaller dataset than its counterpart in the production system. Nonetheless, the test dataset must be representative of actual production data. However, the consolidation planning area can contain a copy of the full production system dataset. Whether the consolidation planning area has a full or reduced dataset depends on the size of the test system and on customer requirements. Consolidation of changes from the configuration planning area to the consolidation planning area is done in the Configuration app, on the Planning Area and Details screen, by selecting Copy Select Existing Overwrite Existing (Replace) .



Once you have completed configuration and/or user testing, you can export the consolidation planning area using the Transport Model Entities app.

The exported planning area can then be imported into production system using the steps outlined above.

CautionEach time a planning area is exported, the entire planning area and all related configuration are transported.

SAP recommends that you do regular transports each time you change and activate a planning area. Do not collect changes of different kinds in one transport request – for example, removing an attribute from a master data type, changes in key figure definitions, and adding attributes to a master data type. Having different kinds of changes in one transport request may lead to issues in activation in the target system, because certain changes must be executed in a given sequence.

Make sure that in the target system you perform the activation of the model entities in the following order:

1. Time profiles2. Master data types3. Planning areas

In projects that require a lot of integration work (for example, development in SAP HANA Cloud Platform, integration service), you have to keep data sets for application consultants and integration consultants separate. In such cases, SAP recommends that you to use an additional, independent data integration planning area for data integration activities. Ideally, this planning area should have its own master data types. With this approach, you can proceed with development and testing of integration content without interfering with configuration tasks. Note that if you use a separate data integration planning area in the integration service, you will require additional effort to change the test integration tasks to the final tasks.


Figure 14: Best Practices: Transporting Planning Areas to Production System

Related Information

Activating Planning Models [page 128]

16.4 Model Transport in a 2-Phase Configuration Project

As most SAP Integrated Business Planning projects are implemented in a phased approach, users may need to make configuration changes for the next phase of the configuration project while, at the same time, they are making minor maintenance-related configuration changes in the production system that is actively used by business users.

The following table gives an overview of the planning areas involved (and the names used for them in the subsequent text and graphics).



Table 90:

Planning Area Planning Phase Example (used in text and graphics)

Active 1 P1_ACTIVE

Configuration 1 P1_CONFIG

Data Integration 1 P1_DATA_INTEGRATION

Data Integration 2 P2_DATA_INTEGRATION

Configuration 2 P2_CONFIG

Consolidation 2 P2_CONSOLIDATION

Transporting the Active Planning Area When Phase 1 is Complete

When phase 1 is complete, transport the active planning area (P1_ACTIVE) to the production system.

Figure 15: Transporting Active Planning Area (Phase 1) to Production System


Preparing the Test System for Phase 2

1. Using Advanced Copy, copy the active planning area from phase 1 (P1_ACTIVE) to the configuration planning area for phase 2 (P2_CONFIG). This creates the configuration planning area for phase 2 and all the related master data objects.

2. Using Copy-Replace, copy the configuration planning area for phase 2 (P2_CONFIG) to the consolidation planning area for phase 2 (P2_CONSOLIDATION).

3. Optional step: If you require a data integration planning area (for example, for activities in SAP HANA Cloud Platform, integration service), copy the phase 1 data integration planning area (P1_DATA_INTEGRATION) to the phase 2 data integration planning area (P2_DATA_INTEGRATION) using Advanced Copy.

Making Configuration Changes in Project Phase 2

1. Make the configuration changes necessary for phase 2 of the project in the configuration planning area for phase 2 (P2_CONFIG). Changes could include creating additional attributes, master data types, or key figures.

2. Once configuration is complete and has been validated, using Copy-Replace, merge the changes into the consolidation planning area for phase 2 (P2_CONSOLIDATION).

Figure 16: Preparing the Test System for Phase 2



Figure 17: Making Configuration Changes for Phase 2

Making Interim Changes in the Production Instance

1. Make any minor configuration changes needed for the production instance in the configuration planning area for phase 1 (P1_CONFIG).

2. Using Copy-Replace, merge these changes into the active planning area (P1_ACTIVE).3. Using the Transport Model Entities app, transport the active planning area (P1_ACTIVE) to the production

system.4. Mandatory step: Repeat the configuration changes made in the phase 1 active planning area (P1_ACTIVE)

manually in the phase 2 configuration planning area (P2_CONFIG) to keep the 2 planning areas in sync.

Transporting Phase 1 Active Planning Area to Production System

Using the Transport Model Entities app, transport the active planning area from phase 1 (P1_ACTIVE) to the production system.


Figure 18: Transporting the Active Planning Area to the Production System

Merging Phase 2 Master Data Changes to Production Planning Area

When the consolidation planning area for phase 2 is ready, proceed as follows to move this planning area to the production system:

1. Using Copy-Replace, merge the master data from the configuration planning area for phase 2 into the configuration planning area for phase 1. This does the following in the target planning area:○ Adds any new attributes to existing master data types○ Creates new master data types



Figure 19: Merging Master Data from P2_CONFIG into P1_CONFIG2. Delete the configuration planning area for phase 1.3. Using Advanced Copy, copy the configuration planning area for phase 2 to the configuration planning area for

phase 1. This adds new planning levels, key figures, and scenarios.4. Activate the configuration planning area for phase 1.5. Using Copy-Replace, copy the phase 1 configuration planning area to the active planning area for phase 1.6. Activate the planning area.7. Using the Transport Model Entities app, transport the planning area to the production system.


Figure 20: Copying Planning Areas



17 Emergency Access to Production System

Manual changes to configuration in a production system and often even in a test system should be avoided to ensure the integrity of the planning area being used productively or tested. However, in exceptional circumstances you may need to configure and activate planning models in a production system. For this purpose, a special business role can be assigned to your business user that provides you with temporary access to the production system.

Note● SAP recommends that emergency access is used only after it has been decided that the system is in an

exception state (also known as a firecall state).● Most configuration activities require model activation and may have an impact on runtime user interfaces

or data integration, for example.

For information on how the emergency access is provided, see the application help at http://help.sap.com/ibp1611 under Identity and Access Management Allow Emergency Access to Production System .

Model Configuration GuideEmergency Access to Production System C U S T O M E R 169

http://help.sap.com/disclaimer?site=http://help.sap.com/ibp1611

http://help.sap.com/disclaimer?site=http://help.sap.com/ibp1611

18 Miscellaneous Settings

18.1 Reason Codes

Reason codes refer to a set of tags that you can use to keep track of the decisions and changes made throughout the planning process in the Excel Add-In. A user can enter a reason code when saving data in Microsoft Excel using the Save Data button.

You can create your own reason codes. Some useful reason codes are provided with SAP Integrated Business Planning.

18.1.1 Creating Reason Codes

Context

You can create reason codes in the Configuration app or in the Reason Codes app. You can view and edit the reason codes in your system in either app, regardless of where you created them.

Procedure

1. Open the Reason Codes app.2. Create a new reason code.3. In the popup window provide the details for the reason code.4. Save your changes.

18.2 Managing Global Configurations

Global configuration lets you maintain application-level defaults.


Miscellaneous Settings

The global configuration parameters are organized in parameter groups. The following groups are supplied by SAP:

Table 91:

Group Area Defaults Relate To

ANALYTICS Analytics: charts and dashboards

COLLABORATION SAP Jam integration

FORECAST Statistical forecasting

HOME_PAGE Dashboards

INTEGRATION Data integration

MASTER_DATA_OP Master data

PLAN_VIEW Microsoft Excel planning views

PLCNTRL Planning controller for simulations

SCENARIO Versions

TRANSPORT Transport request parameters

RecommendationWe recommend that you maintain the following defaults when you install your system:

● Planning area for data integration and dashboards● Time profile for data integration

18.2.1 Creating a Global Configuration Parameter

Context

To create a new global configuration parameter, choose Manage Global Configurations on the initial screen of the Configuration app.

Steps

1. To create a global configuration parameter, click New.

Model Configuration GuideMiscellaneous Settings C U S T O M E R 171

2. Select a parameter group and a parameter name and enter a value of your choice. The following example shows sample entries for a global configuration:

Example

Table 92:

Parameter Group HOME_PAGE

Parameter Name DEFAULT_PLAN_AREA

Value 500


Related Information

Global Configuration Parameters [page 172]

18.2.2 Global Configuration Parameters

On the Manage Global Configurations screen, you set values for the parameters that control various features of the IBP applications.

NoteThe screen displays all parameters that are available in the system, including internal technical parameters. Please note that only the parameters that are listed in the following table are available for external use (by customers).

Table 93:

Parameter Group Parameter Name Default Value Parameter Description

ANALYTICS CHARTS_PUBLIC TRUE All charts are public by default. If set to FALSE, charts are private.

ANALYTICS DASHBOARDS_PUBLIC TRUE All dashboards are public by default. If set to FALSE, dashboards are private.




ANALYTICS MAX_ATTR_VALUES 2000 Represents the maximum number of records displayed in the drill-down lists for alerts. For example, if you select a time period on a daily level, you get 365 lines for each year of data.

ANALYTICS MAX_RECORDS 2000 Limits the number of records retracted from the SAP HANA database when alerts generate an SQL string. Unlike the parameter MAX_ALERT_PER_SUBSCRIPTION, this parameter controls the number of records coming from the SAP HANA DBs and not just the records displayed on the UI.

ANALYTICS MAX_ALERTS_PER_SUBSCRIPTION

100 Limits the number of alerts that are displayed in the custom alerts monitor.

If an alert is not defined correctly, it could generate a large number of alerts (one subscription can lead to millions of alerts). This parameter limits the number of alerts retrieved for each subscription and therefore prevents performance problems. This parameter does not limit the number of records retracted from SAP HANA.

ANALYTICS SNOOZE_NUM_OF_DAYS Defines the number of days an alert is snoozed if you select the option Snooze Indefinitely.

COLLABORATION COLLABORATION_ENABLED False Flag that enables/disables collaboration in Sales and Operations Planning.



FORECAST FORECAST_ESCAPENULL 1 Adds and initializes the value of the forecast input key figure to a small value when historical data is missing for some periods. Setting this value to 0 will not have this effect.

FORECAST PARAM_OPTIMIZATION_MAX_TIME

10 Time limit for the optimization process performed when the automated exponential smoothing algorithm is selected in a forecast model. The time unit is second and the value should be larger than zero.

FORECAST HISTORY_MIN_VALUE 0.001 You have to enter a value for HISTORY_MIN_VALUE if the history data is NULL, that is, unavailable. If no entry is made for this parameter, the default 0.001 is used. This parameter is used only if FORECAST_ESCAPENULL has a value other than “0”. You have to enter this parameter as a numerical value with integer or decimal format.

FORECAST MIN_FORECAST -9999999 If you are using the double or triple exponential smoothing method, forecast values may sometimes be negative. If required, you can prevent such negative values from being returned by setting this parameter, for example, to “0”. Any negative values are then changed to the value entered for this parameter. If you do not specify this parameter, negative values are returned, the lowest possible value being the default value -9999999.




FORECAST FCSTASSIGN_SUPPR_RC_COMMENT

None Controls whether a user can select a reason code and make a comment when changing a forecast model assignment. If the value is TRUE, the list of available reason codes and the comment field are not displayed on the UI.

FORECAST CREATE_MISSING_PLANNING_OBJECT

X – Enabled During the background forecasting it can happen that a planning object that has sales history is not yet created on the level where the forecast is stored. In such a case the missing planning object is created automatically on the base planning level of the output key figure.

FORECAST FCSTASSIGNMENT_LOG_MAX_TIME

10 During the maintenance of forecast model assignments the changes are recorded (who changed the assigned forecast model, old value, new value, reason code, comment). The parameter describes how long the changes are kept for traceability purposes. It takes an integer value that describes the number of years that the changes are kept.

FORECAST DETAILED_LOG NULL During the background forecasting a detailed log can be generated showing additional messages for each planning object that was processed. To enable it, set the parameter to X.



HOME_PAGE DEFAULT_PLAN_AREA NULL Indicates the default planning area to view on the SAP Integrated Business Planning dashboards. This parameter also represents the default planning area for the user interface of SAP Integrated Business Planning add-in for Microsoft Excel.

INTEGRATION ENABLE_SNAPSHOT_KFS NULL By default, snapshot key figures of type Original are not available for upload using data integration. Using this parameter, you can determine whether values for snapshot key figures can be maintained in a given planning area using the data integration process.

You enter the parameter value as a list of planning areas, separated by commas. For example, if the parameter value is PLAN_AREA1, PLAN_AREA2, PLAN_AREA3, then the snapshot key figures are available for upload using data integration in the planning areas PLAN_AREA1, PLAN_AREA2, and PLAN_AREA3.

INTEGRATION KF_UPLOAD_EXT_AT_BASE_LEVEL_ONLY

Controls whether you can upload key figure data at an aggregated time level from an external source, such as SAP HANA Cloud Platform, integration service. Enter x or X as the value to restrict the upload of key figure data to uploading at the base planning level only, and with that, disable time disaggregation.




INTEGRATION KF_UPLOAD_INT_AT_BASE_LEVEL_ONLY

Controls whether you can upload key figure data at an aggregated time level in the Data Integration app. Enter x or X as the value to restrict the upload of key figure data to uploading at the base planning level only, and with that, disable time disaggregation.

INTEGRATION LOGGING DEBUG Controls whether data integration runs in debug or non-debug mode. By default, data integration runs in non-debug mode. While troubleshooting data integration related issues, run data integration in debug mode where the system will do some extra logging that can be helpful. Typically, data integration runs in non-debug mode, which means there should be no configuration entry maintained for INTEGRATION parameter LOGGING. When you want to run data integration in debug mode, maintain the following entry:

● Parameter Group: Integration

● Parameter: LOGGING● Parameter Value: Debug

This parameter is only used by SAP support while troubleshooting data integration issues. After completing the troubleshooting process, SAP support should remove this configuration setting.



INTEGRATION STAGCLEANUP 7 Controls the duration after which data import batches will be purged from your system. Your system comes with a default duration of 7 days. You can overwrite the default by creating the following entry in Global Configuration:

● Parameter Group: Integration

● Parameter: STAGCLEANUP

● Parameter Value: 3The parameter value is always a positive integer. After data import batches are purged, they are permanently removed from your system. Afterwards, data import reporting is not available for the purged batches. Production systems typically set this to 2 days. If you are importing very large volumes of data every day, then you should not set this duration to more than 1 day, otherwise you will accumulate data in your system. After a data import batch has processed, it has fulfilled its purpose. The only reason you may want to retain that data for 1 or 2 days is purely for data import reporting purposes. This data does not participate in any other system function; it just occupies space. The sooner you purge it, the better it is for your system.




INTEGRATION JOB_THREAD_COUNT 1 Controls how many import jobs or batches can be processed concurrently. You can override the default value of 1 with a value that fits your requirements and then test it to verify that your imports run smoothly.

INTEGRATION SPACE_TO_NULL Attribute values consisting of SPACE characters only are not allowed during master data import. To indicate an empty (initial) value for an attribute, NULL must be used instead. If you enter the value 1 for this parameter, the system automatically converts the value of an NVARCHAR attribute that consist of spaces only to the value NULL.

MASTER_DATA_OP MAX_BATCH_SIZE 10,000 The maximum number of records that a user can download or upload using the mass management of master data function in the IBP Excel add-in.

MASTER_DATA_OP SORT_REQFIELD_FIRST YES Controls the order of the columns in the mass management of master data in the IBP Excel add-in. If the value of the parameter is YES, the columns of the required attributes follow the columns of the key attributes. Otherwise, the system puts the columns of the key attributes first, and displays the columns of the remaining attributes in alphabetical order.



MODEL_CONFIGURATION COPY_PLANNING_PROFILE TRUE Controls whether planning profiles are copied when you copy a planning area using simple or advanced copy. The default setting is true, that is, planning profiles are copied. If you don't want to copy the planning profiles, change the value to FALSE.

PLAN_VIEW ALLOW_SAVE_DURING_COPY YES Allows saving data in Excel during the run of a copy operator for same planning area.

PLAN_VIEW ALLOW_SAVE_DURING_DATA_LOAD

YES Allows the key figure values from a planning view in Excel to be saved while a data integration job is running for the same planning area.

PLAN_VIEW ALLOW_SAVE_DURING_SNAPSHOT

YES Allows saving data in Excel during the run of a snapshot for the same planning area.

PLAN_VIEW ALLOW_SAVE_DURING_VERSION_COPY

YES Allows saving data in Excel during the run of a version copy for the same planning area.

PLAN_VIEW DEL_COMB_KF_CHECK_FOR_NULL

YES Controls whether choosing Delete Planning Object in the IBP Excel add-in deletes only those planning objects where all the cells have NULL key figure values, or deletes those planning objects as well that have key figure values.

PLAN_VIEW HOME_PAGE /sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html

This parameter indicates the default path for constructing the SAP Fiori Launchpad.




PLAN_VIEW MAX_DIM_MEMBERS 10,000 You can use this global configuration parameter to activate the dynamic selection of master data attribute values. If the number of values for an attribute is larger than the value you set for this parameter, the IBP Excel add-in does not display all of the values in filtering and planning view definition. Users are notified of this fact and can display all of the values by explicitly searching for them.

PLAN_VIEW MAX_RESULT_ROW_SIZE 2000 The global configuration parameter MAX_RESULT_ROW_SIZE and the number of time periods selected in the planning view are used to restrict the maximum number of cells that can be retrieved from the database for a key figure. The default value for the parameter MAX_RESULT_ROW_SIZE is 2000. Maximum number of cells retrieved for each key figure = MAX_RESULT_ROW_SIZE * Number of time periods. The data retrieved for all key figures at chosen planning levels is then plotted in the planning view according to the selected layout. If the results are restricted and the last row is incomplete, then the last row will not be displayed in the planning view.

PLAN_VIEW MINIMUM_ADDIN_VERSION If you provide a version here, then, upon logon to SAP Integrated Business Planning in the IBP Excel add-in, the system checks the version of the IBP Excel add-in. In case the version is lower than the one defined in the parameter, the system displays a warning message.



PLAN_VIEW LEANQUERY YES Checks whether the response payload of the IBP Excel add-in query service is to be returned in a slim format, to improve performance, particularly if the network is slow.

PLAN_VIEW SUPPRESS_RC_COMMENT X Having an entry with this parameter (regardless of the value) suppresses the dialog where the user is asked to provide a reason code or comment, and where they can share the changes on SAP Jam. Applying this parameter suppresses the dialog for reason codes, comments, and sharing throughout the SAP Integrated Business Planning (such as when saving data of a planning view, or changing a master data).

To re-enable the dialog for reason codes and comments, delete the entry for this parameter.

PLAN_VIEW VALID_NULL_VALUES_NON_ROOT_ATTR

Yes Determines, whether lines containing null values for a non-root attribute should be displayed in the planning view or not. The default behavior is to display the lines containing null values. If you set the global configuration parameter VALID_NULL_VALUES_NON_ROOT_ATTR to “NO”, and you have selected a non-root attribute as part of the characteristic value combination of a key figure, then lines, based on null values for this non-root attribute will not be displayed.




PLAN_VIEW PV_COUNT_MAX 5 The maximum number of open Microsoft Excel workbooks that contain planning views.

PLAN_VIEW SESSION_PRELOAD_CS 5 The number of calculation scenarios created in advance during session preload in Excel planning. It should be equal to the number of versions (including base version) times the number of scenarios (including baseline) which are typically selected in a planning view, so that the loading time of the planning view is reduced. Each combination of version and scenario results in a separate calculation scenario.

PLAN_VIEW SESSION_PRELOADCS_WAIT 30 Time in seconds the Excel query waits for the session preload to finish before creating calculation scenarios on its own. It should be at least equal to the loading time of a template which requires as many calculation scenarios as configured with parameter SESSION_PRELOAD_CS.

PLAN_VIEW SHARE_WITH_NONE FIRST Controls the entries the user sees in the field Share With when saving changes in the SAP Integrated Business Planning add-in for Microsoft Excel. The following values are available:

● FIRST: (None) is displayed as the first entry of the list

● LAST: (None) is displayed as the last entry of the list

● NO: (None) is not displayed at all



PLAN_VIEW ACTIVATE_VBA_HOOKS Allows you to enable your own Visual Basic scripts that run in the following instances:

● Before simulation● Before creating a simula

tion● Before saving data● After using the refresh

button

PLCNTRL MAX_FILTER_VALUES 200 The maximum number of filters for a planning view. For example, for PRDID you could set the filters Product 01 and Product 02. We recommend that you don't exceed the default value of 200. If you need more, you could use other filter criteria, for example, for PRDID you could use Product Group.

PLCNTRL SCM_LOCAL_MODE Yes When set to NO, disables local mode for the supply planning (SCM) operator type to improve performance.

PLCNTRL SESSION_TIMEOUT 7200 The number of seconds before an SAP Integrated Business Planning session times out and requires you to log back in.

PROMOTION PROMO_COUNT_MAX 500 The maximum number of promotions that are loaded in the overview table.




RESPONSE ENG_DIAGNOSIS_LEVEL 0 The level of diagnostic information provided for a response planning run.

Values for this parameter are defined by the domain fixed values in DDIC; for example, they could be as follows:

● 0 - no diagnosis information

● 1 - trace and input data● 2 - trace, input and output

data

SOP OPT_DIAGNOSIS_LEVEL 0 The level of diagnostic information provided for an S&OP optimizer run.




data

After the S&OP optimizer has run, you can access and download the related diagnosis files using the Application Logs app. Search for the affected planning run and choose Application Log Details.



SOP PLNG_OPR_DIAGNOSIS_LEVEL

0 The level of diagnostic information provided when an S&OP planning operator is used.




data

After a an S&OP planning operator has run, you can access and download the related diagnosis files using the Application Logs app. Search for the affected planning run and choose Application Log Details.

SCENARIO SCN_COUNT_MAX 3 The maximum number of versions allowed in an SAP Integrated Business Planning system.

SYSTEM MAX_ACTLOG_ROWS 0 You can specify the maximum number of rows the system displays in the activation log header on the Planning Area and Details, Master Data Types, and Time Profiles screens. The default value is 0, meaning that the number of rows displayed is 19999. Specify an integer value greater than 0 to define the maximum number of rows. The smaller the number you specify, the less time it takes for the activation log to load.




SYSTEM MAXLOGROWS 10,000 Limits the number of logs that are displayed in the Application Logs app. If the maximum number of logs is exceeded, business logs are produced that inform the user of the limit having been exceeded.

TRACE TRACELEVEL E Controls the range of events to be included in the log during runtime.

18.3 Configuration History

You can download a history of changes made to the model configuration for a selected date range. You can also filter the download by planning area and user. The history captures changes to attributes, master data types, time profiles, and certain aspects of planning areas (that is, attributes, planning levels, key figures, and versions). The data is downloaded to a comma-separated values (CSV) file that shows all changes caused by a user inserting, updating, or deleting data.

Steps

To download the configuration history, go to Miscellaneous Settings and choose Configuration History Download. Enter your selection criteria and choose OK. The system downloads the data and you can save the file.

The information in the CSV file includes the following:

● User who made the change● Time of the change● Type of change (insert, update, or delete)

Note that for an update from the UI, the record on the database is deleted and then inserted. In this case, the file therefore contains one row with the action DELETE and one row with the action INSERT.

● Name of the table affected (for example, SOPDM_PLANLEVELATTR is the table that is affected by changes to planning level attributes).

● Change ID and change item IDFor changes on the UI that a user saves together (that is, by choosing Save once on the UI), the following applies:○ All changes share the same change ID in the history even if the changes are stored in different database

tables.○ For changes to the same database tables, the change item ID increases incrementally by 1 for each

change.


● The following fields for the attributes:○ ATTRIBUTE_ID: Contains a comma-separated list of all table column names affected by the change.○ ATTRIBUTE_OLD_VALUE: Contains a comma-separated list of old values from the table columns.○ ATTRIBUTE_NEW_VALUE: Contains a comma-separated list of new values from the table columns.

ExampleExample

You create a new key figure TOTALRECEIPTS. You enter the following values:

● Name: TOTALRECEIPTS● Description: TOTALRECEIPTS● Base Planning Level: PERPRODLOC● Aggregation Mode: Sum● Stored: Selected● Edit Allowed: Not Editable

You also enter a calculation definition.

All entries are saved together. Since you have created a new key figure, the relevant action shown in the table is INSERT, with entries for the database tables used for key figures, key figure texts, key figure calculations, and key figure calculation inputs.

The following is a simplified extract from the configuration history for the above example:

Table 94:

CHANGE_USER

CHANGE_ID

CHANGE_ITEM_ID

TABLENAME ACTION

ATTRIBUTE ATTRIBUTE_NEW_VALUE

MILLER 384 1 SOPDM_KEYFIGURE INSERT

LASTMODIFIEDDATE; CONV_KFID;

2015-05-18 14:20:57; NULL;

MILLER 384 1 SOPDM_KEYFIGURE_T INSERT

DESCR; KFNAME Total Receipts; Total Receipts;

MILLER 384 1 SOPCM_KEYFIGCALC INSERT

CODEID; CREATEDBY; CREATEDDATE;

NULL; MILLER; 2015-05-18 14:20:57

MILLER 384 1 SOPCM_KEYFIGCALC_INPUT

INSERT

CREATEDBY; CREATEDDATE;INPUTTYPE

MILLER; 2015-05-18 14:20:57; 0

Other fields in the configuration history include planning area, key figure ID, calculation ID, planning level, attribute ID, LCODE, scenario, and active status. In the above example, the following additional information would be provided:

● KEYFIGURE_ID: TOTALRECEIPTS● CALCULATION_ID: 209318● ACTIVE: I



19 Advanced Modeling Topics

19.1 Aggregation and Disaggregation of Data Across Different Time Levels

Several applications of SAP Integrated Business Planning, which work with different time profile levels and time horizons, may use the same planning area. With that, the values of the common key figures must be aggregated and disaggregated across different time levels.

This can be realized by a specific modeling concept, which is built on the modeling of time profile levels with multiple parents and that of intermediate levels without parents. If you apply the modeling concept described below (also referred to as week-to-months split after the specific case of the aggregation between weeks and months), you will be able to aggregate and disaggregate key figure values across different time levels.

The modeling concept consists of the following elements:

1. Definition of the period weighting factor attribute2. Definition of a time profile that also includes technical weeks as a time profile level3. Uploading time periods with their period weighting factor4. Assigning the period weighting factor to the relevant planning levels and key figures

NoteYou can apply this modeling concept for aggregation and disaggregation not only between weeks and months, but between custom overlapping periods.

To do so, use the custom (empty value) period type when defining the time profile. Pay special attention to the correct modeling of the parent-child relations between the time profile levels.

Defining the Period Weighting Factor Attribute

In the Configuration app, on the Attributes screen, define one or more attribute that represents the period weighting factor. Typically, the number of workdays or calendar days is used as the period weight.

Specify INTEGER as the data type of the attribute.

Defining a Time Profile

In the Configuration app, on the Time Profiles screen, define a time profile.

The time profile must include a time profile level that has the “technical week” period type. This time profile level must be the base level of the week and month time profile levels.

Model Configuration GuideAdvanced Modeling Topics C U S T O M E R 189

ExampleThe time profile can look like this:

Table 95:

Level Name Base Level Period Type

1 Daily Day

2 Weekly (technical) 1 Technical week

3 Weekly (calendar) 2 Week

4 Monthly 2 Month

5 Quarterly 4 Quarter

6 Yearly 5 Year

Figure 21: Example: Time Periods for a Time Profile with 6 Time Levels

Assign the attribute you defined for the period weighting factor to the technical week level of the time profile.


Advanced Modeling Topics

Uploading Time Periods with Their Period Weighting Factors

Use the Data Integration app to get a CSV file template for the time profile. Fill out the template with the data of the time periods, including the period weighting factors, then upload the file to create the time periods.

For more information, see the Data Integration chapter in the application help.

You can also use SAP Cloud Platform Integration for data services to upload the time periods.

NoteIf you apply the week-to-months split modeling concept, you have to use either the Data Integration app or SAP Cloud Platform Integration for data services to create the time periods. If you create the time periods by scheduling an application job to create them, they will lack the period weighting factors. This can result in inaccurate aggregation and disaggregation between different time levels.

Assigning the Period Weight Factor Attribute to the Relevant Planning Levels and Key Figures

If you want to read and write key figure values in both (calendar) weeks and months, select the technical week time profile level as the root in the base planning levels used in the given key figures. Also assign the period weight factor to the base planning level of the key figure. You do this on the Planning Levels screen in the Configuration app.

You must specify the period weight factor for each key figure whose values you would like to access in both weeks and months. To do this, go to the Key Figures screen in the Configuration app, and select an attribute for the period weight factor.

NoteYou can assign a period weight factor to a key figure only if the disaggregation mode of the key figure is either Equal or Proportional if aggregated value is not zero, otherwise, equal distribution.

Only those attributes can be assigned as period weight factors that are of the INTEGER data type, and have already been assigned to the time profile, and to the base planning level of the key figure.

Special Considerations

You can save forecast model assignments only if planning objects exist at the forecast level. If you store key figures at technical week level, but you want to run forecast at calendar week level, then you must have at least one stored key figure at calendar week level.

If you use the PERIOD_OFFSET parameter for operators of the COPY operator type that you run at technical week level, take it into consideration that periods have different lengths.


Related Information

Creating Attributes [page 17]Creating Time Profiles [page 37]Creating Planning Levels [page 54]Creating Key Figures [page 63]

19.2 Extending the Length of an Attribute

Context

If you extend the length of an attribute, you must make sure that all model entities that use the attribute are updated with the new length. You must activate the relevant master data types, time profiles, and planning areas again for the changes to take effect, to keep the database consistent, and to prevent runtime errors.

NoteIf you use an attribute, which is used in an SAP sample planning area, in any of your planning areas, and the length of this attribute has been changed in the SAP sample planning area, an advanced copy of the SAP sample planning area overwrites the attribute length in your planning areas. You must activate the time profiles, master data types, and planning areas that use this attribute again. After activation, the attribute will have the new length consistently for all model entities where it is used.

Procedure

1. In the Attributes app, change the length of the attribute.

Alternatively, you can use the Attributes screen in the Configuration app to change the length of an attribute.

NoteYou cannot change the length of an attribute if it is used as a referenced attribute in a reference master data type or in a virtual master data type.

To extend the length of the attribute, remove the master data type that uses this attribute from the reference master data type of virtual master data type. Make your changes, then add the master data type that you previously removed to the reference master data type or compound master data type again.

2. Find the time profiles, master data types, and planning areas that use the attribute you have changed.

To do this, click the numbers in the corresponding cells in the Attributes app, or on the Attributes screen in the Configuration app.

3. Activate the time profiles that use the attribute you have changed.



4. Activate the master data types that use the attribute you have changed.5. Activate the planning areas that use the attribute you have changed.

Related Information

Activating Time Profiles [page 138]Activating Master Data Types [page 139]Activating Planning Areas [page 140]Copy Options for Planning Models [page 153]

19.3 Example: Defining an Attribute as a Key Figure

Context

When the value of an attribute of a master data type remains the same over time (for example, the attribute Product Price of master data type Product), you can define the attribute as a key figure. When such an attribute is loaded as a key figure, it should have the same value for all time periods.

ExampleUnit Price is an attribute of the master data type CUSTOMERPRODUCT, that is, it has a single value for a unique customer and product combination (a planning object for a certain customer and a certain location). You can define this attribute as a key figure so that the same unit price value applies across all planning time periods that are valid for a given planning object.

To define an attribute as a key figure, choose Define Planning Area on the initial screen of the Configuration app or click Planning Area and Details in the top menu. The following example shows how to define the attribute Unit Price as a key figure.

Steps

The following procedure shows the entries for defining the attribute Unit Price as a key figure:

1. Change the table filter selection to Available Attributes.2. Select the attribute UNITPRICE and select the Key Figure checkbox.3. In the resulting dialog, choose the Planning Level (PERCUSTPROD).4. Click OK.5. To indicate the time period for which the attribute value is to be stored in the time series for the key figure,

enter values relative to the current period in the Period From and Period To fields. For example, if you enter -6 for Period From and 24 for Period To and you are storing values on a monthly basis, the attribute value is stored for 6 months before and 2 years after the current period.


NoteIf you make an entry in Period To and leave Period From empty, the attribute value will be stored for all past periods - coming from the time profile assigned to the planning area - up to the value entered for Period To in the future.

If you make an entry for Period From and leave Period To empty, the attribute value will be stored from the value you entered for Period From for all future periods determined by the time profile assigned.

If you enter 0 in the From Period or To Period fields, the system takes the current period for the From Period or To Period.

In the following example, month is used as the period in the base planning level of the attribute as key figure. The current period is October 2016. The time profile assigned to the planning area spans from January 2015 to December 2018.

Table 96:

Value Entered in Period From

Value Entered in Period To

Key Figure Values Stored From

Key Figure Values Stored Until

Comment

(empty) (empty) January 2015 December 2018 Key figure values are stored for the entire calendar.

For performance reasons, SAP recommends that you specify exact periods in the Period From and Period To fields.

0 (empty) October 2016 December 2018 Key figure values are stored from the current period to the last period.

-6 24 February 2016 October 2018 Key figure values are stored from the 6th period in the past to the 24th period in the future.

(empty) 24 January 2015 October 2018 Key figure values are stored from the 1st period of the time profile to the 24th period in the future.



RecommendationFor time-dependent attributes as key figures, SAP recommends that you use the Period From and Period To fields to specify the time period for which you want to store attribute values. If you leave these fields blank, the attribute value is stored in the database for all time periods, which can affect system performance.

6. Save your entries.7. To define the key figure properties for the attribute that you have defined as a key figure, navigate to Key

Figures in the Configuration app.8. Edit the following Key Figure Details, and save your entries:

Table 97:

Key Figure ID Name & Description

Base Plan Level

Aggr. Mode Disaggregation Mode* Stored

Editable Calculated

UNITPRICE Unit Price PERPRODCUST SUM Proportional if aggregated value is not zero; otherwise Copy Value To

Current and Future

No

19.4 Time-Independent Key Figures

Time-independent key figures are configured in a similar way to attributes as key figures, except that the key figure value is not dependent on time periods. An example of a time-independent key figure is the Unit of Measure Conversion Factor. Unlike an attribute as key figure, where an attribute value is copied to all time periods in the time series for the planning object, time-independent key figures have just one record in the time series for the planning object.

RecommendationThe unified planning area SAPIBP1 uses time-independent key figures. We recommend that you check it as a reference implementation that you can use to help you set up your own time-independent key figures.

You can load time-independent key figures only if they have been configured as attributes as key figures. You configure them in just the same way, except that the planning level contains no time periods, for example, the base planning level for Unit of Measure Conversion Factor is PRODUOMTO.

You can view and edit time-independent key figures in the IBP Excel add-in under Master Data Maintenance for the master data type they are based on. You cannot, however, view these key figures in the Excel planning views. If you want to be able to view them in Excel, you have to extend the configuration. For example, you have to enter expressions such as the following:

UOMCONVERSIONFACTOR@REQUEST=AVG(UOMCONVERSIONFACTOR@MTHPRODUOMTO)


UOMCONVERSIONFACTOR@MTHPRODUOMTO=UOMCONVERSIONFACTOR@PRODUOMTO(<input_key_figure@MTH>)

Note that the input key figure <input_key_figure@MTH> is not part of the expression but the input key figure of the calculation. This could be any key figure that is aggregated to monthly level and that exists for all months.

RecommendationWe recommend that you use time-independent key figures instead of attributes as key figures in cases where the key figure value does not vary over time and does not have to be maintained in Excel like a regular key figure. This type of key figure provides much better performance than an attribute as key figure, which stores the key figure value for all time periods.

CautionIf you decide to use time-dependent conversion key figures, please be aware that using such key figures can cause higher memory consumption, and have a detrimental impact on performance.

19.5 Example: Configuring Currency Conversion

Context

SAP Integrated Business Planning can convert currency on the fly, for example, when a user of the Microsoft Excel add-in or of Analytics selects Target Currency at runtime for a key figure such as Sales Forecast Revenue. Prerequisites for currency conversion are that exchange rates exist in the system and that a currency conversion calculation has been defined for the key figure involved.

The following example illustrates the configuration steps for currency conversion.

Steps

1. Define the attributes S2CURRID, S2CURRTOID, S2CURRDESCR, S2CURRTODESCR, S2EXCHGRATE.2. Under Master Data Types, create the following master data types:

1. A simple master data type for “Currency” (S2CURR)

Table 98: Basic Data of the S2CURR Simple Master Data Type

Field Label Entry/Selection

Name* Currency

Description Currency




Type Simple

Table 99:

Attributes Description Key Req.

S2CURRDESCR Currency Desc

S2CURRID Currency yes yes

2. A reference master data type for “Currency To” (S2CURRTO)

Table 100: Basic Data of the S2CURRTO Reference Master Data Type


Name* Currency To

Description Currency To

Type Reference

Referenced Master Data Type S2 Currency

Table 101:

Attributes Description Key Req. Ref. Attribute

S2CURRTODESCR Currency Desc S2CURRDESCR

S2CURRTOID Currency yes yes S2CURRID

3. A compound master data type for “Exchange Rates” (S2EXCHANGERATE)

Table 102: Basic Data of the S2EXCHANGERATE Compound Master Data Type


Name* Exchange Rate

Description Exchange Rate

Type Compound

Component Master Data Types S2CURR and S2CURRTO

Table 103:


S2CURR Currency yes yes



S2CURRTOID Currency To yes yes

S2EXCHANGERATE Exchange Rate

3. Under Planning Area and Details, assign the following to the planning area:○ The currency attributes (in the this example, S2CURRENCY and S2CURRENCYTO)○ The “Exchange Rate” attribute as key figure (S2EXCHANGERATE)

4. Under Planning Levels, create currency planning levels. Select the Conversion Source and Conversion Target.5. Under Key Figures, add the conversion expression to the target key figures for currency conversion. For

example, under key figure TARGETREV, you would enter S2EXCHANGERATE for Convert Using.

19.6 Example: Configuring Unit of Measure Conversion

Context

Model configuration for SAP Integrated Business Planning (IBP) supports unit of measure (UoM) conversion, that is, conversion of key figures from the base unit of measure to a target unit of measure using a configured conversion factor. The configuration steps necessary for unit of measure conversion are similar to those for currency conversion. However, there are some differences:

● Units of measure are not usually time-dependent.● Unit of measure is an attribute of a master data type such as Product.

The planning views and Analytics provide the user with the option to select the target unit of measure. The conversion is handled by SAP Integrated Business Planning.

The following example illustrates the configuration steps for unit of measure conversion:

Steps

1. Launch the Attributes app, or choose Manage Attributes on the initial screen of the Configuration app.Define the attributes S2UOMID, S2UOMDESCR, S2UOMTOID, S2UOMTODESCR, and S2UOMCONVFACTOR.

2. In the Configuration app, under Master Data Types, define the master data types S2UOMTO and S2UOMCONVERSION.

Table 104: Basic Data of the S2UOMTO Simple Master Data Type


Name* UoM To




Description Unit of Measure To

Type Simple

Table 105:


S2UOMTODESCR Uom To Description

S2UOMTOID Uom To yes yes

Table 106: Basic Data of the S2UOMCONVERSION Compound Master Data Type


Name* UoM Conversion

Description UoM Conversion

Type Compound

Component Master Data Types S2PRODUCT and S2UOMTO

Table 107:


S2PRDID Product yes yes

S2UOMCONVFACTOR Conversion factor

S2UOMTOID UoM To yes yes

3. Under Planning Areas and Details, assign the unit of measurement attributes to your planning area, and assign the attribute S2UOMCONVFACTOR as key figure.

4. Under Planning Levels, create unit of measure planning levels. Select the Conversion Source and Conversion Target.

5. Under Key Figures, add the conversion expression to quantity key figures for unit of measure conversion. For example, for the key figure TARGETQTY, you would enter S2UOMCONVFACTOR for Convert Using.


19.7 Example: Attribute Transformations

Attribute transformation transforms the value of an attribute based on a calculation expression. You can use attribute transformation to offset key figure values, for example.

Context

SAP Integrated Business Planning supports a special type of transformation that allows you to transform the value of an attribute based on a calculation expression.

Example● Time Period Offset: The attribute PERIODID is transformed with the value for the number of time periods

offset.● Alert Flag, where an attribute can be set to 1 when there is an alert on a key figure. This is used to filter for

alerts.

The calculation expressions in the attribute transformation can be simple as ATTR1 + ATTR2 or can include key figures or a combination of attributes and key figures. All attribute transformations require an input key figure that has the same planning level as the attribute.

To create an attribute transformation, navigate to Key Figures in the Configuration app and select the Attribute Transformation radio button.

The following example of attribute transformation shows how to offset Actuals Qty by 12 months.

Steps

1. Create a new planning level ACTUALSQTY@MTHPRODCUST. (From the time dimension, this planning level has only Month as a root attribute.)

2. Add a calculation that drops all the non-root time dimension attributes:ACTUALSQTY@MTHPRODCUST = SUM(ACTUALSQTY@MTHQTRYEARPRODCUST).

3. Add a calculation that offsets the actuals quantity by a lead time value of 12 periods (here 12 months):PERIODID0@MTHPRODCUST1 = PERIODID0 + 12 (The input key figure is ACTUALSQTY@MTHPRODCUST, that is, the output from step 2.)

4. Add a calculation that assigns the shifted key figure values from Actuals Quantity to Actuals Quantity 1 Year Offset:ACTUALSQTY1YROFFSET@MTHPRODCUST1 = ACTUALSQTY@MTHPRODCUST1

5. Add a calculation to reinclude the other key figure time dimensions. (The input key figures are ACTUALSQTY1YROFFSET@MTHQTRYEARPRODCUST and another key figure K3@MTHQTRYEARPRODCUST.):ACTUALSQTY1YROFFSET@MTHQTRYEARPRODCUST = ACTUALSQTY1YROFFSET@MTHPRODCUST1



NoteFor K3@MTHQTRYEARPRODCUST, you can use any key figure that satisfies the condition, that is, a key figure that has a planning level with at least Month, Quarter, and Year.

(For this calculation to work, K3@MTHQTRYEARPRODCUST must have some values in future shifted months.)6. Save the calculation.7. Activate your planning area.

Related Information

Creating Time Profiles [page 37]PERIODID and PERIODID(n) Attributes in Time Profile Levels [page 39]

19.8 Example: Weighted Average Calculation

Context

This example shows how to use request level calculations to achieve weighted averages.

This example for weighted average calculation is based on the calculation for consensus demand revenue:

Consensus Demand Revenue = Consensus Demand Qty * Unit Price

Weighted average calculation is an example of a calculation at request level. Unit Price is a weighted average of Revenue and Qty. Unit Price is both a stored and an editable key figure.


Figure 22: Weighted Average Calculation of Unit Price

Calculation of Sales Forecast Price

In this example, we use weighted average to calculate the sales forecast price. To do so, we define a new key figure, for example, SALESFORECASTPRICE (such as exists in the supplied model SAP2), which is a stored key figure and use a weighted average calculation at the request level.

Steps1. To change the calculation to a request level calculation, replace the calculation

SALESFORECASTPRICE@REQUEST with the following: IF(ISNULL("SALESFORECASTQTY@REQUEST") OR "SALESFORECASTQTY@REQUEST" = 0 , 0, "SALESFORECASTREV@REQUEST"/"SALESFORECASTQTY@REQUEST")

2. Validate the expression and save.

Calculation of Sales Forecast Revenue

Define a key figure SALESFORECASTREVENUE (such as exists in the supplied model SAP2) as a calculated key figure.



Steps1. Verify the calculation at REQUEST level:

SALESFCSTREV@REQUEST = SUM(“SALESFCSTREV@PERPRODCUST”)2. Select the input key figures and define the input key figures as shown in the table below:

Table 108:

Input Key Figures Stored

SALESFCSTREV@PERPRODCUST

As the input is selected as calculated and not stored, you need to complete the calculation by defining the calculation at the base planning level.

3. Click Add Calculation. A calculation is created with SALESFCSTREV@PERPRODCUST on the left-hand side.4. Add the calculation to the right-hand side of the equation as follows:

SALESFCSTPRICE@PERPRODCUST" * "SALESFCSTQTY@PERPRODCUST5. Click Validate Calculation. If the calculation expression contains no errors, the Input Key Figures dialog is

opened. Verify the Input Key Figures correspond to the entries in the table below.

Table 109:

Input Key Figures Stored

SALESFCSTPRICE@PERPRODCUST X

SALESFCSTQTY@PERPRODCUS

As SALESFCSTQTY@PERPRODCUS is calculated at that planning level, it is not stored.


19.9 Configuring Price and Cost for Currency and UoM Conversions

Key figures such as Price and Cost are expressed as currency / unit of measure, for example, 10 USD / case. When a user selects the target unit of measure or target currency, the value for the Price key figure changes to correspond to the user’s selection. Price can be configured as follows in IBP:

● Stored key figure that can be maintained in IBP● Calculated key figure based on Revenue and Quantity, both of which are stored

For both of the above options, the following aggregations are possible:

● Average● Weighted average based on Revenue and Quantity, both of which have currency and unit of measure

conversions.

The base planning level for a Price key figure, for example, PERPRODCUSTCURR includes the base currency and the base unit of measure from the Product master data type.


Sample Configuration for Price Key Figure with Conversions

The following table shows the Price key figure:

Table 110:

Key Figure Name Price

Key Figure ID PRICE

Base Planning Level PERPRODCUSTCURR

Convert Using EXCHANGERATEBYUOM

Aggregation: Average Price Calculation with Conversions

Set the aggregation mode for the key figure Price to Avg (Average). If the Price key figure is stored and editable, the disaggregation mode is Proportional-Copy Value.

Calculations:

● PRICE@REQUEST = AVG(PRICE@PERPRODCUSTCURRUOMFRTO)● If Price is a stored key figure:

PRICE@PERPRODCUSTCURRUOMFRTO = PRICE@PERPRODCUSTCURR (stored) * EXCHANGERATEBYUOM@PERPRODCUSTCURRUOMFRTO

● If Price is a calculated key figure based on Revenue (stored) and Qty (stored):PRICE@PERPRODCUSTCURR = REVENUE@PERPRODCUSTCURR / QTY@PERPRODCUSTPRICE@PERPRODCUSTCURRUOMFRTO = PRICE@PERPRODCUSTCURR (calc) * EXCHANGERATEBYUOM@PERPRODCUSTCURRUOMFRTOWhere EXCHANGERATEBYUOM@PERPRODCUSTCURRUOMFRTO = IF(UOMCONVFACTOR@PRDUOMTO =0 OR EXCHGRATE@MTHCURRCURRTO = 0, NULL, EXCHGRATE@PERCURRFRTO / "UOMCONVFACTOR@PRDUOMTO" )

Aggregation: Weighted Average Based on Revenue and Quantity with Conversions

Set the aggregation mode of the key figure to CUSTOM. If the Price key figure is stored and editable, the disaggregation mode is Proportional-Copy Value.

Calculations:

● PRICE@REQUEST = HREVENUE@REQUEST / HQTY@REQUESTWhere REVENUE@REQUEST = SUM(REVENUE@PERPRODCUSTCURRFRTO)

● If Revenue is a stored key figure:REVENUE@PERPRODCUSTCURRFRTO = REVENUE@PERPRODCUSTCURR(stored) * EXCHANGERATE@PERCURRFRTO



● If Revenue is a calculated key figure based on Qty (stored) and Price (stored):REVENUE@PERPRODCUSTCURR = QTY@PERPRODCUST (stored) * PRICE@PERPRODCUSTCURR (stored)REVENUE@PERPRODCUSTCURRFRTO = REVENUE@PERPRODCUSTCURR (calc) * EXCHANGERATE@PERCURRFRTOQTY@REQUEST = SUM(QTY@PERPRODCUSTUOMTO) QTY@PERPRODCUSTUOMTO = QTY@PERPRODCUST * UOMCONVFACTOR@PRODUOMTOHREVENUE@REQUEST = SUM(HREVENUE@PERPRODCUSTCURRUOMFRTO)HREVENUE@PERPRODCUSTCURRUOMFRTO = REVENUE@PERPRODCUSTCURRFRTO (Input : QTY@PERPRODCUSTUOMTO)HQTY@REQUEST = SUM(HQTY@PERPRODCUSTCURRUOMFRTO)HQTY @PERPRODCUSTCURRUOMFRTO = QTY@PERPRODCUSTUOMTO (Input : REVENUE@PERPRODCUSTCURRFRTO)

NoteTo avoid divide by zero conditions, check for ISNULL and 0 conditions.

19.10 Example: Split Factor Calculation

You use a split factor calculation when you want to show a key figure that is defined at an aggregated level at a lower level of granularity. You do so by splitting the value for the aggregated key figure proportionally according to the value for another key figure.

In this example, the key figure AggDemandQty, which is defined at planning level Product/Key Customer, is to be disaggregated proportional to the SalesQty, which is defined at planning level Product/Customer. Using split factor configuration, AggDemandQty, which is defined at aggregate level is available at detailed level Product/Customer based on a proportional split of Sales Qty.

Imagine that the key customer group CG1 has achieved a sales quantity of 300 for product P1:

Table 111:

Product ID

Key Customer

Key Customer ID

Key Figure

Oct '14 Nov '14 Dec '14 Jan '15 Feb'15 March'15 ...

P1 CG1 C1 AggDemandQty

200 200 200 200 200 ...

SalesQty

100 100 100 100 100

C2 AggDemandQty

400 400 400 400 400 ...

SalesQty

200 200 200 200 200


The following text describes how to set up this split factor calculation:

Steps

1. Add a helper key figure (for example, HSALESFCSTAGG) that aggregates SALESFORECASTQTY to planning level PRODCUSTGRP. (You need a helper key figure because you cannot use the same key figure name twice in a single calcuation.).Calculation Definitions:○ HSALESFCSTAGG@PERPRODCUST = “SALESFORECASTQTY@PERPRODCUST” ○ HSALESFCSTAGG@PERPRODCUSTGRP = SUM(“HSALESFCSTAGG@PERPRODCUST”)

2. Define the split factor:HSPLITFACTORSALESQTY@PERPRODCUST = IF(ISNULL(“HSALESFCSTAGG@PERPRODCUSTGRP”)or “HSALESFCSTAGG@PERPRODCUSTGRP = 0,0, SALESFORECASTQTY@PERPRODCUST / HSALESFCSTAGG@PERPRODCUSTGRP”)

3. AGGDEMANDQTY@PERPRODCUST = “AGGDEMANDQTY@PERPRODCUSTGRP”* HSPLITFACTORSALESQTY@PERPRODCUST

4. At request level, change the planning level for the input key figure AggDemandQty from @PERPRODCUSTGRP to @PERPRODCUST,

19.11 Enabling Change History for Key Figures and Planning Areas

Context

The change history tracks changes to stored key figures and their dependent calculated key figures. You can view the changes in the IBP Excel add-in, or in the Change History app. For more information, see http://help.sap.com/ibp. Choose your version, then Application Help for SAP Integrated Business Planning English SAP Integrated Business Planning Planning with Microsoft Excel Information for End Users Viewing Change History in the IBP Excel Add-In or Application Help for SAP Integrated Business Planning English SAP Integrated Business Planning Working with Web Applications Change History .

ExampleIf the calculated key figure Revenue depends on two stored key figures, Price and Quantity, and these stored key figures are history-enabled, then changes to Revenue are also captured. If only one of those stored key figures is history-enabled, then any changes tracked for Revenue are incorrect. To be able to track changes to a calculated key figure correctly, enable all stored key figure inputs to that calculated key figure for the change history.

Note the following:

● The change history does not track changes to individual calculated key figures, and it is not supported for snapshot key figures.





● It cannot be combined with S&OP operators and inventory optimization operators.● Before you can view the change history in MS Excel, the Basic Planning Tasks business catalog must have

been assigned to your user.● Before you can use the change history app, the Change History business catalog must have been assigned to

your user.

RecommendationFor best performance, we recommend that you select a maximum of 3 key figures for change tracking.

Steps: Enabling Change History for Key Figures1. Choose Key Figures in the Configuration app.2. Select the key figure whose data changes you want to track.3. Select the Change History Enabled checkbox.4. Save your changes.

Steps: Enabling Change History for Planning Areas

NoteTo track changes on key figures, you must enable the change history on planning area level, too.

1. Choose Planning Area and Details in the Configuration app.2. Select the planning area whose data changes you want to track.3. Under Change History, select the Planning Area Enabled checkbox.4. Save your changes.

CautionIf you select the Change History, Planning Area Enabled checkbox, and later decide to unselect it, the previously recorded change history of the planning area will be deleted upon the next activation of the planning area.

19.12 Period To Period Comparisons using Time Profile Attributes

Context

When you create a custom alert definition, normally you can only use one time attribute at the calculation level. If you want to set up alerts to compare key figures across different time periods, you can configure time profile attributes to facilitate period to period comparison.

For example, period to period comparison allows you to compare:


● Year to year comparison of actuals grouped by month● Year to year comparison of actuals grouped by quarter● Quarter to quarter comparison of sales forecast quarterly, grouped by month in quarter

Time profile attributes are additional attributes that can be assigned to a time profile level. You do not need to change any existing master data or key figure data.

You create the new time profile attributes you want, then add the attributes to a new or existing time profile.

You then assign the new attributes to the lowest time profile level or a higher time profile level at which a key figure is stored or calculated.

ExampleConfiguring Period to Period comparison for ACTUALSQTY

For example, you can attach the attribute MONTHNAME to Time Profiles which has a Monthly Time profile:

Periodid Period Desc MONTHNAME

1000 JAN 2015 01-JAN

1010 JAN 2016 01-JAN

1. Choose Manage Attributes on the initial screen of the Configuration app or click Attributes in the top menu.2. Click Create New and create the following attributes:

○ MONTHINQTY○ MONTHNAME○ PERIODNAME

3. Choose Manage Time Profiles on the initial screen of the Configuration app or click Time Profiles in the top menu. Either create a new time profile by clicking Create New or select an existing time profile.

4. Add the new attributes to the lowest time profile level or at the time profile level at which the key figure you want to compare is stored or calculated. In this example, we will be creating and comparing the key figure ACTUALSQTY, which is calculated at the monthly level, therefore click Assign Attributes at the month level or lower, select MONTHINQTY, MONTHNAME, and PERIODNAME, then click OK.

5. Choose Define Planning Areas on the initial screen of the Configuration app or click Planning Areas and Details in the top menu. Create a planning area for period to period comparison clicking Create New. Include the time profile to which you added the attributes. Add master data types you want to use for the comparison and all other relevant information and save the planning area.

6. Choose Manage Planning Levels on the initial screen of the Configuration app or click Planning Levels in the top menu. Create a planning area for period to period comparison clicking Create New.Create a planning level in the planing area and verify that it contains the time profile attributes you added.

7. Choose Manage Key Figures on the initial screen of the Configuration app or click Key Figures in the top menu. Click Create New and create the key figure ACTUALSQTY, using the base planing level you created.



8. Activate the master data type, time profile and planning area.


20 Reserved Names and Naming Restrictions

Reserved Names

Do not use the IDs, names, descriptions, and values listed below when configuring and using your planning model, as these elements have a special significance in SAP Integrated Business Planning.

Attribute ValuesWhen uploading data, you cannot use the following values for the attribute:

● NONE● ALL● BASELINE● REALTIME

Attribute IDsThe following attribute IDs are not allowed:

● KEY_FIGURES (reserved for key figures)● SCNID (reserved for versions, previously known as “scenarios”)● PLANNING_LEVELS● TIME_ROLLING● TIME_REALTIME● ROWAXIS_DEFINITION● COLUMNAXIS_DEFINITION● FILE_EXTENSION● XL_SHEET● ALERTS_ONLY● ALERT_MAPPING● ALERTS_DEFINITION● PLUNITID_TIME_HORIZON● PLUNTID_TIME_RELATIVE_FROM● PLUNTID_TIME_RELATIVE_TO● IDX● DUMMY● PERIODLEVEL● PERIODID● GROUP


Reserved Names and Naming Restrictions

Key Figure IDs and NamesThe following key figure names are not allowed:

● DUMMY

Both the key figure ID and the key figure name must be unique within a planning area.

Naming Restrictions

AttributesWhen you create attributes, do not create attributes that have any of the following dependencies between their IDs:

Table 112:

ID of Attribute 1 ID of Attribute 2 Example

<ATTRIBUTEID> <ATTRIBUTEID>+A BATCH and BATCHA

<ATTRIBUTEID> <ATTRIBUTEID>+NUM BATCH and BATCHNUM

<ATTRIBUTEID>+ID <ATTRIBUTEID>+NUM BATCHID and BATCHNUM

Attributes and Key FiguresAn attribute ID must not be identical with or contain a key figure ID.

Model Configuration GuideReserved Names and Naming Restrictions C U S T O M E R 211

Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).


Important Disclaimers and Legal Information

http://help.sap.com/disclaimer/

Model Configuration GuideImportant Disclaimers and Legal Information C U S T O M E R 213

go.sap.com/registration/contact.html

© 2017 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

For SAP Integrated Business Planning 1702 - SAP Help · PDF fileFor SAP Integrated Business...

Documents

Transcript of For SAP Integrated Business Planning 1702 - SAP Help · PDF fileFor SAP Integrated Business...