Entering content frame

Function documentation Problem Maintenance Locate the document in its SAP Library structure

Use

Problems can be described using, for example, free-text descriptions and customized details and attributes (like problem type/subtype and locations, damages, and causes). Users later conduct searches based on this information, so when you maintain problems, it is best to describe them as fully as possible.

You can create, change, and display problems. You cannot delete them.

Prerequisites

See Solution Database.

Activities

Creating a Problem

...

       1.      Access problem maintenance (see Solution Database).

       2.      Choose Create.

(SAP GUI only) You can also define a problem using a reference. For example, if the problem you want to define is similar to an existing problem, you can copy the existing problem's data and change it as required. You do this using the Create From field.

       3.      Choose a problem type from the possible entries and press Enter.

A problem number is assigned automatically. Depending on how the problem type has been configured in Customizing for the Solution Database, other fields are filled automatically.

The (short) description is created automatically from the first 40 characters of the long text.

       4.      Enter your data as required. See also:

¡        Structure linkProblem Details

¡        Structure linkShort Descriptions and Long Texts in Multiple Languages

¡        Structure linkValidation Categories

¡        Structure linkLocations, Damages, and Causes

¡        Structure linkLinked Solutions / Linked Problems

¡        Structure linkFrequently Asked Questions (FAQs)

¡        (SAP GUI only) Structure linkBusiness Objects

       5.      When you are ready, release the problem. (On the PC UI, you do this on the Problem Details tab page using the Problem Status field.)

Only released and compiled problems will be found in searches. For information on compilation, see Indexes. If you compile the SDB indexes, and subsequently change the problem, you must recompile the SDB indexes; otherwise your changes will not be found in searches. For this reason, the indexes should be compiled regularly.

Note

If you subsequently change the status of a problem from Released, you must recompile the SDB indexes, otherwise the problem will continue to be found in searches.

       6.      Save your data.

Searching for Problems and Solutions

You can search for problems and solutions by text and/or by details (like problem type) and/or by attributes (like locations, damages, and causes).

If you search by text, details, and attributes, the hit list will contain only problems or solutions that match all of your search criteria.

If you enter more than one criterion of the same type, for example, two problem types or two solution types, the hit list will contain problems or solutions that belong to one of the specified problem types.

If you enter several criteria of different types, for example, two problem types and three validation categories, the hit list will contain problems or solutions that belong to one of the specified problem types AND have at least one of the specified validation categories.

 

Leaving content frame