IBP & CPI–DS:

BASIS OVERVIEW, TASKS

AND STRATEGIES
 WHAT IS
WHAT?

• IBP: Integrated Business Planning is SAP SaaS solution which runs algorithms
required for Supply/Demand calculation, Stock planning etc. In layman terms its
APO on cloud

• CPI-DS: Cloud Platform Integration for Data Services, previously known as HCI-DS
is SAP SaaS solution which SAP sends as a package, along with IBP. In layman
terms its BODS on cloud

• IAG portal: Cloud’s analogue of GRC

Architecture
Technology Platform Architecture – high level overview

Users Users
SAP Clo ud CC EP O n Add-on /
MS excel Web UI L eg end ( BTP) prem ise Add-in
Add-in IBP Fio ri Admin SAP Arib a

Odata
Rest APIs
Service
Integration Layer Backends
SAP Enable
No w
IBP App lications IBP
RFC Add-on
HANA ABAP S/4 HANA
SAP CI-DS SAP SD I agent
FILE ( PS4)
Users Admin
IBP
ECC Add-on
CI – DS agen t
Users Admin ( PER, P R1, EC P)

SAP Id entity Identity

Auth entication Provi sioni ng
Service (IPS) RFC APO
Service (IAS)
( PEA, SCP, P AP )

Webmeth ods
(TBC) RFC BW4H ANA
Admin ( PB4 )
Admin

SFTP PROMAX
Identity & Access
Go vernance (IAG)

Users Admin
SCIM SCIM IDM 8 .0
co nn
( PEI)
Agents
• Agents which are hosted on Premise(Pvt cloud in or case), are used
for setting up connection to SAP SaaS backend.
• Our Landscape uses two types of agents:
• DS Agents: Data service agent is used to connect to CPI-DS
• SDI Agents: IBP requires SDI Agents for connections
Agent tiers

• DS Agents:
• Dev: DSA (one host) – pvaslddsa001
• QA: QSA (two hosts) – pvaslqdsa001 and pvaslqdsa002
• Prod: PSA (two hosts) – pvaslpdsa001 and pvaslpdsa002

• SDI Agents:
• Dev: DPA (one host) – pvaslddpa001
• QA: QPA (two hosts) – pvaslqdpa001 and pvaslqdpa002
• Prod: PPA (two hosts) – pvaslpdpa001 and pvaslpdpa002
Agent Activities
• Start Stop
IBP Agent StartStop.doc | Powered by Box

• Troubleshooting on OS level in case of Issues(doc shared)

• Patching/Agent Registration (doc shared)

Agent Patching.doc | Powered by Box
 CPI–DS:

BASIS OVERVIEW &

TASKS
Agent Availability and Details
• From this tab we can also monitor agent availability, resources, check
for version and check for upgrades from SAP support portal
• sg_<agentname> is basically an Agent group
SAP SaaS version
• Under administration> top right
Agent Alerts: To be set for unavailability

• Under Administration>Agent Notifications

Data Stores
They are present for connection to Source systems, can be SAP/O-data etc
They are created in S/B env and transported along to Prod with the
project. No Datastores are created in Prod directly
• Transports in CPI-DS:

In CPI-DS, we transport Projects and tasks, from Sandbox to Production

Procedures
CI-DS – Transport Management system – How to promote

• Save as version: Allows to go back to that previously version even when it

wasn’t promoted. By default you can roll-back to a promoted version.
• Promote moves the content from sandbox to production
• Export allows to move content from your CI-DS organization to a different
organization or even to a different datacentre within SAP BTP. Not useful
in our case since CCEP one primary org DSEU32090 and no secondary
orgs.
Policies
CI-DS – Transport Management system – Do’s and don'ts

Best practices and watchouts

• Create a datastore for each application or database that SAP Cloud Integration for data services will connect to.
• A given datastore can contain multiple configuration settings of QAS, TEST, PRD
• When promoting to production only the PRD configuration of the datastores should be promote.
• First time task promotion: datastore configuration information is automatically carried over to the Production repository the first time a task is
promoted from sandbox to prod. The Administrator needs to edit and verify the datastore configuration information in the Production repository to
make sure the datastore is pointing to the correct productive repository.
• Re-promoting a task: will not - by default - carry the datastore connection in the promotion to prod. Only in special cases when required user can
request to include the source datastore configuration and include target datastores configuration to overwrite prod datastores settings with the most
recent existing in sandbox.
• When a task, process or datastore that has already been promoted is renamed, the copy in the next environment in the chain is also renamed.
However, copies in more distant environments are not renamed  Watch out CCEP has 2-tier landscape therefore watch out when renaming objects
in sandbox that also exist in production!
• Task promotion requires administrator roles
• You cannot undo a task promotion action.
• When the data store for SOAP is promoted, the WSDL path will be pointing to the test environment of the datastore. Use the multiple datastore
configuration to ensure that the WSDL path of the production is utilized during productive usage.
• CI-DS transport management cannot be linked to external tools.
• Currently the webservices that are available do not have promotion as one of the methods.
• There no way do auto-import of jobs, can it be switch on/off for CI-DS.
• Only one user at a time may edit a task or process. If necessary, ask your administrator to unlock a task process that someone inadvertently left
locked 14
Policies
CI-DS – Approval process

The following slides show the promotion of CI-DS content into production CI-DS using SAP available capabilities to
adhere the best into CCEP existing policies and procedures.
With the aligned approach to use the CI-DS version control in conjunction with the use of Change Requests for
transports in SNOW we are gaining sufficient control of the whole deployment process.
Should SAP make any foundational capability changes, this process will be adjusted accordingly while adhering to
CCEP quality standards".

Overview of all versions created after moving the development of a task into production CI-DS system

Jürgen Heilmann

Philippe Louis Philippe Louis

Lazar Hristov Lazar Hristov

Swathi C K Swathi C K
15
Policies
CI-DS – Approval process

Version 1: Development has been finished by the developer and TER document has been provided by fuctional stream
1. Developer is going to create version 01 / TUT done successfully
2. Developer is going to send an Email to the TUT approver team to request approval to deploy into production
Distribution list: Lazar Hristov, Tushar Apte, Chinmay Joshi (TUT approvers), Majidkhan Pathan, Philippe Staes, Philippe Louis, Amal Zouad (FUT
approvers), Alexandre Mendes and Jürgen Heilmann (Coordinators of whole process)

Swathi C K Swathi C K

3. As the development can only be uniquely identified by the project and task name this combination has always be in the subject of the email
4. If the deployment request contents more than one task, the project - task combination can also be in the body of the email
Policies
CI-DS – Approval process

Version 2: Development has been validated by the TUT approver team

1. TUT approver is going to create version 02 / TUT approved
2. TUT approver is going to send an Email to the FUT approver team to request approval to deploy into production (Reply to email received from
developer)

Lazar Hristov Lazar Hristov

Version 3: Functionality has been checked by FUT approver team

3. FUT approver is going to create version 03 / FUT approved
4. FUT approver is going to send an Email to the coordinator team to request promotion into production system or alternative FUT approver can also
proceed directly with the next step (reply to email received from TUT approver)

Philippe Louis Philippe Louis

17
Policies
CI-DS – Approval process

Version 4: Assignment of Change Request number to the project / task

1. Coordinator / FUT approver is going to create version 04 / Ready for production promotion CHGXXX
2. Coordinator / FUT approver is going to send an Email to Basis team (IBM SAP Basis Ops <IBMSAPBasisOps@ccep.com> ) to request promotion of
task into production environment (Reply to email received from FUT approver / Coordinator)

Versions to be validated: Pre-requisites to be checked by Basis team before promotion into production
3. Change Request in SNOW approved by all approvers including TER document attached to CR as for technical reasons in CI-DS a TER can‘t be
attached
4. All before described approvals are given in CI-DS, means: „changed by“ name matches one of the names out of the different approvers down
below for each version created
Version 1: Developer from Build Factory team
Version 2: TUT approvers: Lazar Hristov, Tushar Apte, Chinmay Joshi
Version 3: FUT approvers: Philippe Staes, Majidkhan Pathan, Philippe Louis, Amal Zouad
Version 4: FUT approvers or coordinators: Alexandre Mendes and Jürgen Heilmann
Policies
CI-DS – Approval process

Final Version: Basis team promotes the development into production

1. After promoting the deployment into production the version will be automatically updated by the system
2. Basis team to reply to the request email and update the team on the promotion (reply to the received version)

How to find a project/task?

3. Make sure you are in sandbox system;
4. Click on the little striped triangle in tab Projects
5. Enter in the poping window the task name
6. System will jump to the requested task

4
Policies
CI-DS – Approval process

How to create / manage a new version

1. Mark the chosen task 6. With help of the „Manage Version“ Menu it is possible to get an
overview of the versions created and also
2. Click on the button „More Actions“
7. to adjust the versions via the „Edi info“ button
7
2

1
3
6

4
3. Choose: „Save as a Version “
4. Pls. Enter version name and description
5. Push the button „Save“
5
Procedures
Transport Management system – CI-DS FAQ

Q: What happens if I delete a version that was imported already to CI-DS

prod?
A: It’s not possible to delete the version that was promoted to CI-DS PRD
Procedures
Transport Management system – CI-DS

Q: What's the effect in production if I modify in sandbox a version that

was already promoted in CI-DS?
A: Nothing is impacted in PRD. If the task is renamed the system shows a pop message and the task in PRD is also renamed
Procedures
Transport Management system – CI-DS

Q: Can I modify the description of a version that was already promoted in

production?
A: Yes
Procedures
Transport Management system – CI-DS – how to promote

• Filter the task to be promoted in the Name, and go to More Action>Manage Versions
• Under Manage Versions, last version will be created by CI – DS itself while promoting
• Before the last version, there should be 3 levels complete- TUT, FUT, Approved for Production
• Basis will only move to Prod, with an Approved CHG in SNOW, after Approved for Prod is complete

24
Procedures
Transport Management system – CI-DS – how to promote

Click on Promote to move the task to Production

Click to add text

Procedures
Transport Management system – CI-DS – how to promote

Special attention to be paid to the fact that these options are unchecked:
Include source datastore configuration: Should be unchecked
Include target datastore configuration : Should be unchecked

26
Procedures
Transport Management system – CI-DS – how to promote

Datastore configuration also get copied as mentioned in previous slide- both source and target
Following screen gives a confirmation that the task has been promoted to Production.

27
 IBP

BASIS OVERVIEW &

TASKS
 Operational standards-System Monitoring
IBP – Monitoring and Troubleshooting
Operational standards
IBP Monitoring & troubleshooting
Functional Scope Functional Scope SAP Security Functional Scope SAP Basis Functional Scope Functional Scope Functional Scope Functional Scope SAP Basis
Create connections to CPU/RAM, jobs, IBP add-in
description description description description backends (ECC, etc.) description description description description conns by version

Functional Scope Functional Scope Functional Scope ALL TEAMS Functional Scope ALL TEAMS Data Integration / SAP SAP SECURITY ALL TEAMS
Sys params  changed by This is like the sm21 for Basis Similar to SM37 with
description description description controlled group description system logs Useful to see the logs Adjust permissions etc. graphical view of jobs

Meet the Expert: SAP IBP System Monitoring PDF | Recording

Functional Scope Functional Scope

description description

SAP Basis SAP Basis

Create traces for
Troubleshooting Troubleshooting

SAP Basis Functional Functional

Functional Scope Functional Scope Functional Scope Functional Scope
User timeouts etc. description description description description description description 29
Operational standards
IBP – Monitoring and Troubleshooting
Meet the Expert: SAP IBP System & Job Monitoring PDF | Recording

Meet the Expert: SAP IBP System Monitoring PDF | Recording

Summary and documentation

• Resource consumption monitoring CPU/RAM selecting time span smaller
than 60 minutes, shows max values.
• Resource consumption monitoring of CPU/RAM selecting time spam
bigger than 1-hour, shows average values.
SAP webinars and docs

• Resource consumption CPU/RAM values are available for the last 90 days.
• System tasks monitoring is available for the last 7 days.

30
 Operational standards
IBP – System task monitoring Remember! SAP webinars and docs
Meet the Expert: SAP IBP System & Job Monitoring PDF | Recording

Meet the Expert: SAP IBP System Monitoring PDF | Recording

• Click on each tile to know more

details.
1
2

31
Operational standards
IBP – Resource consumption monitoring

• Fiori Apps available to monitor IBP: system monitoring > resource

consumption. Direct links here below
• Prod GDX - System Monitoring (ondemand.com)
• Test GGY - System Monitoring (ondemand.com)
• To see max values, select a 1-hour window of the last 90 days.
Operational standards
IBP – Resource consumption monitoring

• To see average values, select a time span bigger than 1 hour.

33
Operational standards
IBP – Resource consumption monitoring

• If you select a time span older than 90 days, system will alert that’s not
possible.

34
Operational standards
Cloud Availability Center
Cloud Availability Center (requires S-user) 
https://launchpad.support.sap.com/#/cacv2
Example: IBP test GGY 
https://launchpad.support.sap.com/#/cacv2/tnt/000000000741516716

35
Operational standards
Subscribe to Cloud Notifications

• Receive mail notifications about service disruption / degradation (initial,

update, resolved, RCA)
• Be informed about regular maintenance
• Visit Cloud System Notification Subscriptions
• Further information – check SAP note 2900069.

36
Operational standards
Early Watch Alert for SAP IBP

• Released for IBP customers on February

2022
• Requires S-user to have special role
“Service Report and Feedback” added.
• Provides feedback about
• status system parameterization is following
SAP standards or not
• data lifecycle is well maintained or not (e.g.
purge Jobs are running or not scheduled)
• Clients are using right IBP add-in version to
connect to IBP or not
Click here EWA IBP Feb
2022

The super admin has the most authorizations of any s-user in your customer number.
The Cloud admin has display cloud data for the different cloud installations.

37
IBP Parameters
• Parameters to be updated by Basis team only base don the recommendation of functional support, with an
approved Service Now Change.
• This can be done by searching for Global Configuration Tile, searching the parameter and editing.
IBP Communication Scenario- Setup

• For setting up communication with systems, we need to setup communication scenario. It is a one-time
setup only.
• Please follow the below doc for the same
Communication Scenario setup.doc | Powered by Box
IBP Transport Strategy
• Scope: We will only do the import in Production and inform the validator

• Step 1: Login to IBP Prod and go to Import collection

IBP Transport Strategy
• Step 2: If the export has been taken successfully(not done by us), transport will be present in the list to be
imported, for ex in the below SS, transport is ready for import.
IBP Transport Strategy
• Step 3 :If we click on the transport, we can even see the content
IBP Transport Strategy
• Step 4 : Click on import
IBP Transport Strategy
• Step 5 : Click on import, you may write a note if required
IBP Transport Strategy
• Step 5 : Import will start and status will change to importing
IBP Transport Strategy
• Step 5 : Go back and see the status of the import after refreshing the screen, or click on Go button, it will
show as imported, inform the validator, nothing else to be done from Basis side