Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

Supported SAP systems / Where can I install ASAPIO Integration Add-on?

ASAPIO Integration Add-on currently supports

  • SAP ECC (“ERP”) 6.0 Enhancement Package 6 and newer
  • SAP S/4HANA 1610
  • SAP S/4HANA 1709
  • SAP S/4HANA 1809
  • SAP S/4HANA 1909
  • SAP S/4HANA 2020
  • SAP S/4HANA 2021
  • SAP S/4HANA 2022
  • SAP S/4HANA 2023
  • Other SAP NetWeaver-based systems (e.g. SAP HCM, SAP SRM, SAP MDG)

All systems need to meet the following minimum requirements:

SAP Component Name Release Service Pack Package
SAP_BASIS 731 0003 SAPKB73103
SAP_ABA 731 0003 SAPKA73103

Please note: No activation of an SAP Business Function is needed for the Framework package. However, certain Connectors like for SAP Fieldglass may require specific SAP Business Functions – please refer to the Connector documentation.

Download and import

Please make sure you have the ASAPIO installation files at hand before proceeding.


The following Add-ons are required to be installed on the supported SAP NetWeaver® systems:

Add-on/component name Type
ASAPIO Integration Add-on – Framework Base component (required)
ASAPIO Integration Add-on – Connector (e.g. for Microsoft® Azure®, Confluent®, Solace®  PubSub+® etc.) Additional package

Download location

Please follow the instructions on the Download page.

Upgrading from SAP NetWeaver Event-enablement Add-on?

In case your are upgrading from SAP NetWeaver Event-enablement Add-on to any other ASAPIO direct license or Solace Edition, please make sure to download and install the package  “ASAPIO ACI – Unlock Usage License”. Please see section “Import sequence” below.

Installation using transport files

Import sequence

Required? Import Sequence Download file
Required 1 ASAPIO ACI <Product/Version> Framework
Required 2 ASAPIO ACI <Product/Version> Event Content (= base package for Connectors)
since 9.32210 this is combined in one file with the Framework transport
Required 3 ASAPIO ACI <Product/Version> <Connector_Name>
Optional 4 ASAPIO ACI – Unlock Usage License

(only necessary for certain cases, e.g. license upgrades, and if provided by ASAPIO – see section “Upgrading…” above)

Import process

Install the packages by importing the transport request packages with SAP Change and Transport Management, make sure to keep the import sequence as specified. Install Add-on packages on SAP NetWeaver® system.

Please refer to the SAP standard system documentation on how to perform the following steps

Unzip the SAP Transport Request archive, you will receive 2 files

  1. Upload the tranport request packages from your local file system to the SAP server, e.g. as explained, using Transaction /nCG3Z
  2. Place the SAP Transport Request files to the following directories
  3. File starting with “R” must be placed in server folder: “/usr/sap/trans/data/”
  4. File starting with “K” must be placed in server folder: “/usr/sap/trans/cofiles/”
  5. Then use transaction SE09 and STMS to add the transport to the import queue and import the request.

Further info on CG3Z can be found at https://answers.sap.com/questions/440345/using-transactions-cg3z-and-cg3y.html

Installation using PAT (ABAP Add-on) files

  1. Use transaction /nSAINT
  2. Please refer to the latest SAP documentation on SAINT at https://help.sap.com/doc/f07cbfc30ae245a4bddea17dc2b176a3/LATEST/de-DE/SAINT_DE.pdf

Please note: if you were provided with a .PAT file from ASAPIO, you can only upload the package through the application server. SAINT front-end does not support .PAT files.


Roles and Authorizations


The following information is applicable for all scenarios and use cases of the ASAPIO Integration Add-On-

Administrator role: For administrator users, role /ASADEV/ACI_ADMIN_ROLE, This role has all necessary authorization objects for configuration and support of the Integration Add-On. This role (or the containing authorization objects) have to be assigned to users who should configure, test, execute and monitor the solution.

Batch job role: For technical / system users, e.g. to run batch jobs, role /ASADEV/ACI_JOB_ROLE is provided. This role includes all necessary authorization objects to run the ASAPIO Integration Add-On.

Authorizations of Administrator role (/ASADEV/ACI_ADMIN_ROLE)

Authorization Object Settings
S_TCODE TCD = /ASADEV/68000202, /ASADEV/68000203, /ASADEV/68000204, /ASADEV/68000205, /ASADEV/68000206, /ASADEV/68000207, /ASADEV/68000212, /ASADEV/68000216, /ASADEV/68000217, /ASADEV/68000218, /ASADEV/ACI_MONITOR, /ASADEV/ACI, /ASADEV/DESIGN, /ASADEV/SCI_CP_RESET, /ASADEV/SCI_TPW, BD52, BD61, RBDCPCLR, SE38, SPRO, WE81, SOAMANAGER


/ASADEV/CU All possibilities




/ASADEV/PL ACTVT = Create, Change, Display, Delete
S_GUI ACTVT = Export
S_TABU_DIS ACTVT = Change, Display


S_TABU_NAM ACTVT = Change, Display


S_DEVELOP ACTVT = Display, Execute









S_SRT_CF_C ACTVT = Create or generate, Change, Display, Delete, Activate, generate


S_IDOCMONI ACTVT = Change, Display

EDI_DIR = Outbound, Inbound





Authorizations of Batch job role (/ASADEV/ACI_JOB_ROLE)

Authorization Object Settings







Authorization Objects

Following table shows the available authorization objects and the corresponding description:

Authorization Object Description
/ASADEV/AR Used to restrict the execution of outbound objects as defined in the ASAPIO Integration Add-on Customizing (Values: Instance, Object)
/ASADEV/CU General access to the ASAPIO Integration Add-on Customizing
/ASADEV/IN Used to restrict the execution of inbound objects as defined in the ASAPIO Integration Add-on Customizing (Values: Instance, Object)
/ASADEV/ML Used to restrict the execution of multiline outbound objects as defined in the ASAPIO Integration Add-on Customizing (Values: Instance, Object) – Not required for event-messaging use cases!
/ASADEV/RC General execution of ASAPIO Integration Add-on functionality (Field: /ASADEV/RF, Values: DATA_PROC, FRAMEWORK)
Data Processing is checked in all extraction FM and Framework in all other places of execution
/ASADEV/PD Authorization to use the ASAPIO Payload Designer (transaction /ASADEV/DESIGN).
/ASADEV/PW General authorization to read a secret for the ASAPIO Integration Add-on from the Secure Store.



Please make sure to save/backup your configuration settings at first, click here for instructions.

  1. If you have installed ASAPIO Integration Add-on / components using the import of transport requests:
    Uninstalled from the SAP system can be performed by manual deletion of the imported packages, as described below.
  2. If you have installed ASAPIO Integration Add-on / components using PAT or SAR files: Unstallation from the SAP system can be performed using the approach described here.


Backup of configuration settings

Please follow this guide in order to record all custom configuration settings within the ASAPIO namespace in transport requests, which can be exported or archived for future restore.

Stop ASAPIO Add-on and unschedule jobs

Preparation: Make sure you un-scheduled any jobs (/nSM36) that would call an /ASADEV/* program and remove any custom coding that would call /ASADEV/* programs or function modules.

Deletion of development objects

  1. Go to SE80 and list all packages in namespace /ASADEV/
  2. Select all objects (using Ctrl + select) to mark all objects of a package, right-click and choose “Delete”
  3. After that, please delete the package itself.
  4. Repeat above for all /ASADEV/* packages

Hint: If deletion of the package in step 3 fails with error message “Package still contains subobjects”, please release the transport first that contains the deleted objects. Then proceed with step 4 please

To double-check if you have removed all objects, please check table TADIR in transaction /nSE16, filtering for DEVCLASS = ‘/ASADEV/*’.

This process might vary based on your transport management settings, but the general approach is to delete the objects and then all Asapio packages (namespace /ASADEV/).

Scroll to Top