|
Functionality
You can use this BAPI to create a new QM notification. You can createcertain fields for the notification header, as well as items, causes,activities, and long texts for the notification. You can also maintainpartner data. Comments
Errors are transferred in the table RETURN.
The changes to the notification data will only be available on thedatabase after the function modules BAPI_QUALNOT_SAVE andBAPI_TRANSACTION_COMMIT have run successfully. Notes
The sort field must be filled if you want to create items, causes,tasks, or activities.
If you want to create a cause, the sort field for the item must also befilled.
The fields OBJTYP and OBJKEY must be filled when creating a long text.OBJTYP can contain the following values:
1. QMEL - Notification Header
2. QMFE - Notification Item
3. QMUR - Notification Cause
4. QMSM - Notification Task
5. QMMA - Notification Activity
OBJKEY must contain the corresponding sort field for the values listedabove. The combination of sort fields for the item/cause, item/task, oritem/activity must be unique within the notification. If you leave thesort field blank, and the OBJTYP is QMEL, a long text will be createdfor the notification header.
Example:
OBJTYP OBJKEY
QMEL initial (' ')
---> Long text for notification header
An external reference key can be transferred in the field REFOBJECTKEY.The relationships between external reference keys and SAP keys aretransferred in the export table KEY_RELATIONSHIP. If the fields SENDER,REFOBJECTTYPE, and REFRELTYPE are filled, an object relationship can becreated at notification header level.
Example: The reference object is a quality notification with the number
4711:
SENDER : Field "Logical System" from table T000
REFOBJECTTYPE : BUS2078
REFOBJECTKEY : 000000004711
REFRELTYPE : REFZ.
Sort number in the item:
If several items have the same sort number, you can assign a commoncause and/or a common activity and/or a common task to these items.
Sort number in cause, activity, task:
The sort number is the key field for accessing the relevant cause,activity, or task.
A sort number for the item also exists in the cause, activity, and task.You can use this to sort causes, activities, and tasks at header or itemlevel.
In the causes, the sort number for the item must be filled with a numberthat is greater than or equal to 1, because causes always belong toitems and can never appear at header level. In activities and tasks, thesort number for the item can be zero; then these are part of thenotification header. Description
Output structure of the notification header Description
Number of the notification that is to be processed Description
Structure containing information for the notification header (generaldata) Description
Notification type Description
Logical system of sender Description
Execution indicator: 'X' = execute function.
If this parameter is set, and if a response profile has been maintainedin Customizing for the notification type, the tasks from the responseprofile are automatically generated when the notification is created. Description
Key relationships within the notification data Description
Notification long text Description
Data for the activities of the notification Description
Data for the notification causes Description
Partner for notification Description
Data for the tasks of the notification Description
Data for the notification items Description
The table contains the list of errors that occurred during processing |