Confirmations are the premise for progress control and the basis for cost charging of internal activities performed for the order. For this reason, confirmations are carried out by the shop floor workers as promptly as possible. You can confirm individual phases or entire orders. Due to the different requirements that arise in practice, SAP provides several different options for posting confirmations.
Confirmation Options

Depending on your business requirements, the system offers various variants for order confirmation:
Process order confirmation on order header level
In this scenario, you enter a confirmation for the entire order. If you enter a confirmation on order header level, the system confirms all phases that have a control key in which confirmation is possible or required. The quantities confirmed in the operations are proportional to the quantities confirmed in the order header. You can either confirm the order in one confirmation posting or post multiple order confirmations until the order quantity was reached. After posting an order confirmation, the system sets a respective confirmation status on order header, operation, and phase level.
Time ticket confirmation
In this scenario, you enter a confirmation for each (confirmation relevant) phase in the order. Similar to the previous case, you can either confirm each phase in one confirmation posting or post multiple phase confirmations until each phase of the order is fully confirmed. After posting a phase confirmation, the system sets a respective confirmation status on phase, operation, and order header level.
Milestone confirmation
In this scenario, you also confirm the order on phase level. However, by assigning a respective control key to the phases, you define some of the phases as milestones. You must only post confirmations for milestone phases. At the same time, the system automatically confirms the non-milestone phases which lie in between the milestones.
Time event confirmation
In this scenario, you confirm the phase start and finish times for each phase. The system calculates the duration based on the time difference between the start and end of the phase.
After posting the confirmation, the order, operation, and phase status values are updated to either partially confirmed (PCNF) or confirmed (CNF).
An order is partially confirmed if at least one but not all of the phases that require confirmation are confirmed (phase status PCNF or CNF). An operation is partially confirmed if at least one but not all of the operation's phases that require confirmation are confirmed (phase status PCNF or CNF). An order is also partially confirmed if all the phases requiring confirmation are finally confirmed, but there are confirmable phases that are partially confirmed. An operation is also partially confirmed if all the operation's phases requiring confirmation are finally confirmed, but there are confirmable phases that are partially confirmed.
An order is finally confirmed when all phases for which confirmation is required are finally confirmed (status CNF) and when there are no confirmable phases that are partially confirmed (status PCNF). An operation is finally confirmed when all the operation's phases for which confirmation is required are finally confirmed (status CNF) and when there are no confirmable phases that are partially confirmed (status PCNF).
Example of an Phase Confirmation

In the figure, an example of an phase confirmation and the effect of the confirmation posting to the order is displayed. When confirming the phase, you provide, for example, the following information:
Operation quantities: Yield, scrap, and rework
The yield quantity is the amount of partially produced quantities that are produced so far in this phase. The scrap quantity is the amount of partially produced quantities that had to be scrapped when you executed this phase. If required, you can provide additional information in text form or even create quality notifications. The rework quantity is the amount of partially produced quantities that cannot be transferred to the next manufacturing phase due to, for example, quality reasons. After you've eliminated the quality deficiencies, the respective quantities reenter the planned production flow.
Actual dates
You enter the actual start and finish date of an phase which can be used for analysis purposes or rescheduling of subsequent production phases.
Phase activities
You enter phase activities, for example, setup time, machine time, labor time, and so on, to confirm how much time effort was invested into the phase. For each phase activity, the system calculates the respective costs using information maintained in the resource and charges these internal activities to the order.
If configured in the phase control key, the confirmation also triggers the automated goods receipt of the manufactured quantities. The goods receipt quantity corresponds to the yield quantity. Furthermore, if components are marked as backflushed, the confirmation triggers the goods issue posting of the respective components. The goods issue quantities of the components are carried out in proportion to the sum of all three confirmed phase quantities according to the BOM relationships.
Note
Refer to the course code S4C40, which is a prerequisite course for this course, if you want to learn more about process order confirmation.
For more details about the complex topic of confirmations, also refer to the SAP application help.
Prerequisites for Confirmations
Regardless of the confirmation option you select, confirmation parameters must be defined in the configuration activity, Define Confirmation Parameters for each order type and plant in order to be able to post confirmations.
To be able to use user-specific layouts for time ticket confirmations, you must set up confirmation profiles in the configuration activity, Define Single-Screen Entry for Confirming Process Orders.
For an phases to be confirmed, the control key for the phase must be set accordingly. The control keys contain information whether an phase is a milestone phase, or whether a phase must, can, or cannot be confirmed. The control keys are defined in the configuration activity, Define Control Keys.