cancel
Showing results for 
Search instead for 
Did you mean: 

PI - MONI Error - Missing or Invalid Receiver Agreement

Former Member
0 Kudos

Hi All,

My scenario is File to ECC(SOAP), Messages are failed in PI MONI as CO_TXT_OUTBINDING_ERROR"

No Standard agreement found

For 5 messages , it worked for 3 messages, failed for 2 messages with above error,.

Please help me how to resolve this error.

Regards

Jeevitha N

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

Hi All,

I tested the same from  RWB  test tool also, still its showing same error.

I changed the same to classical and tested, it working fine..

Same error is occurring for all ICO scenarios suddenly.

Please let me know what is the root cause for this problem

Do we need to do any SLD changes ?

In SXMB_ADM-  Integration Engine configuration ,  role of the business system is also Integration Server.

Regards,

Jeevitha N

former_member182412
Active Contributor
0 Kudos

Hi Jeevitha,

Even from runtime work bench when you send the message it will reach to integration engine and your ICO doen not execute in abap stack of PI system and there will be no configuration for this interface in ABAP runtime cache that is why it is failing with above error, if you want to send the message to ICO then there will be Send Test Message in NWA depending on your PI version, if you dont have use this blog to send the message to ICO , Or you can run the scenario normally means place the file in the directory.

Regards,

Praveen.

former_member186851
Active Contributor
0 Kudos

Hello Jeevitha,

What is the scenario your configuring?

former_member202642
Participant
0 Kudos

Hi Jeevitha,

Maintain SXMB_ADM settings.

1) Configure Sender/Receiver ID

2) Integration Engine Configuration.

former_member202642
Participant
0 Kudos

Hi Jeevitha,

Check your configuration in SXMB_ADM.

In Integartion engine configuration Role of business should be integration server.

Regards,

Aamir

Former Member
0 Kudos

Hi All,

I checked few other ICO scenarios, those also not working at ID level itself.

Its throwing error as "No Receiver Could be determined"

PFA Error screenshot for more details.

But the same is working if we change it as classical.

Please let me know the solution, how to solve this. Any changes in SLD required ??

We have so many ICO scenarios , its not possible to change it as classical.

Regards,

Jeevitha N

former_member182412
Active Contributor
0 Kudos

Hi Jeevitha,

The reason for the above error is you are using Test Configuration tool to test your ICO configuration, Test Configuration will execute in ABAP stack not in java stack that is why for this ICO there will be no configurations in ABAP runtime cache and you are getting error "No Receiver could be determined", for ICO you must not use Test Configuration tool which is developed based on ABAP, this tool only works for classical configuration that is why your classical configuration is working. You need to run your ICO scenario end to end and test the scenario.

Regards,

Praveen.

iaki_vila
Active Contributor
0 Kudos

Hi Jeevitha,

That ID tool is only available for classical scenarios and not for ICO ones.

You should test your scenario from Runtime workbench test tool.

Regards.

Former Member
0 Kudos

Hi All,

Problem still exists, There is no condition in receiver and interface determination. Interface is working at ESR level.

I have selected objects from drop down box only, not manually  typed anywhere..

I tried to change it to Classical from ICO - Its throwing error as "Receiver Determination failed "

In classical -"Receiver agreement not found ".

But 3 messages were successful out of 5 when testing 2 days before, If any issue in Receiver agreement or Receiver determination, how could that have happened?

Please help me to solve this issue .

Regards,

Jeevitha N

former_member182412
Active Contributor
0 Kudos

Hi Jeevitha,

Can you give us the screen shots of your configuration and failed xml messages so that we can help you further.

Regards,

Praveen.

former_member186851
Active Contributor
0 Kudos

Hello Jeevitha,

what is your scenario? I mean sender and receiver.

and as Praveen suggested post the configurations.

Try doing a cache refresh as well.

iaki_vila
Active Contributor
0 Kudos

Hi Jeevitha,

This problem should be raised when a receiver agreement can not be found, normally the problem could be that you have defined a interface or service name manually and you have a typo error. As Praveen said the problem could be in any particular condition, if you are using any payload tag, take into account the case sensitive.

Regards.

former_member182412
Active Contributor
0 Kudos

Hi Jeevitha,

Do you have any conditions in interface determination? check the failed ones does not match the conditions.

Regards,

Praveen

former_member186851
Active Contributor
0 Kudos

Check all the things as experts suggested and do a cache refresh.

sateesh_adma
Participant
0 Kudos

Hello Jeevitha,

Can you please check whether you configured all PI Pipeline steps.

Thanks,

Sateesh