Migration Guide - help.sap.com€¦ · 3 What Does Migration Mean? Migration as Compared to an Upgrade As a system administrator, IT manager, and user you are probably familiar with

CUSTOMER

2017-08-09

Migration Guide

Content

1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Migration Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 What Does Migration Mean?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4 Types of Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

5 Preparing for Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.1 Manage SAP Cloud Platform Integration for Data Services (HCI) Cutover. . . . . . . . . . . . . . . . . . . . . . . 10

5.2 Clean Up Users in the Source System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

5.3 Activate Model Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6 What Does an Assisted Migration Project Look Like?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

7 Post-Migration Steps and Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

7.1 New URL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

7.2 User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Setting Up User Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

7.3 New IBP Excel Add-In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Creating a Connection to the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Setting up Visibility Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

7.4 Reconfigure Jam Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

8 Validation Aspects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

8.1 New Web UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

8.2 Changes in Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Configuration of Key Figures Used in Supply Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

8.3 Planning Operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

8.4 Background Job Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

8.5 Changes in Forecasting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

9 Example: Planning File for Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2 C U S T O M E RMigration Guide

Content

1 Document History

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

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

Table 1:

Version Date Description

1.0 2016-06-23 Initial version

1.1 2016-07-20 Text formally revised

1.2 2016-08-31 Information about attribute length extensions added

1.3 2016-09-09 Information about supply planning key figures added

1.4 2016-10-11 Recommendation about clearing browsing history added

1.5 2016-11-25 Information about user cleanup, maximum number of forecasting steps, and attributes whose length has been extended was added

2.0 2017-02-14 Text formally revised

2.1 2017-03-17 Name SAP Cloud Platform Identity Authentication updated

2.2 2017-04-21 SAP Help Portal reference in section Creating a Connection to the Serverupdated.

2.3 2017-05-10 Name of SAP HANA Cloud Integration changed to SAP Cloud Platform Integration for data services.

Migration GuideDocument History C U S T O M E R 3

http://help.sap.com/ibp

2 Migration Guide

About This Guide

This guide is aimed at the following representatives of companies that use SAP Integrated Business Planning 4.x or 5.x and want to use the highest release available:

● IT decision makers● IT administrators● Consultants

The purpose of this guide is to provide information about what migration means and what a migration project entails, the steps that you need to make to prepare for migration as well as the tasks that you need to perform once the migration is complete and before you can use your new 6.x system.

Notes on Terminology

SAP Cloud Identity (SCI) has been renamed SAP Cloud Platform Identity Authentication service, but the old name SAP Cloud Identity (SCI) is used throughout this guide.


Migration Guide

3 What Does Migration Mean?

Migration as Compared to an Upgrade

As a system administrator, IT manager, and user you are probably familiar with regular upgrades to your IBP system. Typically performed over a weekend, upgrades bring new capabilities to your system, and correct some bugs that might exists. Your system, user management, business data and processes, stay the same, the only changes are new functions added and bugs corrected.

Migration is something different. Because of technological and functional differences between IBP 4.x, 5.x and systems of higher versions, it is necessary to migrate your existing system to a completely new one, which has the following implications for your company:

● You are provisioned an entirely new system● Your existing business processes are migrated to the new system; you can adopt new functions after the

migration project has been completed● Migration is a somewhat more involved process than an upgrade, a fact that we will discuss in detail in

upcoming sections of this guide

Migration GuideWhat Does Migration Mean? C U S T O M E R 5

4 Types of Migration

Depending on your company’s needs, business requirements and situation, you can choose between manual and assisted migration.

Understanding that each company’s system landscape and setup is different, the following sections describe a system landscape with a development, test and productive system. Your company’s setup might differ from the examples below, which means that the migration process at your company might also look slightly different.

Manual Migration

If the following describe your company, you are a good candidate for manual migration:

● Your SAP Integrated Business Planning system is not yet live● You are looking to use the functionality available in the newest-version system as soon as possible● You are planning to adopt the unified planning area● You want to clean up your configuration

During the manual migration process, your company is provided with a new system, which you set up along the following the milestones:

1. SAP provides new tenants (while existing tenants are maintained during the migration period, for approximately 2-3 weeks).

2. You manually set up your configuration on the new IBP tenant while referencing your old tenant configuration.3. You test the new system and configuration.4. Once you are satisfied, the old tenants are decommissioned, and you can use the new IBP system.


Types of Migration

The following figure shows the approximate timeline and steps for a manual migration project:

Figure 1: Timeline of a Manual Migration Project

Assisted Migration

If the following describe your SAP Integrated Business Planning system, you should opt for assisted migration:

● The system is live● It contains complex configuration that you want to keep

During the assisted migration process, the migration tasks are shared by SAP and your company, as follows:

1. SAP provides new tenants (while existing tenants are maintained during the migration period, for approximately 1 week per landscape).

2. SAP runs the migration from your old tenant to your new tenant. This copies all data and configuration from the old tenant to the new tenant.

3. You perform regression tests.4. Once you are satisfied, the old tenants are decommissioned, and you can use the new system.

Migration GuideTypes of Migration C U S T O M E R 7

The following figure shows the approximate timeline and steps for an assisted migration project:

Figure 2: Timeline of an Assisted Migration Project

For more information, see What Does an Assisted Migration Project Look Like? [page 12].


Types of Migration

5 Preparing for Migration

Migration Strategy

Before you start setting up an assisted migration project, it is essential that you work out a migration strategy. The following are some key points that provide guidance to proceed through the migration process:

● Work out a project plan to migrate my entire IBP landscape and determine the resources required● Decide on the planning areas that are brought forward to the new IBP system● Define the identity provider used in the new system and clean up user accounts before migrating (users that

are not required should be deleted before migration starts)● Understand the HCI implications in moving to the new system● Understand how much end-user training is required to cover differences in the new IBP system● Plan for appropriate regression testing

Planning Template

We recommend that you complete a migration planning template to capture important information about your company's IBP system and migration plan, such as the names of contact people involved in the migration process, the names and descriptions of planning areas you want to migrate, a high level model overview, system integration information, and so on.

For more information, see Example: Planning File for Migration [page 32].

Source System Preparation

Some preparation activities are required in your source system as well. These include cleaning up your user landscape and managing switching your HCI from your IBP 4.x or 5.x system to the new IBP system.

For more information, see the following:

● Clean Up Users in the Source System [page 10]● Manage SAP Cloud Platform Integration for Data Services (HCI) Cutover [page 10]● Activate Model Entities [page 11]

Migration GuidePreparing for Migration C U S T O M E R 9

5.1 Manage SAP Cloud Platform Integration for Data Services (HCI) Cutover

During the migration process, to make sure that there is no loss of data during the period of switching from your IBP 4.x or 5.x HCI, to the IBP HCI of the new system, proceed as follows:

1. After your migrated IBP system is made available to you by SAP Cloud Ops, log on to the HCI tenant.2. Find a new application connection with the suffix NW.3. Create a new data store with the new application connection, but keep your old data store that was used in the

IBP 4.x or 5.x system set as the default data store until the new IBP system is not live.4. When the go-live decision for your new IBP system is made and the new system is rolled out, make the new

data store you created for your new IBP system the default data store.

5.2 Clean Up Users in the Source System

In preparation for the migration process, you must clean up users that exist in the source system. This is necessary because if user data is not set up correctly, the users do not get migrated to the target system.

In the IBP 4.x and 5.x system, there might exist users that have no email address assigned to them. Also, there might be users that have been created for demo or testing purposes that are not used or required any more.

In the new IBP system, however, users are uniquely identified by their email addresses with a 1:1 correspondence between user and email address. When you set up the identity provider for your new IBP system, the IDP sends an email with the login information and URL to the email address that is entered for each user. If the email address is incorrect, or missing, the user can't log on to the IBP system.

Steps for Source System IBP 4.x

To prepare your user landscape for migration, proceed as follows:

1. Make sure that each user that you wish to be available in the new IBP system has the following data entered:○ A valid and unique email address

CautionEach user must have exactly one email address assigned to them, and each email address must be assigned to exactly one user. If multiple users are assigned to an email address only one user can be migrated to the new IBP system.

○ First name○ Last name

2. Delete all users that you do not need any more, including demo and test users.


Preparing for Migration

Steps for Source System IBP 5.x

To prepare your user landscape for migration, proceed as follows:

1. Make sure that each user that you wish to be available in the new IBP system has the following data entered:○ A valid and unique email address

CautionEach user must have exactly one email address assigned to them, and each email address must be assigned to exactly one user. If multiple users are assigned to an email address only one user can be migrated to the new IBP system.

○ First name○ Last name

2. Delete all users that you do not need any more, including demo and test users.

NoteIf there are users in your IBP 5.x system without a first name or an email address assigned to them, the users are migrated to the new IBP system.

The system automatically fills the fields where data is missing as follows:

Table 2:

Field Name Automatically Filled Value

First Name UPDATE REQUIRED

Email Address [email protected]

If you want the users to function correctly in the new IBP system, you must enter a valid name and email address in the relevant fields.

5.3 Activate Model Entities

Make sure that the model entities (for example attributes, master data types, time profiles, and so on) that you want to be migrated to the new IBP system are in active status before migration starts. Inactive model entities are not migrated.

Migration GuidePreparing for Migration C U S T O M E R 11

6 What Does an Assisted Migration Project Look Like?

The following section gives you an idea about how an assisted migration project is set up, what steps it includes, what meetings might take place, and who the participants are at each step of the project.

The following process assumes that your system landscape contains a development system, a test system and a productive system. The process description below should be considered only as an example. The number of system tiers in your landscape may be different and therefore, your specific migration process should be modified accordingly.

1. Plan the Migration Project

Table 3:

Activities Participants Duration

Review:

● Project template● Regression test template● IBP documentation: what’s new in IBP, feature

map, user management, integration, IBP Excel add-in

● Your company's IT leader● SAP Customer Office● SAP migration leader

Approximately 2 hours

For more information about the features in the new IBP system, see the SAP Help Portal at http://help.sap.com/ibp .


What Does an Assisted Migration Project Look Like?

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


2. Plan Technical Approach

Table 4:


Discuss:

● Completed migration project and regression test templates and IBP target system sizing (planning for growth)

● The specific plan for your company's migration across your system landscape

● The download location of the IBP Excel add-in and how desktop rollout will be done

● User authentication approach (existing SAP Cloud Identity, new SAP Cloud Identity, corporate identity provider) and location of IBP Identity and Access Management (IAM) training materials

● SAP Cloud Platform Integration for data services (HCI), and migration of HCI content

● IBP functional deltas (changes from prior version, not new modules or features)

● Project risks and contingencies

● Your company's IT● SAP migration

Approximately 2 hours


● User Management [page 18]● New IBP Excel Add-In [page 23]● Validation Aspects [page 25]● Manage SAP Cloud Platform Integration for Data Services (HCI) Cutover [page 10]

SAP Help Portal at http://help.sap.com/ibp , under the following locations:

○ Application Help Planning with Microsoft Excel Installing the IBP Add-In for Microsoft Excel

○ Application Help Administration Identity and Access Management○ What’s New (choose the releases relevant to your target system)

3. Provision IBP Target Systems

Table 5:


Deploy and smoke test empty IBP target systems; number and timing dependent on customer landscape requirements (1, 2, 3 or 4 tier) and rollout plan

SAP Cloud Ops As needed

Migration GuideWhat Does an Assisted Migration Project Look Like? C U S T O M E R 13


4. Freeze Configuration Changes in Source System and Migrate to IBP Target System

Table 6:


Development System

Test System Productive System

● Freeze all changes to source system configuration data and user profiles (document all subsequent configuration changes so they can be applied manually to target system prior to go-live)

● Roll out the new IBP Excel client to relevant user desktops

Your company's IT 1 week 2 days 1 day

● Back up source system and restore backup to IBP target system (upon go signal from your company)

● Run migration procedures on IBP target system (including planning area activations)

● Configure HCI for the IBP target system

● Configure IAM and single-sign-on● Smoke test IBP target system

(planning views, analytics, and so on)

SAP Cloud Ops


● User Management [page 18]● SAP Help Portal at http://help.sap.com/ibp , under the following locations:

○ https://help.sap.com/viewer/eab8fd1726934516a89eabced318b210/1705/en-US

○ Application Help Administration Identity and Access Management




https://help.sap.com/viewer/eab8fd1726934516a89eabced318b210/1705/en-US

5. Regression Test of IBP target system

Table 7:


Development System


● Conduct training on differences from source system (standard IBP training material)

● Ensure all jobs are running correctly (HCI and copy operators)

● Use regression test template to ensure that all existing use cases continue to operate in the new IBP system

● Measure system performance (Web UI, Excel and batch jobs)

● Your company's IT● Your company's

business● SAP migration

1 week 2 weeks 1 day

For more information, see Background Job Management [page 28].

Migration GuideWhat Does an Assisted Migration Project Look Like? C U S T O M E R 15

6. Move Forward with the New IBP Target System

Table 8:


Development System


● Export key figure and master data from source system and import to the IBP target system

● Configure HCI tenant to the IBP target system or set as default (if HCI used with source system)

● Change JAM from source system to the IBP target system (if JAM used with source system)

● Smoke test IBP target system● Announce IBP system cutover

and send new link and login procedure to entire community

● Disable all source system logins● Decommission source system af

ter 1 week of IBP target system stability

● Your company's IT● SAP Cloud Ops

1 day 1 day 1 day


● Manage SAP Cloud Platform Integration for Data Services (HCI) Cutover [page 10]● Reconfigure Jam Integration [page 24]● New URL [page 17]● SAP Help Portal at http://help.sap.com/ibp , under the following locations:

○ https://help.sap.com/viewer/eab8fd1726934516a89eabced318b210/1705/en-US

○ Integration & Analytics Information SAP Jam Integration Guide




https://help.sap.com/viewer/eab8fd1726934516a89eabced318b210/1705/en-US

7 Post-Migration Steps and Considerations

The following are aspects that you need to take into consideration and act upon after migration has been completed. Depending on your company's setup, whether or not you use SAP Jam for collaboration, for example, some of the steps are optional.

● New URL [page 17]● User Management [page 18]● New IBP Excel Add-In [page 23]● Reconfigure Jam Integration [page 24]

7.1 New URL

During the migration process, your company is provisioned a new system and, as a result, your system URL changes too. You as an administrator receive a customized URL and the administrator credentials that you can use to log on to IBP. You can find all of this information in an email sent to the contact person included in the IBP contract.

Figure 3: Sample Email Containing Administrator URL

Second, you need a customized URL for the Administration Console of the SAP Cloud Platform Identity Authentication service. This URL is included in a notification email that SAP sent to the IT contact named in the IBP contract.

Migration GuidePost-Migration Steps and Considerations C U S T O M E R 17

Figure 4: Sample Email Containing the URL for the Administration Console of the SAP Cloud Platform Identity Authentication Service

If it was not you who received this email, the person who received it can create an administrator user for you in IBP, upload it to the SAP Cloud Platform Identity Authentication service, which will then send a similar email to you.

7.2 User Management

Identity and Access Management

User management, user authentication and the provisioning of privileges changes when you migrate your system from IBP 4.x or 5.x to the new IBP system. In the new system, you can perform user management tasks in Web-based Fiori apps of IBP, you no longer need to access back-end transactions such as SU01 (User Maintenance) and PFCG (Role Maintenance).

In the new IBP system, Identity and Access Management (IAM) is the collective name of a set of tools that allows you to manage user access to the Fiori apps and specify what users can see and do in the apps.

The following types of users exist in the new framework:

● Business users for consuming the IBP functionality● Technical users for example, SAP Support users

An initial key user, the SAP admin user and technical users are delivered with the new IBP system.

In the new user management framework, the administrator creates employees in the system, then creates business users for each employee. The administrator then assign business roles to the users and business catalogs that provide access to the apps to each business role. Restrictions can also be set for the business roles


Post-Migration Steps and Considerations

to limit the activities that are allowed and the data sets that are available in the apps. Some of the restrictions are specified in the form of visibility filters.

NoteThe following business roles are created automatically during the migration process:

● SAP_IBP_DATA_IMPORT_REPORTING● SAP_IBP_MODEL_CONFIGURATION_READ_ONLY

These roles are required for technical reasons. You don't have to maintain them at all.

Figure 5: Identity and Access Management

For more information, see the SAP Help Portal at http://help.sap.com/ibp Application Help Administration Identity and Access Management and the relevant FAQ section at http://scn.sap.com/community/scm/ibp .

User Authentication

Before you provide users access to specific apps, you must provide access to IBP itself through user authentication. You can do this in one of the following ways:

● Authentication with SAP Cloud Identity (SCI)● Authentication with a corporate identity provider



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

Figure 6: System Landscape with SCI as Identity Provider

Figure 7: System Landscape with a Corporate Identity Provider

When creating business users, you need to create the same users in the identity provider that your company uses to allow user authentication. You have the following options:

● If you use SCI, you must create all users there as well as in SAP Integrated Business Planning either manually or by uploading them in a CSV file. For more information, see Setting Up User Authentication [page 21].

● If you use a corporate identity provider you must create all users there as well, configure the IDP as a trusted identity provider, and choose it in SCI to be used as the identity provider application.



For more information, see SAP Help Portal at the following locations:

● http://help.sap.com/ibp Application Help Administration Identity and Access Management User Authentication

● http://help.hana.ondemand.com SAP Cloud Identity Service Operation Guide

7.2.1 Setting Up User Authentication

Prerequisites

● You have administrator's privileges in the new IBP system● You have the URL that an administrator can use to log on to the new IBP system

The following sample procedure assumes a system landscape where SAP Cloud Identity (SC)I is used as the identity provider.

Figure 8: Fiori Apps for Identity and Access Management



http://help.hana.ondemand.com

Context

The following procedure describes how you set up user authentication in the new IBP system:

Procedure

1. You create employees in the Maintain Employees app.

You can store employee information such as email, phone number, and so on.2. You create business users in the Maintain Business Users app.

You can store user data, business roles assigned to the business user, and regional settings such as date and time formatting, decimals, and so on.

3. You upload users to SCI tenant in the Maintain Business Users app.a. Click the Download button at the top right corner of the table displaying business users.

A CSV file is created, containing the list of business users.b. Open the SAP Cloud Identity Administration Console and log on with your email address and password.

For more information about where you get the URL and credentials for the logon, see New URL [page 17].c. Choose the Fiori app Import Users.d. Upload the CSV file.e. Click the Send E-mails button, and click Send to send activation emails to users.

The users in IBP are replicated in SCI, and single-sign-on (SSO) is enabled for them. SCI also sends activation emails to users.

4. You can create business roles, and assign business catalogs and users to them in the Maintain Business Roles app.a. You provide general information, such as the name of the business role, its ID and description.b. You assign business catalogs to the business roles.

Business catalogs are delivered by SAP.c. You set up general restrictions, such as read and write access to data by clicking the Maintain General

Restrictions button at the bottom of the Assigned Business Catalogs screen. You can specify the type of read and write access as Unrestricted, Resticted and No Access. If you choose restricted access, you can specify the restriction values as well.

d. You assign business users to business roles in the Assigned Business Users screen by clicking the Add button.

e. Optionally, you can copy business roles, by clicking the Copy button.5. Optionally, you can lock and unlock single or multiple users in the Maintain Business Users app, by selecting

the Locked checkbox in the User Data screen area.

If the checkbox is selected, the users cannot log on to the system.6. You can enable users to share data in the IBP Excel add-in, and Analytics, Cases and Tasks apps by creating

user groups and assigning business users to the user groups in the User Group app. For more information, see SAP Help Portal at http://help.sap.com/ibp , under Application Help Administration Identity and Access Management User Group .




7.3 New IBP Excel Add-In

Installing the IBP Excel Add-In

Once your system has been migrated, your users must install the new Excel add-in that is available with the new IBP system.

For information about the prerequisites for installing the Excel add-in, see SAP Note 2135948 .

Depending on your company's policy, you can allow your users to do the installation themselves, or your IT administrator can install the add-in centrally. In the former case, you must also decide on how you want users to access the installer for the Excel add-in. In general, they can download the installer from the SAP Service Marketplace, provided that they have download privileges for the SAP SMP. Alternatively, your IT Administrator can download the installer, and make it available from your company's file system.

For more information about the different installation types, the steps required, and so on, see the SAP Help Portal at http://help.sap.com/ibp , under Application Help Planning with Microsoft Excel Installing the IBP Add-In for Microsoft Excel .

Setting up Visibility Filters

Visibility filters are a good way to define the set of data that each user can view for each planning view. For information about how to set up visibility filters, and how they can be made available to users, see the SAP Help Portal at http://help.sap.com/ibp , under Application Help Administration Identity and Access Management Visibility Filters .

7.3.1 Creating a Connection to the Server

After migration your company is commissioned a new system with a new URL. Therefore, after your users have the new Excel add-in in place, they must create a connection from the IBP Excel add-in to the new IBP system, so that they can log on to the system and work there. The default logon option uses a SAML-based connection, which means that an identity provider authenticates users before they can access the system.

For more information about creating the connection to the server, see the SAP Help Portal at http://help.sap.com/ibp , under Application Help User Interface Planning with Microsoft Excel Information for Business Users Self-Service Installation (Business Users) Setting Up a Connection to IBP and the Planning Area .

For more information about user authentication, see the SAP Help Portal at http://help.sap.com/ibp , under Application Help Administration Identity and Access Management User Authentication .


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






7.3.2 Setting up Visibility Filters

Visibility filters are a good way to define the set of data that each user can view for each planning view. For information about how to set up visibility filters, and how they can be made available to users, see the SAP Help Portal at http://help.sap.com/ibp , under Application Help Administration Identity and Access Management Visibility Filters .

7.4 Reconfigure Jam Integration

User Authentication

The process of user authentication depends on your company's system landscape. You can use any of the following identity providers to authenticate users in SAP Jam:

● SAP Cloud Identity service (SCI)In this case, the users you create in SAP Integrated Business Planning and SCI are automatically transferred to SAP Jam.

● SuccessFactors FoundationIn this case, you need to create the users in SAP Integrated Business Planning and SCI to get them to work in SAP Integrated Business Planning, and in SuccessFactors Foundation to get them to work in SAP Jam.

● SCI and a corporate identity providerIn this case, SCI acts as a proxy both between SAP Integrated Business Planning and the corporate identity provider, and between SAP Jam and the corporate identity provider. As a result, the users you create in the corporate identity provider are automatically transferred to SAP Jam.

The SAP Jam Integration Guide on the SAP Help Portal at http://help.sap.com/ibp , under Integration & Analytics Information SAP Jam Integration Guide describes how to set up the following:

● SAP Jam to trust SAP IBP as a SAML Identity Provider● The OAuth client in SAP Jam so that the application users can make status posts to SAP Jam from within your

application● The communication system and communication arrangement in your SAP Fiori Launchpad and how to

activate SAP Jam-related Fiori tiles if they are not visible

Tenant Integration

Regardless of the systems used for user authentication, the tenants of SAP Jam and SAP Integrated Business Planning must be integrated to allow collaboration within the apps.

For more information about performing tenant integration manually, see SAP Help Portal at http://help.sap.com/ibp , under Integration & Analytics Information SAP Jam Integration Guide







8 Validation Aspects

The following sections describe aspects that you need to pay attention to after the migration of your system has been completed.

● New Web UI [page 25]● Planning Operators [page 27]● Background Job Management [page 28]● Changes in Forecasting [page 29]

RecommendationIn general, it is a good idea to make sure that your web browser's history is cleared before you start using the migrated system.

8.1 New Web UI

In the new IBP system, the navigation concept is based on the SAP Fiori launchpad, which serves as the access point to all apps for SAP Integrated Business Planning.

For more information about the new Web user interface, see SAP Help Portal at http://help.sap.com/ibp61 , under the following locations:

● What’s New in Release 6.1 English 6.1 Common Features Navigation in the Web Client

● Application Help Working with Web Applications

8.2 Changes in Configuration

Attribute Length Changes

The length of some attributes has been changed in SAP Integrated Business Planning 1608.

CautionThis means that if you are using one or more of the affected attributes with the old attribute definitions in a custom planning area and want to copy an SAP sample planning area with the new attribute definition, the copy of the SAP sample planning area will overwrite your old attribute definitions with the new ones, which might result in inconsistencies in your configuration.

Migration GuideValidation Aspects C U S T O M E R 25


Therefore, you must choose one of the following approaches to avoid possible inconsistencies:

● Keep the new attribute definitionIn this case, you must reactivate the master data types, time profiles and planning areas that use the attributes with the changed length.

● Revert the copy to the old definitionIn this case, you can't use external master data types using these attributes in the copied planning area.

You can find the master data types, planning areas, and time profiles using the affected attributes in the Configuration app, in the Manage Attributes screen, by clicking the link in the relevant cells of the Master Data Types, Planning Areas and Time Profiles columns.

The following table lists the attributes whose length has been changed in IBP 1608:

Table 9:

Attribute Name Attribute Length Up to IBP 6.3

Attribute Length in IBP 6.3

Affected Planning Areas

Affected Master Data Types

SOURCEID 32 66 SAP2

SAP3

SAP4

SAP5

SAPIBP1

S2

S3

S4

S5

SI1

SM4

SOURCEITMID 32 40 SAP3 S2

S3

S4

S5

SI1

SM4

The following table lists attributes whose length has been extended in IBP 1611:

Table 10:

Attribute Old Length New Length

PRDFRDESCR 40 60

PRDTODESCR 40 60

LOCDESCR 40 60

LOCFRDESCR 20 60

LOCTODESCR 20 60


Validation Aspects

Attribute Old Length New Length

RESDESCR 20 60

CATEGORY 20 40

CUSTGROUP 20 60

UOMDESCR 40 60

UOMTODESCR 40 60

CURRDESCR 40 60

CURRTODESCR 20 60

MARKETFAMILY 10 40

For more information, see the model configuration guide on the SAP Help Portal at http://help.sap.com/ibp1608, under Configuration Information.

8.2.1 Configuration of Key Figures Used in Supply Planning

If you were using supply planning in your 4.x or 5.x source system, make sure that the key figures are configured in the new IBP system as follows:

● If a key figure is selected as input for supply planning, all its dependent key figures (key figures used by the input key figure directly or indirectly) must be modeled on the same planning level.

● The key figure calculation chain must end in a stored key figure that is on the same planning level. This means that supply planning input key figures cannot be calculated from key figures that are calculated on other planning levels.

● For any key figure that participates in the calculation chain for supply planning input key figures, you must select Indirect Input for Supply Planning in the I/O for Supply Planning field in key figure configuration.

For more information, see SAP Help Portal at http://help.sap.com/ibp , under What’s New – Release NotesEnglish 6.2 Model Configuration .

8.3 Planning Operators

Planning Operator Types

In the new IBP system, SAP delivers a set of predefined planning operator types that you can use for planning. You can create planning operators based on the delivered planning operator types, but you can no longer create a planning operator type from scratch.


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

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


If you had planning operator types in your IBP 4.x, or 5.x system that you created from scratch, after migration, the operators appear grouped under the predefined planning operator types that are delivered by SAP. The system checks the job procedure and schedule procedure of your custom planning operators and uses them to assess which of the predefined operator types they might belong to.

For more information, see the Planning Operators section of the model configuration guide on the SAP Help Portal at http://help.sap.com/ibp , under Configuration and Deployment Information.

Running and Scheduling Planning Operators

In the new IBP system, you can run and schedule planning operators in the following ways:

● From the IBP Excel Add-inFor more information, see the SAP Help Portal at http://help.sap.com/ibp , under Application HelpPlanning with Microsoft Excel Using Planning Views Simulating Data .

● In the Application Jobs appFor more information, see the SAP Help Portal at http://help.sap.com/ibp , under Application HelpAdministration Application Jobs .

8.4 Background Job Management

In addition to using the IBP Excel add-in, you can schedule and monitor background jobs in the Application Jobs app.

For more information, see SAP Help Portal at http://help.sap.com/ibp61 , under the following locations:

● What’s New – Release Notes English 6.1 Common Features Foundation Apps

● Application Help Administration Application Jobs

During migration, the recurrent scheduled jobs are automatically scheduled in the new IBP system using the same scheduling information and using the migrated planning operators. Jobs that have been executed already are also copied during migration, to preserve the history of job execution.

NoteA scheduled job with an n number of months of yearly recurrence in IBP 4.x and 5.x results in n number of new jobs in the new IBP system where each job has a yearly time granularity and is defined for only one month.


Validation Aspects





Figure 9: Yearly Recurrence with More than One Months

8.5 Changes in Forecasting

Changes from IBP 4.x to versions 6.x and higher

Planning Operator TypesThe planning operator type IBPFORECAST is available in the new IBP system. The planning operator type FORECAST is discontinued. The new planning operator type IBPFORECAST has one planning operator, STATFORECASTING. No further planning operators can be created.

As part of the post-migration activities, you must assign the single planning operator STATFORECASTING to the planning area in place of the old planning operators that are deleted.

Forecast ModelsDuring the assisted migration process, the forecast profiles and algorithm parameters are converted into forecast models. In the new IBP system, forecast models serve as the basis of forecasting and determine which algorithm is used for generating the future forecast. You can create and edit the forecast models in the Fiori app Manage Forecast Models. For more information about the app, see the SAP Help Portal at http://help.sap.com/ibp , under Application Help Advanced Planning Demand Planning Statistical Forecasting Manage Forecast Models .



In the Manage Forecast Models app, you assign forecasting steps to forecast models, each forecasting step representing a forecast algorithm.

CautionThe maximum number of forecasting steps a forecast model can have assigned to it is 999, so make sure that you do not exceed this number when setting up forecast models.

Functional ChangesThe following functional changes apply when you migrate from IBP 4.x to IBP 6.x and higher:

Table 11:

Change Descripion

Forecasting on aggregated levels In the new IBP system, you can run forecasting on aggregated levels, not only on the base planning level of the forecast key figure. You can also simulate forecasting in the IBP Excel add-in.

Prepocessing algorithms Forecasting is enhanced with preprocessing algorithms, such as outlier detection or missing value substitution. These algorithms are always executed prior to the forecasting algorithms. To use these features, you need to check and update the forecast models that were generated from the old forecast profiles during assisted migration.

New forecasting algorithms In the new IBP system more forecasting algorithms are available. For more information, see SAP Help Portal at http://

help.sap.com/ibp , under Application Help Advanced

Planning Demand Planning Statistical Forecasting

Manage Forecast Models .

Handling of multiple smoothing parameter combinations In IBP 4.x it is possible for forecast profiles to refer to multiple smoothing parameter combinations. When these profiles are converted into forecast models during migration, for each parameter combination a corresponding algorithm (such as single exponential smoothing, triple exponential smoothing, etc.) is added to the forecast model with the relevant smoothing parameters.


Validation Aspects



Change Descripion

Filters assigned to a forecast profile In IBP 4.x a filters can be assigned to forecast profiles. In the new IBP system, forecast models can be assigned to individual planning objects. During assisted migration, filters that are assigned to forecast profiles are converted into forecast model assignments, whereby the newly generated forecast model is assigned to all planning objects determined by the filter on the base planning level of the forecast key figure. For more information, see SAP Help Portal at http://help.sap.com/ibp ,

under Application Help Advanced Planning Demand

Planning Statistical Forecasting Assign Forecast

Models .

Group operator In the new IBP system, forecasting cannot be added to the group operator.

Changes from IBP 5.x to 6.x and higher

For information about the functional changes that apply when your source system is IBP 5.x, see the SAP Help Portal at http://help.sap.com/ibp , under What’s New – Release Notes.




9 Example: Planning File for Migration

Table 12:

Overview

Customer name

IBP module subscriptions

High level business solution description

Major use cases (consensus demand, etc)

Number of users, usage pattern (for example, number of users per day

Types of users, user roles

Project Plan

Contact list (email and phone number) for project team members, including named resources from customer IT, customer business, partner and SAP

Project Gantt chart, with specific week numbers

Landscape

Development Test Production

Source IBP system names

Source IBP system ID (SID)

Source IBP system URL

Source IBP system sizes

New IBP system names

New IBP system ID (SID)

New IBP system URL

New IBP system sizes


Example: Planning File for Migration

High Level Model Overview

Planning area names to be migrated, with brief description of each

Master data overview (scale, shared, and so on)

Custom planning operators

User Interface

Excel planning views (templates)

Web UI analytics and dashboards

Web UI alerts

System Integration

Data Flows:

● Sources● Targets● Frequencies● Automated/manual

HCI templates (overview)

Batch jobs

Jam integration

Migration GuideExample: Planning File for Migration C U S T O M E R 33

Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).


Important Disclaimers and Legal Information

http://help.sap.com/disclaimer

Migration GuideImportant Disclaimers and Legal Information C U S T O M E R 35

go.sap.com/registration/contact.html

© 2017 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

Documents

Migration Guide - help.sap.com€¦ · 3 What Does Migration Mean? Migration as Compared to an Upgrade As a system administrator, IT manager, and user you are probably familiar with