Ansicht
Dokumentation

QAM_VC_GQI_TYPE_CAT - Define Access to Quality Issue Types

QAM_VC_GQI_TYPE_CAT - Define Access to Quality Issue Types

Fill RESBD Structure from EBP Component Structure   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

The issue type is one of the most important selection criteria in the worklist of an issue processor. So the issue processor can select all issue types from various systems in the same manner in his or her worklist, in this Customizing activity you can make the following settings for access to issue types from different source systems:

  • By selecting an object category, you specify which issue types are available for selection in the value help in the worklist.
  • You specify which source systems issue types can be read from.
  • You can use value mapping to consolidate the selection of quality issue types from different source systems.
  • You can view and delete logs relating to access and make settings for the logs.
  • If you use Enterprise Services for access to quality issue types, you also require a service connection for the services used.
  • If you want to use ID mapping, you must have activated the business function MDG_FOUNDATION.

We deliver the following object categories including mapping and BAdI implementations:

  • QIT_NOTIF: Notification types in an ERP system
Use this object category if the notification types that you stored in an ERP system are adequate for you as issue types.
  • QIT_QAM: Generic issue types in Quality Issue Management
Use this object category if you want to consolidate issue types from different systems in QIM (for example, notification types in an ERP system and the issue types created in QIM). The cross-system issue types are stored in the Customizing activity Define Generic Quality Issue Types.

If you require other object categories, create them in the Customizing activity Define Object Categories for Issues, Activities, and Issue Types. For these, you must also have created and activated an implementation for the Business Add-In BAdI: Access to Generic Quality Issue Types (BADI_QAM_QUALITYISSUETYP_CAT). For more information, in particular about the interfaces used, see the documentation for the Business Add-In.

Proceed as follows:

  1. On the initial screen, enter as the reference system category the object category that includes the list of issue types that are to be available when you select an issue type in the worklist.
  2. As the reference system, enter the logical system in which this list can be found. For the object category QIT_QAM, this is the local system.
  3. Change to the Object Categories view.
To be able to grant authorizations for access to an object (authorization object S_RFC), you can find the RFCs that are used for access for each category using the Implementation Information pushbutton.
  1. If you have a harmonized system landscape, no additional ID mapping is necessary. If individual values in the systems differ, you must execute an ID mapping. To do this, proceed as follows:
    1. Select the object category and, under System-Dependent Settings, enter the source system for which you want to specify the mapping.
    2. Set the indicator for the ID mapping and choose the icon to display the mapping relationships.
    3. Under List Agency ID, enter the logical system for which you want to execute the mapping.
    4. As the list ID, enter QAM_QI_TYPE.
    5. Define the value mapping for the system by entering a mapping combination for all entries of the generic quality issue types.
  2. In the system-dependent settings for the object category, specify which system the issue types are to be read from by entering the logical system and setting the Active indicator.

In this Customizing activity you can view and manually delete the logs that are written by the system for each access to an object category. You can also make the following settings:

  1. Specify the lowest problem class the messages that are displayed in the log must have.
  2. Specify after how many days a log is to be deleted automatically.






Addresses (Business Address Services)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 4831 Date: 20240523 Time: 193332     sap01-206 ( 98 ms )