Thursday, December 14, 2017

Usage of BAPI GetMembers

There is an MDX Function Module (BAPI) available in BW systems for retrieving data. Its name is BAPI_MDPROVIDER_GET_MEMBERS and it is sometimes referred as “GetMembers” BAPI. Sometimes it is worth to use this BAPI as it is used by frontend tools like WebI. While investigating inconsistencies in data provided by the WebI vs e.g. tcode RSRT the BAPI might be good starting point.

In below example I use technical content InfoProvider - 0TCT_MC01 Front-End and OLAP Statistics (Aggregated). Below is example call of the BAPI. The data is returned in table parameter called MEMBERS.

Import parameters            Value
CAT_NAM                         0TCT_MC01
CUBE_NAM                       0TCT_MC01/0TCT_MC01_Q0121
DIM_UNAM                       [0TCTBISBOBJ]
HRY_UNAM                       [0TCTBISBOBJ]
LVL_UNAM                        [0TCTBISBOBJ]
LVL_NUMBER                    01

Wednesday, December 13, 2017

Trace files for BEx tools

Frontend (BEx) tools of SAP BW are supporting recording of traces. Such traces can be useful for providing detail information for SAP support team in case creating incident via SAP Support Site.
How to enable generation of BEx tools trace files? 

In case of the “BEx tools” like Bex Analyzer, Bex Query Designer or BEx Report Designer there is an menu "BEx/Tools" -> "Global Settings" -> “Trace” tab, where set trace level to shall be set to "Verbose" value. Trace files are stored in folder X:\Users\user_name\AppData\Local\Temp\

Example of the trace file name:

In case of Analysis Office for MS Excel/PowerPoint the trece function can be enable via Analysis menu -> "Settings" -> Support tab. Trace files are stored in folder X:\Users\user_name\AppData\Local\Temp\Sap\Cof\
Example of the trace file name:

More information:
948489 - Customer Message requirements for BEx Report Designer
948487 - Customer Message requirements for Web Application Designer
585643 - Extended BW Component Frontend DLL-Usage Analysis

Friday, December 1, 2017

Skip Process Chain’s process – some details

I mentioned possibility of skipping Process Chain’s (PC) process or step in my older posts related to PCs - Automatic restart of failed PChain step and other PC improvements. While using it I found it very useful as it is possible to prevent failure of the PC. 

It happened to me recently that within one PC I skip the process. The PC was successfully finished because the broken process wasn’t executed. However after some time I have set the process to be skipped it I saw that that my PC is failing. I went to the PC itself and I realized that the particular process is not set to skip. Someone simply went to the PC and “un-skip” it. I was curious to learn when and who did it.

I found a table that stores the processes that re to be skipped. It is table RSPCCHAIN_SKIP – “Skipped processes”. But it was my unpleasant surprise that information on who and when the particular process was set to skip is not there. Only information present there are like Process Type, Process Variant (Name), Sequence number, Skip Process. I found it strange to be honest. I tried to debug the particular functionality hoping there are some other tables logging on information I was looking for. I found methods _SET_SKIPPED of class CL_RSPC_FRONTEND. Here really only fields mentioned above are populated. Furthermore another method SET_SKIPPED of class CL_RSPC_CHAIN is called that updates the RSPCCHAIN_SKIP table.

Conclusion is that at the moment (speaking of BW version 74 SP 09) there is no possibility to find out who and when set/unset Skip of process with the PC.

I followed up and wanted to post this missing functionally to SAP idea place as suggestion for future product improvements. I learned that old site is now obsolete and content was moved to Customer Influence site. As per the Data Warehousing in General (CLOSED) suggestion page the SAP BW is “a stable and mature state now.” .. “we have come to the conclusion that there is no longer a need to keep this communication channel constantly open.” In other words do not dare to suggest any improvements to SAP BW – it is stable and matured enough :)