Wednesday, October 6, 2021

Storage data target type in BW Request Management

There are many new storage data types introduced in BW on HANA and even more in BW/4HANA based systems.

In the BW on HANA these are the storage data types that basically corresponds to standard DSO tables:

AQ      Activation Queue

CL      Change Log

AT      Active Table

AR      Archive


In the BW/4HANA many new were added:

AQ        Activation Queue or Inbound Table for DataStore                      /BIC/A<aDSO_tech_name>1

AX        Inbound Table (of Cold Storage)

AT        Active Table for DataStore                                                        /BIC/A<aDSO_tech_name>2

CL        Change Log for DataStore                                                         /BIC/A<aDSO_tech_name>3

RP        Reference Point Table

VT        Validity Table

AQAT    Inbound Table for Master Data Attributes

ATAT    Active Data Table for Master Data Attributes

CLAT    Change Log Table for Master Data Attributes

AQTE    Inbound Table for Master Data Texts

ATTE    Active Data Table for Master Data Texts

CLTE    Change Log Table for Master Data Texts

ATXA    Active Data Table for Master Data XXL Attributes

AQHI    Inbound Table for Hierarchies

ATHI     Active Data Table for Hierarchies

INCL     Active Data Table for SID Structure of Hierarchies

VR        View for Reporting for DataStore                                               /BIC/A<aDSO_tech_name>7

VE        View for Extraction from DataStore                                           /BIC/A<aDSO_tech_name>6

VX        View for external Access for DataStore                                      /BIC/A<aDSO_tech_name>8



Technically the data dictionary domain called RSPM_DTA_STORAGE holds these values.

Thursday, September 30, 2021

Switching between a Standard (New) Debugger & (Old) Classic Debugger

A New ABAP Debugger was introduced in Release 6.40. Since that there was a change in its name. Thus the “NEW” name became obsolete. The New Debugger is called just Standard ABAP Debugger. Similarly, the Old ABAP Debugger is called Classic Debugger.

Normally when you start to use the debugger system jumps to the Standard ABAP Debugger right away. There is no possibility to set the Classic Debugger as default debugger in ABAP Workbench settings (t-code SE80 or SE38 -> Utilities -> Settings) anymore. Thus by default the debugger starts as a Standard one. However, if there is a necessity to use the old one it is still possible.

Once you enter the Standard Debugger via following value that is entered into t-code field (so called “ok-code”) the debugger switches to Classic one:


/hset debugger=classic


Similarly to switch to Standard one:


/hset debugger=standard


Switching the default debugger using above ok-codes is valid for the current logon session only. After the re-logging to SAP GUI it won’t be valid anymore.

Wednesday, September 29, 2021

Simplified menu System -> Status in version 753 based NW systems

On one of social networks, I came across a status pointing to “simplified” pop-up window for menu System -> Status in SAP GUI. In newer systems based on component, SAP_BASIS 753 the window looks different (left part of picture vs old window – right part of picture):

Most likely, a reason of this is a cloud. In cloud systems, there is no need to know that much of details. Information like license no, product versions, time zone info, host and database data are probably not important for users in cloud.  

However, for some of users this information are still useful and needed. Luckily, the old screen is still there. In function group called SHSY there are following screens representing both old and new windows:

Old: 0701 - Kernel information in System->Status

New: 0750 - Status Window for Repository Data in Cloud Systems

The screen that is shown to the users is driven via user’s authorization. It is authorization object called S_SYS_INFO. Users having it assigned will get detailed (old) screen and users without it will get to see the restricted (new) view.


More information:

SAP Note 2658772 - System -> Status: Restriction of the available information

Friday, July 23, 2021

Checking status of cube behavior – BW4HANA

For overview on this topic and BW classic related specific information see following post: Checking status of cube behavior – BW classic.

In BW4/HANA based system there is no information about real-time behavior persistently stored in database like is in BW classic. Instead, the behavior (whether it is loading/staging or planning mode) is evaluated on the fly while user request the change of the behavior. For example if user triggers the behavior change system checks what real-time behavior is set currently and subsequently is changes it to opposite one.

Behavior change in t-code RSMNG:

Behavior change in BW Cockpit:

As the current mode is not stored persistently in database, it is hard to read it without access either to t-code RSMNG or to BW cockpit. However there is a way how to do it. To find out of aDSO is in planning or loading mode, follow below two procedures:

1) Query table RSPMPROCESS with selection:


PROCESS_TYPE                = PLAN

PROCESS_ID                    = */CPMB/ARI* //your planning enabled aDSO object


Then sort a result set via field PROCESS_TSN and check value of PROCESS_STATUS field. If it is Y means PLANNIG request is active in the aDSO thus whole aDSO is in PLANNIG mode. If the PROCESS_STATUS field has value G (Finished) means there is no open yellow planning request in the aDSO thus it is in LOADING mode. Logic that handles flipping of aDSO mealtime behavior is coded in ABAP class: IF_RSPLS_ADSO_API~SET_PLANNING_MODE (CL_RSPLS_ADSO_API).

2) If above-mentioned procedure does not work, you may try this one. Enter the table  RSPMPROCESS with following selection


PROCESS_TYPE                    = PLAN

UNIQUE_TARGET_DATA        = */CPMB/ARI* //your planning enabled aDSO object


Then sort a result set via field PROCESS_TSN in descending way and check value of PROCESS_STATUS field. If the value is Y means the aDSO is in planning mode with active planning request.

Saturday, July 17, 2021

From SAP NetWeaver to ABAP Platform

This post can be simply called as how SAP got from SAP NetWeaver (approx. 1997-2020 even till end of 2030 if we count extended maintenance) to ABAP Platform (2018 or 2019 onwards). This includes relations between all NetWeaver components like SAP Kernel, NetWeaver/BASIS/ABAP component/ABAP platform and corresponding ERP version (on-premise only).

In past there was an SAP term SAP NetWeaver, which was (still is) an umbrella term for SAP’s software stack. It represents an underlying technology component that provides a runtime environment for many SAP applications. Its roots goes back to year 1997 where it started as an internet portal technology (JAVA stack). Afterward an ABAP stack was added into NW Application Server. Other components were added meanwhile too (e.g. Business Warehouse (BW), Enterprise Portal (EP), Process Integration (PI)/Process Orchestration (PO), Master Data Management (MDM), etc.). Thus, it can be called as product family term. Over the years its name was changing. From SAP Web Application Server (although Application server is just a component of NW, this was during a times of SAP R/3 Enterprise) to just SAP NetWeaver. Then to NetWeaver 2004 (mySAP ERP 2004, SAP ECC Core). Subsequently to NetWeaver 2004s (SAP Business Suite). Followed by a name NetWeaver 7.0 (SAP ERP 6.0). The NetWeaver 7.0 had its versions: 7.01, 7.02, 7.03 and 7.31. Next major releases was NetWeaver 7.4 and NetWeaver 7.5. From 7.5 was first release to be used for next generation of *4 products like S/4 (SAP S/4HANA), BW/4 (SAP BW/4HANA). The NetWeaver 7.5 has its versions: 7.50, 7.51 (Innovation Package) and 7.52.

The SAP NetWeaver reached its maturity level and now it is not being developed any more. Instead, it is being transitioned to ABAP Platform. The new ABAP Platform is the foundation of the S/4HANA products starting with S/4HANA 1809.

For details on how long classic SAP NetWeaver will be supported refer to my blog post Life after life of SAP NetWeaver and Business Suite/ECC.

Below is an overview table that depicts a relations between SAP Kernel, NetWeaver / BASIS  / ABAP component  /ABAP Platform and corresponding ERP version with almost all its versions. Notice that are on-premise versions only.

More information:

Life after life of SAP NetWeaver

SAP NetWeaver is 10 years old!

Introducing ABAP Platform 1809

Support package stacks  - product versions

ABAP platform part 1 whats new in ABAP Platform 2020

ABAP platform part 4 whats new in ABAP Platform 2020

2322469 - Support package levels for newly installed SAP systems (NetWeaver, Solution Manager, ERP/ECC etc.)

774615 - Support Package levels of ERP/ECC installations/upgrades

2236608 - Support Package levels of SAP S/4HANA ON-PREMISE installations/upgrades

Wednesday, June 30, 2021

RSREQREDUCE in BW4 - Request Management Housekeeping

T-code RSREQREDUCE (I wrote a blog post about it here) that is present in classic BW systems (since version 74) was redesigned in case of BW4 system. One of the main drivers for a change is that there are no cubes anymore in BW4. The no of requests reduction incorporated into t-code RSA1 (even the BW4’s RSA1 t-code is much more simplified then it use to be in classic BW) under Housekeeping Tasks -> Request Housekeeping or it can be called standalonly via t-code RSREQREDUCE.

In contrary to classic BW the t-code does not display a list of critical data targets right away once it was triggered. Instead, it shows a selection screen which looks like following (screenshot based on BW4 2.0 SP06):

From there it is possible to choose for which Object Type (aDSO, etc) operation of reducing no of requests will be performed. It is possible to select also InfoAreas as Object Type thus the operation can be one on several objects per one shot.

Request reduction operation can be done in simulation mode too (radio button Simulate Housekeeping). That mode certainly helps to understand how many request can be reduced. That is definitely helpful.

On other hand, I liked that the t-code RSREQREDUCE displayed a list of critical data targets right away once it was triggered in BW classic system. However, as the functionality of t-code RSREQREDUCE was reworked the list of critical data targets can be pulled up via ABAP program RSSTATMAN_REQ_REDUCE_DIALOG. Thus old function is still there in BW4 system.

t-code RSREQREDUCE coded in:

                    ABAP program                          ABAP FM/ABAP class


BW4             RSPM_HOUSEKEEPING                           CL_RSPM_HOUSEKEEPING


Technically the t-code is pointing ot ABAP program RSPM_HOUSEKEEPING and processing logic is coded in ABAP class CL_RSPM_HOUSEKEEPING.


More information:

RSREQREDUCE - Reduction of Requests in InfoProv

SAP wiki on housekeeping BW requests

Monday, May 31, 2021

How to check whether it is BW4 system?

This post is similar to one of my previous post called How to check whether HANA or BWA are available? In which I created small ABAP program to determine whether particular SAP system is running on HANA DB or whether BWA is available in the system.

Similarly, to that one in this post I try to determine whether particular SAP ABAP Platform bases system is running BW4 or not. So, it does distinguish between for example just classic BW and BW/4HANA based systems.

The ABAP code fragment is published on my github’s gists place - ZMM_GET_BW_RELEASE_INFO.

The program itself is based on standard SAP program's /SSA/BWT and routine GET_BW_RELEASE_INFO. In case the system is BW4 (component DW4CORE is available) based then it, returns variable lv_ISBW4HANA set to value X. In case it is not, (e.g. it is classic 7.x BW based system) it returns variable lv_BWRELEASE containing the BW release (SAP_BW), e.g. 740 and variable lv_BWSP that contains the BW support package, e.g. 7. The program reads the data from standard SAP table CVERS – that holds an info on release status of software components in System.

T-code SMENQ - replacement for SM12

Within SAP Basis component (ABAP Platform is its new name, not NetWeaver ApplicationServer ABAP Stack anymore) that runs underneath of S/4 systems installations there is a new SAP enqueue server called SAP Standalone Enqueue server 2 available. It was developed to ensure high availability architecture. It comes within ABAP Platform 1809 version. It is a successor to the standalone enqueue server. It is a component of the SAP lock concept and manages the lock table. This principle ensures the consistency of data in an ABAP system.

As a consequence an old t-code that are used to manage locks in the system were refreshed. Some of them are obsolete for long time – such as t-code SM12OLD. Newer ones like RS12 or SM12 are still available but they should not be used. There is more advanced t-code called SMENQ available. It is used for same activities as  old ones – to monitor and administer the server.

More information:

Difference between transactions RS12 / SM12 ?

How to find out SM12 entries...?

BW jobs/work processes hanging within program SAPLSENA

Standalone Enqueue Server 2

Table RSADMIN parameter analysis

Over the years t-code ST13 -> BW tools has been developed a lot. It was introduced since BW 3.5 SP19 and as SAP BW was enhanced in my features a new features were adding into it.

Here’s how the t-code looks like in the recent versions.

BW 74 or 75:

BW4 2.0:

In this blog post, I would like to explore a ST13 BW tools’ feature called “RSADMIN Parameter Analysis”. The feature is coded in routine called RSADMIN_ANALYSIS within ABAP program /SSA/BWT. There is almost 6k of ABAP code lines that are populating many parameters/values of table RSADMIN. The routine output structure corresponds into the ALV grid that is displayed in the t-code after the analysis:


OBJECT              RSADMIN parameter name itself. E.g. /SAPAPO/DEBUG_FLAG

DEFAULT_VALUE  parameter value, e.g. L or R = Read; S or W = write;

NOTE1               Related SAP Note No, e.g.  302937

NOTE2                as above, if there are more SAP Notes related to the same param

TEXT1                Text related to param, e.g. Debugging APO/SEM/CRM/BPC read/write interface in BW 3.x,7.x

TEXT2                 as above                           

AREA                 BW App area of the param on SAP ONE support site, e.g. SAP BW-BEX-OT-DBIF

VERSION_LOW    Lowest BW version that the param is valid from, e.g. 30+

VERSION_HIGH   Highest BW version that the param is valid to, e.g. 700

CATEGORY          Analysis


The feature it-self enables to see if particular param is applicable for the system. Those which are not are displayed as disabled items in the output grid. It allows to quickly displaying relevant SAP Note that describes the particular param in more detail. There is an overview of the default values for the params, from/to BW version that param is valid for, category, etc.

Although the tools is not very dynamic (as all the RSADMIN table are hardcoded); it also doesn’t allow analysis of what current param values are present in the RSADMIN table it is a nice tool that provides a brief overview of the params.

More information:

Suite of helpful BW programs – BW Tools (ST13->BW-TOOLS)

Friday, May 21, 2021

How to check BPC environment state (on/off line)?

BPC Environment is an umbrella term that groups shared metadata, such as dimensions, common configurations, and security, which becomes the basis of one or more BPC models. Normally when the users are working with the BPC the environment must be - available (it is in online state). In case there are, some changes done within its configuration the environment can be taken offline.

There are a few ways how to spot if the environment is in on/off line state.

1. in BPC web client: In Administration under Manage section there is a part related to managing of environments. Here the state of the environments is visible.

2. In EPM Add-in in MS Excel: On log-on attempt into the BPC there is an pop-up announcing that the environment is in offline state.

3. In SAP BPC backend: Via SAP GUI in table UJ0_PARAM_APP and FIELD = AVAILABLEFIELD the environment is in offline state of the value of the field is zero. It is in online state if the value is 1.

Thursday, May 20, 2021

SAP podcasts


Here is a brief list of podcasts related to SAP and all some other topics related to it. The list is compiled based on what is available in this area as of spring 2021.

Podcast name




Coffee Corner Radio

Simon Kemp, Jakob Kjaer,  Martin Fisc



SAP community report

Jerry Janda


Mindset Nebula



SAP Chat

Gerren Mayne


SAP on Azure talk

Ravi Kashyap, Nathan Weaver


SAP HCM Insights

Steve Bogner, Martin Gillet, Amy Grubb, Mark Ingram, Luke Marson, Rebecca Murray, Sven Ringling, Jarret Pazahanick, Brandon Toombs



Bluebeard's Tech Talk


Josh Bentley



Google Cloud – SAP podcast

Brian Dorsey and Mark Mirchandani

English Inside SAP S/4HANA


English SAP Experts Podcast


English SAP Integration & Extension Talk



Industry Insights by SAP



SAP Partner Podcast



English CX cafe


Yurdi Yesilirmak, Benny Kunkel

German SAP AI business services



English Open source way



UI5 NewsCast



The Best Run Podcast



The HANA effect

Jeff Word


Labs talk

Sven Haiges, Erica Davis


SAP and Enterprise Trends Podcasts

Joh Reed