unwanted ack idocs

[Former Member]

Hi,

i changed this:

IDOC -> XI -> external adapter engine -> JMS queue

to that:

IDOC -> XI -> jms adapter -> JMS queue

Both variants work well so far. But with the newer version (without external adapter engine) i observe in SXMB_MONI in the ack.column a red icon, which says something like ack. cannot be handled.

There is indeed no configuration in the sending r/3 system to handle acks.

The strange thing is, that with the older variant in same column in SXMB_MONI was an icon with a green question mark (something like waiting for ack.)

It looks for me, as if the jms adapter generates an ack on its own, which is sent back via idoc to r/3.

The check box in the jms adapters configuration, about generation delivery acks is not set.

Can someone confirm this behaviour ?

Does this affect the r/3 system (error messages etc.) ?

What would be the best approach to solve this ?

btw. XI is on SP13

Thanks and Regards,

Peter

[MichalKrawczyk · Accepted solution]

hi,

try filling table:IDXNOALE

also have a look at

<b>3.4 Configure the Integration Server (Optional)</b>

point 2

on:

http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how...

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

[Former Member · Accepted solution]

Hello Michael,

sorry for another stupid question ...

The IDXNOALE should be filled on the XI system, right ?

What influence has the setting ACK_SYSTEM_FAILURE in SXMB_ADM ? This was not set in my configuration, is this equal to value 0 ?

Thanks + Regards ,

Peter

[Former Member · Accepted solution]

Hi,

I had replied to a similar thread few days back and the solution suggested was same plus you can find an additional solution by Alessandro Just after my reply.

Now to your queries,

<i>The IDXNOALE should be filled on the XI system</i>

Yes, abap stack.

<i>is this equal to value 0 ?

</i>

If you see the default value is 0.

Regards,

Anirban.

[Former Member · Accepted solution]

Hi,

The similar thread that i wrote was

Sorry, for missing that.

Anirban.

[Former Member · Accepted solution]

Hi Anirban,

thank you, this helped me a lot.

Best Regards,

Peter

[Former Member · Accepted solution]

Hello everybody,

i now have inserted an entry in the IDXNOALE table, but the problem persists.

I followed the instructions in the how-to-document mentioned above. The table shown there, has 3 columns, mine has 5 (what are the 2 fields for ?)

The messagetype i entered is ALEAUD - is this correct ?

Thanks + Regards,

Peter

[Former Member · Accepted solution]

Hi,

What is the mesage type used in we20? Can you check?

And what are the two extra colums you are getting, other than port,client and message type?

Did you use bd54? if so then, What message type you used in bd64?

<b>What is the name of the idoc you are trying to send?

</b>

Regards,

Anirban.

[Former Member · Accepted solution]

Hi,

<i>The messagetype i entered is ALEAUD - is this correct ?

</i>

Check In we30 are you using the ALEAUD01 idoc then the message type is correct.

By the way this will only work if you have configured your patner TYPE as LS IN we20.

Check in we81 if this message type exists and are you planning to use this.

Hope this may narrow down the error scope.

Hope this helps.

Anirban.

[Former Member · Accepted solution]

Hello Anirban,

the 2 relevant systems are listed in bd54:

D01_100 (Dev 100) and XID_100 (XID 100)

in bd64 in the treeview of the distibution models, ican see CRM interface -> Dev 100 -> XID 100 and the message types are ORDRSP, QUOTES and ZDEBMAS.

in we20 there is a messagetype in outbound param.s, which is SERDAT.

in we30 i can see ALEAUD01 listed and checked.

the type of partner is LS in we20.

in we81 ALEAUD is listed.

the IDoc, that is sent from D01 to XID is ORDRSP.

the two extra columns in IDXNOALE are NEG and TYP

Thank you,

kind regards Peter

[Former Member · Accepted solution]

Hi Peter,

Seems we can become good friends after this trouble shooting

Anyways,

Use message type as ORDRSP And you need to use the message type of the idoc you want to send to xi.The pdf used Aleaud as it was sending ALEAUD01 idoc, but in your case use Message type for the idoc you want to send so use ORDRSP and reconfigure and cross check ALL the steps one by one slowly.

Again most importantly Your patner profile in we20 do not have the entry for ORDRSP so need to make an entry on the outbound side as well and also the parner type as LS. To add use the " + " icon and define clearly.Actually SAP needs to know if the data is coming from a server which is of a trading patner, if thats the case it refers to the patner profile.

This should get you going, but donot confuse between the idoc used in the pdf and the idoc you need to send.

All the best!

Anirban.

Ps: Its almost end of day here in India, so if still it does not work after these steps please refer:

/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

And

http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

other then the acknowlegement pdf.

[Former Member · Accepted solution]

Hello Anirban,

my problem is solved now !

Thank you for your patience. This was a bit confusing for me, but now i hope i understood it.

Thanks again and best regards,

Peter

[Former Member · Accepted solution]

Hello Peter,

Thats a great news !! And i am happy that i was helpful.

All the best,

Anirban.

[Former Member · Accepted solution]

Thanks michal. It solved my acknowledgement problem - Arun

[Former Member]

Hi,

you may wanna have a look at SAP Note 888596 also...

regards,

Peter