Skip to Content

Many of you know and widely use SAPlink. I bet this application spared you lots of time not once. No doubt, a great project. Although there are many plugins available which increase its usability, over time however your expectations might increase as well. I experienced that myself last time.

 

Motivation

While working on some recent cutover projects for one of our customers, I faced a problem with existing development. I had to move some customer DDIC objects which contained a number of customer sub objects. That forced me to add each object’s definition one by one to SAPlink nugget. Eventually I missed some anyway, so the process has extended largely, as I had to revert to legacy system and add those missing definitions. Futhermore I had to rename each object separately in target system as very seldom we share the same namespace in different systems.

Then I realized that such drilling object’s hierarchy option would be great to have. One click, several (sub)definitions extracted. Renaming option was optional, but welcome.  

 

So it is there

After a short analysis of how SAPlink works in its core, I was able to achieve my initial goal – develop the “plugin”. It is available under SAPlink chain and rename. It isn’t rocket science, but can help you with transition process. Please feel invited to participate in testing (I was only able to do unit tests), using, proposing changes, reporting bugs, joining the project. Any help that you can offer to make this enhancement useful, is greatly appreciated.

 

Open source project and hosting

I was told by Gregor Wolf who is a member of SAPlink project that it is going to be moved from Google Code to Code Exchange due to some issues with licensing. If this happens you will be able to find this project over there as well. So please stay tuned for upcoming changes in projects hosting.

 

Usage prerequisites

There are only a few things you need to pay attention to:

  • It suports only DDIC objects
  • Chaining options are only available for nugget file. Slinkee doesn’t support it, as from its nature it is used to export/import only single object. So is renaming used for nuggets only and for objects with are exported with chain option
  • Object definition mustn’t already reside in nugget, XML traversing will finish at spot where existing definition was found. Mechanism will treat it as end point of further sub object search. If you get message “No new object added to specified file” this means you need to ensure that definition is not already in nugget or you selected object which doesn’t exist in the system

 

Demo

The process of which you got used to when using SAPlink has changed only slightly:

  • run your SAPlink, create a nugget file
  • choose “Add object” radio
  • you will get three new options available – Rename” and “Only customer objects” can be selected once “Chain” is chosen

  • after you run it, you will get a tree of sub objects that were extracted from main definition, check ones you want to export and rename if needed, then run again

  • Enjoy:)

 

Further info

You will likely want to read User documentation and Developer manual which I created on wiki. Soon it will be submitted and moved as child page to SAPlink.

Hope you will like this small enhancement and will help me to improve it over the time.

To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

  1. Guillaume GARCIA
    Hi,
    Indeed, this is a long overdue feature.  🙂
    Thanks.

    Suggestion, if one can :
    – easily view/pick objects from nuggets
    – embed all Z-objects (same as Utilities->Environment Anaysis) from a large object
    that would be quite interesting also.
    Best regards,
    Guillaume

    (0) 
    1. Marcin Pciak Post author
      Sure, all are welcome.

      1) I think it is already covered by tool called NuggViewer. More on this here
      http://wiki.sdn.sap.com/wiki/display/ABAP/SAPLink+Tools

      2) As I said it only supports DDIC objects at the moment. I don’t reject having such feature in future though. Anyhow not an easy one as would need to support all kinds of plugins. What is more current mechanism analizes XML document (one node per object), not object dependencies directly in the system. So the architecture should change in order to have this supported too.

      Thanks for sharing ideas
      Marcin

      (0) 
      1. Guillaume GARCIA
        Hi,

        1) I know about NuggViewer (I wrote this Wiki page)  🙂
           But I thought of installing parts of the nugget selectively within SAPLink itself
        2) This lead me to think SAPLink should be shipped with as many plugins (or create pack of plugins).

        Thanks.
        Best regards,
        Guillaume

        (0) 
        1. Marcin Pciak Post author
          1) nice 🙂 Ok, this feature is achieveable, so will consider that.

          2) I know it should. Inspired by real case I focused on DDIC ones as these caused me lots of troubles. I will surely consider this upon next release too 🙂

          Thanks
          Marcin

          (0) 
  2. Krishna Mohan V
    Just trying to share our experience, we found the tool is not capable of generating the maintenance views for the DDIC objects (where ever we enabled maintenance view). This caused problem, as all objects dependent on those tables, were not activated.
    (0) 
    1. Marcin Pciak Post author
      Maintenance view (generated one) is probably a separate object which does not come together with metadate for DDIC view. So I guess you are right, SAPlink doesn’t support this feature.
      (0) 

Leave a Reply