ECO Approval Problem

[harmeyerjr]

We implemented the ECO module last week. Only BOM corrections are flowing through the process at this time. All other BOM changes are being handled through the BOM Revisions application.

We are having an issue regarding the approval process. We have elected to set up approval routings specific by branch plant. Our issue is as follows: any one with access to the approval application can approve/reject an ECO that is in process for another user. Is there a way to prevent users from approving/rejecting ECOs in process for other users?

Thank you in advance.

 

[rekblad]

Would it work to implement Br/Plt security (to prevent approvers in plant A from approving Plant B) and then program security that would allow only those approvers who you want to have access?

If that won't work, then a ruler across the knuckles.... ;-)

 

[harmeyerjr]

Unfortunately, we believe the ruler across the knuckles is our only recourse. We have defined a report to determine where users approve for other users. We have also establish application security. Branch plant security will not work for us because some of the approvers need to approve for multiple plants.

Thank you for your input.