Engineering workbench problem

Now if only they had tried to resequence that method as well - they would
have seen the major problem with the EWB....

Diane Rowberry
Westwood Precision, Inc.


-----Original Message-----
From: James Piper [mailto:admin@...]
Sent: Monday, February 10, 2003 12:05 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Engineering workbench problem


Epicor just sent me this as a fix for the Engineering workbench problem
I am giving it to my head engineering guys to test

Thougth it would help to pass this along to the group

Good luck



-----Original Message-----
From: Web Leads [mailto:WebLeads@...]
Sent: Monday, February 10, 2003 1:59 PM
To: 'admin@...'
Subject: Change Request 8621MPS has been closed.


Summary: ABOM: deleted operation or material reappears in the
workbench
Description: Page 8621MPS

Issue:

Deleted operations and materials keep reappearing in the Engineering
Workbench

Steps to Reproduce:

1) Inv Mgt > MFM > Part Master > Hilite a part > select a
revision
below.

2) Click Revision > Check Out to a Group different from the
group
used later in this document.

3) Again click Revision > Engineering Workbench ( EWB ).

4) While in the EWB > Approve the part's rev > click Revision >
Select
Check In. Puts the rev back in the part master.

5) Repeat steps 1 and 2 above to check out the same part's same
revision to a different group in the EWB. (part 8400S-617 rev A was
used
here)

6). Highlight an operation or material and delete it. ( used
operation 20
here) Either thru the menu, Operation > Delete or Right Click > Delete.


7) Click Revision > Update >Approve the rev.

8) Revision > Check In, back to the part master.

9) Repeat steps 1 and 2, to Check Out the same part and rev
again.
Doesn't matter what Group is chosen this time.

10) Revision > EWB > look at this rev and the deleted operation or
material reappears. (In the ECOOpr table here)

11) Can see this formerly deleted operation on the methods master
report. The formerly deleted material will also show on the BOM listing
or BOM Cost Report.


SCR 5469 is available on 5.20.311.

This SCR also applies to call 836698MPS, about the same problem with
materials.

Tester's note: in order to duplicate this, add the following steps
before the steps in this call. (already done above)

1) In the Part Master, select the part revision, and check the part out
to a group different from the group used later in this call.
2) In the Engineering Workbench, approve the part, and check it back
in.

Since the Vantage 5.20 CRM project (SCR 3196) changed the BOM check-in
code
(bm/bmm10-gd.i) to log any ECO changes, it has deleted a part operation
or material only if no ECO operation or material exists for the same
company, part number, and revision. But if the same revision was
checked in for a different group, an ECO operation or material will
exist, and the part operation or material will not be removed. Instead,
the code should remove part operations and materials if no ECO operation
or material exists for the same company, group ID, part number, and
revision.

WORKAROUND:
To prevent the problem, users can check out the same part revision to
the same ECO group each time. Once the problem has occurred, the
workaround is to reduce the operation's production standard to 0.
Epicor just sent me this as a fix for the Engineering workbench problem
I am giving it to my head engineering guys to test

Thougth it would help to pass this along to the group

Good luck



-----Original Message-----
From: Web Leads [mailto:WebLeads@...]
Sent: Monday, February 10, 2003 1:59 PM
To: 'admin@...'
Subject: Change Request 8621MPS has been closed.


Summary: ABOM: deleted operation or material reappears in the
workbench
Description: Page 8621MPS

Issue:

Deleted operations and materials keep reappearing in the Engineering
Workbench

Steps to Reproduce:

1) Inv Mgt > MFM > Part Master > Hilite a part > select a
revision
below.

2) Click Revision > Check Out to a Group different from the
group
used later in this document.

3) Again click Revision > Engineering Workbench ( EWB ).

4) While in the EWB > Approve the part's rev > click Revision >
Select
Check In. Puts the rev back in the part master.

5) Repeat steps 1 and 2 above to check out the same part's same
revision to a different group in the EWB. (part 8400S-617 rev A was
used
here)

6). Highlight an operation or material and delete it. ( used
operation 20
here) Either thru the menu, Operation > Delete or Right Click > Delete.


7) Click Revision > Update >Approve the rev.

8) Revision > Check In, back to the part master.

9) Repeat steps 1 and 2, to Check Out the same part and rev
again.
Doesn't matter what Group is chosen this time.

10) Revision > EWB > look at this rev and the deleted operation or
material reappears. (In the ECOOpr table here)

11) Can see this formerly deleted operation on the methods master
report. The formerly deleted material will also show on the BOM listing
or BOM Cost Report.


SCR 5469 is available on 5.20.311.

This SCR also applies to call 836698MPS, about the same problem with
materials.

Tester's note: in order to duplicate this, add the following steps
before the steps in this call. (already done above)

1) In the Part Master, select the part revision, and check the part out
to a group different from the group used later in this call.
2) In the Engineering Workbench, approve the part, and check it back
in.

Since the Vantage 5.20 CRM project (SCR 3196) changed the BOM check-in
code
(bm/bmm10-gd.i) to log any ECO changes, it has deleted a part operation
or material only if no ECO operation or material exists for the same
company, part number, and revision. But if the same revision was
checked in for a different group, an ECO operation or material will
exist, and the part operation or material will not be removed. Instead,
the code should remove part operations and materials if no ECO operation
or material exists for the same company, group ID, part number, and
revision.

WORKAROUND:
To prevent the problem, users can check out the same part revision to
the same ECO group each time. Once the problem has occurred, the
workaround is to reduce the operation's production standard to 0.