Docs / Reference

Frequently Asked Questions

Is ASAPIO designed for mass data or event-driven scenarios?

ASAPIO Integration Add-on is purpose-built for event-driven integration. It publishes data to messaging platforms in real time, triggered by SAP business events such as a sales order change or a goods receipt posting.

While it is possible to trigger events for large data volumes (for example, using a report to mass-trigger BUS2105 events on existing purchase requisitions), ASAPIO is not a batch ETL tool. For initial loads or mass data replication, consider complementary tools such as SAP DataSphere or the relevant SAP standard extraction mechanisms, and use ASAPIO for the ongoing change-data stream.

Which events can trigger an outbound message?

ASAPIO supports multiple trigger types. See the Outbound Overview for the full list:

Can I use ASAPIO alongside SAP Integration Suite (CPI)?

Yes. ASAPIO publishes raw or formatted event data to a message broker (Azure Service Bus, Confluent, Solace, etc.). SAP Integration Suite (CPI) can consume from the same broker for further processing. ASAPIO and CPI serve different layers: ASAPIO handles the extraction and first-mile delivery from SAP, while CPI handles protocol mediation and complex routing.

What ABAP releases does ASAPIO support?

ASAPIO supports SAP ECC 6.0 EhP 6, SAP S/4HANA and all other NetWeaver-based systems. For detailed technical prerequisites (SAP_BASIS, SAP_ABA and Service Pack levels), please see the Minimum Requirements section in the installation guide.

Does ASAPIO support SAP S/4HANA Cloud (public edition)?

No. ASAPIO Integration Add-on installs as an ABAP Add-on and requires access to a customer-managed SAP system (on-premise, private cloud, or RISE). It is not compatible with the public edition of SAP S/4HANA Cloud.

How do I get support?

Raise a ticket via the ASAPIO Support Portal. Include your ASAPIO release version, the affected system, and reproduction steps or error logs.