Sunday, January 10, 2021

BPC Master Data tables

BPC dimensions are normally maintained via BPC web client (cockpit). There none of its technical information (e.g. tech name of objects) is shown. Because of that, it is a bit tricky to find out what database tables are storing data for the BPC dimensions. There is a small ABAP program that can serve a purpose of revealing of these database tables. It is called UJ0_GET_GEN_TABNAME and it displays following database tables for given BPC Environment and Model ID:

COMMENT

COMMENT_ARCHIVE

AUDDATA

AUDDATA_A

JOURNAL_DETAIL

JOURNAL_TRANSLATION

MEMBER_ACS

MEMBER_INF

CONTROL_SET

CONTROL

CONTROL_BD

Work Status Lock

In addition to that ABAP program, one can use table UJA_DIMENSION which holds data about BPC’s dimension data table, text table (ending with T) and corresponding BW infoobject.

Friday, January 8, 2021

New features of help.sap.com 2020

SAP Help Portal available at help.sap.com is very well known as a source of all help documentation for any of SAP’s software. Site was improved - mostly over last few years. There were some new features added along site redesign. Recently I came across two feature that I find useful.

1. Personalization – one can log into the help.sap.com (e.g. via SAP Universal ID, SAP Support Portal ID, S*, P* user, etc.). Once logged in, it is possible to store bookmarks (so called My Favorite Pages) of visited pages related to any of SAP software. Similarly, a favorite product (so called My Favorite Product) can be selected. All of these is then available under My Profile part of the help.sap.com. In addition, there is a history of the site searches available too. All the items available are manageable (rename, delete) with My Profile.



2. “Latest” in the URLs – historically all help.sap.com pages were static. Meaning that the URL of the product page uniquely points to certain version of the SAP software product. This is now changed a bit. It is possible to produce the URL that always points into documentation of the newest version of some product.

For example, the URL of the documentation of SAP Business Warehouse 7.5 (SP19) is this:

https://help.sap.com/viewer/ff18034f08af4d7bb33894c2047c3b71/7.5.19/en-US/b2e50138fede083de10000009b38f8cf.html

However, in future if there will be a newer SP available (e.g. SP20) below URL should show the documentation of the latest SP:

https://help.sap.com/viewer/ff18034f08af4d7bb33894c2047c3b71/LATEST/en-US/b2e50138fede083de10000009b38f8cf.html

The trick is a keyword the LATEST that always points to the latest version of particular document.


 

 

Thursday, December 31, 2020

SAP TechEd 2020 Virtual event - my recap

Note: The blog is cross posted on my blog at SAP Community.

This year it was obviously very different experience. Due to pandemic situation mostly all over the world, SAP TechEd event was held virtually. That came with some advantages (it was for free) but some may miss face to face part of the TechEd experience. I think format of this year TechEd will prevail going forward however I think perhaps there will be some parts of it (like pre/after show events) that will not be organized virtually. What about gathering of few SAP aficionados and do the TechEd together at some location? Something like small SAP Inside Track – the TechEd edition? Yeah just an idea. Of course, only in case there is no pandemic :(

I liked a “channel 1”. Even when I had no session scheduled I just tuned in. There was a plenty of information available with regards other sessions that I was not aware of, talks/discussions with community members, guests, replays etc. In general, it served me good to get an overview on what is going on other TechEd topics that I wasn’t initially interested in.

In addition, I found a very useful to follow social media during the event. Especially a discord channel to get a tips what are good sessions to see its replays, see live comments from community or just simply hang out with other TechEd goers.

Naturally based on my job, I followed tracks like Analytics, Database and Data Management in detail and partially App Development and Integration. During the time of the TechEd I focused on session type Workshops and Expert Q&A’s because in these I could leverage the most e.g. while having an access to system, performing exercises, ask live experts etc. Most of regular sessions I watched / will watch on demand afterwards. Concerning the workshops, some of them were not really occupied by attendees – simple people did not show up. This I think had a multiple reasons. As the whole event was free, some people may signed up to just whatever workshop was available at the time they were building their agenda. Later on they either were busy with their daily jobs, they forgot about it because they weren’t notified or simply didn’t care. In future perhaps better notification process would need to be setup. In case of some workshops I attended I got the notification when it was about to start via email from SAP sometimes from zoom. I guess for some people it was confusing.

Most of sessions are available on demand. It creates a useful resource list to study for all attendees. There are many sessions I still want to go through. Thus, I highly appreciate this option to do it on demand.

One more highlight for me was a music theme of the TechEd. It was a song called Mysteries by Richard Lacy and Sarah Mac from album Big & Bold 80's. Great choice I admit.

As I tweeted after the event: ... certainly, a new experience as was all in virtual - but I liked it, good job! thanks #SAP

See you perhaps not virtually only on next year's TechEd :)

More information:

Summary

All TechEd news

Wrap up video

Replays

SAP TechEd in 2020 – A Guide

SAP Cheat Sheet, Special Edition: SAP TechEd in 2020

TechEd-2020 SAP Analytics Q/A Summary (SAP DWC, SAC, BW4HANA) - day 1

TechEd-2020 SAP Analytics Q/A Summary (SAP DWC, SAC, BW4HANA) - day 2

Developer Key Note replay

Developer Key Note samples

Monday, December 21, 2020

BW request types: RSSM vs RSPM

 Traditionally in SAP BW systems there are the BW request types of two kinds, representing a request and status management (RSSM):

1. Request ID (e.g. DTPR_59IOI42WSEVCH90JCT5TCKNZZ) or so called Data Transfer Process Request. It describes a list with calls that is generated from the template of a Data Transfer Process (DTP). In addition, there is information how data in a BW is loaded from a source object to a target object, and which data is transferred to the target object under these conditions.
Data element that represent the Request ID is RSREQUID and it is CHAR30 data type. The value can consists of up to 30 characters literal (numbers and strings).

 

2. SID (e.g. 395.609) or so called key number of a request is the internal encryption of the request number that is allocated by the scheduler. The SIDs are sorted into ascending order. They are used in this maintenance for rolling up and compressing the InfoCube.

Data element that represent the SID is RSBKREQUID and it is INT4 data type. The number can be from interval: -2.147.483.648 to +2.147.483.647

 

Each request has both representation Req ID and SID. They can be converted from one form to another and vice versa. These numbers can be seen in t-code like RSA1 where they represent particular data load. T-code RSRQ (Data Load Monitor for a Request) allows to enter both type of the request.

The Req ID and SID that are based on 0REQUID are referred as called classic request and status management.

In general, all these terms like Request ID, Data Transfer Process (DTP) Request, SID or key number of a request area more less synonyms. One may find all these terms mixed.

3. In BW 7.5 there is a 3rd type of BW request type available. It is called Process Transaction Sequence Number (TNS). It has a formal like below:

{2020-05-12 17:18:11 000001 CET} = 20201512151811000001000

Even t-code RSRQ is extended in BW 7.5 to include this type of the request. It is based on timestamps.  Data element that represent the SID is RSBMREQUID and it is DEC data type with length of 23 and 9 decimals.

More over in BW/4HANA based systems the classic request and status management is not available. It was replaced by the TNS (0REQTSN) and it is referred as request status and process management (RSPM). It is used not only for loading processes but also for data staging, distribution, streaming, and planning processes for InfoObjects, aDSO, and Open Hub Destinations.

Below is a picture how t-code RSRQ looks like in BW lower than BW 7.5 and in the BW 7.5 or in BW/4HANA.


More information:

2482164 - BW4SL - Request and Status Management

2462639 - BW4SL - Interfaces and Customer-Specific ABAP Development

 

Saturday, December 19, 2020

t-code RSPM_MONITOR - BW Process Monitor

Within highest SPs of BW version 7.4 (higher than SP08) in BW version 7.5  (higher than SP03) and in BW/4HANA there is a t-code RSPM_MONITOR available to support BW Process Monitoring in general. Its purpose is to manage load request of aDSO objects.

There is a handful of things can be achieved in this t-code:

1. Changing process status: Active data load request (process) can be forcefully set to red. There is an icon “Change status to red” available for this operation on toolbar. Technically done by ABAP program report RSPM_CLOSE_FAILED_PROCESSES.


2. Monitor the process: The BW process can be monitored. Directly here either in the t-code RSPM_MONITOR or user can jump to the particular DTP, Process Chain or to Manage screen of the involved InfoProvider. 

Notice that since BW 75 a terminology changed a little bit. Data load term is in high level referred as process. This t-code serves to handle all process regardless of what they are. By the process following operations in BW are considered:

·        DTP Load Data (DTP_LOAD)

·        API Load Data (DATA_LOAD)

·        Move Requests (MOV_REQ)

·        Delete Request (DEL_REQ)

·        Activate DSO (ADSO_ACT)

·        Integrated Planning (PLAN)

·        Selective Deletion (SELDEL)

·        Deletion of Master Data (MD_DEL)

·        Remodeling (ADSO_REMOD)

·        DSO Table Conversion (REORG)

·        Data Mart (DMART)

·        Set manually status of Load Request (DTPR_UST)

 

The t-code support regular BW data loads request in form of:

·        Request ID (e.g. DTPR_59IOI42WSEVCH90JCT5TCKNZZ)

·        SID (e.g. 395.609)

·        Process Transaction Sequence Number (TNS, e.g. {2020-12-15 17:52:27 000001 CET})

 

More information:

2574738 - aDSO: Data target &1 is locked by process &2