Okay folks… file this one under “imaginary database fields”.
In Engineering Workbench, Method of Manufacturing > Materials > List, you can scroll down the Collection of available fields to find MtlRevisionNum (which as seems logical will be the Revision Number of this material part to use for this parent part and revision). In Method Tracker you can also link to this field.
There is no corresponding database field in the Erp.ECOMtl table.
In past lives (both V8 and E9) there have been instances where Epicor puts fields in various OTHER tables before moving them to the right place (notably the PO Release Lock Qty/Lock Date fields in E9 that actually lived in the ComXRef table).
Any idea if this is the case here, or if this value somehow lives in another view (or quantum dimension)?
Good question. The field also appears in the ECOMtl and PartMtl result sets. We implemented a UD field to handle material revision because we could never find a way to use the ‘real’ one.
Do you suppose it’s just calculated based on the effective date? Try running it with a different effective date (PartRev) and see if it changes. Just a thought.
The less-likely scenario is the infamous PATCHFLD table.
Effective Date DOES have something to do with it. I changed the material part to a subassembly (checked the Pull As Assembly box) and then created a job… it gave me an ERROR saying that there was no approved revision with an Effective Date on or before 9/30/2018.
So just for fun I changed the effective date on the material revision part to 8/27/2018, and added ANOTHER revision for that part with an effective date of 10/15/2018.
Engineering Workbench would ONLY save the newest revision. If I changed it, it would change it back on save. Okay, so I checked it in with the NEWER revision selected.
Then I created a job.
The material part came over with the OLDER revision.
