cancel
Showing results for 
Search instead for 
Did you mean: 

Capture Message ID for (IDOC-XI-HTTP)

Former Member
0 Kudos

Hi! Thanks to some kind help last week, I can capture the message ID in my mapping via the following:

*******************code**********************

java.util.Map = container.getTransformationParameters();

String mid = (String) map.get ( StreamTransformationConstants.MESSAGE_ID);

return mid;

*********************end code******************

However, my scenario is IDOC->XI Multimap->File(s). In the case that the IDOCs are mapped into multiple files, each file has a unique reference associated with it. I can see these in the HopList as follows:

<Trace level="3" type="T">clone_MMF 453D478CFCF537B0E10000009B7D1E4D</Trace>

Does anyone know how I can capture this reference in the mapping?

Help is much appreciated and rewarded. Thx, Duncan

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Message ID can be captured while going in to

IDX5 Trancation Code , where you give the Date and time when the IDOC is pushed...then you will get the squence of your data flow and in that you have a coloume header with the name MESSAGE ID...If you click that one you will have XML Message...

Amaresh

Former Member
0 Kudos

Hi Amaresh

Thanks for the reply. I need to capture the clone ID during the mapping. I don't have a problem with seeing this online via SXMB_MONI / IDX5. Thx, Duncan

bhavesh_kantilal
Active Contributor
0 Kudos

Duncan,

Am not sure how this is done, but still would like to know why you are attempting this ? Any special reason?

Regards,

Bhavesh

Former Member
0 Kudos

Hi Bhavesh, We are using the Seeburger AS2 adapter and I am developing a solution whereby we update a custom table on the SAP application when the MDN is received from the trading partner. In the case of a 1:n IDOC to XML relationship, the reference in the MDN is clone message ID and not the parent message ID. So the only way to link back the MDN with the originating IDOC is via the clone ID. Thx, Duncan