Saturday, December 8, 2018

Software Provisioning Manager (SWPM) – list of SAPinst properties

SAPinst is part of Software Provisioning Manager (SWPM)and it is a tool used to logistics of SAP software products. It basically executes installations/upgrades of SAP software. In this post I’d like to list out all parameters (called properties) that can be used while running the SAPinst.

To get an information about version of the SAPinst use parameter: -version It will give a output similar to following:

SAPinst build information:
Version:         749.0.49
Build:           1838559
Compile time:    Apr 24 2018 - 09:56:11
Make type:       optU
Codeline:        749_REL
Platform:        ntamd64
Kernel build:    749, patch 500, changelist 1837688
SAP JRE build:   SAP Java Server VM (build 8.1.038 9.0.4+011, Mar 19 2018 16:55:53 - 81_REL - optU - windows amd64 - 6 - bas2:303791 (mixed mode))
SAP JCo build:   3.0.18
SL-UI version:   2.6.22
SAP UI5 version: 1.50.4

To get a list of all properties just run it with parameter: -p Here are all the properties:

SAPINST_BROWSER Path to the browser executable that is started with the SLP access URL.
Windows only: If SAPINST_BROWSER is not set, the default browser of the system is started. For more information, see SAP Note 2336746.
Value type: string
Default value:

SAPINST_CONTROL_URL Path and name of a control file 'control.xml' or a catalog file 'product.catalog'.
If this parameter is missing, the first unknown parameter that is not a valid parameter is used for control file.
Value type: string
Default value:

SAPINST_CRL_PATH        The path to the downloaded CRL. Download the CRL from https://tcs.mysap.com/crl/crlbag.p7s
Value type: string
Default value: ~/.sapinst/crlbag.p7s

SAPINST_CWD       Directory that is used as working directory. Requires write permissions to that directory.  This parameter has the same effect as previously changing to this directory.
Value type: string
Default value:

SAPINST_EXECUTE_PRODUCT_ID       With this value you can directly process the required option using the attribute ID at the 'component' tag in the 'product.catalog' file, for example id="NW_ABAP_OneHost:S4HANACLOUD.CORE.HDB.ABAP". If no option exists with this ID, the 'Welcome' screen displays all available options.
Value type: string
Default value:

SAPINST_HTTPS_PORT   HTTPS port in SL Common-GUI mode
Value type: number
Default value: 4237

SAPINST_INIFILE_URL   File to be used for reading initial values of component parameters. For more information, see SAP Note 950619. Aliases: SAPINST_PARAMETER_CONTAINER_URL
Value type: string
Default value: inifile.xml

SAPINST_INPUT_PARAMETERS_URL   Path and name of a text file containing 'key=value' pairs to be used preferentially when evaluating component parameters. A component parameter attribute 'defval-for-inifile-generation' defines the key. Its value is used as the initial value when processsing the component for the first time.
Value type: string
Default value:

SAPINST_IPv6_ACTIVE   If set to 'true', the usage of IPv6 is enabled by default
Value type: bool
Allowed values: true = {true, yes, 1}, false = {false, no, 0}. Other values are not allowed.
Default value: false

SAPINST_MESSAGE_CONSOLE_THRESHOLD Trace level console
Value type: string
Allowed values: flow_trace, trace, info, phase, warning, error, external(for ACC)
Default value: error

SAPINST_MESSAGE_DEVLOG_THRESHOLD   Trace level developer logfile
Value type: string
Allowed values: flow_trace, trace, info, phase, warning, error
Default value: flow_trace

SAPINST_MESSAGE_GUILOG_THRESHOLD    Trace level standard logfile 'sapinst.log'
Value type: string
Allowed values:   values: flow_trace, trace, info, phase, warning, error
Default value: info

SAPINST_REMOTE_ACCESS_USER       Name of an OS user who is authorized to log on remotely with name and password via the GUI. By default, this is the user of the SAPinst process. For more information, see SAP Note 1745524.
Value type: string
Allowed values: the login name of the user who can logon to the remote UI
Default value:

SAPINST_REMOTE_ACCESS_USER_IS_TRUSTED     If set to 'true', warnings concerning the remote access user are disabled. This user must be a trusted user.  For more information, see SAP Note 1745524.
Value type: bool
Allowed values: true = {true, yes, 1}, false = {false, no, 0}. Other values are not allowed.
Default value: false

SAPINST_SKIP_DIALOGS          If set to 'true', all dialogs are skipped. Value type: bool
Allowed values: true = {true, yes, 1}, false = {false, no, 0}. Other values are not allowed.
Default value: false

SAPINST_SKIP_ERRORSTEP      If set to 'true', the first step with status ERROR is skipped; step status is set to 'OK'. Value type: bool
Allowed values: true = {true, yes, 1}, false = {false, no, 0}. Other values are not allowed.
Default value: false

SAPINST_STACK_XML     Path and name of the stack configuration file 'stack.xml' as described in SAP Note 1680045.
Value type: string
Default value:

SAPINST_STACK_XML_ACTIVE_SID    For unattended mode only: Contains the SAPSID of the active target system if working with a stack configuration file 'stack.xml'.
Value type: string
Default value:

SAPINST_START_GUI      If set to 'true', on Windows the default browser starts automatically with SL Common UI.
Value type: bool
Allowed values: true = {true, yes, 1}, false = {false, no, 0}. Other values are not allowed.
Default value: true

SAPINST_START_GUISERVER   If set to 'true', the SL Common UI server starts automatically. Alternatively, option '-noguiserver' can be used to turn off the SL Common UI server.
Value type: bool
Allowed values: true = {true, yes, 1}, false = {false, no, 0}. Other values are not allowed.
Default value: true

SAPINST_STOP_AFTER_DIALOG_PHASE       If set to 'true', the execution stops after processing all steps of the 'Define Parameters' phase. Used for generating parameter files only. If set to 'false', the 'Execute Service' phase is also performed.
Value type: bool
Allowed values: true = {true, yes, 1}, false = {false, no, 0}. Other values are not allowed.
Default value: false

SAPINST_TRACE_JSLIB   Switch to activate the JS trace functionality for specific JS classes. The values 'flow_trace' and 'Retry' activate the flow trace. Aliases: SAPINST_JSLIB_TRACE
Value type: string
Allowed values: comma separated list of JS classes or all
Default value:

SAPINST_TRACE_KERNEL         Determines the trace level of the kernel trace library   Aliases: SAPINST_MSLIB_TRACE
Value type: number
Allowed values: 0, 1, 2 or 3
Default value: 1

SAPINST_TRACE_RFC      If set to 'true', traces for RFC calls are written. CAUTION: This can cause passwords to appear in logfiles. Aliases: SAPINST_RFCLIB_TRACE
Value type: bool
Allowed values: true = {true, yes, 1}, false = {false, no, 0}. Other values are not allowed.
Default value: false

SAPINST_USE_HOSTNAME        The framework returns the value of that property if the getHostName() function is called. The value is not checked. For more information, see SAP Note 1564275.
Value type: string
Default value:


Selfextractor properties:
-sfxver:
  display selfextractor version information within a message box and ends.

-sfxverNB (Windows only):
  prints selfextractor version information without a message box and ends.

-noMessageBox (Windows only):
  Selfextractor errors are usually displayed within a message box.
  Using this parameters suppresses message boxes and errors are written to stdout only.

-exitOnError (Windows only):
  After a successful installation the selfextractor window is closed automatically.
  In case of an error the window stays open to show logging information.
  Setting this property will close selfextractor window automatically also in error case.

-extract [
]:
  unpacks SAPinst files to
or to current directory if is not specified.
  If
does not exist it is created.

* Example of property usage:
SAPINST_SKIP_DIALOGS=false

Return codes:
0   success
1   unknown exception
2   user decided to stop
3   iSeries specific initialization problem
4   framework error; contact SAP support (BC-INS-FWK)
5   incomplete service; contact SAP support (fitting subcomponent below BC-INS)
6   stop after dialog phase requested
7   unknown exception during step execution
8   problems creating support archive
9   problems in GUI subsystem; contact SAP support (BC-INS-FWK)
10  SLC could not be started in server mode because of missing encryption jars within the used JVM
11  executed step requested to "abort the installation"
12  terminated by a signal
13  service needs to display a dialog but no GUI is available; restart SAPinst with GUI.
14  executed step stopped service execution
15  problems concerning the SDT server's user (default 'sapsdt')
16  problems with loading of DLL modules (only for Windows)
17  framework error; see console output
18  reserved for framework issues ; not used at the moment
19  reserved for framework issues ; not used at the moment
20  reserved for framework issues ; not used at the moment
21 - 110  error code was defined by an exception thrown by an installation step
 // see message.xml
111 step execution ends with an error without specifying an return code via messages identifier
112 - 126 error code was defined by a exception thrown by an installation step
 // see message.xml

Monday, December 3, 2018

BW/4HANA: Custom ABAP code in transformations

In BW/4HANA there are some changes with respect to a usage of ABAP code in transformations. In classic BW there are areas called "1st and 2nd global declarations" (*$*$ begin of global ... *$*$ end of global) available where to place ABAP routines. Normally we can use both of the global declaration areas in the classic BW. It only makes a difference in case that the ABAP code shall be able to be reached globally in the transformation we go for 1st global area. The 2nd one is originally used for the transformations which are migrated from an update or transfer rules.

In the BW/4HANA only the first global area is respected. The 2nd global area is not supported by the BW/4HANA – it no longer exists. In reality there is just one global area – called global part but the global part is not supposed to be used, it is optional. All custom code shall be placed in the local part of the routine. The ABAP routine is a methods of a local ABAP class that consist of a predefined definition and an implementation area.

For existing transformations this also means that the transformation that uses 2nd global area won’t be displayed in the Eclipse - in the BW Modeling tools. SAP GUI will be opened instead. Then a manual migration needs to happed in the SAP GUI and code from 2nd global area must be moved to 1st global area in order to migrate such transformation to the BW/4HANA.

Another point is that existing custom ABAP code that shall in BW/4HANA must be ABAP OO compatible. Means statements that are non-compatible with ABAP OO coding needs to be removed and the code must be refactored to be the ABAP OO correct. Examples of non-compatible things can be: obsolete statements used in the code like internal tables with header, includes, etc. Again such transformations will be opened in SAP GUI to make required changes.

No need to mention that all this is only valid in case the transformation is being executed by ABAP runtime. This is to be selected in Runtime Properties of the transformation. Of course there can be routines in SAP HANA SQLScript in case the transformation is being executed by SAP HANA runtime.

More information:
2654109 - Conversion of ABAP/AMDP routines/exits in SAP BW/4HANA to the processing in Eclipse
2639435 - Transformations are opened in SAP GUI instead of in Eclipse
2462639 - BW4SL - Interfaces and Customer-Specific ABAP Development
ABAP Routines in Transformations

Sunday, December 2, 2018

BW/4HANA Simplifications (BW4SL)

One of strengths of BW for HANA aka BW/4HANA (BW/4, B4H, BW4) is simplification. This comes as something that can’t be seen (e.g. removal of approx. more than 5 million lines of ABAP SAP BW code) and also more visible changes that need to be adapted otherwise it will break BW systems once moved to BW/4 e.g.:

- changes to official interfaces (RSNDI, RSDRI)
- deletion of old/obsolete customer exits (CMOD) and BAdI methods for exit variables that are replaced by corresponding enhancement spots
- switch to new request management for all loading processes
- SAP HANA generated views are Calculation Views only (so called OneView model)

To get an overview of all “simplifications” that BW/4 comes with there see so called BW4SL notes available on SAP support site. At the time of writing this blog there were 66 SAP Notes like that. Each of the Note is dealing with particular BW functionality that was changed/simplified. Change is described also with possibilities how to dealt with it - like how to migrate/convert/adjust particular object. Below few examples of the Notes: 

2444718 - BW4SL - MultiProviders
2443489 - BW4SL – InfoCubes
2479567 - BW4SL - Transformations

Central Note has number 2421930. All changes are also described in one central PDF document called Simplification List for SAP BW/4HANA. SAP offers also interactive web page that provides a description of all changes having an impact when converting from SAP BW to SAP BW/4HANA called Simplification Item Catalog (SIC).


More information:
Simplification Item Catalog (SIC) -> launchpad.support.sap.com/#/sic
2421930 - Simplification List for SAP BW/4HANA
BW-B4H-CNV – SAP support site component

Thursday, November 22, 2018

SAP HANA 2.0 express edition (HXE) administration - cheat sheet

I tried today an installation of HXE via preconfigured Virtual Machine image via VirtualBox.
I basically followed this video. Also there is a nice tutorial available with all the details.

For a reference I put here a brief reference of all the steps that are needed to make in order to setup the HXE. In case you are using preconfigured Virtual Machine there are few steps to be performed to configure HXE after importing of Open Virtual Appliance (OVA) file into hypervisor. 

I keep this mostly for me as a kind of cheat sheet :-)

1. first time logon:
user: hxeadm pwd: HXEHana1 (tmp pwd)
system prompts for the pwd change immediately

2. prompt for change of HANA DB master pwd

3. choose whether you use proxy server

4. wait till XSA config is done, this takes quite a significant time to complete, in my case approx. 40 min

5. find out IP address of the HXE server, by running command:
/sbin/ifconfig
-> e.g. 192.168.1.106

6. add the IP address to host OS into host file like:
192.168.1.106         hxehost

7. XS Engine check: open HANA console in browser: http://hxehost:8090
it shall show wheatear XS Engine is running correctly

8. URL of API endpoint enter command:
xs login -u XSA_ADMIN -p "hana master DB pwd" -s SAP
-> see API endpoint: https://hxehost:39030

9. webIDE install check, via command:
xs apps | grep webide
-> see URL: https://hxehost:53075          user: XSA_DEV        pwd: master DB pwd

10. cockpit install check, via command:
xs apps | grep cockpit-admin-web-app
-> see URL: https://hxehost:51047          user: XSA_ADMIN    pwd: master DB pwd

While you trying out all different URLs (webIDE, cockpit, etc.) make sure you open new incognito/private) session in your web browser. Else you will run into an authorization issues as there are supposed to be used different users (XSA_ADMIN, XSA_DEV) for different services.

11. check status of HANA processes, use command:
HDB info

12. stopping HXE, use command:
HDB stop

13. starting HXE again, use command:
HDB start

14. restart of HXE, use command:
HDB stop 
and
HDB start

or
HDB restart

15. switch off virtual machine, use command:
sudo shutdown now

16. see information about version of HXE, use command:
HDB version

17. see information about HXE, use command:
HDB info

16. connecting to HXE with HANA Studio (eclipse):
First install plugins aa a new software in eclipse Help menu to Eclipse from site https://tools.hana.ondemand.com/#hanatools -> e.g. https://tools.hana.ondemand.com/photon in case of Eclipse Photon version. Once plugins are present open new perspective called "SAP HANA Administrator Console". Choose "Add system" and enter info like: host name, instance number, single container, user and password. Afterwards the XSE system will appear in the Eclipse.

More information:

Wednesday, October 31, 2018

SAP TechEd 2018 Las Vegas my experience

Note: The blog is cross posted on my blog at SCN.
Although second TechEd of this season is over now I just want to come back to first one that was in Las Vegas. So here’s my experience…

It was September 17th Monday’s evening when I checked my emails and I saw an email with subject “SAP TechEd Invitation to Register”. I didn’t even care to open the email as I thought that it another marketing email inviting for the TechEd. I continued to read a news feed on my phone for another hour before I wanted to go to bed. After I was done with reading the news hour I checked my emails for last time and the email from Craig Cmehil popped up. This time I opened it and read it. It was really nice surprise to hear that I was selected for the TechEd. As Craig mentioned in the email I should have received an official invitation with details about how to claim my TechEd prize. I realized that he referred to the first email I received on that evening. So it turned out the first email wasn’t marketing one but invitation to the TechEd. I was lucky I opened the 2nd email otherwise I would completely miss my chance to go to the event :-)

So this is how I made it SAP TechEd 2018 in Las Vegas for first time. I was fortunate enough to be selected based on my participation in SAP TechEd 2018 Tutorial Mission contest held back in August. When I participated in the content I had an option to choose TechEd location. I didn’t really expect to be one of lucky winners so I thought to myself it has to be Las Vegas or nothing :-) and it worked out.

As a preparation for conference I read few blogs (e.g. How to Survive SAP Tech-Ed) about it. For someone like me attending for first time the best source of information is Tammy Powlas blog Getting Ready for #SAPTechEd – a @SAPCommunity Call

I arrived to Vegas on October’s 1st Monday evening. Thanks to my friend and SAP mentor Ethan Jewett I attended SAP Mentors Reception. Although a jet lag started to attack me very soon it was it was very pleasant occasion to meet and talk to other SAP mentors. 

On Tuesday I woke up very early and had enough time to register myself for conference. I used some time before registration was opened to familiarize myself with the conference’s venue. Sands Expo Convention Center it large facility and short walk way around it helped me later during the conference to easily navigate between different floor, rooms etc. Just one remark to registration process. Paying attendees were eligible to receive free hoodie. Although I wasn’t one of them as my ticket was provided by SAP to me for free I heard some comments regarding the hoodie. On Tuesday morning only large sizes were available and some people were not happy about that :-) I guess smaller sizes were given away on days before already as registration was opened since Sunday’s evening. 

The TechEd started with key note delivered by Bernd Leukert. Personally I expected some more technical person like Bj√∂rn Goerke to deliver it. Reason is that this is the technical conference thus the technical people like CTO would fit better. However, I understand that delivering 3 key notes by same person can be little too much. As for the key note an announcements were: a part of “Kubernetes as a Service” and “SAP Cloud Platform Functions” for me the biggest was “SAP Cloud Platform ABAP Environment” is now GA. The SAP CP ABAP Environment also known as project steampunk. Other than that emphasis of the key note was “intelligent enterprise”.

For rest of my TechEd stay I following tracks related to mostly Analytics (Next Gen Data Management (DAT),    Applied Intelligence (AIN),  App Landscapes and Cloud Native Architectures (CNA) and Integration Out-of-the-Box (INT) sessions. In total I attended 27 sessions. I did few exercised at google booth – part of App Space. Unfortunately had no time to do more tutorials in other vendor’s booths. Also not really had time to go through all exhibitor’s booths. I visited only few which I had an interests in their products. In next part of the blog I briefly introduce what I learned during sessions I attended.

As my TechEd package didn’t contain hands-ons I was only visiting few of them and I tried just shadow other people who were working on them. It was actually great to meet new people and engage.

AIN100 – Analytics Overview 101 – Dedicated to SAP’s analytics strategy. Got an overview on what’s are current tools within portfolio.  In this session I learned about SAP Analytics Cloud (SAC) tool. 

CNA222 - A Developer’s View of SAP Cloud Platform, ABAP Environment – one of sessions related to SAP CP ABAP Environment. Overview of use cases for ABAP in CP was provided. Along the others I think possibility to leverage ABAP skills in CP by SAP customers is the biggest benefit of ABAP Environment in the CP that I see. Learned things like: $TMP as development package is not present anymore in the CP; ABAP key words related to web/dynpro, OS, SAP GUI (basically everything which have no sense in cloud environment, see what is whitelisted in blog) are not supported; RESTful ABAP Programming (RAP) intro. Seen demos on: console app; abapGit usage, CDS view creation + ODATA service generation + FIORI Elements preview.

AIN200 – SAP Analytics Cloud and SAP BW/4HANA: Complementing SAP S/4HANA – Got an overview of SAP S/4HANA embedded analytics, apps (Content) available in this area; how it is integrated with SAP BW/4HANA and SAP Analytics Cloud (SAC). Speakers were nicely answering to pretty tricky questions like “do we still need BW if we have embedded analytics?”  J

DAT110 – Project Blueberry – A Sneak Peek – intro to new product Packaged DWH as a Service (DWaaS). It shares same code line as SAP BW/4HANA; to be a first app to run on the SAP CP ABAP Environment; components of SAP “DWaaS”; integration with integration to SAP Data Hub and SAC were discussed.

AIN105 – Overview of SAP Cloud Analytics (SAC), All Analytics on One Platform – Dedicated to analytics as BI/Planning/Predictive/App Design on one platform; Live connections that is used to access data in SAC tool. Very basic feature of the SAC that I learned is that it doesn’t move/store/replicate any data before it is displayed to user.

DAT367 – End-to-End Modeling and Operations with SAP BW/4HANA – hands-on session. In this one we did a creation a new data flow; creation of a Process Chain in the SAP BW/4HANA Administration Cockpit and finally we tried data tiering optimization in BW/4HANA system.

DAT100 – Analytics Clients for SAP BW/4HANA – learned about analytics strategy as big picture, front end tools like SAC, SAP Lumira (mostly about designer edition as for discovery edition won’t get new major feature updates starting in 2019) and SAP Analysis for Microsoft Office were discussed. Great demos were provided. For support of BEx tools in SAP BW/4HANA see SAP Note 2496706.

AIN864 – SAP Analysis for Microsoft Office: Road Map – Learned about upcoming new features of 2.7 version introduced for the tool like: EPM and Analytics plug-ins in MS Excel are now merged into one products; left outer join feature; comments feature; history panel; integration with SAC; etc.

CNA120 – ABAP Strategy – current innovation in ABAP were discussed, in particular:
1. On premise: SAP S/4HANA On Premise
2. Cloud:
2.1 SAP S/4HANA Cloud
2.2 SAP CP ABAP Environment
Other topics: implication on modifications/custom code (move to cloud extensions); must learn topics for ABAP developers like in area of UI: SAP Fiori / SAPUI5, RESTful ABAP Programming model (RAP); area of code pushdown: ABAP SQL, Core Data Services and code pushdown in SAP HANA; area of code securing/managing: ABAP Tools, Development-methodology; area of cloud: In-App extensibility, SAP Cloud Platform. There are many new things going on in ABAP. Really exciting times to be an ABAP developer!

DAT202 – Conversion Paths to SAP BW/4HANA – different possibilities on how to convert BW system to BW/4HANA based system. Few interesting facts about the BW/4HANA that caught my attention: 3k tables were removed, 5 mil of ABAP code lines removed in BW/4HANA in comparison to NetWeaver based BW system.

DAT204 – SAP BW/4HANA: An Agile Architecture for the Intelligent Data Warehouse – different architecture approaches discussed within BW/4HANA like: simplified EDW, flexible EDW, agile DWH and relational Data Lake architecture.

DAT366 – SAP BW/4HANA and SAP SQL Data Warehousing – hands-on session. Example of an integration of SAP and non-SAP data combined in SAP BW/4HANA and SAP SQL Data Warehousing solution. We created Flowgraph in Web IDE tool (DWH) and data flow in BW/4HANA. Data from both sources were accessible in SAP BW/4HANA.

CNA302 – Custom Code Adaptation for SAP S/4HANA – Options of checking custom code when converting to SAP S/4HANA were discussed. Different tools for that were presented like Custom Code Lifecycle Management (CCLM), ABAP Test Cockpit (ATC) etc.

CNA202 – How to Get to SAP S/4HANA Embedded Analytics – capabilities of S/4HANA’s embedded analytics were discussed. Many demos presented.

DAT370 – Experience with Using SAP Analytics Cloud for SAP BW/4HANA – hands-on session. We could practice working with SAC tool in scenarios leveraging local data and live data. It was great session as Ingo Hilgefort went beyond expectation and he provided very deep insight on topics like storytelling in analytics, gave a tips on books for BI people etc.

DAT101– What’s New in Native Development for SAP HANA – delta information between HANA 2 SPS02 and SPS03 were discussed from Client Interfaces, SQL, SQLScript, CDS, Development Tools and XSA perspectives.

INT303 – Using Hana Express with No SAP Experience – Example on how HANA Express edition can be installed and used even in productive manner.

DAT839 – SAP Data Hub: Road Map – SAP Data Hub 2.3 solution was discussed.

CNA210 – Entering the World of Git with ABAP – Great session showcasing power of ABAPGit in conjunction with Continuous Integration (CI) tool Jenkins. In spirit of “CTS goes Git” demo was presented where and ABAP change was done in development system in Eclipse. The change was pushed (exported) to git repository. CI part (pipeline): CI server observed the change in the repository. It created a new build and deployed it into test system. Afterwards the CI server tests the change in test system. In case the test is successful the change is promoted to production system.

CNA216 – A Technical Deep Dive into the ABAP RESTful Programming Model –Technical things about the RESTful ABAP Programming (RAP) model. Stared with business object (BO) and business service details. Demo on how the BO is modeled/implemented via business definition/implementation language. Followed by service definition and binding. Finally, the BO was exposed in SAP Fiori UI service with SAP Fiori Elements Preview called from Eclipse.

CNA415 – Test Driven Development with ABAP – better say it was about how to write testable ABAP code. Great session by Graham Robinson. I had a lot of fun while attending it. Graham showcased in his demo how he can rely on a fact that ABAP code was refactored correctly by leveraging ABAP Unit classes.

DAT203 – Best Practices for Modeling Mixed Scenarios – very helpful session providing an examples of possible mixed scenarios while combining modeling capabilities of BW/4HANA and HANA.

DAT108 – An Outlook on Data Integration Tools from SAP: When to Use What – different use cases of products like SAP Data Services, SAP Cloud Platform Integration for data services, SAP HANA smart data integration / SAP Cloud Platform Smart Data Integration, SAP Landscape Transformation Replication Server and SAP Data Hub were discussed.

DAT876 – SAP BW/4HANA: Road Map – features were discussed from Recent innovations -> Planned innovations (2019) -> Product direction (2020) -> Product vision (2021) point of view. See also here.

DAT815 – Machine Learning in SAP HANA – machine learning capabilities of HANA were discussed.

AIN102 – Application Design with SAP Analytics Cloud – probably best session in analytics area I had a chance to attend. David Stocker discussed a lot of detail on how SAC was designed. Also many background information on how SAP tried to integrate many of their BI front end tools. Can’t wait to try this tool out. Hope there will be trail version available soon!
In closing I’d to say that it was a great experience for me being at the TechEd. A part of gaining knowledge, opportunity to talk to SAP people like product managers, trying out new solutions, and so on the biggest asset of the TechEd is that you meet a lot of new people. It doesn’t matter either you stay few minutes longer after some session finished and discuss the topic further, or you join a bunch of strangers talking about topic you are interested in while waiting in hallway to enter room where another session gonna start soon, or you join people during lunch… basically wherever you go during the TechEd there you will find some new people who share with you a common interest in SAP solutions.

Friday, October 26, 2018

SAP RFC APIs: "Classic" RFC Library and NetWeaver RFC SDK

To enable different computer systems where one of them is SAP to communicate each other so called Remote Function Call (RFC). The RFC is the standard SAP interface for communication between SAP systems. RFC calls a function to be executed in a remote system.

Initially there was only an RFC library which is called now "classic" RFC Library (see my very old blog http://blog.maruskin.eu/2011/11/where-to-download-librfc32dll-rfc.html) is obsolete and replaced by SAP NetWeaver RFC Library.

Later the SAP NetWeaver RFC Library was introduced that is used to interface SAP systems starting from release R/3 4.0B (in case of NW RFC SDK 7.20) and from release 4.6C (in case of NW RFC SDK 7.50) and above including the newest one (NW 75).
Both the things classic and NetWeaver are doing basically same thing. Using the SDK a function in different programming languages can be written that can read/write data out/to SAP system. The newest version (NetWeaver) of course supports the latest technologist such as:  dynamic meta data retrieval, support of all SAP single code pages, new binary protocol (basXML) reduce of data volume when using complex parameter types (nested data types).

Below see overview of different versions and patch levels o of the SAP NetWeaver RFC Library SDK:

SAP NW RFC SDK 7.50 (supported till Dec 31st, 2025)
patch level              release date                                 SAP Note
02                          24.09.2018                                  2659804
01                          07.05.2018                                  2586468
00                          before 13.12.2017 init delivery      2573881

SAP NW RFC SDK 7.20 (obsolete as of Dec 31st 2018)
patch level              release date             SAP Note
43                          before 20.10.2017    513266
40                          11.08.2016              2299080
39                          20.04.2016              2247044
38                          before 17.11.2015    2229450
24                          before 14.07.2014    2035997
22                          before 02.05.2014    2003530
08                          21.05.2012              1635866
07                          28.09.2011              1609391
06                          25.07.2011              1592501
05                          before 30.05.2011    1591259
04                          before 19.05.2011    1589976
03                          19.05.2011              1562569
02                          24.02.2011              1511433
01                          before 23.09.2010    1511382
         
SAP NW RFC SDK 7.11 (obsolete)
patch level              release date            SAP Note
10                          17.11.2010             1511377
09                          23.09.2010             1474682
08                          10.5.2010               1465290
07                          04.05.2010             1445129
06                          03.02.2010             1409906
05                          29.12.2009             1407615
04                          13.10.2009             1383253
03                          before 17.8.2019     1359377
02                          before 19.05.2009   1278062
01                          in 2008                   1236530

SAP NW RFC SDK 7.10 (obsolete)
patch level              release date             SAP Note
02                          before 11.06.2008    1058327
01                          before 09.10.2007    1056472 

Supported platforms: AIX, HP-UX, LINUX REDHAT, LINUX SUSE, LINUX ORACLE, SOLARIS, WINDOWS, Z/OS, as of SAP NW RFC SDK 7.50 support of MacOS was added.

More information:
2573790 - Installation, Support and Availability of the SAP NetWeaver RFC Library 7.50
1025361 - Support and Availability of the SAP NetWeaver RFC Library 7.20