TechEd16 Example by grahamrobbo

Welcome.

Thanks for your interest in my presentation "Building NetWeaver Gateway Services". You can grab the ABAP code here and install it on your own system to look at it more closely and see it in action.

* Update 5 - September 2017 *

This content was updated for a presentation at the SAUG Summit in Sydney.

The latest samples and slides have been moved to the building_gateway_services project.

This project will no longer be maintained.

* Update 4 - June 2017 *

There have been reports of poor performance on some systems in the CALL_ALL_GETTERS method where it uses RTTS (run-time type services) to walk through the entity to determine the ABAP field names.

Now if you pass the model and the entity name to the ZIF_GW_METHODS~MAP_TO_ENTITY method it will use the model to determine the ABAP field names which should be faster. Don't know why I didn't do it this way in the first place.

This change makes slide 53 in the slide deck out of date. Refer to the Pull Request #6 and the code itself to see what has been changed.

* Update 3 - April 2017 *

I have been asked to re-deliver this session on a upcoming ASUG Webcast and also at the SAUG Brisbane Conference in May 2017.

Therefore I have done some minor code refactoring - but most importantly I have updated the slides so that they now match the sample code.

* Update 2 - February 2017 *

SAP have deprecated a significant part of the standard NetWeaver Gateway interface parameters.

This is nicely described in this blog by Nabi Zamani.

I have refactored this demo code to remove all references to the deprecated interface parameters.

The downside is that the code snippets in the slides no longer match the code examples. But the concepts and programming patterns described here remain the same.

The new code has much simplier interfaces. What used to look like this...

... now looks like this ...

* Update 1 - October 2016 *

At @gregorwolf's suggestion I have changed my demo code to use the NetWeaver Enterprise Procurement Model (EPM) tables rather than ERP tables. This means you can now install the code on non-ERP ABAP systems.

The downside is that the slides no longer 100% match the code examples. If you prefer to use the original version you can find it here.

To install the code onto your ABAP system you will need to use the abapGit project by @larshp.

If you haven't seen abapGit before I highly recommend you take a good look at it. If you find it useful perhaps you could consider joining the project and making your own contributions?

abapGit will transfer the ABAP code from my GitHub repository to a package on your ABAP system. I recommend using a local package just for this purpose called something like $GWDEMO.