Does anyone have any insights on what intended functionailtyis available to handle Obsolescence and Supersession linkages between Parts? On the surface it does not look like Alternate or Substitute Parts (MPM-Link Functionality maybe?) do the job.
It would be great if there were a better way than changing the Name Attribute to "Obsolete - Use XXXXXXX" manually.
It would be even better if New Part Requestscould be integrated into a Change Notice Implementation Plan at the same level as Change Tasks and there were something equivalent to a Change Tasks and/or New Part Request that created a supercession linkage (likea special change task type thatheld the Part to be made Obsolete {Affected Object}open and active until theNew Part [Resulting Object]that replaced it were set up, and landed at Receiving ready for Implementation/Effectivity and then set theState to "Obsolete" [or eq] and created the supercession linkage.
Am I missing the obvious? Is this functionality available, buried or otherwise?
Dare to Dream right?
Cheers, Keir
