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

Code inspector - how can I create approval for exceptions?

marcin_cholewczuk
Active Contributor
0 Likes
1,122

Hi Gurus,

I've a question regarding this functionality. How can use approval/rejection of exceptions in Code Inspector? On main screen there is possibility to view list of it (Goto->Exceptions->Approve/Requested), but I don't know how can I create entry that will be shown here. I've tried to look on page with results of check, but without success. I know that these data are storred in table SCIEXCEPTN_APPL, but nothing more.

I would appreciate any help

B.R.

Marcin Cholewczuk

1 ACCEPTED SOLUTION
Read only

former_member184455
Active Participant
0 Likes
764

Dear Mr. Cholewczuk,

Currently the type of exception that suppresses a check message in the Code Inspector is hard-coded inside each check and cannot be configured. Most messages in program-like objects can be suppressed by a pseudo-comment; only some check messages of one of the security checks demand a table based exception.

You can find this check in transaction SCI --> Goto --> Management of --> Message Priorities. Open the 'Security Checks' category, and then the check 'Critical Statements'.

The check messages for

  • Write/delete a report/text pool

  • Write/Read Screen

  • Write NAMETAB

have the value 'Table Entry' in column 'Exception'. Therefore those messages can only be suppressed by a table based exception.

So if you check some program that uses these language elements, you will find an icon in the Code Inspector check result tree next to the message. Clicking the icon gives you a pop-up where the table based exception can be defined. The person you entered as approver of the exception will find it in the SCI 'Approver Inbox' you mentioned above.

In a self-defined check, specify the pseudo-comment in the constructor of the check class as

CL_CI_TEST_ROOT=>C_EXCEPTN_BY_TABLE_ENTRY. This will then be handled as a table based exception.

Best Regards,

Randolf Eilenberger

3 REPLIES 3
Read only

former_member184455
Active Participant
0 Likes
765

Dear Mr. Cholewczuk,

Currently the type of exception that suppresses a check message in the Code Inspector is hard-coded inside each check and cannot be configured. Most messages in program-like objects can be suppressed by a pseudo-comment; only some check messages of one of the security checks demand a table based exception.

You can find this check in transaction SCI --> Goto --> Management of --> Message Priorities. Open the 'Security Checks' category, and then the check 'Critical Statements'.

The check messages for

  • Write/delete a report/text pool

  • Write/Read Screen

  • Write NAMETAB

have the value 'Table Entry' in column 'Exception'. Therefore those messages can only be suppressed by a table based exception.

So if you check some program that uses these language elements, you will find an icon in the Code Inspector check result tree next to the message. Clicking the icon gives you a pop-up where the table based exception can be defined. The person you entered as approver of the exception will find it in the SCI 'Approver Inbox' you mentioned above.

In a self-defined check, specify the pseudo-comment in the constructor of the check class as

CL_CI_TEST_ROOT=>C_EXCEPTN_BY_TABLE_ENTRY. This will then be handled as a table based exception.

Best Regards,

Randolf Eilenberger

Read only

0 Likes
764

Hello,

I found this thread only very late, but hope you`re still around:)) I would like to know how can I change existing SCI checks from their current masking status to this one needing an approval. That means more work in the approval area, but also tightens the security, which is something customers often ask. Can that be done? I mean without heavily changing the standard SCI delivery.

Any ideas highly appreciated.

Thanks for the initial pointer,

cheers Otto

Read only

0 Likes
764

Hi Otto,

You could try to create your own classes that woud inheritate from SAP standard check classes and use them instead - maybe it is possible to change mentioned settings in your own coding.

Best Regards

Marcin Cholewczuk