Entering content frameProcess documentation Symptom Definition Locate the document in its SAP Library structure

Purpose

You define a symptom using various types of information. The user later conducts searches based on this information. A comprehensive symptom explanation can greatly simplify a search for solutions, offering a variety of methods or categories by which the user can search.

Process Flow

  1. You enter the basic data and classification of a symptom as detail information. The detail information includes:

The symptom type is the highest categorization level of a symptom in the SDB.

You can define various categories for each symptom type.

You can assign customized code groups and codes from a catalog to a symptom according to symptom type.

You create priorities in Customizing and then assign these priorities to symptoms.

The subject profile is a collection of code group profiles across multiple catalogs. The subject profile can be structured.

You define where or for what situation the symptom applies. You can use a table in Customizing to define your own application areas.

You can customize a list of validation categories independent of the symptom type.

You enter the date range from and to which the symptom is valid.

A symptom can have one of two statuses, created or released.
  1. You enter a text description of the symptom. You can also upload texts from other sources. If necessary, you enter descriptions in multiple languages. For more information, see Maintaining Descriptions in Multiple Languages.
  2. If applicable, you define the following for the symptom:
Leaving content frame