• Since the ABAP cheat sheets provide information in a nutshell, they do not claim to be exhaustive as far as the described syntax and concepts are concerned. If you want to go more into the details, just consult the ABAP Keyword Documentation, for example, by choosing F1 for a keyword in your code or directly researching via the online version or the system-internal version.
• If not stated otherwise in the cheat sheets and examples, the content of this repository is relevant for these ABAP language versions:
  • ABAP for Cloud Development: Restricted ABAP language scope for developments in the SAP BTP ABAP environment → Online version of the documentation
  • Standard ABAP: Unrestricted ABAP language scope, for example, for developments in an on-premise ABAP system → Online version of the documentation (latest version)
• Check the Known Issues and Disclaimer.
• In the cheat sheets, links are available to glossary entries and topics of the ABAP Keyword Documentation. Note that these links refer to the ABAP for Cloud Development version in most cases.

• A few DDIC artifacts, for example, database tables, are part of the repository. They are used by the examples to ensure self-contained examples. For all examples to work, all artifacts must be imported.
• All examples are designed to display some output in the ADT console. Once successfully imported, you can execute the examples in ADT by choosing F9 to display the output in the ADT console.
• The examples include descriptions and comments in the code for providing explanations and setting the context.

Prerequisites

• Before importing the code, you have made a system-wide search for, for example, classes named ZCL_DEMO_ABAP* so as not to run into issues when you try to import the code. If someone has already imported the content in the system, you can simply check out that imported version and proceed with the step 3) Run the code.
• You have access to an SAP BTP ABAP Environment instance (see here for additional information).
• You have downloaded and installed ABAP Development Tools (ADT). Make sure that you use the most recent version as indicated on the installation page.
• You have created an ABAP cloud project in ADT that allows you to access your SAP BTP ABAP Environment instance (see here for additional information). Your logon language is English.
• You have installed the abapGit plug-in for ADT from the update site.

Import Code

Use the abapGit plug-in to install the ABAP Cheat Sheets by carrying out the following steps:

1. In your ABAP cloud project, create a package, for example, ZABAP_CHEAT_SHEETS as target package. It is recommended that you assign the package to a transport request suitable for demo content.

2. Add the package to the Favorite Packages in the Project Explorer view in ADT.

3. To add the abapGit Repositories view to the ABAP perspective, choose Window → Show View → Other... from the menu bar and choose abapGit Repositories.

4. On the abapGit Repositories view, click the + icon in the top right corner of the ADT tab to link a new abapGit repository.
   

5. The Link abapGit Repository pop-up is displayed. Insert the following URL:

https://github.com/SAP-samples/abap-cheat-sheets.git

6. Choose Next.

7. On the Branch and Package Selection screen, insert the name of the created package (e. g. ZABAP_CHEAT_SHEETS) in the Package field.

8. Choose Next.

9. On the Select Transport Request screen, select the created transport request suitable for demo content and choose Finish to link the Git repository to your ABAP cloud project. If the created package is already assigned to a transport request for the demo content and a message that an object is already locked in a transport request is displayed, choose Finish, too.

10. In the abapGit Repositories view, filter for your package. The repository appears in the abapGit Repositories view with status Linked.

11. Right-click the new abapGit repository and choose Pull... to start the cloning of the repository contents.

12. On the Branch and Package Selection screen, choose Next.

13. If the Locally Modified Object screen is displayed, select the objects (for example, the package to automatically select all artifacts) in the list and choose Next.

14. On the next screen, select a transport request and choose Finish. Same as above, if an object already locked message is displayed, choose Finish, too. The status in the abapGit Repositories view changes to Pull running.... Note that the pull run may take a few minutes.

15. Once the cloning has finished, the status is set to Pulled Successfully. You might need to refresh the abapGit Repositories view to see the progress of the import. To do so, choose the icon for refreshing (Refresh) in the top right corner of the view.

16. Refresh your project tree. E. g. in ADT, right-click the package and choose Refresh or F5. The package should contain all artifacts from the GitHub repository.

17. Make sure that all artifacts are active. To activate all inactive development objects, choose the Activate all inactive ABAP development objects button from the menu (or choose CTRL+Shift+F3).

Prerequisites

• The assumption is that you are on the latest ABAP release. The content was also tested with release 7.56.
• Before importing the code, you have made a system-wide search for, for example, classes named ZCL_DEMO_ABAP* so as not to run into issues when you try to import the code. If someone has already imported the content in the system, you can simply check out that imported version and proceed with the step 3) Run the code.
• You have downloaded and installed ABAP Development Tools (ADT). Make sure that you use the most recent version as indicated on the installation page.
• You have created an ABAP Project in ADT that allows you to access your Application Server as mentioned above. Your logon language is English.
• You have downloaded and installed the standalone version of the abapGit report. Make sure that you use the most recent version as indicated on the installation page. You can create a report, for example, zabapgit_standalone and copy and paste this code into the program.
• You have installed the certificate files for github.com, see abapGit Documentation.

Import Code

Use the standalone version of the abapGit report to import the demo examples of the ABAP Cheat Sheets by carrying out the following steps:

1. In your ABAP project, create a package, for example, TEST_ABAP_CHEAT_SHEETS as target package suitable for demo content (e. g. by using LOCAL as software component).
2. Add the package to the Favorite Packages in the Project Explorer view in ADT.
3. Run the standalone version of the abapGit report.
4. Choose the New Online button. If the button is not available, for example, if another repository is already opened, choose the Repository List button.
5. On the New Online Repository screen, make the following entries:

   • Git Repository URL:

     https://github.com/SAP-samples/abap-cheat-sheets.git
     

   • Package: Your demo package, for example, TEST_ABAP_CHEAT_SHEETS

6. Leave the other fields unchanged and choose Create Online Repo.
7. On the Repository screen, you will see the available ABAP artifacts to be imported into your ABAP system.
8. Choose the Pull button. The import of the artifacts is triggered. It might take some minutes.
9. If the Inactive Objects pop-up is displayed, select all artifacts and choose Continue (✔️).
10. Once the cloning has finished, refresh your project tree. E. g. in ADT, right-click the package and choose Refresh or F5. The package should contain all artifacts from the GitHub repository.
11. Make sure that all artifacts are active. To activate all inactive development objects, choose the Activate all inactive ABAP development objects button from the (or choose CTRL+Shift+F3).

• Open your created package containing the imported ABAP artifacts in the ABAP Development Tools (ADT).
• Open an ABAP cheat sheet example class as listed in the ABAP Cheat Sheets Overview section, for example, zcl_demo_abap_string_proc. The classes are contained in folder Source Code Library → Classes.
• Choose F9 to run the class. Alternatively, choose Run → Run As → 2 ABAP Application (Console) from the menu.
• Check the console output.

💡 Note

• Check notes on the context and the ABAP syntax used included in the class as comments.
• Due to the amount of output in the console, the examples include numbers (e. g. 1) ..., 2) ..., 3) ...) representing the header of the individual example code sections. Plus, the variable name is displayed in the console in most cases. Hence, to easier and faster find the relevant output in the console, just search in the console for the number (e. g. search for 3) for the particular output) or variable name (STRG+F in the console) or use break points in the code to check variables in the debugger.
• You might want to clear the console by making a right-click within the console and choosing Clear before running another demo class so as not to confuse the output of multiple classes.