Kontakt

Ansicht
Dokumentation

QAM_TEXTCAT_QIM - Define Settings for Text Types

QAM_TEXTCAT_QIM - Define Settings for Text Types

General Data in Customer Master   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you can make settings that are dependent on text types.

In issue processing, a number of different text areas are available in which you can enter descriptions for issues, issue resolutions, or activities, for example. A text area comprises the fields for description, detailed description, codes, and code groups. Specific text types were defined in Customizing for the fields of a text area under Cross-Application Components -> Processes and Tools for Enterprise Applications -> Reusable Objects and Functions for BOPF Environment -> Dependent Object Text Collection -> Maintain Text Schema.

Note:
The other settings that you can make in the Customizing activity for a text schema are not active in SAP Quality Issue Management (QIM).

The text types are grouped in a text schema. In the standard system, SAP supplies a text schema for each issue category (issue, defect, cause, and effect) and for the activity categories.

In QIM Customizing, the text schema is displayed together with the text types for an issue category or activity category under Define Settings for Issue Categories and Define Settings for Activity Categories. The assignment cannot be changed.

You can, however, extend the text schema by including your own text types in it. You must then add the new fields for creating texts to the Web UI configuration so that they are displayed on the interface. In addition, you must extend the filter for the text types in the FPM feeder parameters to include the new text types.

The text schema becomes effective in the application by the assignment of the issue or activity category to an issue type or activity type.

You control authorization for different text types using the authorization object for Descriptions (/IAM/TXTTY).

You have created codes under Quality Issue Management -> Issue Processing -> Codes -> Define Codes.

You have created catalogs and assigned codes and code groups to the catalogs under Quality Issue Management -> Issue Processing -> Codes -> Define Catalogs and Code Groups.

In the standard system, separate catalogs are supplied for issues, defects, causes, effects, and activities and assigned to the respective text types. This means the respective catalog is set as the default in the application when searching for codes and only those codes are displayed that belong to the issue or activity category.

Default Value for Catalog:

In this activity, you can specify a catalog depending on the text type, which is displayed in the application as the default value when searching for codes.

For example, you can specify that when you create an issue in the Issue Resolution screen area, the catalog Cat_1 is proposed by default for the search for codes if you assign the catalog Cat_1 to the text type ISOLU. The text fields in the issue resolution area, that is, code, code group, and detailed description belong to the text type ISOLU.

Historical Texts:

For each text type, you can specify that a history is stored for the long texts entered in the various text areas. You can specify the following settings for freezing long texts:

  • Always new version: Long texts are frozen following each change.
  • New version on change of user or language: Long texts are frozen if the text is changed by a different user or in a different language.
  • No historical text: Long texts are not frozen as historical.

The frozen long texts are displayed in their own text area and cannot subsequently be changed.

For each text type, a history is displayed directly beneath the respective long text field, sorted according to the time of entry. The newest text is at the top. There is also an overview of the historical texts of all text types, also sorted according to the time of entry.

The display of the historical texts is integrated in the advanced processing of issues, in individual processing of activities, and in the hierarchy view.

  1. In Customizing for reusable objects, the text types IDESC and ISOLU were defined and assigned to the text schema QIM_ISSUE.
  2. The text schema was assigned to the issue category QIM (quality issue) under Issue Processing -> Define Settings for Issue Categories.
  3. In the standard system, the issue category quality issue was assigned to the issue type QI1. Thus, the text schema QIM_ISSUE with the text types ISOLU and IDESC applies for the issue type.
  4. In Customizing for QIM under Basic Settings -> Text Types -> Define Settings for Text Types, the catalog ISS (issues) was assigned to the text type IDESC and the catalog RES (resolutions) was assigned to the text type ISOLU.
  5. In addition, in the standard system under Issue Processing -> Define Issue Types in the folder Code Groups, the code group ISS_000001 (issues) was specified as the proposal for the text type IDESC and the code group RES_000000 (resolutions) was specified as the proposal for the text type ISOLU. (For activities, you make these settings under Issue Processing -> Define Activity Templates.)
  6. When you create an issue with the issue type QI1, in the standard system the fields in the search for codes and code groups are preset accordingly in the text areas Issue Overview and Issue Resolution.
Note:
If a code group is preset when you search using the Codes field, no default value is specified for a catalog to avoid contradictory selection conditions. If, for example, a catalog was specified as a default value that does not contain the code group, the selection result would not contain any hits.





Fill RESBD Structure from EBP Component Structure   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 6977 Date: 20240523 Time: 201748     sap01-206 ( 126 ms )