Show TOC

Maintain Catalogs

In this step, you structure the content of the notifications based on the following definition of catalog profiles. This means:

Example

Depending on the scope of your catalog profile, you need catalogs, for example for:

You can define tasks and activities at the following levels of a notification:

Activities

1. First, decide on the notification elements that are to contain the information you require. This information is represented using catalogs of terms.
This decision depends on:
The decision can also depend on the cause and the purpose of the notification.
You can therefore subsequently define different notification types according to these criteria, with each one having its own catalog profile.
2. Organize the catalogs you require, once you have made your decision.
a) Define the catalogs in a catalog index.
You then use these predefined catalogs to structure the catalog profiles for the individual notification types.
b) Maintain the catalog content.
You can find detailed instructions on how to organize catalogs in the section Planning -> Basic Data -> Catalogs.

Further Notes

The system copies the keywords that have been maintained for the relevant catalog types into the fields 'defect type' and 'defect location' as field descriptions.
The field descriptions are fixed in the defect data records.

The catalog has a manual transport link. When you call up this transport link, you can select individual code groups or codes and include these in an transport request. Long texts are not transported in this request.
SAP recommends that you treat catalogs as master data and only maintain them in the productive system.