Hierarchy
⤷
⤷
Basic Data
| Data Element | CRMCHKCLS_ANALYSIS |
| Short Description | Analysis runtime class (IF_CRM_OBJECT_CHECKER) |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| 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 | Analysis |
| Medium | 15 | Analysis class |
| Long | 20 | Analysis class |
| Heading | 25 | Analysis Class |
Documentation
Definition
Class that implements IF_CRM_OBJECT_CHECKER which is the API from a CheckMan check plug-in towards the framework. Typically implementing classes invoke some technical analysis and use the result API CL_CRM_CHK_RESULT_NEW to report any issues on the objects analyzed.
Use
Please note that the successor of CheckMan the ATC still requires a CheckMan plug-in. Additionally ATC (in SAPs CheckMan Mode) requires a further adapter class. This multitier architecture is basically a compromise for backward compability.
Dependencies
Please note CheckMan plug-in requires additional meta data maintained in the following tables:
CRMCHK (mandatory)
CRMCHKOBTY (mandatory)
CRMCHKMSG (mandatory)
CRMCHKMSGP (optional, recommended not to use)
Do never transport entries in these tables directely (LIMU TABU). Please always use the SCRM_TRANSPORT_CHECK!
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 740 |