Customer-Based Upgrade


A Customer-Based Upgrade (CBU) is a special version of the Upgrade (AS-ABAP) that can significantly reduce total downtime when you upgrade to Releases SAP R/3 4.6C, SAP R/3 Enterprise 4.70, or SAP ECC 5.0 SR1. Only certified SAP consultants are allowed to perform a CBU.

If you have to do the following, we recommend you to consider CBU:

·        Activate and import a large number of objects

·        Import additional software components such as add-ons (that is, industry solutions)

·        Import a large number of support packages

You can find more information on CBU on SAP Service Marketplace at:  ® Media Library


·        You must create a copy of the production system.

·        After the copy, you must freeze the Repository of the production system. You must manually repeat any transports or corrections made after this point.

·        To reliably estimate the downtime and the time needed for platform-specific load generation, make sure that the hardware used to upgrade the second copy is the same type as the hardware of the production system.


·        Activation time for add-ons and support packages is eliminated.

·        Repository modifications do not increase downtime, as happens with a normal upgrade.

·        Repository objects do not have to be imported after the upgrade.

·        Treatment of post-upgrade transports can be integrated into the CBU upgrade, so reducing downtime.

To decide whether a CBU upgrade offers benefits for your setup, you can perform a standard upgrade in a test system. Ideally, the test system is an identical copy of your production system. By analyzing the resulting upgrade runtime report RSUPGSUM, you can easily determine how much the downtime would be reduced if you were to use the CBU method.

CBU offers the following advantages and risks compared to the standard SAP upgrade:



No dictionary activation

CBU has to be performed by a CBU-certified consultant

No import of repository objects in downtime

Production upgrade is slightly different to standard upgrade

No modification adjustments

Modifications and transports of repository objects in production after first copy need to be handled manually

No transports after upgrade except customizing

Verification of copy system might lead to another export, which increases the time required

Report loads pre-generated and part of export data

Reductions in application adjustment

Reductions in language import

Accurate timing for production upgrade


The following diagram shows the activities involved in a CBU:


       1.      You create a copy (C31) of the production system (P31).

From now on, the Repository of the production system is frozen.

       2.      You perform a standard SAP upgrade of the copy, completing the copy with post-upgrade and other actions in system C46:


                            a.      You perform a modification adjustment in the copied system, or copy the modifications from the development system.

                            b.      You complete the Repository by importing customer developments.

                            c.      You perform ABAP load generation.

       3.      You export the substitution set from the copy (C46) and create the new Repository CDs.

       4.      You create an additional copy (C31') of the production system.

       5.      You test the CDs that have been created by upgrading the copy (C31').

       6.      You verify the upgraded test system (C46').

       7.      You upgrade the production system.