IDoc Has Left The Building
SAP IDocs are a tried and true interface methodology. But as with any interfacing technology the most brittle component is the connection between the two systems (in the case, SAP and the subsystem). In scenarios where SAP is sending IDocs to a subsystem via the transactional RFC, one question is paramount:
How do you know when an Outbound IDoc has physically left SAP?
It’s a simple fact that if your subsystem never receives an IDoc from SAP, the subsystem will not be able to route or process the IDoc. I have always gone by the notion that once the subsystem has successfully received the IDoc, the subsystem now has all the responsibility to process and route the IDoc, but before that time, SAP has the responsibility to ensure that the IDoc is fully dispatched. The subsystem should have processes in place to determine if the IDoc has been received at the target system successfully or not. In this blog I will focus on the handshake between SAP and the subsystem. This will entail Outbound IDoc status and a couple of batch jobs that should be setup to ensure a better chance of a successful handoff between SAP and the subsystem.
SAP Event Driven Batch Job
When creating SAP batch jobs to run a program, most of the scheduling can be accomplished by setting a periodic time for when the job is executed. For example, execute the job every 10min, 30min, or 1 hour. But what if you needed more control of when a batch job was executed?
Turn any SAP remote-enabled function module into a Web Service – Part 2
In my previous blog I showed the steps into turning a simple function module into an Enterprise Service. Now that we have the service defined in ECC, our next step is to configure it so an external application can call our newly created service.
I will show how to configure and test the Web Service on ECC with Service pack 14 and higher. Before Service Pack 14, the configuration is completed in ECC, however after SP14 the configuration is completed on the Java Stack.
Turn any SAP remote-enabled function module into a Web Service – Part 1
It still amazes me that not a lot of developers know that you can turn any existing SAP remote enable function module into a Web Service. It may sound like a challenging task, but it is just one of those things that you either know how to do it or you don’t. And to know how to do it only takes 15min to understand.
I have broken this down into 2 blogs Part 1 will show how to create the simple structured web service Part 2 will show how to configure and test the web service using SOAMANAGER and WSNAV
