Custom analysis types can be created by customers to complement the standard-out-of-the-box ShiftLeft analyzers. In order to do this, entries must be maintained in the following tables:
| Table | Usage |
|---|---|
| /BTI/TE_ANLTYPE | Lists all the analysis types currently available within ActiveControl |
| /BTI/TE_ANLTYPEP | Contains all the analysis type parameters. These are only required for the types that need them |
| /BTI/TE_ANTYPEPT | Analysis parameter types: 01 BOOL TRUE or FALSE 02 COMBO Combination 03 COMBOLIST Combination list 04 DATE Date value 05 STRING String value 06 MEMO Multi-line 07 NUMERIC Numeric value |
| /BTI/TE_ANREASON | Lists all the analysis error reason codes |
| /BTI/TE_ANREAS_P | Configuration used to control the approval / import anyway functionality. This is stored by Reason, Analysis type, Target and Location. • If the Analysis type is blank the config applies to all analysis types • If the Target is blank or 9999 the config applies to all targets • If the Location type is blank the config applies to all locations |
| /BTI/TE_ANRELINK | Used to link the error reason codes to the relevant analysis types |
To implement an analysis type one of the standard ShiftLeft analysis function modules should be copied to a Z version so the framework and parameters can be copied and utilised. The recommendation is to copy function module /BTI/TE_ANALYSIS_CHECKDATE as this FM utilises analysis parameters and custom field processing both of which are likely to be required in most custom analysis types.
It is recommended to number any custom analysis types and reason codes starting with a ‘9’ to distinguish them from standard ones and to prevent them from being overwritten during upgrades. E.g. 9001
Once the table entries and function module are available, they will appear for use within the ActiveControl configuration alongside the standard ShiftLeft analysers.
Post your comment on this topic.