Customizable UDF's for Engineering Masters and Work Orders

marvin-schultz

The short question: Is it possible to have different customizable UDF's or required fields on Engineering Masters and Work Orders?

Long explanation:
Our products require data proofs whenever we have a new product, a product changes, or when we produce them at a new vendor. For audit purposes, we have to track the dates and reasons of the most recent data proofs.

My solution to this was to create customizable UDF's in the WO with required fields to indicate if a data proof is required, and the reason. This way if we try to save a WO without updating the fields, we get an error. However, if they are required on the WO, they'll also be required when we build a new EM, and the data will carry over when we create new WO's from EM's, and the buyer could forget to update the fields.

In an ideal world, I would like to have a field on the EM that inicates the date of the last data proof, and have required fields on the WO's that requires the buyer to stop and think. This way, we could track the process entirely in the system and eliminate the need for external tracking.

Any suggestions?

unknown

Kristy,

You seem to have two issues. One is a method to track the last “data proof” date and reason for it. The second is an indicator on if a new “data proof” is required and for what reason. I see these as two separate items.

Tracking suggestion is to put the information on the last data proof date and reason on a UDF in the part maintenance record.

For the second item of “determination if a new data proof is required”, that would require human intervention [although I bet you could create a macro that would walk thru the criteria and give you a pop up that a new proof is required]. That may be the way to go. Think it thru and if you can logically put together a selection sequence, then you can build the macro to prompt the creator of the work order that a new proof is required.

Since you may have many work orders and many masters for the same product, the suggestion on the use of the PM record should give you a more stable location for recording the proof information for the audit purposes. Good luck with the macro.