SAP ISU_SMNOTIF_ADD_ONETIME_PARTNR Function Module for Sets Date and Malfunction Time of a Notification
ISU_SMNOTIF_ADD_ONETIME_PARTNR is a standard isu smnotif add onetime partnr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Sets Date and Malfunction Time of a Notification processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for isu smnotif add onetime partnr FM, simply by entering the name ISU_SMNOTIF_ADD_ONETIME_PARTNR into the relevant SAP transaction such as SE37 or SE38.
Function Group: EEWM_SV_NTF
Program Name: SAPLEEWM_SV_NTF
Main Program: SAPLEEWM_SV_NTF
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_SMNOTIF_ADD_ONETIME_PARTNR pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'ISU_SMNOTIF_ADD_ONETIME_PARTNR'"Sets Date and Malfunction Time of a Notification.
EXPORTING
X_QMNUM = "Declaration number
X_PARTNER_NUMBER = "Partner
X_PARTNER_ROLE = "Partner Role
X_PARTNER_DETAILS = "One-Time Customer Details
* X_COMMIT = 'X' "Flag: COMMIT WORK
EXCEPTIONS
SYSTEM_ERROR = 1 NOTIFTYPE_INVALID = 2 PARTNER_ROLE_INVALID = 3 PARTNER_NOT_FOUND = 4 PARTNER_NOT_ONETIME_CUSTOMER = 5 ERROR_ADDING_ONETIME_CUSTOMER = 6 ERROR_ADDRESS_CHECK = 7 OBJECT_NOT_FOUND = 8
IMPORTING Parameters details for ISU_SMNOTIF_ADD_ONETIME_PARTNR
X_QMNUM - Declaration number
Data type: VIQMEL-QMNUMOptional: No
Call by Reference: No ( called with pass by value option)
X_PARTNER_NUMBER - Partner
Data type: I_PARNROptional: No
Call by Reference: No ( called with pass by value option)
X_PARTNER_ROLE - Partner Role
Data type: PARVWOptional: No
Call by Reference: Yes
X_PARTNER_DETAILS - One-Time Customer Details
Data type: ISU_NOTIF_ONETIMECUST_DETAILSOptional: No
Call by Reference: No ( called with pass by value option)
X_COMMIT - Flag: COMMIT WORK
Data type: SY-BATCHDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SYSTEM_ERROR - System Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOTIFTYPE_INVALID -
Data type:Optional: No
Call by Reference: Yes
PARTNER_ROLE_INVALID - Partner function not valid
Data type:Optional: No
Call by Reference: Yes
PARTNER_NOT_FOUND - Partner Not Found
Data type:Optional: No
Call by Reference: Yes
PARTNER_NOT_ONETIME_CUSTOMER -
Data type:Optional: No
Call by Reference: Yes
ERROR_ADDING_ONETIME_CUSTOMER -
Data type:Optional: No
Call by Reference: Yes
ERROR_ADDRESS_CHECK -
Data type:Optional: No
Call by Reference: Yes
OBJECT_NOT_FOUND - Object Not Found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_SMNOTIF_ADD_ONETIME_PARTNR Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_x_qmnum | TYPE VIQMEL-QMNUM, " | |||
| lv_system_error | TYPE VIQMEL, " | |||
| lv_x_partner_number | TYPE I_PARNR, " | |||
| lv_notiftype_invalid | TYPE I_PARNR, " | |||
| lv_x_partner_role | TYPE PARVW, " | |||
| lv_partner_role_invalid | TYPE PARVW, " | |||
| lv_partner_not_found | TYPE PARVW, " | |||
| lv_x_partner_details | TYPE ISU_NOTIF_ONETIMECUST_DETAILS, " | |||
| lv_x_commit | TYPE SY-BATCH, " 'X' | |||
| lv_partner_not_onetime_customer | TYPE SY, " | |||
| lv_error_adding_onetime_customer | TYPE SY, " | |||
| lv_error_address_check | TYPE SY, " | |||
| lv_object_not_found | TYPE SY. " |
|   CALL FUNCTION 'ISU_SMNOTIF_ADD_ONETIME_PARTNR' "Sets Date and Malfunction Time of a Notification |
| EXPORTING | ||
| X_QMNUM | = lv_x_qmnum | |
| X_PARTNER_NUMBER | = lv_x_partner_number | |
| X_PARTNER_ROLE | = lv_x_partner_role | |
| X_PARTNER_DETAILS | = lv_x_partner_details | |
| X_COMMIT | = lv_x_commit | |
| EXCEPTIONS | ||
| SYSTEM_ERROR = 1 | ||
| NOTIFTYPE_INVALID = 2 | ||
| PARTNER_ROLE_INVALID = 3 | ||
| PARTNER_NOT_FOUND = 4 | ||
| PARTNER_NOT_ONETIME_CUSTOMER = 5 | ||
| ERROR_ADDING_ONETIME_CUSTOMER = 6 | ||
| ERROR_ADDRESS_CHECK = 7 | ||
| OBJECT_NOT_FOUND = 8 | ||
| . " ISU_SMNOTIF_ADD_ONETIME_PARTNR | ||
ABAP code using 7.40 inline data declarations to call FM ISU_SMNOTIF_ADD_ONETIME_PARTNR
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single QMNUM FROM VIQMEL INTO @DATA(ld_x_qmnum). | ||||
| "SELECT single BATCH FROM SY INTO @DATA(ld_x_commit). | ||||
| DATA(ld_x_commit) | = 'X'. | |||
Search for further information about these or an SAP related objects