Time Ticket Confirmation for Secondary Resources 
Use
You can use this function to perform time ticket confirmations directly from within production by using a process message. Thus, one process message sent from production is enough to confirm all activities performed for a secondary resource along with the resource used.
You can confirm the following data:
Activities performed (for example, machine time, labor time, duration, or energy consumption)
Secondary Resource
You can also confirm secondary resources as follows:
Time ticket confirmation
Manually from within the area menu for process orders
If you use the relevant transaction for time ticket confirmation, you can also update standard values and confirm HR data.
Time event confirmation
Using a process message from within the PI sheet or the process control system
For more information, see:
Manually from within the area menu for process orders
In contrast to time ticket confirmations, you only confirm a single time event, such as the start or end of a secondary resource or a single activity, per process message.
See also:
Integration
You can request process messages for time ticket confirmation from within the PI sheet or the process control system in a process instruction.
You can, for example:
Define a process data request for the PI sheet to request a time ticket confirmation for a specific secondary resource
Define a process message subscription for process control systems to request time ticket confirmations for all secondary resources that were created during order execution
Customizing of the SAP reference client contains several sample process instruction categories for time ticket confirmation. For general information on process instructions, see Process Instructions .
Prerequisites
The control key that has been assigned to the secondary resource allows confirmation.
The process order has been released.
No time event confirmation has been created for the secondary resource so far.
Features
The following data is available for time ticket confirmations for secondary resources in the standard system:
Process message category PI_SRCON
Message destination PI15
Process data request SR_CON for time ticket confirmations for secondary resources from the PI sheet
The following sections describe what you must bear in mind when you create the process messages.
Secondary Resource
For the system to be able to identify the secondary resource, you must specify the item number of the secondary resource and the phase number to which it belongs.
Activities
You can enter up to six standard values in a phase. The number and meaning of the standard values depends on the standard value key assigned in the primary resource. In the process message, you can confirm the actual activity performed for each standard value entered for a phase. The characteristics for activity confirmation are numbered in the same order in which the standard values and its activities are displayed in the process order.
Indicator: Remaining Work for Activity
You use this indicator to specify if you expect further confirmations for the activity in question.
Confirmation Text
In the short text, you can, for example, describe the reason for the variance.
Posting Date
If you do not want to post the confirmed quantities for the current date, you can enter any other date within an allowed posting period (backdating and postdating permitted). If you do not specify a posting date in the message, the system posts the confirmation on the date when the message was created ( Event date characteristic).
Status for Activity Confirmation
The status shows whether secondary resource processing has been completed.
The following table provides an overview of possible confirmation statuses:
Confirmation 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. |
Consistency Checks
When processing the messages, the system checks whether the values they contain are valid and consistent with one another. If an inconsistency (for example, an invalid order number) is discovered:
The system writes a corresponding system message to the message log
The system sets the process message status 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 order confirmation function.
Confirmation Number
The system assigns a unique number to each confirmation. The number is written to the message log.