what's new in sap integrated business planning for supply

PUBLICDocument Version: 1.5 – 2021-04-16

What's New in SAP Integrated Business Planning for Supply Chain 2011

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 What's New in SAP Integrated Business Planning for Supply Chain 2011. . . . . . . . . . . . . . . . . . 61.1 How to Use the What's New Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371.2 What's New History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401.3 Identity and Access Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Manage Business Role Changes After an Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .421.4 Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

New Apps for Exporting and Importing Software Collections. . . . . . . . . . . . . . . . . . . . . . . . . . . 43Enhancements to Navigations to Other Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Resource Consumption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Monitor Application Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46SSL Client Certificate Authentication for SAP_COM_0035 – Planning – Data Services Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Deprecated App: Maintain Employees. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Deprecated Job Template: Delete Application Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Maintain Communication Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48New Types Available in Content Administration App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Spaces and Pages Enhanced. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

1.5 Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Deprecated OData Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Authorization Check for /IBP/EXTRACT_ODATA_API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51New OData Service for Importing Key Figure Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52New OData Service for Integrating Planning Calendar Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

1.6 Model Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Switch to Calculation View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Normalization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Checks for Stored Key Figures Read from Incompatible Input Planning Levels. . . . . . . . . . . . . . . 55Suppressible Errors Expiring in Upcoming IBP Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Calendar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60New App: Where-Used Information for Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61New Validation Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61MIN and MAX with Multiple Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Generate Missing Time Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Improved Processing of Copy Operator Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Where-Used List for Copy Operator Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Usability Enhancements for Copy Operator Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Usability Enhancements for the Planning Areas App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

2 PUBLICWhat's New in SAP Integrated Business Planning for Supply Chain 2011

Content

Enhancements for the Comparison of Planning Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Activation Check for Fixing-Enabled Key Figures with a Wrong Generated Key Figure Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Activation Check For Fixing-Enabled Key Figures with a Version Assignment Problem. . . . . . . . . .69

1.7 Unified Planning Area (SAPIBP1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Unassignment of Attributes Used in Inventory Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . .70Adjustment of Key Figure Names and Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Activation Checks: Change of Planning Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Adjustment of Attribute Name and Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Change of Request Level of HCONVRECOMMENDEDSAFETYSTOCK Key Figure. . . . . . . . . . . . . . . . . 72

Change of Disaggregation of STATISTICALFORECASTQTY Key Figure. . . . . . . . . . . . . . . . . . . . .73

Consideration of Change Points in SAPIBP1 Forecast Automation Profile. . . . . . . . . . . . . . . . . . 74

SAPIBP1: Dynamic Lag for Propagation of Forecast Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Unit of Measure Conversion for Output Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Change of Default Optimizer Parameters in S&OP Operator Profiles. . . . . . . . . . . . . . . . . . . . . . 75Change of Key Figure Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Change of Attributes Related to Lead Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Simplification of Technical Key Figures in Demand Sensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 78New Key Figures: Late Delivery for Inter-Subnetwork Demand. . . . . . . . . . . . . . . . . . . . . . . . . . 78Unassignment of Attributes from Planning Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

1.8 SAP IBP, Excel Add-In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80New Excel Add-in Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Removing a Global Configuration Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80System Behavior Adjustment for Applied Invalid Attribute Filters. . . . . . . . . . . . . . . . . . . . . . . . 80Sorting in Planning Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Folders for Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Basic Planning Tasks Business Catalog Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Filtering Planning Views in Offline Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.NET version upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

1.9 Demand Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Settings for Phi in Automated Exponential Smoothing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84Outlier Correction for Seasonality and Trend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Forecast Deleted After Phase-Out End Date even if History is Missing. . . . . . . . . . . . . . . . . . . . . 86Seasonality Handled by Change Point Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Categorical Variables for MLR and GBDT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Time Series Analysis for Demand Sensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Snapshot Key Figure Becoming Optional in Demand Sensing. . . . . . . . . . . . . . . . . . . . . . . . . . .89Simplification of Technical Key Figures in Sample Planning Area. . . . . . . . . . . . . . . . . . . . . . . . 90Enhanced Disaggregation of Weekly Promotion Sales Lifts in Demand Sensing. . . . . . . . . . . . . . 93Number of Change Points Shown in the Assign Forecast Models App. . . . . . . . . . . . . . . . . . . . . 93Upload of Realignment Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

What's New in SAP Integrated Business Planning for Supply Chain 2011Content PUBLIC 3

Usability Enhancements in Manage Product Lifecycle App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Disable Deletion of Product Assignments, Forecast Dates, and Phase-In/Phase-Out Curves. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Preferred Launch Dimension Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Deletion of Product Assignments, Forecast Dates, and Curves Using File Upload. . . . . . . . . . . . . 96

1.10 Inventory Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Dynamic Lag for Propagation of Forecast Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97New App: Inventory Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Incorporate Non-Stocking Push Logic in Inventory Components Operator. . . . . . . . . . . . . . . . . 101Master Data Quality Log Messages when Running Inventory Functions. . . . . . . . . . . . . . . . . . . 102New Optional Parameter in Inventory Optimization Job Templates. . . . . . . . . . . . . . . . . . . . . . 103

1.11 Demand-Driven Replenishment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Enhancements for Demand-Driven Supply and Operations Planning. . . . . . . . . . . . . . . . . . . . . 104Include Prebuilt Stock in DDMRP Buffer Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108New App: DDMRP Buffer Status Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Reporting of DDMRP projected on-hand stock in number of days of coverage. . . . . . . . . . . . . . . 111Support of Filter Variant Management in the DDMRP Buffer Analysis App. . . . . . . . . . . . . . . . . 112

1.12 Time-Series-Based Supply Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Time-Series-Based Shelf Life Planning Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Late Delivery for Inter-Subnetwork Demand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Change of Default for Minimum Aggregated Constraints in S&OP Operator Profiles App. . . . . . . . 114Change to Planning Levels in Sample Planning Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Enhanced Documentation for Expert Settings in Optimizer Profiles. . . . . . . . . . . . . . . . . . . . . . 115Status Handling in Settings for TS Supply Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Optimization Problem Inputs on Optimizer Run Details Screen. . . . . . . . . . . . . . . . . . . . . . . . . . 116New Table: Supported Functions per Algorithm (Docu Enhancement). . . . . . . . . . . . . . . . . . . . 116

1.13 Order-Based Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Planning Run Profiles: New Object-Attribute Combinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Enhanced Transportation Costs in Planning Runs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118Copy of Order-Based Planning Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118Generation of Costs in Deployment Runs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Expert Settings in Optimizer Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119Resource Consumption Unit Shown in Analyze Supply Usage. . . . . . . . . . . . . . . . . . . . . . . . . . 119Deprecation of OpenAPI Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120New Key Figures and Attributes for DPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Mandatory Data Entries Changed in IBP_MATERIAL_UNIT_CONVERSION. . . . . . . . . . . . . . . . . 123

New Table: Supported Functions per Planning Run in OBP (Documentation Enhancement). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123Default Time Zone in OBP Planning Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

1.14 Cross Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124New App: Change History Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124


Content

New App: Manage Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Bookmark Update Required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127Public Holidays in the Planning Calendars App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Enhancements for Copy Version Operator and Delete Version Operator. . . . . . . . . . . . . . . . . . . 128Enhancements to Application Job Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Local Time Zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

1.15 Exception Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Enhancements to Define and Subscribe to Custom Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Enhancements to Monitor Custom Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

1.16 End-to-End Visibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Enhancements to Intelligent Visibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132New App: Intelligent Visibility Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

1.17 Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Enhancements to Analytics - Advanced. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Enhancements to Dashboards - Advanced. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Supply Chain Network: Render DDMRP Decoupling Points in Network Charts. . . . . . . . . . . . . . 135Supply Chain Network: Filter Bar Added to Chart List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Supply Chain Network: Required Master Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

1.18 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Customer-Initiated Penetration Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

What's New in SAP Integrated Business Planning for Supply Chain 2011Content PUBLIC 5

1 What's New in SAP Integrated Business Planning for Supply Chain 2011

About this version

Product Version SAP Integrated Business Planning for Supply Chain 2011, including Hotfix Collection (HFC) 7

Document Information 1.5 - January 15, 2021

For software corrections, new software features, and major documentation enhancements in this HFC, see the What's New History [page 40].

Important SAP Notes 2937901 (central note)

2937868 (release restriction note)

2937857 (release information note)

2937891 (patch collection information note)

2954137 (documentation corrections)

2135948 (prerequisites for the installation of the SAP IBP, Excel add-in)

2394311 (version information for the SAP IBP, Excel add-in)

Licensing Information Applications and Features of SAP Integrated Business Planning

What's new in 2011, and what you need to do after the upgrade to 2011?

The What's New table below lists all news and changes. You can filter the table according to your needs, in particular, to find the tasks that you need to perform immediately after the upgrade. Just click the blue Filter in the column header. For more information, see How to Use the What's New Table [page 37].



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







https://help.sap.com/viewer/6b0a6820ebf94ff4a15d68af6db7745b/2102/en-US/b48f855725308a1be10000000a44147b.html

https://help.sap.com/viewer/6b0a6820ebf94ff4a15d68af6db7745b/2102/en-US/b48f855725308a1be10000000a44147b.html

What's New

Business Topics Types

Target Groups Impact What's New - Headline

What's New - Details

Administration

New Administrator/configuration expert

Web UI The Resource Consumption app now has a simplified UI to make it more efficient and user-friendly when monitoring the CPU and SAP HANA memory usage in real-time.

Resource Consumption [page 45]

Administration


Web UI You can use the new features of the Monitor Application Jobs app to perform the following tasks:

● Schedule jobs by navigating directly to the Application Jobs app

● Use the Quick Schedule option to schedule jobs using job templates where all the mandatory parameters are filled

● Cancel jobs and job chains with statuses Scheduled or Running

● Restart a job or a job chain that failed to run successfully

● Copy any single or multi-step jobs regardless of the job status

Monitor Application Jobs [page 46]

Administration Must

know

Administrator/configuration expert

Web UIApplication job

The application job template Delete Application Logs has been deprecated in the current release. We plan to remove it with the SAP IBP 2105 release. The system is now handling the log deletion process and no further action is required.

Deprecated Job Template: Delete Application Logs [page 48]

Administration Must

knowPrepare next releaseNew


Web UINew SAP Fiori app

The Maintain Employees (F2288) app has been replaced by Maintain Employees (F2288a).

The Maintain Employees (F2288) app will be removed with the SAP IBP 2105 release. We recommend that you switch to the successor app Maintain Employees (F2288a) as soon as possible.

Deprecated App: Maintain Employees [page 47]

Identity and access management


Web UIRole/business catalog

You can now view changed business catalog dependencies after an upgrade. Additionally, you can display deprecated business catalogs, view successor catalogs, and adopt the required changes in your business roles.

Manage Business Role Changes After an Upgrade [page 42]

Administration


Web UI You can now assign more than one certificate to a communication user to enable a smooth transition when certificates are exchanged.

Maintain Communication Users [page 48]

What's New in SAP Integrated Business Planning for Supply Chain 2011What's New in SAP Integrated Business Planning for Supply Chain 2011 PUBLIC 7




Administration

Prepare next release


New SAP Fiori appModel configurationRole/business catalog

The Export Software Collection, Import Collection, and Extensibility Inventory apps are now supported in SAP IBP. If a system landscape is enabled for extensibility development, the new apps can be used for the export and import of software collections with extension items, such as model entities. This allows for better control of the import in the landscape and better handling of the dependencies between extension items.

If you have at least two SAP IBP systems in your landscape, for example, a test and a production system, you will be contacted by SAP to evaluate and plan the next steps for enabling your landscape for extensibility development.

If your system landscape is not yet enabled for extensibility development, you can continue to use the Transport Model Entities app. When all customers have switched to the new apps in the upcoming releases, this app will be deprecated and will be deleted from the SAP Fiori launchpad.

Three new business catalogs are available that include the new apps.

New Apps for Exporting and Importing Software Collections [page 43]

Administration


Integration You can now choose the SSL Client Certificate authentication method for communication scenario SAP_COM_0035 – Planning – Data Services Integration.

SSL Client Certificate Authentication for SAP_COM_0035 – Planning – Data Services Integration [page 47]






AdministrationOrder-based planning


Web UIModel configuration

In the Manage Navigation to Other Systems app, you can now define static attribute values for some of the target attributes that can be passed to a navigation to an SAP GUI system. This will allow users to navigate to an SAP GUI system and proceed with their tasks more quickly.

To support the creation of navigations for order-based planning from the Intelligent Visibility or Web-Based Planning app to the selected order documents in SAP ERP or SAP S/4HANA, new simple master data types have been added to the SAP7 sample planning area. To use these master data types, make sure they're added to your planning areas.

Enhancements to Navigations to Other Systems [page 44]

Administration


Web UI In the Content Administration app, you can now use the new Change History View (Web-Based) and Intelligent Visibility types.

New Types Available in Content Administration App [page 49]

Administration

NewChanged


Web UI New features were added to the spaces and pages layout to provide better handling, ease navigation between the different apps involved, and enhance translation processes.

Spaces and Pages Enhanced [page 49]

Data integration Man

datory task after upgrade


Integration As previously announced, the /IBP/EXTRACT_SRV OData service is now deprecated, and you need to use the /IBP/EXTRACT_ODATA_SRV OData service instead.

Deprecated OData Service [page 50]

Data integration Man

datory task after upgrade


Integration An authorization check is now performed when extracting master data using the /IBP/EXTRACT_ODATA_API OData service. To continue using the service, check the permissions assigned to business users, and adjust them where necessary.

Authorization Check for /IBP/EXTRACT_ODATA_API [page 51]

Data integration


Integration There is a new OData service, which you can use to integrate key figure data to SAP IBP from external systems that can call OData service APIs other than SAP Analytics Cloud.

New OData Service for Importing Key Figure Data [page 52]





Data integration


Integration There is a new OData service, which you can use to import planning calendar data to SAP IBP.

New OData Service for Integrating Planning Calendar Data [page 52]

Model configuration


Model configurationWeb UI

The Compare Planning Areas app now supports the following object types:

● Attributes as key figures● Snapshot definitions● Versions● Planning operators

The app now allows you to export comparison results to CSV files.

The Compare in CSV function, which is available in the Planning Areas app and the Sample Model Entities app, now supports snapshot definitions as well.

Enhancements for the Comparison of Planning Areas [page 67]

Model configuration



Various usability enhancements have been implemented for the Planning Areas app concerning snapshot definitions, key figures, attributes, and navigation.

Usability Enhancements for the Planning Areas App [page 66]






Model configuration



Model configuration Remember

The following errors are suppressible in SAP IBP 2011:

● *S* Key Figure &1 has generated key figure assignment problemAs announced in SAP IBP 2005, this error will become non-suppressible in the 2102 release.

● *S* Key Figure &1 has version assignment problem in Version &2As announced in SAP IBP 2008, this error will become non-suppressible in the 2105 release.

Please prepare for these changes by resolving the inconsistencies.

Activation Check for Fixing-Enabled Key Figures with a Wrong Generated Key Figure Assignment [page 68]

Activation Check For Fixing-Enabled Key Figures with a Version Assignment Problem [page 69]

Model configuration Must

know


Model configuration

In SAP IBP 2011, the rollout of the switch to calculation views is finalized. Calculation view replaces analytic view as the data source of the calculation scenario. It is needed to enable further features and to improve performance.

To find out if calculation views are used as data sources in your system, open the log of an activation that took place after the upgrade to SAP IBP 2011.

Switch to Calculation View [page 53]





Model configurationNormalization



Model configuration

As announced previously, a new normalized data model has been introduced to improve performance, memory utilization, robustness, and scalability in the upcoming releases. To be ready for normalization, please make sure that your planning model fulfills the following requirements:

● In calculation definitions, an input planning level where the stored value of a key figure is used must contain the same set of root and non-root attributes as the base planning level.

● The number of time series entries that can be created or updated using an attribute as key figure must not exceed the limit of 1 million time series entries per attribute as key figure.

NoteActivate your planning areas without suppressing any errors to check whether your planning areas meet these requirements.

To find out if a system has already been normalized, activate a planning area and open the activation log. If the log contains the message Planning area activation is running in a normalized data model., the system has already been normalized.

Normalization [page 54]

Model configurationNormalization



Model configuration

As part of the normalization project, we provide activation checks that help you to spot and fix errors in your configuration that would prevent the normalization of your data model. These checks indicate if there are calculation definitions where the stored value of a key figure is used at an input planning level other than its base planning level, and whether the input planning level has a different set of root and non-root attributes from the base planning level, which is not allowed.

This is an existing modeling requirement, which is supported by five activation checks, implemented as suppressible errors.

Checks for Stored Key Figures Read from Incompatible Input Planning Levels [page 55]






Model configuration



Model configuration

The following suppressible errors will turn into errors in the upcoming SAP IBP releases:

● *S* PL &1 and PL &2: Both cannot be used as base PL of stored key figures

● *S* Calculation &1@&2: Expression doesn't start with aggregation function

● *S* Stored values of KFs, with different base PLs, are read from PL &1

● *S* Calc. &1@&2: PL of input KF &3 has more attr. than base PL &4.

● *S* Calc. &1@&2: PL of input KF &3 doesn't contain root attr. of base PL.

After that, you can no longer activate your planning areas with limited scope if these errors occur. Correct the invalid configurations to be able to activate your planning areas.

Suppressible Errors Expiring in Upcoming IBP Releases [page 59]

Model configurationCross applications


Model configuration

The calendar (IBP_CALENDAR) function is now available to count with different calendars (integrated from SAP ERP) in key figure calculations.

Calendar [page 60]

Model configuration


Model configurationRole/business catalog

You can use the Where-Used Information for Key Figures app to display the list of key figures, copy operator profiles, and planning view templates and sheets that use the selected key figures.

New App: Where-Used Information for Key Figures [page 61]

Model configuration


Model configuration

In the Planning Areas app, the following new modeling requirements and validation checks have been introduced to prevent erroneous configurations:

● A planning area that is not enabled for external time series cannot use versionspecific external master data types.

● An aggregation (SUM, AVG, MIN, or MAX) cannot contain an embedded expression; it must have exactly one input key figure.

New Validation Checks [page 61]





Model configuration


Model configuration

The MIN and MAX functions can have several input key figures now.

If there are several input key figures, there is no aggregation in the MIN and MAX functions; the output is simply the lowest or highest value of the input key figures.

MIN and MAX with Multiple Inputs [page 62]

Model configuration


Model configuration

The generate missing time periods (IBP_GENERATE_MISSING_TP) function is now available to generate missing time buckets for the calculation horizon.

Generate Missing Time Periods [page 63]

Model configuration


Planning algorithm

Various usability enhancements have been implemented for the Copy Operator Profiles app.

Usability Enhancements for Copy Operator Profiles [page 65]

Model configuration


Planning algorithm

There are two new where-used features for copy operator profiles:

● The Where Used tab in the Copy Operator Profiles app shows you all application job templates and application jobs that use the copy operator profile.

● The Where-Used Information for Key Figures app shows you all copy operator profiles a specific key figure is contained in.

Where-Used List for Copy Operator Profiles [page 65]

Model configuration


Planning algorithmApplication job

The processing of copy operator profiles has been improved by enabling reruns of erroneous packages and parallel processing for the Clear Values feature.

Improved Processing of Copy Operator Profiles [page 64]

Unified planning area (SAPIBP1)Inventory optimization

Changed Administrator/configuration expert

Model configuration

Attributes that are not required for reporting in planning views or analytics have been unassigned from the planning area and planning levels. They still, however, must stay assigned to the master data types. This change was done to simplify the unified planning area SAPIBP1.

Unassignment of Attributes Used in Inventory Optimization [page 70]






Unified planning area (SAPIBP1)Time-series-based supply planning


Model configuration

The names and descriptions of the MINCAPAUSAGE and MINCAPAUSAGEVIOLCOSTRATE key figures have been adjusted to be in line with the SAP4 sample planning area.

Adjustment of Key Figure Names and Descriptions [page 71]



Model configuration

The CALWKPRODLOCRESSRCAGG and CALWKPRODLOCLOCFRRESAGG planning levels have been changed to be in line with enhanced planning area activation checks for aggregated constraints key figures.

Activation Checks: Change of Planning Levels [page 71]

Unified planning area (SAPIBP1)Cross applications


Model configuration

The name and description of the CUSTCOUNTRY attribute have been adjusted. They are now Customer Country/Region.

Adjustment of Attribute Name and Description [page 72]


Changed Administrator/configuration expertBusiness user

Model configuration

The request level of the HCONVRECOMMENDEDSAFETYSTOCK key figure has been changed to AVG.

Change of Request Level of HCONVRECOMMENDEDSAFETYSTOCK Key Figure [page 72]

Unified planning area (SAPIBP1)Demand planning


Model configuration

The STATISTICALFORECASTQTY key figure is now disaggregated by the DISAGGFACTOR key figure when statistical forecasting is run on an aggregated level.

Change of Disaggregation of STATISTICALFORECASTQTY Key Figure [page 73]






New Administrator/configuration expertBusiness user

Model configuration

Change points are now considered by the SAPIBP1 (Time Series Analysis) forecast automation profile.

Consideration of Change Points in SAPIBP1 Forecast Automation Profile [page 74]



Model configuration

With the addition of a new master data type and two new key figures, dynamic lag is now available when calculating inventory targets for each location in a multistage supply chain network.

SAPIBP1: Dynamic Lag for Propagation of Forecast Error [page 74]



Model configuration

You can now use unit of measure conversion for the DEPENDENTCUSTOMERDEMANDMEAN and DEPENDENTCUSTOMERDEMANDSTDD output key figures. Two helper key figures have been introduced for this purpose.

Unit of Measure Conversion for Output Key Figures [page 75]



Model configurationPlanning algorithm

The default setting for whether violations of minimum aggregated constraints are possible has been changed.

Change of Default Optimizer Parameters in S&OP Operator Profiles [page 75]



Model configuration

The calculations of the HDEMANDRATIO and HAGGCONSENSUSDEMANDQTYRO key figures have been changed to enhance the disaggregation in driver-based planning.

Change of Key Figure Calculations [page 76]








Model configuration

Attributes that are related to lead time in the IBPSOURCELOCATION and IBPSOURCECUSTOMER master data types have been changed.

Change of Attributes Related to Lead Time [page 77]




Model configuration

Several technical key figures will be removed from the SAPIBP1 sample planning area in the 2102 release of SAP Integrated Business Planning to be in line with the SAP6 sample planning area.

Simplification of Technical Key Figures in Demand Sensing [page 78]




The time-series-based optimizer and the time-series-based finite heuristic now support late delivery of subnetwork dependent demand, so if supply isn't available in time, it can be fulfilled in a later period.

This feature introduces two new input key figures and one new output key figure in the SAPIBP1 sample planning area.

New Key Figures: Late Delivery for Inter-Subnetwork Demand [page 78]



Model configuration

In normalized planning areas, two attributes no longer have to be assigned to the planning area. They still, however, must stay assigned to the corresponding master data type.

Unassignment of Attributes from Planning Areas [page 79]





SAP IBP, add-in for Microsoft Excel



With SAP Integrated Business Planning 2011, the IBP Excel add-in 2011.2.0 is available. For more information about the versions of the IBP Excel add-in, see 2394311 .

NoteIn general, the upgrade to SAP IBP 2011 does not require that you install the new version of the Excel add-in. You can decide to install it at any point in time when you wish to use the new features; however when you do, please note that .NET Framework 4.7.2 or higher is required for the new version of the Excel add-in. The new features that become available with the Excel add-in 2011.2.0 are described in the 2011 documentation.

New Excel Add-in Version [page 80]


New Business user

SAP IBP, add-in for Microsoft ExcelGlobal configuration parameter

You can now sort attribute values, for example, specific customers or products, in planning views. Rules for this can be set based on standard and custom logics.

Beside ascending (A-Z) or descending (Z-A) sorting, you can apply custom rules that allow you, for example, to pin preferred values to the top of your planning view.

The limit on the number of attribute values that can be handled via custom sorting is defined through a new global configuration parameter.

Sorting in Planning Views [page 81]

Global Configuration Parameters



SAP IBP, add-in for Microsoft ExcelApplication job

In some cases, attribute-based planning filters become invalid. This can happen when attribute values that were once set as filters are removed from SAP IBP, therefore they cannot be used for filtering any longer. In the past, invalid attribute filters were ignored by application jobs that were run from the Excel add-in; the application job ran without a filter, processing mass-amounts of data.

From version 2011.2.0. of the Excel add-in – if all attribute filters applied are invalid – an application job launched from the add-in provides the same output as one launched from the WebUI. It is executed, however, no data is processed.

System Behavior Adjustment for Applied Invalid Attribute Filters [page 80]




https://help.sap.com/viewer/bf99e931b8d44aafb4e306ec3602cbdd/2102/en-US/b5210a550e38eb14e10000000a4450e5.html








Global configuration parameter


For some time now, a second query has been available for the Excel add-in that reads data from the database using the filters in the planning view. Until now, you could switch between the old and the new query using the NEW_QUERY parameter. Since the new query is the basis for many existing and future new add-in features, we have made it the standard query as of 2011. The old query is no longer available. Therefore, we have removed the parameter NEW_QUERY. Please note that this change has no impact on end users.

Removing a Global Configuration Parameter [page 80]


New Business user


Filters are saved by default in a flat list, but as of release 2011, if you have many filters, you can arrange them in folders in the planning view settings. Both attribute-based and value-based filters can be organized this way.

Folders for Filters [page 82]


Mandatory task after upgrade


SAP IBP, add-in for Microsoft ExcelRole/business catalog

As of 2011, the business catalog Basic Planning Tasks SAP_IBP_BC_EXCEL_ADDIN_PC is mandatory for users who want to use the Excel add-in.

NoteApplicable to all SAP IBP users, those who do not have their business roles and business users assigned to this business catalog will not be able to use the add-in after release date.

Basic Planning Tasks Business Catalog Setting [page 82]


New Business user


Users who are working with SAP IBP planning views in offline mode can now also use Microsoft Excel filters. The option to filter offline workbooks increases the usability of planning views for business users who don’t have the Excel add-in installed.

Filtering Planning Views in Offline Mode [page 83]









With the upcoming SAP IBP, add-in for Microsoft Excel 2102.2.0, which is planned to be released in February 2021, we are planning to raise the minimum allowed .NET version to 4.8. It will be mandatory to upgrade the .NET version to 4.8 or higher in order to install the 2102.2.0 version of the add-in.

NoteInstalling the new version of the .NET framework is not mandatory if you do not plan to upgrade your Excel add-in version.

.NET version upgrade [page 83]

Demand planning

New Business userAdministrator/configuration expert

Web UI In the Manage Forecast Models app, you can now define upper and lower ranges for the phi coefficient in forecast models containing the automated exponential smoothing algorithm.

Settings for Phi in Automated Exponential Smoothing [page 84]

Demand planning


Web UIPlanning algorithm

You can now set the outlier correction algorithm to consider the results of time series analysis during the preprocessing steps of forecasting. If you do so, the algorithm will detect and correct outliers that significantly differ from the identified patterns of trend, seasonality, or both.

Three new correction methods are available in the Manage Forecast Models app that are specific to seasonality and trend patterns. If you decide to use one of these methods on your data, you also need to define the length of the smoothing window that the algorithm should apply.

Outlier Correction for Seasonality and Trend [page 84]

Demand planning

New Business user

Web UI A new column in the Assign Forecast Models app shows how many change points were identified by the most recent change point detection jobs that were executed on the various planning objects within the selected planning area and planning level.

Number of Change Points Shown in the Assign Forecast Models App [page 93]






Demand planning

Changed Business user

Planning algorithm

When the Disregard Leading Nulls option is selected in the Manage Forecast Models app and no historical data is available for a planning object, the system doesn’t calculate the forecasts but keeps the results of the preceding forecasting job instead.

Previously this also meant that the system couldn’t consider the phase-in and phase-out dates specified in the Manage Product Lifecycle app since the last successful run. Now, if the phase-out end date is maintained for a planning object, the system deletes the forecast values for the periods after that date even if the most recent job didn’t run successfully due to the lack of sales history.

Forecast Deleted After Phase-Out End Date even if History is Missing [page 86]

Demand planning


Planning algorithm

In forecast automation, you no longer need to run time series analysis before running change point detection on a data set.

Previously this was recommended because change point detection was not executed for a planning object if time series analysis found seasonality or intermittency in its history. Now both patterns are identified by change point detection itself. Seasonality doesn’t prevent change point detection from running anymore but it has an impact on the results. If intermittency is found, it still stops change point detection.

Seasonality Handled by Change Point Detection [page 86]

Demand planning



For each independent variable you choose for the multiple linear regression (MLR) and gradient boosting of decision trees (GBDT) algorithms in the Manage Forecast Models app, you can now specify if it is a categorical variable or not.

Categorical variables allow the algorithms to learn from sales patterns connected to events in the past that are expected to occur again in the future in varying periods.

Categorical Variables for MLR and GBDT [page 87]





Demand planning


Planning algorithmWeb UI

In the Manage Forecast Models app, you can now activate the option to automatically run time-series analysis for the demand sensing (full) algorithm. This functionality helps the algorithm avoid extreme outputs that are either too high or too low compared to sales history characteristics.

NoteThis analysis is based on a different logic than the time series analysis you can run via a Forecast Automation application job.

Time Series Analysis for Demand Sensing [page 88]

Demand planning


Planning algorithm

You no longer have to specify the snapshot key figure for the demand sensing (full) algorithm in the Manage Forecast Models app.

If you choose not to specify it, demand sensing uses the Consensus Forecast key figure for every lag while predicting the sensed demand for each week in the planning horizon.

Snapshot Key Figure Becoming Optional in Demand Sensing [page 89]

Demand planning


Planning algorithm

In demand sensing, weekly promotion sales lifts are now disaggregated into days according to the optimal daily demand split determined by machine learning instead of getting equally distributed.

Enhanced Disaggregation of Weekly Promotion Sales Lifts in Demand Sensing [page 93]

Demand planning


Web UI Downstream signals are now referred to as extra signals in the Demand Sensing (Full) section of the Manage Forecast Models app.

N/A

Demand planning



Model configuration

Several technical key figures that are used for demand sensing will be removed from the 2102 release of SAP Integrated Business Planning.

You should not create any new analytics or calculations based on the technical key figures that are planned to be removed.

Simplification of Technical Key Figures in Sample Planning Area [page 90]






Demand planning

New Business user

Application jobWeb UI

You can now specify for each Forecast Automation application job how the system should determine the current period.

If you don’t choose any of the available methods, the time of execution will be considered as the current period.

Enhancements to Application Job Templates [page 129]

Demand planning

New Business user

Application jobWeb UI

You can now specify the following optional settings in the Lag-Based Snapshots application job template:

● The planning area version in which you want the system to take lag-based snapshots

● The method in which the system should determine the current period when taking lag-based snapshots.

Enhancements to Application Job Templates [page 129]

Demand planning

New Business user

Web UI In the Manage Realignment Rules app, you can now upload realignment projects from a CSV file.

Upload of Realignment Projects [page 94]

Demand planning

New Business user

Web UI Various usability enhancements have been implemented for the Manage Product Lifecycle app.

Usability Enhancements in Manage Product Lifecycle App [page 95]

Demand planning


Web UI In the Manage Product Lifecycle app, you can now upload files with product assignments, forecast dates, and phase-in/phase-out curves that you wish to delete.

Deletion of Product Assignments, Forecast Dates, and Curves Using File Upload [page 96]

Demand planning


Web UI In the Settings for Product Lifecycle app, you can now optionally define a preferred value for your launch dimensions.

Preferred Launch Dimension Values [page 96]





Demand planning


Web UI In the Settings for Product Lifecycle app, you can now specify whether the demand planner is allowed to delete product assignments, forecast dates, and phase-in/phase-out curves.

Disable Deletion of Product Assignments, Forecast Dates, and Phase-In/Phase-Out Curves [page 95]

Inventory optimization


Model configurationGlobal configuration parameterPlanning algorithm

Dynamic lag is now available when calculating inventory targets for each location in a multistage supply chain network.

Dynamic Lag for Propagation of Forecast Error [page 97]



Application job

Planning algorithm

You can now set the current period calculation method for the Inventory Optimization Operator job template and the Profile Based Inventory Optimization job template.

New Optional Parameter in Inventory Optimization Job Templates [page 103]



New SAP Fiori appRole/business catalog

The Inventory Analysis app allows you to spontaneously create scenarios for inventory-related changes to input demand, supply, and policy variables. Once created, you can view and edit scenarios.

New App: Inventory Analysis [page 100]



Planning algorithm

The Calculate Target Inventory Components operator now uses the non-stocking push logic used by the Global (multi-stage) inventory optimization operator to provide a complete calculation of reorder points for networks with non-stocking nodes.

Incorporate Non-Stocking Push Logic in Inventory Components Operator [page 101]









A quality check of master data is performed when running an inventory operator. If there are issues with the master data quality, messages are logged in the business log.

Master Data Quality Log Messages when Running Inventory Functions [page 102]

Demand-driven replenishment



Model configuration

The DDMRP Buffer Status Monitoring app allows you to monitor the buffer status percentage for the current day, on-hand stock, order recommendation, net flow position, and projected on-hand stock for future dates. You can also define the sorting and filtering of information using variants, including a default variant.

NoteThere are two key figure changes we recommend you make to your demand-driven replenishment-based planning areas so that the app displays data correctly. The app functions with demand-driven replenishment-based planning areas created prior to SAP IBP 2011 without changes, but some information is missing or reported less accurately

New App: DDMRP Buffer Status Monitoring [page 109]



Planning algorithmModel configuration

To support demand-driven supply and operations planning, you can now run the time-series-based supply planning heuristic in your DDMRP-based planning area to create a weekly rough-cut capacity plan for unconstrained supply planning.

If you want to use the heuristic, you need to enhance you planning area with the required objects (master data types, planning levels, and key figures) and reactivate the planning area.

Enhancements for Demand-Driven Supply and Operations Planning [page 104]



Model configuration

If you make changes to your planning area, you can now use prebuilt stock as an input to the demand-driven replenishment operators that calculate DDMRP buffer levels. This can increase the accuracy of the top of yellow and top of green values, and result in more accuracy when the operators calculate the netflow equation and order recommendations.

Include Prebuilt Stock in DDMRP Buffer Levels [page 108]







Model configuration

With the addition of a new key figure,you can now view the projected on-hand inventory coverage in days.

Reporting of DDMRP projected on-hand stock in number of days of coverage [page 111]


New Business user

Web UI In the DDMRP Buffer Analysis app, you can now save and manage filter views (variants).

Support of Filter Variant Management in the DDMRP Buffer Analysis App [page 112]

Time-series-based supply planning



We've changed the default for minimum aggregated constraints when creating a new S&OP operator profile for the time-series-based supply planning optimizer. Previously the default was not to allow violation, but this could lead to infeasible or unsolvable solutions. Now the default is to allow violation of minimum aggregated constraints.

This change only affects new S&OP operator profiles; other actions (edit, copy, view, delete) are unaffected and you don't need to change existing profiles.

Change of Default for Minimum Aggregated Constraints in S&OP Operator Profiles App [page 114]




Aggregated constraints for transportation and production capacity usage are now supported in normalized planning areas.

N/A




To comply with an existing enhanced activation check for aggregated constraints key figures announced in 1705, we've made a change to certain planning levels in the SAP4, SAP4C, SAP4S, and SAPIBP1 sample planning areas.

Change to Planning Levels in Sample Planning Areas [page 115]








SAP IBP, add-in for Microsoft ExcelApplication job

You can now run the TS-Based Forecast Consumption (Not Enabled for S&OP Operator) application job template from the Excel add-in. Previously you could only run it from the Application Jobs app.

N/A



Planning algorithm

There's a change in the way the time-series-based supply planning finite heuristic determines the priority of a source of supply based on its cost rate. The finite heuristic now considers the costs of the first valid period of the source of supply. Previously it considered the cost rate specified in the first period of the planning horizon.

Be aware that if you've specified different costs in the first period and in the first valid period, you may get different results from previously.

N/A



Planning algorithmWeb UIModel configuration

We've enhanced the time-series-based shelf life planning heuristic as follows:

● You can now use the Carry Over Negative Projected Stock parameter by adding it to the Additional Parameters section of the S&OP Operator Profiles app. This generates a supply plan with negative projected stock, indicating location products that cannot completely satisfy their demand.

● The Inventory Correction key figure is now supported, so that you can influence the calculation of projected stock by adding positive or negative values in this key figure.

Time-Series-Based Shelf Life Planning Enhancements [page 112]



Planning algorithmWeb UIModel configuration


This feature introduces two new input key figures and one new output key figure.

Late Delivery for Inter-Subnetwork Demand [page 113]

Time-series-based supply planningUser assistance


Planning algorithm

The documentation for Time-Series-Based Supply Planning includes a new table that lists the supported functions per algorithm. This information is provided for the supply planning heuristic, the shelf life planning heuristic, the optimizer, and the finite heuristic.

New Table: Supported Functions per Algorithm (Docu Enhancement) [page 116]





Time-series-based supply planningUser assistance


Planning algorithm

We provide enhanced documentation for the expert settings in optimizer profiles, which you maintain in the S&OP Operator Profiles app. Expert settings help you deal with numerical issues in optimizer runs. They include numerical focus, numerical scaling, and numerical pre-optimization. The documentation has been enhanced with typical use cases and with a link to an SAP Note. The latter contains in-depth explanations of numerical issues and how expert settings can support you in solving them.

Enhanced Documentation for Expert Settings in Optimizer Profiles [page 115]



Web UIModel configuration

We have introduced status handling in the Settings for TS Supply Planning app, where you can, for example, assign attributes and key figures different from the standard ones to your planning area. The status handling enables you to save your settings in an inactive version and activate them for use in the respective planning area when necessary.

Status Handling in Settings for TS Supply Planning [page 116]




On the Optimizer Run Details screen, which you can access from the application job log, you can now find information about the size of the optimization problem and its mathematical properties.

This information is displayed in the new section Optimization Problem Inputs.

Optimization Problem Inputs on Optimizer Run Details Screen [page 116]

Order-based planning



We have added new object-attribute combinations that you can use when creating cost rules in the Planning Run Profiles app.

Planning Run Profiles: New Object-Attribute Combinations [page 117]



Application jobPlanning algorithm

The calculation of transportation costs in planning runs using the optimizer planning algorithm has been enhanced. Generated costs are now added to the transportation costs to avoid unnecessary transports.

Enhanced Transportation Costs in Planning Runs [page 118]








Model configuration

When you copy a planning area or sample planning area, the order-based planning settings are now also copied automatically.

Copy of Order-Based Planning Settings [page 118]



Application jobPlanning algorithm

You can now let the system generate the costs that are relevant in a deployment run instead of manually setting up a cost model with which you achieve the desired distribution of inventory.

Generation of Costs in Deployment Runs [page 118]


New Business user

Web UI In the Analyze Supply Usage app, the Resource Consumption Quantity columns now show the resource consumption unit in addition to the numeric value.

Resource Consumption Unit Shown in Analyze Supply Usage [page 119]




We have added Expert Settings to the Optimizer Parameters in the Planning Run Profiles app.

They include the following options to be set: Numerical Focus, Numerical Scaling, and Numerical Pre-Optimization. Those can help to better handle numerical issues, that is, undesired effects on the optimization results that are caused by big numerical differences in cost or material flow key figures, or by high cost values that are internally computed by the planning engine.

Expert Settings in Optimizer Parameters [page 119]







Model configurationPlanning algorithmSAP IBP, add-in for Microsoft Excel

New key figures are now available in the SAP7 sample planning area that you can use to analyze quantities from planned orders in the production planning stage (PP stage) Detailed Planning and Scheduling (DPS) as opposed to quantities from planned orders in the production planning stage Operational Supply Planning (OPS).

To distinguish the location materials that are expected to have a DPS share as part of the overall planned order quantities, new attributes have been added to the S7LOCATIONPRODUCT master data type in the SAP7 sample planning area.

To use these key figures and attributes, make sure they're added to your planning areas.

New Key Figures and Attributes for DPS [page 122]



Integration It is now mandatory to enter data for denominator and nominator for conversion to base units of measure in the UMREN and UMREZ columns in the IBP_MATERIAL_UNIT_CONVERSION table. This change is relevant for all available full inbound versions of OpenAPI in SAP IBP 2011.

Mandatory Data Entries Changed in IBP_MATERIAL_UNIT_CONVERSION [page 123]




Integration The following OpenAPI versions will no longer be available as of SAP IBP 2105:

● 1808.0.0_FULL (inbound integration)● 1808.0.0_TRANS (inbound integration)● 1808.0.0_OUTBOUND (outbound integration)● 1808.0.0 (planning results extraction)

If you are using 1808.0.0 OpenAPI versions, you will get a warning about the deprecation, but you can continue to use them in the 2011 and 2102 releases of SAP IBP. Note that these OpenAPI versions will cease to function as of the 2105 release and any jobs that use these OpenAPI versions will fail after the upgrade to 2105. We therefore strongly recommend that you cancel or delete any scheduled jobs that use these OpenAPI versions, and replace them with jobs using newer OpenAPI versions.

If you haven't already used the 1808.0.0 OpenAPI versions, you will not be able to schedule a job using them as of 2011.

Deprecation of OpenAPI Versions [page 120]









Integration As announced in SAP IBP 2008, the following OpenAPI versions will no longer be available as of SAP IBP 2102:

● 1805.0.0_FULL● 1805.0.0_TRANS

If you are using 1805.0.0 OpenAPI versions, you will get a warning about the deprecation, but you can continue to use them in the 2011 release of SAP IBP. Note that these OpenAPI versions will cease to function as of the 2102 release and any jobs that use these OpenAPI versions will fail after the upgrade to 2102. We therefore strongly recommend that you cancel or delete any scheduled jobs that use these OpenAPI versions, and replace them with jobs using newer OpenAPI versions.

If you haven't already used the 1805.0.0 OpenAPI versions, you cannot schedule a job using them as of 2008.





Integration As announced in SAP IBP 2005, the following 1802.0.0 OpenAPI versions are no longer available as of SAP IBP 2011:

● Inbound integration: 1802.0.0_FULL, 1802.0.0_TRANS

● Outbound integration: 1802.0.0_OUTBOUND

NoteThese OpenAPI versions have ceased to function as of the 2011 release and any jobs that use these OpenAPI versions will fail after the upgrade to the 2011 release of SAP IBP. We therefore strongly recommend that you cancel or delete any scheduled jobs that use these OpenAPI versions, and replace them with jobs using newer OpenAPI versions.






Order-based planningUser assistance


Planning algorithm

The user assistance for order-based planning includes a new table that lists the supported functions per planning run and planning algorithm.

New Table: Supported Functions per Planning Run in OBP (Documentation Enhancement) [page 123]


Changed

Must know


Model configuration

Previously, there was no default time zone specified in the OBP planning areas and when you imported an external data source, it was assigned the time zone of its location. Now the default time zone in the OBP planning areas is UTC.

Please note that this change will be only applied after you reactivate your planning area after the upgrade to SAP IBP 2011.

Default Time Zone in OBP Planning Areas [page 124]

Cross applications

NewPrepare next release

Administrator/configuration expertBusiness user


The new Change History Analysis app is now available. You can use this new app to view and analyze the effects of changes to key figure data. It also offers you the option to save your filter criteria as a view that the administrator can share with other users using the Content Management app.

If you have been using the old Change History app, the new Change History Analysis app is added automatically to your launchpad.

This app is the successor of the old Change History app. We plan to remove the old app with 2105. To prepare, we recommend that you familiarize yourself with the new app by the upgrade to 2105 at the latest.

New App: Change History Analysis [page 124]

Cross applications



The Manage Master Data app provides access to all the master data managed in SAP IBP by your organization. As a planner, you can search, filter, and sort the full set of master data available in your system in a customizable and user-friendly way. As an integration or configuration expert, you can easily check whether external master data has been correctly integrated to SAP IBP.

New App: Manage Master Data [page 126]






Cross applications Must

know

Business user

Web UI The user interface of each app has a property called “semantic object”, which is used to construct the app URL in the browser. These semantic objects had to be harmonized for technical reasons, and were all changed in this process. For this reason, the browser favorites or bookmarks that you've created for the apps no longer work, and you need to update them right after the upgrade.

NoteAny favorites that you created using the Save as Tile button within the apps are not affected.

Bookmark Update Required [page 127]

Cross applications

New Business user

Web UI In the Planning Calendars app, you can now display the public holidays of factory calendars on which your planning calendars are based.

Public Holidays in the Planning Calendars App [page 127]

Cross applications


Application job

The Copy Version Operator and the Delete Version Operator now process data in packages rather than processing it all in one single batch. This new way of processing the data can lower memory consumption. Information about the number of packages that is processed or the processing status is now shown in the application log.

Enhancements for Copy Version Operator and Delete Version Operator [page 128]

Cross applications


SAP IBP, add-in for Microsoft ExcelGlobal configuration parameterApplication job

As a planner, you can now display data in your local time zone.

Local Time Zones [page 129]





Exception management

New Business user

Web UI You can now do the following in the Monitor Custom Alerts app:

● You can view calculation level attributes in separate columns on the spreadsheet when you download your alerts to a Microsoft Excel or CSV file.Only the visible columns are downloaded.

● You can view alert metrics of the periods before and after the alert occurence with hashed pattern for a better visualization. This feature is available when you choose to display periods before and after in the alert subscription and when you choose the following chart types in the alert definition: bar, column, dual x-axis bar, and dual y-axis bar.

Enhancements to Monitor Custom Alerts [page 131]

Exception management

NewPrepare next release

Business user

Web UI The following features are now available in the Define and Subscribe to Custom Alerts app:

● You have more options when defining the display of charts for custom alerts, such as defining different colors, appearance, and number formats for key figures.

● You have the flexibility of selecting the calculation level attributes and period that you want to apply as filters for the complementary charts in the underlying subscriptions.

● You can see all custom alert subscriptions: both the ones created by you or shared with you and the ones created by other users and not shared with you. This will allow you to assess the impact that any changes you make to definitions might have on the underlying subscriptions.

This app is the successor of the old Define and Subscribe to Custom Alerts app. The old app is no longer supported and will be deleted from the SAP Fiori launchpad as of 2102. We recommend that you switch to the successor app as soon as possible.

Enhancements to Define and Subscribe to Custom Alerts [page 130]






End-to-end visibility

NewBusiness user

Web UI

New SAP Fiori app

You can now use the new Intelligent Visibility Profiles app to configure the content and appearance of the Intelligent Visibility app.

For example, you can create more than one profile to use in Intelligent Visibility. One profile can include supply charts and the other profile can include inventory charts. Users that have these profiles shared with them can switch between both profiles to view different data.

New App: Intelligent Visibility Profiles [page 133]

End-to-end visibility

New Business user

Web UI You can now do the following in the Intelligent Visibility app:

● You can view alerts from your alert subscriptions for specific scenarios using the Versions/Scenarios filter.

● You can view calculation level attributes in separate columns on the spreadsheet when you download your alerts to a Microsoft Excel or CSV file.Only the columns you see are downloaded.

● You can create public or private variants. If you create a public variant, it is shared with other users in a similar role. You can also set variants created by other users as favorites.


● You can use the Select Profile button to apply a profile that is shared with you or that you've configured in the Intelligent Visibility Profiles app.

Enhancements to Intelligent Visibility [page 132]

Analytics New Business user

Web UI You can now do the following in the Analytics - Advanced app:

● You can use the new Horizontal Waterfall and Vertical Waterfall chart types from the Comparison chart group to view the cumulative increase, decrease, and total result for a set of key figures.To use these chart types, you need a minimum of two key figures and no group by attributes.

● You can navigate to the Web-Based Planning app to quickly change or update data.

Enhancements to Analytics - Advanced [page 134]






Web UI You can now do the following in the Dashboards - Advanced app:


● You can navigate to the alert subscription or definition from the dashboard.

Enhancements to Dashboards - Advanced [page 135]


Web UI The Supply Chain Network app now displays an icon of DDMRP buffers next to nodes that are decoupling points.

Supply Chain Network: Render DDMRP Decoupling Points in Network Charts [page 135]


Web UI You can now filter the chart list in the Supply Chain Network app.

Supply Chain Network: Filter Bar Added to Chart List [page 136]

Analytics Must know



As documented since SAP IBP 2005, as of SAP IBP 2011 it is required for the Supply Chain Network app that you add the master data types needed to visualize supply chain networks to your planning area.

Please adjust and reactivate your planning areas as needed to comply with this requirement.

Supply Chain Network: Required Master Data Types [page 136]

Security New Administrator/configuration expert

Web UI You can now find information about customer-initiated penetration testing in the Security Aspects section of the application help.

Customer-Initiated Penetration Testing [page 139]






Cross applicationsUser assistance


Web UI The following languages are available as system languages for the SAP Fiori apps of SAP IBP:

● Arabic (Saudi Arabia)● Italian (Italy)

Not applicable

New features introduced in previous releases

If you’re interested in what has happened in previous releases, please see What's New for Previous Releases.

1.1 How to Use the What's New Table

Learn how you can use the What's New table for a new release. In particular, find the tasks that you need to perform immediately after the upgrade to a new release, even if you do not plan to use any new features.

The table in the section What's New in SAP Integrated Business Planning <release> lists all news and changes that come with a new release and can be extensive.


https://help.sap.com/viewer/62772a60ce5543e3b46fbd787866b6dc/2102/en-US/7c059da0b73047269f1daaa414e03be9.html

RecommendationStart with identifying the items that require an immediate follow up after the upgrade. To do so, use the respective filter values in the Types column. Just click the blue Filter in the column header, as shown in the following animation:



Here an overview of the tasks and filter values:

Filter Value in Types Column Task Urgency Details


Accomplish the mandatory post-upgrade tasks.

Mandatory

Post-upgrade activities are sometimes required because although we try, we cannot always avoid “disruptive” changes. Post-upgrade activities may include changing configuration or other settings to make sure that the processes you were using previously are running in the same way after the upgrade. They may also require using a new app for existing business processes.

NoteIn general, the upgrade does not require you to reactivate your planning area or install a new version of the SAP IBP, add-in for Microsoft Excel. This typically only happens with new features. But there might be exceptions, which you can find in the table by filtering for Mandatory task after upgrade. The need for a planning area enhancement or a new version of the Excel add-in is highlighted where required.

Must knowTake note of changes that require a changed approach later after the upgrade.

Mandatory

In some cases, a disruptive change does not have an impact on your existing objects or running processes (like items classified with Mandatory task after upgrade). Only if you create objects or start processes later after the upgrade, you need to handle things differently than before the upgrade. For this reason, you need to take note of these changes immediately after the upgrade.

Prepare next release Start preparing the next (!) release.

Highly recommended

Sometimes, we plan disruptive changes for the next release. Typical examples include the following:

● New appA new app introduced in the current release will replace an existing app in the next release. The old app will no longer be available in the next release. Therefore, you need to switch over to the new app by the next release.

● Activation checksA warning of an activation check will be changed to an error. You need to fix the related issue by the next release to be able to activate the planning area.

We want to let you know about such changes one release ahead, so that your company can prepare for the changes before they become effective.


Filter Value in Types Column Task Urgency Details

Changed Take note of smaller improvements and roundoffs of the user interface or features that you are already using.

Recommended

This category can include, for example, rearranged user interface elements or changed user interface texts, improved checks, and more. You might want to draw your business users' attention to these items because they need to familiarize themselves with the changes. This category does not include new features that enhance the functional scope of SAP IBP. To list changed features, just filter the Types column in the What's New table by Changed.

New Identify the new features and enhancements that might be interesting for you.

Optional, on demand

Using the new features, you can enhance your business processes

Grouping according to the type – and business topic of course – is a little coarse-grained when it comes to planning your next activities for handling the new release. Therefore, each change comes with tags in the filter in the Impact column that help you to determine your post-upgrade activities according to various criteria. You might ask yourself: For which new features would I have to enhance and reactivate my planning areas? Which new features require the installation of the new Excel add-in? Are there any new SAP Fiori apps that can help to improve my business processes - but also require training my business users?

To deep-dive into the details for a particular change, please click the link in the respective table row.

NoteWhat’s New information is also available in the SAP Fiori apps that have been enhanced, to inform business users about changes directly in the apps they work with.

1.2 What's New History

Overview of changes since the publication of the sneak preview for SAP Integrated Business Planning 2011.

This section covers the following changes:

● Feature roundoffs provided with the Hotfix Collections for 2011● Major enhancements and corrections to the documentation

For software fixes for 2011, see SAP Note 2937891 (patch collection information note).




What's New History

Document Version Software Version Publication Date Changes

1.5 HFC 7 January 15, 2021 New Software Features

None

Documentation Enhancements and Corrections

Miscellaneous enhancements and corrections

1.4 HFC 6 December 23, 2020 New Software Features

None


Miscellaneous enhancements and corrections, including the following:

As of 2011, the default time zone in the OBP planning areas is UTC (see Default Time Zone in OBP Planning Areas [page 124]).

1.3 HFC 5 December 11, 2020 New Software Features

None



1.2 HFC 4 November 27, 2020 New Software Features

None




Document Version Software Version Publication Date Changes

1.1 HFC 3 November 13, 2020 New Software Features

When using the /IBP/EXTRACT_ODATA_API OData service, it is no longer required to have permission to access all key attributes of a master data type in order to access its other attributes.


Miscellaneous enhancements and corrections, including the following:

Further reference has been added to Normalization about attributes as key figures.

1.0 SAP IBP 2011 October 27 , 2020 No changes since the publication of the sneak preview on October 2, 2020

Preliminary What's New Sneak preview October 2, 2020 Not applicable

1.3 Identity and Access Management

1.3.1 Manage Business Role Changes After an Upgrade

This feature enables you to view changed business catalog dependencies after an upgrade. Additionally, you can now display deprecated business catalogs, view successor catalogs and adopt the required changes in your business roles.

Technical Details

Types New

Available as of 2011



Related Information

How to Manage Changed Business Catalog Dependencies After an UpgradeHow to Manage Deprecated Business Catalogs After an UpgradeManage Business Role Changes After Upgrade

1.4 Administration

1.4.1 New Apps for Exporting and Importing Software Collections

The Export Software Collection, Import Collection, and Extensibility Inventory apps are now supported in SAP Integrated Business Planning. If your system landscape is enabled for extensibility development, the export and import of extension items, such as model entities, is based on the Adaptation Transport Organizer. You can use these apps to create software collections, add extension items to software collections, export and import software collections, and check dependencies between various extension items.

Technical Details

Types Prepare next release


Additional Details

If you have at least two SAP IBP systems in your landscape, for example, a test and a production system, you will be contacted by SAP to evaluate and plan the next steps for enabling your landscape for extensibility development.

If your landscape is not yet enabled for extensibility development, the transport of model entities is based on the Change and Transport System in Application Server ABAP and you can continue to use the Transport Model Entities app. If your landscape is enabled for extensibility development and you start using the three new apps, you will not be able to continue to use the Transport Model Entities app.

Depending on your current landscape setup, the following options are now available:

● If you are working in a two-system landscape, you can create and change extension items in your test system that is enabled for extensibility. You can export the extension items from the test system and import them in your production system using the new apps.

● If you are working in a three-system landscape, the export and import mechanism in your landscape will change. You will only be able to export extension items that have been created or changed in the


https://help.sap.com/viewer/685fbd2d5f8f4ca2aacfc35f1938d1c1/2102/en-US/95d0b4e7975e4bdfb487a3158ddb564a.html

https://help.sap.com/viewer/685fbd2d5f8f4ca2aacfc35f1938d1c1/2102/en-US/9ae9b3aa23fc49d897e50400f7d164ee.html

https://help.sap.com/viewer/685fbd2d5f8f4ca2aacfc35f1938d1c1/2102/en-US/6bbf941a47e348c2a32624a663890756.html

development system that is enabled for extensibility. You will not be able to export extension items that have been created or changed in your test system. The exported new and changed extension items from the development system are imported into the test system. After a successful test in your test system, you need to forward the export from the development system to allow the import into the production system.

Note that when you export a planning area using the new apps, the following dependent entities won’t be included automatically in the export and you have to select them manually:

● Attributes● Master data types● Time profiles

The model entities that can be transported using the old app, can also be exported and imported in your landscape using the new apps. In addition, the following extension items can be exported and imported using the new apps:

● Business roles● SAP Fiori launchpad spaces● SAP Fiori launchpad pages● Settings for change history

Effects on System Administration

The Extensibility - Transport Management - Export (SAP_CORE_BC_SL_EXP) business catalog is now available and must be assigned to the relevant business role to access the Export Software Collection app. The Extensibility - Transport Management - Import (SAP_CORE_BC_SL_IMP) business catalog is now available and must be assigned to the relevant business role to access the Import Collection app. The Extensibility - Extensibility Inventory (SAP_CORE_BC_EXT_INVENTORY) business catalog is now available and must be assigned to the relevant business role to access the Extensibility Inventory app.

When all customers have switched to the new apps in the upcoming releases, the Transport Model Entities app will be deprecated and will be deleted from the SAP Fiori launchpad.

Related Information

Apps for Export and Import of Extension Items

1.4.2 Enhancements to Navigations to Other Systems

In the Manage Navigation to Other Systems app, you can now define static attribute values for some of the target attributes that can be passed to a navigation to an SAP GUI system. This will allow users to navigate to an SAP GUI system and proceed with their tasks more quickly. To support the creation of navigations for order-based planning from SAP IBP to selected order documents in SAP ERP or SAP S/4HANA, new simple master data types have been added to the SAP7 sample planning area.



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/d07b572a4c794ad0a954149d830a941c.html

Technical Details

Types New


Additional Details

For example, if you want to pass the value to the With filter field in the Display Stock/Requirements Situation (MD04) transaction, enter RM61R-DFILT as target attribute and X as value. When a user navigates to the transaction, the With filter checkbox will be selected, which will allow the user to filter the stock/requirements list on the following screen.

To support the creation of navigations for order-based planning from the  Intelligent Visibility  or Web-Based Planning app to the selected order documents in SAP ERP or SAP S/4HANA, the following new simple master data types have been added to the SAP7 sample planning area:

● S7ORDERNAVIGATION● S7ORDERNAVIGATIONHELP

Related Information

Creating Navigations to Other SystemsS7ORDERNAVIGATIONS7ORDERNAVIGATIONHELP

1.4.3 Resource Consumption

The Resource Consumption app now has a simplified UI to make it more user-friendly when monitoring the CPU and SAP HANA memory usage in real-time.

You’ll see the following improvements on the UI:

● Simplified filters have date and time pickers.● Default view displays data at the minute level for the past hour on the current date.● Additional views display weekly, daily, and hourly data.● Reference lines display average memory and CPU consumption levels as a percentage: 60 – orange, 80 –

red.


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/ea71df1d3ead4bbe8e12c286421baa5b.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/420eb90495564cd581fdd10b71018d24.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/10d03a1a1fea40fe82ab8ae954fac529.html

Technical Details

Types New


Related Information

Resource Consumption

1.4.4 Monitor Application Jobs

You can now use the Monitor Application Jobs app to perform the following tasks:

● Schedule jobs from the Application Jobs app by choosing the Schedule button in the Monitor Application Jobs app.

● Schedule a job quickly without having to navigate to the Application Jobs app. These jobs can be scheduled using job templates where all the mandatory parameters are filled.

● Cancel jobs and job chains with statuses Scheduled or In Progress.● Restart a job or a job chain that failed to run successfully; possible statuses for restart are Canceled, User

Error, and Failed.● Copy any single or multi-step jobs regardless of the job status.

Technical Details

Types New


Related Information

Monitor Application Jobs



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/0046a6d87cc742dd9c1552848293ba98.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/220f6f179ff749d4a4a457ad6aa06c74.html

1.4.5 SSL Client Certificate Authentication for SAP_COM_0035 – Planning – Data Services Integration

You can now choose the SSL Client Certificate authentication method for communication scenario Planning – Data Services Integration (SAP_COM_0035).

Technical Details

Types New


Related Information

Configuring the Outbound Communication with SAP Cloud Integration for Data Services

1.4.6 Deprecated App: Maintain Employees

The Maintain Employees (F2288) app has been replaced by Maintain Employees (F2288a).

The Maintain Employees (F2288) app will be removed with the SAP IBP 2105 release. We recommend that you switch to the successor app Maintain Employees (F2288a) as soon as possible.

For more information, see Maintain Employees.

Technical Details

Types New


Must know



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/a2d679579ca36a2be10000000a441470.html

https://help.sap.com/viewer/685fbd2d5f8f4ca2aacfc35f1938d1c1/2102/en-US/c0e1da2b8098498eaa0319e46e6c376f.html

Additional Details

The new Maintain Employees app uses Employee - Master Data (SAP_HCM_BC_EMP_MDT_PC), which is the business catalog of the old app.

Related Information

Maintain Employees

1.4.7 Deprecated Job Template: Delete Application Logs

The application job template Delete Application Logs has been deprecated and will be removed with the SAP IBP 2105 release. The system is now handling the log deletion process and no further action is required.

Technical Details

Types Must know



During the deprecation phase, we recommend that you avoid using the Delete Application Logs application job tempate in scheduled jobs, job chains, and custom job templates.

1.4.8 Maintain Communication Users

With this feature you can assign more than one certificate to a communication user to enable a smooth transition when certificates are exchanged.



https://help.sap.com/viewer/685fbd2d5f8f4ca2aacfc35f1938d1c1/2102/en-US/c0e1da2b8098498eaa0319e46e6c376f.html

Technical Details

Types New


Related Information

How to Create Communication Users

1.4.9 New Types Available in Content Administration App

In the Content Administration app, you can now use the new Change History View (Web-Based) and Intelligent Visibility types.

For more information, see Content Administration.

Technical Details

Types New


Related Information

Change History AnalysisIntelligent Visibility

1.4.10 Spaces and Pages Enhanced

New features were added to the new spaces and pages layout to provide better handling, ease navigation between the different apps involved and enhance translation processes.


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/4bff8d203d4c4b1c8dd25564d1913302.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/2a1006589c010846e10000000a441470.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/4080b7afc41b4421983f7b3b204c900d.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/69b6fc590ae34727acd3b4c334f67757.html

Technical Details

Types New

Changed


Additional Details

The following enhancements will improve the use of both the Manage Launchpad Pages and Manage Launchpad Spaces apps:

● Translating spaces and pages was changed: It is now supported directly and all fields (titles, descriptions and section titles) can be translated. For translation purposes you export and import XML files.

● The apps now offer more flexibility when working on smaller devices: the list of available pages or the catalogs list can be hidden and you can switch easily between the main view and the lists.

● Further enhancements were made in the Manage Launchpad Pages app:○ A new tab shows all spaces a selected page is assigned to.○ The display of issues was improved: the assignment of errors, warnings and information was

structured more clearly and additional information will be displayed for several issues. In addition, the message indicator now indicates with its color the highest message severity.

○ Keyboard navigation with F6 is now also supported when navigating in pages and personalizing pages.○ In the App Finder, the dialog to select a page for the app was enhanced: you can now filter for specific

pages.○ When a section is empty, it is no longer shown on desktop devices. You can still see the section, when

you edit the page.

Related Information

Managing Launchpad Spaces and Pages

1.5 Data Integration

1.5.1 Deprecated OData Service

As previously announced, the /IBP/EXTRACT_SRV OData service is now deprecated and cannot be used any longer. Instead, you can use the /IBP/EXTRACT_ODATA_SRV service to extract key figure and master data from SAP IBP. Using this latter service, you can also import key figure data from SAP Analytics Cloud to SAP IBP.



https://help.sap.com/viewer/0292066056f642f1a0f6d9135e39abaf/2102/en-US/e55f5cc8ccec490f83a00284659bce9f.html

Technical Details

Types Mandatory task after upgrade


Additional Details

As the /IBP/EXTRACT_SRV OData service has been deprecated, you can no longer use the /IBP/EXTRACT_SRV/extract_kf, /IBP/EXTRACT_SRV/extract_md, and /IBP/EXTRACT_SRV/extract_mdt endpoints either.

1.5.2 Authorization Check for /IBP/EXTRACT_ODATA_API

From now on, an authorization check is performed when extracting master data using the /IBP/EXTRACT_ODATA_API OData service. To continue using the service, check the permissions assigned to the relevant business users, and adjust them if necessary.

Technical Details

Types Mandatory task after upgrade


Additional Details

Configure business users as follows:

1. Open the Communication Arrangements app in the Communication Management group.2. Select those communication arrangements that are linked to the SAP_COM_0143 communication scenario.3. Under Additional Properties, select the assigned business user ID.4. Open the Maintain Business User app in the Identity and Access Management group and enter the business

user ID you selected before5. Review the authorization settings of relevant business users using the related business catalogs, the

Manage Attribute Permissions app, and the Manage Permission Filters app. Make sure that users have the required permissions to continue using the service for extracting master data.


1.5.3 New OData Service for Importing Key Figure Data

You can use the new OData service /IBP/PLANNING_DATA_API_SRV to integrate key figure data to SAP IBP from external systems.

Technical Details

Types New



There is also a new communication scenario, SAP_COM_0720, based on which you need to set up the communication arrangement for using the /IBP/PLANNING_DATA_API_SRV service.

Effects on Data Integration

This service was designed to import key figure information from external systems that can call OData service APIs other than SAP Analytics Cloud. If you want to integrate data from SAP Analytics Cloud, please use the /IBP/EXTRACT_ODATA_API service instead.

Related Information

Importing Key Figure Data Using the /IBP/PLANNING_DATA_API_SRV OData Service

1.5.4 New OData Service for Integrating Planning Calendar Data

Using the /IBP/API_PLNGCAL OData service, you can import planning calendar data to SAP Integrated Business Planning for Supply Chain. Via requests, you can create and change planning calendars in the SAP IBP system, and also mark planning calendars for deletion.



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/45a6271e272d4accacc0139632450771.html

Technical Details

Types New


Additional Details

Using the /IBP/API_PLNGCAL service, you can maintain planning calendar data.

NoteTo only extract calendar data, the previously introduced /IBP/CALENDAR_API_SRV service is more suitable.

NoteUsing the /IBP/API_PLNGCAL OData service with SAP Cloud Platform Integration for data services is not supported.


To use the service, you need to set up the communication arrangement based on the SAP_COM_0550 communication scenario.

Related Information

Importing Planning Calendar Data with OData API

1.6 Model Configuration

1.6.1 Switch to Calculation View

In SAP IBP 2011, the rollout of the switch to calculation views is finalized. Calculation view replaces analytic view as data source of the calculation scenario. It is needed to enable further features and to improve performance.


https://help.sap.com/viewer/da797ae2bf6246d58abd417f24915d55/2102/en-US/b4c9d084c43b4f23ad036c81626d3f17.html

Technical Details

Types Must know

Available as of N/A

Additional Details

To find out if calculation views are used as data sources, open the log of an activation that took place after the upgrade to SAP IBP 2011. If the log contains the message Activation generates calculation views as data sources., the system already uses calculation views. In this case, you do not need to do anything.

If the log contains the message Activation generates analytic views as data sources., analytic views are still used in calculation scenarios. In order to switch to calculation view, reactive your planning area.

For more information, see 2773629 .

1.6.2 Normalization

As announced previously, a new normalized data model has been introduced to improve performance, memory utilization, robustness, and scalability in the upcoming releases.

All systems are planned to be migrated to this normalized data model in cooperation with the customers in year 2021.

Technical Details


Available as of N/A

Effects on Configuration

NoteAs of SAP IBP 2105, most of the new features will be supported only in normalized systems. If you want to use these new features, you need to ask SAP to normalize your systems. To prepare your systems for the normalization migration, please complete the steps described in SAP Note 2885814 . Key preparation tasks are to look for suppressible errors in your activation logs, correct invalid configurations, and activate





your planning areas with full scope. These steps need to be completed before your systems can be normalized by SAP.

For non-normalized systems, please note that features that work in 2102 will still do so in 2105. A list of new 2105 features that will only be supported in normalized systems will be made available with the What’s New for 2105. We plan to deliver the preliminary What’s New (sneak preview) on April 12.

For more information about new 2102 features, see New 2102 Features Only Available in Normalized Systems.

1.6.3 Checks for Stored Key Figures Read from Incompatible Input Planning Levels

As part of the normalization project, we provide activation checks that help you to spot and fix erroneous configuration that would prevent the normalization of your data model. These checks indicate if there are calculation definitions where the stored value of a key figure is used at an input planning level other than its base planning level; and whether the input planning level does not have the same set of root and non-root attributes as the base planning level, which is not allowed.

Technical Details


Available as of N/A


In calculation definitions, an input planning level where the stored value of a key figure is used must contain the same set of root and non-root attributes as the base planning level.

This is an existing modeling requirement, which is now supported by five activation checks, implemented as suppressible errors. That is, you can only activate a planning area that contains such calculation definitions if you suppress these errors and activate the planning area with limited scope. This is a temporary solution, available for a couple of releases. We recommend that you correct the invalid calculation definitions as soon as possible.

NoteYou will only be able to use the new normalized data model if you correct the invalid calculation definitions in all planning areas. We recommend that you delete all planning areas that you do not use anymore so that you'll only have to fix these issues in the active planning areas.


https://help.sap.com/viewer/bd21293337754c1098c5cfe28ec6057f/2102/en-US/5c0d233904ea419db3c6e8f659454ab1.html

https://help.sap.com/viewer/bd21293337754c1098c5cfe28ec6057f/2102/en-US/5c0d233904ea419db3c6e8f659454ab1.html

Stored Values of Key Figures, with Different Base Planning Levels, Are Read from the Same Planning LevelMessage: *S* Stored values of KFs, with different base PLs, are read from PL &1

In multiple key figure calculations, where the stored values of key figures are used at the same input planning level, the key figures cannot have different base planning levels.

All key figures that are used as stored inputs at the same planning level must have the same base planning level.

As of the 1911 release, you can only activate a planning area that contains such calculation expressions if you suppress these errors and activate the planning area with limited scope. This is a temporary solution that is available for a couple of releases. SAP recommends that you correct the invalid calculation expressions, if there are any, as soon as possible.

To identify and correct the invalid calculation expressions, proceed as follows:

1. In the Planning Areas app, select a planning area, and choose Check.2. Open the log for the check.

You can navigate to the log from the Planning Areas app, or you can find the corresponding log in the Application Logs app by filtering for the external identifier, which is PA: <ID of the planning area>.

3. Look for the following entry: *S* Stored values of KFs, with different base PLs, are read from PL &1, where &1 stands for the ID of the input planning level.

4. Before making any corrections, check your activation log and look for the error message Stored key figure read from an incompatible planning level. If you have run into this error during activation as well, fix it first as it might solve the problem of stored key figures with different base planning levels.If the problem still persists, proceed as follows:The attachment of the messages in the activation log contains a list of calculations divided into the sections below:○ Calculations where the input planning level of stored key figures is their base planning level.○ Calculations where the input planning level of stored key figures does not match their base planning

levels.Depending on your business requirements, make one of the following changes:○ Use the base planning level of the key figures as the input planning level in the calculation definitions.

Change only the calculations where the input planning level (where the stored value of a key figure is used) is not the base planning level of the key figure. As result, all stored key figures will be sourced from their base planning levels, which is the recommended approach.

○ If your business requirements justify that you use the stored values of key figures at a planning level other than their base planning levels, create a copy of each base planning level (with the same set of root and non-root attributes), and use the stored value of the key figure at this compatible planning level.As a result, all stored key figures will be sourced from a planning level that is compatible with their base planning level, that is, they share the same root and non-root attributes.

○ Select one of the base planning levels listed in the attachment, and for each key figure use it as its base planning level.As a result, all stored key figures sourced from the same input planning level will have the same base planning level.

5. Perform a consistency check on the planning area.6. Activate the planning area.



Input Planning Level Has More Attributes than Base Planning LevelMessage: *S* Calc. &1@&2: PL of input KF &3 has more attr. than base PL &4

In calculation definitions, an input planning level where the stored value of a key figure is used cannot have more attributes than the base planning level of the given key figure. That is, the input planning level of a calculation cannot contain attributes that cannot be sourced from the base planning level.





3. Look for the following entry: *S* Calc. &1@&2: PL of input KF &3 has more attr. than base PL &4, where &1 stands for the ID of the key figure,&2 stands for the ID of the planning level, &3 stands for the ID of the input key figure, and &4 stands for the base planning level.

4. For each listed calculation, make one of the following changes depending on your modeling requirements:○ Use the base planning level of the key figure as the input planning level.○ If you want to use the extra attributes that are not available from the base planning level, create a

calculation (if not yet available) and use the calculated value of the key figure instead of the stored value.

○ Remove these extra attributes from the planning level where the stored value of a key figure is used.○ Use a planning level that has the same attributes as the base planning level.


Input Planning Level Does Not Contain All Root Attributes of Base Planning Level; Calculation Doesn't ExistMessage: *S* Calc. &1@&2: PL of input KF &3 doesn't contain root attr. of base PL.

In calculation definitions, an input planning level where the stored value of a key figure is used must contain all root attributes of the base planning level of the given key figure.





3. Look for the following entry: *S* Calc. &1@&2: PL of input KF &3 doesn't contain root attr. of base PL., where &1 stands for the ID of the key figure,&2 stands for the ID of the planning level, and &3 stands for the ID of the input key figure.


4. For each listed calculation, make one of the following changes depending on your modeling requirements:○ Use the base planning level of the key figure as the input planning level.○ Create a calculation on the input planning level and use the calculated value of the key figure instead of

the stored value. If the aggregation level of the input key figure is lower, use Split Factor Calculation; if it is higher, use an aggregation.

○ Use a planning level that has the same attributes as the base planning level.5. Perform a consistency check on the planning area.6. Activate the planning area.

Input Planning Level Does Not Contain All Root Attributes of Base Planning Level; Calculation Exists

Message: *S* Calc. &1@&2: PL of input KF &3 doesn't contain root attr. of base PL.







4. For each listed calculation, make one of the following changes depending on your modeling requirements:○ Since there is a calculation already defined on the input planning level, use the calculated value of the

key figure instead of the stored value.○ Use the base planning level of the key figure as the input planning level.○ Use a planning level that has the same attributes as the base planning level.


Input Planning Level Does Not Contain All Root Attributes of Base Planning Level; Calculation Is Not Used

Message: *S* Calc. &1@&2: PL of input KF &3 doesn't contain root attr. of base PL.


Furthermore, the calculation is not used in any REQUEST level calculation in the calculation graph.




https://help.sap.com/viewer/bf99e931b8d44aafb4e306ec3602cbdd/2102/en-US/ac4e41554731972de10000000a174cb4.html





4. If you do not want to create a REQUEST level calculation in the calculation graph that is based on this calculation, delete this calculation and all other calculations that are built on it.If you want to use the calculation, make one of the following changes depending on your business requirements:○ Use the base planning level of the key figure as the input planning level.○ Create a calculation (for example, an aggregation) on the input planning level and use the calculated

value of the key figure instead of the stored value.○ Use a planning level that has the same attributes as the base planning level.


1.6.4 Suppressible Errors Expiring in Upcoming IBP Releases

The following suppressible errors will turn into errors in the upcoming IBP releases:

● *S* PL &1 and PL &2: Both cannot be used as base PL of stored key figures● *S* Calculation &1@&2: Expression doesn't start with aggregation function● *S* Stored values of KFs, with different base PLs, are read from PL &1● *S* Calc. &1@&2: PL of input KF &3 has more attr. than base PL &4.● *S* Calc. &1@&2: PL of input KF &3 doesn't contain root attr. of base PL.

After that, you can no longer activate your planning areas with limited scope if these errors occur. Correct the invalid configurations to be able to activate your planning areas.

Technical Details


Available as of N/A

Additional Details

For more information about how to fix these errors, see section Suppressible Errors in the Model Configuration Guide.


https://help.sap.com/viewer/bf99e931b8d44aafb4e306ec3602cbdd/2102/en-US/ca5312546b3948e982fef747e6e829e6.html

1.6.5 Calendar

The calendar (IBP_CALENDAR) function is now available to count with different calendars (integrated from SAP ERP) in key figure calculations.

Technical Details

Types New



Instead of using several complex calculations, use the IBP_CALENDAR function to integrate calendar information into key figure calculations.

Example

In this example, we calculate the value of the DEMANDADJUSTED key figure for two locations using the DEMANDCALENDARID calendar attribute. There are 2 calendars integrated from SAP ERP into this calendar attribute:

● Chinese calendar (CN)● German calendar (DE)

DEMANDADJUSTED@REQUEST = SUM("DEMANDADJUSTED@DAYPRODLOC")

DEMANDADJUSTED@DAYPRODLOC = IBP_CALENDAR("DEMAND@DAYPRODLOC", "DEMANDCALENDARID") * "DEMAND@DAYPRODLOC"

Shanghai has the Chinese calendar assigned to it; whereas Berlin has the German calendar assigned to it. Since the 24th, 25th and 31st of December are non-working days in Germany, the value of the DEMANDADJUSTED key figure is 0 (0 * DEMAND) for the German location. However, they are working days in China, so the value of the DEMANDADJUSTED key figure is 150 (1 * DEMAND) for Shanghai.

For more information about how to use the calendar function, see the Calendar section in the Model Configuration Guide.



https://help.sap.com/viewer/bf99e931b8d44aafb4e306ec3602cbdd/2102/en-US/9877489a7f2b40548dcfea923242d02a.html

1.6.6 New App: Where-Used Information for Key Figures

You can use the Where-Used Information for Key Figures app to display the list of key figures, copy operator profiles, and planning view templates and sheets that use the selected key figures.

Technical Details

Types New


Additional Details

In the Where-Used Information for Key Figures app, select a planning area, and then select the status. Select one or more key figures, and then choose Go. You can now display the where-used list of the selected key figures in the table below.

To be authorized to use the app, make sure that the Where-Used Information for SAP IBP Entities (SAP_IBP_BC_WHERE_USED_PC) business catalog is assigned to your role.

NoteDepending on your user permissions, you might not be authorized to see all objects of the where-used list. To ensure that you can display all dependent objects, make sure that the following business catalogs are assigned to the business role that is assigned to your business user:

● Planning Model ConfigurationSAP_IBP_BC_PLANMODEL_CF_PC

● Copy Operator ProfilesSAP_IBP_BC_COPYOPPROFILE_PC

● Basic Planning TasksSAP_IBP_BC_EXCEL_ADDIN_PC

1.6.7 New Validation Checks

In the Planning Areas app, new modeling requirements and checks have been introduced to prevent erroneous configurations.


Technical Details

Types New


Additional Details

The following modeling requirements and checks have been introduced:

● A planning area that is not enabled for external time series cannot use versionspecific external master data types.

● An aggregation function (SUM, AVG, MIN or MAX) cannot contain an embedded expression; it must have exactly one input key figure.

1.6.8 MIN and MAX with Multiple Inputs

The MIN and MAX functions can have multiple inputs now.

Technical Details

Types New



In the case of several input key figures, there is no aggregation in the MIN and MAX functions; the output is simply the lowest or highest value of the input key figures. If any of the key figure values is NULL, both the minimum and maximum will be NULL as well.

ExampleMINCAPACITY@REQUEST = MIN("MINCAPACITY@MTHPRODLOC")

MINCAPACITY@MTHPRODLOC = MIN("CAPACITYMORNING@MTHPRODLOC", "CAPACITYAFTERNOON@MTHPRODLOC", "CAPACITYNIGHT@MTHPRODLOC")

MAXCAPACITY@REQUEST = MAX("MAXCAPACITY@MTHPRODLOC")



MAXCAPACITY@MTHPRODLOC = MAX("CAPACITYMORNING@MTHPRODLOC", "CAPACITYAFTERNOON@MTHPRODLOC", "CAPACITYNIGHT@MTHPRODLOC")

For more information, see section MIN and MAX with Multiple Inputs in the Model Configuration Guide.

1.6.9 Generate Missing Time Periods

The generate missing time periods (IBP_GENERATE_MISSING_TP) function is now available to generate missing time buckets for the calculation horizon defined by the parameters of the function.

Technical Details

Types New



Until now, it was the responsibility of the consultant or key user to make sure that all time buckets are available and uploaded with data. Using the IBP_GENERATE_MISSING_TP function, you can now generate the missing time periods, which have a default NULL value.

ExampleIn this example, we generate missing time periods for the November 2019 - November 2021 period. The current month is November 2020. We have the following time periods and data available for the ACTUALSREV key figure at the base planning level:

We use the IBP_GENERATE_MISSING_TP function to generate the missing time periods.

ACTUALSREV@MONTHPRODLOCCUSTCURRCURRTO = IBP_GENERATE_MISSING_TP( "ACTUALSREV@MONTHPRODLOCCUSTCURRCURRTO", -12, 12)


https://help.sap.com/viewer/bf99e931b8d44aafb4e306ec3602cbdd/2102/en-US/2cdeb9a7471d4a9e8d9a98d7ffd12168.html

As a result, the existing input key figure values stay the same, and the missing time periods are generated with a default NULL value for the calculation horizon. Please keep in mind that no data is stored in the database. The combinations are stored in the memory until the topmost key figures in the calculation graph of the ACTUALSREV key figure are calculated.

For more information about how to use the generate missing time periods function, see the Generate Missing Time Periods section in the Model Configuration Guide.

1.6.10 Improved Processing of Copy Operator Profiles

The following improvements are now available for processing copy operator profiles:

● To improve the reliability of processing, the system reruns erroneous packages. If a package can’t be processed successfully, for example due to locking issues, the system retries processing the package twice, if necessary.

● For the execution of copy operator profiles where the Clear Values option is set to Yes and there’s no source key figure defined, the system can process packages of key figure groups in parallel. With the new global configuration parameter PARALLEL_PROCESSES_CLEAR, you can define how many packages you want to be processed in parallel. The default value is 3, the maximum value is 5. Increasing this value can lead to out-of-memory situations.



https://help.sap.com/viewer/bf99e931b8d44aafb4e306ec3602cbdd/2102/en-US/61a5c50a67c04c0fb8f6902ded431db8.html

https://help.sap.com/viewer/bf99e931b8d44aafb4e306ec3602cbdd/2102/en-US/61a5c50a67c04c0fb8f6902ded431db8.html

Technical Details

Types New


1.6.11 Where-Used List for Copy Operator Profiles

There are now two where-used features for copy operator profiles:

● The Where Used tab in the Copy Operator Profiles app shows you all application job templates and application jobs that use the copy operator profile.

● The new Where-Used Information for Key Figures app shows you all copy operator profiles a specific key figure is contained in. You can see if the key figure is used as source or target and if it's used for copying within one planning area or between two planning areas. From the list of profiles, you can navigate directly to the Copy Operator Profiles app. For more information, see New App: Where-Used Information for Key Figures [page 61].

Technical Details

Types New


Additional Details

On the Where Used tab in the Copy Operator Profiles app, you see all application job templates as well as all executed, running, and scheduled application jobs used to run the copy operator profile. Via the View Settings you can display a number of KPIs like Runtime, Values Read, or Values Written. You can compare and evaluate the application jobs from the past and adapt the scheduled jobs, if necessary, using the navigation link.

1.6.12 Usability Enhancements for Copy Operator Profiles

The following usability enhancements are now available in the Copy Operator Profiles app:

● The attribute selection for copying values within a planning area has been enhanced with the Apply To field that was previously only available for copying between planning areas. This field allows you to define if the selection is applied to source key figures, target key figures, or both.


● In the processing options, there's a new option for defining how attribute selections from the copy operator profile are combined with user selections. If you select Restrict Selection from This Profile, the selections you specify when you schedule a job, further restrict the selections from the profile.

● When you copy a planning area, you can now also copy the related profiles for copying between planning areas, if the copied planning area is used as a source planning area.

● When you schedule a Copy and Disaggregate Key Figure Operator with a daily time profile level, you can now easily select a specific date by using the new date picker.

Technical Details

Types New


1.6.13 Usability Enhancements for the Planning Areas App

Various usability enhancements have been implemented for the Planning Areas app concerning snapshot definitions, key figures, attributes, and navigation.

Technical Details

Types New


Additional Details

● The Snapshots tab has been enhanced as follows:○ There is now no length restriction for the IDs of input key figures for snapshot definitions. In cases

where the resulting snapshot key figure ID would be longer than 32 characters, the system automatically truncates the ID when generating the ID of the snapshot key figure. The shortened ID is available (but hidden by default) in the Input Key Figures table.

○ You can change the maximum number of snapshots (Number of Snapshots field) even after saving the snapshot definition. The change takes effect with respect to operator runs after the next planning area activation.

○ You can view the status (active, inactive or pending deletion) of the snapshot definition and the assignment status of the input key figures. Also, the Restore Active Instance option is now available for snapshot definitions.



○ When creating a new snapshot definition, you can make settings for the snapshot operator and redo snapshot operator to be generated. You can set an Interactive, Batch or Filter Mode for the operators.The IDs of the relevant snapshot/redo snapshot operators are shown in the snapshot definition worklist.

Other enhancements for the app include the following:○ On the Key Figure (details) and Edit Key Figure screens, a new Attribute as Key Figure Definition section

is available for key figures created from attributes, which gives you easier access to that information when you need to modify the key figure.

○ From the Key Figure (details) screen and the Key Figures tab of Focus Mode, you can navigate to the Key Figure Calculations app and view the complete calculation graph for the key figure selected by clicking the new Show Graph button. The Key Figure Calculations app is also available under Related Apps, allowing direct navigation to the app from any tab of the Planning Areas app.

○ To support the upload of data into your planning area and the analysis of the planning area, a new Root In column has been introduced on the Attributes tab of the Planning Areas app, which enables you to view the number and list of planning levels that an attribute is root in. The new column is hidden by default. If you choose to display the column, the number of planning levels that the attribute is a root attribute of is shown as a hyperlink. By clicking the hyperlink, you can display the list of the relevant planning levels.The list of all planning levels, which you can display by clicking the number in the Planning Levels column of the Attributes table, is now arranged in groups, according to whether the attribute is a root or non-root attribute in them.

1.6.14 Enhancements for the Comparison of Planning Areas

Various new functions and features are available to support the comparison of planning areas and the download of comparison results.

Technical Details

Types New


Additional Details

The following enhancements have been implemented:

● The Compare Planning Areas app now supports the following object types as well:○ Attributes as key figures○ Snapshots○ Versions


○ Planning operators● On the Compare Planning Areas screen, new popovers are available to provide detailed information on the

following objects:○ Time profile○ Planning horizons○ Attributes○ Planning levels○ Attributes as key figures○ Key figures

You can display the information by clicking on the ID of an item only included in one of the planning areas.● You can now export comparison results to CSV files from the Compare Planning Areas app. After

performing your comparison and filtering comparison results as needed, you can download the filtered results by clicking the (Export to CSV files) icon.

● The Compare in CSV function is now also available for snapshot definitions. When you download comparison results from the Planning Areas app, or the Sample Model Entities app, a separate file is generated for snapshot definitions.

1.6.15 Activation Check for Fixing-Enabled Key Figures with a Wrong Generated Key Figure Assignment

As previously announced, as of the 2005 release you can only activate a planning area containing the error *S* Key Figure &1 has version assignment problem in Version &2 if you suppress the error and activate the planning area with limited scope.

The error will become non-suppressible in the 2102 release, therefore we recommend that you resolve the inconsistency as soon as possible.

Technical Details



Additional Details

To identify and correct the inconsistency, proceed as follows:





3. Look for the following entry: Key Figure &1 has generated key figure assignment problem.4. For each listed key figure, perform the following steps:

1. Activate the planning area, choosing Limited Scope, with Dependencies or Limited Scope, No Dependencies. There will be cases when your activation fails. Go on to step b nevertheless.

2. Deselect the Enable Fixing checkbox and save the key figure.3. Select the Enable Fixing checkbox and save the key figure.4. Again: deselect the Enable Fixing checkbox and save the key figure.5. Again: select the Enable Fixing checkbox and save the key figure.

NoteThese two steps might seem redundant but they are needed for resolving some special cases of the problem, therefore should not be skipped.

6. Perform a check on the planning area, and – provided it doesn't contain any errors – perform a full-scope activation. If the planning area does contain errors, choose Limited Scope for your activation.

1.6.16 Activation Check For Fixing-Enabled Key Figures with a Version Assignment Problem

As previously announced, as of the 2008 release you can only activate a planning area containing the error *S* Key Figure &1 has version assignment problem in Version &2 if you suppress the error and activate the planning area with limited scope.

The error will become non-suppressible in the 2105 release, therefore we recommend that you resolve the inconsistency as soon as possible.

Technical Details



Additional Details

To identify and correct the inconsistency, proceed as follows:



3. Look for the following entry: Key Figure &1 has version assignment problem in Version &2.


4. For each listed key figure, perform the following steps:1. Deselect the Enable Fixing checkbox for the key figure.2. If the key figure isn't assigned to the version, assign it and save it.3. Select the Enable Fixing checkbox and save the key figure again.4. Perform a check on the planning area, and - provided it doesn't contain any errors - perform a full-

scope activation. If the planning area does contain errors, choose Limited Scope for your activation.

1.7 Unified Planning Area (SAPIBP1)

1.7.1 Unassignment of Attributes Used in Inventory Optimization

Attributes that are not required for reporting in planning views or analytics have been unassigned from the planning area and planning levels. They still, however, must stay assigned to the master data types.

This change was done to simplify the unified planning area SAPIBP1. Some inventory-related attributes are not needed for reporting purposes, for example, in planning views or analytics. For these attributes, it is sufficient to have them assigned to the master data type only. They can be unassigned from the planning area and the planning levels. This applies to the following attributes:

● LOCATIONPRODUCT○ DISTRIBUTIONTYPE○ SAFETYSTOCKPOLICY○ SERVICELEVELTYPE○ NONSTOCKALLOCATIONHORZION

● SOURCEPRODUCTION○ PDELIVERYTYPE○ PSHIPMENTFREQUENCY○ PRATIOTS○ OUTPUTCOEFFICIENTTS

● SOURCELOCATION○ TDELIVERYTYPE○ TSHIPMENTFREQUENCY○ RATIOTS

Technical Details

Types Changed





You can either copy the 2011 version of the SAPIBP1 sample planning area or manually follow up on these changes. For a detailed description of the changes, see the IBP 2011 for Cross Topics: SAPIBP1 Planning Model Template document.

1.7.2 Adjustment of Key Figure Names and Descriptions

The names and descriptions of the MINCAPAUSAGE and MINCAPAUSAGEVIOLCOSTRATE key figures have been adjusted to be in line with the SAP4 sample planning area. The names and descriptions are now Minimum Resource Capacity Usage and Minimum Resource Capacity Violation Cost Rate.

Technical Details

Types Changed




1.7.3 Activation Checks: Change of Planning Levels

The CALWKPRODLOCRESSRCAGG and CALWKPRODLOCLOCFRRESAGG planning levels have been changed to be in line with enhanced planning area activation checks for aggregated constraints key figures. Therefore, the PRDID attribute was removed from the two planning levels. For more information, see Change to Planning Levels in Sample Planning Areas [page 115].


http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fcontent%2Fdam%2Fproductfeatures%2Fassets%2F00033%2F089E017A62AB1EDABB8C21A569E8A0EB%2Fpresentations%2FIBP_2011_for_Cross_Topics_SAPIBP1_Planning_Model_Template.pdf




Technical Details

Types Changed




1.7.4 Adjustment of Attribute Name and Description

The name and description of the CUSTCOUNTRY attribute have been adjusted. They are now Customer Country/Region.

Technical Details

Types Changed




1.7.5 Change of Request Level of HCONVRECOMMENDEDSAFETYSTOCK Key Figure

The request level of the HCONVRECOMMENDEDSAFETYSTOCK key figure has been changed to AVG. The AVG request level is suitable because the disaggregation mode of the RECOMMENDEDSAFETYSTOCK key figure is set to Copy Value. The change avoids data inconsistencies for calendar weeks that split into two technical periods.







Technical Details

Types Changed




1.7.6 Change of Disaggregation of STATISTICALFORECASTQTY Key Figure

The STATISTICALFORECASTQTY key figure is now disaggregated by the DISAGGFACTOR key figure when statistical forecasting is run on an aggregated level.

When you run statistical forecasting on an aggregated level, for example, product customer level, then until the last release output values were disaggregated equally to the product location customer base planning level. From this release, there's a new key figure to improve the disaggregation: DISAGGFACTOR. It is used as a proportional factor to disaggregate the forecast. To calculate this proportional factor a new forecast model, Calculate Disaggregation Factor, is shipped as part of SAPIBP1.

Technical Details

Types Changed









1.7.7 Consideration of Change Points in SAPIBP1 Forecast Automation Profile

Change points are now considered by the SAPIBP1 (Time Series Analysis) forecast automation profile. When you want the system to consider change points when performing time series analysis, use the corresponding option in the Manage Forecast Automation Profiles app. The Consider Change Points option is selected by default in all new forecast automation profiles, but it is not selected in the profiles that were created in earlier releases of IBP. This means that your previously scheduled application jobs are not affected until you change the default setting in the relevant forecast automation profiles.

Technical Details

Types New




1.7.8 SAPIBP1: Dynamic Lag for Propagation of Forecast Error

With the addition of a new master data type and two new key figures, dynamic lag is now available when calculating inventory targets for each location in a multistage supply chain network.

Technical Details

Types New






Additional Details

For more information, see Dynamic Lag for Propagation of Forecast Error [page 97].



1.7.9 Unit of Measure Conversion for Output Key Figures

You can now use unit of measure conversion for the DEPENDENTCUSTOMERDEMANDMEAN and DEPENDENTCUSTOMERDEMANDSTDD output key figures. Two helper key figures have been introduced for this purpose.

Technical Details

Types New




1.7.10 Change of Default Optimizer Parameters in S&OP Operator Profiles

The default setting for whether violations of minimum aggregated constraints are possible has been changed. Previously, the default setting was that these violations were not allowed, that is, they were treated as a hard constraint. From release 2011, they are allowed by default, that means, they are treated as pseudo-hard






constraint. The new default is pseudo-hard because hard aggregated constraints can often lead to solutions that are not feasible.

In the S&OP operator profiles for the optimizer algorithm, the default state of the switch was OFF (not allowed). The default state of the switch has now been changed to ON (allow). The following violations are now allowed by default:

● Violations of minimum aggregated constraints for customer transports● Violations of minimum aggregated constraints for transports● Violations of minimum aggregated constraints for production● Violations of minimum aggregated constraints for inventory

This change affects the following S&OP operator profiles that are shipped with SAPIBP1:

● 102 (Time-Series-Based Supply Planning Optimizer)● 104 (Time-Series-Based Supply Planning Optimizer - Fair Share)

The new setting is selected by default in all new S&OP operator profiles, but it is not selected in the profiles that were created in earlier releases of IBP. This means that your previously scheduled application jobs are not affected until you change the setting in your S&OP operator profiles.

Technical Details

Types Changed


Additional Details

For more information, see Change of Default for Minimum Aggregated Constraints in S&OP Operator Profiles App [page 114].



1.7.11 Change of Key Figure Calculations





The calculations of the HDEMANDRATIO and HAGGCONSENSUSDEMANDQTYRO key figures have been changed to enhance the disaggregation in driver-based planning. The planning level of the input key figure was changed from MTHRO to MTHROPRDFAMCUSTREG.

Technical Details

Types Changed




1.7.12 Change of Attributes Related to Lead Time

Attributes that are related to lead time in the IBPSOURCELOCATION and IBPSOURCECUSTOMER master data types have been changed. From the IBPSOURCELOCATION master data type, the LEADTIME attribute was removed. For the IBPSOURCECUSTOMER master data type, the new CLEADTIME attribute was assigned and the LEADTIME attribute unassigned.

Technical Details

Types Changed









1.7.13 Simplification of Technical Key Figures in Demand Sensing

Several technical key figures will be removed from the SAPIBP1 sample planning area in the 2102 release of SAP Integrated Business Planning to be in line with the SAP6 sample planning area.

Technical Details



Additional Details

For more information, see Simplification of Technical Key Figures in Sample Planning Area [page 90].

1.7.14 New Key Figures: Late Delivery for Inter-Subnetwork Demand


This feature introduces two new input key figures and one new output key figure, as follows:

● IPU Late Delivery Cost Rate (IPULATEDELIVCOSTRATE)An input key figure that defines the costs per piece and per period when dependent demand for a subnetwork is delivered late.

● IPU Late Delivery Maximum Periods (IPULATEDELIVMAX)An input key figure that specifies the maximum number of periods for which a subnetwork's dependent demand can be delivered late.

● Amount of IPU Demand Delivered Late (IPUDELIVEREDLATE)An output key figure that shows the amount of a subnetwork's dependent demand that has been delivered late in a particular period



Technical Details

Types New




Related Information

Late Delivery for Inter-Subnetwork Demand [page 113]

1.7.15 Unassignment of Attributes from Planning Areas

In normalized planning areas, the PLUNITID1 and PLUNITID2 attributes no longer have to be assigned to the planning area. They still, however, must stay assigned to the PLANNINGUNIT master data type.

Technical Details

Types Changed









1.8 SAP IBP, Excel Add-In

1.8.1 New Excel Add-in Version

With SAP Integrated Business Planning 2011, the SAP IBP, add in for Microsoft Excel 2011.2.0 is available. For more information about the versions of the Excel add-in, see 2394311 .

NoteIn general, the upgrade to SAP IBP 2011 does not require that you install the new version of the Excel add-in. You can decide to install it at any point in time when you wish to use the new features; however when you do, please note that .Net Framework 4.7.2 or higher is required for the new version of the Excel add-in. The new features that become available with the Excel add-in 2011.2.0 are described in the 2011 documentation.

1.8.2 Removing a Global Configuration Parameter

For some time now, a second query has been available for the Excel add-in that reads data from the database using the filters in the planning view. Until now, you could switch between the old and the new query using the NEW_QUERY parameter. Since the new query is the basis for many existing and future new add-in features, we have made it the standard query as of 2011. The old query is no longer available. Therefore, we have removed the parameter NEW_QUERY. Please note that this change has no impact on end users.

Technical Details

Types Changed


1.8.3 System Behavior Adjustment for Applied Invalid Attribute Filters

In some cases, attribute-based planning filters become invalid. This can happen when attribute values that were once set as filters are removed from SAP IBP, therefore they cannot be used for filtering any longer. In the past, invalid attribute filters were ignored by application jobs that were run from the Excel add-in; the application job ran without a filter, processing mass-amounts of data.

From version 2011.2.0. of the Excel add-in – if all attribute filters applied are invalid – an application job launched from the add-in provides the same output as one launched from the WebUI. It is executed, however, no data is processed.




Technical Details

Types Changed


Related Information

Filters in Planning Views

1.8.4 Sorting in Planning Views

You can now sort attribute values in planning views. Rules for this can be set based on standard and custom logics.

Beside ascending (A-Z) or descending (Z-A) sorting, you can apply custom rules. For example, you may pin your top three customers to the beginning of the attribute value list and put the worst performing three customers to the end. In between, you can set the sorting rule to ascending (A-Z).

Technical Details

Types New


Additional Details

Sorting rules can be applied to most attributes displayed in your planning view, with the exception of time attributes such as Day Weight Factor, as well as the change history based calculation attributes such as Change ID.

Effects on Business Users

Custom sorting rules can be saved, updated and deleted. If you are using planning view templates or favorites, they are saved as part of the favorite or template definition, hence they can also be shared with other users along with the templates or favorites that you are sharing.


https://help.sap.com/viewer/b28ffdd739bf45678ef36c44e64652d7/2102/en-US/4d93235589f5eb14e10000000a4450e5.html


Due to performance considerations, the number of attribute values that can be handled via custom sorting is limited through the new global configuration parameter MAX_SORTING_VALUES.

Related Information

Sorting in Planning Views

1.8.5 Folders for Filters

Filters are saved by default in a flat list, but if you have many of them, you can use this feature to arrange them in folders. Both attribute-based and value-based filters can be organized this way, and you can manage the folders either from the Edit Planning View window or directly by choosing the Organize button in the Filter drop-down of the Planning View group in the SAP IBP ribbon.

Technical Details

Types New


For more information about folders for filters, see Filters in Planning Views.

1.8.6 Basic Planning Tasks Business Catalog Setting

As of 2011, the business catalog Basic Planning Tasks SAP_IBP_BC_EXCEL_ADDIN_PC is mandatory for users who want to use the Excel add-in.

NoteApplicable to all SAP IBP users, those who do not have their business roles and business users assigned to this business catalog will not be able to use the add-in after release date.



https://help.sap.com/viewer/b28ffdd739bf45678ef36c44e64652d7/2102/en-US/ea426f7ae7b34a73b20823750ad2ccd5.html

https://help.sap.com/viewer/b28ffdd739bf45678ef36c44e64652d7/2102/en-US/4d93235589f5eb14e10000000a4450e5.html

Technical Details

Types Must know


For more information about this business catalog, see Business Catalogs.

1.8.7 Filtering Planning Views in Offline Mode

You can now apply Microsoft Excel filters to SAP IBP planning views in offline mode.

The option to filter offline workbooks increases the usability of planning views for business users who don’t have SAP IBP, add-in for Microsoft Excel installed.

Technical Details

Types New


Related Information

Filtering Planning Views in Offline Mode

1.8.8 .NET version upgrade

With the upcoming SAP IBP, add-in for Microsoft Excel 2102.2.0, which is planned to be released in February 2021, we are planning to raise the minimum allowed .NET version to 4.8.

Technical Details




https://help.sap.com/viewer/685fbd2d5f8f4ca2aacfc35f1938d1c1/2102/en-US/f320ac2954b94cc8bbf9e6c7ea399b83.html

https://help.sap.com/viewer/b28ffdd739bf45678ef36c44e64652d7/2102/en-US/0f2fa3b8b42046639ecd35c720b3e8ba.html


It will be mandatory to upgrade the .NET version to 4.8 or higher in order to install the 2102.2.0 version of the add-in.

NoteInstalling the new version of the .NET framework is not mandatory if you do not plan to upgrade your Excel add-in version.

1.9 Demand Planning

1.9.1 Settings for Phi in Automated Exponential Smoothing

In the Manage Forecast Models app, you can now define upper and lower ranges for the phi coefficient in forecast models containing the automated exponential smoothing algorithm.

Technical Details

Types New


Additional Details

If the Enable Trend Dampening option is selected for a forecast model, trends are gradually eliminated from the forecasts based on the phi parameter. This parameter was previously optimized between 0 and 1 by the system, which often resulted in inaccurate results because the trend could be completely dampened or not dampened at all. Now you can specify smaller ranges to improve the quality of the forecasts.

1.9.2 Outlier Correction for Seasonality and Trend

You can now set the outlier correction algorithm to consider the results of time series analysis during the preprocessing steps of forecasting. If you do so, the algorithm will detect and correct outliers that significantly differ from the identified patterns of trend, seasonality, or both.



Technical Details

Types New


Additional Details

This new functionality can help the algorithm find outliers that don’t vary significantly from the mean or median but do vary from the seasonality or trend pattern in the data. It can also prevent the algorithm from wrongly identifying values as outliers because they are parts of a pattern of seasonality or trend. For example, the highest value in a trend may wrongly be considered an outlier and corrected with the selected method. This can be avoided if the trend property is considered by the algorithm.

For the detection of outliers, the algorithm divides the time series into trend, seasonality, and a residual component. Then it checks the data against the residual and detects any value that significantly differs from it.

For the correction of outliers, the algorithm uses the correction method you select. The following new methods are available:

● No Correction● Adjustment to Seasonality and Trend● Adjustment to Seasonality and Trend with Tolerance

Please check the application help for a detailed explanation of these settings.

Both adjustment methods involve the calculation of moving average, for which the algorithm needs information on the subset size, which is also known as the smoothing window. If trend and seasonality are both found in the time series, the algorithm uses the length of the seasonal cycle as the smoothing window. If only trends are found in the time series, it applies the smoothing window that you define for the algorithm in a new field.


This new option is disabled by default, so it won’t have an impact on the calculations that are based on your existing forecast models.

Related Information

Outlier Correction


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/9a458154c2652357e10000000a44176d.html

1.9.3 Forecast Deleted After Phase-Out End Date even if History is Missing

When the Disregard Leading Nulls option is selected for a forecast model in the Manage Forecast Models app and no historical data is available for a planning object, the system doesn’t calculate the forecasts but keeps the results of the preceding forecasting job instead. Previously, this also meant that the system couldn’t consider the phase-in and phase-out dates specified in the Manage Product Lifecycle app since the last successful run. Now, if the phase-out end date is maintained for a planning object, the system deletes the forecast values for the periods after that date even if the most recent job didn’t run successfully due to the lack of sales history.

Technical Details

Types Changed


Additional Details

This functionality is useful when you decide to phase out a product that stopped bringing revenue, but for future reference you want to keep the last forecasts calculated for future periods before the phase-out date. The values for the periods after that date are usually not required and can now they be deleted.

Note that the forecast values are only deleted until the end of the forecast horizon that was specified in the forecast model used by the most recent application job.

Related Information

General SettingsPhase-In and Phase-Out Planning for New Products

1.9.4 Seasonality Handled by Change Point Detection

In forecast automation, you don’t need to run time series analysis anymore before running change point detection on a data set.



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/8c481b3a66194be2a2b5838be3d9732b.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/202c00d3378f4d05943c6a68661c4896.html

Technical Details

Types Changed


Additional Details

Previously this was recommended because change point detection was not executed for a planning object if time series analysis found seasonality or intermittency in its history. Now both patterns are identified by change point detection itself.

When seasonality is found in a time series, it doesn’t prevent change point detection from running anymore but it has an impact on the results. This means that major changes are not identified as change points if they’re caused by a seasonal pattern. For example, no trend change or level shift is identified for December if time series analysis finds that the higher values in that month are caused by a yearly seasonal pattern related to the holidays.

When intermittency is found in a time series, change point detection stops and doesn’t bring any result for the affected planning object.

Related Information

Change Point Detection

1.9.5 Categorical Variables for MLR and GBDT

For each independent variable you choose for the multiple linear regression (MLR) and gradient boosting of decision trees (GBDT) algorithms Manage Forecast Models app, you can now specify if it is a categorical variable or not.

Technical Details

Types New



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/be9bc5e98fc244269e18aab55432f386.html

Additional Details

Categorical variables allow the algorithms to learn from sales patterns connected to events in the past that are expected to occur again in the future in varying periods. You can mark the past and future periods of holidays, sport events, promotion campaigns, and many other events in this way.

For example, a holiday such as Easter has a different date each year. If you define a categorical variable for the holidays, you can choose to save a number such as 100 in it for Easter, and the algorithms will interpret that number as a code, not as a value. They will learn that sales values are higher in the weeks marked by 100, and they will forecast higher sales values for future periods with the same code.


The checkbox you can use to set an independent variable as categorical is disabled by default. You can enable it both in exsting and new forecast models if you wish.

Related Information

Multiple Linear RegressionGradient Boosting of Decision Trees

1.9.6 Time Series Analysis for Demand Sensing

In the Manage Forecast Models app, you can now set the system to automatically run time series analysis for the demand sensing (full) algorithm.

Technical Details

Types New


Additional Details

When this option is selected, sales history is statistically analyzed to identify trends and other characteristics, and the outputs of this analysis guide machine learning steps to refine weekly optimized sensed demand further. Through this functionality, the demand sensing algorithm avoids extreme outputs that are either too



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/d857975618ad292fe10000000a441470.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/a2a3eada1d954aeaaaa8259ac2720767.html

high or too low compared to sales history characteristics. It also identifies and handles trending demand situations better.

NoteTime series analysis in demand sensing is based on a different logic than the time series analysis you can run via a Forecast Automation application job.

For example, without an analysis of the time series, the algorithm would forecast low sensed demand values for some periods due to low open order levels. However, when time series analysis is run and doesn’t find any downward trends in the sales history, the algorithm pulls up the lower sensed demand values to be more in line with the historical sales characteristics.

We strongly encourage you to activate this functionality as it improves forecast accuracy.

Although this option is not available for the demand sensing (update) algorithm, it will still influence the results of the update runs if it is selected for the demand sensing (full) algorithm. This is because the machine learning outputs are generated and saved during a demand sensing (full) run and the demand sensing (update) run uses this information to update sensed demand according to latest data.

For any new product that is mapped to reference products, only the new product's own sales history after its phase-in end date will be used for this time-series analysis step. Data borrowed from the reference products will not be analyzed.


This new option is disabled by default, so it won’t have an impact on the calculations that are based on your existing forecast models.

1.9.7 Snapshot Key Figure Becoming Optional in Demand Sensing

You don’t have to specify the snapshot key figure anymore for the demand sensing (full) algorithm in the Manage Forecast Models app.

Types Changed


Additional Details

Up until now, a key figure holding the lag-based snapshots of the consensus forecast has been a mandatory input for demand sensing. This key figure is called Consensus Demand Snapshot and Demand Planning Qty


Snapshot in SAP6 and SAPIBP1 sample planning areas, respectively. Providing this data helps demand sensing analyze input forecasts at different lags during its machine learning steps and is the preferred approach.

Starting with IBP 2011, you can leave the Snapshot Key Figure field empty if you wish. If you do so, demand sensing uses the Consensus Forecast key figure for every lag in its machine learning algorithm while predicting sensed demand for each week in the planning horizon.

Leaving this input empty and letting demand sensing use the Consensus Forecast key figure for every lag in its prediction is useful in the following cases:

● If the consensus forecast for the week doesn’t change by much over time● If you don’t have enough historical lag-based snapshots of the consensus forecast but you still want to

start using demand sensing

CautionYou should leave the Snapshot Key Figure field empty unless you know for sure that you have enough historical data for the snapshots. If you enter a key figure in this field, it will be used as-is, meaning that the missing data in the key figure will not be autofilled. This case may lead to demand sensing defaulting to the input consensus forecast during its weekly optimization steps or to issues with demand sensing outputs.

1.9.8 Simplification of Technical Key Figures in Sample Planning Area

Several technical key figures will be removed from the SAP6 sample planning area in the 2102 release of SAP Integrated Business Planning.

The goals of this simplification process are the following:

● To simplify configuration requirements by removing certain key figures that will no longer be used in demand sensing.

● To replace the numerous profile weights and daily profile key figures that are currently in use with one set of daily profile key figures that show the final weighted profile after daily disaggregation is performed.

After the IBP 2102 release, if you still have key figures in your planning area that were removed from the sample planning areas, you can run demand sensing without having to change anything: these key figures will just simply not be populated. You can then remove these key figures any time to simplify your configuration.

In IBP 2011, you should not create any new analytics and calculations based on the technical key figures that are planned to be removed.





Additional Details

The following changes will be made in the SAP6 sample planning area to the key figures used for demand sensing:

Key Figure CategoryExample Key Figure (Naming Convention) With 2102 New Definition

Bias adjustment detail key figures

FORECASTBIAS Kept

FCTBIASMAPEIMPROV Removed

FCTBIASWEIGHT0

Optional. Removed from SAP6 and SAPIBP1 but the key figure with the right business meaning and right planning level will be populated.

FCTBIASWEIGHT1

FCTBIASWEIGHT2

FCTBIASWEIGHT3

FCTBIASWEIGHT4

FCTBIASWEIGHT5

FCTBIASWEIGHT6

FCTBIASWEIGHT7

FCTBIASWEIGHT8

Open order adjustment detail key figures

FUTUREORDEREDQTYFCTADJUSTMENT

Kept

FUTUREORDEREDQTYWEIGHT

RemovedFUTUREORDEREDQTYINPUTFCTWGHT

FUTUREORDEREDQTYMAPEIMPROV

Extra signal detail key figures (sample key figures for PoS)

CUSTSTORESLSQTYFCTADJUSTMENT (optional)

Kept in SAP6

CUSTSTORESLSQTYMAPEIMPROV (optional)

Removed

Daily disaggregation profile detail key figures

CONSENSUSDEMANDPROFILEWEIGHT

Removed

CONSENSUSDEMANDPROFILE0






Key Figure CategoryExample Key Figure (Naming Convention) With 2102 New Definition



ADJDELIVQTYPROFILEWEIGHT

ADJDELIVQTYPROFILE0

ADJDELIVQTYPROFILE1

ADJDELIVQTYPROFILE2

ADJDELIVQTYPROFILE3

ADJDELIVQTYPROFILE4

ADJDELIVQTYPROFILE5

ADJDELIVQTYPROFILE6

FUTUREORDEREDQTYPROFILE0

Kept with a changed definition

The final daily disaggregation profile for day 1













Total MAPE improvement estimate key figure

TOTALMAPEIMPROV Optional. Removed from SAP6 and SAPIBP1 but will be populated if a key figure with this exact name exists in a planning area.

Related Information

Key Figures Used for Demand Sensing



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/79edd3555520410ee10000000a441470.html

1.9.9 Enhanced Disaggregation of Weekly Promotion Sales Lifts in Demand Sensing

In demand sensing, weekly promotion sales lifts are now disaggregated into days according to the optimal daily demand split determined by machine learning instead of getting equally distributed.

Technical Details

Types Changed


Additional Details

Previously, when the promotion sales lift key figure was used at a weekly level in demand sensing in conjunction with the promotion sales lift elimination pre-processing step, demand sensing used optimal daily split from machine learning to distribute the weekly baseline demand between the days, and then added daily promotion sales lifts by equally distributing its weekly value within the working days. With the new approach, weekly promotion sales lifts are also split into days using the optimal daily split from machine learning instead of getting equally distributed. This approach increases daily sensed demand accuracy.

If you are using a promotion sales lift key figure in your demand sensing forecast models that is at a daily level, there is no change in the logic: demand sensing already respects daily promotion sales lifts during daily sensed demand calculations.

1.9.10 Number of Change Points Shown in the Assign Forecast Models App

A new column in the Assign Forecast Models app shows how many change points were identified by the most recent change point detection jobs that were executed on the various planning objects within the selected planning area and planning level.

If you choose a linked number in this column, you can see the details of the application job that brought the displayed results.


Technical Details

Types New


Related Information

Assign Forecast Models

1.9.11 Upload of Realignment Projects

In the Manage Realignment Rules app, you can now upload realignment projects from a CSV file.

You can use this feature to create new realignment projects or edit existing ones. To get started with a new project, you can download one of the available templates or an existing project as a reference.

The following templates are available for download to show you the structure and columns of the files to be uploaded:

● Template for Master Data and Key Figures● Template for Master Data

To edit or enhance an existing project, you can download it, add or change lines, and upload it again. The upload always processes the complete project.

Technical Details

Types New


Related Information

Uploading Realignment Projects



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/a09c76555545011de10000000a44538d.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/558cd0c5e8f0490fab08e1c8560e57f2.html

1.9.12 Usability Enhancements in Manage Product Lifecycle App

Several usability enhancements are now available in the Manage Product Lifecycle app:

● A log that shows all the changes that were made in the last 30 days is available. You can also see if the assignment level was changed manually in the Settings for Product Lifecycle app or if there were changes by a file upload or by the external OData service /IBP/DEMAND_LIFE_CYCLE_EXT_SRV.You can filter the changes by data type, type of change, action, and by user who made the change.

● You can now undo the changes you made in the mass maintenance view for product assignments and forecast dates. Once you've saved your changes, you can no longer undo them.

● To get a better overview of your product assignments and forecast dates, you can now toggle to a more compact display. This compressed view only shows the first line of the assignments of a new product and the number of assignments for this product but not the assigned products themselves.The new Number of Assignments field indicates how many assignments there are and allows you to navigate to the detailed list of product assignments.If you want to always work with the compressed view, you can save the view as a variant under My Views.

Technical Details

Types New


Related Information

Manage Product Lifecycle

1.9.13 Disable Deletion of Product Assignments, Forecast Dates, and Phase-In/Phase-Out Curves

In the Settings for Product Lifecycle app, you can now specify whether the demand planner is allowed to delete product assignments, forecast dates, and phase-in/phase-out curves.

If you set Delete Product Assignments, Delete Forecast Dates, or Create and Delete User-Defined Curves to No, the Delete buttons and the operation type Delete in the file upload aren’t available in the Manage Product Lifecycle app.


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/5dad8c570c9b6d10e10000000a441470.html

Technical Details

Types New


1.9.14 Preferred Launch Dimension Values

In the Settings for Product Lifecycle app, you can now optionally define a preferred value for your launch dimensions.

In the Manage Product Lifecycle app, the demand planner can filter according to preferred values in the overview screen. If you define a preferred value, you see the forecast dates for this value when you open the detail screen of the Forecast Dates tab in the Manage Product Lifecycle app. To display or hide all forecast dates, use the toggle button.

Technical Details

Types New


Related Information

Settings for Product Lifecycle

1.9.15 Deletion of Product Assignments, Forecast Dates, and Curves Using File Upload

You now have the option to upload files with product assignments, forecast dates, and phase-in/phase-out curves that you wish to delete. To use the deletion feature, choose the operation type Delete in the Upload File dialog. The structure of the deletion file is identical to the one for adding product assignments, forecast dates, and curves. However, in the deletion file only the key fields must be filled.



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/444043ad74b54cd68a21227c6e9a39c2.html

Technical Details

Types New



To disable this feature, the system administrator can set the Delete Product Assignments, Delete Forecast Dates, and Create and Delete User-Defined Curves options in the Settings for Product Lifecycle app to No.

Related Information

Settings for Product Lifecycle

1.10 Inventory Optimization

1.10.1 Dynamic Lag for Propagation of Forecast Error

You can use this feature to apply lagged forecast error inputs to calculate inventory target plans considering the lagged effect of demand variability for upstream nodes in the multistage network.

Technical Details

Types New


Additional Details

The dynamic lag logic in inventory optimization uses each lag-based forecast error coefficient of variation as an input corresponding to the cumulative lead time applicable to a node. For example:

● A Lag 2 based forecast error coefficient of variation is applied to a customer facing node that has a sourcing lead time of two (2) weeks.


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/444043ad74b54cd68a21227c6e9a39c2.html

● A Lag 7 based forecast error coefficient of variation is applied to an upstream node when the upstream node sources a downstream node with a 2 week lead time, and that node is sourced from another upstream node with a lead time of 5 weeks.

● Multiple sourcing cases: For an upstream node, sourced upstream with a lead time of seven (7) weeks, and sourcing two nodes downstream; one with lead time of two (2) weeks and another with a lead time of zero (0) weeks, the lag-based forecast error coefficient of variation applied to the upstream node is based on demand-weighted lead time between 2 weeks and 0 weeks, plus 7 weeks; if the demand is equal between the two downstream nodes, the lag applied to the upstream node is 7 + (2+0)/2 = 8.


A global configuration parameter ENABLE_DYNAMIC_LAG has been added to test the effects of dynamic lag.

When set to YES, dynamic lag is considered. When set to NO or any other value, dynamic lag is not considered. The default parameter value is NO.

The following planning operators are affected by dynamic lag (when enabled):

● Global (multi-stage) inventory optimization● Decomposed (single-stage) inventory optimization

In addition, you can calculate lag-based forecast error coefficient of variation inputs from the Manage Forecast Error Calculation for inventory optimization app.

The following changes must be made to your planning area. They have been made to the SAP3 and SAPIBP1 sample planning areas, so you can use those as a reference.

Add the following key figures:

Key Figure ID Name Base Planning Level Definition More Information

IOLAGFORECAST IO Lagged Demand Forecast

WKPRODLOCCUSTGROUPLAG

IOLAGFORECASTERRORCV

IO Lagged Demand Forecast Error CV

WKPRODLOCCUSTGROUPLAG

HCONVIOLAGFORECAST

Helper Key Figure WKPRODLOCCUSTGROUPLAG

Helper key figure supporting UOM conversion for input key figure IOLAGFORECAST.

To support dynamic lag, the Decomposed (single-stage) inventory optimization operator now consumes the existing key figures Independent Demand Mean (DEPENDENTCUSTOMERDEMANDMEAN) and Independent Demand Standard Deviation (DEPENDENTCUSTOMERDEMANDSTDDEV).

As a result, you must add two new unit of measure conversion helper key figures:




HCONVDEPENDENTCUSTOMERDEMANDMEAN

Helper Key Figure WKPRODLOCCUSTGROUP

Helper key figure supporting UOM conversion for the output key figure DEPENDENTCUSTOMERDEMANDMEAN.

HCONVDEPENDENTCUSTOMERDEMANDSTDD

Helper Key Figure WKPRODLOCCUSTGROUP

Helper key figure supporting UOM conversion for the output key figure DEPENDENTCUSTOMERDEMANDSTDDEV.

Add the new master data type SOURCECUSTGROUPLAG (Master Data Type ID: IBPSOURCECUSTGROUPLAG) to support new output attribute Forecast Error CV Type:

Field Value

Name Lagged Demand Stream

Description Lagged Demand Stream

Type Simple

Attributes for Master Data Type Lagged Demand Stream

Attributes Attribute Description

Key (X) Required (X) Referenced Attribute Notes

PRDID Product ID X X

LOCID Location ID X X

CUSTGROUP Customer Group / Segment

X X

LAG Lag X X Indicates the lead time between when the forecast was created and the forecast date.


Attributes Attribute Description

Key (X) Required (X) Referenced Attribute Notes

FORECASTERRORCVTYPE

Forecast Error CV Type

When equal to user defined CV, the corresponding CV value is not considered for dynamic lag logic. When equal to system calculated CV, the CV is considered for dynamic lag logic.

NoteWhen non-sequential lag inputs (for example, 0, 3 ,5) are used in a forecast error profile, the algorithm calculates the forecast error coefficient of variation values for missing input lags.

When the global configuration parameter ENABLE_DYNAMIC_LAG is enabled, but lag-based forecast error coefficient of variation inputs are not used, the inventory optimization operators calculate inventory targets with no dynamic lag logic.

The inventory optimization algorithm ignores lag-based forecast error coefficient of variation inputs that do not correspond to a cumulative lead time for any node.

Related Information

Global Configuration ParametersDynamic LagMaster Data TypesKey Figures

1.10.2 New App: Inventory Analysis

You can use this new app to create scenarios for inventory-related changes to input demand, supply, and policy variables. Once created, users can view and edit scenarios.




https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/b734d198ebf24ba7b70d6c8b548b93df.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/23060e5681558c5be10000000a44147b.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/c0046454cdeee530e10000000a44538d.html

Technical Details

Types New


Additional Details

The Inventory Analysis app helps uncover the impact of certain scenarios when compared to baseline planning outputs or other scenarios.

With the app, you can create analyses by the following types:

● Demand● Transportation● Production● Inventory Policy


To work with the new app, you have to assign the SAP_IBP_BC_INVANA_PC business catalog to your business role.

Related Information

Inventory Analysis

1.10.3 Incorporate Non-Stocking Push Logic in Inventory Components Operator

With this feature, the Calculate Target Inventory Components operator uses the non-stocking push logic used by the Global (multi-stage) inventory optimization operator to provide a complete calculation of reorder points for networks with non-stocking nodes.


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/a278989106e84e329da4991689d1c8b1.html

Technical Details

Types Changed


Additional Details

The operator uses the following push logic for non-stocking nodes: for the relationship Stocking Node A → Non-Stocking Node B → Stocking Node C, Lead Time and Lead Time Variability between Stocking Node A and Non-Stocking Node B is pushed to Stocking Node C.

The reorder point is a function of lead time, demand, and uncertainty over lead time. In inventory optimization, the calculation of the reorder point sumsthe recommended safety stock and the propagated demand mean over the lead time.

NoteIf the non-stocking node is multi-sourced, then the lead time is not pushed.

Related Information

Inventory Optimization Planning Operators

1.10.4 Master Data Quality Log Messages when Running Inventory Functions

This feature checks the quality of the master data upon running an inventory operator. If there are issues with the master data quality, messages are logged in the business log.

Technical Details

Types New




https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/eafe6454cdeee530e10000000a44538d.html

Additional Details

The table below lists the errors the master data quality check looks for, which operator runs the check, and the message logged if the check fails:

Master Data Check Error Operator Log Message

MOTID attribute not configured in the SOURCELOCATION master data type when it is configured in the SOURCELOCATIONVALIDITY master data type.

Global (multi-stage) inventory optimization

Missing NULL MOTID from SOURCELOCATION master data.

SOURCELOCATIONVALIDITY / MOTID ignored. Incompatible with SOURCELOCATION.

MOTID attribute not configured in the SOURCELOCATIONVALIDITY master data type when it is configured in the SOURCELOCATION master data type.


SOURCELOCATIONVALIDITY ignored. Incompatible with SOURCELOCATION / MOTID.

MOTID attribute is not configured in required planning levels.


Missing MOTID from WKPRODLOCLOCFR planning level.

Missing MOTID from WKPRODLOCLOCTO planning level.

IOFORECAST key figure not included in version.


Missing required key figure IOFORECAST.

CUTSGROUP attribute does not have input data in CUSTOMER master data.


CUSTGROUP data missing in Customer master data

Calculate Target Inventory Components

Decomposed (single-stage) inventory optimization

Related Information

Inventory Optimization Planning OperatorsMaster Data Types

1.10.5 New Optional Parameter in Inventory Optimization Job Templates

You can use this feature to optionally set the current period calculation method for either the Inventory Optimization Operator job template or the Profile Based Inventory Optimization job template.


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/eafe6454cdeee530e10000000a44538d.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/23060e5681558c5be10000000a44147b.html

Technical Details

Types New


Additional Details

You can select one of the following options for Current Period Calculation:

● Execution Time (default) - if no other option is selected, then the job is run with the system time settings, as in previous releases.

● Selected Time - you can select the time and date.● Execution Time in Selected Time Zone - you can select the time zone for the execution time.

Related Information

Time ZonesJob SchedulingUsing Application Jobs to Create and Schedule Inventory Optimization Jobs

1.11 Demand-Driven Replenishment

1.11.1 Enhancements for Demand-Driven Supply and Operations Planning

You can use this feature to run the time-series-based supply planning heuristic in your DDMRP-based planning area to create a weekly rough-cut capacity plan for unconstrained supply planning. Master data types, planning levels, and key figures have been added to allow the heuristic to run in a DDMRP-based planning area. In addition, you must enable supply planning for your area if you wish to use this feature.

Technical Details

Types New




https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/d5fe6f8a635e4c02b7a50cde9c49e696.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/2a7140faec6f42a5943b855fc6b2aabf.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/00d40f2fd8504773af0dd72ee5bba402.html


To enable demand-driven supply and operations planning, the changes listed in this section must be made to your DDMRP-based planning area. The changes have also been added to the SAP8 sample planning area, so you can use that as a reference.

To use the time-series-based supply planning heuristic with a copy of the SAP8 sample planning area, you must switch on Enable Supply Planning under Planning Area Settings in the Planning Areas app. After you enable the setting, the planning area must be activated or reactivated.

CautionIf you do not enable this setting, the time-series-based supply planning heuristic fails with the following error message: The scheduled procedure finished with status "Error”.

Enable Supply Planning is not turned on for the SAP8 sample planning area by default, because copying a sample planning area with this setting enabled also copies additional master data types that are not relevant for capacity buffer reporting. Those master data types support broader use cases for the time-series-based supply planning heuristic. In addition, copying the SAP8 sample planning area with that setting enabled also copies the PRODUCTTO master data type, which is not supported by Supply Chain Network app without additional manual configuration of the planning area.

The following table lists these master data types and attributes required to run the time-series-based supply planning heuristic with demand-driven replenishment, and provides links to more detailed information about the master data type.

Master Data Type Name Assigned Attributes Detailed Information

IBPLOCATIONTO Location To LOCTO Ship-To Location

LOCTODESCR

LOCTOREGION

LOCTOTYPE

IBPRESOURCE Resource CAPACITYBUFFERGREENPCT Resource

CAPACITYBUFFERREDPCT

CAPACITYBUFFERYELLOWPCT

RESDESCR

RESID

IBPPRODUCTIONRESOURCE Production Source Resource PCAPACONSEND Production Source Resource

CONSUMPTIONTS


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/950172553d590c30e10000000a441470.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/dba17255adb4be19e10000000a423f68.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/fea67255adb4be19e10000000a423f68.html

Master Data Type Name Assigned Attributes Detailed Information

PCAPACONSSTART

RESOURCELOCATION Location Resource CAPASUPPLYEXPANSIONTS Location Resource

CAPASUPPLYTS

CONSTRAINTTYPE

RESOURCETYPE

To facilitate the use of the time-series-based supply planning heuristic with demand-driven replenishment, add the following planning areas:

● WKPRODLOC● WKPRODLOCCOMPSRC● WKPRODLOCLOCFR● WKPRODLOCLOCTO● WKPRODLOCNOROOT● WKPRODLOCSRC● WKRESLOC● WKRESPRODLOCSRC

To facilitate the use of the time-series-based supply planning heuristic with demand-driven replenishment, the following key figures must be added to your planning area:

NoteKey figure values for INDEPENDENTDEMAND should be provided for customer-facing product locations so that the supply heuristic can propagate this demand through the network.

Key Figure ID Name Base Planning Level More Information

CAPASUPPLY Capacity Supply WKRESLOC Capacity

CAPASUPPLYEXPANSION Capacity Supply Expansion WKRESLOC Input Key Figures for the Optimizer and the Finite Heuristic Only

DEPENDENTDEMAND Dependent Demand WKPRODLOC Location Product

DEPENDENTPRODUCTIONDEMAND

Outbound Production Demand

WKPRODLOCCOMPSRC Downstream Key Figures

INDEPENDENTDEMAND Independent Demand WKPRODLOC Location Product

INITIALINVENTORY Stock on Hand WKPRODLOC Location Product

INVENTORYTARGET Inventory Target WKPRODLOC Location Product



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/c8a27255adb4be19e10000000a423f68.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/57a937561b12de21e10000000a4450e5.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/ec76385609686f78e10000000a44147b.html



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/c9a19c55cfa8d007e10000000a44538d.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/eb2e44567b94e223e10000000a441470.html




Key Figure ID Name Base Planning Level More Information

MAXINVENTORY Maximum Inventory WKPRODLOC Maximum Key Figures

MAXPRODUCTION Maximum Production Receipts

WKPRODLOCSRC Maximum Key Figures

MINPRODUCTION Minimum Production Receipts

WKPRODLOCSRC Production

NETDEMAND Net Demand WKPRODLOC Location Product

PCAPACONSUMPTION Capacity Consumption Rate of Production Resource

WKRESPRODLOCSRC Capacity

PCAPADEMAND Capacity Demand of Production Resource

WKRESPRODLOCSRC Capacity

PRODUCTION Production Receipts WKPRODLOCSRC Production

PRODUCTIONCOMPONENT Component Usage WKPRODLOCCOMPSRC Upstream Key Figures

PROJECTEDINVENTORY Projected Stock WKPRODLOC Late Delivery

RECEIPT External Procurement/Receipts

WKPRODLOC Location Product

SUPPLY Supply WKPRODLOC Location Product

TOTALRECEIPT Receipts WKPRODLOC Location Product

TRANSPORTDS Transport Supply WKPRODLOCLOCTO Downstream Key Figures

Add the following copy operator: Copy Buffers and On-Hand (for DDMRP) to Supply inventory key figures (for SOP)

The copy operator copies buffers and on-hand inventory to the relevant S&OP key figures.

Add the following operator: Time-Series-Based Supply Planning Heuristic

Related Information

Master Data TypesPlanning LevelsKey FiguresPlanning Operators


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/39194156f7baf81ae10000000a441470.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/39194156f7baf81ae10000000a441470.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/be9136565b0ec44ee10000000a44147b.html




https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/be9136565b0ec44ee10000000a44147b.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/fd596556f2441d58e10000000a4450e5.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/65934c564a9ff81ae10000000a441470.html




https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/a65a6556d5401c58e10000000a4450e5.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/53538993436b4e538c6874b0133529be.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/a20227d611dd4b9f93058dd47e9e4d41.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/c3a244a14ec04c4f83a0a8c774b94876.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/94b0510a0a2944f89f942f63a3e52829.html

1.11.2 Include Prebuilt Stock in DDMRP Buffer Levels

You can use this feature to use prebuild stock as an input to the demand-driven replenishment operators used to calculate DDMRP buffer levels. This can increase the accuracy of the top of yellow and top of green values, and result in more accuracy when the operators calculate the netflow equation and order recommendations.

Technical Details

Types New


Additional Details

You can now configure a prebuild buffer zone key figure that is part of the yellow zone. The prebuild zone does not impact top of red calculation, but is included in the top of yellow and top of green calculations.

It causes replenishment to be triggered earlier in order to prebuild stock in case of capacity constraint scenarios. It also helps avoid false low-on-hand alerts.

The size of the prebuild zone is an input from another process, such as rough-cut capacity planning and is not calculated by the demand-driven replenishment operators.

You can also manually adjust the prebuild buffer zones for specific dates.


To include prebuild stock, the following changes must be made to your DDMRP-based planning area. The changes have also been added to the SAP8 sample planning area, so you can use that as a reference.

Add the following key figures:


PREBUILDZONE Prebuild Zone DAYPRODLOC Prebuild Zone An input from another process such as rough-cut capacity planning (it is not calculated by the demand-driven replenishment operators).




PREBUILDZONEVAL Prebuild Zone Value DAYPRODLOCCUR Prebuild Zone Value Prebuild zone value

DDPREBUILDADJ Adjusted Prebuild Zone DAYPRODLOC Adjusted Prebuild Zone Prebuild delta adjustment.

DDPREBUILDFINAL Prebuild Zone Final DAYPRODLOC Prebuild Zone Final Size of prebuild zone final (after adjustments).

The following key figures need to be changed to include DDPREBUILDFINAL:

● TOPOFYELLOW● HKFDDYELLOWFINALDLTSHIFT● DDEXECLOWYELLOW● AVGONHAND

Please reference the key figures in the updated SAP8 sample planning area for the exact changes.

The following key figures must be changed to remove the prebuild zone:

● DDEXECUPYELLOW● DDEXECUPRED

Please reference the key figures in the updated SAP8 sample planning area for the exact changes.

Related Information

Key Figures

1.11.3 New App: DDMRP Buffer Status Monitoring

You can use this new app to monitor the DDMRP buffer status percentage for the current day, on-hand stock, order recommendations, net flow positions and projected on-hand stock for future dates.

Technical Details

Types New




Additional Details

The list of decoupling points displayed by the DDMRP Buffer Status Monitoring app is highly adaptable, filterable, and sortable. You can view information in multiple ways, including by charts and tables. You can share the data with other users by email, SAP Jam, or as a dashboard tile.


To work with the new app, you have to assign the SAP_IBP_BC_DDMRPSTATUS_PC business catalog to your business role.


We recommend you made the following key figure changes to your demand-driven replenishment-based planning areas so that the data is correctly displayed in the app. The SAP8 sample planning area has been updated accordingly, so you can use that as a guide.

NoteThe DDMRP Buffer Status Monitoring app functions with demand-driven replenishment-based planning areas created prior to IBP 2011 without changes, but the Decoupling Integrity Status column displays blank, and the Projected On-Hand Color column is limited to Lower Dark Red, Lower Red, Lower Yellow, and Green colors, and excess projected on-hand inventory is reported under Green.

● For the key figure Decoupling point integrity status (execution) (DDBUFFERINTEGRITYSTATUS), under Display Settings, deselect Display as Percentage.

● For the key figure Projected on-hand (buffer) status color indicator (DDPROJONHANDSTATUSCOLOR), change the calculation to:DDPROJONHANDSTATUSCOLOR@DAYPRODLOC = IF(ISNULL("DDPROJONHANDINV@DAYPRODLOC") OR ("PERIODID0">"$$PERIODID0CU$$"+"DECOUPLEDLEADTIMEDAYS@DAYPRODLOC"), NULL, IF("DDPROJONHANDINV@DAYPRODLOC"<=0,0,IF("DDPROJONHANDINV@DAYPRODLOC"<"DDEXECTOPOFLOWRED@DAYPRODLOC",1,IF("DDPROJONHANDINV@DAYPRODLOC"<"DDEXECTOPOFLOWYELLOW@DAYPRODLOC",2,IF("DDPROJONHANDINV@DAYPRODLOC"<"DDEXECTOPOFGREEN@DAYPRODLOC",3,IF("DDPROJONHANDINV@DAYPRODLOC"<"DDEXECTOPOFUPYELLOW@DAYPRODLOC",4,IF("DDPROJONHANDINV@DAYPRODLOC"<"DDEXECTOPOFUPRED@DAYPRODLOC",5,6)))))))

NoteThis updates the key figure to distinguish upper yellow and upper red execution zones for projected on-hand. Prior to IBP 2011, excess projected on-hand inventory was classified as key figure value 3, which corresponds to green zone execution.

The following key figure value to color mapping is used:○ 0 – Lower Dark Red



○ 1 – Lower Red○ 2 – Lower Yellow○ 3 – Green○ 4 – Upper Yellow○ 5 – Upper Red○ 6 – Upper Dark Red

Related Information

DDMRP Buffer Status MonitoringKey Figures

1.11.4 Reporting of DDMRP projected on-hand stock in number of days of coverage

You can use this feature to display the projected on-hand stock in days of coverage, in addition to the quantity of stock.

Technical Details

Types New



To be able to report the projected on-hand stock in days of coverage, you must add the following key figure your DDMRP-based planning area. The change has also been added to the SAP8 sample planning area, so you can use that as a reference.


DDPROJONHANDINDAYSCOVERAGE

Projected on-hand inventory in days coverage

DAYPRODLOC Projected on-hand inventory in days coverage

Calculation of projected on-hand coverage, in days.


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/5fcc5b06bd764720b7bc1104732f8918.html


Related Information

Key Figures

1.11.5 Support of Filter Variant Management in the DDMRP Buffer Analysis App

You can use this feature to save and manage filter views (variants) in the DDMRP Buffer Analysis app.

Technical Details

Types New


Additional Details

You can save a view you've created as a variant by selecting the arrow ( ) next to the name of the view, and selecting Save As. You can also manage your views by selecting Manage.

Related Information

Creating and Running Scenarios in DDMRP Buffer Analysis

1.12 Time-Series-Based Supply Planning

1.12.1 Time-Series-Based Shelf Life Planning Enhancements

We've made the following enhancements to the time-series-based shelf life planning heuristic:

● You can now use the Carry Over Negative Projected Stock parameter by adding it to the Additional Parameters section of the S&OP Operator Profiles app. This allows you to carry over negative projected inventory to the next period, as an additional demand. For the shelf life planning heuristic, this demand derives its minimum shelf from the shelf life of the negative projected inventory.




https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/c03dee43cb87404da018f7c91f98e843.html

You have to use the technical name (CARRY_OVER_NEGATIVE_PROJECTEDINVENTORY) when adding the parameter.

● The Inventory Correction key figure is now supported. If you want to use this key figure, you must extend its planning level to include the SHELFLIFEID in a planning area configured for shelf life.Positive values are treated by the shelf life heuristic as additional inventory, meaning that the shelf life is the remaining shelf life (as for the Stock on Hand key figure). Negative values are treated in the same way as the values in the Independent Demand key figure, so the shelf life defined in this case is the minimum shelf life, as for all other demand-related key figures.

Related Information

Primary ParametersKey Figures with Shelf Life ID Attribute

1.12.2 Late Delivery for Inter-Subnetwork Demand


This feature introduces two new input key figures and one new output key figure, as follows:

● IPU Late Delivery Cost Rate (IPULATEDELIVCOSTRATE)An input key figure that defines the costs per piece and per period when dependent demand for a subnetwork is delivered late.

● IPU Late Delivery Maximum Periods (IPULATEDELIVMAX)An input key figure that specifies the maximum number of periods for which a subnetwork's dependent demand can be delivered late.

● Amount of IPU Demand Delivered Late (IPUDELIVEREDLATE)An output key figure that shows the amount of a subnetwork's dependent demand that has been delivered late in a particular period

Technical Details

Types New


Related Information

Late Delivery


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/f271fed72c0d4234a07ee469aca8655c.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/33aed794991c4853ac50007085b54294.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/65934c564a9ff81ae10000000a441470.html

1.12.3 Change of Default for Minimum Aggregated Constraints in S&OP Operator Profiles App

When creating a new S&OP operator profile for the time-series-based supply planning optimizer, the default for minimum aggregated constraints now allows violation of these constraints. Previously, the default was not to allow violations. In effect, we've changed the default from a hard constraint to a pseudo-hard constraint, because hard aggregated constraints can potentially lead to infeasible or unsolvable solutions.

You can still change the new default if required under Other in the Optimizer Parameters section of the S&OP Operator Profiles app.

This change only affects new S&OP operator profiles; other actions (edit, copy, view, delete) are unaffected and you don't need to change existing profiles.

The behavior of the S&OP operator is also not affected by this change.

Technical Details

Types Changed


Additional Details

The new default applies to minimum aggregated constraints for customer transports, transports, production, and inventory.


Be aware of the new default when creating a new S&OP operator profile for the optimizer.

Related Information

Optimizer ParametersAggregated Constraints



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/74f362b10a5e475094e7a1f7416f9239.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/63b1bb56ed263f23e10000000a44147b.html

1.12.4 Change to Planning Levels in Sample Planning Areas

We've removed the PRDID attribute from the *PRODLOCLOCFRRESAGG and the *PRODLOCRESSRCAGG planning levels in the SAP4, SAP4C, SAP4S, and SAPIBP1 sample planning areas (where * indicates all prefixes for these planning levels).

This is to comply with an existing enhanced planning activation check for aggregated constraints key figures first announced in the 1705 What's New.

Technical Details

Types New


Related Information

1.12.5 Enhanced Documentation for Expert Settings in Optimizer Profiles

We provide enhanced documentation for the expert settings in optimizer profiles, which you maintain in the S&OP Operator Profiles app. Expert settings help you deal with numerical issues in optimizer runs. They include numerical focus, numerical scaling, and numerical pre-optimization. The documentation has been enhanced with typical use cases and with a link to SAP Note 2922352 . The latter contains in-depth explanations of numerical issues and how expert settings can support you in solving them. See Optimizer Parameters.

Technical Details

Types Changed




https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/74f362b10a5e475094e7a1f7416f9239.html

1.12.6 Status Handling in Settings for TS Supply Planning

We have introduced status handling in the Settings for TS Supply Planning app. This enables you to save settings in an inactive version and activate them for use in the respective planning area when necessary. For more information, see Settings for TS Supply Planning.

Technical Details

Types New


1.12.7 Optimization Problem Inputs on Optimizer Run Details Screen

The following new information is displayed on the Optimizer Run Details screen, which you can access from the application job log:

● Information about the size of the optimization problem, including the number of locations, location products, products, and planning periods.

● Information about the mathematical properties of the optimization problem, including the number of continuous variables, discrete variables, binary variables, and linear constraints.

This information is displayed in the new section Optimization Problem Inputs.

Technical Details

Types New


1.12.8 New Table: Supported Functions per Algorithm (Docu Enhancement)

The documentation for Time-Series-Based Supply Planning includes a new table that lists the supported functions for each of the following algorithms:

● Time-Series-Based Supply Planning Heuristic



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/ea9c9ecaaaa04d828418112e3071a235.html

● Time-Series-Based Shelf Life Planning Heuristic● Time-Series-Based Supply Planning Optimizer● Time-Series-Based Supply Planning Finite Heuristic

For more information, see Planning Algorithms for TS-Based Supply Planning: Supported Functions.

Technical Details

Types New


1.13 Order-Based Planning

1.13.1 Planning Run Profiles: New Object-Attribute Combinations

You can use the following new object-attribute combinations when creating cost rules in the Planning Run Profiles app:

Object Attribute Attribute Can Be Used In

ProductionDataStructure ProcurementPriority Production cost rules

TransportationLane ProcurementPriority Transportation cost rules

Procurement cost rules

LocationMaterial SoSSelectionProfile Production cost rules

ShipFromLocationMaterial SoSSelectionProfile Transportation cost rules

ShipToLocationMaterial SoSSelectionProfile Transportation cost rules

Procurement cost rules

Technical Details

Types New


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/aada642335c84ead8c4fd807b8a54f0d.html


1.13.2 Enhanced Transportation Costs in Planning Runs

The calculation of transportation costs in planning runs using the optimizer planning algorithm was enhanced. Generated costs are now added to the transportation costs. This is to avoid unnecessary transports, which in the past could occur, for example, if your defined transportation costs were lower than your inventory holding costs as the optimizer always picks the cheapest solution. The generated costs that are now added prevent additional transports being planned to avoid inventory holding costs. In the planning run, the network, inventory levels, and associated costs are analyzed and the required costs to avoid transportation loops are added.

Technical Details

Types Changed


1.13.3 Copy of Order-Based Planning Settings

When you copy a planning area or sample planning area, the order-based planning settings are now also copied automatically. This saves you time when copying a planning area, as you no longer have to maintain these settings from scratch in the Settings for Order-Based Planning app. All you need to do is adjust any of the copied settings as needed.

Technical Details

Types New


1.13.4 Generation of Costs in Deployment Runs

You can now let the system generate the costs that are relevant in a deployment run instead of manually setting up a cost model with which you achieve the desired distribution of inventory. The generated costs are based on



the demand prioritization rule, priorities of transportation lanes, and, if you apply fair share, segments for fair share for inventory. You can switch the generation of deployment costs on and off in the Planning Run Profiles app on the Optimizer Parameters tab.

If you choose to let the planning engine generate the costs in a deployment run, time-independent cost rules or time series for cost key figures are not considered. Instead, the planning engine generates the costs based on the demand prioritization rule, procurement priorities of transportation lanes, and, if applicable, segments for fair share for inventory.

For more information, see Deployment Cost Generation.

Technical Details

Types New


1.13.5 Expert Settings in Optimizer Parameters

We have added Expert Settings to the Optimizer Parameters in the Planning Run Profiles app.

They include the following options to be set: Numerical Focus, Numerical Scaling, and Numerical Pre-Optimization. Those can help to better handle numerical issues, that is, undesired effects on the optimization results that are caused by big numerical differences in cost or material flow key figures, or by high cost values that are internally computed by the planning engine.

For more information, see Optimizer Parameters.

Technical Details

Types New


1.13.6 Resource Consumption Unit Shown in Analyze Supply Usage

In the Analyze Supply Usage app, the Resource Consumption Quantity columns now show the resource consumption unit in addition to the numeric value. The Supply Usage and Resource Usage tables both have this column, but you need to adapt the table settings for it to be displayed.


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/8b83e981139e40539040058974c4910e.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/93c6a8b1eecd4a158bf1df718efb06aa.html

Technical Details

Types Changed


1.13.7 Deprecation of OpenAPI Versions

The 1808.0.0 OpenAPI versions will no longer be available as of SAP Integrated Business Planning 2105:

Component Version

INBOUND STATIC DATA MODEL 1808.0.0_FULL

1808.0.0_TRANS

OUTBOUND STATIC DATA MODEL 1808.0.0_OUTBOUND

OUTBOUND ANALYTICAL DATA MODEL 1808.0.0

As announced in IBP 2008, the following 1805.0.0 OpenAPI versions will no longer be available as of SAP Integrated Business Planning 2102:

Component Version


1805.0.0_TRANS

As announced in IBP 2005, the following 1802.0.0 OpenAPI versions have been deprecated and are now no longer available:

Component Version


1802.0.0_TRANS

OUTBOUND STATIC DATA MODEL 1802.0.0_OUTBOUND



Technical Details





The 1802.0.0 OpenAPI Versions

CautionThe 1802.0.0 OpenAPI versions have ceased to function as of the 2011 release and any jobs that use these OpenAPI versions will fail after the upgrade to the 2011 release of SAP Integrated Business Planning. We therefore strongly recommend that you cancel or delete any scheduled jobs that use these OpenAPI versions, and replace them with jobs using newer OpenAPI versions.

The 1808.0.0 OpenAPI VersionsIf you are using 1808.0.0 OpenAPI versions, you will get a warning about the deprecation, but you can continue to use them in the 2011 and 2102 releases of SAP Integrated Business Planning. Note that these OpenAPI versions will cease to function as of the 2105 release and any jobs that use these OpenAPI versions will fail after the upgrade to the 2105 release of SAP Integrated Business Planning. We therefore strongly recommend that you cancel or delete any scheduled jobs that use these OpenAPI versions, and replace them with jobs using newer OpenAPI versions.

If you haven't already used the 1808.0.0 OpenAPI versions, you cannot schedule a job using them as of the 2011 release of SAP Integrated Business Planning.

The 1805.0.0 OpenAPI VersionsIf you are using 1805.0.0 OpenAPI versions, you will get a warning about the deprecation, but you can continue to use them in the 2011 release of SAP Integrated Business Planning. Note that these OpenAPI versions will cease to function as of the 2102 release and any jobs that use these OpenAPI versions will fail after the upgrade to the 2102 release of SAP Integrated Business Planning. We therefore strongly recommend that you cancel or delete any scheduled jobs that use these OpenAPI versions, and replace them with jobs using newer OpenAPI versions.

If you haven't already used the 1805.0.0 OpenAPI versions, you cannot schedule a job using them as of the 2008 release of SAP Integrated Business Planning.

NoteIf you use ABAP adapter and want to switch to the higher OpenAPI versions from versions lower than 1902, you must first do the following:

● In the Configure Remote Sources (SDI) app, create a new remote source with a real logical system you have defined for your external system.


● In the Integration Profiles app, assign your logical system to the integration profile.

Otherwise, the inbound integration job will abort and you will get an error message "Remote logical system X does not match remote source configuration EXTERNAL".

Related Information

Version Information

1.13.8 New Key Figures and Attributes for DPS

The following new key figures are now available in the SAP7 sample planning area that you can use to analyze quantities from planned orders in the production planning stage (PP stage) Detailed Planning and Scheduling (DPS) as opposed to quantities from planned orders in the production planning stage Operational Supply Planning (OPS):

● Dependent Demand Planned in DPS (DEPDEMANDPLANNEDORDERDPS): This is the aggregated demand of planned orders in the DPS PP stage for a component. The demand is derived because the material is part of a bill of material of a finished material on the PERPRODLOC base planning level. The external quantity of this key figure is DEPENDENT_DEMAND_DPS.

● Dependent Demand Planned (PDS) in DPS (DEPDEMANDPLANPDSDPS): This is the aggregated demand of planned orders in the DPS PP stage for a component in a production data structure on the PERPDSCOMP base planning level. The demand is derived because the material is a part of a bill of material of a finished material. The external quantity of this key figure is PLANNED_DEMAND_QUANTITY_DPS.

● Production Planned in DPS (PRODPLANNEDDPS): This is the aggregated receipt quantity from planned orders in the DPS PP stage on the PERPRODLOC base planning level. The external quantity of this key figure is PRODUCTION_PLANNED_DPS.

● Production Planned in DPS Used by Demand (PRODPLANNEDDPSASU): This is the aggregated receipt quantity from planned orders in the DPS PP stage based on pegged demand attributes on the PERPRODLOCASU base planning level. The external quantity of this key figure is PRODUCTION_PLANNED_DPS.

● Production Planned (PDS) in DPS (PRODPLANNEDPDSDPS): This is a calculated key figure. This is the aggregated receipt quantity from planned orders in the DPS PP stage on the PERPDS base planning level. The external quantity of this key figure is PLANNED_ORDER_QUANTITY_DPS.

You can check the aggregated quantities from planned orders in both PP stages in the respective key figures that do not contain a suffix in DPS in key figure descriptions.

To distinguish the location materials that are expected to have a DPS share as part of the overall planned order quantities and to identify the DPS horizon for such location materials in SAP Integrated Business Planning, add-in for Microsoft Excel, and in the Web-Based Planning app, the following new attributes have been added to the S7LOCATIONPRODUCT master data type in the SAP7 sample planning area:

● PPINTMODE● DPSHORIZON



https://help.sap.com/viewer/f31706b080044e58b9a9acebfb7808b2/2102/en-US/578edd56f3a90950e10000000a44147b.html

Technical Details

Types New


Related Information

Key Figures for Detailed Planning and SchedulingS7LOCATIONPRODUCT

1.13.9 Mandatory Data Entries Changed in IBP_MATERIAL_UNIT_CONVERSION

It is now mandatory to enter data for denominator and nominator for conversion to base units of measure in the UMREN and UMREZ columns in the IBP_MATERIAL_UNIT_CONVERSION table. This change is relevant for all available full inbound versions of OpenAPI in SAP IBP 2011.

Technical Details

Types Changed


Related Information

IBP_MATERIAL_UNIT_CONVERSION

1.13.10 New Table: Supported Functions per Planning Run in OBP (Documentation Enhancement)

The user assistance for order-based planning includes a new table that lists the supported functions for each of the following planning runs:

● Order-Based Planning: Constrained Forecast Run using the finite heuristic planning algorithm


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/097dd5612beb4ee0a1999da79319e54e.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/21c84c56a94b9e21e10000000a44538d.html

https://help.sap.com/viewer/ccb4b02977d844daa2db9c64a5472216/2102/en-US/3ffa7a36427143ec84914b0d7a9b198b.html

● Order-Based Planning: Constrained Forecast Run using the optimizer planning algorithm● Order-Based Planning: Confirmation Run using the finite heuristic planning algorithm● Order-Based Planning: Deployment Run using the finite heuristic planning algorithm● Order-Based Planning: Deployment Run using the optimizer planning algorithm

For more information, see OBP Planning Algorithms and Supported Functions.

Technical Details

Types New


1.13.11 Default Time Zone in OBP Planning Areas

Previously, there was no default time zone specified in the OBP planning areas and when you imported an external data source, it was assigned the time zone of its location. Now the default time zone in the OBP planning areas is UTC.

Please note that this change will be only applied after you reactivate your planning area after the upgrade to SAP IBP 2011.

Technical Details

Types Changed

Must know


1.14 Cross Applications

1.14.1 New App: Change History Analysis

You can use this new app to view and analyze the effects of changes to key figure data that have been captured by the change history functionality.



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/b32aad11dae24cf7a0474a7a8d9c0955.html

Technical Details

Types New



Additional Details

This app shows you how your plan has evolved after changes have been made to key figure data. You can search for effects of changes for a planning area, version, specific key figures and attributes, and use filters to narrow down the results. For example, you can filter by certain reason codes that were linked to the original change, the users who made the original change, or specific attribute values.

Information such as the difference between the prior value and the new value helps you analyze the impact of the changes.

You can save the filter criteria as a view. The administrator can share this view with other users using the Content Management app.


This app is the successor of the old Change History app. We plan to remove the old app with 2105. We therefore recommend that you familiarize yourself with the new app by the upgrade to 2105 at the latest.


If your users have been working with the old Change History app, the new app appears automatically on their launchpad after the upgrade to 2011. If your users have not been working with the old app and you want to make the new app available to them, you need to add the Change History business catalog (SAP_IBP_BC_CHANGEHIST_PC) to their business role.

Related Information

Change History AnalysisChange History for Key Figures


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/4080b7afc41b4421983f7b3b204c900d.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/8f6d3393dd0e480c8c5b1146b96eb2e6.html

1.14.2 New App: Manage Master Data

A streamlined tool that supports planners and integration experts in carrying out master data management activities.

The Manage Master Data application provides access to all the master data managed in SAP Integrated Business Planning by your organization. As a planner, you can search, filter, and sort the full set of master data available in your system in a performant, customizable, and user-friendly way, while as an integration expert, you can easily check whether external master data has been correctly integrated to IBP.

Technical Details

Types New


Additional Details

The initial screen of the app displays a worklist of master data type entries. For each entry, a list report view can be accessed, which provides details on the master data maintained for the selected master data type.

By default, the app displays planning area-independent master data. However, list report views can be modified to specifically show master data that only exists in planning versions.

To support users in customizing their master data views, filtering, sorting, and variant management features are available in the app.


To work with the new app, you have to assign the SAP_IBP_BC_MAN_MASTERDATA_PC business catalog to your business role.

User restrictions for accessing master data in the app can be set at multiple levels. On the one hand, user access can be configured based on a combination of Business Role, Attribute Permissions, and Permission Filters, which are assigned to the business user's ID. On the other hand, Restriction Types can be defined to limit access to specific master data types.

Related Information

Manage Master Data



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/34ef5d45d1fb45c182e8a24efe9b37db.html

1.14.3 Bookmark Update Required

Due to the fact that the semantic objects of the apps have been changed, you need to update any browser favorites or bookmarks that you've created for any apps within IBP.

Technical Details

Types Must knowChanged


Additional Details

The user interface of each app has a property called “semantic object”, which is used to construct the app URL in the browser. These semantic objects had to be harmonized for technical reasons, and were all changed in this process. As a result, the URLs containing these objects changed as well. For this reason, you need to update any browser favorites or bookmarks that you've created for any apps within IBP.

For example, the semantic object of the Manage Forecast Models app was ForecastModel-maintain, which is now replaced with IBPStatisticalforecastProfile-manage. Any bookmark you created for the app needs to be recreated because of this change.

NoteAny favorites you created using the Save as Tile button within the apps are not affected.

1.14.4 Public Holidays in the Planning Calendars App

As of the 2011 version, you can display the public holidays of factory calendars on which your planning calendars are based using the Planning Calendars app. Public holidays are recurring non-working days, unlike exceptional dates.

Technical Details

Types New




To maintain the public holidays of factory calendars, use the SCAL transaction in your NetWeaver-based on-premise system.

1.14.5 Enhancements for Copy Version Operator and Delete Version Operator

The copy version operator and the delete version operator now process data in packages rather than processing it all in a single batch. These packages are automatically created by the system without you having to do anything. Processing data in smaller packages can help decrease memory consumption.

Another advantage is that if there’s a problem with a package, the operator automatically retries processing the package. If a package can’t be processed after all, the operators continue with the next packages. This way, the operators can finish with a partial success, compared to earlier releases where they failed completely when a single record in a job couldn’t be processed. If a package doesn’t get processed, you can reschedule the operator.

Technical Details

Types New


Additional Details

The application log shows you information such as the number of packages or the number of records that the operators have processed. If the operator cannot process a package after all, you can see which package it was. This can help you further investigate the root cause.

NoteIn some cases, you may want to copy data for a master data attribute that is configured as an attribute as key figure. Please remember that in normalized planning areas, the number of time series entries that can be created or updated using this method is limited to 1 million per attribute as key figure.



1.14.6 Enhancements to Application Job Templates

You can now specify for Forecast Automation and Lag-Based Snapshots application jobs how the system should calculate the current period.

By default, it is defined based on the system time zone. However, you can also choose to convert the execution time to a different time zone, or pick a specific date and time to be used. If you don’t choose any of the available methods, the time of execution will be considered as the current period.

In the Lag-Based Snapshots application job template, you can now also set the planning area version in which you want the system to take lag-based snapshots. If you don't specify any, lag-based snapshots will be taken for the baseline version of the planning area.

Note that the source and target key figures need to be a part of the same version on which the operator is being run.

Technical Details

Types New


1.14.7 Local Time Zones

As of SAP Integrated Business Planning for Supply Chain 2011, the current period can be determined using your local time zone.

Technical Details

Types New



As a planner, this feature can be beneficial because you don't have to do calculations to find out when the current period is over and whether, for example, you can still edit key figures that are editable in the current and future periods.



To enable businessuserspecific time zones, change the default value of the CURRENT_PERIOD_CALCULATION_TYP global configuration parameter to BUSINESS_USER_LOCAL. If the CURRENT_PERIOD_CALCULATION_TYP parameter is not configured, the system time zone is considered for all users.


After configuring the global parameter, you can maintain the time zone settings of each business user using the Maintain Business Users app.

1.15 Exception Management

1.15.1 Enhancements to Define and Subscribe to Custom Alerts

You have more options when defining the display of charts for custom alerts. You have the flexibility of selecting the calculation level attributes and period to apply as filters for the complementary charts in subscriptions. You also have visibility on all custom alert subscriptions: both created by you or shared with you and created by other users and not shared with you. This will allow you to assess the impact that any changes you make to definitions might have on subscriptions.

Technical Details

Types New



Additional Details

The following features are now available:

● When you define the display options for your custom alerts, you have to select the default chart type first. The chart type that you select will impact the number of key figures that you can select. For most chart types, you can also define different color and appearance options.



● If the calculation level attributes you select for the custom alert definition have a description attribute defined in the Master Data Types app, you can select the display option for each attribute, for example, display only the ID or both the ID and the description. You can also order the calculation level attributes and period in the list and this is going to be the order in which the calculation level is displayed for the corresponding custom alerts in the Monitor Custom Alerts, Intelligent Visibility, and Analytics - Advanced apps.

● You can select the calculation level attributes and period to be used as filters for the complementary charts in the underlying subscriptions. The complementary charts for the custom alerts calculated in the Monitor Custom Alerts and Intelligent Visibility apps will use only the calculation level attributes and period that you’ve selected.

● You can define options for your charts, such as legend position, value label, axis title, and number format.● When you edit a custom alert definition and add calculation level attributes and period, key figures, and

complementary charts, you can choose whether you want these changes to be included or excluded in all underlying custom alert subscriptions.

● In two separate lists, you can view all subscriptions for a custom alert definition that you’ve created and that have been shared with you and all subscriptions that have been created by other users and that haven't been shared with you, if any.


This app is the successor of the old Define and Subscribe to Custom Alerts app. The old Define and Subscribe to Custom Alerts app is no longer supported and will be deleted from the SAP Fiori launchpad as of 2102. The app may no longer be available by default on the SAP Fiori launchpad. In this case, you can find it in the app finder until it’s deleted. We recommend that you switch to the successor app as soon as possible.

Related Information

Define and Subscribe to Custom Alerts

1.15.2 Enhancements to Monitor Custom Alerts

Technical Details

Types New



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/220035848899456d97b298925618debb.html

Additional Details

You can now do the following in the Monitor Custom Alerts app:



Related Information

Monitor Custom Alerts

1.16 End-to-End Visibility

1.16.1 Enhancements to Intelligent Visibility

Technical Details

Types New


Additional Details

You can now do the following in the Intelligent Visibility app:

● You can view alerts from your alert subscriptions for specific scenarios using the Versions/Scenarios filter.

NoteWhen you choose a version/scenario, the list of subscriptions is reduced to only the ones that are defined for that version/scenario.

The Supply Chain Network data layer is disabled when a scenario is selected.



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/ff4474547412bb24e10000000a4c4043.html




● You can use the Select Profile button to apply a profile that is shared with you or that you've configured in the Intelligent Visibility Profiles app.

Related Information

Viewing Custom Alerts by LocationViewing Key Figures by LocationHow to Create a ProfileContent Administration

1.16.2 New App: Intelligent Visibility Profiles

You can now use the new Intelligent Visibility Profiles app to configure the content and appearance of the Intelligent Visibility app.

For example, users can create more than one profile to use in Intelligent Visibility. One profile can include supply charts and the other profile can include inventory charts. Users that have these profiles shared with them can switch between both profiles to view different data.

Technical Details

Types New


Additional Details

The following new features are available in the Intelligent Visibility Profiles app:

● You can customize the display of key figures such as the color and the number formatting.


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/1e33b6faac3a4d4ea37ce75f1a4b69ec.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/285455c67a014956a0f17c4c372fcf69.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/ef2fdfcf693c401e8483f08668c8965a.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/2a1006589c010846e10000000a441470.html

● You can choose to show a specific detail content layout and reorder the sections according to your preferences.

● You can select analytics charts that you want to include in the profile.● You can share your profile with other users and user groups to view the same data.

Related Information

Intelligent Visibility ProfilesHow to Create a Profile

1.17 Analytics

1.17.1 Enhancements to Analytics - Advanced

Technical Details

Types New


Additional Details

You can now do the following in the Analytics – Advanced app:

● You can use the new Horizontal Waterfall and Vertical Waterfall chart types from the Comparison chart group to view the cumulative increase, decrease, and total result for a set of key figures.To use these chart types, you need a minimum of two key figures and no group by attributes.Key figure values can be inverted and reordered. The last key figure can be set as the total (for example, net profit).

● You have the option to navigate to the Web-Based Planning app to quickly change or update data.To navigate to the Web-Based Planning app, choose Go To Web-Based Planning . A new tab opens, and a generated planning view is displayed. The planning area, calculation level, key figures, and filters are carried over to the Web-Based Planning app.

Note○ It is only possible to navigate when a time period is selected.



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/b14eb7fd327944859eaf177055df8998.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/ef2fdfcf693c401e8483f08668c8965a.html

○ Only one time range is allowed. If you select distinct time ranges, an error occurs.○ If only one day, one week, one quarter, or one month is selected, theFrom and To are the same.

Related Information

Chart TypesAnalytics Details

1.17.2 Enhancements to Dashboards - Advanced

Types New


Additional Details

You can now do the following in the Dashboards - Advanced app:


● You can navigate to the alert subscription or definition from the dashboard.

Related Information

Working with a Dashboard

1.17.3 Supply Chain Network: Render DDMRP Decoupling Points in Network Charts

When rendering DDMRP-based network charts, the Supply Chain Network app now displays an icon of DDMRP buffers next to nodes that are decoupling points.


https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/18cd8c57f21f44c69b457be953da5081.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/192a60cdb5294fc39d090d565a3a08a9.html

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/092c2b3861e241fc8edc5886f324ab54.html

Technical Details

Types New


Additional Details

The decoupling point icon is only available for planning areas based on the SAP8 sample planning area, and is only displayed if the MRPTYPE attribute for the location product master data type is set to D1.

Related Information

About Supply Chain Network Charts

1.17.4 Supply Chain Network: Filter Bar Added to Chart List

You can use this feature to filter charts in the chart list. Filters can be hidden and modified.

Technical Details

Types New


1.17.5 Supply Chain Network: Required Master Data Types

For the Supply Chain Network app to function properly, the proper supply chain data must exist in your planning area. This means that certain master data types must be part of your planning area. As documented previously in IBP 2011, these master data types and data are required in order to use the Supply Chain Network app.

Please update and reactivate your planning area as needed.



https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-US/fd3ce2cda3e94fd39f0600aa77f44cbb.html

Technical Details

Types Must know



Certain master data types are required to render the supply chain network chart.

If an inventory-compatible (SAP3 or SAPIBP1) planning area is detected, it is used. The following master data types and attributes are required for an inventory-compatible planning area:

Master Data Type Attributes

CUSTOMER CUSTID (key),

CUSTGROUP

LOCATION LOCID (key)

PRODUCT PRDID (key)

LOCATIONPRODUCT LOCID (key), PRDID (key), STOCKINGNODETYPE.

NoteIf STOCKINGNODETYPE is null, the chart renders a warehouse stocking node.

SOURCECUSTOMER CUSTID (key), LOCID (key), PRDID (key)

NoteOptional if SOURCECUSTGROUP exists.

SOURCECUSTGROUP CUSTGROUP (key), LOCID (key), PRDID (key)

NoteOptional if SOURCECUSTOMER exists.

SOURCELOCATION LOCFR (key), LOCID (key), PRDID (key)

LOCATIONFR LOCFR (key)

SOURCEPRODUCTION LOCID (key), PRDID (key), SOURCEID (key), SOURCETYPE



NoteIf SOURCETYPE is null, the chart renders a processing/manufacturing node.

PRODUCTIONSOURCEITM PRDID (key), SOURCEID (key), SOURCEITMID.

NoteChart renders without links to component products.

COMPONENT PRDFR (key)

If any of the attributes are missing from the planning area, you must add them and load data.

NoteThe app supports both SOURCECUSTOMER and SOURCECUSTGROUP. You can have one or the other, or both.

If STOCKINGNODETYPE (attribute of LOCATIONPRODUCT) or SOURCETYPE (attribute of SOURCEPRODUCTION) are null, the app renders a warehouse stocking node and a process/manufacturing node, respectively.

If an inventory-compatible (SAP3 or SAPIBP1) planning area is not detected, then the app looks for a response and supply-based planning area (SAP7), and the following master data types and attributes are required:


PRODUCT PRDID (key)

LOCATION LOCID (key), LOCTYPE (key), PLANTTYPE

LOCATIONPRODUCT LOCID (key), PRDID (key), LOCTYPE (key)

LANEPRODUCT PRDID (key), LOCFR (key), LOCTO (key), LOCFRTYPE (key), LOCTOTYPE (key)

PDS PRDID (key), LOCID (key), LOCTYPE (key)

PDSCOMP PRDID (key), LOCID (key), LOCTYPE (key), PRDFR (key)

If any of the attributes are missing from the planning area, you must add them and load data.

NoteIf neither set of the required master data types are available, a message about an incompatible planning area is displayed or logged.



1.18 Security

1.18.1 Customer-Initiated Penetration Testing

In addition to SAP-managed penetration tests, you can request approval to perform an annual vulnerability test on your specific Cloud product.

Check the Security Aspects for a comprehensive process description including how you can request approval for the testing and what actions SAP takes following your tests.

Technical Details

Types New


Related Information

Customer-Initiated Penetration Testing


https://help.sap.com/viewer/685fbd2d5f8f4ca2aacfc35f1938d1c1/2102/en-US/503ec0b4d2584496a921508775baaa47.html

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use genderspecific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.


Important Disclaimers and Legal Information

What's New in SAP Integrated Business Planning for Supply Chain 2011Important Disclaimers and Legal Information PUBLIC 141

www.sap.com/contactsap

© 2021 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 https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

what's new in sap integrated business planning for supply

Documents