In transaction SCI it is possible to setup Code Inspector variants to perform security checks on SAP programs. These can be setup as General variants for all users or user specific ones. Dev Enforcer: Security (0004) hooks into these variants to perform the check as part of the Analysis/Approval process within ActiveControl.

Parameters:

Parameter Description
CIEXCL_EXISTING_ISSUES Can be used to display the Code Inspector results in following modes:
LIST_ALL – All the CI issues that have been existing will be listed
LIST_BOTH_SEP – issues that have been existing and issues that are introduced with the current transport will be displayed with separate section.
LIST_NEW – Only issues that are introduced with the current transport will be displayed.
CIIGNORE_WARNING_INFO EXCLUDE_BOTH: Exclude both Informational and Warning messages from DevEnforcer results. Only Errors will be reported.
EXCLUDE_INFO: Exclude only Informational messages. Warning and Error messages will be reported.
EXCLUDE_WARNING: Exclude only Warning messages. Information and Errors messages ill be reported.
CIREFSID SID of where the TR is to be imported. Typically, this is not required to be configured.
CISID SAP System ID for Execution. Specify the system ID (e.g. D01) where the Code Inspector variant is to be run from.
CITARGET Target System for Execution if CISID is not specified. Specify the target system ID (e.g. 0001) where the Code Inspector variant is to be run from.
CIUSER Code Inspector Execution User. Leave blank for global variants.
CIVARIANT Code Inspector Variant name.
IGNORE_EXTERNAL_TRANSPORTS Can be used to exclude external transports from the analysis results.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment