Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
QQM (Package) QM quality notification
Basic Data
| Data Element | QNVERS |
| Short Description | Variants for Determining Existence of Notifications |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | QKZVERS | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | VERSION | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Variant |
| Medium | 15 | Variant |
| Long | 20 | Variant |
| Heading | 2 | Va |
Documentation
Use
The system uses two variants to find related notifications. If you do not specify a variant, the system automatically selects variant 1.
Variant 1
The system determines the number of notifications on the basis of the original documents.
Advantage:
With the exception of the current notification, the system displays all notifications that have the same reference object(s).
Disadvantage:
The more notifications that exist in the system, the longer the processing time. This is because each related notification is selected directly from the database of the original documents.
Variant 2
The system determines the number of notifications on the basis of the statistics database.
Advantage:
The processing time is shorter since the system retrieves the data from the statistics database.
Disadvantage:
If you want to change a notification and the update program has run, this current notification is taken into account in the statistics.
The archived notifications in the statistic database are also taken into account. However, when you call up the list of notifications, the system only displays the notifications that have not been archived. This may result in an inconsistency in the statistics.
Examples
Over the past five years, your system has accumulated 1000 notifications. You archive your database and retain the 200 notifications from the previous year.
If you call up the related notifications using variant 1, the system selects the notifications from the 200 in the database.
If you call up the related notifications using variant 2, the system determines the key figures on the basis of the 1000 notifications in the statistics database. If, however, you call up the notifications using the list function, the system searches among the 200 notifications in the database.
History
| Last changed by/on | SAP | 19991102 |
| SAP Release Created in |
