SAP BI Strategy and BI portfolio simplification

Being either SAP consultant or guy at SAP’s customer side we all know that there are many BI tools in SAP’s portfolio. Partially it is caused by acquisitions done by SAP over the years but also partially by SAP’s pursuit of new technologies and offerings built on top of them. Basically like in every part of life a lifecycle comes in place and the new offerings (Lumira) are supposed to replace old technologies/tools (BEx) in long run.

It is clear that there has to be done something about all these tools. This is not only to relieve a worries of customers bit. But also as SAP is sticking to their newest strategy: Run simple as echoed in this year spring at annual SapphireNow conference in Orlando. As per run simple mantra it should be up to customers to keep existing BI content in place but from SAP side there is a focus on few core products allowing customers to do possible migration from existing tools to the new ones.

This means the portfolio of SAP BI products should potentially shrink a bit. Some tools will not be developed further and their functions will be covered by other tools. Possible paths of replacements can be as follows:

SAP BusinessObjects Explorer -> SAP Lumira

SAP BusinessObjects Dashboards (Xcelsius) -> Design Studio

*picture taken from blog: SAP BI strategy behind Lumira roadmap ASUG BOBJ conference

Of course one can argument that tools which is supposed to left behind have features which are not included yet in those who are supposed to stay. There are issues like this but there is no “do migration now!” approach. Customers can keep using what they use at the moment but they should evaluate and test new things just in case to be prepared for migration which may come in future.

Further information:

BI strategy

BI Strategy Assessment

Business content (BI Content aka BCT) activation procedure – part II

Long time ago I wrote a short blogpost about Business content (BI Content or BCT) activation procedure. However the post is just really brief. Therefore I establish on that post and will try to improve it within this post.

So what I have to do in order to activate BI Content?

First let’s check if BI Content is present in your SAP NetWeaver based system. This can be done while user is logged in the system e.g. via SAP GUI. In menu of the system choose System -> Status -> Component Information. Here observe if there is software component called BI_CONT. I this is not there then there is nothing to be activated. You need to ask your SAP Basis support about missing component. They have to install it via TA SAINT.

Once it is there you are good to go further. In case of BW system we use TA RSOR to see and further to activate the BCT. While we enter the RSOR we need to know which object we are going to install. If you follow either:

- Standard implementation of e.g. Best Practices or

- Implementation Guide of some SAP solution or

- Documentation of BW’s BCT like in case of Procurement’s Purchase Orders Confirmed as Requested report

just check what objects are supposed to be installed and search for them.

Imagine we go with 3^rd option and we want to activate e.g. report [ABC Analysis - Vendors 0D_NW_EPM_MP01_Q0001]. First we search for that object as per following object:

Once we transfer the object it is useful to set following settings:

Grouping -> Only Necessary Objects – by this only objects which are needed for report’s data flow will be included in activation.

Now we can bring more objects into the list of objects that will be displayed. This is useful in case we want to activate other e.g. reports:

Limitations of BAPI RFC_READ_TABLE

While working with BAPI RFC_READ_TABLE I came across following issue. In case I called the BAPI with input parameters where I specified very large table (e.g. MARA) I got exception DATA_BUFFER_EXCEEDED thrown.

I checked the ABAP code and what it does is that in case of data extracted for a row of table is larger than 512 bytes then exception is raised. This means function call limits extracted data to 512 bytes per row and there is nothing you can do about it.

However there is a kind of workaround available. There is another BAPI Z_AW_RFC_READ_TABLE which doesn't have that limitation. I found the other BAPI working perfectly. All of cases I tested I never got the same issue as with 1^st BAPI.

However you need to notice that the 2^nd BAPI although it is delivered by SAP is included in Z* namespace. The BAPI is included in development package ZDAV which belongs to BusinessObjects Data Integrator (BODS) Development Class. It is not clear to me why it is in Z* namespace. There is already few years after SAP acquired BO so SAP had already enough time to migrate it.

However I must admit that at least the issue is correctly described and documented via SAP Note: 1752954 - DATA_BUFFER_EXCEEDED error - Data Services.

SAP GUI 74

As of Oct 8^th 2014 a successor to GUI 7.3 (for Windows) was introduced. This means product reached its General Availability. Major enhancements are as follows. When it comes to new design there is one new theme called Blue Crystal Design as successor of Corbu. See on picture below where it is compared to Corbu:

Main goal of new theme is to integrate designs of NWBC and SAP GUI. Those two are even integrated more tightly in 7.4. SAP GUI can be embedded into NWBC for example. Also desktop or taskbar icon consolidates sessions of both. Configuration files are the same for both. SAP UI Landscape is introduced in this matter also. It means that GUI session can run either stand alone or embedded into NWBC. So it is same “UI landscape”. Technically UI landscape is configured with single XML file.

There are also installation improvements according accessibility, paths, etc. The 74 GUI has SAP Screenreader (SRX) Extensions.  SRX is now part of GUI.

The 74 version is built on MS Visual Studio 2012 (VS). This VS is supported until January 2018. Therefore the GUI will be maintained till Jan 9^th 2018.

Version 7.4 for JAVA will be released in December 2014.

As always new GUI is downloadable from service.sap.com/swdc -> Installations and Upgrades -> A – Z Index -> G -> SAP GUI FOR WINDOWS -> SAP GUI FOR WINDOWS 7.40 CORE

More information:

New features in SAP GUI 74

Note 2022335

SAP Kernel and its types of releases

- Update 11/01/2019 -

SAP Kernel similarly as kernel of operating system is a central module of SAP application server type of ABAP. It is a basis for all programs executed by ABAP AS. It does represent interface between OS that hosts SAP app and SAP app itself. Physically the kernel is represented by process running on OS (file like SAPEXE, SAPEXEDB, disp+work, tp, R3trans, lib_dbsl). SAP AS kernel is loaded first while SAP system is starting up. It provides all essential services (e.g. memory management) required by SAP application components. It is programmed in C/C++ programming language. There are methods in the kernel that are implemented in the kernel of the ABAP runtime environment instead of in an ABAP program.

SAP kernels is always build for particular version of operating system, database and respective compiler.  This needs to be noticed when files of the kernel are being downloaded from SAP Support portal.

What are different types of SAP kernel?

standard kernel:

This is normal SAP kernel built for specific OS/DB/compiler. By naming convention this type of kernel can be recognized as: ABC_REL (where ABC stands for 3-digit abbreviation of version e.g. 720_REL - standard SAP Kernel. which is downward compatible with older versions of OS and database clients. It was compiled on older versions of OS Compilers and linked to older database client libraries.

Extension Kernel (EXT):

By the time when the OS/DB/compiler for a particular platform reaches the end of support, SAP will make a newer kernel with a newer version of the operating system and compiler called the EXT kernel. From naming convention point of view this can be recognized based on following abbreviation: ABC_EXT e.g. 720_EXT - new extended kernel, which is released for recent OS releases and database clients. It does not support older versions of operating system platforms.

Downward Compatible Kernel (DCK):

The SAP kernel versions are usually developed as downward compatible. This means that higher version kernels may not be only used in systems of same version but in systems of lower versions (e.g. kernel of version 4.6D in system of Basis Component 4.6D but also lower versions like 4.6C, 4.6B, etc.). Notice that there must be an SAP Note published to indicate that recent kernel release can be used as downward compatible kernel. In case there is the DCT kernel available patched for older kernel (replaced by DCK one) are not being provided anymore. Kernels are marked as DCK if the kernel can be used to correct errors without you having to a need to upgrade the system.

UC - UniCode enabled kernel

The kernel has to be upgraded from time time to as there might be an security issues popping up here and there. How the kernel can be upgraded? The kernels are normally upgraded just by replacing executable files directly on OS level file system. Old kernel files are replaced by new one. This is purely technical activity that has no impact on business processes implemented in particular SAP system.

More information:

SAP Kernel: Important News - wiki

1629598 - SAP Kernel 720 will replace older kernel versions

1553300 - 7.20 EXT Kernel - Extended Kernel Maintenance

Software Logistics (SL) Toolset

In the post http://sapport.blogspot.sk/2011/07/different-sap-upgrade-tools.html I mentioned Software Logistics Toolset. Lately I also introduced new tool called Software Provisioning Manager (SWPM) used for SAP basis processes such as installation, uninstallation, system copy, or system transformation. By introducing SWPM SAP basis tools like SAPINST became part of it. But even the SWPM is part of something bigger. It is Software Logistics (SL) Toolset.

Aim of the SL Tool which was introduced in November 2010 is to make SAP software logistics tolls independed from releases of their corresponding SAP application products. By the SL Tool an independent shipment channel is established and the SW tool is decoupled from application SW. The tools in the SL Tool are available in their newest versions and have their own release cycle.

There are two flavors of the SL Toolset:

- CTS Plug-In: add on to NetWeaver based SAP Solution Manager, it enhances standard CTS (Correction and Transport System)

- SAP Add-On Installation Tool and Support Package Manager: manages import of Support Packages Stacks

You can download the SL Toolset from service.sap.com/swdc -> Installations and Upgrades -> S -> SL Toolset -> SL Toolset 1.0

More information:

help.sap.com/sltoolset

help.sap.com/nwcts

help.sap.com/spmanager

service.sap.com/sltoolset

SCN SW community

SAP Note 1563579 - Logistics Toolset 1.0

Software Provisioning Manager (SWPM)

If you are SAP Basis consultant most likely you are aware that this tool. For me as BW guys it was new information that I heard lately. Actually there is a new tool for so called software provisioning. In terms of SAP software provisioning embraces all processes such as installation, uninstallation, system copy, or system transformation of SAP systems. The tool itself is called Software Provisioning Manager (SWPM).

This basically means that our old and much known tool for installation of SAP systems SAPINST (e.g. sapinst.exe on MS Windows OS) is not delivering together with SAP installation media. Instead the SAPINST is bundled into the tool with broader scope – the SPM. What happens is that SAP changed delivery model of their software with introduction of the SWPM. By this installation framework tools (like SAPINST) are independed from product-specific installation (e.g. master DVD) and are not bounded into specific product corresponding delivery cycle. By downloading the SWPM you always get the newest version of it. Therefore do not be confused by e.g. SAP note 1825724 which says in its title: “SAP Software Provisioning Manager has replaced SAPINST and the SAP Installation Master Media as of SAP Netweaver 7.0 SR3 or greater.” The SAPINST is not replaced it is just decoupled from SAP Installation Master Media. Or in this Note 1233320 where it says that SWPM is successor of SAPinst – it is not per se.

You can download SWPM from service.sap.com/swdc -> Installations and Upgrades -> S -> SL Toolset -> SL Toolset 1.0 -> Software Provisioning Manager 1.0

As of now there are two archives, based on supported product version:

- 70SWPM*.SAR: for systems based on SAP NW 7.0x

- SWPM*.SAR: for systems based on SAP NW 7.3x+

More details:

http://scn.sap.com/docs/DOC-30236

Magic of unwanted 3

Recently I found following two funny things in SAP. First one is from ABAP code and second one from SAP BW’s DTP object. Enjoy! J

I tweeted them also.

#DontPanic in #ABAP #fun #SAP #developer CC @SAPdevs

my very EVILicious DTP :) #fun #SAP #BW #developers

Sequencing of function modules execution

Recently I ran into the issue of having one standard SAP function module (FM) which needed to be followed by COMMIT. As you may know such FM do not create any data as the real date need to be posted by the COMMIT. My solution was to create custom ABAP report where I called standard FM first and then BAPI_TRANSACTION_COMMIT.

However later I realized that creation of ABAP report wasn’t necessary. There are feature of Tcode SE37 which allows to you execute several FMs in sequence. By this I can call standard SAP function module and then COMMIT one.

This feature is available on main screen of tcode SE37 under menu Function Module -> Execute -> Test Sequences. There is a pop-up window which allows you to specify the sequence of FMs:

More information:

Function Module Test Sequence SCN wiki

Online docu

ShellShock – UNIX/Linux systems bash vulnerabilities, is SAP affected?

Earlier this year we all experienced a bug in OpenSSL called Heartbleed. Seems there is never enough security issue around and last week ShellShock appeared. The ShellShock is vulnerabilities (CVE-2014-6271 and CVE-2014-7169) in UNIX/Linux’s bash (GNU Bourne-Again Shell) shell.  The bash is command line shell used in many UNIX/Linux/Mac OS based operating systems. Flaw in there can potentially allow attacker execute shell commands. This can be achieved by attaching malicious code in environment variables used by the OS. To fix this patch for needs to be applied for specific OS. A vendor of particular OS needs to provide the patch and customers have to apply it.

In case of SAP as an application running on affected OS situation is as follows. As SAP has standardized its OS scripts on C Shell there should be an issue. However there might be customer’s script still bash based. Therefore a careful and thoroughful checks are advised to be performed.

Anyway SAP is still investigating what influence this vulnerability may have on its software. Therefore keep an eye on SAP Note below to receive up to data information from SAP about the issue.

More information:

2072994 - "ShellShock“ vulnerability (CVE-2014-6271)

Shellshock – Lessons Learned for SAP Customers

Connecting to SAP backend with Eclipse

I bet that many of you already tried ABAP development in Eclipse (AiE). The Eclipse is modern development platform and has a lot to offer also to ABAP developers. I tried the Eclipse recently (see my post: How to install SAP NetWeaver Application Server ABAP 7.03 SP04 Trial – Ready for ABAP in Ecplipse (AiE)) and I must say I like it and currently it is my preferred way of developer IDE. Needless to say that Eclipse is not only for ABAP development but currently there are many other SAP development objects backed by the Eclipse.

Once I started with AiE I tried to use it in as many systems as I have an access to. For some of them it worked for some it didn't. Actually my attempt to connect SAP back-end ended with following error message:

User xyz is not authorized to access system ABC via ABAP in Eclipse (The system does not support Eclipse based ABAP Development Tools).

Therefore I started to look what are prerequisites to connect with the Eclipse to SAP backend system. What needs to be deployed in SAP NEtWeaver ABAP backend is software component called SAP_BASIS_AIE. There are following versions of this component:

SAP_BASIS_AIE version	Available as of	SAP Note
2.0	20.11.2012	1718399 - RTC of ABAP Development Tools for SAP NetWeaver
2.7	07.05.2013	1856574 - RTC of ABAP development tools for SAP NetWeaver 2.7
2.13	12.07.2013	1886449 - RTC of ABAP development tools for SAP NetWeaver 2.13
2.16	20.09.2013	1916008 - RTC of ABAP development tools for SAP NetWeaver 2.16
2.19	04.12.2013	1950493 - RTC of ABAP development tools for SAP NetWeaver 2.19
2.24	28.02.2014	1985505 - RTC of ABAP development tools for SAP NetWeaver 2.24
2.28	22.05.2014	2020847 - RTC of ABAP development tools for SAP NetWeaver 2.28
2.31	14.07.2014	2041627 - RTC of ABAP development tools for SAP NetWeaver 2.31

They all need at least SAP enhancement package 3 for SAP NetWeaver 7.0. Means any SAP NetWeaver ABAP 7.03 SP04 or 7.4 SP00 and higher system.

More information:

http://www.slideshare.net/wolf.gregor/abap-in-eclipse-26193311

What are Eclipse based SAP development tools?

For SAP an Eclipse become an strategic tool. As seen in last few years more and more development tools are moving to Eclipse. The Eclipse is not only the tools for JAVA like languages but SAP is embracing it into more and more offerings for different areas of SAP related development.

Architecture of the tool is as follows. There is a standard open source Integrated Development Environment (IDE) framework of Eclipse. Furthermore there are so called SAP relevant plug-ins into the Eclipse which enhances its functionality for SAP development objects. Plug-in appears in the tool as perspective. There are many different perspectives for different SAP objects.

Here's a short summary of the currently available development tools that are based on the Eclipse:

SAP Visual Composer - A design tool that facilitates the creation of SAP Enterprise Portal content using a visual user interface, rather than writing code. The tool appeared for first time approximately in 2004. Download.

SAP HANA Studio - A collection of tools that manages data and monitors the SAP HANA database. The SAP HANA Studio provides an administration console, a modeler, and a lifecycle management perspective. First time appeared with event of HANA in 2010. Download.

ABAP in Eclipse – First attempts of having Eclipse for ABAP development appeared in Feb 2008. On June 2012 an AiE – ABAP in Eclipse = ABAP Development Tools for SAP NetWaver was released. Download.

SAP NetWeaver Developer Studio – Developers can develop an objects for SAP NetWeaver. Mostly it is related to Web Dynpro for Java applications as there is Web Dynpro perspective available. Also there is a range of toolsets such as the Web Dynpro design time tools, graphical tools for the development of J2EE applications, and Web Service client tools. SAP NetWeaver Developer Studio is integrated into the SAP Java development infrastructure. The SAP NetWeaver Developer Studio appeared approx. in 2005. Download.

SAP NetWeaver Gateway – So called SAP Mobile Platform tools. Development objects are client development objects. The tool helps designing and provisioning OData services for SAP Mobile Platform Download.

SAPUI5 – So called UI Development toolkit for HTML5 (or SAPUI5 tools). SAPUI5 was introduced in 2012. Download.

SAP HANA Cloud Platform tools – Tool for developing of apps for SAP HANA Clpud Platform. Appeared approx. in 2012. Download.

SAP HANA Cloud Integration tools - facilitates the integration of business processes and data across on-premise and cloud applications. Data integration capabilities allow you to efficiently and securely use ETL tasks to move data between on-premises systems and the cloud. It contains following features: Designer and Operations for SAP HANA Cloud Integration. Appeared approx. in 2012. Download.

How to check whether your ABAP NetWeaver is HANA DB based?

Tonight this will be just very short blog post. It is about how to check whether SAP system is running on HANA. In particular how to check that within ABAP program. We can use following statements.

Option 1: Classic way:

IF sy-dbsys NE 'HDB'.
  MESSAGE i398(00) WITH 'this is not HANA'.
ENDIF.

Option 2: More sophisticated way J

IF cl_rs_utilities=>is_hdb_system( ) <> rs_c_true.
  MESSAGE i398(00) WITH 'this is not HANA'.
ENDIF.

Related posts:

How to check whether your ABAP NetWeaver is HANA DB based?

How to find BWA version?

Learn your BW in hard way

What is replacement of Visual Administrator (VA)? NetWeaver Administrator (NWA)

JAVA Visual Administrator (VA) tool (also known as J2EE Visual Administrator tool) is well known for SAP Basis guys. It is graphical user interface (GUI) which enables administration of JAVA related settings across all clusters and all modules running on them. By using it administrator can do things like remote management and monitoring of managers, services, libraries, and interfaces, log files, changing key store etc.

The tool can be started via go.bat (on WINDOWS) or go.sh (on l/unix) from server path: usr/sap///j2ee/admin/

The tool was introduced early when JAVA stack of NetWeaver came to market. What has changed with introduction of SAP NetWeaver 7.1 EhP1 is that Visual Administrator got ramped down and is replaced by SAP NetWeaver Administrator (NWA). 

The new NWA is browser tool for administration and monitoring of SAP NetWeaver JAVA Application Server system. The tool runs as a servlet on the Java engine. 

It is accessible on top of your JAVA stack under following URL: http(s)://:/nwa 

All its function are accessible either via menu within the tool or via URL shortcuts. List of all shortcuts is available on: http(s)://:/nwa/quicklinks

More information:

From VA to SAP NWA

VA online docu

VA wiki page

Replacement of VA