SAP ABAP報表依賴設計原理詳解
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:
data: lt_table type STANDARD TABLE OF ZCRMM_CCTV_CHAL.select * INTO TABLE lt_table FROM ZCRMM_CCTV_CHAL.
(1) Create and activate the test report for the first time
Execute report RSDEPEND with ZTESTLOAD as program name = ZTESTLOAD. it returns the result as below. In the first part we see the timestamp of ABAP load and ABAP source are both initial one when I activate the report. In the second part we see our simple report has many dependencies on system includes like and . Those system includes are automatically inserted into the test program I have created, it is not necessary for application developers to manually include them, or else there would be compilation errors:
In the third part “Dependencies of Dictionary Types”, we found the depended database table which was initially created on 10.21 in year 2013.
(2) only change the depended database table description
Re-run 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 remain unchanged;
(3) Add a new column to database table
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.
要獲取更多Jerry的原創文章,請關注公眾號"汪子熙":
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/24475491/viewspace-2712492/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- SAP 電商雲 Spartacus UI DeliveryComponent 的依賴設計UI
- 設計模式例項講解 - 依賴倒置設計模式
- 「轉」Laravel 依賴注入原理(詳細註釋)Laravel依賴注入
- Dependency Injection-依賴注入詳解依賴注入
- Maven依賴中的scope詳解Maven
- Maven依賴scope範圍詳解Maven
- Angular 依賴注入原理Angular依賴注入
- Java程式設計師必須掌握的Spring依賴管理原理Java程式設計師Spring
- Java的Covariance設計原理和SAP ABAP的模擬實現Java
- SpringDI四種依賴注入方式詳解Spring依賴注入
- 理解設計模式及依賴注入設計模式依賴注入
- 詳解 Laravel 中的依賴注入和 IoCLaravel依賴注入
- spring 詳細講解(ioc,依賴注入,aop)Spring依賴注入
- 一文詳解spring迴圈依賴Spring
- 解決eclipse的maven依賴報錯EclipseMaven
- 面向切面程式設計和依賴注入程式設計依賴注入
- 一、.Net Core 依賴注入詳解及Autofac使用依賴注入
- 【穩定性】穩定性建設之依賴設計
- Golang 依賴注入設計哲學|12.6K 🌟 的依賴注入庫 wireGolang依賴注入
- 設計原則-依賴反轉原則
- SAP ABAP 平臺新的程式設計模型程式設計模型
- SAP ABAP資料表的操作
- 併發程式設計 — CAS 原理詳解程式設計
- 依賴注入?依賴注入是如何實現解耦的?依賴注入解耦
- 物件導向程式設計程式碼詳解(依賴關係,關聯關係,組合關係)物件程式設計
- 從原始碼解析vue的響應式原理-依賴收集、依賴觸發原始碼Vue
- 領域驅動設計對依賴的控制
- 設計原則之【依賴反轉原則】
- 詳解.NET依賴注入中物件的建立與“銷燬”依賴注入物件
- SAP官方釋出的ABAP程式設計規範程式設計
- 玩了一下 SAP Fiori ABAP程式設計模型程式設計模型
- Vue原始碼閱讀 – 依賴收集原理Vue原始碼
- Vue原始碼閱讀 - 依賴收集原理Vue原始碼
- golang中的Mutex設計原理詳解(一)GolangMutex
- 雜湊表(雜湊表)原理詳解
- SAP CRM資料庫表CRMD_CUMULAT_H的設計原理資料庫
- 具備自動重新整理功能的 SAP ABAP ALV 報表
- 直播軟體原始碼,pom 依賴遇到 build 下的依賴報錯原始碼UI