Symptom Definition
Definition
Detail information contains basic data and basic classification of a symptom. The detail information includes:
· Symptom Type
Symptom type is the highest level of grouping and categorizing features of symptom in SDB. Major customized tables are related to the symptom type. All the catalogues used to define code groups and codes must pre-defined with a symptom type.
· Symptom Category ( Dependent on Symptom Type)
A list of customized categories is available for each symptom type.
· Symptom Code ( Dependent on Symptom Type)
One catalogue with customized code groups and codes can be assigned to a symptom type.
· Symptom Priority
Multiple catalogues can be customized. The priority is independent of symptom type. However, a default catalogue can be assigned to a symptom type.
· Symptom Catalogue Profile
Catalogue profile is independent of symptom type. However, a default catalog profile can be assigned to a symptom type.
· Symptom Application Area
A list of options can be customized. Symptom application area is independent of symptom type.
· Symptom Validation Category
A list of options can be customized. Validation category is independent of symptom type.
· Symptom Validation Dates
From- and to- validation dates.
· Symptom Status
SAP R/3 standard status management. Two statuses, Created and Released, are valid for the release 4.6A.
Use
The detail information provides a set of highly customizable entries to classify or categorize symptoms created under various conditions, used by various departments and different purposes.
Definition
Symptom type describes of different types of symptoms. Symptom types are the highest level of grouping and categorizing feature of symptom records in the SDB. Each symptom type allows to default various code groups, catalog types, profiles and priority groups for symptoms. Each default value is allowed to be overwritten in a single symptom record.
Definition
Symptom categories are the next level of categorization for symptoms, after symptom types. Multiple symptom categories can exist per symptom type. Each symptom can be categorized with one allowed symptom category according to its symptom type.
Definition
A catalog customized via IMG provides categories for the different symptom type.
Definition
Priority of a symptom customized via IMG.
Definition
A profile contains accessible catalogues for symptoms.
Definition
Symptom application areas are free defined attributes. All possible application areas have to be defined in the customized table.
Definition
Symptom validation category is an additional freely defined feature to classify symptoms. All possible values for validation categories have to be defined in the customized table.
Definition
R/3 standard status management.
Create/Change/Display Descriptions Using a Text Editor
Use
Create/change/display free text descriptions using a text editor. During the process to create/change/display a symptom, the text editor is a box on the right-hand screen where user can directly type in texts as in most full-screen editor.
Procedure
1. In the detail screen with a navigation tree on the left-hand side, the symptom text editor is located at the Symptom sub-screen on the right-hand side of the navigation tree.
2. The standard keys such as insert, delete, page up, page down, home, end and arrow keys can be used to move around on the text editor.
3. Mouse can also be used to select a block of text for cut, copy, delete and paste. Right mouse buttons will bring a menu where additional features can be executed.
4. Click on the right mouse button, there are two important functions where users can download or upload texts from and to local workstations.
Result
The first line of the text typed in the symptom will become the short-text description of the symptom. However, the text will not by populated into the navigation until user makes an action that refreshes the screen, such as press ENTER, push a button, or double-click on the tree.
Create/Change/Display Multi-lingual Descriptions
Use
The free text descriptions can be maintained in multiple languages. This feature provides convenient way for knowledge engineers to edit the symptom free-text descriptions without logging on to the server using different languages.
Procedure
1. In the Symptom sub-screen with a navigation tree on the left-hand side, the multi-lingual editors can be activated by pressing on the More button (a green right-arrow with three dots).
2. A dialog box will show a short description and all existing descriptions in different languages. User can directly enter descriptions and define the language using F4 help.
3. Once the short description and the language are assigned, a change/display button will show on the most right field. By clicking on the button, user can enter the long-text descriptions of the selected language.
Result
The first line of the text typed in the symptom free-text editor will be transferred to the multi-lingual dialog-box as the short description.
Definition
Problem locations are possible entries customized in a catalogues that describe where the problem is located using the code groups and the codes. The problem locations can be mapped to the object parts in Notification.
Procedure
1. On the toolbar of detail screen where the navigation tree is on the left-hand side, Problem Locations can be added under the symptom by pressing the Problem Location button.
2. A dialog box will show a tree diagram including code groups and codes. Multiple codes can be selected by marking the check boxes of code entries.
3. Press Copy button to finish the selection.
Result
The problem locations will be added to the default symptom which is the one whose information is shown on the symptom sub-screen. For multiple linked symptom, single click or double click on a selected symptom or any sub-nodes under the symptom before start the procedures described above will result in adding problem locations into the selected symptom even it is not a default symptom.
Definition
Problem damages are possible entries customized in a catalogue that describes what type of damages is observed for a problem location.
Procedure
1. On the toolbar of detail screen where the navigation tree is on the left-hand side, Problem Damages can be added under the symptom by pressing the Problem Damage button.
2. A dialog box will show a tree diagram including code groups and codes. Multiple codes can be selected by marking the check boxes of code entries.
3. Press Copy button to finish the selection.
Result
The problem damages will be added to the default symptom, which is the one whose information is shown on the symptom sub-screen. For multiple linked symptom, single click or double click on a selected symptom or any sub-nodes under the symptom before start the procedures described above will result in adding problem damages into the selected symptom even it is not a default symptom. If single click or double click on a problem location, the selected problem damages will be added under the problem location as the hierarchy structure. Notice that the problem damages can not be added under a problem cause. If user click on a problem cause before adding the problem damages, the problem damages will not be added under the problem cause, but rather added under the Problem Analysis node under the Symptom node.
Definition
Problem causes are possible entries customized in a catalogue that describes what causes the damage observed for a problem location.
Procedure
1. On the toolbar of detail screen where the navigation tree is on the left-hand side, Problem Causes can be added under the symptom by pressing the Problem Causes button.
2. A dialog box will show a tree diagram including code groups and codes. Multiple codes can be selected by marking the check boxes of code entries.
3. Press Copy button to finish the selection.
Result
The problem causes will be added to the default symptom, which is the one whose information is shown on the symptom sub-screen. For multiple linked symptom, single click or double click on a selected symptom or any sub-nodes under the symptom before start the procedures described above will result in adding problem damages into the selected symptom even it is not a default symptom. If single click or double click on a problem location or problem damage, the selected problem causes will be added under the problem location or the problem damage as the hierarchy structure.
Create a Link to an Existing Business Object
Use
Link business objects as the symptom content.
Procedure I
1. Press the Business Object button in the detail screen where the navigation tree resides.
2. A new dialog box will show the available business objects that can be linked. Those business objects are customized through IMG. Select a business object or double click on the list.
3. Another dialog box will show and ask for key which should be the identification number.
4. Using the F4 help to search the existing business objects, and select the target one.
Procedure II
1. Click the right mouse button on the node of the Symptom node or the Business Object node.
2. Choose add business object.
3. A new dialog box will show the available business objects that can be linked. Those business objects are customized through IMG. Select a business object or double click on the list.
4. Another dialog box will show and ask for key which should be the identification number.
5. Using the F4 help to search the existing business objects, and select the target one.
Procedure III
1. Click the right mouse button on the node of an existing Business Object Type node.
2. Choose add business object.
3. A dialog box will show and ask for key which should be the identification number.
4. Using the F4 help to search the existing business objects, and select the target one.
Procedure IV
See Wizard: Add Business Object.
Result
The business object will be linked and the new node will be shown on the navigation tree and the business object sub-screen accessible through the symptom tabstrip.
Use
Navigate to a business object linked to the symptom.
Procedure I
See Display a Business Object from the Navigation Tree.
Procedure II
See Display a Business Object from the Table.
Hierarchy vs. Non-hierarchy Structures
Definition
Hierarchy structure means that the problem damages and problem causes can be sub-nodes of the problem location, and problem causes can be sub-nodes of the problem damage. The non-hierarchy structure or called flat structure will treat problem locations, problem damages and problem causes as parallel sub-nodes under the Problem Analysis node of the Symptom node. See also Selection of Wizard Steps.
Use
Create a empty new symptom, or create a symptom using a referenced symptom or referenced notification.
Procedure I - Create an empty new symptom
1.
Execute transaction IS01 .2.
Make sure that the Symptom Number and Notification Number inside the Reference frame are empty.3. Click the Create button in the Symptom sub-screen.
Procedure II - Create a new symptom with referenced symptom
1.
Execute transaction IS01 .2.
Fill in the Symptom Number to be copied.3. F4 help for the symptom number field can assist user to locate the existing symptom
4. Click the Create button in the Symptom sub-screen.
Procedure III - Create a new symptom with referenced notification
1.
Execute transaction IS01 .2.
Fill in the Reference Number to be copied.3. F4 help for the reference number field can assist user to locate the existing notification.
4. Click the Create button in the Symptom sub-screen.
Procedure IV - Using the wizard
See also Create a Symptom, Create a Symptom with a Symptom Reference, and Create a Symptom with a Notification Reference under the Step-by-step Guide (Wizard).
Result
A detail screen will be shown in the window with the navigation tree on the left-hand side, and an expanded symptom screen and a reduced solution screen on the right-hand side. A new symptom assigned a new number is created with all content copied from the referenced object if assigned. If the reference object is notification, the structure in notification will be mapped to a symptom. If the content of the notification can not be mapped to a symptom, all the information will be converted into free-text descriptions to prevent any information loss.
Use
Change an existing symptom.
Procedure I - Change a symptom with a known symptom number
1. Execute transaction IS01.
2. Enter the symptom number on the same row of the Create, Change and Display buttons.
3. Use F4 help if need to search the completely SDB.
4. Press the Change button.
Procedure II - Change a symptom recently edited
1. Execute transaction IS01.
2. Look at the table list titled My Recently Edited Symptoms.
3. Find the symptom to be changed.
4. Double click on the symptom.
5. Press the Display/Change Toggle button (the first button) on the toolbar to switch to the Change mode after going to the detail screen with the navigation tree.
Procedure III - Search and Change a Symptom
1. Execute transaction IS01.
2. Press the Other Object button (the first one) on the toolbar and switch to the search screen.
3. Type in the search criteria to find the matched symptoms. See Search Existing Symptoms.
4. Double click on the symptom.
5. Press the Display/Change Toggle button (the first button) on the toolbar to switch to the Change mode after going to the detail screen with the navigation tree.
Procedure IV - Using the wizard
See also Change a Symptom under the Step-by-step Guide (Wizard).
Result
The symptom selected will be loaded from the database. Then, a detail screen will be shown in the window with the navigation tree on the left-hand side, and an expanded symptom screen and a reduced solution screen on the right-hand side in the change mode.
Use
Display an existing symptom.
Procedure I - Display a symptom with a known symptom number
1. Execute transaction IS01.
2. Enter the symptom number on the same row of the Create, Change and Display buttons.
3. Use F4 help if need to search the completely SDB.
4. Press the Display button.
Procedure II - Display a symptom recently edited
1. Execute transaction IS01.
2. Look at the table list titled My Recently Edited Symptoms.
3. Find the symptom to be displayed.
4. Double click on the symptom.
Procedure III - Search and Display a Symptom
1. Execute transaction IS01.
2. Press the Other Object button (the first one) on the toolbar and switch to the search screen.
3. Type in the search criteria to find the matched symptoms. See Search Existing Symptoms.
4. Double click on the symptom.
Procedure IV - Using the wizard
See also Display a Symptom under the Step-by-step Guide (Wizard).
Result
The symptom selected will be loaded from the database. Then, a detail screen will be shown in the window with the navigation tree on the left-hand side, and an expanded symptom screen and a reduced solution screen on the right-hand side in the display mode.
Use
Search the existing symptoms using the search engine.
Procedure I
1. Execute transaction IS01.
2. Press the Other Object button (the first one) on the toolbar and switch to the search screen.
3. Type the free-text descriptions for text search (fuzzy search).
4. Click on the buttons listed on the top of the criteria grid control.
5. Different criteria including symptom details, business objects, problem locations, problem damages, and problem causes can be selected as criteria to conduct the attribute search (exact search).
6. Press the Search Symptom button.
Procedure II
See also Search Symptoms under Wizard.
Result
A list of matched symptom will be shown on the screen, or the dialog box if the wizard is executed.