Sometime around 2018 SAP finally realized that migrating from classing ECC to S/4 is not that easy for a customer. ECC systems are usually heavily customized, bloated with custom code, flooded with numerous background jobs - not clear what data they process and wired in with many interfaces that it is not possible to track what data they bring in/out. Back then the SAP’s introduced a clean core

There are few possibilities for debugging a process chain. In case BW system is based on older versions it needs to be debugged is a background process. This can be done via capturing the background process from the chain’s job. In case the BW system is newer the chain debugging function is available out of the box. In the process chains related t-codes (e.g. RSPC1) when the chain is in EDIT

Recently I encountered a strange DTP runtime figure. The runtime value was displayed in the DTP monitor screen and when I saw it, I rolled up my eyes. The duration of the DTP runtime was 739444Days 12H 59m 29s. That looked really strange to me. When I debug it I saw that the duration is calculated by FM RSSM_SUBSTRACT_TIMESTAMPS. The FM is called by a method TSTMPS_TO_DURATION in ABAP class

Notifications and Subscriptions functionality is available in BW4/HANA based BW systems. In case of the Notifications, the user has a chance to receive notification either via email or to mobile devices about different events that happened in the BW system. The events are following: Process chain run aborted Process chain run completed Process chain run is overdue Process chain run is

While checking process chain there can following message displayed:Processes with Error        Message No. RSPC022 Diagnosis Error occurred when checking the process chain. System Response When errors occur, the system does not activate the chain. Procedure Call the relevant messages for the processes that are marked in yellow and red using the context

Recently I have developed a BW flow to load hierarchies data from one InfoObject to another. I have found a SAP documentation that discusses IO 0H_NORESRNO (Display assigned nodes only) usage in such a data transformations. Recommendation here is to do not map this IO at the transformation due to performance. The IO mentioned is present in the Hierarchy Header segment of the transformation.

When there is an issue related to master data loading following technical program is created in the system: GP_ERR_RSDGTMPLIR. The load itself indicates an error RG 102 - Syntax error in &1, row &2 (-> long text). The error occurs during the generation of master data routines. In particular it is related to SID generation. Characteristics that is effected is listed in the report in its

In case there is a need to recognize programmatically whether the BW system runs in cloud or on-premise there are some options on how to check it. First let’s see how it is regarding HANA DB. There is ABAP class CL_SHDB_HC (HANA cloud base functions). Its method IS_HANA_CLOUD fetches versions of the HANA (major, minor, revision and patch) via calling system function call DB_GET_REL. The method

To check the technical configuration of BW state there is a t-code RS_SICK available. The T-code runs ABAP program RSTCO_200_TEST_CHECKS. It executes different checks for BW functions with relation to the following: &nbsp; <!--[if !supportLists]-->·&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <!--[endif]-->HANA authorizations <!--[if !supportLists]-->·&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <