CX_INM_M_DB_DELETE 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 CX_INM_M_DB_DELETE including details of:
Also check out the Resources section below to view useful tips, screenshots, links and general information related to this SAP class and its methods, or even add your own for future reference.
This OO class has a superclass assigned to it, which means it will inherit its objects and methods. The superclass for CX_INM_M_DB_DELETE is CX_ACO_DB
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 CL_ABAP_CHAR_UTILITIES=>methodname EXPORTING/IMPORTING...
List of attributes within class CX_INM_M_DB_DELETE. These can be referenced using the following syntax CX_INM_M_DB_DELETE=>
|CX_INM_M_DB_DELETE||Cx Inm M Db Delete||'882D1FDEE121764DBD06BB23FA58A0B9'|
Events are created within your class using special event handler methods. These must be registered at runtime for the event and can then be triggered using the ABAP syntax: RAISE EVENT
CX_INM_M_DB_DELETE - Error During Data Access (Delete) CX_INM_BOE_CONNECTION - BOE Exception Class CX_INM_BOE_AUTH - BOE Authorization Exception CX_INDEX_TOO_LOW - Index for table access cannot be less than one CX_INCLUDE_DOES_NOT_EXIST - exception class used in CL_OO_CLIF_SOURCE CX_IM_SE_CHECK - General checks in XI proxies for IM