Receiver determination doesn't work for same IDoc type but in differentSWCV

[Former Member]

hi guys,

we have an emergency now. Receiver determination doesn't work for same IDoc type but in different SWCV.Please check below for detail.

1. The process flow is : R/3 IDoc -> XI -> Third party system

2. In previous release R13, IDoc ORDERS05 was imported and used in XI and software component version is R13. And receiver determination was created.

3. Now, in new release R17, IDoc ORDERS05 was imported from R/3 to XI again and software component version is R17. And in R17, the receiver determination created in R13 was used for both old interface(R13) and new interface in R17.

Then we encountered the problem, both interfaces doesn't work now, even we deleted the receiver condition(In R13, IDoc ORDERS05 was sent to system A, and in R17 IDoc ORDERS05 was sent to system B, RCVPRN was used as an condition).

Does anyone encounter this problem? really need and appreciate your help.

-Eddie

[ranjit_deshmukh]

Hi Eddie,

Can you tell exactly where your scenario is failing?

I mean can you extract some info from moni or some more inputs?

Ranjit

[Former Member]

information from monitor:

Status Sender Service Sender Namespace Sender Interface

reschedul XXXCLNT100 urn:sap-com:document:sap:idoc:messages ORDRSP.ORDERS05

columns for "Receiver Service","Receiver Namespace", "Receiver Interface" are blank

And then double click records in monitor, go into detail information...

Normally there's lots of setps existed, such as

-

---

Inbound Message ( CENTRAL )

-

---

Receiver Identification

-

---

Interface Determination

-

---

Receiver Grouping

-

---

Message Branch According to Receiver List

-

---

Technical Routing

-

---

Call Adapter

But now there's only one setp -

---

"Inbound Message ( CENTRAL )" existed, no any another setp..., and payload in inbound message looks good.

And in SMQ2, I checked the queue information, found there's an error - "An exception occurred that was not caught." No any other detail information for this error.