Interface Issue in PI7.1 - Unable to find receiver

[Former Member]

Hi,

I have a strange issue cropping up. An interface has gone for production. Now due to some support packs being installed on the target side, they are testing few interfaces in Dev environment again. But this time it is not working. This interface was tested long back.

Issue:

PI receives message from SAP but is unable to send the message to target

Error Shown:

<SAP:Stack>No receiver could be determined</SAP:Stack>

• -->

<Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>

<Trace level="1" type="T"> Cache Content is up to date </Trace>

<Trace level="1" type="T">No Relation found - accept given Receivers. </Trace>

</Trace>

</Trace>

<Trace level="1" type="System_Error">Error exception return from pipeline processing! </Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>

<!-- ************************************ -->

Observation and Steps Taken for checking:

No conditions are there for Receiver Determination. Its a simple proxy to http scenario.

I performed the unit testing. Did the configuration testing as well as have sent a same payload to the target system using RWB.

All are successful and message also reached target successfully.

But when SAP sends it gets stuck. i have the same issue with 2 interfaces, both having the same problem.

Please Guide me.

Thanks,

Kevin

[Former Member]

Hi,

Can you check in transaction SXI_CACHE if your receiver determination object exists on ABAP stack?

Regards,

Vikas

[sumesh_k2]

May be you can try regenerating the proxies and checking again from SAP to PI.

[former_member187339]

Hi Kevin,

Got to SXMB_MONI, take sender details (system, interface etc) from soap header.

Based on that do a seacrhc in ID part and try to locate your receiver determination.

Are you able to do a search and find the object? Also try doing a cache refresh

Regards

Suraj

[Former Member]

Hi,

Thanks for the inputs. But all seems fine.

Suraj - I have verified as per the steps you have mentioned. All is good and the namespaces and other details are correct.

When i search i am able to find the respective Receiver Determination.

-Kevin

[former_member187339]

Hi Kevin,

Then the old method which we use to follow here.. Do a dummy change (like putting some value in description) in Receiver determination and activate it.

See if this solves the problem.

BTW you were saying that a successful message comes when you test this interface from RWB or test configuration; but when you test from SAP it is throwing this error!!!

try comparing all fields in SOAP header field. Also try comparing the "trace" in both cases.

Regards

Suraj

[Former Member]

Check the sender interface name and sender system details populated by the SAP when sent via Proxy..

may be some party fields might be getting populated...as a result not able to find the receiver ...

Rajesh