SAP ABAP IMG Activity SIMG_CMMENUOLQNOQNS1 (Maintain Catalogs)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ QI (Package) QM IMG and area menu
IMG Activity
ID SIMG_CMMENUOLQNOQNS1 Maintain Catalogs  
Transaction Code S_ALR_87004476   IMG Activity: SIMG_CMMENUOLQNOQNS1 
Created on 19981222    
Customizing Attributes SIMG_CMMENUOLQNOQNS1   Maintain catalogs 
Customizing Activity SIMG_CMMENUOLQNOQNS1   Maintain Catalogs 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CMMENUOLQNOQNS1    

In this section, you define the contents of the notifications while also taking the next step into consideration (defining the catalog profiles). This means that you must:

  • Define which elements (for example, catalog entries, short text, long text) of the notifications will be used and which information these elements will contain
  • Organize and maintain the catalogs that are used for the notifications and the defects recording function

Example

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

  • Problem descriptions (coding) at the notification header level
  • Defect criteria at the notification item level
    • Defect type
    • Defect location
    • Defect cause
  • Tasks and activities
    You can define tasks and activites on two levels in the notification:
    • Notification header (immediate tasks, immediate activities)
    • Notification item (tasks, activities)

      Important: in the notifications, you can only use code groups at the plant level (and not selected sets). As an alternative, you can limit the selection of available catalogs with the help of the catalog profile.

Activities

  1. First determine which elements in the notification are to contain information that can be described with the help of terminology catalogs.
    The answer to this question generally depends on:
    • The scope of the required quality documentation
    • The evaluations that are required for quality control purposes

      The answer may also depend on the purpose and origin of the notification. The information may be different for:

    • Complaints against vendors
    • Internal problem notifications
    • Customer complaints

      On the basis of this criteria, you can later define different notification types, each with their own catalog profile.

  2. After you clarify this, organize and create the catalogs you need.
    1. Define the catalogs in a directory for catalog types.
      With the help of the predefined catalogs, you can define the catalog profiles for the individual notification types later.
    2. Maintain the contents of the catalogs.

Refer to the chapter Quality Planning -> Basic Data -> Catalog for detailed information about the organization of the catalogs.

Further notes

For the 'defect type' and 'defect location' fields in the notification items, the system uses the keywords from the corresponding catalog types as field descriptions.
The field descriptions in the defect records are predefined.

The catalog processing function does not have a transport link. Enter the details and final entries for the catalogs in the target system!

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CMMENUOLQNOQNS1 0 ALR0077563 O  
SIMG SIMG_CMMENUOLQNOQNS1 1 BIO0000031 O  
SIMG SIMG_CMMENUOLQNOQNS1 2 HLA0006831 Creating Quality Notifications 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_TQ15 V - View SM30 Define Catalogs 
V_QPGR_CL C - View cluster QS41 Edit Catalogs 
History
Last changed by/on SAP  19991116 
SAP Release Created in