Expanding SAP Systems with AWS - Part III

Last week we discussed configuring a Site-to-Site VPN between AWS and your on-premises data center. This week let's discuss how we configured the SAP system to interpret the AppFlow connection. We talked briefly about this process in our first blog but let us now review it in more depth.

OData Service Generation

It is important to note that we can use a new or existing data source during this process. To keep this blog post to the point we will use an existing data source. However, if you wish to create your own data source this can be done via the T-Code RSO2 and by following the necessary steps to configure a new data source.

The existing data source that we will use for this demonstration is 2LIS_11_VAHDR. The first step in this process involves navigating to the T-Code SEGW, otherwise known as the Gateway Service Builder. Select “New Project” and give the project a meaningful name and description to create your new project.

When your project has been created successfully, we can right-click on it and select redefine -> ODP Extraction.

A new pop-up will appear – requesting three pieces of information:

· RFC Destination: In this case, we can select known.

· ODP Context: Datasource/Extractors

· ODP Name: Data Source Name

Upon entering these three pieces of information the “Add ODP” button can be selected and then “Next”.

The next screen will request a description for both the Model and the Service – once entered we can select “Next”.

The final step in this wizard (step 3) involves the nodes you wish to use. In this case, we will select all the nodes present and finally select “Finish”.

Generate Runtime Objects

The next step in this process involves generating the runtime objects – this can be done by simply selecting your new project and selecting the “Generate Runtime” button. Once this button has been pressed a pop-up will appear – it is already prepopulated. Click continue.

If everything has been configured correctly all runtime objects should return with a green icon like in the screenshot below. If you drop down the “Runtime Artifacts” folder, you should also be able to see that this folder has now been populated.

Service Maintenance

Now to ensure that the OData service has been configured correctly it must be activated, we can use the T-Code /IWFND/MAINT_SERVICE to do this. Once you have navigated to this T-Code select “Add Service”. Provide the new pop-up with a System Alias and a Technical Service Name. Finally, select “Get Services” and select the service we created previously.

Lastly, the “SAP Gateway Client” can be used to test the configuration and activation. Once in the SAP Gateway Client clicking execute will run a test of the OData Service. If the configuration and activation have been successful a status HTTP 200 code will be returned. Alternative entity sets can be tested by selecting “EntitySet” located at the top of the screen.

With this approach, we can expose any data source which is ODP enabled to an external system. In our case, we decided to expose our data source to Amazon AppFlow. One of the benefits of using this approach along with Amazon AppFlow is that the delta capabilities are preserved meaning we can run incremental loads, rather than full loads each time.

We hope you have enjoyed the second blog in this series and follow along as we continue the process of helping you add value to your data housed in SAP.

If you or your colleagues have further questions or queries, please do not hesitate to contact us at william.hadnett@seaparkconsultancy.com