Message comes through ABAP stack instead Java

[manikandan_shanmugam3]

Hi All,

I have created an ICO for IDoc to File scenario , created RFC destination(Type T TCP/IP) in ECC for PI Java Stack but still IDoc are reaching ABAP stack instead Java (IDoc_AAE). Its the same case with HTTP_AAE to RFC Scenario as well.

PI version 7.31

Regards,

Mani

[Former Member · Accepted solution]

Hi Mani

Take the idoc number, check it in ECC using transaction WE02 or WE05.

Check the port it is using. Then check the port and find out the RFC destination it is using.

I am sure the port is using the old RFC destination and hence it went to ABAP stack.

[manikandan_shanmugam3]

Hi,

Problem was that IDoc has not reached PI which stuck in ECC SM58 due to authorization issue of user( to send data to IDoc AAE), end user was wrongly sending data to ABAP stack port

Regards,

Mani

[Former Member]

Hi Mani,

I guess the problem is with your existing old configurations without ICO if any.

Are you still having any standard configuration for this scenario. if yes delete that first.

Check any floating objects like sender agreements or interface determinations still existing without pointing to any scenario in ID. if yes delete them also. then you re-run the scenario with

ICO, then it works properly.

Regards,

Nagesh

[roger_alluivall]

I guess the problem is you didn't configure properly the Resource Adapter InboundRA. And your ALE sender port is not pointing to the proper destination. Please, check the following link:

Configuration of inboundRA in the Java IDoc_AAE Adapter - Process Integration - SCN Wiki

I hope it helps!

Regards!

[naveen_chichili]

Hi Mani,

Adding some more info .. the below blog might be able to help you.

http://scn.sap.com/docs/DOC-34155

Thanks,

Naveen         

[manikandan_shanmugam3]

Hi Naveen,

I just checked RFC destination in ECC which is pointing to PI Java Stack.

Any View on HTTP to RFC scenario?

Regards,

Mani

[iaki_vila]

Hi Manikandan,

May be in the sender system you have configured the RFC destination to the PI ABAP stack.

You can check all the configurations in this link:

Regards.