Good advise was already given – use Change Assistance to list objects and objects by SAR for a given ESU, it helps. To completely get rid of such a problems you can keep two interconnected platforms with DV, PY on one and only PD on the second, as some FDA-controlled companies do, but this out of scope of this case. During my training, I remember specifically hearing that it was alright to backup a work order out of status 99, fix the issue, and return it to status 99. ![]() Well, still you have some common things like data dictionary entries but chance to screw something there is small. In my company, it is fairly common for the manufacturing floor to close a work order and have it reach status 99 with the material issues being incorrect. I usually use a custom VaLidation path code to apply an candidate ESU into VL and to see which objects were actually applied – in most cases a lot of objects in the ESU are not applied because are already the same and you only need to do impact analysis only applied objects which greatly simplifies the process. ![]() ![]() In fact the ESU will not be installed in your path code, but you will have what you needed. ![]() If you need an ESU to fix a few objects but the ESU containing it has many others objects associated with different SARs then the best option is to install it to one path code only (for this a custom path code is best but can be any) and then promote the needed objects to the destination path code and forget all other objects.
0 Comments
Leave a Reply. |