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.