cancel
Showing results for 
Search instead for 
Did you mean: 

Entry doesn't exist for root attribute CUSTID in MD CUSTOMER for planning level DAYPRODLOCCUST.

nazarali1308_37
Explorer
0 Kudos

Any insight on how to fix the above issue.

the Data integration job has some entries rejected(Rejection Code 135) with the above subjected error.

However the Master data already have those values in the attribute - Customer ID's

Thanks & Regards

Nazar Ali.M

0 Kudos

Hello,

Are you trying to create Attribute as key Figure?

Regards

Gaurav

nazarali1308_37
Explorer
0 Kudos

Hello guglanigaurav1987 ,

Thanks for your response,

i created a Stored KF - "ZBACKLOGSALESORDERSPAST" at DAYPRODLOCCUST to bring in the Backlog SO's for visibilty.

Thanks & Regards

Nazar Ali.M

Accepted Solutions (0)

Answers (3)

Answers (3)

avijit
Employee
Employee
0 Kudos

Dear,

The KBA should help.

2742072 - IBP data integration: Entry doesn't exist for root attribute

The rejection error means, the CUSTID which is available in the Source/File is not found in the MDT CUSTOMER. Download the Rejection report from Data Integration app and look for rejected CUSTIDs. Upload the missing CUSTIDs in MDT CUSTOMER before uploading key figure value Or remove from Source/File.

Best regards,
Avijit

0 Kudos

Hello Nazar,

The root attribute like Key/Required from Customer MDT should be same as the root attribute of that Planning Level DAYPRODLOCCUST at Customer MDT.

Steps:

1. Go to Customer Master Data Type, check the Key/Required field it would be ticked at CUSTID attribute

2. Go to Planning Level DAYPRODLOCCUST check the root attribute of that corresponding Customer MDT, it should be same

Please confirm if it helps.

Thank you,

Best regards,

Veera Reddy Sagili.

nazarali1308_37
Explorer
0 Kudos

Hello Veera,

Now i understood, both the above steps are true in my case,

i mean CUSTID is been selected, but still i have this problem and few records(not all) are getting rejected while i run the interface which brings in Backlog orders.

Thanks & Regards

Nazar Ali.M

0 Kudos

Please check that the Root attribute would be different in the customer under KEY from the Root attribute of Customer at the corrsponding Planning Level DAYPRODLOCCUST, it should be same then it will resolve.

nazarali1308_37
Explorer
0 Kudos

Hello Veera,

Thanks for your insight.

However was not able to follow your suggestion, Root attribute should be same between which Master Data?

Thanks & Regards

Nazar Ali.M