on 2023 Aug 20 4:22 PM
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
Request clarification before answering.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
4 | |
4 | |
3 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.