Technical Articles
Roland Kramer

SAP BW/4 2.0 – CAL for it …

SAP BW/4 2.0 as working CAL Image? …

Ripley’s believe it or not, but it is true …

I was in a session with @jakobflaman when we had a look to the CAL library for the latest releases of BW/4 and we found a brand new DEV Image of BW/4 2.0 including the BW/4 1.0 Content Add-On

The good news: while I was updating the Image to SP01 for BW/4 2.0, some new Add-On’s for BW/4 2.0 where available:

  • BW/4 2.0 Content T/B
  • BPC 11.1

With that you can also start using the BPC and IP Applications as well in the BW/4 2.0 environment!

Ok, start you engines and activate the Image (app. 60 min.)

So, the CAL Image is active (on Paper … 😉 what about accessing it?
Check the Getting started Guide (no typo’s this time …)

Good News again: SAP First Guidance – Implement SAP BW/4HANA in the Azure Cloud

Hmm, creating a logon entry in SAP GUI and: nothing happens …

Accessing the OS (check the Cloud FAQ Wiki, not the Troubleshooting Wiki for the Putty access …)

 sappfpar pf=A4H_D00_vhcala4hci check

nothing wrong in the profile, however system is not available …

restarting the system … stopsap/startsap r3 is not available anymore (for your convenience get a copy of the programs from an existing SAP Installation … 😉otherwise:

su – a4hadm
sapcontrol -nr 00 -function Stop/Start
sapcontrol -nr 01 -function Stop/Start

for the sake of the system resources (64 GB for HANA 2.0 2.0.036 and Kernel 7.73 for 7.53)

I have optimized the Instance Profile, as the automatic Kernel calculation calculate itself to death …
Remember: this is a BW system with read optimization …

PHYS_MEMSIZE = 16456 (before 6456)
abap/buffersize = 500000
abap/shared_objects_size_MB = 256
em/proc_max_size_MB = 0
em/proc_use_stdheap = TRUE
ipc/shm_psize_10 = 198000000
ipc/shm_psize_40 = 1978000000
rdisp/elem_per_queue = 2000
rdisp/max_comm_entries = 2000
rdisp/tm_max_no = 6000
rdisp/wp_ca_blk_no = 6000
rsdb/cua/buffersize = 5000
rsdb/esm/buffersize_kb = 131000
rsdb/esm/large_object_size = 67108864
rsdb/esm/max_objects = 2000
rsdb/ntab/entrycount = 50000
rsdb/ntab/ftabsize = 50000
rsdb/ntab/irbdsize = 50000
rsdb/obj/buffersize = 128509 kB
rsdb/obj/large_object_size = 67108864
rsdb/obj/max_objects = 5000
rsdb/otr/buffersize_kb = 16384
rsdb/tbi_buffer_area_MB = 256
rsdb/tbi_dir_entries = 2000
zcsa/calendar_area = 5000000
ztta/roll_extension = 40000000000

Additional Information about the SAP Kernel Configuration – SAP First Guidance – SAP BW on HANA – Edition 2017

still, no sign of the system. HANA is available all the time (maybe to much RAM used)

The system configuration looked a bit weird (but it works, and the external IP is also available …)

SAPDBHOST = vhcalhdbdb
SAPGLOBALHOST = vhcala4hcs
SAPFQDN = dummy.nodomain

The root cause: double entries in the file for sapdp00 and sapgw00 (removing and restart)


SAP BW/4 easy configuration with the task list

So after the system looks somehow “optimized” in ST02,

you should do the client copy if you do not want to work in client 000 (actually I don’t know, if this is still an issue … 😉

Finally, go to Transaction STC01 to configure the task list, and STC02 to execute the task list(s)




Use the file system.xml and update the Instance

Now as everything looks so nice, create the file system.xml in client 000

and go the the Maintenance Planer and update to the latest Components (also the latest 7.73 Kernel):

  • BW/4 2.0 SP01
  • SAP Application Server 7.53 SP02
  • SAP UI 7.53 SP03
  • BW/4 Content T/B initial delivery
  • BPC 11.1 initial delivery

Of course there are additional things to do, like:

  • setting up the BW Modelling Tools
  • Setup the SAP Web Dispatcher for the In-Application Help
  • Setup CORS for the SAC connection
  • etc.

These configuration steps can also be found in the Documents of the SAP First Guidance Collection

Fazit: go for BW/4 2.0 and redefine your Data warehouse requirements!

Roland Kramer, SAP Platform Architect for Intelligent Data & Analytics