Wednesday, April 28, 2021

SAP and Microsoft Teams

In January 2021, SAP issued an announcement of Microsoft Teams integration across SAP solutions. While having this kind of integration SAP hopes for better collaboration. This can be seem from business user’s perspective. In most cases these users are tied to MS Windows platform and having possibility to collaborate with the Teams e.g. from SAP GUI can perhaps bring a value to such a users.

From SAP product portfolio where this integration will probably happen it is about S/4HANA, SAP SuccessFactors and SAP Customer Experience offerings.

This initiative reminds me about something similar that took place more than 10+ year ago. Back then, it was called a Duet. It is jointly Microsoft-SAP developed product based on MS .NET framework and SAP NetWeaver platform as a foundation for SAP’s ESA (Enterprise Services Architecture). The aim is a seamless data exchange between users's desktop and SAP enterprise applications. One of the use cases was called "Duet for Microsoft Office and SAP". In there, users were able to interact SAP business process and data Microsoft Office via data exchange.

Up to my knowledge, it is not known how successful Duet was. Most of duet product pages are gone in the dust. However, help.sap.com still has some info on it. Similarly, there are some SAP Notes referring to it. Component of the Duet on SAP Support Portal is OPU-DUE (Duet).

There are also people in SAP having working on duet claiming on their linkedin.com profiles.

SAP still owns domain duet.com registered and at this time, it redirects to sap.com.

 

More information:

SAP and Microsoft Expand Partnership and Integrate Microsoft Teams Across Solutions

Duet formerly known as Mendocino

906427 - Mendocino 1.0 Central

Monday, April 12, 2021

SAPJSF user in SAP NetWeaver system?

One may notice in SAP NetWeaver based systems that user SAPJSF is logged in the system. It can be seem in t-codes like SM66, SM04 etc. Such a user ID is basically technical user (type of system or communication) that serves a purpose of communication between UME (User Management Engine of AS Java) and ABAP user management. Means it communicates between two stacks of NetWeaver: ABAP and JAVA in landscapes where both stacks are present (dual stack systems). In the landscapes where only Java stack systems are present it is used for internal communication.

In the ABAP stack it exits in clients 000 and 001.

The user is created during the systems installation. JSF stands for Java Security Framework.

For BW people the user can be familiar because it is also used to run BW (BEx) queries from SAP NetWeaver Portal (former name SAP Enterprise Portal). While the query is running from the Portal the user can be observed in the ABAP stack as logged user.

 

More info:

Online docu

891162 - User SAPJSF does not have authorization for SYST

655349 - SAP WebAS 6.20(+): Missing RFC authorizations for SAPJSF

999962 - PI 7.10 and higher: Change passwords of PI service users

Wednesday, March 31, 2021

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

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

RSB4HTRF

RS_B4HANA_TRANSFER

SAP HANA Transformation

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

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

Friday, March 19, 2021

BW/4HANA specific objects

In next generation of BW systems based on SAP BW/4HANA there are significant changes done with regards to the BW object types. The BW objects are simplified and only few of them are supported. So, what are classic BW object types that are not supported in BW/4HANA?

 

- MultiProviders are Composite Providers (object type HCPR) - tables like RSDCUBEMULTI and RSDICMULTIIOBJ are empty

- InfoSet (object ISET) are Composite Providers (object type HCPR) - table RSQISET is empty

- Cubes (object CUBE) are aDSOs (advanced DSO, object type ADSO) - table RSDCUBE is empty

- Classic DSO objects (object ODSO) are aDSOs (object type ADSO) - table RSDODSO is empty

- Virtual Providers (object flag RSDCUBE-CUBETYPE = V) are now Open ODS Views (object type FBPA, stored in table RSFBP) or BADI Providers - table RSDCUBE is empty

- Hybrid Providers (object flag RSDCUBE-CUBETYPE = H) are now aDSOs (object type ADSO) - table RSDCUBE is empty

- Transient Providers (InfoProvider that allows analysis on top of an application object like SAP Business Suite) are now Open ODS Views or BADI Providers (object type FBPA)

- PSA tables are now aDSOs (object type ADSO) - no tables like /BIC/B00* for PSA of DataDources, but Transfer Structure/Change Logs/Error Stack tables remain in BW4 systems

- No APD (object ANPR) are not supported - tables RSANT_PROCESS and RSANT_PROCESSR do not even exit

- InfoObject Catalogs (object IOBC) are now replaced by InfoAreas (object AREA) - tables RSDIOBC and RSDIOBCT having only values for NODESNOTCONNECTED IO catalogs like:

0CHANOTASSIGNED - Unassigned characteristics

0KYFNOTASSIGNED - Not assigned key figures

0TIMNOTASSIGNED - Not assigned time characteristics

0UNINOTASSIGNED - Not assigned units

 - Open Hub of types 3.x or "Third Party Tool" are not supported, OHs (object type DEST) that are supported (TAB, FILO, FILL) are still present in table RSBOHDEST and RSBDBTAB

- No 3.x InfoSource (object ISTD) present in the BW4 system anymore, as is it not supported - table RSISOSMAP is not present in the BW4 system anymore

 - No Communication Structure (object ISCS) present in the BW4 system anymore, as is it not supported - table RSKS is empty

 - InfoSource 7.x (object TRCS - Communication Structure for Transformation) is still available in table RSKSNEW

  

For classic BW object conversion, see Tools for migrating to SAP BW/4HANA (B4H)

BW/4HANA specific object types tables:

RSOADSO - DataStore Object (although table exits in the system starting from BW 7.4 version)

RSOHCPR – HANA Composite Provider

RSDHAMAP - HANA Analysis Processes

 

 

Typical look into table RSDCUBE in classic BW based system where the table has zero records would be pretty scary. However, in the BW/4HANA based system it is pretty normal :)




Saturday, March 6, 2021

SAP RISE (RISE with SAP)

In January 2021 SAP has come up with a new offering called RISE with SAP. It is the latest move to push a sales of its cloud software. Branded, as the offering that brings all pieces a customers need to have in order to transfer their business. So called business transformation as a service (BTaaS).

(Rise logo – credit SAP)

The service includes, software and hosting offer, which can involve a lift and shift of an existing application portfolio to the cloud, part of process analysis (via acquisition of Signavio), migrations to the latest HANA-backed version of the software and a lot of business process change. Customer signed to this service (on subscription basis) will have one responsible party for service-level agreement, operations and support. It includes: BTaaS, Infrastructure as a Service (from SAP or a hyperscaler (Azure, GPC, most like AWS too)), Cloud Managed Services – CMS (from SAP), and Application Managed Services – AMS (from SAP or a systems integrator).

In past there were similar solutions (although at lower scale) trying to push customers towards running SAP’s HANA based software in cloud. Around year 2013; it was HANA Enterprise Cloud. Back then HANA wasn’t offered by major cloud providers and it required special hardware to run it on. That killed this initiative. Nowadays; the hyperscalers are offering the HANA hosting however, there is another problem. Move to HANA still lacks the business case. There is no killer application for HANA. Similarly, as push to cloud is driven by cloud providers SAP has nothing to say about it to customers. 

With the SAP RISE offering, the SAP is trying to address issues like those. By offering a service of business process mining (included in process analysis /business process change - BTaaS) it can build the case for HANA move (e.g. of legacy ECC running on any DB). By offering cloud migration (CMS), it can help customers who has no cloud experience yet. Finally, by offering AMS on top of above and having it on one single contract (e.g. also having SLAs defined against single vendor) can help to reduce overall TCO. Let’s see in future how does this offering will be picked up by a market.


More information:

RISE with SAP

RISE accouchement

RISE overview

SAP RISE FAQ