Simple SAP related flow in MuleSoft application – IDOC based

Similarly as in my previous post I’m sharing a little about my experience while working with MuleSoft Mule ESB platform.

In next text I depict simple flow in the mule which listens for incoming data coming into the mule’s app from an IDoc generated in SAP. Once the IDoc of certain type is created in the SAP it is displayed in the app’s console. Needless to say that the IDoc gets generated in the SAP when some business data gets modified (created/changed/deleted). There is quite extensive configuration to be done at SAP side with regards to ALE customizing in order to setup the IDoc generation. On the mule side there is just an SAP Connector configured which acts as the IDoc listener. The IDoc Basic Type needs to be specified in its Object Name field. All parameters for connection form the mule app to the SAP are taken via parameters form mule-app.properties file.

Here’s the mule app’s console output looks like:

Related post:

Simple SAP related flow in MuleSoft application – BAPI based 

Mapping between IDoc segment’s fields and SAP application fields

This blog is intended for ABAP developers (me including) dealing with interfaces. In particular the interfaces developed in SAP ALE – means IDoc technology.

From time to time I need to quickly check what is field mapped to field in IDoc’s segment. To do that it is very common to use TA WE60 – Documentation for IDoc basis types. Basically inhere I need to know what IDoc basic type I’m interested in and I can quickly get overview of all the fields within segment of that IDoc basic types are used.  So this gives me a list of all the fields within particular segment (or all segments in particular basic type of IDoc).

However sometimes it is a case other way round. I would like to know what segments are out there where particular SAP application field is used in. For this I can use table EDSAPPL.