Display joblog (SM37) in source system

After having upgraded a customers BI system to version 7.0 last weekend (and worked lots of hours), the last step was to extract the missing delta data from the R/3 source system. As a pre-caution all collective runs were stopped in both clients, prior to the upgrade, so they needed to be restarted (by CONTROL-M).
When I logged on to client A of the R/3 system and watched the joblog of the collective run, I found out that data was extracted from the Qrfc and placed within the delta queue. Unfortunately the delta queue (RSA7) showed no delta data, so I was really puzzled.
Luckely a not so tired colleague pointed out that SM37 is CLIENT INDEPENDENT and thus I was looking at the joblog of the collective run which has ran in client B (Even though I was logged on to client A)!!


To make sure that you're looking at the right joblog, it's advisable to always display the client within the joblog overview.
Settings --> Layout --> Change layout (drag CLIENT from right to left)

Shortdump when accessing a (role) menu

When logging on to a BW system via the SAPGui, you can access your user (role) menu. Within this user menu/SAP easy access menu, a hierarchy of roles/menu entries will be displayed upon wich can be clicked. Clicking such an entry generated a shortdump (MESSAGE_TYPE_X) which was not self explanatory. (Program CL_GUI_CFW====================CP dumps)
Searching OSS led to note 362883 which advised to enter 3 values in table SSM_COL.

The values displayed in the picture above are max. values. Exceeding these max. values has no purpose as the default value will be taken (in case of exceeding).

Inconsistent Multiprovider after upgrade to version 7.0

After having upgraded to SAP BI version 7.0, several multiproviders became inconsistent. (Starting a query, based upon these multiproviders, ended with a BRAIN 152 error)
Inserting a "NO_A135_A152" entry to table RSADMIN solves the problem. You can use program SAP_RSADMIN_MAINTAIN to add an entry to the RSADMIN table
(For more info please check OSS note 1086744)