This project provides file format definitions of ABAP repository objects.
The project is still in an early phase. We plan to modify and extend this document as our understanding improves. Since the ABAP file formats can still change in the future, we do not recommend to use them in a productive environment, yet.
ABAP repository objects are stored on development systems and not as regular text files as many other programing languages including python, C++ and others. The aim of the ABAP file formats is to provide a common and transparent definition of how to store ABAP repository objects in files. The file representation of ABAP repository objects facilitates the ongoing effort of applying and adopting existing developer tools and paradigm to ABAP.
The design of the ABAP file formats covers the following principles:
- The file content is complete and can be used for the sharing and distribution of ABAP repository objects.
- The file content is human-readable and the structure is as close as possible to what users know from their IDE.
- The files don't contain metadata like dates, usernames, last editor, system specific information, plus no obsolete or redundant information.
Details on technical specification can be found here.
| Type | Specification |
|---|---|
| CHKC | ATC Check Category |
| CHKO | ATC Check |
| CHKV | ATC Check Variant |
| CLAS | Class |
| ENHO | BAdI Enhancement Implementation) |
| ENHS | BAdI Enhancement Spot |
| FUGR | Function Group |
| INTF | Interface |
| NROB | Number Range Object |
Feel free to raise issues to ask questions or report bugs.
Comments and suggestions for improvements are most welcome.
You feel responsible for an ABAP object type? We will be more than happy if you contribute your object type to this project. Just open a new pull request.
More details are found at Contributing.
Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.