In SAP note 1230076 “Generation of ABAP loads: Tips for the analysis”, a tool report RSDEPEND is introduced.
It is explained in the note “An ABAP program generally depends on many other repository objects. If an object like this changes (for example, an include or a DDIC type), the load of all dependent programs must be invalidated. The load of these programs is then regenerated with the next use, and valid loads are generated again.”
In order to demonstrate the ABAP load invalidation logic, I create a very simple database table ZCRMM_CCTV_CHAL and write a simple report ZTESTLOAD to fetch all its data:
The execution result of RSDEPEND report:
a. The timestamp of ABAP load and ABAP source of the test report ZTESTLOAD remain unchanged;
b. The timestamp “last changed” of database table ZCRMM_CCTV_CHAL changed to the time when I change the table description;
c. The ABAP timestamp and Screen timestamp of database table ZCRMM_CCTV_CHAL also changed to the time when I change the table description;
(4) Execute the test report ZTESTLOAD
The execution result of RSDEPEND report:
a. The timestamp of ABAP load and ABAP source of the test report ZTESTLOAD remain unchanged;
b. The timestamp “last changed” of database table ZCRMM_CCTV_CHAL changed to the time when I change the table description;
c. The ABAP timestamp and Screen timestamp of database table ZCRMM_CCTV_CHAL also changed to the time when I change the table description;
Further reading
For more detail about ABAP load please read this document SGEN- an Overview.
