Show TOC

 Entering Confirmations Locate this document in the navigation structure


A confirmation documents the processing status of orders, operations, suboperations, and individual capacities.


You can enter a confirmation for the following:

  • For an operation

    You have the following options:

    • To confirm quantities, durations, activities, or personnel data, enter a time ticket confirmation or a progress confirmation.

    • To make a confirmation at a particular point in time (for example, at the start of setup or the finish of processing), enter a confirmation for a time event.

    • When you confirm time events, the system calculates the required duration. For example, the setup duration is the time between setup start and setup finish.

  • For an order

    If you enter a confirmation at order header level, the system confirms all the operations that have a control key in which confirmation is optional or necessary. The quantities confirmed in the operations are proportional to the quantities confirmed in the order header.

  • By using another confirmation as a reference

    You can copy the data from a confirmation that has already been made to the current confirmation. Enter the number of the reference confirmation to identify it.

    Note Note

    Control keys are assigned to the individual operations in the routing. They control

    • Whether a confirmation for an operation is necessary, possible, or not possible An operation is confirmable if a confirmation is possible. An operation requires confirmation if it has to be confirmed.

    • Whether the operation should have milestone confirmation

    End of the note.

    Note Note

    Confirmation changes the status at operation header level or order header level (PCNF = partially confirmed, CNF = finally confirmed). An order is partially confirmed if at least one but not all of the operations that require confirmation have been confirmed (operation status PCNF or CNF). An order is also partially confirmed if all the operations requiring confirmation have been finally confirmed, but there are confirmable operations that have been partially confirmed. An order is finally confirmed when all operations for which confirmation is required have been finally confirmed (status CNF) and when there are no confirmable operations that have been partially confirmed (status PCNF).

    If you are confirming an operation, you can decide if it is a partial or final confirmation. This decision can be taken automatically; the system examines the confirmed quantity and then decides ( Partial/Final Confirmation indicator in the confirmation parameters, see Confirmations: Fixed Parameters ). An operation that was confirmed manually also receives the status MCNF (manually confirmed).

    End of the note.

    Note Note

    Once you have entered a confirmation for an operation, you cannot confirm at order level. If you want to confirm the whole order, you must cancel the confirmation at operation level.

    The same is true at operation level for a time ticket and time event confirmation for the same operation.

    End of the note.
Collective Entry

You can use collective entry to enter several confirmations on an operation basis, on one screen. Collective entry has the following advantages:

  • You can adapt the table in which the confirmations are entered individually (table control).

  • You can define various settings in Customizing (identification with order number or confirmation number, default settings for actual data).

  • Various types of input help are available (enter default values, suggest actual data).

For more information, see Entering Collective Confirmations .

Fast Entry

Fast Entry is a type of time ticket confirmation that has the following advantages:

  • You can enter several confirmations on one screen.

  • The system does not set any locks.

  • The system only executes limited checks.

One of the main features of fast entry is the decoupling of the processing functions from online data entry. The process, up to the complete update of the confirmations, is as follows:

  1. You enter the confirmations .

  2. The confirmations are marked. If you want to, you can display these confirmations ( Displaying Marked Confirmations ).

  3. To update the marked confirmation, schedule program CORUPROC1 as a background job. To do this on a regular basis, you can schedule program CORUPROC1 to run periodically.

    Depending on the settings in Customizing, Decoupling Processes Carried Out During Confirmation can be triggered during the confirmation update.

  4. If errors occur during the update, you can reprocess the error records ( Reprocessing Confirmations ). In this case, you use the same function as for processing error records from PDC data transfer.

Comparison of Collective Entry and Fast Entry

The screen and the entry flow are identical for both functions. There are the following differences in processing:

  • In comparison to collective entry, fast entry only conducts limited checks.

  • In fast entry the confirmations are marked first. In collective entry the confirmations are processed according to the confirmation parameters (possibly decoupled processes).

Single Screen Entry

Single screen entry provides you with a simple option for entering time tickets confirmations. You can design your own screen layout for single screen entry. This enables you to adapt it to the processes in your company.

The differences between this and Time Ticket Confirmation Without Single Screen Entry are:

  • All entries are carried out on an entry screen, that is, there is no initial screen.

  • The layout of the entry screen can be individually defined.

  • The detail areas can be opened and closed, that is, the data to be entered is not organized on a tab.

  • If the predefined screens are not sufficient, you can define your own screens in the customer enhancement CONFPP07.