Rejection code 134 when changing subnetwork ID

[dmitriy_karpov]

Hi all,

Please, recommend a way to address the error in subj.

I am working with a copy of PA UNIPA in IBP Starter where everything works well and trying to separate a subnetwork from the entire supply chain. For this I did quite little:

1. Entered a new ID SPA_1 in MD Subnetwork

2. Changed attribute SubnetworkID in Location Product from SPA to SPA_1

At step 2 I got stuck, bacause my changes were rejected with rejection code 134 "Can't find unique value for attribute "PLUNITID" using root "LOCID" at PL WKRESLOCSRCALTRES in MD S01LOCATIONPRODUCT."

Looking into this PL I see the LocationProduct is a non-root attribute (see below), so ambigous values must be acceptable. Why it tells me about LOCID only when LOCATIONPRODUCT has to root attributes? What did I do wrong and how to manage this?

Thanks for sharing your knowledge.

[piyush_parekh]

Hi,

I can see Location ID as root and Subnetwork ID as non-root in the planning level. This creates hierarchical relation between 2 attributes. 1 Subnetwork can have multiple Location IDs but 1 Location ID cannot be part of multiple Subnetworks. Check if this is what's happening when you're maintaining Subnetwork in Location Product MDT. If this is not possible from supply chain modeling standpoint, remove subnetwork from planning level.

Why it tells you only about LOCID is because the planning level doesn't have product ID attribute.

Hope this helps!!

Regards,

Piyush

[ruslan_lyzunov]

Hello Piyush,

Thank you very much for such a detailed answer. Do I get it right that separate planning of independent product groups in the same supply chain cannot be used in my case, when Subnetworks is not the root, and Locations is the root in PL? And subnetworks here can only be created by grouping locations?

[piyush_parekh]

As a standard, Subnetwork ID is not added in WKRESLOCSRCALTRES planning level. Remove this attribute from planning level. It seems this was added as a custom development. This is creating an issue where same location could be part of different subnetworks.

[Irmi_Kuntze]

Hi Dmitrii

I know that the template planning area SAPIBP1 has never had any locationproduct attribute in that planning level. And I would doubt that the pre-delivered UNIPA had that from the beginning. My guess is that at some point in time someone has added it. If you would be interested, you could compare the current active UNIPA with that very first version it was delieverd and check the differences. ... or just delete the attribute ... 🙂

Irmi

[Irmi_Kuntze]

Sorry Ruslan for not reading your post correctly at the first time

Planning Level WKRESLOCSRCALTRES must NOT have the subnetwork in the planning level, you seemingly have added it accidentally to the planing level after the copy. SAPIBP1 does not have it, because the roots of that planning level only contain the LOCID but not the PRDID and therefore the subnetwork can not uniquely be identified.

Delete it before you make the adjustments to the master data

Yours

Irmi

[dmitriikarpov976]

Alright. It is clear now that I must remove Subnetwork from WKRESLOCSRCALTRES. For whatever reason UNIPA is delivered with this attribute assigned to this PL.

[Irmi_Kuntze]

The LOCATIONPRODUCT master data type has an attribute check on master data type PLANNINGUNIT. You just need to maintain the value SPA_1 in there and it will work

[ruslan_lyzunov]

Hi Irmhild,

This is exactly what I was trying to do. I saved the SPA_1 value in the Subnetwork MD LocationProduct attribute, but the change was rejected. The fact is that I have a PL, where Location is the root attribute, and Subnetworks is a non-root attribute. It is not clear what non-roots are in PL for? Will planning at this level for subnetworks become impossible if I remove this non-root Subnetwork from the PL?

[dmitriikarpov976]

That's right,

This PL was added to the initial instance later but by an SAP service user. After LOCATION PRODUCT deletion SUBNETWORK assignment works well.

Many thanks)