SAP2Moose

With this release the logic to search into the "other direction" is now provided (down search, who is used by an element). There are some other small bugfixes and improvements. Due to them the "Upsearch", this is the search who is using an element is now much faster.

Contains the fix to issue "No elements extracted if package starts with $ #85". This is mandatory to extract models from local packages.

13.02.2018 v1.1.0

Contains the following improvements:

• Support programs better #53 Programs that are used by other programs or coding are now extracted together with their usage
• Support functions in more detail #52 Functions are now displayed together with elements that use them

• Support elements with equal names #84

New feature to show dynamic usages in the diagrams: Add dynamic calls to the model #80 A new parameter "Classes to read dynamic usages" is available. Add a list of class names here separated by blanks. Each class has to have a static method WHERE_USED with an export parameter data of type any table that is passed by reference. Internally the method has to build a table of type: TYPE STANDARD TABLE OF wbcrossgt WITH DEFAULT KEY, that is to be passed to the export parameter data. This table has to fill the fields otype, name and include of the internal table like this is done by the where used analysis in table wbcrossgt. See also this example for a class that provides dynamic usages:

CLASS z2mse_test_dynamic_usage DEFINITION
  PUBLIC
  CREATE PUBLIC .
      PUBLIC SECTION.
      CLASS-METHODS where_used
      EXPORTING
        !data TYPE ANY TABLE .
  PROTECTED SECTION.
  PRIVATE SECTION.
ENDCLASS.

    
CLASS z2mse_test_dynamic_usage IMPLEMENTATION.
  METHOD where_used.

    " Example of a method to transfer dynamic usages to the extractor
    DATA: dyn_usage TYPE STANDARD TABLE OF wbcrossgt WITH DEFAULT KEY,
          line      TYPE wbcrossgt.

    CLEAR line.
    line-otype = 'ME'.
    line-name = 'Z2MSE_TEST_CL_A\ME:CONSTRUCTOR'.
    line-include = 'Z2MSE_TEST_CL_B1==============CM002'.
    INSERT line INTO TABLE dyn_usage.

    CLEAR line.
    line-otype = 'ME'.
    line-name = 'Z2MSE_TEST_CL_A\ME:METHOD_A'.
    line-include = 'Z2MSE_TEST_CL_B1==============CM002'.
    INSERT line INTO TABLE dyn_usage.

    data = dyn_usage.

  ENDMETHOD.
ENDCLASS.

Fix bug in older releases

See Methods that are redefined are not part of the extracted model #67 and the changelog

Fixes Issue 75 Release v0.5.4 is not compatible to ABAP 7.0.2

Includes: Issue 73 Make modifiers for programs, function groups and SAP BW transformation specific Issue 72 Map functions to classes with name of function group Issue 71 Support ADT links to programs, functions and includes of function groups

It is now possible to open SAP BW transformations that are part of the extracted model directly in the SAP-BW project in eclipse. (Click on the "method" that corresponds to the transformation in the Moose2Model diagram and call RWDiagram openLinkTo: self.) Requires that linking is enabled in Moose2Model and the settings of Eclipse are so, that ADT links are executed.

Contains the fix #68

With #63 ADT links for classes and class components are added. Moose2Model v0.2.0 should be used, see also https://blogs.sap.com/2013/05/10/how-adt-links-change-the-way-you-work/ on how to activate and use ADT links. ADT links work currently only on Windows systems.

With #65 the links are compatible to Moose 6.0

With #63 ADT links for classes and class components are added. Moose2Model v0.2.0 should be used, see also https://blogs.sap.com/2013/05/10/how-adt-links-change-the-way-you-work/ on how to activate and use ADT links. ADT links work currently only on Windows systems.

Fix issue #62 "Usages by Interfacemethods not found if name longer than 30 characters" Adds #48 "Add usage of interface components"

The extraction coding had syntax errors in older releases. This is corrected.

Provides informations on the extracted elements using SAP Gui only. This functions will be improved with future releases. Nonetheless it can already be used to perform a Where-used analysis for multiple "layers". This is an early release that will not show all usages in all cases.

Mandatory error corrections to extract ABAP interfaces correctly

With this release it is now possible to use the extractor without drawing diagrams in Moose.

A first use case is specifying either a class element or a table and analyzing all using elements (Downsearch is prepared but not yet implemented). This can be done without exporting to Moose.

Please keep in mind, that this is an early alpha version. The report may not yet find all relevant dependencies.

Usage by Programs, Functions and SAP BW is also in an early stage of implementation and not yet finished.

See changelog.txt for details. Starting with this version a new logic to handle the extraction is used. This is a major improvement to the architecture used in v0.2.1. Starting with this release adding new functions will be much easier. This is also the first release where usage by components of the "outer world" will be added. With "outer world" elements are meant that are not regularly part of the standard where-used functionality.

Fixes a bug that caused a dump when an interface with event is part of the selection (#45)

The main coding for extracting the where-used information is now completely rewritten. The application has now a very high coverage with Unit and Integration tests.

The extractor works in a ABAP 7.02 system (But no full test is done yet on release 7.02)

The extraction is still limited do classes, methods, attributes, database tables and Web Dynpro components. Interfaces are better covered compared to version 0.1.0.

Extracts packages, classes, methods, attributes, tables and WebDynpro ABAP. Maps these to package, class, method and attribute. Extracts also programs and maps them to module.

Analyses where-used-index but only in one direction (used by).

Has limited functions and may have bugs. But is useful to extract packages and understanding the limitation. Is used successfully in a project for at least three month.