I have a situation in MRO, some Modifications found not included to tab "Modifications" in relevant Disposition Shop order. When I check I see those MOD REVs exist in Work Scope Task has been Obsolete but new revision has been created.
Question is, if the “define work scope” consists an Obsolete modification revision will it not included to Disposition Shop order?
Appreciate your assistance here.
Thanks,
Kasun
Best answer by Iroshan
If the modification is already include to work scope, please do the following to remove.
Go to Change Work scope Tasks → Modification and select All Running radio button.
select the modification code and un-tick the “include in Workscope?” check box.
save the changes.
you might get errors, and will have to deal with them as per the situation.
To include new revision, select the modification from Change Work scope Tasks → Modification → All Not Complied Tab.
The ideal way should be when a modification is in Obsolete state, it should not be allowed to include to any work scope. Rather the new revision should be visible in Change Work scope Tasks → Modification → All Not Complied Tab.
An item made obsolete means it has ended the life, thus shouldn’t be considered for including to another work scope.
The ideal way should be when a modification is in Obsolete state, it should not be allowed to include to any work scope. Rather the new revision should be visible in Change Work scope Tasks → Modification → All Not Complied Tab.
An item made obsolete means it has ended the life, thus shouldn’t be considered for including to another work scope.
Hope this helps.
Thanks and Regards
Iroshan
Many Thanks Iroshan, It seems those new revisions of modifications has been created later but older ones still remain in work scope. Can we include new revisions here back to the work scope removing obsolete one, then how? Thanks again.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.