Milestone Confirmation
Use
The milestone confirmation is a special form of confirmation, in which the confirmation of one operation causes other operations or suboperations to be automatically confirmed at the same time.
Milestones are operations that have the corresponding indicator in the control key.
You use milestones, for example, if you have included inspection operations that require confirmation.
Features
Operations can be defined as milestone operations in their control keys . If a milestone operation is confirmed, then previous operations are automatically confirmed.
Example
Operation 30 is marked in its control key as a milestone operation. You partially confirm operation 30 with a quantity of 100 pieces. Operations 20 and 30 are then also partially confirmed with the same quantity.
Observe the following special features:
If several operations in an order are marked as milestones , the processing sequence of these operations must be adhered to when carrying out confirmations. In this case, automatic confirmation is effective up to the preceding milestone within the operation sequence.
Example
Operation 30 and operation 50 are marked in their control keys as milestone operations. First, you must confirm operation 30. By confirming operation 50, you only automatically confirm the preceding operation 40.
You can define whether the planned scrap percentage rate is incorporated in the quantity calculation for automatically generated confirmations. You make this setting in Customizing for
Shop Floor Control
by choosing
Operations
Confirmation
Define Confirmation Parameters
(
Generated confirmations
without quantity adjustments
,Generally Valid Settings
tab page):
If the indicator is not set , the planned scrap percentage rate is used for the quantity calculation. The yield as well as the scrap are displayed.
If the indicator is set , then the scrap is posted as yield in the automatically confirmed operations. The confirmed total quantity is identical in the milestone confirmation and in the automatically generated confirmations.
If a milestone operation is confirmed, all preceding suboperations up to the next milestone operation are also automatically confirmed. Suboperations of milestone operations must always be confirmed manually.
Example
Operations 10, 20, 30 and 40 each have a suboperation. Operation 20 and operation 40 are marked in their control keys as milestone operations. You confirm operation 20 with a quantity of 50 pieces. The system automatically confirms operation 10 with the same quantity and its suboperation with its corresponding activities. You then confirm operation 40 with a quantity of 100 pieces. The system automatically confirms operation 30 (+ suboperation) with the same quantity (+ activity). You must confirm the suboperations for operation 20 and 40 manually.
Operations that have already been manually confirmed are not affected by milestone confirmations.
Example
Operation 30 is marked in its control key as a milestone operation. You partially confirm operation 10 manually with a quantity of 50 pieces. You then finally confirm operation 30 manually with a quantity of 100 pieces. Operation 10 is still partially confirmed with a quantity of 50 pieces; operations 20 and 30 however are finally confirmed with quantities of 100 pieces.
If you enter a milestone confirmation for an operation, it receives the status MILE (milestone confirmation) and the status MCNF (manually confirmed). The automatically confirmed operations also receive the status MILE. If you use the transaction for entering progress confirmations, the operation also receives the status MILE.
Example
You enter a confirmation for milestone operation 30. It does not matter which transaction you use. Operation 30 receives the statuses MCNF and MILE. Operations 10 and 29 receive the status MILE.
In collective orders , you can use milestone confirmations to confirm operations of more than one order simultaneously (see Example: Confirming Collective Orders ).
In milestone confirmations, planned activities are always posted on the basis of the confirmed quantity. If you have entered activities manually during a milestone operation, planned activities are also confirmed when the preceding operations are automatically confirmed. The exception to this is the setup times, which are always confirmed fully, independently of the entered quantity
Example
You enter a confirmation of 7 pieces for milestone operation 30, which has a planned yield of 10 pieces. Operation 20 is confirmed automatically. The planned machine time for operation 20 is 40 minutes, therefore a machine time of 28 minutes is confirmed.