This project is actively maintained and used (28 September 2021). Please open an issue to get support :-)
Installation to analyze applications
Create a new program in your SAP system. You need only the files z_moose_extractor.abap, z_moose_extractor_texts.txt and z_moose_extractor_documentation.txt. You find the most actual version on the tab Code. Or go to releases to get the code of a certain release.
Open file z_moose_extractor.abap with a text editor and paste the coding in your program. Add texts and documentation of the report for convenience using the other files. The documentation contains example which you may use for a first test.
You typically will run the program, select a package and download the file (preferable with extension .mse). The result is displayed by the report. To create diagrams, open with Moose Analysis or Moose2Model to analyze it.
This repository provides a program to extract model data from a SAP system into the analysis platform Moose on Pharo Smalltalk. It uses FAMIX as a flexible enhancable meta model.
It allows drawing diagrams that visualize SAP applications with Moose Analysis. It is currently used mainly to generate customizable Dependency Diagrams with the application RW-Moose-Diagram. But it is open to other usages.
This is not a tool made or owned by SAP.
With Moose2Model diagrams like this can be made:
Example how to analyze a class method:
The documentation is in the Wiki of this repository (Switch to the tab Wiki).
There are currently not many changes in the extractor, just because I am happily using it nearto every day (Rainer Winkler).
Last stable release v1.0.0: Extractor and Texts for extractor.. This is the first release where ADT links to ABAP classes and class components are extracted. Moose2Model v0.2.0 is required to use this links.
Earlier release v0.5.8: Extractor and Texts for extractor.. This is the first release where data can be analyzed without using Moose. It also provides a Where-Used analysis over multiple levels. This is an early version that is incomplete and should not find all dependencies.
ABAP releases higher than 7.02 SP6.
There may be minor issues in older releases due to eroneous usage of modern ABAP statements, this should be easy to be fixed. You can do it yourself or open an issue for this.
Installation to participate in development
Use abapGit to install the coding in a local system. The package name has to be Z2MSE (Required so that test objects have the correct names). The folder logic is prefix, but you should still use package Z2MSE to ensure that all tests work correct.
abapGit for development
This repository will use abapGit for all objects relevant to the development. The extractor itself is a simple program and can be installed with copy and paste. See wiki for details.
The local classes of the extractor are now generated using global classes. This allows ABAP Unit to be used to improve the quality and reduce the time needed for implementation. There is now also a new program z_moose_translate_to_local for this conversion. This program can also be used for other projects.
I would like to thank especially:
Damir Majer for many helpfull discussions and especially for inviting Tudor Girba to the SAP Inside Track Munich 2015, thus indirectly initiating this project
Tudor Girba for many valuable informations and tips on how to use Moose and FAMIX
Enno Wulff for making a 7.31 version available and many discussions to improve the extractor and to give hints on what can be done
And all colleagues that made this tool possible!
CubeServ is encouraging and supporting this project.