In version 10.1 and 10.2 I have several customers that are seeing quoting rates double for operations that precede an operation that is using Pieces per hour, pieces per minute. (with no production standard)
This happens if the default standard for the company is PM or PH
To recreate it - follow these steps:
On the method of manufacturing, enter in two operations.
For the first operation enter on 1 for production rate and select a production standard type of Minutes/Piece, Hours/Piece or Fix Hours
Go to worksheet and note – 1-hour labor.
On the second operation select Pieces/Minute, Pieces/Hour, Cycles/Minute*, or Cycles/Hour* (*version 10.2) – do not put any production standard in.
Go to worksheet and note – 2-hour labor.
Short term fix - change default production standard to MP or MH, create BPM to prevent having zero with PH or PM.
Epicor has moved this to a Problem state, but no date has been set.
We are also seeing this issue. I have also noticed it on operations per minute. However, if the zero production standard is in HP, HR, or MP there is no doubling of the labor. This was not an issue in 10.1.400.25, but is now occurring in 10.1.600.18.
When I saw this issue documented it didn’t make much sense that the behavior changed between versions; however, when you use “pieces per hour” or “pieces per minute” and leave the production standard at zero, you’re asking Epicor to plan and schedule the manufacturing of an item, and telling it that a particular operation will take forever to complete, since you can complete zero of them in an hour. IMHO the system should not allow these records to be created but since it allows them, I believe a warning would be in order when a user saves the quote opr, ECO opr, or job opr record. If the time required to complete an operation is zero or negligible, the correct way of specifying that is zero minutes per piece. Once again different versions of Epicor are found to treat undefined information in two different ways.
I added a warning before the document unit price field changes that looks for zero prod standards and the appropriate stdformat. If any are zero pieces per hour, it warns them to double check their quote.
Yet again, upgrading has caused more problems than it solved for us…