2.4 SAP IDOC Extraction

Lab 4: Application-level extraction

Application-level extraction

In this lab we will configure this SAP IDoc integration with Amazon S3 by using Amazon API Gateway.

➡️ In SAP ERP applications, business logic largely resides in the ABAP layer. Even with the code push-down capabilities of SAP HANA database, the ABAP stack still provides an entry point for API access to business context.

➡️ SAP applications also support HTTP access to function modules, and you can use AWS Glue or Lambda to access these function modules using HTTP.

➡️ SAP has also published PyRFC library that can be used in AWS Glue or Lambda to natively integrate using RFC SDK. SAP IDOCs can be integrated with S3 using an HTTP push pattern.

The key considerations for application-level extraction include the following:

  • Extractions can happen with business context in place as the extractions happen at the application level. For example, to pull all sales order data for a particular territory, you could do so with all related data and their associations mapped through function modules. This reduces additional business logic–mapping effort outside SAP.

  • Change data capture is not supported by default. Not all SAP function modules or frameworks support change data capture capabilities.

  • Using AWS native services like AWS Glue or Lambda removes the requirement for a third-party application, hence reducing the total cost of ownership. However, customers might see an increase in custom development effort to wire the HTTP or RFC integrations with SAP applications.

  • Potential performance limitations exist in this pattern as compared to database-level extraction because of application-level integration.

  • Also, additional performance load in the SAP application servers is caused due to pulling data using function modules and other frameworks.

Below is a list of the steps for this lab: