No suitable sender agreement found on single stack system

[former_member198060]

Dear experts,

I am currently doing some tests on a PO 7.31 system.

I have created a simple file to file scenario where I just want to route a file from point to point without creating any content on the design part.

So I created an integration flow with two dummy service interfaces. For sender and receiver I am using a BC, one sender and one receiver FTP file channels have been created. All objects have been activated and are showing up as consistens when I am doing a cache check from NWDS.

Now in the CC monitor for the file sender channel I am getting the message "No suitable sender agreement found".

I am not sure if I am missing any step in the iFlow, but I have checked all the tabs and cannot seem to find a missing setting. Also I have start/stopped the CCs and did some dummy changes / reactivations of my objects. Unfortunately none of this helped.

Do you have any idea what else could be the reason for this error?

[iaki_vila · Accepted solution]

Hi Peter,

A few cents, have you checked this document http://scn.sap.com/docs/DOC-27342?

Regards.

[former_member198060 · Accepted solution]

Thank you for the hint, in fact I forgot the most important step: Deploying the iFlow. I thought it would be enough to activate it (similar to the other objects), but this is not sufficient.

[former_member190624]

Hi Peter,

Please cross check your sender agreement is using same sender business component as sender communication component. Also check , you might be selected wrong communication channel in Sender agreement .

Thanks

Hari.

[former_member198060]

Hi Hari,

In this case there is no sender agreement. Similar to an integrated configuration I am using an integration flow (object that is created in NWDS). So aside from the BCs and CCs we only have one configuration object.

In the ICO we had the tab organisation so everything was quite easy to oversee. In the iFlow now I am not sure if I maybe missed some important step which is causing this error.

[former_member190624]

Hi Peter,

Yes you are correct , what I meant is please check in  Inbound processing tab .

Thanks

Hari.