Reporting Completions

Completed units are received into inventory when quantities are reported as complete for the last operation for an item, using Repetitive Labor Transaction (18.14). Components can be backflushed when completed units are received if the components are linked to the last operation.

Note: For each change in the quantity complete at a milestone operation, the quantity complete at all of the previous non-milestone operations is changed to reflect the fact that the later operation was completed.

If completions are recorded on nonscheduled dates, the reporting of quantities on these dates causes entries to be automatically added to the repetitive schedule.

If you report completions for today’s date using Repetitive Labor Transaction, the report has the following effects:

• Inventory is incremented by the completion amount. A backflush occurs. Component inventory is shown as issued to the repetitive order. The requirements for components at all previous non-milestone operations are decremented. Floor stock items are accounted for.

• If there is a scheduled amount for today, the quantity completed is incremented and the quantity open decremented until the scheduled quantity is reached. These quantities can be reviewed in Operation Schedule Report (18.2.5).

• If there are previous non-milestone operations, the quantity completed at each previous operation is also incremented, up to the amount required to make the scheduled amount of the finished item.

• If the quantity open at the last operation is still nonzero, indicating the quantity completed is less than the quantity scheduled, the quantity open is treated as supply by MRP, and shown as the current amount of the planned order in MRP Detail Inquiry (23.16). See Material Requirements Planning.

The Consume Forward, Consume Back, and Start of Week settings in Repetitive Control (18.24) determine how the system handles item completions that exceed the quantity scheduled on a given day. For example, you may complete some items ahead of schedule or scrap fewer items than expected. When this occurs, the system follows these steps to record the excess completions against other exploded schedules:

1 The system searches for a scheduled order routing with a start and due date range that includes the effective date of the repetitive labor transaction. If the system finds scheduled order routings that meet this criterion, it applies the excess completions to their corresponding schedules, starting with the schedule that has a due date closest to the reporting transaction effective date.

2 If excess quantities still remain after the previous step has executed, the system subtracts the number of days specified in the Consume Back field from the reporting transaction effective date. It then searches for exploded schedules with due dates that are between this day and the effective date. Schedules with due dates that are before the day specified in the Start of Week field are not considered.

Starting with the schedule that has the earliest due date, the system consumes open scheduled quantities until all available quantities are consumed or all excess completions have been recorded against a schedule.

Note: When Start of Week is set to Today, the system does not consider the Consume Back value when searching for open schedule quantities to consume. Only the Consume Forward setting is used.

3 If excess quantities still remain after the system has consumed open quantities on past schedules, the system adds the number of days in the Consume Forward field to the reporting transaction effective date. It then searches for exploded schedules with due dates that are between this day and the effective date.

Starting with the schedule that has a due date closest to the transaction effective date, the system consumes open scheduled quantities until all available quantities are consumed or all excess completions have been recorded against a schedule.

When Consume Back and Consume Forward are both 0 (zero), the system simply transfers excess completed quantities to inventory and does not report them against a repetitive schedule. This also occurs when the system runs out of open schedule quantities to consume.