CCo (COM Connector) for SAP® NetWeaver® RFC

SAP® offers different connectors to develop ABAP® compatible components and applications. There are the Java™ connector (JCo) for Java™ environments and the dotNET® connector (NCo) for the dotNET® languages. Also SAP® offers the NetWeaver® RFC SDK to develop ABAP® compatible components and applications in C++. All libraries supports the communication with the ABAP® application server in both directions: inbound (application calls ABAP®) and outbound (ABAP® calls application). You can find the connectors here - SAP® passport necessary.

But what's up if you work neither with Java™ or dotNET® environments nor with C++?

Here is another alternative

CCo - the COM connector for SAP®

CCo is a COM library and offers wrappers around all functions in the SAP® NetWeaver® RFC library. So it is possible to use all functionalities of the SAP® NetWeaver® RFC library inside any language which is COM enabled.

With CCo it is easily possible to use the SAP® NetWeaver® RFC functions inside e.g. Visual Basic for Application® (VBA), VBScript® or AutoIt script. Here is a VBScript example, how to ping an SAP® system.

CCo enhances your possibilities to write ABAP® compatible components and applications in your favorite scripting language.

Requirements:  CCo needs 32-bit SAP® NetWeaver® RFC libraries. You find it here - SAP® passport necessary.
  Copy the SAP® RFC and the necessary libraries in your CCo directory or set the path variable of your environment to the directory where the libraries are stored.
  Register CCo.dll on your system via the registry files without admin rights.
Restrictions:  It is not native possible to use multi threading with VBA®, VBScript®, and AutoIt with SAP® NetWeaver® RFC library, also it is not possible to code server applications.
Important hints:  You can use it in production environments, the interface of CCo is stable.
  CCo includes no documentation about the functions. Look at the SAP® NetWeaver® RFC SDK documentation. You can find it here - SAP® passport necessary.

The duality of accesses via SAP® GUI Scripting and RFC with scripting languages

architecture map of scripting tracker

CCo opens a powerful second channel to communicate with an SAP® backend. You can code in your favorite COM-enabled scripting language and use two ways: on the one hand the SAP® GUI Scripting to communicate via SAP® GUI for Windows® with an SAP® system, and on the other hand the COM Connector (CCo) to communicate via SAP® NetWeaver® RFC library with an SAP® application server.

CCo is an ideal complementation to SAP® GUI Scripting in this application area. You can e.g. use the wide range of thousands of remote-enabled function modules from an SAP® system. Use the transaction code BAPI to open the BAPI explorer and find a lot in the alphabetical hierarchy tree.

Enrich your SAP® GUI Scripting operation processes. Get information easy and fast via CCo RFC interface in your scripting environment. Combine the best of both worlds.

Download of (Version 2.10 from 24.12.2017) with the size of 1'176'234 bytes and the SHA256 CRC check sum 4b6d7ab8f4488251f884741e3279e03ae468c439d41af06771c7f567df71c5e6
CCo.dll with the size of 322'560 bytes and the SHA256 CRC check sum 0ad63fba8ec6ed9e7a28fc8ae4b2c1d01d36ab2b30233b276b28592939f06ae7

The zip file contains:
CCo.dll  —  32-bit native Windows® COM library
CCo.pdf  —  Help file for COM Connector
unzip.dll  —  32-bit native Windows® library
VBScript directory  —  VBScript® examples, also BAPI examples for VBScript®
VBA directory  —  VBA examples
AutoIt directory  —  AutoIt examples, also BAPI examples for AutoIt
ABAP directory  —  ABAP® functions modules with examples in different scripting language
HTA directory  —  HTA examples with VBScript for Internet Explorer®
Register directory  —  Registry files to register and unregister CCo without admin rights

Last update 06.05.2020 / Online since 21.04.2013