Abap Cheat Sheets Save

• Since the ABAP cheat sheets provide information in a nutshell, they do not claim to be fully comprehensive as far as the described syntax and concepts are concerned. If you need more details, you can always consult the ABAP Keyword Documentation, for example, by choosing F1 on a keyword in your code, or by searching directly using the online or the system-internal version.
• Unless otherwise stated in the cheat sheets, the content of this repository is relevant for these ABAP language versions, with a focus on ABAP for Cloud Development:
  • ABAP for Cloud Development: Restricted ABAP language scope for ABAP Cloud → Online version of the documentation
  • Standard ABAP: Unrestricted ABAP language scope, for example, for classic ABAP → Online version of the documentation (latest version)
• Check the Known Issues and Disclaimer.
• The cheat sheets provide links to glossary entries and topics in the ABAP Keyword Documentation. Note that unlike the classic ABAP-only cheat sheets, in most cases these links refer to ABAP for Cloud Development.
• Here is an overview of the different ABAP language elements in the different ABAP versions, i.e. what is allowed in ABAP Cloud and what is not. See also the released APIs here.
• In order to have all ABAP cheat sheet documents in one place, the main branch (for ABAP Cloud examples) also contains the ABAP cheat sheet documents that are only relevant for classic ABAP.
• The example classes contained in the branches for classic ABAP mostly use syntax that is also available in ABAP for Cloud Development. Only the TEST_ABAP_CHEAT_SHEETS_CLASSIC subpackage contains syntax relevant to Standard ABAP and that is not available in ABAP for Cloud Development, such as dynpro-related ABAP keywords.

• Some DDIC artifacts, such as database tables, are part of the repository. They are used by the examples to ensure self-contained examples. All artifacts must be imported for all examples to work.
• Most examples are designed to display some output in the ADT console. Once successfully imported, you can run the examples in ADT by choosing F9 to display the output in the ADT console. The programs included in the branches for classic ABAP can be executed with F8.
• The examples include descriptions and comments in the code to provide explanations and set the context.

Prerequisites

• You have access to an SAP BTP ABAP Environment instance (see here for additional information).
• You have downloaded and installed the ABAP development tools for Eclipse (ADT). Make sure that you are using the latest version, as indicated on the installation page.
• Before importing the code, you have performed a system-wide search for classes named ZCL_DEMO_ABAP*, for example, so that you do not run into errors when you try to import the code. If someone has already imported the content into the system, you can simply check out that imported version and proceed to the step 3) Run the code.
• You have created an ABAP cloud project in ADT that allows you to access your SAP BTP ABAP Environment instance (see here for more information). Your login 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 the target package. It is recommended that you assign the package to a transport request that is 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. In the abapGit Repositories view, click the + icon in the upper right corner of the ADT tab to link a new abapGit repository.
   

5. The Link abapGit Repository popup appears. Enter the following URL:

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

6. Choose Next.

7. On the Branch and Package Selection screen, enter the name of the created package (for example, ZABAP_CHEAT_SHEETS) in the Package field.

8. Choose Next.

9. On the Select Transport Request screen, select the created transport request that is suitable for the 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 appears that an object is already locked in a transport request, choose Finish, too.

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

11. Right-click on 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) from 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 as well. The status in the abapGit Repositories view changes to Pull running.... Note that the pull run may take several minutes.

15. Once the cloning is complete, the status changes to Pulled Successfully. You may need to refresh the abapGit Repositories view to see the progress of the import. To do this, choose the Refresh icon in the upper right corner of the view.

16. Refresh your project tree. For example, in ADT, right-click the package and choose Refresh. The package should contain all the 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

• You are running an ABAP release for which examples are available. See the different branches of the repository. For example, you can find out about your ABAP release by checking the value of sy-saprl:

  DATA rel LIKE sy-saprl.
  rel = sy-saprl.
  BREAK-POINT.
  

• Before importing the code, you have performed a system-wide search for classes named ZCL_DEMO_ABAP*, for example, to avoid errors when you try to import the code. If someone has already imported the content into the system, you can simply check out that imported version and proceed to the step 3) Run the code.
• You have downloaded and installed the ABAP development tools for Eclipse (ADT). Make sure that you are using the latest 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 login language is English.
• You have downloaded and installed the standalone version of the abapGit report. Make sure you are using the latest 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.

Import Code

Use the standalone version of the abapGit report to import the demo examples of the ABAP cheat sheets by performing the following steps:

1. In your ABAP project, create a package, such as TEST_ABAP_CHEAT_SHEETS as a target package suitable for demo content (for example, by using LOCAL as the 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 open, 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

   • Branch: Choose the button with the 3 dots to the right of the input field. In the pop-up window, select the appropriate branch, e.g. v757 if your ABAP release is 7.57, and choose the Continue (✔️) button. Note: The examples in the main branch are for ABAP Cloud only.

   • Folder Logic: Full

6. Choose Create Online Repo.
7. The Repository screen displays the available ABAP artifacts to be imported into your ABAP system.
8. Choose the Pull button. The import of the artifacts is triggered. This may take a while.
9. If the Inactive Objects popup is displayed, select all artifacts and choose Continue (✔️).
10. When the cloning is complete, refresh your project tree. For example, in ADT, right-click on the package and choose Refresh. 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 menu (or choose CTRL+Shift+F3).

• Open the package you created containing the imported ABAP artifacts in the ABAP development tools for Eclipse (ADT).
• Classes:
  • Open one of the ABAP cheat sheet example classes listed in the ABAP Cheat Sheets Overview section, for example, zcl_demo_abap_string_proc. The classes are located in the Source Code Library → Classes folder.
  • Choose F9 to run the class. Alternatively, choose Run → Run As → 2 ABAP Application (Console) from the menu.
  • Check the console output.

    💡 Note
    

    • Check the notes on the context and the ABAP syntax used that are included as comments in the class.
    • Due to the amount of output in the console, the examples include numbers (e.g. 1) ..., 2) ..., 3) ...) that represent the headers of each example code section. Also, in most cases, the variable name is displayed in the console. Therefore, to find the relevant output in the console more easily and quickly, simply search the console for the number (e.g. search for 3) for the particular output) or variable name (CTRL+F in the console), or use breakpoints in the code to check variables in the debugger.
    • You may want to clear the console by right-clicking in the console and choosing Clear before running another demo class to avoid confusing the output of multiple classes.

• Programs:
  • The programs included in the repository can be executed with F8 (or Run → Run As → 1 ABAP Application).