SAP CL_ABAP_AAB_UTILITIES OO Class - Auxiliary Methods for Activatable Assertions/Breakpoints
CL_ABAP_AAB_UTILITIES is a standard SAP object class available within R/3 SAP systems depending on your version and release level. You can view/maintain the class details by entering its name into the relevant SAP transactions such as SE24, SE80 or even SE84. Below is the documentation available for class CL_ABAP_AAB_UTILITIES including details of:
- Interface class implementations
- Inheritance details
- Methods defined within class ( including link to full details )
- Attributes ( including initial values )
- Class Events
Method list of CL_ABAP_AAB_UTILITIES SAP class
A method is a coding block that performs a certain procedure (i.e. ABAP functionality) on an object within the overall SAP class. In simple terms if the object is an SAP database table a method could be the procedure to add a record or to delete a record. If you are new to OO in many respects, the implementation of a method is similar to a function module and can be called in a very similar way using CALL METHOD.
Instead of "CALL FUNCTION", Methods are referenced using the following syntax: CALL METHOD =>methodname EXPORTING/IMPORTING...
| Method Name | Description | Visability |
| CONVERT_ID_TO_INCLUDE | (Only for Internal Use) | Public |
| CALL METHOD cl_abap_aab_utilities=>CONVERT_ID_TO_INCLUDE...more details | ||
| GET_KEY | (Only for Internal Use) | Public |
| CALL METHOD cl_abap_aab_utilities=>GET_KEY...more details | ||
| IS_ACTIVE | Query Activation State for Checkpoint Group | Public |
| CALL METHOD cl_abap_aab_utilities=>IS_ACTIVE...more details | ||
| STORE_CHAR_MESSAGE | Format Character String Message as FIELD | Public |
| CALL METHOD cl_abap_aab_utilities=>STORE_CHAR_MESSAGE...more details | ||
| STORE_T100_MESSAGE | Format T100 Message as FIELD | Public |
| CALL METHOD cl_abap_aab_utilities=>STORE_T100_MESSAGE...more details | ||
CL_ABAP_AAB_UTILITIES attributes
List of attributes within class CL_ABAP_CHAR_UTILITIES. These can be referenced using the following syntax CL_ABAP_CHAR_UTILITIES=>. Although depending on where you are inserting the ABAP code you do need to check if the attribute is public or private.
| Name | Level | Description | Initial Value | Type | Visability |
| BITMASK_ASSERT_ABORT | Constant | Assert: Cancel | 40 | LIKE X | Public |
| BITMASK_ASSERT_ABORT_BTC | Constant | Assert: Cancel in Background | 32 | LIKE X | Public |
| BITMASK_ASSERT_ABORT_DIA | Constant | Assert: Cancel in Dialog | 8 | LIKE X | Public |
| BITMASK_ASSERT_ANY | Constant | Assert: Active | 62 | LIKE X | Public |
| BITMASK_ASSERT_BREAKABORT | Constant | Assert: Stop in Dialog, Cancel in Background | 34 | LIKE X | Public |
| BITMASK_ASSERT_BREAKLOG | Constant | Assert: Stop in Dialog, Log in Background | 18 | LIKE X | Public |
| BITMASK_ASSERT_BREAK_DIA | Constant | Assert: Stop | 2 | LIKE X | Public |
| BITMASK_ASSERT_LOG | Constant | Assert: Log | 20 | LIKE X | Public |
| BITMASK_ASSERT_LOG_BTC | Constant | Assert: Log in Background | 16 | LIKE X | Public |
| BITMASK_ASSERT_LOG_DIA | Constant | Assert: Log Dialog | 4 | LIKE X | Public |
| BITMASK_BREAKPOINT | Constant | Breakpoint: Stop | 1 | LIKE X | Public |
| BITMASK_LOGPOINT | Constant | Logpoint: Log | 64 | LIKE X | Public |
| CATEGORY_ERROR | Constant | Message Type: Error | 'E' | LIKE SYMSGTY | Public |
| CATEGORY_INFO | Constant | Message Type: Information | 'I' | LIKE SYMSGTY | Public |
| CATEGORY_WARNING | Constant | Message Type: Warning | 'W' | LIKE SYMSGTY | Public |
| KIND_CHAR | Constant | Internal usage | 63 | LIKE I | Public |
| KIND_T100 | Constant | Internal usage | 127 | LIKE I | Public |
Links to Related Class(s)
CL_ABAP_...Full list of available SAP object classes
Search for further information about these or an SAP related objects