Product Documentation > Installation

Release: 9.32204 / Last update: September 7, 2022

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

Pre-requisites for SAP NetWeaver® systems

For installation of the ASAPIO Integration Add-on and its components, please make sure your system meets the following minimum requirements:

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

Please no: No activation of an SAP Business Function is needed.

Download and import

Please make sure you have the ASAPIO Shipment Info email at hand before proceeding.

Overview

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 download the packages from the link you received via e-mail from ASAPIO (requires an active subscription contract).

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)
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)

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

Roles and Authorizations

Note

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/SCI_CP_RESET, /ASADEV/SCI_TPW, BD52, BD61, RBDCPCLR, SE38, SPRO, WE81, SOAMANAGER
/ASADEV/AR /ASADEV/CO/ = *

/ASADEV/OB/ = *

/ASADEV/CU All possibilities
/ASADEV/IN /ASADEV/CO/ = *

/ASADEV/IN/ = *

/ASADEV/ML /ASADEV/CO/ = *

/ASADEV/ML/ = *

/ASADEV/RC /ASADEV/RF = *
S_GUI ACTVT = Export
S_TABU_DIS ACTVT = Change, Display

DICBERCLS = ALE0, EDI0

S_TABU_NAM ACTVT = Change, Display

TABLE = /ASADEV/*

S_DEVELOP ACTVT = Display, Execute

DEVCLASS = SALE

OBJNAME = RBDCPCLR

OBJTYPE = PROG

S_APPL_LOG ACTVT = Display

ALG_OBJECT = /ASADEV/AMR_LOG

ALG_SUBOBJ = *

S_IDOCDEFT ACTVT = Display

EDI_TCD = WE30

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

SRT_NAME = /ASADEV/*

S_IDOCMONI ACTVT = Change, Display

EDI_DIR = Outbound, Inbound

EDI_MES = *

EDI_PRN = *

EDI_PRT = *

EDI_TCD = *

Authorizations of Batch job role (/ASADEV/ACI_JOB_ROLE)

Authorization Object Settings
S_TCODE TCD = /ASADEV/ACI
/ASADEV/AR /ASADEV/CO/ = *

/ASADEV/OB/ = *

/ASADEV/IN /ASADEV/CO/ = *

/ASADEV/IN/ = *

/ASADEV/ML /ASADEV/CO/ = *

/ASADEV/ML/ = *

/ASADEV/RC /ASADEV/RF = *

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 Cloud Integrator Customizing (Values: Instance, Object)
/ASADEV/CU General access to the ASAPIO Cloud Integrator Customizing
/ASADEV/IN Used to restrict the execution of inbound objects as defined in the ASAPIO Cloud Integrator Customizing (Values: Instance, Object)
/ASADEV/ML Used to restrict the execution of multiline outbound objects as defined in the ASAPIO Cloud Integrator Customizing (Values: Instance, Object) – Not required for event-messaging use cases (e.g. for the Azure Connector)
/ASADEV/RC General execution of ASAPIO Cloud Integrator functionality (Field: /ASADEV/RF, Values: DATA_PROC, FRAMEWORK)

Data Processing is checked in all extraction FM and Framework in all other places of execution

Uninstallation

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.

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.

  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