Pieter Rijlaarsdam
Read all my blogsI have been around for a while, working with SAP and debugging quite considerable amounts of coding.
There was one piece I never really understood, but always took for granted, which is the statement ‘Destination None’ after a call function. Destination None sound a little like the road to nowhere…
When working with SAP ABAP, you have several options for building up your coding and calling other pieces of coding, such as ‘Submit, Call Method, Call Transaction, Call Function, call-ICT, call transformation, perform etc.
Some are old, some are new, some are good, some are not.
Personally, I prefer an object oriented approach, and definitely dislike call transaction and submit. But maybe that’s just taste, and sometimes, you just have to use what SAP has delivered.
So in the end, we can use a mix of calls, procedures, methods and functions to eventually get to Rome.
Of course, the different roads have different features, which can be used to the programmers benefit. For instance, ‘Call function’ has some features that can come in handy.
Some background on functions in ABAP.
We probably all know that you can call remote functions directly. Basically, calling a remote function allows you to step synchronously to another system, perform a function there, and get back.
CALL FUNCTION func DESTINATION dest
parameter_list.
That’s an easy one. The function will be called in the system specified by parameter ‘dest’.
CALL FUNCTION func STARTING NEW TASK task
[DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
[{PERFORMING subr}|{CALLING meth} ON END OF TASK]
parameter_list.
This one is a little more expert… This is the asynchronous brother of the first option, where ‘dest’ again is the system the function will be called in.