ABAP static analysis tool SQF is a static code analysis tool developed in package SUPPORT_QUERY_FRAMEWORK in software component SAP_BASIS.
It contains lots of handy tool or short cut to other system utility tools. The most attractive function which is worthy to put it into my toolset is the static code analysis.
1. use tcode SQF, double click on "Source code Analysis"
2. Maintain the ABAP object which you would like to do static analysis.
In this example it is function module CRM_PRODUCT_GETLIST2. Specify the object type as well, below is the list of possible values.
There is one very disturbing bug when one enters the object, is that the last entered field is ignored if one presses BACK or SAVE immediately. Workaround: press ENTER or TAB so that the value is taken into account.
We may analyze “only” these object types/subobjects (source: method CREATE_FOR_OBJECT of class CL_SRC_ENTITY_ROOT) :
- FUNC <function module>
- PROG <prog> FORM (empty subroutine) : the whole program
- PROG <prog> FORM <subroutine>
- PROG <prog> CLAS <local class>
- FUGR <func group> FORM <subroutine>
- FUGR <func group> CLAS <local class>
- CLAS <class pool>
- CLAS <class pool> METH <method>
- CLAS <class pool> CLAS <local class>
- INTF <interface pool>
- INTF <interface pool> METH <method>
- INTF <interface pool> CLAS <local class>
The Analysis Depth 6 means: for example in the implementation of the FM, it calls another FM or subroutine, these delegated calls will also be analyzed by the tool. Say FM calls A and A calls B, B calls C, C calls D, D calls E, E calls F and F calls G, depth = 6 means any further calls starting from F calls G will be ignored.
3. Click save button and it is automatically navigated back to SQF main view. Click F8 to execute.
The progress will be displayed in the bottom, the bigger size of depth specified, the more time the analysis will take.
After execution, the color of icon changes from white to blue, which means the analysis result is available.
4. The analysis results are categorized into four groups:
a. Call hierarchy, something like the one in SAT.
b. the table read access in static call. Those table read access done via dynamic coding will be listed in group d.
Compare with DB access list analyzed by runtime trace SAT, there are far more entries than the static one. This is not surprising, as in CRM product, the set type access is implemented in a highly dynamic way.
c. interface call:
d. Dynamic coding