Still getting same issue. Going to work on it some more today. Our issue is we bought a 3rd party application that has an Addon in ERP. This addon code is using the RFC to send data from ERP to PI and then to the 3rd party app.
I created a ticket with SAP. Created the trace files etc. but in the end SAP pushed it off to the 3rd party software company who then said its a Basis or PI issue. So not resolved.
Can you see any errors in transaction sm58 of the sender system? In case of communication problems, you should find an entry there, that will tell you details about the reason for your issue.
I think I get the problem now. Most probably you are missing the NWA configuration. It was described by in his blog here: . Focus on "Sender IDOC AEX adapter" part, steps 2 and 3. And don't mind that the topic of this blog is "IDoc adapter" - this part is identical for IDoc and RFC adapters.
We have already configured Step2 and step3. In previous PI Version even in PI system ABAP Stack we will mention rfc name. But in single stack do we need to maintain Function Module name anywhere in NWA.
Please check the sender adapter as its not able to get the meta data required from ECC into PI. can you validate your sender adapter metadata settings.
First : Test your FM in ECC alone with out Sending to PI. Does it work correctly.
Second: Test the TCP/IP connnection in SM59 of ECC if it works correctly. U have used the same Programme ID whcih is used in your sender RFC channel whcih you gave in PI.
Thrid: Execute the FM to send the data into PI let me know what is the exact error your getting.
in step3: while executing the FM with the rfcdestination it is throwing an error in SM58 as Unsupported function module FM_NAME used with IdocActivationSpec reg
I am using same rfc destination for both IDOC and RFC..... I cant remove inboundRA parameters....If I remove those thing my IDOC wont work properly..... so for RFC do we need to create another RFC destinationin Both NWA and ECC.
u get this problem when there are mutiple listners for the same messages. You need to close all the mutiple listners. also you can check NWA logs there will be enter for the same error.
you have delete the mutiple connections which are listening from ECC to PI ask the basis team to do it. You need to go logs and trace in NWA and look for the logs.
Hi Srinivas, I am having the same issue. RFC alone working fine. TCP/IP connection test in SM59 working perfectly fine no error. Program id is maintain in PI. No error while program calling RFC. Nothing is ST22. Can you please share, how did you resolve the issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.