Rejection Code 134 - Ambiguous value for non-root Attribut

[former_member703940]

Dear experts,

I have created a new non-root attribut CONTROLCHECK as NVCHAR(4) of a master data type LOCMOTGRCUST on the plannning level LOC | MoTGr | CUST.

If I try to load this attribute Control Check via Master Data Workbook , I am getting an error message Rejection Code 134 as below.

Ambiguous value for non-root CONTROLCHECK using root CUSTID;LOCID at plan level DEVDV.WKPRODLOCLOCFRMOTCUST in MD LOCMOTGRCUST.

Can you please help me find the problem, how can I upload my attribute successfully?

Regards

[riyazahmed_ca2 · Accepted solution]

Hi Kenan,

This might also due to the case sensitivity of the Control Check Value. 'Yes' and 'yes' are different values. Please try to align the planning object and master data to get rid of the issues.

Best Regards,

Riyaz

[revanchatraban]

Hi,

Can you please check the below information on the ambiguous data?

Regards,

Revan C

[former_member703940]

Hi,

I try to understand, whether the described case in 2367185 the same issue with my problem.

Here is my issue again:

I try to upload the attribute CONTROLCHECK (non-root) into my master data LOCMOTGRCUST and get the error message for "Planning object 2" WKPRODLOCLOCFRMOTCUST:

Ambiguous value for non-root CONTROLCHECK using root CUSTID;LOCID at plan level DEVDV. WKPRODLOCLOCFRMOTCUST in MD LOCMOTGRCUST.

The attribute MOTID(root) does not belong Master Data LOCMOTGRCUST.

Should I add MOTID(root) in my Master Data LOCMOTGRCUST? or should I change MOTGROUPID(non-root) to root in Planning Object 2?

[AyanBishnu]

Change the root attribute from MOTID to MOTGROUPID in planing object 2 and let me know the outcome

[revanchatraban]

Hi,

It needs detailed understanding of the set up to resolve the issue.

As mentioned in the note, there are 2 ways to resolve it. I would suggest you to follow the trial and error method to resolve the issue.

Please post the results of your observation.

Thanks and Regards,

Revan C

[AyanBishnu]

Hi Kenan

Although the information that you provided is little insufficient. But i think the issue in in the MDT setup itself. You have 3 mandatory inputs in the MDT you have share which is CUSTID, LOCID and MOT. The first 2 are existing in their respective simple master type and may be you are using the reference attribute check for this MDT. Are you referencing MOT attribute from some other MDT ? if yes then please check if you have any MDT where you maintain it as I could see from the error that you have 2 roots here CUSTID and LOCID but not MOT. Please share screenshots of the respective MDT.

Also try to update the MDT using the file upload method and share the outcome.