Ansicht
Dokumentation
QAMV_CATEGORY - Define Object Categories for Issues, Activities, and Issue Types
rdisp/max_wprun_time - Maximum work process run time SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
So you are able to display quality issues and quality activities from different systems in the Quality Issue Management (QIM) worklists, objects in QIM are decoupled from a specific data model.
The object category specifies which types of issues, activities, and issue types can be accessed in the worklists.
In this Customizing activity, you can create new object categories for the following object types:
- Generic quality issue (I)
- Generic quality activity (A)
- Generic quality issue type (QIT)
In the standard system, many object categories are supplied, including the following:
Generic quality issues:
- Quality issue in QIM
- Quality notification
- Service notification
- General notification
- Maintenance notification
- Claim
- FMEA defect
- Action-relevant audit question
Generic quality activities:
- Quality activity in QIM
- Quality notification task
- Service notification task
- General notification task
- Maintenance notification task
- Claim task
- FMEA action
- Audit action
Generic quality issue types:
- Notification type (ERP)
- Generic quality issue type in QIM
In general, the object categories supplied are sufficient to be able to use the worklists in QIM. If, however, you require additional object categories, create them in your customer namespace. For new object categories, you must also create a BAdI implementation to access them and activate it.
For newly created object categories and the default object categories supplied, specify in the respective Customizing activities which systems the data is to be read from and which object categories you actively wish to use:
Define Access to Quality Issues
Define Access to Quality Activities
Define Access to Quality Issue Types
BAL Application Log Documentation ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 2760 Date: 20240523 Time: 184743 sap01-206 ( 37 ms )