XO_API_ADAPTER 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 XO_API_ADAPTER 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 an interface implementation which means it has access to all methods within the interface class. Here are the interface classes for XO_API_ADAPTER
This OO class has a superclass assigned to it, which means it will inherit its objects and methods. The superclass for XO_API_ADAPTER is XO_OBJECT
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 XO_API_ADAPTER. These can be referenced using the following syntax XO_API_ADAPTER=>
|CLEANUP_HANDLER_SET||CLEANUP Processor Is Registered|
|MO_CHANGE_DATA_TYPE||Structure Name for Data to Be Changed in MO||'STR_XO_MO_CHANGE_DATA'|
|MY_BO_NAME||Name of Business Object|
|REF_LIST||API Adapter for Each Business Object|
|TESTRUN||Test Run Active/Inactive|
|TESTRUN_SET||Settings Have Been Made for Test Run|
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