So, this is yet another blog post about executing BAPI functions in SAP using the Adapter Framework; one day I will get bored with writing about SAP, but right now, it’s on the top of the heap. Today’s post is around error handling and reporting; any monkey can make something work, but handling error conditions gracefully is often a stumbling block that can trip you up during integration.

I re-watched groundhog day quite recently; it is still a work of genius but it got me to thinking about the subtext of the film and how it relates to software development.

Last time I wrote about how easy it was to execute an arbitrary BAPI using the adapter framework and get meaningful results back as XML. At the simplest level, that’s pretty much all you really need to integrate with SAP. Unless…

SAP R/3 is used in a lot of enterprises and so having to integrate with SAP R/3 is something that we familiar with. The adapter has a broad range of support for SAP R/3; we can send and receive IDocs if you are trading documents electronically, or we can invoke arbitrary RFCs/BAPI functions within SAP R/3 if IDocs aren’t your thing.

Hyper-V 2012 has been out for a while now; I finally took the plunge and upgraded my lab infrastructure at home¹. Given that all my test containers are virtualised in Hyper-V 2008 already; it should just be a case of moving the images around to free up a host machine so that the hosts can be upgraded in sequence. Ultimately it was painless, but time consuming; a large part of it was copying gigabytes of data around my network.