Skip to content

Releases: SAP2Moose/SAP2Moose

Support Pharo 7

30 Aug 11:27
Compare
Choose a tag to compare

Fixes

  • Source Language not exported (isSmalltalk was sent to nil in new Moose) #110
    This is helpful to work with Moose on Pharo 7

Downsearch and faster Upsearch

25 Jan 07:47
Compare
Choose a tag to compare

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.

Allow extracting elements of local packages

08 Jun 14:28
780183a
Compare
Choose a tag to compare

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

Usage of programs and functions

13 Feb 19:11
Compare
Choose a tag to compare

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

Dynamic usages

15 Jan 21:13
Compare
Choose a tag to compare

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 issue #76 wrong usage of implementing interface method

06 Nov 21:11
Compare
Choose a tag to compare

Support 7.02

05 Nov 20:23
Compare
Choose a tag to compare

Fix bug in older releases

Support redefined methods

05 Nov 20:06
Compare
Choose a tag to compare

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

Make release v0.5.4 7.02 compatible

05 Nov 15:16
Compare
Choose a tag to compare

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

Improve function group and more ADT links

05 Nov 14:31
Compare
Choose a tag to compare

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