Skip to Content
avatar image
Former Member

Impact of modifying existing VAT nodes ID when Setting up Property Tree - Specification Management

Hello,

We're wanting to add a value assignment type to a given property tree and are carrying out the configuration activity of "Setting up Property Tree" to do so. Initially, we spaced out node IDs in the property tree by 10 in a way that's similar to as follows:

ID VAT

100 VAT_A

110 VAT_B

etc.

An additional 9 VATs were eventually needed between VAT_A and VAT_B, resulting in the following:

ID VAT

100 VAT_A

101 VAT_A_A

102 VAT_A_B

...

109 VAT_A_I

110 VAT_B

etc.

There's now a desire to add another VAT between A and B, but there are no more node IDs available. Adding between VAT_A and VAT_B again results in the node ID for VAT_B being shifted down to 111.

The configuration documentation for the "Setting up Property Tree" activity explicitly states the following:

Enter numbers in ascending order for the values of the ID field with large enough intervals between the numbers so that you have room to insert value assignment types in your property tree later.

even though the change has been made in Dev, the data seems unaffected. Is there a reason that SAP provides this guidance on the spacing of IDs? My guess is that a changing of node IDs has some impact and should not be done, but we are not sure of what that impact is. Has anyone else faced this?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jan 24 at 01:07 PM

    Hey Tyler,

    even though the change has been made in Dev, the data seems unaffected. Is there a reason that SAP provides this guidance on the spacing of IDs?

    No it will not give any impact cause you are just adding some value assignment with new node IDs.

    Setting up Property Tree is just a hierarchical view based upon the requirement of business they can shuffle it, it will not have any impact on data base table cause data will hold in class for VAT.

    My guess is that a changing of node IDs has some impact and should not be done, but we are not sure of what that impact is. Has anyone else faced this?

    You did the good thing when you created 100 VAT_A 110 VAT_B , Cause you maintain the gap of 10 ,So that you able to maintain VAT_A_I to VAT_A_I. If we assume that there is no gap in between then you can also continue after VAT_B based how you want to view the property tree in specification data base.

    SAP always suggest that you need maintain the gap between node ID's for future purposes. If you want to add anything in between you can always allow to add it.

    Its just a normal behaviour and i hope it helps.

    Thanks

    Satya

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 24 at 06:40 AM

    Hi Tyler,

    in the database there is something called value assignment types which actually hold the data, the property tree and property tree structure is the view you create to see the data in a certain order so that you can work with the data more effectively. So if you happen to modify the value assignment positions in the property tree, it does not have impact on the backend database structure and will not loose any information. So to conclude change of the ID can be done as required and it will not have any impact on the underlying data.

    Thanks and Regards

    Jayakumar

    Add comment
    10|10000 characters needed characters exceeded