JR48601: ABAP STAGE DOES NOT HANDLE RFC DESTINATION CREATION ERRORS CORRECTLY

APAR status

• Closed as fixed if next.

Error description

• ABAP RFC data transfer: when the RFC destination registration
  fails the ABAP stage just continues to wait for data, although
  there is no connection. It should abort instead.
  

Local fix

• Uncomment lines 568 and 570 in Z_RFC_DS_SERVICE (554 and 555 for
  Z_RFC_DS_SERVICE_CTS) by removing the leading asterisks. The
  code fragment should look like this:
  
     IF SY-SUBRC <> 0.
       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
     ENDIF.
  

Problem summary

• ABAP RFC data transfer: when the RFC destination registration
  fails the ABAP stage just continues to wait for data, although
  there is no connection. It should abort instead.
  

Problem conclusion

Temporary fix

• Uncomment lines 568 and 570 in Z_RFC_DS_SERVICE (554 and 555 for
  Z_RFC_DS_SERVICE_CTS) by removing the leading asterisks. The
  code fragment should look like this:
  
  IF SY-SUBRC <> 0.
  MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
  WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
  ENDIF.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R700 PSY

     UP