This document explains how you create an action and how this action is connected to an alias number, service kit and service expense.
An action for common service assignments has been created.
The action text:
When an action text is created, the Measure file (SMECOD) is updated.
If the action is to connected to:
If the action is to be searchable per:
Start 'Service Action. Open' (SOS412).
Enter an ID for the action in the Action field.
Select "New" to create a new action and to go to the E panel.
Enter a description and a name of the action in the Description and Name fields.
Select whether the action is to be connected to an individual item, an item, a service expense or a service kit.
Enter an action class to be used in the invoicing statistics in order to classify costs and revenues.
Connect an individual item and/or group of individual items to the action in the 'Individual item number' and 'Individual item group' fields.
This will enable you to search for common actions per individual item or group of individual items.
Enter an item in the 'Item number' field or a service expense, an alias or a service kit in the 'Service expense' field to connect them with the action.
The connected item/expense is defaulted during service order entries/reporting for assignments with this action.
Check and if necessary change the defaulted information in the fields:
Press Enter to save the action.
|Program ID/Panel||Field||The field indicates…|
…the action performed for service order assignments or its service order lines.
If an action for a service order assignment is entered, it will be proposed by default for all service order lines, but may be changed.
An action may also be entered for each service expense, thereby overriding the default action. The action is saved in the invoice statistics file (OSBSTD).
|(SOS410/E)||Description||…a description of the current identity.|
|(SOS410/E)||Name||…the name of the action.|
…a classification of an action.
Action classes are stored in the invoice statistics file (OSBSTD), where, for example, the addition of revenues and expenses for each action class may take place.
|(SOS410/E)||Individual item number||
…the unique number for a machine.
By entering an individual item number you can later search for common actions for a specific individual item.
|(SOS410/E)||Individual item group||
…a grouping of individual items with the same owner, same brand/model or any other common characteristics.
An individual item group may be entered during action entry, thus enabling a search for common actions for a particular group of individual items.
A group also makes it possible to collect statistics for each group of individual items.
|(SOS410/E)||Item number||…the unique ID for the item connected to the action.|
…the service expense defaulted when a service order line with the action is reported or created.
Instead of a service expense, you can enter an alias number or service kit here.
If you use this predefined action at service assignment entry, default values for a service expense, alias number or service kit can be defaulted for the assignment from this action.
This field is optional, but if used will simplify entry of the service order lines.
|(SOS410/E)||Name||…a description of the service expense.|
|(SOS410/E)||Qualification||…a code for the skills required to perform a service assignment with this action.|
|Planned work hours||
…the time required to perform a service assignment.
All time is considered except preparation time, travel time and finish time.
Planned work hours can be obtained from error symptoms, error causes, action messages or actions specified when a service assignment is entered.
A condition in which no work hours would be indicated is when, for example, a predefined error symptom is obtained for the service order.
Any planned time obtained may be changed when the service assignment is entered.