SAP ABAP IMG Activity CA_NCC (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 CA_NCC Maintain Catalogs  
Transaction Code S_ALR_87100714   (empty) 
Created on 19991122    
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 CA_NCC    

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

  • You define the structural elements of the notification that are to be used and the information these elements are to contain.
  • You organize and maintain the catalogs that are used in the notifications and when defects are recorded.

Example

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

  • Subject matter (coding) at notification header level
  • Defect attributes at notification item level
    • Defect type
    • Defect location
    • Defect cause
  • Tasks, activities

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

  • Notification header (immediate tasks, immediate activities)
  • Notification item (corrective tasks, corrective activities)

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 scope of documentation required
    • The evaluations required

      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.
    1. Define the catalogs in a catalog index.
      You then use these predefined catalogs to structure the catalog profiles for the individual notification types.
    2. 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.

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 
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  19991124 
SAP Release Created in