What’s New in SAP Integrated Business Planning

2302 (Planned)
SAP IBP Product Management, SAP
January, 2023
PUBLIC
Disclaimer

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 2

Agenda (all times CET)

01
Tuesday: 13:00-14:00 05
Session 1 – Intro, Best Practices and Thursday: 13:00-13:45
Configuration Session 5 – Synchronized Planning,
Inventory, Order Based Integration

02
Tuesday: 14:00-14:45 06
Session 2 – Response & Supply Thursday: 14:00-14:30
Session 6 – Demand Topics

03
Wednesday: 13:00-14:15
Session 3 – Planning UIs

04
Wednesday: 14:30-15:00
Session 4 – Integration Topics and
Extensions
© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 3
WebSocket RFC Switch
Parveen Kumar, SAP

PUBLIC
Who Needs to Switch
JDBC
§ SAP IBP systems created in 2105 or Lower
§ Using SAP-managed communication scenario
§ If you don’t find the Communication Scenario SAP_COM_0593, the Switch is needed

Integrating Data via Websocket RFC

§ SAP IBP systems created in 2108 or Higher
§ Using the SAP_COM_0593 communication scenario.
§ No Switch required for them

© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 5

WebSocket RFC Advantages

o Simple Architecture: Direct connection from DS Agent to IBP. Allows Easier Troubleshooting.

o Detailed Trace Logs: The detailed trace logs provide lot of information relevant for the better
troubleshooting and analysis in case of any issues/errors.

o Timeouts: For Data Export Scenarios from IBP, there is no more 10/15 minutes connection
timeouts during initial selection phase. This also helps in better system stability for Long running
jobs

o Well Secured: WebSocket RFC is better complied with the security standards required for the
IBP Hyperscaler Deployments.

o Future Innovations : This is also a pre-requisite for lot of new future technology innovations
planned for IBP - IBP HANA Cloud,

© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 6

 Call to action – Customers

• Deadline extended until June 2023

• Approx. 500 Customers running WebSocket RFC.

• Link to Survey https://forms.office.com/r/qV22JTeJvr

• Select the wave to schedule the switch as per your

convenience.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 7

WebSocket RFC Switch Process
Customer Preparation- Prior to Wave SAP Customer

§ Minimum agent version -CPI-DS: 1.0.11 § Communication Scenario § Follow the configuration KBAs to
Patch 42HF1(1.0.11.4733) SAP_COM_0593 enabled in the IBP Switch the test system to WebSocket
test and Production System RFC
§ Upgrade the Agent to the latest version if
the current agent version is lower than § No downtime is required for this § DS Agent: Whitelisting of IBP API URL
minimum agent version. activity might be needed
Note: Should be done at least 1 week prior to § WebSocket RFC instance added in § Monitor the Data Integration jobs for
the wave. the Cloud Integration for Data 1-2 weeks in the test system.
Services § Once the switch is validated in the test
§ No Agent Upgrade is needed if you are on
or higher than the Minimum Agent version § Notification will be sent once the steps system, then you can do the
are completed in your system configuration in the production system
§ Create an incident in the component –
SCM-IBP-OPS-MIG § Monitor the Data Integration jobs for
• CI-DS organization name 1-2 weeks in the Production system
• Preferred date for the switch § Update the initial incident created
§ The Switch will be triggered only when the accordingly
incident is created § Report an incident with prefix
WEBRFC in case of an issues.
3202763 - Switching from JDBC to WebSocket RFC Connection
3166596 - Password Based Authentication Configuration Steps for WebSocket RFC
3152253 - Certificate-Based Authentication Configuration Steps for WebSocket RFC
© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 8
 Improvement / Restrictions

o Supports the IN and NOT IN Operators

o Simpler filter conditions- PRDTYPE = ‘X’ OR PRDTYPE=‘Y’ OR PRDTYPE=‘Y’ can be defined as
o PRDTYPE IN(‘X’, ‘Y’, ‘Z’)

o Supports Pushdown of sorting in IBP

o PERIODID Mapping- If your data flows contain PERIODID in their data mapping, the you should map the PERIODIDn column that corresponds to the
appropriate time aggregation level.
o PERIODID mapping- Specific Time Level is not defined. Sub-optimal Results Set

o PERIODIDn mapping- Specific Aggregation Level and Ensures Consistent Results

o Clean-up of Technical Columns

o Technical fields like NUM attributes can be cleaned-up
o These columns that are not used in data integration

Cleaning Up Table Columns

© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 9

Where can I find out more?

3202763 - Switching from JDBC to WebSocket RFC Connection

3166596 - Password Based Authentication Configuration Steps for WebSocket RFC

3152253 - Certificate-Based Authentication Configuration Steps for WebSocket RFC

3158200 - IBP : FAQ's for switching to WebSocket RFC for Time-series Integration with CI-DS

SAP Help document.

§ Integrating Data via WebSocket RFC

§ Switching from JDBC to WebSocket RFC Connection

§ Setting Up a WebSocket RFC Connection

© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 10

Upcoming deprecation warning:
PLOBJID field no longer exposed in reporting tables with 2305
Karoly Daxkobler, SAP

PUBLIC
What will change?

• When writing key figure data to IBP,

integration saves row-level reporting of post-
processing results in the “reporting tables”

• The “reporting tables” are exposed for

reading through CI-DS with the suffix ‘_REP’
so that customers can download and analyze
the data

• The technical field PLOBJID (“Planning

Object ID”) is currently exposed in the
reporting tables

• That field will no longer be exposed starting

2305 through the WebSocket RFC
connection to CI-DS
© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 12
Why is the change necessary?

• The content of the technical field PLOBJID is an SAP-internal technical number with no business
relevance

• Some customers are running out of possible IDs for planning object combinations. To help that
situation, the data type of the technical field for those IDs will change to hold bigger numbers

• As a result, CI-DS data flows reading that field would break, requiring a manual effort to fix the
flow

• Instead of changing the data type of the field in the CI-DS metadata, SAP will hide the field
instead as it does not have a business meaning

© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 13

Problem details and required steps

You are affected when

• You have a data flow in CI-DS that reads key figure post-processing reporting information
• In that data flow, you map the technical field PLOBJID
• You
• use WebSocket RFC to connect CI-DS to IBP or
• use JDBC, but are migrating to WebSocket RFC with 2305 or later.

In such a case, that data flow will fail after the upgrade to 2305 latest when the metadata are refreshed in CI-
DS for the WebSocket RFC connection.

To avoid or correct the error, you will need to open the affected data flow in CI-DS and remove the mapping
of the field PLOBJID of the IBP key figure reporting table.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 14

SAC-IBP: Performance Improvement of Key Figure Import

Zsolt F. Sipos, SAP

PUBLIC
Overview

Prelude
q The performance of importing key figure data from SAC to IBP has been poor
q Example: importing ~ 100K records took ~ 48 minutes
q Unsatisfied customers who tried to use this process

New Feature in 2302 Release for Key Figure Import

q A separate approach was implemented to import key figure data to IBP supported
by NW layer
q Measurement results for ~100K records are below 4 minutes
q This approach is not the default one, it requires explicit switch on by customers

© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 16

Details
New Feature Activation
q Global configuration parameter IMPORT_SAC_KF_VIA_DATA_INTEG of the parameter group
FLEXQUERY needs to be set to TRUE
q Default value of this parameter is FALSE
q Do the parameter setting when there is no key figure import job running triggered by SAC
q Consider some functional differences (see below)

Functional Differences
Function Default New Approach
Approach
Time based key figure disaggregation Yes Yes
Attribute based key figure disaggregation Yes No
Creation of new planning objects No Yes
Write data using non-base unit of measures /
© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public
Yes (?) No 17
RTI: Mass Actions on Reconciliation UI

Zsolt F. Sipos, SAP

PUBLIC
Summary

q Customer pain point related with RTI Reconciliation UI: order/stock items can only be selected
one by one to perform any corrective action on them
q High need for additional options to execute mass actions too
q In 2302 release, alternative actions are offered – „execute ALL without selection”
q Actions triggered with the new option are executed asynchronously
q DEMO

© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 19

© 2023 SAP SE or an SAP affiliate company. All rights reserved. | Public 20
Thank you.
Contact information:

ina.glaes@sap.com – Best Practices ferencz.zsolt.sipos@sap.com - Integration r.meyfarth@sap.com - IBP Global Customer

Engagement
zoltan.miklos.biro@sap.com – Configuration spyridon.negas@sap.com – Integration john.lopus@sap.com - IBP Customer Office
gabor.mittweg@sap.com – Configuration b.akin@sap.com – Integration
mohannad.el-jayousi@sap.com – Configuration alexis.lozada@sap.com – Inventory
pramod.mane@sap.com – Time Series Planning laura.tozzo@sap.com – Demand
thomas.fiebig@sap.com – Order Based Planning
thorsten.kulick@sap.com – Order Based Planning
claus.bosch@sap.com – Order Based Planning
patrick.weber01@sap.com – Planning UIs
parveen.kumar01@sap.com – WebRFC Migration
rainer.moritz@sap.com – Configuration, Demand & Demand
Sensing
© 2023 SAP SE or an SAP affiliate company. All rights reserved. |See
Public
Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences. 21