Show TOC

Function documentationProblem Details

 

You can use problem details to describe problems. Users can conduct searches based on this information.

Features

Field

Use

Problem Type

Highest level at which you can categorize a problem. Depending on how your system administrator has configured the problem type, it can determine:

  • Default value for the Problem Subtype field and the other possible values for this field, and the default value for the Priority Type field.

  • Catalog to be used if you specify a code, location, damage, or cause when maintaining a problem of this problem type.

  • Default value for the Solution Type field. When you create a problem of this problem type and go to create a solution and link it to the problem, this default value is proposed automatically.

Note Note

Configure problem types in Customizing for Customer Relationship Management, by choosing Start of the navigation path Enterprise Intelligence Next navigation step Solution Database Next navigation step Problems Next navigation step Define Problem Types End of the navigation path.

End of the note.

Problem Subtype

Subdivision of the problem type. For example, if you have the problem type Computer Accessories, you may want to have the problem subtypes Ergonomic Accessories, Media Storage, Printer Accessories, and so on.

Problem subtypes are defined by your system administrator in Customizing for Customer Relationship Management, by choosing Start of the navigation path Enterprise Intelligence Next navigation step Solution Database Next navigation step Problems Next navigation step Define Problem Subtypes for Each Problem Type End of the navigation path .

Code

Individual problem code in a problem code group.

You can use the problem code group and problem code to classify the problem. For example, you could have the problem code group Media for media storage. This problem code group could contain problem codes such as CD for CD storage and MS for multimedia storage.

The problem code groups and problem codes that can be assigned to a problem are contained in the problem catalog that is assigned to the problem type by your system administrator. (In the above example, the problem catalog could be Computer Accessories.) As a result, the problem type determines which problem code groups and problem codes you can assign to a problem of this problem type.

Catalogs, code groups, and the individual codes in each code group are defined by your system administrator in Customizing for Customer Relationship Management, by choosing Start of the navigation path Enterprise Intelligence Next navigation step Solution Database Next navigation step Basic Data Next navigation step Catalog Maintenance Next navigation step Define Catalogs End of the navigation path and Define Code Groups and Codes for Catalogs

Priority Type

2-character ID that, together with the priority level, describes the priority.

Priority types are defined by your system administrator in Customizing forCustomer Relationship Management, by choosing Start of the navigation path Enterprise Intelligence Next navigation step Solution Database Next navigation step Basic Data Next navigation step Priorities Next navigation step Define Priority Types End of the navigation path.

Priority Level

Single character (for example, 1, 2, or 3) that indicates the priority (for example, 1 could be high, 2 medium, and 3 low) of the priority type.

You may want to use this field to indicate how quickly the problem has to be resolved.

Priority levels are defined by your system administrator in Customizing for Customer Relationship Management, by choosing Start of the navigation path Enterprise Intelligence Next navigation step Solution Database Next navigation step Basic Data Next navigation step Priorities Next navigation step Define Priorities for Each Priority Type End of the navigation path.

Application Area

Groups together similar problems. Unlike the problem subtype, the application area is not dependent on the problem type.

Application areas are defined by your system administrator in Customizing for Customer Relationship Management, by choosing Start of the navigation path Enterprise Intelligence Next navigation step Solution Database Next navigation step Problems Next navigation step Define Application Areas End of the navigation path.

Valid-From Date

Date from which the problem record is valid.

Valid-To Date

Date to which the problem record is valid.