Identify All Changes with Conflicting Redlines
HI Raju,
Please elaborate your question. Do you want changes with conflicting part for particular parts? just all conflicting changes which are not yet released ? Or do you want the parts for which there are conflicting changes in the system?
Thanks,
Vaibhav
Probably easier to find all those assemblies/parts that have more than 1 unreleased change against them, and then go through those to see if anything is conflicting. To do this correctly, I would need to know what attributes I would need to look at (just BOM, or part attributes as well).
In some systems that I have worked on, each affected item is limited to 1 active/non-released change at a time (Agile does not do this). If you have 2 users creating a change against a part and modifying the part descriptions (for example) in different ways, then you may need to have better coordination between your users.
Note that part description is by definition a change-controlled attribute, but if you have P2/P3 attributes that are not change-controlled, then you cannot tell what change altered the value to what it is right now. The only way for this to work correctly is for the part attributes you want to compare be change-controlled, so you can see the value associated with each change (no record means no modification), and then see how they are different. That would involve working with the REDLINE_ATTRIBUTE and REDLINE_MSATTRIBUTE tables.