SuperRFC - One BAPI to Call All BAPIs
Within an IT landscape occupied by SAP systems, there are invariably requirements for external data exchanges with these systems.
There are many different ways in to support this interaction a common method is via BAPIs, since this provides a synchronous communication handshake.
The Kagool Innovation Team are always looking for ways to do things differently with the following mindset - Simple, Fast, Performant, Scalable and Reusable.
They looked at Integration patterns across client accounts to look for improvements and created a solution referred to as the SuperRFC which is now widely deployed supporting high volume transactions.
This article explains this solution...
Traditional Method for External BAPI Calls: Single Caller
Below is a standard approach example - one calling system needs to call 4 BAPIs
That’s 4 separate developments (Designs, Builds, SITs, UATs, COs) and each return message needs to be handled. Each BAPI will have different input structures & hierarchies that the Caller will need to understand and map to and the return messages will not be standard either. Essentially each time a new BAPI needs to be called there is a lot of work to do, this is not efficient!
Method Using Kagool SuperRFC: Single Caller
The diagram below shows how the above integration pattern achieved through the SuperRFC
External calling systems have a single standarised interaction point, regardless of the number of BAPIs that need to be called. The interface for the SuperRFC is completely generic and independent of which RFC/BAPI needs to be called, all return messages are also passed back in the same standardised structure.
All the Caller needs to do is:
- Provide the name of the BAPI that needs to be called
- Provide the data to be loaded in a standard structure
- Accept the Return status messages in a standard structure
Now….Into the Real world
The above example was somewhat unrepresentative of the complex environments that we operate within. In order to illustrate how the SuperRFC technology can help, let’s add just two more Caller systems to our example to illustrate the point:
Traditional Method: Multiple Callers
As you can see, it can get complicated very quickly and when this is scaled to multiple SAP systems with hundreds of BAPIs and calling systems it’s understandable how difficult things can become extremely difficult to manage!
SuperRFC Method: Multiple Callers
The above diagram illustrates how multiple Callers are managed when using the SuperRFC as an Integration Point.
Below are the High Level Benefits of the SuperRFC
- The SuperRFC provides a single integration point to a SAP system to can any number of BAPis
- Cusom (Z) BAPIs follow the Same Integration Pattern
- Single common, generic design for calling systems to use
- Single common message return framework
- Provides commit control to caller enabling Test Mode (simulate loading data without committing)
- Improved Security to the SAP system via Fewer Integration Points
- Simple Scalable Integration Pattern
- Highly Performant Data Exchange Supporting any Number of Parallel Data Streams
- Utilises SAP Load Balancing and Basis Managed Application Resources
- Impact Assessments Easier and quicker to Perform
- Integration Testing is Simplified
- Regression Testing is Simplified
- Reduced Maintenance Costs Managing a Simpler Integration Landscape
- Simplifies the integration for your calling processes - Reduced Development Costs
- Follows the Principle of Build Once and Reuse
- Re-use Build Costs are Reduced