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 | OLQN-SCR | Define Screen Templates |
| Transaction Code | S_ALR_87004456 | IMG Activity: OLQN-SCR |
| Created on | 19981222 | |
| Customizing Attributes | OLQN-SCR | Define screen templates for notification type |
| Customizing Activity | OLQN-SCR | Define Screen Templates for Notification Type |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OLQN-SCR |
In this step, you structure the screen templates you want to use for quality notifications.
Requirements
The notification types are predefined.
Standard settings
Recommendation
Copy the standard settings.
Activities
A Screen Areas
You can assign the groups of information contained in the quality notifications to various tab pages and screen areas to give a flexible structure to the screen templates. You perform the following tasks in separate screen areas:
- Define screen areas for the notification header.
Here you can assign up to 5 user-defined screen areas in addition to an origin-related screen area. - Define screen templates for the simplified view. transactions. Assign the required screen areas.
- Define screen templates for the extended view.
You can define tabstrips for complex notification transactions and assign screen areas to each tabstrip.
First copy the settings from client 000.
Determine whether the standard settings for the screen templates are suitable for the contents and functions of the quality notifications in your company and optimize the settings for the tab pages and screen areas. Follow these steps: - Gain an overview of the available tabstrips and screen areas and their related fields.
You need a sample notification for each notification origin, in which you can check the screen areas. - Assign the required screen areas to the tab pages available and give these tab pages a suitable title.
Note: Tab pages 10\TAB are at header level; tab pages 20\TAB at item level in the Q-notification.
Tip: Check the effect of the settings immediately in a parallel session using a sample notification.
Hide the fields that you do not require.
For more information on this method, refer to the section Environment / Tools / System Settings / Field Selection
Note: If you have not yet defined any screen areas for the relevant notification type, when you create a notification, the system searches in the standard client 000 for a notification type with the same notification origin and uses its screen area settings.
You can also copy the standard settings for the relevant notification type into the standard client manually (transaction OIMN). This transaction does not contain an automatic transport connection. You must add the relevant entries to a transport order manually (see note 745169).
Note: The screen area with the reference to related notifications is only shown if the appropriate settings have been made in the QM Information System.
Note (for specialist only): The available screen areas are defined in a subscreen table per notification type and are accessed via view V_TQSUB. Caution: The table affects all clients and has the delivery class E. You must NOT change or delete the SAP entries because standard programs use these. This is why the view is not offered for maintenance in the Implementation Guide.
B Initial Screens
You can cause the system to offer additional recording screens when you access the quality notification by assigning the corresponding function modules and initial screens to the notification types. The system contains examples of this. You can find a list of these initial screens, if you call up the reference documentation stored for the words initial screens, or if you use the F1-Help (not F4-Help) in the table.
- Determine the notification origins and notification types for which you require this function and use the examples provided, or create your own program. Note: The structure RQM01 (SE12) contains all fields that can be copied into the notification in this way.
- Hide the fields that you do not require.
For more information on this method, refer to the section Environment / Tools / System Settings / Field Selection.
C Long Texts
You can control the formatting of the long text on the notification screen. If required, the system can
- Automatically insert log lines
- Prevent changes to text
For more details see the online documentation for corresponding view.
Determine whether you need such functions for specific notification types.
Determine whether such functions are needed for certain notification types.
Further notes
Business Attributes
| ASAP Roadmap ID | 261 | Define Screen Control |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | 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-SCR | 0 | ALR0077563 O | |
| SIMG | OLQN-SCR | 1 | BIO0000031 O | |
| SIMG | OLQN-SCR | 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 |
| VC_TQSCR | C - View cluster | SM34 | 0000000000 | Define Screen Areas and Tabs | ||
| IMGDUMMY | D - Dummy object | OIMN | Copy Screen Areas from the Standard System | |||
| V_TQ80_E | V - View | SM30 | Define Initial Screens | |||
| V_TQ80_L | V - View | SM30 | Format Notification Long Text | |||
| SFAC | T - Individual transaction object | OQM1 | Field Selection: General Screens | |||
| SFAC | T - Individual transaction object | OQM2 | Field Selection: Initial Screens | |||
| SFAC | T - Individual transaction object | OQM3 | Field Selection: Reference Object Screens | |||
| SFAC | T - Individual transaction object | OQM4 | Field Selection: Partner Screens |
History
| Last changed by/on | SAP | 20060201 |
| SAP Release Created in |
