One of the main reasons that the Epicor Requestions seem to get a bad rap is because it doesn’t seem to be designed to fit typical manufacturing and it’s further poorly designed and executed.
In this example, Epicor provides fields on the Requisiton to specify the Manufacturer & Manufacturer Part number but then when the Requisition is approved and the PO Suggestion created the Manufacturer & Mfg Part data is not passed along to the PO Suggestion, and thus never makes it to the PO and then Suppliers send the wrong parts or are calling back for further specification.
I opened and Epicor Case on this expecting it to be a bug, but after several months they tell me development determined this was ‘standard behavior.’ Data loss through a Business Process is standard behavior. There are at least two types of bugs, Design & Code. However it seems like some issues are only evaluated for Code bugs and are sent to development for that. However, I think these types of issues should also go to a Product Manager or something to determine if there is a Design bug and if so then they would issue a fix.
Sorry for the rant…
Regardless, they sent me to Epicor Ideas, so I have posted the idea here and I would appreciate any votes anyone can spare:
Requisition PO Suggestion: Include Mfg & Mfg Part from | Kinetic Ideas (aha.io)
BTW - In the meantime I have ‘patched’ this bug with a Data Directive that adds the missing data when the PO Suggestion is created.
Thanks!