Issue with SOAP to RFC Sync scenario

[former_member440061]

Hello Experts,

I am currently facing an issue with SOAP to RFC Sync scenario which we recently transported to Quality system. The scenario works fine in Development environment. we are using SAP PO 7.4.

I am testing the ICO using SOAP-UI --> PI --> RFC (ECC). and I get below error in SOAP-UI error logs.

ERROR:java.net.SocketTimeoutException: Read timed out

The response window in SOAP UI does not shows anything except "<missing raw response data>" when clicked on "Raw" tab. Also, there is no error in both the channels (SOAP and RFC) in PI, and status of both is green.

The only anomaly I noticed is that there is no After Mapping (AM) payload available for response. I do however see the response sent by RFC. Also, when I go to Message Monitor --> Database tab --> Message Content --> Main Document. The browser window opens up with nothing inside it. But when I do View Source, I get the following:

Now I am not sure why the After mapping payload is not being generated and why am I getting above HTML output.

1. I have tested the mapping in ESR and it is working fine.

2. Sync message logging is enabled in NWA and both MS and AM are visible for Request part.

3. I have tried full cache refresh, but did not work.

4. Also, tried re importing the objects in ESR.

5 The scenario works fine in Dev both with SOAP UI and the actual source application/system.

6. In Quality, I am receiving Request from SOAP UI in PI, which further sends it to RFC. RFC's Response also received in PI, but no mapping output is visible in Response.

Given below is the message log for Response message:

Could there be any other reason why I am getting the time out error in SOAP UI?

Please help me resolving the issue. Any help will be appreciated. Thanks in advance.

Regards,

Faisal

[former_member440061]

Any thoughts on this please..? Anyone..?

[former_member440061 · Accepted solution]

The issue got resolved by increasing the Socket Time out in SOAP UI.

[sugata_bagchi2]

Hi Faisal,
could you please enable logging in the ICO -advance tab settings for mapping step? enable and log the mapping step AM for both logging and staging, you will be able to see the transformed payload there after the response mapping executed. Please verify this payload as it will be passed to SOAP sender system.
use this steps to check the payload -

You will find a AM step there and get the payload from there to verify-

Also check in QA, if you have the correct service interface and associated schemas imported for the sender SOAP system.

Thanks

Sugata

[sugata_bagchi2]

Hello Faisal,
Check the below pointers - if your scenario is simple SOAP to RFC Sync-

1. Check you have J2EE auth to post message from external tool - soap ui to your PI system.

2. as you are getting socket exception, check if your soapui is in the same network.

3. check the quality of service in your sender soap channel - should be Best Effort as it is a sync scenario.

I think all the above are already in.

4. Now, execute the RFC in standalone - in ECC system itself with the same data that you are passing from PI and see if it is generating output.

5. Instead of checking the main document of the response message id in PI, select the response message ID and click on the open message button.

6. it will open a new window and there you will find a tab below called payload, you can check the response payload from there.

7. take that payload and execute that in the response mapping you created in PI, standalone mode.

8. Verify that, if the response payload is matching the rfc.response schema.

9. Did you use the RFC imported schema in response or used the RFC as external definition?

Thanks

Sugata

[former_member440061]

Hello Sugata,

PFB my response:

1. Check you have J2EE auth to post message from external tool - soap ui to your PI system.-- Will check this. But I think auth should be in place since I am able to receive requests from SOAP UI.

2. as you are getting socket exception, check if your soapui is in the same network.-- Yes

3. check the quality of service in your sender soap channel - should be Best Effort as it is a sync scenario.--Yes

I think all the above are already in.

4. Now, execute the RFC in standalone - in ECC system itself with the same data that you are passing from PI and see if it is generating output.-- I checked this with ABAP Team and they said the RFC is working fine. Also, as I mentioned, I am able to receive the response from RFC in PI.

7. take that payload and execute that in the response mapping you created in PI, standalone mode.-- This is working fine and is generating output. Also, the message logs mention that the response mapping is being executed fine and the response being delivered.

8. Verify that, if the response payload is matching the rfc.response schema.--Yes

9. Did you use the RFC imported schema in response or used the RFC as external definition?--I am using the RFC imported schema.

Anything else that can be checked?

Regards,

Faisal

[former_member619892]

Hi Faisal,

You are referring synchronous scenario in your post while it's asynchronous message in the error message you posted. I suppose there are some difference between working interface in DEV and error in QA.

I also recommend to deactivate and then re-activate communication channels to backend system in case it's caching issue (cache refresh alone often is not sufficient) for any issues that involve calling RFC.

Regards,

Walter

[former_member440061]

Hello Walter,

I noticed that too. Actually, when I check the logs for Request message, it has similar message logs with synchronous. But in Response, it is "Async" in both Dev and QA. probably thats the default way how SAP choose to log the processing.

Also, I have tried de-activating and activating channels, ICO multiple times along with full cache refresh, but it is not helping.

Any other thoughts?

Thanks,

Faisal

[former_member440061]

Hello Sugata,

Please be informed that I was able to get this work by maintaining "Socket Time Out" in SOAP UI.

Default time out for SOAP UI is 1 minute and it is 5 minutes for PI. The RFC in ECC is taking around 2 minutes to return the response, and by that time the Request gets timed out in SOAP UI. I have increased the SOAP UI time out to 5 minutes and now able to receive response.

RFC performance is being checked to make it better.

Thank you very much for taking out time to look into this and helping me.

Regards,

Faisal

[former_member440061]

Any thoughts on this please..? Anyone..?

[vinaymittal]

check in ecc qas if the rfc destination pointing to PO for that rfc works fine or not

Go to sm59 in ecc qas check the program id if it’s valid and do a ping test

Something seems wrong with the rfc destination

[former_member440061]

Hello Vinay,

I dont think RFC destination is the issue here. we are using ECC(RFC) as receiver here. The Receiver RFC channel does not contains any RFC destination and has ECC Q credentials. Also, Request is working just fine and we are receiving response from RFC.

The issue is that SOAP UI is not receiving any response from PI. Any other thoughts?