SAP ABAP Data Element SATC_CI_EXEMPTION_FLAGS (Options for an exemption)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DWB-TOO-ATF (Application Component) ABAP Test Frameworks ( ATC, CheckMan, Code Inspector)
     ⤷ SATC_CI_DDIC_TYPES (Package) INTERNAL: - *NO* REUSE - "Code Inspector" types
Basic Data
Data Element SATC_CI_EXEMPTION_FLAGS
Short Description Options for an exemption  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type SAP_BOOL    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Exmp. Set. 
Medium 15 Exmpt. Setting 
Long 20 Exemption Setting 
Heading 25 Exemption Setting 
Supplementary Documentation - SATC_CI_EXEMPTION_FLAGS0000

Restrict Scope of the Exemption to Single Finding

This option specifies that an exemption is only valid for a certain finding. Other findings of the same check on the same object are not covered by such an exemption.

The meta data of a check defines whether this option is available or even mandatory. In case of mandatory granularity per finding it is not possible to specify the validity for the complete object or all message codes of a check.

Please note the identity of an exemption and a finding consists of the key for the object, the key for the check message code plus a checksum. This checksum is computed by the check and can be used for reference purposes only.

Supplementary Documentation - SATC_CI_EXEMPTION_FLAGS0001

Scope of the Exemption with Respect to Repository Objects

With these options, you can decide how broadly the exemption that you are requesting should be applied, with respect to repository development objects.

Your choices for the scope of the exemption are as follows:

  • This Sub-Object: If you choose this option, then the exemption, if it is granted, will apply only to occurrences of the check message in the sub-component listed in the Include field.

    This is the most restricted scope for an exemption.

    Example: You have three findings for check message Table ...: No WHERE Condition in Include LFUGRU03.

    If you request an exemption with scope Sub-Object, then all three of your No WHERE Condition findings in this include will be exempted and will disappear from the list of ATC findings. But findings with this check message in other includes and programs will not be affected by the exemption.

    Note that this option is not displayed if the repository object does not have any sub-components.

  • This Object: With this option, you can request an exemption for all findings with this check message in an entire repository object.

    Example: You have a program with six findings for check messageTable ...: No WHERE Condition in two separate includes.

    If you request an exemption with the scope This Object, then the exemption, if granted, will exempt all six findings - all findings for the entire program.

  • This Package: With this option, you can request an exemption for all findings with this check message for all repository objects in the package that is shown in the Package field.

    This is the broadest type of exemption that you can request. Do not request this scope if there other developers working in the same package; your exemption would exempt ATC findings for the other developers as well.

    Example: You have 12 findings for check message Table ...: No WHERE Condition, distributed across several programs in your development package.

    If you request an exemption for one of these findings and choose the option This Package, then all 12 findings will be exempted if your request is approved. All findings with this check message in the entire package are masked by the exemption, if it is approved.

Note that you can separately determine whether your exemption request applies only to the check message shown in the Check Message field or to all findings produced by the check, as shown in the Check field.

Be aware the exemptions are not restricted to your user; they affect other users who are working within the same scope. For example, if you and several colleagues are working on function modules in a function group, then requesting an exemption for This Object exempts ATC findings not only for your function module, but for those of your colleagues as well. Limit the scope of your exemption requests as much as you can.

Supplementary Documentation - SATC_CI_EXEMPTION_FLAGS0002

Check Restriction

With these options, you can decide on the scope of your exemption request with respect to the findings produced by the ATC check.

You can choose from these options:

  • This Check Message: If you choose this option, then the exemption - if approved - applies only to findings with this check message, as shown in the Check Message field.
  • This Check: With this option, you can request an exemption that applies to all findings produced by the check shown in the Check field.

    This option lets you, in effect, turn off the ATC check completely. Be aware that the exemption applies not only to you, but to all other users as well, within the repository object scope that you defined.

Example

Assume that you have three findings for check message Table ...: No WHERE Condition in your function module. Assume also that you limited the scope of your exemption to This Sub-Object, that is, your function module.

If you ask for the exemption to be valid for This Check Message, then your three Table... findings will be exempted and will be removed from the list of open findings. Any similar findings in the separate function modules of your colleagues will not be affected.

If you ask for the exemption to be valid for This Check, then your three Table... findings and any other findings produced by this database performance check will be exempted. Again, findings that pertain to your colleagues in separate function modules will not be affected.

If, however, you had chosen as the repository object scope This Package, then you would turn off this performance check for all repository objects of all developers in the package shown in this screen. Always limit the scope of your exemptions as much as you can.

Supplementary Documentation - SATC_CI_EXEMPTION_FLAGS0003

Notification

With these options, you can decide if you want to be informed about the state of your request:

  • Have a mail sent to you if the request is rejected
  • Have a mail sent to you if the request is approved or rejected
  • You do not want to be informed at all about the request.

History
Last changed by/on SAP  20140117 
SAP Release Created in 732