Receiver Determination Error: Message is incomplete. No sender found

[former_member391594]

Hi Experts,

Please help me on below issue.

We are using PI 7.4.we are getting the below error, when we are trying to test the payload by using Test Configuration option in ID part.

Receiver Determination

<Not found>

Runtime error

Message is incomplete. No Sender found

  (ImH1)

<Trace level="1" type="B">CL_RD_PLSRV-ENTER_PLSRV</Trace>
<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="E">CL_RD_PLSRV-ENTER_PLSRV</Trace>

Thanks in advance.

Regards,

Anoosha

[former_member391594]

Hi All,

Thanks for your response.

But still my issue there. This is File to Idoc scenario. there is no multiple receivers.And i have done the End To End testing,but getting same error.

In Receiver Agreement it is picking wrong Business component. That BC is not available in our ID.

PFA is the error.

Please do the needful.

Regards,

Anoosha

[former_member186851]

Hello Anossha,

Do some  dummy changes and activate the RA and check the cache status.

[former_member391594]

Hi Raghuraman,

Done,But getting same error.

Regards,

Anoosha

[hasan_celebi]

Hi Anoosha;

For business system services, the adapter-specific identifiers are defined in the System Landscape Directory (SLD) (as attributes of the relevant business system) and therefore cannot be changed.

If the adapter-specific identifiers for a business system change in the SLD, this information is not automatically updated in the Integration Directory. To synchronize the information in the Integration Directory with the SLD, choose Comparing with System Landscape Directory in the window forEditing Adapter-Specific Identifiers . This function is only available for business system components.

Adapter-Specific Identifiers - Integration Directory - SAP Library

Regards

Hasan

[former_member186851]

cache is up to date?

[former_member391594]

Hi Hasan,

I have compared the SLD n Adapter specific attribute both are same. And cache is also up to date. We are unable to understand why we getting this issue.

Regards,

Anoosha

[former_member186851]

Hello Anoosha.

If all the configs are fine,Try re-congifuring completely and check..Also ensure the message is going to RA and check that RA.

[markangelo_dihiansan]

Hi Anoosha,

Using the test configuration option in ID gives mixed results. Use RWB -> send test message instead.

Regards,

Mark

[PriyankaAnagani]

Do you have multiple Operations in your Service interface? If yes, then as suggested by Hasan, please check the Radio button "Operation Specific" in the Receiver Determination.

Also, try making dummy changes an reactivating the Receiver Determination and make sure cache is updated.

---Priyanka

[hasan_celebi]

Hi Anoosha;

I think the problem is in Receiver Determination with the (ON) radio button call Operation Specific

Regards

Hasan

[former_member5611]

Hello Anoosha,

Please check the following thread:

https://scn.sap.com/thread/1506450

Best regards,

Bence

[former_member186851]

Hello Anoosha,

Are you using multiple receivers?

Might be conditon is not satisfied or payload is incorrect.

[former_member391594]

Hi Raghuraman,

No we are not using multiple receivers. And there are no conditions maintained.

[former_member186851]

Hello Anoosha,

Then the problem could be with the payload.Your XML is correct and did you try any end-end testing?

What is the end-end scenario?