Client strategy for SAP BW

While SAP BW system is being installed, a decision needs to be done on a client strategy for the system itself. How to decide which client is to be used as BW Client? One important thing to mention is that SAP BW handles only one client in the particular system (see You can only work in client 001). This is contrary to SAP ERP systems where such the system can have multiple clients (see How to get rid of clients 001 and 066 ?). Sometimes the client strategy is referred by a term Client Distribution. Technically the BW client is stored in table RSADMINA and in column BWMANDT. There are following function modules to work with the BW’s client ID:

·        RS_MANDT_UNIQUE_GET Determine BW Client

·        RS_MANDT_UNIQUE_SET Define BW Client Permanently

As a rule of thumb it is recommended to have BW dedicated client in cases like:

·  If data is physically replicated from SAP application to Embedded BW, both the another SAP app and the Embedded BW runs on the same system

· Organization reasons (data separation due to different companies e.g. holding structure, etc.)

There are several aspects to be considered. One of the major one is depending on what type of BW systems it is. There can be following cases:

1 Standalone BW – a full blow BW system, running on dedicated server, has its own client as it is running on its own server separated from other SAP systems.

2 SAP S/4HANA embedded analytics using ABAP-based CDS and the Analytical Engine (automatically generated transient BEx providers). In case organization is using this scenario heavily for many use cases, it is better to create dedicated client for analytics.

3 SAP S/4HANA BPC Optimized using SAP BPC on PAK models. No separate BW client needed unless (similar to the case above) there will be a use cases combining external data with the S4/HANA data.

4 Embedded BW – BW included in SAP ERP systems since SAP NetWeaver 7.0, see more info here.

4.1 Embedded BW usage creating small customer-specific data models for reporting and planning (incl. BPC on PAK), including external data sources to stage data into the Embedded BW (other SAP system, e.g. other SAP ERP/CRM/etc., stand-alone BW or non-SAP legacy system) – no usage as Enterprise Data Warehouse.

4.2 Embedded BW usage to stage data from the same SAP S/4HANA system - separate client for Embedded BW is recommended. E.g. there are multiple S4/HANA clients (dev, testing, training, etc.) along one client dedicated to the Embedded BW.

More information:

Embedded SAP BW Definition and Positioning

You can only work in client 001

Embedded BW 1

Embedded BW 2

BW4 – Parameters of RSADMINA table

I described parameters of table RSADMINA (Control Table That Customer Can Change (Tenant-Specific)) table in my earlier post here. However since introduction of BW/4 systems there are more params in the mentioned table.

 

TLOGO_EXEC_DISAB       TLOGO Types: Automatic Execution Deactivated

 

BW4HANA_SWITCH         SAP BW, Edition for SAP HANA Switch, provides an information about BW4 operating mode.

Possible values:

           unknown (only internal)

0        Add-on not installed

1        Compatibility mode

2        B4H mode

 

TECH_SCOPE                   Operating Scope, so called Data Warehouse mode: Data Warehouse, Embedded BW, and Embedded Analytics

Possible values:

          (NO_BW_SCOPE)

1        Lean Data Warehouse (ANALYTICS_ONLY)

4        BPC Planning only

16      Data Warehouse (DATA_WAREHOUSE)

 

TECH_COMPONENTS        Data element for tech. content component

 

HDI_MODE                       HCPR, IOBJ: Consumption Mode for HANA Native Objects. It checks if HANA DB schema name is equal to ‘_SYS_DI’.

Possible values

0        Repository Version 1 (No HDI Support)

1        Hybrid Support (Repo1 and HDI in parallel)

2        Pure HDI Support (Repo 1 is not supported)

 

ODATA_AUTO_REL           Release OData Service after Generation, whether BW queries are released automatically for OData consumption.

Comparision of RSADMINA table in BW/4 and classic BW systems:

More information:

Parameters of RSADMINA table

Parameters of RSADMINA table

In today’s post I introduce another important customizing table of BW. Among tables like RSADMIN and RSADMINC it is RSADMINA table. Similarly to previous ones it also stores params need to BW system functioning properly.

For BW/4 related RSADMINA params see here.

General parameters

CUSTOMIZID                ID for Customizing in BW. For the BW system a value of this param is always BW.

BWMANDT                    Unique client in BW. For the BW system a value of this param must be maintained.

BWMANDTRFC              Multiple Client Function: Destination in BW Clients. In case BW is used in as system with more than one client then this param is used. It can be a case of an APO system since APO customizing is client dependent unlike BW where it is independent. Param technically enables working with BW in different clients.

TPBWMANDTRFC          After-Import: Destination in Target Clients. This parameter is a destination used during the import post processing for the logon from client 000 into the target client.

BEX_REQUEST               Transport Request number for BEx

BW users related parameters

BW_USER                      User in BW for ALE communication

DEBUG_USER               User permitted for Debugging. Some of BW processes (e.g. staging: loads, DSO activation, etc.) perform a checks for this user and these processes are forced to wait for a specified amount of time before they continue. Therefore never run BW processes with this user.

HANA/BWA related parameters

TREX_RFC_DEST                        RFC Destination for BIA Indexes or HANA appliance

Data loads related parameters

MDINSRECBYREC         Loading Master Data: Use Single Record Insert Statement. Refers to the addition of data records when loading master data attributes. The two values that follow are provided:

initial: For the addition of records to the database, a mass insert statement is used (standard)

X: For the addition of records to the database, a single record insert statement is used (debugging)

PAK_MD_DEL                 Package-Based Deletion of Master Data

MONFILLED                  Monitor initialization completed. Used internally if monitor is run for the first time and has made its initial entries.

IDOCLASTNBR              Last IDoc type number. Param used to define and make unique the name of the basic IDoc type for the source system connection ('number range').

ISLASTNBR                    Last number entered for InfoSource

MONARCHNBR                (Next free) archive number for monitor

XPRADONE                    XPRA executed (2.0a)

ODSMAXTASKS              Maximum Number of Parallel Processes in ODS Activation

ODSMINPAKSIZE          Minimum Number of Data Records per Data Package (ODS Activ.)

ODSACTTIMEOUT          Maximum Wait Time in Secs. for ODS Activation

ENQ_PROT_ON             Switch-on Logs for Lock Manager. Writes an application log for each lock that is requested in the lock manager.

ODSSERVGROUP          Server Group (RZ12) for RFC Call when Activating Data in DataStore used for parallel ODS activation. The parallelization accesses the active table when determining the system ID and during the insert operation. Use tcode RSODSSETTINGS to maintain the param.

Obsolete parameters

DBSYSDEPGLOBL          Name of a generated global program (OBSOLETE)

DBSYSDEPREAD             Name of a generated program (OBSOLETE)

HIERREL                      Release status of application hierarchy DWB (OBSOLETE). . Is evaluated while metadata upload takes place to decide whether the hierarchy is overwritten or not. Used in release 2.0A below       .

TSLASTNBR                   Last number entered of a transfer structure (OBSOLETE)

Related posts:

How to work with RSADMINA table

Finally there is a list of RSADMIN table parameters

How to work with RSADMIN table

You can only work in client 001

You may encounter this error message in freshly installed SAP system. Also newly copied systems are suffering with this message. The message pop-ups while we attempt to run TA RSA1. The only thing that it tells us is current client is not the one that is indented to run BW.

Solution is simple; a proper client needs to be introduced into one of customizing tables. The table is RSADMINA and field is BWMANDT. Just make sure that client where BW is supposed to be is the same as value of this field. Afterwards TA RSA1 is working.