SAP ABAP IMG Activity OLIAOQN6 (Define Catalog Profile)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-CIC (Application Component) Interaction Center WinClient
⤷
INSC (Package) Application Development R/3 Plant Maintenance Customizing

⤷

⤷

IMG Activity
ID | OLIAOQN6 | Define Catalog Profile |
Transaction Code | S_ALR_87000935 | IMG Activity: OLIAOQN6 |
Created on | 19981222 | |
Customizing Attributes | OLIAOQN6 | Maintain Catalog Profiles |
Customizing Activity | OLIAOQN6 | Maintain Catalog Profiles |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CA_NCP |
In this step, you define the catalog profiles for notifications. You define:
- Which catalogs and code groups from the individual catalogs are to be accessed by the system for notifications.
You can make a selection of code groups from the catalog by entering a generic key for these code groups.
To do this, you can use the special characters '+' and '*'. If you enter '+A*' in the code group field, the system only selects code groups, whose key has the second letter 'A'. - Which class of class type 015 is to be proposed for the classification of the notification items.
You can use classes to freely define additional general problem attributes, if you cannot adequately describe the problem attributes contained in the data structure (defect type, defect location, defect cause) using the existing catalogs and texts.
If, for example, you maintain the class 'Problems in production', together with the class characteristic 'Initiating object', you can then enter the cause of production problems as characteristic values. - The type of system message that is to appear, if the catalog profile is not followed.
Requirements
- The catalogs that are to be used for the notifications have already been defined.
Recommendation
- Define that the system displays a warning (type W) if the catalog profile is not followed.
Activities
- Define the code groups required for each catalog that is contained in the catalog profile.
- Discuss the structure of the eight-digit, mnemonic keys for the code groups with all other users of the catalogs; take the option of generic selection into consideration. You can for example define that separate code groups are formed for each notification type or for each plant and that the initial digits in the code group key are the same as those in the notification type or plant.
- Maintain the code groups. Codes can also be maintained retroactively.
- Determine whether you require a classification of the notification items. If necessary, create the classes in Classification System and assign them to the catalog profile. You should define and maintain the class characteristics at the same time.
Class type 015 is reserved for classifying the notification items.
If required, when processing classed notification items, you can enter the class characteristic values on a subscreen.
Further notes
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | 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_T352B_CL | C - View cluster | OQN6 | IHBSCHEMA | Catalog Profile |
History
Last changed by/on | SAP | 20000128 |
SAP Release Created in |