Skip to Content
Technical Articles

Upgrade BW/4 2.0 – the time is now …

Last Changed: 11th of September 2019

Upgrade BW/4 2.0 – the time is now …

Since BW/4 2.0 initially was available, it was only possible to start an Upgrade to Version 2.0 without any Add-On’s like BPS or BCS which are available now.
The current Version brings additional Features to the Market – SAP BW/4HANA- Technical Overview
To implement BW/4 2.0 either as on-premise or IaaS see – SAP BW/4 2.0 – CAL for it …
Please also Note, that BW/4 differs from an ABAP 1809 Foundation as follows:

Now let’s see the Upgrade process in the Maintenance Planer (MP)

Preparations for the usage of the Maintenance Planer 

  • Update the SLD with tx. RZ70 from your BW/4 Backend System
  • Synchronize the LMDB from SLD in the Solution Manager
  • Upload the Data to the MP

This is described in detail in the Blog – S/4HANA 1709 FPS03 – back on the Mothership again …

Or as an Alternative, create the system.xml and upload this directly to the MP

If the “Installed Software Component Versions” differ from the “Installed Product Versions”, please make sure that a proper and corrected source system template is used for the maintenance process.


Steps in the Maintenance Planer

Select the target release and released support package(s) …

Adapt your Add-On’s …

Check the Plan Changes for your System …

Add the Non-ABAP components …

Optionally you can deselect the Language Packages you don’t need here to save time/space for the download of the load based export


Download the stack.xml and the software content and you are ready the run the SUM tool

Steps in the Software Update Manager (SUM)

Please Note the following screenshots are already based on SUM 2.0 SP06. So you might see differences in the final version. You will just see the most important screens. Additional Details can also be seen in the Blog – Upgrade to S/4HANA 1809 FPS01/FPS02 – the final frontier

Always get the latest Version from – SAP Software Logistics Toolset

Note 2742706 – Central Note – Software Update Manager 2.0 SP06 [lmt_022]
Note 2690522 – Central Note – Software Update Manager 2.0 SP05 [lmt_021]

As you can imagine, a current Version of SAP HANA 2.0 is mandatory. I chose the latest Version from SP04 – SAP HANA 2.0 SPS 04 Database Revision 042 which will be released soon.

Don’t forget to update the HANA Client for the ABAP System as well, especially when you use a HANA Version from onwards …

Since the Blog – Upgrade was never been easier… was created, the SUM tools for DMO and Upgrade were improved a lot, including the SUM Utilities …

use you resources in the best possible manner and change the process parameters to improve the performance in certain phases over the time and systems …


As for NetWeaver/SAP Application Server based systems like BWoH and BW/4 the option “Single Server” is the optimal option in terms of overall runtime, a shadow instance mandatory used as the BW/4 2.0 sources are available as “load-based” delivery.

Depending on the used scenarios, mixes scenarios (BW/4 and native HANA) are recognized as “MCOD System”, it is one system …

Even you didn’t checked the system before either with the ASU toolbox or the usage of the task list, you can always do the configuration dynamically … (in this case tx. SE14 – clean)

If you will be asked for certain upgrade strategies in the Phase

Note 2452819 – Release strategy for the ABAP add-on BPC4HANA
Note 2805174 – Release strategy and Maintenance Inform for the ABAP add-on BCS4HANA 200
Note 2393067 – Release strategy for the ABAP add-on BW4CONT / BW4CONTB
Note 2705605 – Release strategy and Maintenance Information for the ABAP add-on SAP DSIM 1.0 FOR BW/4HANA

Only Install the Languages you need to save additional runtime …

depending on the installed Add-On’s there might be inconsistencies with the result of the MP and the created stack.xml with the SAP Backend. In this case, you only can go back to the MP and create a new stack.xml based on the updated system.

The minimum installed Version of the BPC 11.0 Add-On on BW/4 1.0 is SP07


Franz Beckenbauer would say: “it’s a classic, ein Klassiker” this is BW my friends … 😉
from now on the time counts …

Now it is time to improve the runtime and the real downtime starts …

Note 2597660 – Lack of performance in phase RUN_RUTDDLSCREATE



The Shadow Instance 

check the Blog – Upgrade to S/4HANA 1809 FPS01/FPS02 – the final frontier for the solution …

check /usr/sap/SUM/abap/system/B42/SYS/profile
add the profile parameters in advance

abap/buffersize = 1400000
abap/heap_area_total = 108197104800
abap/shared_objects_size_MB = 1024
em/initial_size_MB = 65536
em/global_area_MB = 49152
em/proc_max_size_MB = 128000000
em/proc_use_stdheap = TRUE
ipc/shm_psize_10 = 198000000
ipc/shm_psize_40 = 1978000000
rsdb/esm/buffersize_kb = 524288
rsdb/obj/buffersize = 524288
rsdb/otr/buffersize_kb = 16384
rsdb/tbi_buffer_area_MB = 2048
rdisp/PG_MAXFS = 128000
rdisp/PG_SHM = 128000
ztta/roll_extension = 40000000000

Like already described with the S/4 Upgrades: don’t ignore anymore the ACT_UPG Phase, as the return will follow immediately in Phase PARCONV_UPG

Note 2793766 – CDS View cannot be created/activated – Repair tool
Introducing Transaction SDDLAR

Ok, some other hick-up’s which can be solved easily …

Note 2793766 – CDS View cannot be created/activated – Repair tool
Introducing Transaction SDDLAR

make sure your BW-MT and ABAP in Eclipse access is updated to the latest versions – SAP First Guidance – Implementing BW-MT as the new SAP BW Modeling Experience

Note 2607883 – Checking Column view and calculation scenario/ calculation model errors in BW Queries

Is this the end?

Almost … check your original Instance profile for doubled entries …

the software components and the product versions are in sync …

after a short check running SPAU, it seems I have earned some objects in the /SPN/ namespace which were not in the system before …


Finally: The timing and Runtime

Overall I have spent a half day running the MP process and downloading the necessary software. after this I started the Upgrade. Later this day I have continued the SUM procedure and finished the day after. So the netto runtime was 7h, which actually is a good mark. (1st brutto runtime 2d)

SAP BW/4 on premise is back …

Hot of the press: BW-PCA is available for BW/4!

Note 2743291 – PCA for BW/4
Note 2570363 – Availability of BW PCA for BW/4HANA
Note 1707321 – BW System Copy: Post Copy Automation (BW-PCA)
Note 1614266 – System Copy: Post-Copy Automation (PCA) / SAP Landscape Management (LaMa)
Note 2821852 – HANA SDA & SDI connections in context of BW and BW/4HANA system copies

Roland Kramer, SAP Platform Architect for Analytics SAP SE

“I have no special talent, I am only passionately curious.”

Be the first to leave a comment
You must be Logged on to comment or reply to a post.