Bindings for the SAP NetWeaver RFC SDK

Downloads in past


202.0.13 years ago7 years agoMinified + gzip package size for @e2ebridge/sapnwrfc in KB


SAP Netweaver RFC SDK Bindings for Node.js


This module provides bindings to the SAP Netweaver RFC SDK. With it, you will be able to call remote enabled function modules of a SAP system. Opening the connection and function invocations are fully/partially asynchronous operations, which will call a callback function upon completion.


Note: In order to use this module you will have to obtain the SAP NW RFC SDK via http://service.sap.com. For further instructions see OSS note 1025361.


  • Extract the SDK archive with SAPCAR
  • Copy the files from the lib and include folders to the corresponding system directories (/usr/local/Lib /usr/local/include)

./SAPCAR_3-20002089.EXE -xf NWRFC_8-20004549.SAR
cd nwrfcsdk
cp ./lib/* /usr/lib
cp ./include/* /usr/inlude


  • Extract the SDK archive with SAPCAR
  • Copy the files from the lib folder to C:\Windows\system32
  • Warning: If you are working with NodeJS 32-bit on a Windows 64-bit OS, you should copy the files to C:\Windows\SysWOW64 instead.


OS X is not supported due to the fact that there is no suitable SAP RFC NW SDK available. The module will compile but fail when trying to lazy-load its dependencies.

Installation (both Linux and Windows)

  • You may now download the addon from the npm registry and install it by using the npm command.

npm install sapnwrfc


As with all other Node.js modules, you need to require it:
var sapnwrfc = require('sapnwrfc');

Connection parameters

Connection parameters have to be specified using a JavaScript object. For a complete list of possible parameters, refer to the SAP NetWeaver RFC SDK Guide which is available via SAP Connectors.
var conParams = {
  ashost: '',
  sysid: 'NPL',
  sysnr: '42',
  user: 'DEVELOPER',
  passwd: 'password',
  client: '001',
  lang: 'E'

Set path to sapnwrfc.ini

Before you open a connection you can set the directory path to look for the sapnwrfc.ini file.
var con = new sapnwrfc.Connection;
var iniPath = '/path/to/dir/with/inifile/in/it'


Opening the connection

Before you can invoke a remote function, you will have to open a connection to the SAP system.
Connection.Open( connectionParameters, callback( errorObject ) );

  • connectionParameters: JavaScript object containing the parameters used for connecting to a SAP system (see above)
  • callback: A function to be executed after the connection has been attempted. In case of an error, an errorObject will be passed as an argument.

versionInfo = Connection.GetVersion( );

  • versionInfo: An Array containing major number, minor number and patch level of the NW RFC SDK

var con = new sapnwrfc.Connection;

con.Open(conParams, function(err) {
  if (err) {
  console.log('sapnwrfc: ' + con.GetVersion());

Calling a remote function module

This is a two step process:
  • You will first have to lookup the function module's definition, getting a Function object in return
  • After a successful lookup, you may invoke the function and pass arguments to it

However, you can use the Function object subsequently multiple times for invocations, without having to do another lookup upfront.
functionObject = Connection.Lookup( functionModuleName )

  • functionModuleName: A string containing the name of the remote function module to be called
  • functionObject: A JavaScript object (class name: Function) which represents an interface to invoke the function

Function.Invoke( functionParameters, callback( errorObject, result ) )

  • functionParameters: JavaScript object containing the parameters used for connecting to a SAP system (see above)
  • callback: A function to be executed after the connection has been attempted. In case of an error, an errorObject will be passed as an argument. The result will be returned as a JavaScriptObject (see below for details)

For the sake of simplicity, the following example will neither pass arguments to the remote function nor receive a result:
var func = con.Lookup('RFC_PING');
func.Invoke({ }, function(err, result) {
  console.log('Got pong!');

Passing and receiving arguments

Remote function arguments are being passed by using a plain JavaScript object. For each parameter to pass in, you'll have to define a member property named according to the remote function's interface. There is no need to distinguish between importing, exporting or table parameters.


Assigning primitive types (non-structures, non-tables) is straightforward. You will, however, have to take care that the argument matches the parameter's data type. E.g. if the parameter type is an integer, you may not assign a string value to it.
var params = {
  QUESTION: 'How are you'

var func = con.Lookup('STFC_STRING');
func.Invoke(params, function(err, result) {
  if (err) {


Binary data

SAP data types like XSTRING and RAW need some special treatment as JavaScript does not support binary data very well. In order to safely pass binary data back and forth, you will have to use Node Buffers. This, of course, also holds true for binary data types used within structures and tables.
var func = con.Lookup('STFC_XSTRING');
var params = { QUESTION: new Buffer('00FF65', 'hex') };

func.Invoke(params, function (err, result) {
  console.log(result); // => <Buffer de ad>


Structures are represented by JavaScriptObjects, where each field corresponds to a member property.
var params = {
  IMPORTSTRUCT: { RFCFLOAT: 3.14159, RFCINT1: 123, RFCTIME: '094500', RFCCHAR4: 'NODE' }

var func = con.Lookup('STFC_STRUCTURE');
func.Invoke(params, function(err, result) {
  if (err) {



A table is nothing else than an array of structures. This means, in terms of JavaScript, that you need to put JavaScript objects into an array.
var table = [
  { I: 1, C: 'A', STR: 'String1' },
  { I: 2, C: 'B', STR: 'String2' },
  { I: 3, C: 'C', STR: 'String3' }

var params = {
  IMPORT_TAB: table

var func = con.Lookup('STFC_DEEP_TABLE');
func.Invoke(params, function(err, result) {
  if (err) {

  for (var i = 0; i < result.EXPORT_TAB.length; i++) {
    console.log('Row ' + (i + 1) + ':');

Retrieving function signature as JSON Schema

You can retrieve the name and types of remote function arguments with MetaData() call.
var func = con.Lookup('STFC_STRING');
var signature = func.MetaData();
console.log(JSON.stringify(signature, null, 2));

The console output is:
  "title": "Signature of SAP RFC function STFC_STRING",
  "type": "object",
  "properties": {
    "MYANSWER": {
      "type": "string",
      "length": "0",
      "sapType": "RFCTYPE_STRING",
      "description": "",
      "sapDirection": "RFC_EXPORT"
    "QUESTION": {
      "type": "string",
      "length": "0",
      "sapType": "RFCTYPE_STRING",
      "description": "",
      "sapDirection": "RFC_IMPORT"

The result of function MetaData() is an object of JSON Schema.
The properties sub-object specifies the parameter of the remote function. In the above example the remote function STFCSTRING has the parameters MYANSWER and QUESTION. The sapDirection specifies if it is an input parameter (RFCIMPORT) or output parameter (RFCEXPORT) or input and/or output (RFCCHANGING | RFCTABLES).
Attributes with the prefix sap are specific to this JSON Schema instance.
  • title: Name of the JSON Schema.
  • type: JavaScript type.
  • length: Length of a simple type or structure.
  • description: Description of parameters from SAP. Can be empty.
  • sapType: Native SAP type. RFCTYPETABLE | RFCTYPESTRUCTURE | RFCTYPESTRING | RFCTYPEINT | RFCTYPEBCD | RFCTYPEFLOAT | RFCTYPECHAR | RFCTYPEDATE | RFCTYPETIME | RFCTYPEBYTE | RFCTYPENUM | ... . You find the complete list of possible values in the SAP header file sapnwrfc.h. Look for enum type RFCTYPE.
  • sapDirection: Attribute of the first level of properties. RFC
  • sapTypeName: Name of a structure or name of a structure of a table.
  • Contributors

    • Alfred Gebert
    • Stefan Scherer
    • Michael Scherer
    • Szilard Novaki
    • Jakub Zakrzewski
    • Alex
    • LeandroDG


    0.2.0 (2015-11-11)

    • Add SetIniPath
    • RAW fields and XSTRINGs return/expect node Buffers

    0.1.8 (2015-11-02)

    • Automatic builds for Linux and Windows
    • Add tests
    • Bugfixes

    0.1.7 (2015-11-01)

    • Add gulp script for bulk compiling

    0.1.6 (2015-11-01)

    • Support for Node.js 4.x (and io.js)
    • Fix library path issue (Windows)
    • Add parameter msvsnwrfcsdkpath for node-gyp
    • Add MetaData()

    0.1.5 (2013-05-25)

    • Support for Node.js 0.10

    0.1.4 (2013-02-09)

    • Fix compilation on Linux (issue #2)

    0.1.3 (2012-08-16)

    • Support for Node.js >= 0.7.9
    • Change global invocation lock to a connection based lock


    • Unit tests
    • Missing but probably useful functions:
    - RfcIsConnectionHandleValid (aka Connection::IsOpen()) - RfcRemoveFunctionDesc (invalidate cache) - RfcGetPartnerSSOTicket
    • Use of buffers for xstring
    • Event emission on disconnect