This document explains how you create an error symptom text and how this text is connected to an alias number, service kit and service expense.
An error symptom text has been created. The error symptom text:
When error symptom texts are created, the Error symptom file (SERSYM) is updated.
The error symptom text is used during service order entry to describe an error and to recommend repair. An error symptom text connected to a service kit, alias number or service expense is used to speed up the service order entry for known errors and preventive service.
If the error symptom text is to be connected to a service expense, an item, a service kit or an alias number, the respective prerequisites must be met:
Create error symptom text
Start 'Error Symptom Text. Open' (SOS410/AB).
Enter a name for the error symptom text in the 'Error symptom' field.
Select "New" to create a new error symptom text and to go to the E panel.
Enter a description and a name of the error symptom text in the Description and Name fields.
Enter a detailed description of the error symptom in the 'Error symptom' field.
Select whether the error symptom text is to be connected to an error cause, individual item, item, service expense or service kit.
Connect error symptom
Select an error cause that is to be associated with the error symptom text.
The error cause is displayed in (SOS120/E2) during service order entry
Connect an individual item and/or group of individual items to the error symptom text in the 'Individual item number' and 'Individual item group' fields.
This will restrict the usage of the error symptom text to errors reported on the specified individual items.
Enter an item in the 'Item number' field or a service expense, an alias number or a service kit in the 'Service expense' field to connect them with the error symptom text.
The connected item/expense is defaulted during service order entries for assignments with this error symptom text.
Check and if necessary change the defaulted information in the fields:
Press Enter to save the error symptom text.
|Program ID/Panel||Field||The field indicates…|
…the error symptom to which the error symptom text is connected.
You may enter optional error symptom texts for general usage or direct them to an individual item group, individual item number or item number.
A stated error symptom text code must have been entered in the system. This entry is made in (SOS410).
|(SOS410/E)||Description||…a description of the current identity.|
|(SOS410/E)||Name||…the name of the error symptom.|
|(SOS410/E)||Error symptom text||
…the text that describes the error symptom for an individual item.
You may also use the text to describe a request for actions needed.
The error symptom text may be retrieved automatically from the predefined error symptom texts by selecting F4 = Prompt in the 'Error symptom code' field.
In order to use a predefined text, the 'Error symptom text 1' field must be blank.
…a predefined error cause.
The error cause can either be for general usage or directed to a certain individual item or item.
The error cause is displayed in 'Service Order. Open Line' (SOS120/E2). The error cause can be connected to an individual item, an item, a service expense, an alias number or a service kit.
|(SOS410/E)||Individual item number||
…the unique number for a machine.
For each individual item number, the history regarding service carried out, defects and defect codes, measures taken, replaced parts, etc, can be stored. A maximum of 15 alphanumeric characters can be used as an individual item number.
|(SOS410/E)||Ind 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 error symptom text entry. This enables you to search for common error symptoms 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 no||…the unique ID for the item connected to the error symptom text.|
…the service expense proposed when a service order line with the error symptom text is created.
Instead of a service expense, you can enter an alias number or a service kit here.
If you use this predefined error symptom at service assignment entry, default values for a service expense, an alias number or a service kit can be proposed for the assignment from this error symptom. This field is optional, but if used will simplify the entry of the service order lines.
|(SOS410/E)||Name||…a description of the service expense.|
|(SOS410/E)||Qualification||…a code for the skills needed to perform a service assignment with this error symptom text.|
|Pln 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 action text that are specified when a service assignment is entered.
A condition in which no work hours would be indicated is when, for instance, a predefined error symptom is obtained for the service order.
Any planned time obtained may be changed when the service assignment is entered.