SAP IBP Normalization and Upgrade

[former_member783850]

Dear Expert,

i have some doubt and question regarding IBP normalization and upgrade.

According to IBP Wiki,all user must perform normalization until end of 2021. New feature for IBP release version 2105 only can be done in normalized data model.

1. Is it necessary if we delayed our IBP normalization process until Dec 2021?

FYI, our IBP system already go live last year using IBP version 2008. So i can say, our user are not using new feature for newer IBP version (let say 2011 onwards)

2. Is there any technical impact?

Thank you,

Warm Regards,

William

[former_member436135 · Accepted solution]

Hi William,

there are two reasons to address normalization migration as early as possible.

Reason number one is that the normalized architecture offers better performance.

Second, as you correctly quote, from IBP 2105, most of the new features will be supported only in normalized systems (Details of affected features will be published with "What's New in 2102" documentation as soon as IBP 2102 will be released end of this week).

If you do not plan to use new 2105 features immediately and are OK with current runtimes, you are not under time pressure. Then you can also consider normalization migration in the second half of 2021.

It will not have any technical impact other that you do not use the normalized architecture and do not benefit from the improved performance.

Best regards,

Andreas Weber

Project Manage IBP Development, Normalization Migration Team

[former_member783850]

Hello Lingaiah,

Thanks for your prompt reply.

FYI, I have read Note 2885767, IBP Wiki, and read the webinar presentation as well.

Thank you,

Warm Regards,

William

[lingaiahvanam]

Hi,

Please refer to below details.

What is Normalization and What Does it Mean for Me?

Normalization is an IBP-internal technical change that affects how data is stored on the data base. For normalization, a new data model is introduced. In this normalized data model, the data base tables in which the data is stored are structured in a different and more efficient way.

From IBP release 1908 onwards, all new customers automatically use the normalized data model. For existing customers, a migration is needed to move the data from the existing data tables of the non-normalized data model to the new data base tables of the normalized data model.

Normalization is done to improve performance, memory utilization, scalability, and robustness.

Starting IBP 2105, most of the new features will be supported only in normalized systems.

The migration from a non-normalized data model to a normalized data model has no direct impact on the user or the business processes.

Migrated systems cannot be reverted to the old non-normalized data model.

When will My Landscape be Migrated?

All customer systems will be migrated over the next releases until end of 2021.

Note that we will schedule the migration for each customer individually based on the readiness of your landscape. We will get in touch with you in due time (approximately 3-6 weeks prior to the scheduled migration).

To be ready for normalization, your planning areas need to fulfill certain prerequisites. You can prepare for migration by completing the tasks described in SAP note 2885814.

Schedule for partner IBP systems

All partner SAP IBP test & demo systems will be migrated to the normalized data model in 3 waves between November 2020 and January 2021.

A Webinar for Partners took place on Sep 30, 2020.

How is Migration Carried Out and What Do I Need to Do?

The migration will be managed and executed by SAP.

The migration runs for several hours (depending on your data volume and the number of planning areas) and requires a downtime. It will be done during the contractual maintenance period(CMP). See FAQ 5 for details.

What impact on performance can be expected?

The normalized data model generally reduces memory consumption and thus improves runtime. The impact depends on the individual modeling of each planning area.

But the architecture of the normalized data model implies one exception: Planning area activation will not be faster. In a normalized data model, planning area activation might take more time as objects are created on the level of planning levels.

More information/Webinar

• On December 2, 2020 a Webinar "Information Session of Upcoming Normalization Migration of Customer SAP IBP Systems" took place.
  • Here are the links to the slides PDF and the Recording.
• The Webinar will be repeated at 7 AM UTC on Feb 10, 2021 for participants in Eastern timezones. You will find the registration link on the "Events and Webinars" page
• For partner systems, see above information on Webinar of Sep 30, 2020.

Frequently Asked Questions

1. After the migration, how can I see whether my system is already normalized?
   If your system is normalized, the message “/IBP/ACTIVATION:196 ‘Planning area activation is running in a normalized data model’” is shown in the activation log. Note that this message does not appear in the check’s log.
2. Is it possible to normalize one planning area only so that we can test?
   No, normalization migration can only be done for the complete system.
3. Do we need to change anything in CPI-DS?
   No changes in CPI-DS are necessary. The staging tables (target tables) remain unchanged.
4. Are any follow on activities needed from customer side after migration?
   Except for testing (we recommend similar test coverage as for a release upgrade), there are no follow-on activities required.
5. During which weekends are migrations possible?
   Migration can be done during the contractual maintenance period (CMP) if the CMP is not blocked by upgrade or Hotfix Collection implementation.
   • You can check the blocked weekends on the Wiki. Here you also find the exact time slot of CMP for your respective data center.
   • If you accept extraordinary downtime, then migration is also possible during other timeslots.
6. Will my complete system landscape be migrated at the same time?
   No, test and production systems will be migrated on separate dates. After the test system was migrated, the production system will follow typically 1 or 2 weeks later. For available weekends, see FAQ 6 above.
   If you are still implementing IBP, migration of test and production system on the same date are possible.
7. How long will the migration take?
   For most systems, the migration will be finished within 4 hours. For systems with huge data volume or a large number of planning areas, migration can take longer.
   Please delete obsolete planning areas prior to the migration to reduce the runtime of the migration.
8. How are normalization migration activities communicated?
   Emails will be sent out to the contacts according to the entries you maintained as Cloud System Notifications Subscriptions (CSNS) for your systems. This includes the information about the planned scheduling, the readiness check a few days prior to the actual migration and the notification about start and end of the migration.

Best Regards,

Lingaiah