Skip to main content

Hi All,

We use UNSPCS classification standard for Part numbers. Accordingly, there are instances where the “Part No’ and ‘Node ID’ could have the same value. In such instance, when trying to connect the part to the node, it gives below error message.

However, Node ID and Part No are two different things, where we are not trying to create another Node with same Node ID, it’s that we are trying to connect a part with same value for the node. This error is observed in App10 UPD9. Is this a bug? Is it corrected in any latest update? Thanks.

 

Hi,

With the current design, it is impossible to add a Part number same as the Assortment ID or Node ID in an Assortment. This is due to a technical constraint and therefore the recommendation is to use different IDs for Parts and Nodes.

Hi @Upasari Contents well noted and many thanks for your kind clarification. 

Just wanted to leave my surprise about the explanation: a technical constrain? Seems to me a design failure, but I don't know all the in and outs of the API/SVC in place for this maintenance.

Reply


Terms & ConditionsCookie settings