Show TOC

 Time Event Confirmation for Phases Locate this document in the navigation structure

Use

You use this function to confirm time events for the phases of a process order control by sending a corresponding process message in process control. You can confirm the following time events:

  • Processing time events for particular points in time (for example, start, finish)

  • Time events for variable activities

See also:

Completion Confirmations in the Process Order

Prerequisites

  • Standard values with record type group Processing or Variable activity have been maintained in the standard value key of the corresponding primary resource.

  • The control key that has been assigned to the phase allows confirmation.

  • The process order has been released.

Features

You can use the following process messages and destinations to confirm time events:

Time event

Message category

Destination

Processing time event

PI_PHST

PI05

Time event for variable activity

PI_PHACT

PI11

The following sections describe what you must bear in mind when you create process messages.

Process Messages for Processing Time Events

Time event:

You determine which time event you want to confirm by entering the corresponding phase status in the process message.

You can confirm the following time events or statuses:

Time event / status

Meaning

Start

Partial confirmation: Processing of the phase has been started.

You also need to set this status when you continue executing a phase after an interruption.

Finish

Final confirmation: Processing of the phase has been finished.

Interruption

Partial confirmation: Processing of the phase has been interrupted.

Partial finish

Partial confirmation: Processing of the phase has not yet been finished, but the yield obtained so far is to be confirmed.

In the process message, you use the characteristics for the event date and time to specify the confirmed point in time.

Yield to be confirmed:

Depending on the time event, you can also use the process message to report the yield obtained for the phase. The yield is processed as follows:

  • Time events Start and Interruption :

You cannot confirm a yield.

  • Time event Partial finish:

In this case, you can use the process message to confirm a yield.

  • Time event Finish :

If you specify a yield in the process message, this quantity will be confirmed. Otherwise, the system confirms the planned yield, that is, the operation quantity.

Yield that you confirm using time event Finish is added to yields that have been confirmed using time event Partial finish .

Resource:

For the time event Start, you can also confirm that a different primary resource was used than planned. To do so, you include the characteristics used for the resource name and plant of the resource in the process message.

Process Message for Variable Activities

Time event:

To determine the time event you want to confirm, you enter the corresponding status in the process message.

You can confirm the following time events or statuses:

Time event / status

Meaning

Partial finish

Partial confirmation: Resource usage has not yet finished, but the activity performed so far is to be determined.

Finish

Final confirmation: Resource usage has finished.

If no specific time event is contained in the process message, the system automatically sets status Partial finish.

Variable activity:

You use the parameter ID of the standard value to determine the activity you want to confirm in the process message. The parameter must be defined in the standard value key that is assigned to the phase via the primary resource.

You enter the activity performed and, if required, the unit of measurement for this parameter in the process message.

General Notes on Message Processing

The following applies to both processing time events and variable activities.

Additional confirmation data:

If required, you can also confirm a short text for the confirmation and the reason for deviating from the planned data.

Consistency checks:

When processing the message, the system checks whether the values contained in it are valid and consistent with one another. If an inconsistency is discovered (for example, an invalid order number or a time event that is not allowed at the current processing stage of the phase):

  • The system writes a corresponding error or warning message to the message log

  • The system sets the status of the process message to Destination erro r or Sent with warning

Subsequent processing:

All further processing of the data confirmed is carried out according to the general logic of the confirmation function.

Confirmation number:

The system assigns a unique number to each confirmation. The number is written to the message log.