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
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