SAP ABAP IMG Activity OLQN-OQN6 (Define Catalog Profile)
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
⤷ 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 | OLQN-OQN6 | Define Catalog Profile |
Transaction Code | S_ALR_87004469 | IMG Activity: OLQN-OQN6 |
Created on | 19981222 | |
Customizing Attributes | OLQN-OQN6 | Define catalog profile |
Customizing Activity | OLQN-OQN6 | Define Catalog Profile |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OLQN-OQN6 |
In this step, you define the catalog profiles for notifications.
The initial view for the catalog profile relates to notifications in general. In this view, you specify:
- Which catalogs and code groups from the individual catalogs should be used for the notifications.
If you enter a generic key for the code group, you can display a selection of the code groups contained in the catalog.
Use the special characters '+' and '*' for this purpose. For example, if you enter '+A*' in the field for the code group, the selection will only contain the code groups whose keys contain the letter 'A' in the second character position. - Which class in class type 015 should be proposed for the classification of the notification items.
You can use the classes to define general additional problem criteria flexibly, if the problem criteria in the data structure (defect type, defect location, defect cause) cannot be described adequately using the catalogs and texts.
For example, if you maintain the class 'problems in production' along with the class characteristic 'cause,' then you can record the causes of production problems as characteristic values. - The type of system message that will be issued, if you do not adhere to the assigned catalog profile.
Another view applies specifically to the defects recording function. In this view, you specify:
- The unit of measurement and number of decimal places to be used when you record the quantitative defect valuations.
In the defects recording function, you can valuate the defects quantitatively and, if necessary, assign a unit of measurement to the value. For example, you can use the potential for damage or the time and effort required to correct a defect as a criterion for weighting the defects.
Requirements
- You have defined the catalogs for the notifications.
Recommendation
- Configure the system to respond with an warning (category W), if the assigned catalog profile is not used.
Activities
- Define the required code groups for each catalog in the catalog profile.
- You should agree with all other catalog users how to best define the eight character mnemonic keys for the code groups. Make a note of the generics of the keys. For example, you can specify that separate code groups be created for each notification type and that the first two characters correspond to the notification type.
- Define the maintenance of the code groups. You can maintain the codes in retrospect.
- Determine whether you want to classify the notification items. If necessary, create the classes in the classification system and assign them to the catalog profile. The class characteristics should be defined and maintained at the same time.
Class type 15 is provided for classifying notification items.
If required you can record class characteristic values in a dialog box when you process classified notification items. - If you want to use the defects recording function, determine:
- Whether you want to valuate defects
- Whether a unit of measurement should be predefined in the catalog profile for this purpose. The unit of measurement must have been defined previously. Refer to the step Units of measurement in the chapter Basic Settings and Environment.
Further notes
- Each notification type is assigned a specific catalog profile.
You can also store a catalog profile in the material master. This catalog profile takes precedence over the catalog profile assigned to the notification type.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 2 | Optional 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 | OLQN-OQN6 | 0 | ALR0077563 O | |
SIMG | OLQN-OQN6 | 1 | BIO0000031 O | |
SIMG | OLQN-OQN6 | 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_T352B_CL | C - View cluster | SM34 | Define Catalog Profile | |||
V_T352B_F | V - View | SM30 | 9999999999 | Unit of Measurement for Defect Valuation |
History
Last changed by/on | SAP | 20020116 |
SAP Release Created in |