BW objects - Differences between DDIC and DB

BW system generates a lot of temporary database objects while it is running e.g. during query execution, or other processes that read data from BW infoproviders. These objects can be database views or tables. Mostly they are placed in '/BI0/0' namespace.

I wrote some information about the BW temporary objects here. In that blog post I mentioned that program SAP_DROP_TMPTABLES can be used to remove these type temporary objects. However if some of those temporary objects are reported as inconsistent via t-code DB02 there is another program that should be executed. It is program SAP_UPDATE_DBDIFF. The program makes a copy of an information about differences between definitions in ABAP DDIC and in database catalog to table DBDIFF. The DB02 t-code than includes the DBDIFF  table when checking for inconsistencies.

 

More information:

Deletion of temporary database BW objects

t-code RSMNG – Administration of data targets in BW/4

In BW/4 a primary environment of BW administration has moved from SAP GUI to either web or into SAP HANA Studio. In case of the web, it is an FIORI app called SAP BW∕4HANA Cockpit. The BW/4 cockpit can be start from the SAP GUI via t-code BW4WEB (also known as “BW Fiori Launchpad”). Needless to say that in case of the SAP HANA Studio it the modelling part of the BW tasks that is performed in the Studio.

However, in case the BW/4 system is freshly installed/upgraded the Cockpit may not be functioning right off the bat. In addition, there might be issues while installing security certificates of web server, activating web service, obtaining proper authorization, etc. All of these can prevent you from starting to use the Cockpit. On other hand, some old-school BW folks may still prefer to use SAP GUI for administrating of the BW data targets. One strong argument for this is also performance of the web. In case huge data targets (like aDSOs) that are loaded with couple thousands of data requests to browse the requests in the web environment can be tedious. For situations like these, there is a fallback scenario.

It is a t-code RSMNG – with official title as “RSPM MNG UI” or “Administration of RSPM managed targets (aDSO)” or just "MNG UI" or "administration UI". It serves to purpose of managing objects like aDSOs, Characteristics (InfoObjects) and Open Hub Destinations. It is a kind of old “RSA1 -> Modelling -> e.g. InfoProvider -> right click: Manage” navigation; screen - look alike thing. 

The t-code itself allows to manage the data requests like: navigate to the request’s monitor screen, delete/activate/find the request, change its technical status), refresh the requests list, change behavior of the aDSO (planning vs loading), jump to t-code SE16 screen to see the New/Active/Change Log data (depending on aDSO type), perform: Delete Contents, Selective Deletion  etc.

One more interesting feature is “Show Connection” button to analyze the data target by its “connection”. The feature enables quick review of source objects/DTPs that were used to load data to chosen data target.

I find the RSMNG very useful. I do not advice to anyone to use it as SAP may decide to “delist/defunction” it anytime in future releases of the BW as the main environment for BW/4 is above mentioned Cockpit and/or Studio. Also, I do not expect that SAP will enhance the RSMNG any further. From my point of view, there is a lack of DTP integration into it. A description of the DTP could be shown in table grid. For example, an ALV table grid could be customizable so user could choose from a list of available fields what is shown. Similarly, having an options like to copy/delete the DTPs from this t-code would bring further benefit. Anyhow, I find the t-code very useful. 

PS: the RSMNG t-code started to appear in classic BW as well. In particular BW 75 systems.

 

More information:

BW/4 related posts

SAP BW/4HANA (B4H) versions

SAP BW/4HANA (B4H) – what is it?

SAP BW4/HANA related t-codes

BW/4HANA specific objects

SAP BW∕4HANA Cockpit

2859559 - How to use GUI transaction instead BW Cockpit in BW/4HANA 2.0

Number of Processes for DTP Parallel Processing

To speed up runtime of DTP it is possible to parallelize it. There is a possibility to set a maximum number of DTP instances that run in parallel. In t-codes like RSA1->DTP or RSDTP in its menu Goto->Settings for Batch Manager->Number of Processes.

This settings is stored in table RSBATCHPARALLEL (Control Parallel Batch Processes) in field PARALLEL_PROCS (Maximum Number of All Parallel Processes for This type). Corresponding domain is RSBATCHPAR. Table can be read in a way that in field PROCESS_TYPE = DTP_LOAD and into PC_VARIANT = DTP technical name.

Similarly, in t-code RSBATCH there is a possibility to set this via button Parameter Settings under which also number of processes for DTP parallel processing. See more info about the t-code RSBATCH here. This can be setup either set:

1. For all DTPs – means default value for all DTP that do not have it setup, default value is 3

2. Or via button Mass Maintenance of ALL Settings for Parallel Processing for particular DTP

More information:

Degree of Parallelization in SAP BW

Table RSBKADMIN – DTP System Specific Attributes

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

BW classic     RSSTATMAN_REQ_REDUCE_DIALOG          RSSTATMAN_CRITICAL_TARGETS

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

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

SAP BW4/HANA related t-codes

 

In case of BW4/HANA majority of activities are performed either in SAP HANA Studio (mostly modeling activities) or in web environment (mostly administration activities). However, the backend (based on SAP NetWeaver, which is now transitioned to ABAP Platform) is still there.  Here is brief overview of t-codes that are used in BW4/HANA based systems. Most of them are not really the BW4/HANA specific as they may started to appear already in BW classic e.g., BW 7.4 and BW 7.5 based systems.

t-code	ABAP prg	Description
RSMNG	RSPM_MANAGE	Support Function: Manage
HANA_ABAP_PYTHON	HANA_ABAP_PYTHON	execute report HANA_ABAP_PYTHON
HDB_SQLDBC	RSHDB_SQLDBC_CONS	SQLDBC Trace for HANA
ODQMON	SAPLODQ_MONITOR	Monitor for Operational Delta Queue, a new RSA7 t-code
RS_HANA_CONSUMPTION	RS_HDI_SETTINGS	Settings for HANA consumption in BW
RS2HANA_ADMIN	RS2HANA_ADMIN	Administration ext. SAP HANA views
RS2HANA_CHECK	RS2HANA_CHECK	SAP HANA Model Generation Check
RS2HANA_GEN	RS2HANA_AUTH_RUN	Replicate Authorizations to SAP HANA
RS2HANA_VIEW	RS2HANA_VIEW_SETTINGS	Settings for SAP HANA Views
BW4WEB	BW4_WEB_SHOW	BW HANA Cockpit
BW4CHECK	BW4_UI5_IFC_CONSISTENCY	Check BW/4HANA Cockpit Setup
BW4_WEB_START	BW4_WEB_START	BW/4HANA: Web UI Entry Point
RSB4HTRF	RS_B4HANA_TRANSFER	SAP HANA Transformation
RSB4HAPDR	RS_B4HTAPD_APD_LIST	B4H - APD conversion remote
RSB4HCONV	RS_B4HANA_CONVERSION_CONTROL	BW/4 Conversion
RSDD_LTIP	RSDDLTIP_ADMIN	Administration of Analytic Indexes
RSDDSTAT	SAPLRSDDSTAT_UI	Maintain the BW Statistics Settings
RSDHAAP	SAPLRSDHAF_ANALYSIS_UI	SAP HANA Analysis Process Designer
RSDHAAP_MONITOR	SAPLRSDHAF_ANALYSIS_UI	SAP HANA Analysis Process Monitor
RSDHATR	SAPLRSDHAF_ANALYSIS_UI	SAP HANA Transformation
RSDRC_HANA_HIER	RSDRH_ACTIVATE_HANA_HIERS	Activate Use of HANA Hierarchies
RSDSHANA	SAPLRSDS_ACCESS_HANA	Manage SAP HANA Remote Subscriptions
RSDSHANAS	SAPLRSDS_ACCESS_HANA	Overview Realtime Repl. (SAP HANA)
RSHDBMON	RSHDB_MON	HDB Monitoring
RSLIMO	SAPLRSDD_GUI_LM	BW Lean Modeler Test UI
RSLIMOBW	SAPLRSDD_GUI_LM	Composite Providers
RSMIGRHANADB	RSDRI_CONVERT_CUBE_TO_INMEMORY	Conversion to In-Memory Optimized
RSOADSO	SAPLRSO_RES_HCPR_SUPPORT	DataStore (ADSO) Support, a new LISTCUBE t-code
RSOADSODTO	RSO_RES_ADSO_TEMP_MAIN	Temperature Maintenance
RSOADSODTOEXE	RSO_RES_ADSO_TEMP_MAIN_EXEC	Transaction for the DTO Execution
RSOADSODTOS	RSO_RES_ADSO_TEMP_MAIN_START	TX for RSOADSODTO for eclipse calls
RSODSO_BRKPNT	RSODSO_BRKPNT	DataStore-Specific Breakpoints
RSODSO_HDB_LOCK	RSODSO_HDB_LOCK	Management of Native Locks (HDB)
RSODSO_RUNTIME	RSODSO_RUNTIME	Runtime Measurements
RSODSO_SETTINGS	RSODSO_SETTINGS	Maintenance of Runtime Param. DS Obj
RSODSO_SETTINGS_OLD	RSODSO_MAINTAIN_SETTINGS	Parameter maintenance for DataStores
RSODSO_SHOWLOG	RSODSO_SHOW_LOG	Logs for DataStore Object
RSODSO_SQLTRACE	RSODSO_MPP_SQL_LOG	SQL Statements for MPP DataStores
RSODSVIEW	SAPLRSFBP_UI	Open ODS View
RSOHCPR	SAPLRSO_RES_HCPR_SUPPORT	CompositeProvider(HCPR) Support
RSOSM	RSOSN_MAINTENANCE	BW Search on SAP HANA Maintenance
RSPM_MONITOR	RSPM_PROCESS_MONITOR	BW Process Monitor
RSMONITOR	RSCNV_MONITOR	Generic Monitor
RSMRT	RSCNV_DESIGN	Metadata Remodeling Toolbox
RSWQD	RSL_WQD_LAUNCH	Workspace Query Designer
RSWSP	SAPLRSL_GUI_WSP	Workspace Individual Processing
RSWSP_CUST	SAPLRSL_WSP_GUI_CUST	Workspace General Customizing
RSWSPW	SAPLRSL_GUI_WSP	Workspace Mass Processing
UJHANAMDX	UJHANA_MDX_TEST	BPC HANA MDX Test
RSBITC	SAPLBW_BICS_INA_TEST_TOOLS	InA Trace Cockpit
RSBITT	SAPLBW_BICS_INA_TEST_TOOLS	InA Test Monitor