ABAP News for Release 7.50 – Dynamic RFC Destinations
Up to now, there was no officially released or documented possibility to create a fully fledged dynamic RFC destination that can be entered behind CALL FUNCTION DESTINATION.
If you crawl the Web for “dynamic RFC destination”, you find one or the other hint how to achieve that, but the general recommendation is: Don’t do that!
In order to direct that uncontrolled growth into the right channels, a new class is delivered with ABAP 7.50:
DATA(dest) =
cl_dynamic_destination=>create_rfc_destination(
logon_client = …
logon_user = …
logon_language = …
sid = …
server = …
group = …
… ).
CALL FUNCTION ‘DEMO_RFM_PARAMETERS’
DESTINATION dest
EXPORTING …
From ABAP 7.50 on, CL_DYNAMIC_DESTINATION is the officially released and documented possibility to create a dynamic RFC destination and the only one to be used if SM59 is not sufficient.
Good notes. Thanks for update new things!
Hi Horst,
Could you please comment about the future of ABAP in the s4/hana roadmap based SAP world.
Regards,
See NetWeaver AS for ABAP 7.5 - One ABAP Platform for SAP Business Suite and SAP S/4HANA, on-premise edition orSAP NetWeaver 7.5 - One common foundation for SAP Business Suite and SAP S/4HANA, on-premise edition .
A general question is there any way that in future we see a ABAP runtime on HCP allowing ABAP on public s4/hana clouds. also any work on classical screens to allow for screen personas like and in fiori style outputs or it's going to be ui5 and abap mix in future?
Thanks! Very helpful
More flexible