Error while extracting and loading material hierarchy data

[former_member226000]

Hello Experts ,

I am getting below error while extracting and loading material hierarchy data .

Node [ 00036089,00036087]:Leaf '000000000000175190' already exists as child node of 00003128.

I checked in RSA1HCAT program in source system and observed that "000000000000175190" which is actually an article number , does exist under 8 different nodes . Now I am unable to check and correct in the source system table where to find this duplicate hierarchy . Can anybody help me on this ?

-Mandar.

[RamanKorrapati · Accepted solution]

Hi Mandar,

pls see the below links, and last reply

http://scn.sap.com/thread/3214852

http://help.sap.com/saphelp_nw70/helpdata/en/d0/538f3b294a7f2de10000000a11402f/content.htm

Below link may be useful. in info package , update tab, error handling options useful.

http://bisharath.blogspot.in/2010/12/duplicate-record-found-when-update.html

Regards

[former_member226000 · Accepted solution]

Thanks Raman . Unfortunately at our project , we are not maintaining product hierarchy . We are only implementing Material hierarchy . So I couldn't find anything in the navigations provided by you

Also in Infopackage-->Update-->Error handling , only thing I can see is "Terminate after no.of errors " which is already set to 1000.

-Mandar.

[former_member226000 · Accepted solution]

Dear All ,

The issue has been resolved.Got to know about report RCCLINOBDEL from SAP note . This report , when run in TEST mode displays the duplicate INOB entries. When the same run normally , deletes the duplicate INOB entries.

Thanks all for your co-operation.

-Mandar.

[amine_lamkaissi]

Hi Mandar,

If you are using a DTP to load data into your Master Data.

Check option "Handle Duplicate Record Keys"

Your problem will be solved

Amine

[former_member226000]

Thanks Amine for prompt response. But the problem is we are using 3.X flow for hierarchy data load . Hence it don't have DTP involved

[amine_lamkaissi]

Try this option on your datasource.

Set the option to none.

Amine

[former_member226000]

Thanks Amine for your concern. We are working in production system since DEV system is under maintenance , I see some risk in directly modifying datasource in production .

-Mandar.

[amine_lamkaissi]

Yes I agree with you Mandar.

The best practice is to start in DEV and transport into Production.

Anyways, I think that you have to modify somethinh in Dev.

Waiting for your DEV maintenance, you can carry out an urgent modification in Production and make the situation proper after with a transport order.

If you don't want to take any risk. Delete the problematic records manually from PSA.

Amine