RTI Integrate Extensible Master Data Attributes - BAdIs and Parameters

 It corresponds to the BAdIs configuration in S4/ECC system.

Source: SAP

IBP Order Based Planning Integration Architecture for Real Time Integration (RTI)

 Update SAP IBP 2111.

Real-Time Integration of master and transactional data • 

Initial and delta load • 

Push from source system to target system by direct data capturing in ECC and SAP S/4HANA • 

Master data: • Location • Product • Resource • PDS • Transportation Lane • 

Transactional data: • Stock • Planned Order / Production Order • Purchase Requisition / PO / STR / STO / Inbound Delivery • Sales Order / Outbound Delivery • 

Outbound integration (only transactional data): • Planned Orders, STRs, Purchase Requisitions, and Sales order confirmations

Source: SAP

Unified planning process flow - IBP

 

Difference of IBP Version and Scenario

 

Difference of IBP Version and Scenario

Source: SAP IBP Online help

Object Type	Version	Scenario
Purpose	Alternate plans maintained over time.	On-the-fly “what if” scenarios
Created By	Administration user at time of configuration. (The number of versions is defined during configuration.)	Planner or end user (dynamically when using the system)
Created From	Planning Areas app, by choosing Versions, and then New.	IBP Excel add-in by choosing Create in the Scenarios group.
Change Method	Copy Customers copy data between versions. As a result, a version is based on a copy (or an overlay of multiple copies) and not on a collection of deltas. Changes to the base version (or to another version that you copied from) do not automatically “shine through” in the target version of the copy.	Delta The system keeps track of all changes to key-figure values as delta records inside the scenario. If, at the same time, changes are made in the base version, these are visible in the scenarios, unless there are conflicting scenario deltas, in which case those take precedence. This change method could be thought of as “shine-through” logic.

Excel Formatting - Local Members

Local Member:

How to keep IBP system highly configurable but also optimize its performance?

SAP IBP Planning Area Configuration & Performance Recommendations
Source: https://launchpad.support.sap.com/#/notes/2211255 (Version 4 from Apr 21, 2017 in English)


Symptom
IBP is a highly configurable system and it is possible to configure it in a way that's not optimal for performance. This note describes some general guidelines to achieve good performance for a planning area in IBP both in terms of configuration and sizing.

Other Terms 
IBP, S&OP, Scaling, Performance, Planning Area

Reason and Prerequisites

None. This note is generally valid fo S&OP3.0, IBP4.0,  IBP5.0 and IBP6.0

Solution

1. Sizing and Planning Area Complexity

• It is highly recommended to perform sizing prior to project start to work through the current and future sizing requirements and to also attempt to get the right initial size of the system.
• Sizing is primarily based on the number of stored key figure value (which we call planning points). As each planning area is different in terms of key figure calculations and planning views and charts being used, the details of system performance need to be verified by each project
• During your implementation project, it’s recommended to verify the sizing assumptions after uploading data into the system. 
• SAP recommends a phased approach to go-live with complex planning areas with many configured key figures and to plan for a performance test.

2. Keep your Configuration as Simple as possible

Attributes

• Use as few attributes as possible in master data and even more so in planning levels.
• Do not make attributes as key of master data types or roots of planning levels that really aren’t.

Master Data Types: 

• Keep the number of Master Data Types to a minimum. Fewer Master Data Type also typically reduces the number of planning levels and the need for joins for calculations across multiple planning levels.

Key Figures and Planning Levels

• Model key figures at the required detail with regard to time and attributes. A finer granularity than needed carries a performance penalty. (e.g. if you don't have to plan at the ship-to level for customer, don't)
• You can use non-key attribute of a master data type as root attribute in Planning Levels.  That way you don’t need to model additional Master Data Types
• Minimize the overall number of planning levels in your planning area (but do not increase the amount of data you need to store while doing this)
• Minimize the number of root attributes in a planning level. A root attribute is to model an independent dimension (which means the root attribute is a key to the key figure data). It is recommended to have no more than 5 root attributes for a planning level. 
• Minimize the number of calculations that include different input planning levels wherever possible (but without increasing the number of  key figure values you need to store)
• Avoid on the fly attribute transformations as much as possible, as corresponding queries can be slow. Instead try to store the result of attribute transformation to a stored key figure using Copy Operator.

Attribute as Key Figures

• If you use key figures that are filled via a master data “attribute as key figure”, use time-independent key figures instead of time-dependent ones. If Time Dependent Attribute as Key Figures are required, use From Periods and To Periods settings in Attribute as Key Figure configuration to limit the number of time periods this attribute needs to be copied to.
• In case, an attribute value is not time independent and needs to vary over time, then load it as a regular key figure.
• Do not configure master data attributes used in Supply Planning – such as CRATIO, PRATIO or TRATIO as attributes as key figures. There are key figures for this purpose.
• Attributes of master data types can be used in calculations: You don’t need to add integer attributes as key figures just for using them in calculations.

Aggregations and Disaggregations

• If request level calculation is SUM or AVG, use the aggregation mode of SUM or AVG instead of CUSTOM. For Min , Max or Weighted Average Calculations continue using CUSTOM aggregation mode.
• If you need to disaggregate a key figure based on a calculated key figure, avoid the Advanced Simulation Operator if possible as it may have some performance impact.. Rather consider using copy operator to copy the calculated key figure to a stored key figure using a batch job.
• Keep the number of attributes in the planning views to minimum necessary. More than 6 attributes in planning view may affect disaggregation performance.

Verification (very important)

• Check for attributes or key figures that are not used in planning views or analytics and remove them from planning area or even from master data. You can ask SAP for help if you have a large number of attributes to check.

3. Topics that require Special Performance Consideration:

Multiple Planning Areas:

• If you have multiple planning areas in your system, it is recommended to have separate master data types for each.

Data Integration

• Schedule large data loads during off hours. During import jobs users might be blocked from saving data.
• Implement a delta mechanism to limit the number of rows per periodic data import job.
• Don’t load data frequently if not required.
• Use the purge functions to purge data that is not used in the system. There are different options: PURGE (Purge Operator for time series) , PCH ( Purge Change History) ,  Deletion of Key Figure Values and/or master data.

Change History:

• Only switch on change history for planning areas and individual key figures where it’s really required.For example Key Figures that are changes from excel.
• Usually it’s not required to track changes for key figures loaded from external systems. If you need to make manual changes to such key figures, which you want to track in the change history, it is better for logical and for performance reasons to introduce an additional key figure where you make the change and use an overwrite calculation (defaulting).

Snapshots and Copy Operator

• Avoid Snapshots or Copy of key figures with complicated calculations. Instead try to copy the input key figures and then reconstruct the calculation with the copied key figured.
• For example if you want to snapshot a Key figure with currency and/or UOM conversions, first snapshot the key figure without conversion and later apply conversion on the snapshotted key figure.      
•  It is recommended to use Copy Operator instead of Snapshots if  you’re not using cascading of Key Figures for snapshots or if you don’t need the entire time series in the snapshot.. Copy Operator is preferred because you can change the duration, define Target Key Figures and  you have the flexibility  to modify calculations.

Global Configuration Parameters.

• Make sure the following global configuration parameters are configured to the recommended default settings to get better performance. The defaults are available in the system for reference:
• TRACE->TRACELEVEL .
  • Make sure it is not set to D for debugging or some parts of the application like disaggregation will be slowed down
• PLAN_VIEW->MAX_RESULT_ROW_SIZE
• INTEGRATION-STAGCLEANUP
• PLAN_VIEW->MAX_DIM_MEMBERS
• SCN_COUNT_MAX 

Planning Operators:

• Schedule the planning operators staggered so that they don’t overlap each other and cause unwanted locking.

Scenarios and Versions:

• Creating many versions can increase your system database size. It is recommended to have 4 or less versions.
• Try using more baseline key figures as reference key figures for versions in place of version-specific key figure
• Ensure that the number of end user created scenarios remains reasonable and manageable. This requires educating the users on use cases.

IBP- CPI Integration - Best Practices for Extracting Data out of IBP

Source: SAP note - 2493042

You are using SAP Cloud Platform Integration for data services to export key figure data from an IBP application. 

Please note that SAP HANA Cloud Integration(HCI) has been renamed to SAP Cloud Platform Integration(CPI)

Environment

• Supply Chain Management (SAP SCM)
• Integrated Business Planning (SAP IBP)

Cause

You are using SAP Cloud Platform Integration for data services to export key figure data from an IBP application.

For extracting the key figure data, a calculation scenario is used to extract the data out of IBP. A calculation scenario is a special construct in the SAP HANA database that the integration service can use to read data from an IBP application and to write to a file, or to write the data directly to the target on premise system using a web service call. Calculation scenarios are generated in the planning area of the IBP application.

While defining the Data Export Task, it becomes essential to put necessary filters and optimize the filter conditions to ensure that filter conditions are pushed down to IBP.

• It decreases the run time of Data Export Task and optimal usage the resource/CPU/Memory consumption.
• Minimize the impact of this task on the normal business activities of the users. 
• It also reduces the chances of exceptions like connection reset which might lead to an open cursor IBP and in turn impact the performance of IBP.

Resolution

Kindly follow the below guidelines while designing the Data Export Task in CPI-DS.

1. You should split the data extraction needs into multiple tasks based on different filter conditions wherever possible. You need to ensure that smaller data set is extracted from IBP for the optimal usage of resources in HANA.
2. You should avoid the concurrent execution of the Data Export Task. Instead, you schedule the Data export task sequentially 
3. You should always specify the exact PERIODIDn attribute based on the time level you want to extract the data, instead of selecting the generic PERIODID attribute in your data flow. Please note PERIODIDn do not refer directly to the time profile level. For your planning area PERIODIDn are mapped as follows to the time profile level.  
• PERIODID0 Day (Lowest Time Profile Level)
• PERIODID4 Week
• PERIODID3 Month
• PERIODID2 Quarter
• PERIODID1 Year (Highest Time Profile Level)
4. You should not use the IN/NOT IN operator, instead you can use the OR operator for filter conditions.
• For e.g. instead of PRDID IN('X','Y') use (PRDID='X' OR PRDID='Y')
5. You should put the filter on PERIODIDn attribute instead of TSTFR for time period filter conditions. You can give the relative filter conditions for the PERIODIDn.
• For e.g. If you want to extract the data for the current period+12 periods in future, you can define the filter as (PERIODIDn>=0 AND PERIODIDn<=12).
• If you only use the equal to filter, then you need to provide the absolute technical PERIODID which can be retrieved from the excel UI. The filter condition will be like PERIODIDn=1067
• You may also use CPI DateTime functions like WEEK_IN_YEAR, MONTH to meet the different extraction requirement from the Business Perspective. You can refer to the following help document for the full list of CPI DS functions: https://hcids.hana.ondemand.com/DSoD/help/index.html#5cc2bab3d53e43c1bfdeda50c6674625.html

Product

	Product or Product Version
	SAP Integrated Business Planning 1702
	SAP Integrated Business Planning 1705
	SAP Integrated Business Planning 1708

This document is referenced by

	Number	Title
	2571962	Key Figures aggregating at wrong level - SAP Cloud Platform Integration for data services
	2565151	Error: Exception Message: SAP DBTech JDBC: [260]: invalid column name .TSTFR - SAP Cloud Platform Integration for data services
	2516625	HCI:attribute is missing in the Calculation Scenario

First SAP IBP Certification published.

C_IBP_1711

SAP Certified Application Associate - SAP Integrated Business Planning (1711)

Delivery Methods:

Certification

Level:

Associate

Exam:

80 questions

Sample Questions:

View more

Cut Score:

64%

Duration:

180 mins

Languages:

English

Description

• The "SAP Certified Application Associate - SAP Integrated Business Planning (1711)" certification exam verifies that the candidate possesses the basic knowledge in the area of the SAP Integrated Business Planning. This certificate proves that the candidate has a basic overall understanding within this consultant profile of the industry solutions, and can implement this knowledge practically in projects under guidance of an experienced consultant. It is recommended as an entry-level qualification to allow consultants to get acquainted with the fundamentals of SAP Integrated Business Planning.

Notes

• To ensure success, SAP recommends combining education courses and hands-on experience to prepare for your certification exam as questions will test your ability to apply the knowledge you have gained in training.
• You are not allowed to use any reference materials during the certification test (no access to online documentation or to any SAP system).

Topic Areas

Please see below the list of topics that may be covered within this certification and the courses that cover them. Its accuracy does not constitute a legitimate claim; SAP reserves the right to update the exam content (topics, items, weighting) at any time.

Solution Architecture > 12%

Describe the benefits of implementing SAP's Integrated Business Planning solution.

• IBP100 (SAP IBP OD 1705)
• IBP200 (SAP IBP 1708)
• IBP300 (SAP IBP OD 1705)

----- OR -----

• IBP10E (SAP IBP OD 1705)
• IBP20E (SAP IBP OD 1705)
• IBP30E

General Configuration of a Planning Area > 12%

Build an example company.

• IBP200 (SAP IBP 1708)
• IBP300 (SAP IBP OD 1705)

----- OR -----

• IBP20E (SAP IBP OD 1705)
• IBP30E

User Interface > 12%

Use SAP Fiori to personalize the user experience.

• IBP200 (SAP IBP 1708)

----- OR -----

• IBP20E (SAP IBP OD 1705)

Advanced Analytics & Reporting > 12%

Perform analytics and create reports.

• IBP200 (SAP IBP 1708)
• IBP300 (SAP IBP OD 1705)

----- OR -----

• IBP20E (SAP IBP OD 1705)
• IBP30E

Key Figures & Attributes > 12%

Create and use key figures.

• IBP200 (SAP IBP 1708)
• IBP300

----- OR -----

• IBP20E (SAP IBP OD 1705)
• IBP30E

Planning Operators  8% - 12%

Use Planning Operators.

• IBP300 (SAP IBP OD 1705)

----- OR -----

• IBP30E

Statistical Forecasting < 8%

Manage a statistical forecast.

• IBP200 (SAP IBP 1708)

----- OR -----

• IBP20E (SAP IBP OD 1705)

1. Supply Chain Management (SCM)
2.  SAP SCM
3.  SCM Integrated Business Planning (IBP)

SAP IBP Upgrade Planning 1802

Skip to end of metadata

• Created by David Kahn, last modified on Feb 10, 2018

Go to start of metadata

This post is used for ongoing SAP customer communications related to SAP Integrated Business Planning major release upgrades.

For the upgrade process and communication Information, please see this link.

Upcoming Planned Upgrades

• SAP IBP 1802: Applied to Customer Systems February through March 2018  (Planned Release to Hosting February 6, 2018)
• SAP IBP 1805: Applied to Customer Systems May 11 through June 8, 2018  (Planned Release to Hosting May 8, 2018)
  
• SAP IBP 1808: Applied to Customer Systems August 10 to August 31, 2018 (Planned Release to Hosting August 7, 2018)
• SAP IBP 1811: Applied to Customer Systems November 9 to November 30, 2018 (Planned Release to Hosting November 6, 2018)

Future timings of upgrades are subject to change.

Published SAP Integrated Business Planning Roadmap: LINK

Upgrade Notification Guidelines

• Upgrade notifications are sent to system administrator contacts.
• Emails are sent from: sapcloudsupport@alerts.ondemand.com
  Tip: make sure your email software doesn’t block this email address to avoid it going to your SPAM/Junk Mail email.
• Specific schedule of customer system updates will be communicated via email.
• SAP provides code fix support only for "n-1" versions. ie. when a new version (version "n") is "Released to Hosting," support is dropped for the "n-2" version.
• Upgrade notifications are only provided for major release upgrades.
• Hot Fix Collections (HFC) and Emergency Patches (EP) are applied during the regular Contract Maintenance Period. Customer communications are not provided for HFC or EPs.

Upgrade NOTIFICATION for SAP Integrated Business Planning

Notification Purpose

As part of SAP’s continued commitment to provide you with high value applications, we will be upgrading SAP Integrated Business Planning 1711 systems to SAP Integrated Business Planning 1802.

• For more information about the new features, please see What’s New in 1802.
• “What’s New” webinar
• Release restrictions note 2536930.

When

• Upgrade window: Friday 10 PM Local Data Center Time to Monday 3 AM Local Data Center Time
• Expect your systems to be unavailable during this period. This is consistent with the contracted maintenance windows.
• SAP will apply this upgrade from February through March 2018 (see above).

Important Information

Visibility Filters → Permission Filters

To reflect the fact that visibility filters can now also be used to control write access, the term permission filter replaces visibility filter in the IBP applications and in the documentation as of 1802.  Particularly, the Visibility Filters app has been renamed to Manage Permission Filters. Also see the  "Permission Filters" section in the What’s New in 1802.

Activation of Planning Area

• Generally, you do not need to reactivate your planning areas when you upgrade. However, you may have to reactivate to take advantage of certain capabilities. Please review What’s New in 1802 for more information (available as of RTH, planned for Feb 6).
• For additional activation guidance, please review the model configuration guide (available as of RTH, planned for Feb 6). If activation ends with an error you cannot solve, please create a customer incident.

Excel add-in

• The upgrade generally does not require that you install the new version of the IBP Excel add-in. You can decide to install the new version at any time, for example, when you wish to use the new features that are available with the new add-in version. For more information, see What’s New in 1802 (available as of RTH, planned for Feb 6).
• Customers can download and install the latest Excel add-in version on the SAP Support Portal. For more information about restrictions related to the IBP Excel add-in, please check SAP Note 2519069. 
• To apply the latest version of the Excel add-in, please uninstall your current Excel add-in and re-install the new Integrated Business Planning Excel add-in. For more information on how to install the Excel add-in see Setting Up the IBP Excel Add-In (Administrators) and Setting Up the IBP Excel Add-In (Business Users).
• For guidance on packaging and deploying the Excel add-in to end users, please see SAP Note 2114654.
• For supported configurations and prerequisites, please see SAP Note 2135948.
• For the IBP 1711 version of the IBP Excel add-in, you download a zip-archive from the SAP Support Portal , in which you find:
  • IBP_Add-in_NET45_x64.exe: This file installs the IBP add-in as a single ribbon for 64-bit Excel installations
  • IBP_Add-in_NET45_x86.exe: This file installs the IBP add-in as a single ribbon for 32-bit Excel installations
  • IBP_Add-In_SbS_x86: This file installs the IBP ribbon as an additional ribbon next to the EPM ribbon (side-by-side installer) for 32-bit Excel installations
  • IBP_Add-In_SbS_x64: This file installs the IBP ribbon as an additional ribbon next to the EPM ribbon (side-by-side installer) for 64-bit Excel installations
• For the IBP 1802 version of the IBP Excel add-in, you download a zip-archive from the SAP Support Portal , in which you find:
  • IBP_Add-in_NET45_x64.exe: This file installs the IBP add-in as a single ribbon for 64-bit Excel installations
  • IBP_Add-in_NET45_x86.exe: This file installs the IBP add-in as a single ribbon for 32-bit Excel installations
  • IBP_Add-In_SbS_x86: This file installs the IBP ribbon as an additional ribbon next to the EPM ribbon (side-by-side installer) for 32-bit Excel installations
  • IBP_Add-In_SbS_x64: This file installs the IBP ribbon as an additional ribbon next to the EPM ribbon (side-by-side installer) for 64-bit Excel installations
• For a list of available IBP Excel add-in versions and the features they contain, please see SAP Note 2394311.

Activities by end-user after the upgrade

• End-users need to clear their browser cache.
• SAP recommends that customers delete old transports after every upgrade.
• Note: Transports must be transported between systems at the same version level.

Questions? Who you should contact.

• For scheduling changes, please contact engage-ibp@sap.com or submit a customer incident.
• For application and technical support, please use standard SAP support (support.sap.com).