• Same as CL_ABAP_BEHAVIOR_SAVER. It is used as base class from which a RAP saver class in an ABAP behavior pool (ABP) inherits.
• Normally, the basic rule is that failures must not occur in the RAP late save phase, but must be detected in the RAP early save phase in order for the save to be successful. The base class CL_ABAP_BEHAVIOR_SAVER_FAILED can be used in exceptional cases where the basic rule cannot be met.
• For more information, see the ABAP Keyword Documentation.

• Explicitly setting transactional phases (the modify and save transactional phase) to enable transactional consistency checks with the controlled SAP LUW (which is an extension of the SAP LUW concept)
• The controlled SAP LUW is automatically and implicitly supported by newer ABAP concepts such as RAP, i.e. the transactional phases are implicitly active when RAP handler methods are called.
• Operations that are not allowed in a transactional phase are detected, resulting in a runtime error in certain contexts (or the violations are logged). For example, database modifications are only allowed in the save transactional phase because the data being processed in the modify phase may be inconsistent. Therefore, a database modification in the modify phase can disrupt the SAP LUW.
• For more information, refer to the chapter Controlled SAP LUW.
• See the restrictions in the ABAP Keyword Documentation: ABAP for Cloud Development / Standard ABAP.

• For an object-oriented representation of regular expressions.
• For example, the CREATE_PCRE method creates instances of regular expressions with PCRE syntax.
• The instances can be used, for example, with the CL_ABAP_MATCHER class, which applies the regular expressions.
• A variety of methods and parameters can be specified to accomplish various things and to further specify the handling of the regular expression.

• getting type information on data objects, data types or instances at runtime (Runtime Type Identification (RTTI)).
• defining and creating new data types as type description objects at runtime (Runtime Type Creation (RTTC)).

CL_ABAP_TYPEDESCR 
  | 
  |--CL_ABAP_DATADESCR 
  |   | 
  |   |--CL_ABAP_ELEMDESCR 
  |   |   | 
  |   |   |--CL_ABAP_ENUMDESCR 
  |   | 
  |   |--CL_ABAP_REFDESCR 
  |   |--CL_ABAP_COMPLEXDESCR 
  |       | 
  |       |--CL_ABAP_STRUCTDESCR 
  |       |--CL_ABAP_TABLEDESCR 
  | 
  |--CL_ABAP_OBJECTDESCR 
     | 
     |--CL_ABAP_CLASSDESCR 
     |--CL_ABAP_INTFDESCR 

• The processing of XML can be done using class libraries such as the Integrated XML Library (iXML) and the Serial XML Library (sXML).
• In iXML, you need input and output streams that are created using iXML methods to access XML data.
• sXML provides XML readers and writers for different sources and targets to process XML data sequentially. JSON can also be handled.
• For more information and code snippets, you can refer to the ABAP Keyword Documentation and the XML/JSON cheat sheet.

• Provides access to abstractions for ABAP Dictionary objects such as database tables, data elements, types and more.
• For more detailed examples, refer to the SAP Help Portal. See also the executable example of the ABAP for Cloud Development cheat sheet.
• The code snippet contains a small selection and only hints at the many ways to retrieve different pieces of information that the classes provide.
• The snippet does not only include the XCO_CP_ABAP_REPOSITORY class but also others such as XCO_CP_ABAP, XCO_CP_ABAP_SQL, and XCO_CP_CDS. More XCO classes are available in that context.

• For sending emails, a configuration is required. Find more information here.
• Note that you can also send emails asynchronously using the method send_async.

Hello

This is a test mail.

• Used in the context of the Background Processing Framework (bgPF) to run code asynchronously in the background.
• Different flavors are available:
• Using bgPF without transactional control, for example, if you do not work with a RAP application or transactional control is not relevant in an ABAP program. In this case, you can implement the IF_BGMC_OP_SINGLE_TX_UNCONTR interface.
• Using bgPF with transactional control, for example, if you work with a RAP application. In that case, you can implement the IF_BGMC_OP_SINGLE interface. Note: If you are in a RAP context, you do not need to implement COMMIT/ROLLBACK WORK because the RAP framework takes care of it.
• More information:
• Background Processing Framework
• Transactional control with the controlled SAP LUW
• The following, self-contained, and oversimplified example is intended to give a rough idea about the functionality. It does not include transactional control. The example class can be run using F9 in ADT. It does the following: A demo database table of the cheat sheet repository is filled synchronously and asynchronously (using bgPF) with entries, just to show an effect and get an idea. Two entries are created in the background. WAIT statements are included to have a self-contained example, and that all created database entries can be shown in the output. In the example, the background processing may be visualized, for example, by the MODIFY statement that is followed by a WAIT statement in the loop. The output can show that the entry for the first asynchronously created entry was added before a synchronously created entry. For more visualization options regarding the execution in the background, you can, for example, check the ABAP Cross Trace. For more information, refer to the documentation.

• For creating a client object using an HTTP destination. The HTTP destination is provided based on an HTTP destination object. The latter can be created, among others, based on a communication arrangement or a plain URL.
• For more information, refer to the class documentation and the topic Integration and Connectivity.