SAP Message RH109 - Node [&1]: Node name '&3' for characteristic &2 already exists

Diagnosis
The nodes NODEID = [&V1&] have the same node names NODENAME = '&V3&'.This is not allowed because neither node is a leaf and both nodes areassigned to the same characteristic &V2&.
Note that a maximum of 50 characters is available for message variables.The node name NODENAME = '&V3&' might not be displayed in its fulllength.

System Response

Procedure
Try to localize the problem. If the hierarchy is loaded from an SAPsource system, you can check whether the extracted data is correct byexecuting transaction RSA3 in the source system. If necessary, check ifthe data is modified with a user exit. If the hierarchy is loaded from afile, check the contents of this file. The problem might also be due toan error in the transfer rules or in the transformation.
You can identify the two duplicate nodes from the values for the node IDNODEID = [&V1&].
The problem can be caused by identical nodes delivered more than oncefrom the source. It is also possible that incorrect values forparameters such as the node name NODENAME or validity period [DATEFROM,DATETO] are the cause of the problem.
First check if the value for node name NODENAME = '&V3&' is correct. Thenode name consists of the characteristic value for the hierarchy basiccharacteristic and the characteristic values of all the characteristicscompounded to this characteristic. Errors creating the node name oftenresult in duplicate nodes. This problem also occurs if the node names ofall nodes are initial.
If the structure of the hierarchy is defined as time-dependent, the timevalidity of a node can be restricted with the fields DATEFROM andDATETO. Duplicate nodes generally do not occur if the validity intervalsof two nodes do not overlap in time. In this case check if the fieldsDATEFROM and DATETO are correctly filled.
In this case the duplicate nodes are not leaves. If you want to reuse anexisting subtree at another location in the hierarchy, you can refer tothis subtree with a link node. Possibly one of the two duplicate nodeswere incorrectly not marked as link nodes.

912115BW30B (SP30): Checking duplicate or postable nodes
837216Hierarchies: Consistency check for link nodes
1026749Hierarchies: Consistency check for duplicate nodes