SAP Universal ID (UID)

User accounts used for SAP support sites (like SAP Support Portal, SAP ONE Support Launchpad, sap.com, community.sap.com, OpenSAP, etc.) that used to be individual for each of the sites are finally becoming consolidated.

It was a matter of critique for many years that there were many different users to be used for particular SAP sites. Mostly each site was acting like a silo application for which user had to register separately. As of July this year, SAP came up with a solution. It is called SAP Universal ID. While creating the UID it allows you to link existing S* or P* users into one universal ID that can be used to login for multiple SAP sites. Currently following sites are being supported by the UID:

    SAP for Me

    SAP.com

    SAP ONE Support Launchpad

    SAP Support Portal

    OpenSAP

    SAP Help Portal

    SAP Training / SAP Learning

    SAP Customer Experience Wiki

    SAP SuccessFactors Community

    Service Now

    SAP CX Microlearning videos & SAP CX DOJO

    SAP Store

    SAP Best Practices Explorer

    SAP Ariba Connect

    SAP Customer Influence Center

See SAP Note 2948407 - Which SAP sites/platforms support SAP Universal ID login? For an up2data list of the supported sites.

Main advantage I see in here is that I could link many different SAP users I have for example to SAP Support Portal into one account. As it is normal, that an independent SAP consultant is working for multiple clients then the consultant has many different S* or P* users belonging to these clients. The SAP UID make the usage of the accounts easier as they can be linked into the one ID. The UID SAP hosted at address me.sap.com can manage all these different S* or P* users by adding/removing them from the UID.

More information:

SAP for Me

SAP Universal ID

Create SAP UID

Support component: XX-SER-UID

Populating BW hierarchy description from custom ABAP code

I recently developed a transformation that generates BW hierarchy on top of InfoObject. I did it via hierarchy transformation type – means source object IO was type of hierarchy and target as well. BW transformation that generates the hierarchy used a custom ABAP code. Within that code I populated the tables for the hierarchy like below.

table1: Hierarchy header

table2: Hierarchy header description

table3: Hierarchy data itself – all the nodes and leaves

table4: Texts of hierarchy text nodes

table6: Text of hierarchy text levels

It took me some time to figure out that I have to use table 2 for these kind of BW hierarchy description. Before I was trying to use also table6 but the system just ignored it. Once I adjusted my ABAP code to populate the table2 there was one more error message.

More than one text specified for hierarchy header for language EN

Message No. RH608

This error was caused due to long text that I populated to some of the fields in the table 2. Once I shortened it, it work fine. Note that depending if you are using Start/End routine there will be either result_package_2 or source_package_2 only.

result_package_2 = VALUE #( BASE result_package_2 (
         objectid = 0
         langu    = 'EN'
         txtsh    = 'Hier1'
         txtmd    = 'PARENTH1'
         txtlg    = 'PARENTH1 hier'
         record   = 1 ) ).

More information:

Simplest Way to Generate a Custom Hierarchy in BW – Without a DataSource & Using Master Data (Attribute/s) Only.

MD maintenance: maximum number of hits

Webdynpro app of master data (MD) maintenance can be sometimes annoying as there is max number of hits defined as 200. That number is sometimes not very convenient. I understand that had to put something in there to prevent performance issues, timeouts etc. However, perhaps some higher number would suit the purpose better.

Luckily, there is an option how to override that default setting of 200. First, there can be an parameter introduced into RSADMIN table called RSDMDM_MAX_NO_HITS. This parameter started to appear in BW version 7.4 SP16. Setting the parameter the no of the hits becomes valid system wide. As always, when it comes to BW switches a user parameter wins over RSADMIN parameter. Thus, it is possible to setup user value via menu System -> User Profile -> Own Data. It must have same name as the RSADMIN table parameter - RSDMDM_MAX_HITS.

If no value exists for the user parameter and if no RSADMIN table parameter value is maintained, 200 is used as the maximum number of hits, by default.

More information:

Deleting BW Master Data

New version of the Master Data deletion

IO's Attributes flag: Delete master data with 0RECORDMODE

How to work with RSADMIN table

BW 74: Master data maintenance: web based environment

2344879 - InfoObject master data maintenance: Configuring maximum number of hits system-wide

Deleting BW Master Data

There are few possibilities how to delete master data in SAP BW. Normally this activity is done via SAP GUI. There are few possibilities how to do it.

1. RSA1 -> InfoObject/InfoProv right click -> Delete Master Data

  
2. ABAP report RSDMDD_DELETE_BATCH

Selection report of the report is similar to popup that follows after right click -> Delete Master Data on InfoObject

3. Master Data Maintance (WebDynpro app)

While user is in RSA1 in InfoObjects area or in t-code RSD1 there is a button Maintain available that triggers webdynpro (WD) application called rsdmdm_md_maintenance_app. The WD allows master data maintenance like adding, deleting and changing the master data.

The WD app was introduced in BW74. I wrote about it here. If someone does not like the WD way of MD maintenance there is still a chance to go back to SAP GUI way.

Also comparing how fast is the data maintenance done via WD vs SAP GUI the GUI way wins. For example deletion of few records done in WD takes sometimes minutes whereas in the SAP GUI it is matter of seconds based on my experience.

In a newer versions of BW system that use Hana Studio (Eclipse based) the maintenance of master data is going on there. In the newest BW like BW/4 it is done via a new web based tool called “SAP BW∕4HANA Cockpit”. See online docu here.

More information:

New version of the Master Data deletion

IO's Attributes flag: Delete master data with 0RECORDMODE

BW 74: Master data maintenance: web based environment