Issue that has been brought up by order entry for customer parts that
are being requoted at a new rev. Below is a message from my order
entry group:
What is the best way for estimating to process and save revision
changes so all concerned are aware of the change?
Old Way of saving revisions to the part master maintenance.
We used to requote parts and save the requote over current methods,
but then change the revision # back to the old rev. as a flag. This
way, operations are correct, and the new revision level is then saved
when the job is engineered.
We historically have not saved old revisions in part master
maintenance. Some feel we are loosing valuable information/history by
deleting old revisions from our system.
New way of saving revision changes to the part master maintenance.
When estimators quote a new revision level on a part, that
quote is saved to part master maintenance unapproved.
These are now being saved as new revision levels.
We are now saving old revision levels for a history of all
revision changes.
Problem:
When order entry enters an order, if the new revision level has been
saved and approved, it does not flag order entry that there is a
revision change.
Order entry needs to know so they can flag the job as a rev
change and know if it needs to be reprogrammed.
Order entry needs to know so they can check inventory and
have old revision stock parts updated or tossed.
It has been suggested to unapprove the rev. with a note in the
description (rev change) to flag order entry. This note (rev change)
would be removed when the job is engineered. The fact that the rev is
unapproved would flag order entry to see what revision the last job
was run at.
Suggestions?
are being requoted at a new rev. Below is a message from my order
entry group:
What is the best way for estimating to process and save revision
changes so all concerned are aware of the change?
Old Way of saving revisions to the part master maintenance.
We used to requote parts and save the requote over current methods,
but then change the revision # back to the old rev. as a flag. This
way, operations are correct, and the new revision level is then saved
when the job is engineered.
We historically have not saved old revisions in part master
maintenance. Some feel we are loosing valuable information/history by
deleting old revisions from our system.
New way of saving revision changes to the part master maintenance.
When estimators quote a new revision level on a part, that
quote is saved to part master maintenance unapproved.
These are now being saved as new revision levels.
We are now saving old revision levels for a history of all
revision changes.
Problem:
When order entry enters an order, if the new revision level has been
saved and approved, it does not flag order entry that there is a
revision change.
Order entry needs to know so they can flag the job as a rev
change and know if it needs to be reprogrammed.
Order entry needs to know so they can check inventory and
have old revision stock parts updated or tossed.
It has been suggested to unapprove the rev. with a note in the
description (rev change) to flag order entry. This note (rev change)
would be removed when the job is engineered. The fact that the rev is
unapproved would flag order entry to see what revision the last job
was run at.
Suggestions?