Skip to Content
0

No Receiver Could be determined in SAP PI in IDOC to FTP scenario

Jul 08, 2017 at 11:07 PM

228

avatar image
Former Member

Hi Guys,

I know this may have been raised already in previous posts but none specifically to my situation.

Really need your help on this error.

Always get this error in my receiver determination: "No receiver could be determined". I did create one already and please see screenshot below.

Where did I go wrong?

Hope to hear you soon.

Thanks,

Jeff

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Manoj K Jul 09, 2017 at 03:55 PM
1

Jeff,

Do you have condition in your RD ?

Try to test End to End scenario instead of testing it local in ID part.

Br,

Manoj

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Jul 10, 2017 at 06:08 AM
0

Hi Manoj,

No conditions on RD part.

How do I do an end to end testing scenario?

Thanks,

Jeff

Show 4 Share
10 |10000 characters needed characters left characters exceeded

Jeff,

You may take some test data i.e IDOC XML then in RWB-->Testing you may trigger this data.

Just give it a search you will find lots of thread on how to trigger data.

Br,

Manoj

1
Former Member

See if you have access to T-Code WE19 on your ECC backend. With that you can simply copy an existing IDoc and send it to your PI/PO system, manipulating any of the existing header data if needed.

As far as I'm aware, there is no standard program in ECC to download IDocs as XML. There are functions that can be used to easily write such a program but unless somebody has done that already (chances for that are not too bad) you would be able to get the test data from ECC without sending the IDoc to PI/PO first.

1

There are FM to get IDOC as XML if you have IDOC number : IDOC_XML_TRANSFORM and for vice versa IDOC_XML_FROM_FILE. But i remember i used on of them in that past and had issue of converting '&' characters to '#'.

1
Former Member
Manoj K

Indeed there are. The main problems I see with them is that

a) you need access to test function modules, which will be restricted in many client environments outside the development system

b) the output is not usable as is and will require manual or programmatic reformatting

1
gurudatta d Jul 10, 2017 at 06:45 AM
0

Hi Jeff,

In Case you have an authorisation to trigger idoc from source system ..you can directly trigger the idoc and test end to end from Source-->Target and see what exactly is the error it is throwing

Thanks,

Guru

Share
10 |10000 characters needed characters left characters exceeded