Skip to Content

Receiving ALEAUD as acknowledgment in ccBPM


In SAP PI world, getting acknowledgement and processing on the basis of that acknowledgement is a very common scenario. During different use cases, I was required to get response from R/3 system and process it further on the basis of acknowledgement received. The way I found initially, to get the acknowledgement from R/3 system, was to use event and call proxy from the IDOC receiving system.


Blog by Rene Klumberg, Code free dispatch confirmation from ERP to MDM using PI, helps to move ahead it that direction.

Code free dispatch confirmation from ERP to MDM using PI

But what if we don’t have the required event as in case with Vendor Business object where we don’t have event for Vendor create/change. Then we can schedule report RBDSTATE with variants configured that help to generate acknowledgments ALEAUD for inbound Vendor Create IDOCs. In general, this acknowledgement message, ALEAUD, appears as below image in SXMB_MONI.

To get a separate message entry in SXMB_MONI for ALEAUD, make the configuration mentioned in this link.

So after configuration done based on above link, a separate message appears in the SXMB_MONI.

Now after this configuration with a defined scenario in Integration Directory, these messages can be collected and dumped into any file server for further usage. With the scenario discussed above, we don’t have a clear picture of a particular acknowledgment is for which IDOC number till we have a manual check on that.  Now if you have defined a correlation on the basis of field element in messages then we can use these ALEAUDIT for further processing in ccBPM, but again if we don’t have any field which can be used for defining correlation then what to do? Can we use IDOC number? but that is generated in adapter, so we don’t have IDOC number readily available to compare with ALEAUDIT message received.

So lets start, in this blog I will talk about the scenario, Vendor master create, where after sending an IDOC from SAP PI to a SAP ERP system I want to get an ALEAUD message back and process further based on that message. We need a ccBPM process that will send the IDOC message and then will pick the correct ALEAUD based on the correlation.

But again the question remains the same, what will be the condition in our correlation? I would say IDOC number. Yes, we will have our correlation based on IDOC number. We will have an ABAP mapping program to retrieve IDOC number generated in XI system and then on the basis of the retrieved IDOC number and E1STATE-DOCNUM field of ALEAUDIT message, our correlation will work and get correct acknowledgement and process further.

Let us first start with the scenario we are going to discuss.

I won’t go through the development of all the design objects. I will just provide a reference to the objects that are required and a note for the special interface objects and mapping objects to be created for this scenario.




Used By

Data Type

Vendor, Address

Sender Interface

Message Type


Sender Interface

Message Interface


Sender Interface










Imported Objects








ccBPM, Receiver Interface

Message Mapping/ Interface mapping

Between Vendor and CREMAS

Between source and ccBPM


An ABAP mapping between CREMAS and RFC: ZALEAUDIT4XI

ccBPM, to retrieve IDOC number

Here is the mapping program; I have highlighted the section in this mapping program that is responsible to get IDOC number based on PI system tables SWFRXIHDR and IDXRCVPOR and then push it into the RFC request message ZALEAUDIT4XI.

ABAP Mapping to retrive IDOC Number. 

Talking about integration process, it will look like this:

Correlation in this integration process is defined based on:

1) IDOC number (generated in XI system and is retrieved in a RFC request message ZALEAUDIT4XI through ABAP mapping) and

2) Field E1STATE-DOCNUM of response ALEAUD (to be received from target SAP ERP by ccBPM).

Step 4 in the ccBPM, which is an RFC call, will trigger an ALEAUD message for the inbound IDOC Vendor Create message. Here the RFC that will trigger the acknowledgement:



I assume that all the required ALE setting are already done in the target system to receive the CREMAS IDOC and send ALEAUD message as a response back to XI system.

Based on the above correlation correct ALEAUD message will be picked and further processing can be done. There are different fields in ALEAUD which can be helpful like field ALEAUD01.IDOC.E1ADHDR.E1STATE.STAPA1 contains the Document number created in the target system, field ALEAUD01.IDOC.E1ADHDR.E1STATE.STATYP contains the status of the IDOC message which can be used for error processing.

The scenario I have taken gives just a idea on how correct ALEAUD message can be gather in SAP PI. One can add more steps as per requirement too process further on the basis of ALEAUD. 

You must be Logged on to comment or reply to a post.
  • Excellent blog. Had been on my to-blog list of almost a year now, but I am glad you did it. Infact I had this thread open for 3 months, before I solved it the difficult way.

    Idoc Acknowledgements and BPM.

    Just a quick note ~ It is not a absolute must to use a ABAP mapping; you can juse standard RFC lookup and do this using Graphical Mapping. Adding this note; might avoid confusion to beginners.

    Otherwise, great job.


  • I m trying to Map the CREMAS and RFC ZALEAUDIT4XI using your ABAP Code . When i execute it I m getting the below payload in runtime where the Message id is not getting populated i beleive . Can you please help me to understand where i m missing.

  • Hello Mitesh,

    I am trying to implement your BPM scenario wherein i intend to receive acknowledgements for MATMAS Idocs posted in ECC.

    I have a concern on the ABAP mapping step used in this case. ABAp mapping program neeeds PI msg id as input. Does the mapping program itself read the msg id generated in PI or do we have to handle it somewhere in BPM? Same is the concern for the output generated from the ABAp mapping.

    Kindly advice.