cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

IDoc->File scenario: can you explain thses acknowledgments?

Former Member

on ‎06-10-2008 3:42 PM

0 Kudos

Hi,

I have an idoc->file scenario. in sxmb_moni I can see a green "OK" mark for my message in acknowldgment status column. when I dblclick the message, I can see my original message and 2 acknowldgment messages under this one in the top left.

1 acknowledgement is the OK one, the 2nd one is of type AckNotSupported.

When I dlbclick the OK one ack and click the idocoutbound, I can see:

<SAP:TABNAM>EDI_DC40</SAP:TABNAM>

<SAP:MANDT>450</SAP:MANDT>

<SAP:DOCREL>700</SAP:DOCREL>

<SAP:DOCNUM>0000000000257842</SAP:DOCNUM>

<SAP:DIRECT>2</SAP:DIRECT>

<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>

<SAP:CIMTYP />

<SAP:MESTYP>ALEAUD</SAP:MESTYP>

and when I dblclick the 2nd ack and IdocOutbound, I see:

<SAP:MANDT>450</SAP:MANDT>

<SAP:DOCREL>700</SAP:DOCREL>

<SAP:DOCNUM>0000000000257862</SAP:DOCNUM>

<SAP:DIRECT>2</SAP:DIRECT>

<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>

<SAP:CIMTYP />

<SAP:MESTYP>ALEAUD</SAP:MESTYP>

<SAP:MESCOD />

450 is the client of my IE, not the sender SAP system.

What should all this mean? What does each ack mean and why do I get 2 of them?

When I check the Idoc no. in XI, there is no such IDoc. Where are these Idocs sent from?

POINTS WILL BE ASSIGN FOR SURE FOR CORRECT ANSWER.

Thanks, Olian

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
‎06-11-2008 1:36 PM
0 Kudos

Probably by default the ale configuration request an ack.

By managing the idxnoale you change this settings, and you should not recevie any ack and we can see if the first ack is related with the second.

Show replies
Show replies
Former Member
‎06-11-2008 2:00 PM
0 Kudos

But I want to receive acknowledgments if it is possible.

Olian

Former Member
‎06-11-2008 2:06 PM
0 Kudos

Using acknowledge with file adpater is possible only using BPM, i have spent many days for this issue, and i found out there is not a standard way (except with BPM) for managing ackowledge in the idoc-file scenraio.

Former Member
‎06-11-2008 2:10 PM
0 Kudos

Marco, but I am receiving acknowldgements!! I can send you a screen shot from my sxmb moni

I just don't understand, why there is 1 ok and another AckNoSupported and where do these ALEAUD idocs come from! But I'. receiving green acknowldgemtn status "Acknowledgment contains no error" in an IDoc->File scenario.

Of course, this also depends on the SP you are using..

Olian

Former Member
‎06-11-2008 2:14 PM
0 Kudos

Yes, you receive the ack, but one of this is a "false ack" beacuse says "ack not supported" and for me this is the default ack that the file adapter send (beacause, as i write before, it cannot send other ack, positive or negative).

Former Member
‎06-11-2008 2:19 PM
0 Kudos

Marco,

if it doesn't support Acks, how can I receive a green one? (positive)

if I get a green one, why do I get also Ack no supported?

Olian

Edited by: Olian Saludew on Jun 11, 2008 3:19 PM

Former Member
‎06-11-2008 2:26 PM
0 Kudos

These are the right question!

Can you see in the sap system the two aleaud idoc send by XI? In what status? In the body of the idoc you shoul find the idoc number of the first idoc send. It is correct?

Former Member
‎06-11-2008 2:45 PM
0 Kudos

yes, in the sender SAP R/3 there are ALEAUD idocs received exactly in the time, when these messages were processed. But there is no original IDOc number information. status is 50.

Olian

Former Member
‎06-11-2008 2:50 PM
0 Kudos

It's quite strange. A correct aleaud should contain the referenced idoc number. Could you post the payload of the two ack and alse the "hoplist" data?

Former Member
‎06-11-2008 3:18 PM
0 Kudos

green:

hoplist

<?xml version="1.0" encoding="UTF-8"?>

<!-- Response -->

<SAP:HopList SOAP:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">

<SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">

<SAP:Engine type="IS"/>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDOC</SAP:Adapter>

<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>

<SAP:Info>ARTMAS.0000000000026370:20080610211506</SAP:Info>

</SAP:Hop>

<SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">

<SAP:Engine type="IS">is.12.shlxiqcis1</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>

<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>

<SAP:Info>3.0</SAP:Info>

</SAP:Hop>

<SAP:Hop timeStamp="2008-06-10T21:15:13Z" wasRead="true">

<SAP:Engine type="AE">af.xiq.shlr3qdbs3</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>

<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>

<SAP:Info/>

</SAP:Hop>

</SAP:HopList>

content

<?xml version="1.0" encoding="UTF-8"?>

<!-- Response -->

<SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">

<SAP:TABNAM>EDI_DC40</SAP:TABNAM>

<SAP:MANDT>350</SAP:MANDT>

<SAP:DOCREL>700</SAP:DOCREL>

<SAP:DOCNUM>0000000000258080</SAP:DOCNUM>

<SAP:DIRECT>2</SAP:DIRECT>

<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>

<SAP:CIMTYP/>

<SAP:MESTYP>ALEAUD</SAP:MESTYP>

<SAP:MESCOD/>

<SAP:MESFCT/>

<SAP:SNDPOR>SAPXIQ</SAP:SNDPOR>

<SAP:SNDPRN>SHLSYSQAS</SAP:SNDPRN>

<SAP:SNDPRT>LS</SAP:SNDPRT>

<SAP:SNDPFC/>

<SAP:RCVPOR>SAPR3Q</SAP:RCVPOR>

<SAP:RCVPRN>R3QCLNT330</SAP:RCVPRN>

<SAP:RCVPRT>LS</SAP:RCVPRT>

<SAP:RCVPFC/>

<SAP:TEST/>

<SAP:SERIAL/>

<SAP:EXPRSS/>

<SAP:STD/>

<SAP:STDVRS/>

<SAP:STATUS>03</SAP:STATUS>

<SAP:OUTMOD/>

<SAP:SNDSAD/>

<SAP:SNDLAD/>

<SAP:RCVSAD/>

<SAP:RCVLAD/>

<SAP:STDMES/>

<SAP:REFINT/>

<SAP:REFGRP/>

<SAP:REFMES/>

<SAP:CREDAT>0000-00-00</SAP:CREDAT>

<SAP:CRETIM>00:00:00</SAP:CRETIM>

<SAP:ARCKEY/>

</SAP:IDocOutbound>

Red one:

<?xml version="1.0" encoding="UTF-8"?>

<!-- Response -->

<SAP:HopList SOAP:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">

<SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">

<SAP:Engine type="IS"/>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDOC</SAP:Adapter>

<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>

<SAP:Info>ARTMAS.0000000000026370:20080610211506</SAP:Info>

</SAP:Hop>

<SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">

<SAP:Engine type="IS">is.12.shlxiqcis1</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>

<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>

<SAP:Info>3.0</SAP:Info>

</SAP:Hop>

<SAP:Hop timeStamp="2008-06-10T21:15:13Z" wasRead="true">

<SAP:Engine type="AE">af.xiq.shlr3qdbs3</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>

<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>

<SAP:Info/>

</SAP:Hop>

</SAP:HopList>

content

<?xml version="1.0" encoding="UTF-8"?>

<!-- Response -->

<SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">

<SAP:TABNAM>EDI_DC40</SAP:TABNAM>

<SAP:MANDT>350</SAP:MANDT>

<SAP:DOCREL>700</SAP:DOCREL>

<SAP:DOCNUM>0000000000258083</SAP:DOCNUM>

<SAP:DIRECT>2</SAP:DIRECT>

<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>

<SAP:CIMTYP/>

<SAP:MESTYP>ALEAUD</SAP:MESTYP>

<SAP:MESCOD/>

<SAP:MESFCT/>

<SAP:SNDPOR>SAPXIQ</SAP:SNDPOR>

<SAP:SNDPRN>SHLSYSQAS</SAP:SNDPRN>

<SAP:SNDPRT>LS</SAP:SNDPRT>

<SAP:SNDPFC/>

<SAP:RCVPOR>SAPR3Q</SAP:RCVPOR>

<SAP:RCVPRN>R3QCLNT330</SAP:RCVPRN>

<SAP:RCVPRT>LS</SAP:RCVPRT>

<SAP:RCVPFC/>

<SAP:TEST/>

<SAP:SERIAL/>

<SAP:EXPRSS/>

<SAP:STD/>

<SAP:STDVRS/>

<SAP:STATUS>03</SAP:STATUS>

<SAP:OUTMOD/>

<SAP:SNDSAD/>

<SAP:SNDLAD/>

<SAP:RCVSAD/>

<SAP:RCVLAD/>

<SAP:STDMES/>

<SAP:REFINT/>

<SAP:REFGRP/>

<SAP:REFMES/>

<SAP:CREDAT>0000-00-00</SAP:CREDAT>

<SAP:CRETIM>00:00:00</SAP:CRETIM>

<SAP:ARCKEY/>

</SAP:IDocOutbound>

Former Member
‎06-11-2008 3:43 PM
0 Kudos

Comparing the two document of the first and second ack seem to be equals except for the docnumeber, this is normal beacuse two aleuad idoc are generated.

I need more infos, could you post the row of the table IDXNOALE in the SAp system and in the XI system? Can you also post the xml where in the first ack is written "ok" and in the second "ack not supported"?

Former Member
‎07-03-2008 8:32 PM
0 Kudos

Hi Olian, i had the same problem: i successfully managed to receive ALEAUD IDocs from System Acknowledgments issued by a File Adapter but the field DOCNUM in segment E1STATE was missing and so the outbound IDoc's status wasn't updated accordingly.

After 2 weeks looking for the answer in SDN and finding only links and incoherent answers i started debugging XI pipeline and managed to find the method where the ALEAUD IDoc is built and discovered that there's no line of code setting the value for DOCNUM.

More details:

Class name: CL_IDX_IDOC_SERVICE

Method: BUILD_ALEAUD_IDOC

Missing code (somewhere between lines 70 and 130):

L_E1STATE-DOCNUM = L_CONTEXT-DOCNUM

Hope that helps!

Edited by: Nicolás Dijkstra on Jul 3, 2008 9:32 PM

Former Member
‎08-20-2008 7:41 PM
0 Kudos

Hi, I am also interested in that scenario.

The the current status is, that in a IDoc -> Xi -> File scenario, we are not able to update the status record of the IDoc according to the system acknowledgement?

According to the table at the end of the pagein "IDoc Processing with the IDoc Adapter" (http://help.sap.com/saphelp_nwpi71/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm)

there should be a mapping between the system acknowledgement and the IDoc status.

So is there currently a possibility to update this IDoc status without using an integration process?

Best regards

Florian

former_member181962
Active Contributor
‎06-10-2008 3:48 PM
0 Kudos

Hi Olian,

It looks like the IDOC Acknowledgement configuration is enabled in your backend system.

What it means its that when there is an IDOC sent from XI to your backend, the status of that IDOC will be sent back to XI .

This is done by a set up in your backend system.

There will be a batch program which send the ALEAUD idocs(Acknowledgements which has the status information of the idoc that was created in the backend).

Regards,

Ravi

Show replies
Show replies
Former Member
‎06-10-2008 3:53 PM
0 Kudos

Hi Ravi,

but this is an IDOC->FILE async scenario. I'd understand if the target was IDOC, then ALEAUD would be sent back. But which system is createing this ALEAUD idocs, if the target is a file adapter?

Olian

Edited by: Olian Saludew on Jun 10, 2008 4:53 PM

Former Member
‎06-10-2008 4:04 PM
0 Kudos

You can refer to link

http://help.sap.com/saphelp_nw04/helpdata/en/44/932e8896b610bbe10000000a422035/frameset.htm

You are getting error as NoAckSupport because File adapter does not support any kind of Acknowledgment.

http://help.sap.com/saphelp_nw04/helpdata/en/44/a1b46c4c686341e10000000a114a6b/frameset.htm

If you check the link then it will clarify your doubt. It says that

"In the XI request message, the original sender of the acknowledgment IDoc is no longer known.

The XI request message created is a new message. Monitoring is not able to determine which was the original message."

That's the reason you are getting Idoc number which is not exist in XI as well as R/3.

Gaurav Jain

Points if answer is helpful

Former Member
‎06-10-2008 4:16 PM
0 Kudos

>You are getting error as NoAckSupport because File adapter does not support any kind of Acknowledgment.

How can you explain then that I receive Acknowledgment OK? (yes, the green one)

>If you check the link then it will clarify your doubt. It says that

>"In the XI request message, the original sender of the acknowledgment IDoc is no longer known.The XI request message created is a new message. Monitoring is not able to determine which was the original message."

>That's the reason you are getting Idoc number which is not exist in XI as well as R/3.

But this is only when sending Acks as XI message. I have nothing configured in IDX_ALEREQUEST. It is empty.

Olian

Former Member
‎06-10-2008 4:35 PM
0 Kudos

I have mention about error NoAckSupport, (which is green flag only).

You can refer to link below

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50...

Gaurav Jain

Former Member
‎06-10-2008 4:49 PM
0 Kudos

>I have mention about error NoAckSupport, (which is green flag only).

Green flag is a correct acknowldgement with label "Acknowldgement contains no errors"

All others even "AckNotSupportd", which has a label Acknowledgment is not possible is a "red" one.

Thanks for the link, but I've seen it many times before and it doesn't help me.

Any other ideas?

Thanks,

Olian

Former Member
‎06-11-2008 9:32 AM
0 Kudos

No one to help me with this?

Pliiiiz..

Olian

Former Member
‎06-11-2008 10:09 AM
0 Kudos

Hi Olian,

the second ack you receive is sent by the file adapter because it doesn't support acknwledge, ad it is normal. If you don't want this ack you have to simply manage the table IDXNOALE.

The first positive acknowledge is quite strange, do you use a sender idoc adapter in your scenario?

Former Member
‎06-11-2008 11:02 AM
0 Kudos

Hi,

yes, it is an IDoc->File scenario, so yes, I'm sending IDocs as a source document, but there is no need for sender adapter (in Idoc case).

Since I know, file adapter supports acknowldgement, but system acknowldgment, not application.

But still I'd like to know, how exactly should this work, where come these acknowldgements from, why there are 2 of them and what should these ALEAUD idocs mean.

Thanks,

Olian

Former Member
‎06-11-2008 12:03 PM
0 Kudos

File adpater support system ackowledge only via BPM, so in a no-BPM scneario it doesn't support ack.

Can you try to manage tabel IDXNOALE, add new raw with the right port mandt (referred to sap ecc system) and message category (the idoc type), and leave the field typ empty.

After this try to resend the idoc.

Former Member
‎06-11-2008 12:15 PM
0 Kudos

How is it then possible I'm receiveing acknowldgements?

What should be achieved with your suggestion? Stopping acknowldgment requests?

Thanks,

Olian

Ask a Question