Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAP Code Inspector (SCI): checking DDIC objects

ralf_wenzel_heuristika
Active Participant
0 Likes
2,581

Hi, folks.

I want to write a custom check in SCI for DDIC objects (data elements). All examples and tutorials are for developing ABAP code checks but not DDIC objects.

Can someone help me to do this?

Thanks, Ralf

1 ACCEPTED SOLUTION
Read only

former_member184455
Active Participant
1,807

Hi Ralf,

Maybe it helps if you look into class CL_CI_TEST_DDIC_TABLES which is a check for DDIC objects, namely database tables and views. It is quite similar to code checks with the difference, that data preparation (in this case: reading meta data of DDIC tables) is done in the check class itself. To optimize check performance, all objects that shall be checked are collected in the RUN method and the true check is performed in the RUN_END method, reading all the necessary meta data in chunks. But this optimization is not a must (and even could be harmful in the case of checking data elements, since this could be some 100.000 leading to memory problems).

Best Regards, Randolf

2 REPLIES 2
Read only

Jelena_Perfiljeva
Active Contributor
0 Likes
1,807

This blog explains how to create a custom check and it seems that we just create a "new category" and then we can run that new category check with any object. So I'm guessing in general it's the same process for all the object. The code inside the check method would depend on what exactly you want to check for, I guess.

I haven't tried this myself but I see that randolf.eilenberger is still answering questions in the SCI wiki, so maybe he has something to share further on this.

Read only

former_member184455
Active Participant
1,808

Hi Ralf,

Maybe it helps if you look into class CL_CI_TEST_DDIC_TABLES which is a check for DDIC objects, namely database tables and views. It is quite similar to code checks with the difference, that data preparation (in this case: reading meta data of DDIC tables) is done in the check class itself. To optimize check performance, all objects that shall be checked are collected in the RUN method and the true check is performed in the RUN_END method, reading all the necessary meta data in chunks. But this optimization is not a must (and even could be harmful in the case of checking data elements, since this could be some 100.000 leading to memory problems).

Best Regards, Randolf