SAP Integration With MuleSoft
SAP Integration With MuleSoft
MuleSoft saves enterprises time and money by integrating SAP with their SaaS solutions using Mule ESB. Learn about benefits to the business and customer.
Join the DZone community and get the full member experience.Join For Free
The new Gartner Critical Capabilities report explains how APIs and microservices enable digital leaders to deliver better B2B, open banking and mobile projects.
Mule ESB - The Best Way to Integrate SAP
An alternative approach to point-to-point quick fixes and expensive SOA stacks is integrating SAP using an ESB (Enterprise Service Bus). ESBs provide a modern, lightweight, standalone solution for integrating SAP with other applications, including SaaS solutions like Salesforce, ePOS, e-Commerce, and SharePoint. Mule ESB is the only enterprise service bus to be certified by SAP for SAP integration. Mule’s SAP Enterprise Connector provides bidirectional communication and works with existing SAP technologies such as:
Intermediate Documents (IDocs)
Business Application Programming Interfaces (BAPIs)
SAP Java Connector (JCo)
Mule ESB SAP Connector
Mule ESB supports SAP integration through an SAP-certified Java connector. With the Mule Enterprise Gateway for SAP, integration between applications with SAP ECC is faster and easier. Mule SAP JCo Connector is a transport developed to provide bi-directional connectivity between SAP and other applications or tools. Using SAP JCo connector we can easily invoke BAPIs (Business Application Programming Interface) and iDocs (Intermediate Document Interface) in SAP. The SAP JCo connector is built using SAP Java Connector libraries provided by SAP. The connector leverages the SAP Java Connector (JCo) libraries, which enable Mule applications to:
Send and receive iDocs over tRFC and qRFC.
Transform all SAP objects (JCoFunction & IDocs) both to and from XML.
Execute Business Application Programming Interface (BAPI) functions using all of the following types of Remote Function Calls (RFC) like sRFC (synchronous RFC), tRFC (transactional RFC) and qRFC (queued RFC).
Act as a JCo Server to be called as a BAPI over the following protocols like sRFC, tRFC, and qRFC.
The SAP connector establishes a connection to a SAP system using JCO libraries (provided by SAP). The Connector supports the option to configure SAP connection details, connection pooling, and max limit of active connections. If the connector is used for outbound data from SAP, then ESB registers the current Mule ESB instance as JCO destination/Gateway Server.
Integration for SAP BAPI Functions
A simple BAPI performs a single operation, such as retrieving a list of product master data. The adapter supports simple BAPI calls by representing each with a single business object schema. Simple BAPIs can be used for outbound or inbound processing. You can specify synchronous RFC processing or asynchronous transactional RFC (tRFC) processing when you configure a module for a simple BAPI. In addition, for outbound processing, you can specify asynchronous queued RFC (qRFC) processing, in which BAPIs are delivered to a predefined queue on the SAP server.
In synchronous RFC processing, the SAP server and the adapter must be available during processing.
In outbound processing, the message flow sends a request, then waits for a response from the SAP server.
In inbound processing, the SAP server sends a request through the adapter to an endpoint and waits for a response from the adapter.
In asynchronous tRFC outbound processing, the adapter associates a transaction ID with the function call to the SAP server. The adapter does not wait for a response from the SAP server. If the delivery is unsuccessful, the message flow can use the SAP transaction ID (TID) to make the request again. The TID is a field in your message.
In asynchronous tRFC inbound processing, the adapter does not have to be available when the SAP server runs the function call. The function call is placed on a list of functions to be invoked, and the call is attempted until it is successful. To send function calls from a user-defined outbound queue on the SAP server, you also specify asynchronous tRFC inbound processing.
In asynchronous qRFC outbound processing, the process is similar to asynchronous tRFC outbound processing. A TID is associated with the function call, and the adapter does not wait for a response from the SAP server. In addition, the BAPIs are delivered to a predefined queue on the SAP server. By sending BAPIs to the predefined queue, you can ensure the order in which they are delivered.
Integration for SAP IDocs Documents
The IDoc adapter is part of the Integration Server. Essentially, the IDoc adapter comprises two parts, namely an adapter at the Integration Server inbound channel, and an adapter at the Integration Server outbound channel. The metadata for the IDoc types involved is shared. The adapter at the inbound channel is located before the Integration Server pipeline and calls this pipeline.
The adapter at the outbound channel, however, is called by the pipeline, and can, therefore, be regarded as part of the pipeline. As part of ESB flow definition, a SAP inbound endpoint was used to receive iDocs from SAP. A new destination (Program ID) was created in SAP, the iDocs created in SAP were also published to the new destination. There are two processes in IDOC processing one is INBOUND PROCESS (IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS (IDOC is sent to another system. Outbound data from SAP, in case of Price/VAT data from SAP, ESB receives iDocs as JCO iDocDocumentList elements. Each iDocDocument contains iDoc metadata and Segments which internally had the Segment data (Price or VAT information).
ESB can receive multiple iDocs at any time: inbound data to SAP, in case of Sales/Return Order from other application to SAP, Mule ESB converted payload to iDoc XML format using XML-to-iDoc transformer, and posted the request to SAP.
Support for Clustering, HA, Reliability, and Throttling
Mule ESB Enterprise can be clustered to support High Availability. The SAP adaptors are cluster-aware. The TID handler should be configured to use the database in case of Clustered ESB nodes to ensure that ESB does not process the same transaction twice. Reliability and Throttling were enabled by using Active MQ message broker using Mule ESB which provided an out of the box connector. Throttling was controlled through configurations such that Mule ESB processes load to a downstream system like POS, based on a response acknowledgment.
Batch Process and Tuning
It is possible for Mule ESB to handle a higher volume of data from SAP to support batch process. ESB received data from SAP and output to destination interfaces were throttled using Active MQ. ESB also provides options to tune the number of threads for processing.
Benefits to the Customer
When SAP is properly integrated with other applications, companies are able to streamline and fully automate their business processes. Companies further benefit from SAP integration in the following ways:
Increased Business Alignment: the ability to create an integrated agile software infrastructure for changing business needs.
Better Business Efficiency: the ability to streamline, automate, and enable a better tracking and visibility to business processes.
Improved Business Visibility: the ability to integrate systems and to aggregate data for a consistent and accurate view of business as a whole.
Significant cost savings by using low-cost Mule ESB Enterprise.
Support for functional and non-functional requirements.
Ability to generate reports in SAP based on regions and evaluate the sale across the world.
Improved customer interactions by automating direct communications.
Elimination of the need for dual data entry, saving time and money.
Fewer data redundancies and errors caused by manual data entry.
Enhanced agility to act on new information quickly.
SAP Integration Challenges
Although integration has been around for well over a decade, the specific challenge of integrating SAP with other system emerged much more recently. Moreover, traditional approaches to integration have been costly and complex. Direct, point-to-point integration, for instance, has been utilized in some cases as a quick, ad hoc solution to SAP integration challenges. However, such an approach creates tight dependencies between the two systems, resulting in a brittle environment and a progressively more complex architecture as new integration are added over time.
Opinions expressed by DZone contributors are their own.