If a work ticket is marked for the auto issuing or backflushing of labor, a Labor type transaction is automatically created for the work ticket.
An auto-issue labor transaction is created when the work ticket is released. The transaction is not automatically updated, so you can make changes to it if needed.
A backflush labor transaction is created when a completion entry is entered in Work Ticket Transaction Entry. As with an auto issue, the transaction is not automatically updated, so you can make changes if needed.
If the completion entry is a partial completion (for example, the work ticket planned quantity is 20, but the completion entry is for a quantity of 5), the backflush labor transaction is scaled according to the quantity completed.
Auto-issue and backflush transactions are updated when the Work Ticket Transaction Journal is updated.
When updating a partial completion and backflushing the labor, the labor transaction is updated before the completion entry. This ensures that the correct costs are included in the work ticket when the completion entry is updated.
Note When auto issuing or backflushing labor, the labor transaction does not include an employee number and is costed at the standard rate for the activity codes referenced in the work ticket steps.
