cancel
Showing results for 
Search instead for 
Did you mean: 

0CUST_SALES_LKDH_HIER Hierarchy load issue

0 Kudos

Hello,

The Hierarchy load from the datasource 0CUST_SALES_LKDH_HIER to a time dependent InfoObject is failing with the below error:

Node [000073, 000075]: Leaf  '006766765' already as child of node 000069.

I have checked in the KNVH table in R/3 and I found two entries for 006766765 with 'valid from' and 'valid to' dates as below:

Can some help me on this issue? Is this scenario valid?

Thanks,

Prateeksha Kalyani

Accepted Solutions (0)

Answers (1)

Answers (1)

RamanKorrapati
Active Contributor
0 Kudos

That might be duplicate.

You need to cross check with your source team and rectify it.

As my guess they might be forgot to delete the extra entry.

So inform to source team,they can solve this issue.

0 Kudos

Hi Ramanjaneyulu,

I did check with business on this and they said its invalid scenario.

But they do not know how to delete the second (Invalid) entry. Can you please tell me the procedure to delete it from R/3?

Thanks,

Prateeksha.

RamanKorrapati
Active Contributor
0 Kudos

With your client permission try to delete extra entry from source table.

About deletion you can check with ABAP Team with help of functional team.

Like in bw selective deletion at cube level, please check with abap team is there any option to delete selected entry from table?

if not then ask them(ABAP) to write a program to delete extra entry.

Even you can at try to check ABAP forum as well. you may get more possible options.

0 Kudos

Thanks Ramanjaneyulu.

0 Kudos

Hi Ramanjaneyulu,

A similar scenario had occurred around 10 months back. But the people then in BW team had fixed it not sure how without changing any records in the KNVH table.

Unfortunately these people are no longer working with the project.

Can you suggest how this can be fixed in BW?

RamanKorrapati
Active Contributor
0 Kudos

if possible try to delete KUNNR(one entry) from bw master data table.

if your hierarchy data load run full load every time then no use bw side handling option.

Better to ask source team and delete that extra entry.

0 Kudos

Hi Ramanjaneyulu,

Unfortunately, its a full load :-(.

In the past too this was a full load and a similar issue with similar scenario was fixed without changing the entries in the table in ECC.

Can you please suggest any other alternative?

RamanKorrapati
Active Contributor
0 Kudos

Try to see at your dtp,

you may find Handle duplicate reocrd key check box option.

if its unselected then select it. it will avoid getting getting duplicates.

0 Kudos

its a 3.x flow.. and there is no DTP

RamanKorrapati
Active Contributor
0 Kudos

at info pack, updating process tab.

if you used PSA then we will get option to ignore double data records check box.

please check it