B2B Integration

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

Hello Manuel,

Thank you for your response. I am attaching the sap3 and JCo logs along with SM58 screenshot. One other note if it matters, if we are using the existing system's program ID the idoc comes through but this issue with the new program ID. The existing program ID is connected to GENTRAN server for Unix. BASIS confirmed that the new program ID is registered. They see our SI IP hitting their server in their logs.

Best Regards,

Vamsi. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

Hi Vamsi,

which encoding is used in SAP system?

Perhaps you have to align the outbound encoding in the SAP JCo adapter with SAP's encoding.

Also in in SM59 the unicode flag active?

Best regards

Manuel

Hello Manuel,

Thank you for your response. I am attaching the sap3 and JCo logs along with SM58 screenshot. One other note if it matters, if we are using the existing system's program ID the idoc comes through but this issue with the new program ID. The existing program ID is connected to GENTRAN server for Unix. BASIS confirmed that the new program ID is registered. They see our SI IP hitting their server in their logs.

Best Regards,

Vamsi. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

Hello Manuel,

Am attaching the screenshot from SM59. Is this the one you are talking about? Where would the unicode setting in JCo that similar to SAP?  Unicode and Encoding are different I presume but I don't see an encode option. I could only run the Connection Test and it works fine but I couldn't run the Unicode test in SM59. I will have to reach out to BASIS to run the Unicode TEST. Should that be running successfully? 

Hi Vamsi,

which encoding is used in SAP system?

Perhaps you have to align the outbound encoding in the SAP JCo adapter with SAP's encoding.

Also in in SM59 the unicode flag active?

Best regards

Manuel

Hello Manuel,

Thank you for your response. I am attaching the sap3 and JCo logs along with SM58 screenshot. One other note if it matters, if we are using the existing system's program ID the idoc comes through but this issue with the new program ID. The existing program ID is connected to GENTRAN server for Unix. BASIS confirmed that the new program ID is registered. They see our SI IP hitting their server in their logs.

Best Regards,

Vamsi. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

Hi Vamsi,

these are just guesses as I have seen in the trace that the EDIDC40 control segment contains non ANSII characters.

From my point of view you have to change in SM59 to Unicode in your screenshot and test it.

Best regards

Manuel

Hello Manuel,

Am attaching the screenshot from SM59. Is this the one you are talking about? Where would the unicode setting in JCo that similar to SAP?  Unicode and Encoding are different I presume but I don't see an encode option. I could only run the Connection Test and it works fine but I couldn't run the Unicode test in SM59. I will have to reach out to BASIS to run the Unicode TEST. Should that be running successfully? 

Hi Vamsi,

which encoding is used in SAP system?

Perhaps you have to align the outbound encoding in the SAP JCo adapter with SAP's encoding.

Also in in SM59 the unicode flag active?

Best regards

Manuel

Hello Manuel,

Thank you for your response. I am attaching the sap3 and JCo logs along with SM58 screenshot. One other note if it matters, if we are using the existing system's program ID the idoc comes through but this issue with the new program ID. The existing program ID is connected to GENTRAN server for Unix. BASIS confirmed that the new program ID is registered. They see our SI IP hitting their server in their logs.

Best Regards,

Vamsi. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

Thank you. I will try that, but would that give a java longtime error? 

Hi Vamsi,

these are just guesses as I have seen in the trace that the EDIDC40 control segment contains non ANSII characters.

From my point of view you have to change in SM59 to Unicode in your screenshot and test it.

Best regards

Manuel

Hello Manuel,

Am attaching the screenshot from SM59. Is this the one you are talking about? Where would the unicode setting in JCo that similar to SAP?  Unicode and Encoding are different I presume but I don't see an encode option. I could only run the Connection Test and it works fine but I couldn't run the Unicode test in SM59. I will have to reach out to BASIS to run the Unicode TEST. Should that be running successfully? 

Hi Vamsi,

which encoding is used in SAP system?

Perhaps you have to align the outbound encoding in the SAP JCo adapter with SAP's encoding.

Also in in SM59 the unicode flag active?

Best regards

Manuel

Hello Manuel,

Thank you for your response. I am attaching the sap3 and JCo logs along with SM58 screenshot. One other note if it matters, if we are using the existing system's program ID the idoc comes through but this issue with the new program ID. The existing program ID is connected to GENTRAN server for Unix. BASIS confirmed that the new program ID is registered. They see our SI IP hitting their server in their logs.

Best Regards,

Vamsi. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

If you look at the trace the runtime error is caused by a method from the Calendar object.

Perhaps the characters in the EDIDC40 segments are moving the offset. But as I said, just guessing :-)

Same function is also mentioned on the IBM site, where the issue was with DNS resolution and then they had to use IP adresses in the JCo adapter.

So if the unicode switch does not work,  I would recomment to open a case for the IBM support.

Thank you. I will try that, but would that give a java longtime error? 

Hi Vamsi,

these are just guesses as I have seen in the trace that the EDIDC40 control segment contains non ANSII characters.

From my point of view you have to change in SM59 to Unicode in your screenshot and test it.

Best regards

Manuel

Hello Manuel,

Am attaching the screenshot from SM59. Is this the one you are talking about? Where would the unicode setting in JCo that similar to SAP?  Unicode and Encoding are different I presume but I don't see an encode option. I could only run the Connection Test and it works fine but I couldn't run the Unicode test in SM59. I will have to reach out to BASIS to run the Unicode TEST. Should that be running successfully? 

Hi Vamsi,

which encoding is used in SAP system?

Perhaps you have to align the outbound encoding in the SAP JCo adapter with SAP's encoding.

Also in in SM59 the unicode flag active?

Best regards

Manuel

Hello Manuel,

Thank you for your response. I am attaching the sap3 and JCo logs along with SM58 screenshot. One other note if it matters, if we are using the existing system's program ID the idoc comes through but this issue with the new program ID. The existing program ID is connected to GENTRAN server for Unix. BASIS confirmed that the new program ID is registered. They see our SI IP hitting their server in their logs.

Best Regards,

Vamsi. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

Yes. That calendar object was confusing, and we used the IP Address instead of the SAP message Server and still the same error. I sincerely hope the Unicode change works. 

If you look at the trace the runtime error is caused by a method from the Calendar object.

Perhaps the characters in the EDIDC40 segments are moving the offset. But as I said, just guessing :-)

Same function is also mentioned on the IBM site, where the issue was with DNS resolution and then they had to use IP adresses in the JCo adapter.

So if the unicode switch does not work,  I would recomment to open a case for the IBM support.

Thank you. I will try that, but would that give a java longtime error? 

Hi Vamsi,

these are just guesses as I have seen in the trace that the EDIDC40 control segment contains non ANSII characters.

From my point of view you have to change in SM59 to Unicode in your screenshot and test it.

Best regards

Manuel

Hello Manuel,

Am attaching the screenshot from SM59. Is this the one you are talking about? Where would the unicode setting in JCo that similar to SAP?  Unicode and Encoding are different I presume but I don't see an encode option. I could only run the Connection Test and it works fine but I couldn't run the Unicode test in SM59. I will have to reach out to BASIS to run the Unicode TEST. Should that be running successfully? 

Hi Vamsi,

which encoding is used in SAP system?

Perhaps you have to align the outbound encoding in the SAP JCo adapter with SAP's encoding.

Also in in SM59 the unicode flag active?

Best regards

Manuel

Hello Manuel,

Thank you for your response. I am attaching the sap3 and JCo logs along with SM58 screenshot. One other note if it matters, if we are using the existing system's program ID the idoc comes through but this issue with the new program ID. The existing program ID is connected to GENTRAN server for Unix. BASIS confirmed that the new program ID is registered. They see our SI IP hitting their server in their logs.

Best Regards,

Vamsi. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

Manuel,

Looks like the Unicode change worked. Look at the screenshot attached. I did not see a JAVA error in SAP, and it looks like it kicked off some BPs. We are still trying to validate if these BP errors are legitimate and outside of the connection issue we were having. We are all new to this SI here. 

Yes. That calendar object was confusing, and we used the IP Address instead of the SAP message Server and still the same error. I sincerely hope the Unicode change works. 

If you look at the trace the runtime error is caused by a method from the Calendar object.

Perhaps the characters in the EDIDC40 segments are moving the offset. But as I said, just guessing :-)

Same function is also mentioned on the IBM site, where the issue was with DNS resolution and then they had to use IP adresses in the JCo adapter.

So if the unicode switch does not work,  I would recomment to open a case for the IBM support.

Thank you. I will try that, but would that give a java longtime error? 

Hi Vamsi,

these are just guesses as I have seen in the trace that the EDIDC40 control segment contains non ANSII characters.

From my point of view you have to change in SM59 to Unicode in your screenshot and test it.

Best regards

Manuel

Hello Manuel,

Am attaching the screenshot from SM59. Is this the one you are talking about? Where would the unicode setting in JCo that similar to SAP?  Unicode and Encoding are different I presume but I don't see an encode option. I could only run the Connection Test and it works fine but I couldn't run the Unicode test in SM59. I will have to reach out to BASIS to run the Unicode TEST. Should that be running successfully? 

Hi Vamsi,

which encoding is used in SAP system?

Perhaps you have to align the outbound encoding in the SAP JCo adapter with SAP's encoding.

Also in in SM59 the unicode flag active?

Best regards

Manuel

Hello Manuel,

Thank you for your response. I am attaching the sap3 and JCo logs along with SM58 screenshot. One other note if it matters, if we are using the existing system's program ID the idoc comes through but this issue with the new program ID. The existing program ID is connected to GENTRAN server for Unix. BASIS confirmed that the new program ID is registered. They see our SI IP hitting their server in their logs.

Best Regards,

Vamsi. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

Yes, looks like the connection is ok and now you can dig deep into the business processing world :-) Have fun.

Manuel,

Looks like the Unicode change worked. Look at the screenshot attached. I did not see a JAVA error in SAP, and it looks like it kicked off some BPs. We are still trying to validate if these BP errors are legitimate and outside of the connection issue we were having. We are all new to this SI here. 

Yes. That calendar object was confusing, and we used the IP Address instead of the SAP message Server and still the same error. I sincerely hope the Unicode change works. 

If you look at the trace the runtime error is caused by a method from the Calendar object.

Perhaps the characters in the EDIDC40 segments are moving the offset. But as I said, just guessing :-)

Same function is also mentioned on the IBM site, where the issue was with DNS resolution and then they had to use IP adresses in the JCo adapter.

So if the unicode switch does not work,  I would recomment to open a case for the IBM support.

Thank you. I will try that, but would that give a java longtime error? 

Hi Vamsi,

these are just guesses as I have seen in the trace that the EDIDC40 control segment contains non ANSII characters.

From my point of view you have to change in SM59 to Unicode in your screenshot and test it.

Best regards

Manuel

Hello Manuel,

Am attaching the screenshot from SM59. Is this the one you are talking about? Where would the unicode setting in JCo that similar to SAP?  Unicode and Encoding are different I presume but I don't see an encode option. I could only run the Connection Test and it works fine but I couldn't run the Unicode test in SM59. I will have to reach out to BASIS to run the Unicode TEST. Should that be running successfully? 

Hi Vamsi,

which encoding is used in SAP system?

Perhaps you have to align the outbound encoding in the SAP JCo adapter with SAP's encoding.

Also in in SM59 the unicode flag active?

Best regards

Manuel

Hello Manuel,

Thank you for your response. I am attaching the sap3 and JCo logs along with SM58 screenshot. One other note if it matters, if we are using the existing system's program ID the idoc comes through but this issue with the new program ID. The existing program ID is connected to GENTRAN server for Unix. BASIS confirmed that the new program ID is registered. They see our SI IP hitting their server in their logs.

Best Regards,

Vamsi. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

Yes, looks like the connection is ok and now you can dig deep into the business processing world :-) Have fun.

Manuel,

Looks like the Unicode change worked. Look at the screenshot attached. I did not see a JAVA error in SAP, and it looks like it kicked off some BPs. We are still trying to validate if these BP errors are legitimate and outside of the connection issue we were having. We are all new to this SI here. 

Yes. That calendar object was confusing, and we used the IP Address instead of the SAP message Server and still the same error. I sincerely hope the Unicode change works. 

If you look at the trace the runtime error is caused by a method from the Calendar object.

Perhaps the characters in the EDIDC40 segments are moving the offset. But as I said, just guessing :-)

Same function is also mentioned on the IBM site, where the issue was with DNS resolution and then they had to use IP adresses in the JCo adapter.

So if the unicode switch does not work,  I would recomment to open a case for the IBM support.

Thank you. I will try that, but would that give a java longtime error? 

Hi Vamsi,

these are just guesses as I have seen in the trace that the EDIDC40 control segment contains non ANSII characters.

From my point of view you have to change in SM59 to Unicode in your screenshot and test it.

Best regards

Manuel

Hello Manuel,

Am attaching the screenshot from SM59. Is this the one you are talking about? Where would the unicode setting in JCo that similar to SAP?  Unicode and Encoding are different I presume but I don't see an encode option. I could only run the Connection Test and it works fine but I couldn't run the Unicode test in SM59. I will have to reach out to BASIS to run the Unicode TEST. Should that be running successfully? 

Hi Vamsi,

which encoding is used in SAP system?

Perhaps you have to align the outbound encoding in the SAP JCo adapter with SAP's encoding.

Also in in SM59 the unicode flag active?

Best regards

Manuel

Hello Manuel,

Thank you for your response. I am attaching the sap3 and JCo logs along with SM58 screenshot. One other note if it matters, if we are using the existing system's program ID the idoc comes through but this issue with the new program ID. The existing program ID is connected to GENTRAN server for Unix. BASIS confirmed that the new program ID is registered. They see our SI IP hitting their server in their logs.

Best Regards,

Vamsi. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated. 

Hi Manuel,

I can't thank you enough for your help with the Unicode issue! Before I post a new thread in the community, I wanted to check with you about another problem we're facing. During our regression testing, we took the SI App offline and attempted to push an IDoc from SAP. I expected the IDoc to go into Status 02, indicating the destination port or app was unavailable. However, it went into Status 03, as if everything downstream was functioning, even though SI was down.

Could you help me understand what's happening, where the IDoc might be going, and how to track these IDocs if the app goes down for real? Any assistance would be greatly appreciated.

Thanks again!

Yes, looks like the connection is ok and now you can dig deep into the business processing world :-) Have fun.

Manuel,

Looks like the Unicode change worked. Look at the screenshot attached. I did not see a JAVA error in SAP, and it looks like it kicked off some BPs. We are still trying to validate if these BP errors are legitimate and outside of the connection issue we were having. We are all new to this SI here. 

Yes. That calendar object was confusing, and we used the IP Address instead of the SAP message Server and still the same error. I sincerely hope the Unicode change works. 

If you look at the trace the runtime error is caused by a method from the Calendar object.

Perhaps the characters in the EDIDC40 segments are moving the offset. But as I said, just guessing :-)

Same function is also mentioned on the IBM site, where the issue was with DNS resolution and then they had to use IP adresses in the JCo adapter.

So if the unicode switch does not work,  I would recomment to open a case for the IBM support.

Thank you. I will try that, but would that give a java longtime error? 

Hi Vamsi,

these are just guesses as I have seen in the trace that the EDIDC40 control segment contains non ANSII characters.

From my point of view you have to change in SM59 to Unicode in your screenshot and test it.

Best regards

Manuel

Hello Manuel,

Am attaching the screenshot from SM59. Is this the one you are talking about? Where would the unicode setting in JCo that similar to SAP?  Unicode and Encoding are different I presume but I don't see an encode option. I could only run the Connection Test and it works fine but I couldn't run the Unicode test in SM59. I will have to reach out to BASIS to run the Unicode TEST. Should that be running successfully? 

Hi Vamsi,

which encoding is used in SAP system?

Perhaps you have to align the outbound encoding in the SAP JCo adapter with SAP's encoding.

Also in in SM59 the unicode flag active?

Best regards

Manuel

Hello Manuel,

Thank you for your response. I am attaching the sap3 and JCo logs along with SM58 screenshot. One other note if it matters, if we are using the existing system's program ID the idoc comes through but this issue with the new program ID. The existing program ID is connected to GENTRAN server for Unix. BASIS confirmed that the new program ID is registered. They see our SI IP hitting their server in their logs.

Best Regards,

Vamsi. 

Hello Vamsi,

I guess you see the Runtime Exception in SM58?

Can you share the sap3.log entries created when you try to send the idoc?

Best regards

Manuel

Hello Community, I hope everyone is doing well.  

We are setting up SI for the first time and in that process creating a new ALE port in SAP with the new program ID and everything. The connection in SM59 works great for the new RFC destination and SAP is able to see SI's IP address but when we run an idoc from SAP to SI we are getting a java.lang.RuntimeException error in SAP and SAP logs in SI shows some RFC error. What could be going on here? We tried both transfer protocols in the RFC Destination tRFC and BGRFC but still nothing.  We made sure the new program ID is registered in SAP and all the parameters entered in JCo are validated. 

ANy help is greatly appreciated.