QM
BAPI
RFC
Used the same way in S/4HANA
BAPI_QUALNOT_SAVE Save QM Notification
Saves a quality notification that was created or changed earlier in the same session and assigns the final number. It is always called after BAPI_QUALNOT_CREATE or BAPI_QUALNOT_MODIFY_DATA. Check RETURN, then call BAPI_TRANSACTION_COMMIT to write the data to the database.
- Function group
- 2078
- Remote-enabled (RFC)
- Yes
- Type
- BAPI
Importing parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| NUMBER | BAPI2078_NOTHDRE-NOTIF_NO | Notification number (temporary or final) | Yes |
Exporting parameters
| Parameter | Type | Description |
|---|---|---|
| NOTIFHEADER | BAPI2078_NOTHDRE | Saved notification header |
Tables parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| RETURN | BAPIRET2 | Return messages | — |
Call template (ABAP)
A skeleton generated from the interface. It lists mandatory importing parameters, exporting parameters and tables; declare the variables with suitable types in your own program.
CALL FUNCTION 'BAPI_QUALNOT_SAVE'
EXPORTING
number = lv_number
IMPORTING
notifheader = lv_notifheader
TABLES
return = lt_return.Related tables
Can't find the report you need?
We also build anything that is not in the catalog. Describe it briefly and we will suggest the right solution.