Overview

TIBCO ActiveMatrix BusinessWorks™ Plug-in for SAP Solutions provides the interoperability between TIBCO ActiveMatrix BusinessWorks™ and the SAP system. The plug-in was formerly known as TIBCO ActiveMatrix® Adapter for SAP. With the plug-in, you can manage and transfer IDocs, manage and perform the RFC/BAPI invocation and read data from SAP tables (excluding clustered and pooled tables) and views.

TIBCO ActiveMatrix BusinessWorks is a leading integration platform which can integrate a wide variety of technologies and systems within enterprise and on cloud. TIBCO ActiveMatrix BusinessWorks includes an Eclipse-based graphical user interface (GUI) provided by TIBCO Business Studio™ for design, testing, and pushing the application to cloud. If you are not familiar with TIBCO ActiveMatrix BusinessWorks, see the TIBCO ActiveMatrix BusinessWorks documentation for more details.

This product has certified integration with SAP NetWeaver^® and SAP^®S/4HANA, on-premises edition.

ActiveMatrix BusinessWorks™ Plug-in for SAP Solutions extends TIBCO ActiveMatrix BusinessWorks, and adds an SAP Connection shared resource, an SAP TIDManager shared resource, and an SAP palette to TIBCO Business Studio:

• SAP Connection

  Use the SAP Connection shared resource to establish bidirectional connections with the SAP system and download schemas at design time. The Message Source Configuration connection is added where the Kafka or JMS Server Configurations are maintained.

• SAP TIDManager

  Use the SAP TIDManager shared resource to manage the check of duplicate IDoc messages published from the SAP system.

• SAP Palette
  • Dynamic Connection

    Use the Dynamic Connection activity to establish a dynamic connection for invoking RFC/BAPIs.

  • IDoc Acknowledgment

    Use the IDoc Acknowledgment activity to update the IDoc status in the SAP system.

  • IDoc Confirmation

    Use the IDoc Confirmation activity to confirm the status of the IDocs posted to the SAP system.

    Note: The IDoc Confirmation activity requires TIBCO Enterprise Message Service. For confirming IDocs without using TIBCO Enterprise Messaging Service, see IDoc Processing Without Messaging

  • IDoc Converter

    Use the IDoc Converter activity to convert a raw IDoc into XML output. For more information on this activity, see IDoc Processing Without Messaging

  • IDoc Listener

    Use the IDoc Listener activity to receive the IDocs published from the SAP system.

    Note: The IDoc Listener activity can be configured to use either the TIBCO Enterprise Messaging Service or Apache Kafka. This activity can also be configured without using messaging. For more information on using the IDoc Listener activity without messaging, see IDoc Processing Without Messaging
  • IDoc Parser

    Use the IDoc Parser activity to retrieve the IDocs processed by the IDoc Listener activity, and then parse the IDocs as the activity output.

    Note: The IDoc Parser activity requires the TIBCO Enterprise Messaging Service.
  • IDoc Reader

    Use the IDoc Reader activity to post the IDocs to the SAP system.

    Note: The IDoc Reader activity requires the TIBCO Enterprise Messaging Service.

  • Post IDoc to SAP

    Use the Post IDoc to SAP activity to post the IDocs to the SAP system without the need to use the messaging service like TIBCO Enterprise Messaging Service.

  • IDoc Renderer

    Use the IDoc Renderer activity to receive the IDoc in XML format and provide output in raw IDoc format.

  • RFC BAPI Listener

    Use the RFC BAPI Listener activity to listen to the SAP system and receive RFC/BAPI requests from the SAP system.

  • Invoke RFC BAPI in SAP

    Use the Invoke RFC BAPI in SAP activity to invoke RFC/BAPIs in the SAP system.

  • Reply from RFC BAPI in SAP

    Use the Reply from RFC BAPI in SAP activity to receive the return message from the SAP system when the invocation of the RFC/BAPI is completed.

  • Read Table

    Use the Read Table activity to read data from SAP tables (excluding clustered and pooled tables) and views.

The plug-in supports the following SAP integration interfaces:

• Business Application Programming Interface (BAPI)

  BAPIs are the methods exposed by SAP business objects. This interface is best used with the plug-in for performing real-time queries and updates to and from the SAP system. BAPIs are the SAP recommended integration interfaces over Remote Function Calls (RFCs).

• RFC

  By using the RFC interface, non-SAP and SAP applications can execute SAP Advanced Business Application Programming (Advanced Business Application Programming) functions, which have been RFC-enabled. They are similar to BAPIs in functionality, but are not attached to SAP business objects.

• Application Link Enabling/Intermediate Documents (ALE/IDoc)

  IDocs are document containers for business transactional data, such as sales orders (for example: ORDERS01) and order invoices (for example: INVOIC02). ALE helps achieve cross-business functionality and facilitates the event driven, asynchronous exchange of information directly out of business transactions.