Skip to Content
author's profile photo Former Member
Former Member

spec import_inheritance data

Dear experts,

I m trying to export and import spec that has inheritance relationship. but after importing spec data, inheritance relation is getting deleted.

please advice me how to import data having inheritance relationship.

1> I tried using [restart inheritance]button to reload but nothing happens then

2> I tried [inheritance acitve/inactive]button to get back the relationship. and i got the the relationship but my instance in the property is

not the same. a new instance is been added.

does anybody has gone throught with this situation? please advice is you have an solution.

thanks in advance.

Add comment
10|10000 characters needed characters exceeded

5 Answers

  • Best Answer
    Posted on Nov 20, 2012 at 03:16 PM


    Kamal's response is not entirely accurate since you can, in fact, import inheritance relationships. Prerequisite is that in the target system the same inheritance templates are defined as in the source system. Using the DataEditor, you can then, in online-mode, migrate the relationship.


    Add comment
    10|10000 characters needed characters exceeded

    • Hi Christoph,

      I didn't express properly what I meant, I admit it. In order to avoid confusion: You are correct, an inheritance cannot be imported using the standard import functionality. However, as I wrote, it can be migrated using the DataEditor.

      As to LSMW: I'm on your level, I never used it within EH&S so I can't say whether it can be used for the "import" of inheritance relationships.


  • author's profile photo Former Member
    Former Member
    Posted on Nov 20, 2012 at 11:16 AM


    You can import and export the specifications. But not the relations ships. Inheritence templates are master data. You must create them manually in all environments.

    follow the steps -

    1. create inheritance templates (master data) in all environments in uniform way.

    2. export the specifications and import them.

    3. check the Relation ships, Available as you desired it's ok. or esle edit them.

    Have one more short cut the program - RC1R0INH, which initiates the inheritance process.

    Let me know still you have any doubts in the process.

    Best Regards


    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 21, 2012 at 07:46 AM


    Thank you so much for the quick responses.

    I feel that above inheritance procedure is to tranport data between two sap systems or third party systems.But my requirement is to do changes in the same systems.

    export spec..make some changes to export file ..then import this process my inhertiance relationship is getting deleted as i explined above instances are getting added...

    by the way, while importing i m using delete parameter [Spec. deletion type =1] in tr CG33.

    i heard that DataEditor has this capability to do but we dont have this tool i need to find the way out..please advice if there is any procedure to maintain the relationship..

    and just wondering how do you guys are making changes to spec master(property tree data) on a daily basis.. I know there are bapi's (change and delete etc) to achieve this...does everybody are creating their own ABAP report??? or using standard import export pocess..??? PLS do share with me..



    Add comment
    10|10000 characters needed characters exceeded

    • Dear Saleem

      the options which Kamal explained are may be the best approach (e.g. use of ALE (refer to my thread as well)); the "inheritance" topic is a "technique" to manipulate/add data within EH&S. To use "export/imort" to "change" data is no option in my opinion. The "DataEditor" mentioned is one "chance".

      May be check if you can change from "inheritance" to "Reference" as reference is supported n export/import. But in any case you need to deal with the "file" and this approach is not recommended. The manipulation of data can be done with "Easy Expert" and "Expert" which is the standard approach in SAP EH&S. As explained by myself the next option is to use one "secondary data determination" programs. Here you are "free" in design etc.

      Now it depends a little bit on your "real business" case. As mentioned by Kamal an "EXCEL" import (as secondary data determination program) is one option; here you need to "simply" add a function module in the corresponding customizing creating a "hit list" in maintain mode; mark the specification to be updated and then try to process the "EXCEL" so that insert, update or delete may be possible.

      In any case: if you use "inheritance" you need to understand the "basic" idea of this technique; this is not easy; by the way: by using a secondary data "exit" you can try to "insert""/update" etc. inheritance relationships by "mass" depending on user input etc.

      Any optin mentioned so far is no! modification of EH&S but using the standard SAP EH&S "extension" points (like user exits etc.)

      With best regars


  • author's profile photo Former Member
    Former Member
    Posted on Oct 01, 2014 at 07:17 PM


    Just a couple quick notes...

    1. When you export data from EHS and those specifications has inheritance relationships, then the export file does not differentiate between locally maintained data, or the inherited data.

    2. Importing that file in a new system will result in all locally maintained data without the inheritance relationship.

    That means your inheritance specification will not be there, rather the data passed on is locally maintained. This is why you need to identify your data migration strategy in such a way that you know which data points are being passed on through inheritance, and which data points are locally maintained. You can then decide if you would rather keep it locally maintained or you can choose to create a property tree that does not contain inherited data points.



    Add comment
    10|10000 characters needed characters exceeded

    • Dear Duncan

      thanks for highlighting the topic once again. To my knowledge the only chance to "reuse" inheritance in a target SAP system is may be using an ALE scenario; Therefore base on generated IDOCs one could "reinstall" an inheritance scenario in a SAP target system; but the "inheritance template" can not be transferred using ALE; this need to be maintained in the target system;

      And yes you are right: importing data is a challenge in EHS; os if there is the need to migrate data from SAP to SAP or Non SAP to SAP you should take your time in doing so. IN most cases you will not succeed in one run.


      PS: for those who love using LSMW: you can use (in my opion) as well LSMW approach wiht the ALE used in EHS context; LSMW can generate IDOCs, SAP system can receive and book the IDOCs in EH&S.

  • author's profile photo Former Member
    Former Member
    Posted on Oct 03, 2014 at 02:14 PM

    We have a custom ABAP program that assigns our inheritance templates to the specs. The Data Editor tool only work in Online Mode for assigning Inheritance Relationships.

    To identify the inheritance relationship and distinguish between the target/source so you do not duplicate, you can build an SQVI query and easily get that information to then narrow down your loading to only those source Specs. You will be able to see which ones have the inheritance relationship by looking at the values in. TCGTPLREL-RECN_TPLH

    Then once you load data to only those source specs using CG33, the inheritance job will get triggered will automatically pass down the data the target specs.

    Inheritance.png (42.3 kB)
    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Christoph Bergemann

      The automatic assignment of the Inheritance Relationship is user friendly but totally custom.

      It is done automatically daily via a background job when new Specs are created based on logic that we have to identify the difference between the target and source (i.e. commercial product spec / formula spec).

      Mass data loading is never user friendly though and always requires some degree of support from an SAP functional IT resource.