Skip to Content
Author's profile photo Lars Hvam

Upload and download Code Inspector variants via XML

Code Inspector variants are technically saved as ABAP programs using data clusters,/wp-content/uploads/2015/08/variant_760590.png

This makes it difficult to move the data between systems, and tell what exactly the variant contains without installing it. The project https://github.com/larshp/upDOWNci tries to address this issue by allowing upload and download of Code Inspector variants in XML format. It analyzes the ABAP code inside each check to determine the structure of the check settings and exports it to XML, the checks must  use class attributes with direct data dictionary for this to work, most of the checks use this approach, but expect errors and bugs in the program.

Start the program via report ZUPDOWNCI,

/wp-content/uploads/2015/08/selection_760591.png

and enter the variant, this will upload or download the variant to the frontend PC. Leave username blank for global variants.

Downloaded XML files will look like the following,

/wp-content/uploads/2015/08/example_760973.png

Upload will show a log for the imported check variant. The check variant will be created if it does not exist, and add additional settings to existing check variant if the check version in the XML matches the check version in the system.

/wp-content/uploads/2015/08/result_760974.png

Project page: https://github.com/larshp/upDOWNci

Issue list: https://github.com/larshp/upDOWNci/issues

Assigned tags

      8 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Florian Henninger
      Florian Henninger

      Hey Lars,

      I really love your open checks and this is a good addition to it.

      Thank you for sharing it with the community and of course with me 😛

      ~Florian

      Author's profile photo Peter Inotai
      Peter Inotai

      Hi Lars,

      I love this idea with the XML.

      I just wonder if instead of ZUPDOWNCI, wouldn't it be possible to use the saplink framework?

      Thanks,

      Peter

      Author's profile photo Lars Hvam
      Lars Hvam
      Blog Post Author

      Hi,

      Are you thinking about the distribution of the ZUPDOWNCI program, or adding code inspector variant as a plugin in saplink?

      Author's profile photo Peter Inotai
      Peter Inotai

      Hi,

      I meant the second one "adding code inspector variant as a plugin in saplink".

      For me it would make sense.

      Thanks,

      Peter

      Author's profile photo Lars Hvam
      Lars Hvam
      Blog Post Author

      hmm, I dont think there is an object type(TADIR-OBJECT) for code inspector variants. The variants are saved as PROG programs, along with some TABU contents, so it might be possible via existing plugins, though only in "data cluster" format.

      Author's profile photo Peter Inotai
      Peter Inotai

      Thanks for checking it! You're right, I didn't think of the TADIR entry.

      I just checked the ZSAPLINK* classes in our system, but couldn't find one for variants. Maybe we have an older version. I'll check if there is any plugin for variants.

      Peter

      Author's profile photo Lars Hvam
      Lars Hvam
      Blog Post Author

      I was thinking of using the existing plugins for PROG and TABU for import/exporting code inspector variants

      Author's profile photo Peter Inotai
      Peter Inotai

      Unfortunately I have to authorization to test this in our system (and authorization check was implemented quite tricky way in SCI, so it's difficult to fool it even with debug and replace), but I think your approach would work. ZSAPLINK_TABLE_CONTENTS should do the job.

      Peter