SAP NAST_PROTOCOL_UPDATE Function Module for NOTRANSL: Verarbeitungsprogramm Protokoll: Protokoll eines Schrittes
NAST_PROTOCOL_UPDATE is a standard nast protocol update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Verarbeitungsprogramm Protokoll: Protokoll eines Schrittes 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 nast protocol update FM, simply by entering the name NAST_PROTOCOL_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: WMCP
Program Name: SAPLWMCP
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function NAST_PROTOCOL_UPDATE 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 'NAST_PROTOCOL_UPDATE'"NOTRANSL: Verarbeitungsprogramm Protokoll: Protokoll eines Schrittes.
EXPORTING
MSG_ARBGB = "Application area (message ID)
MSG_NR = "Message number from T100
MSG_TY = "Message type (S,I,W,E,A)
* MSG_V1 = ' ' "Message parameter 1
* MSG_V2 = ' ' "Message parameter 2
* MSG_V3 = ' ' "Message parameter 3
* MSG_V4 = ' ' "Message parameter 4
EXCEPTIONS
MESSAGE_TYPE_NOT_VALID = 1 NO_SY_MESSAGE = 2
IMPORTING Parameters details for NAST_PROTOCOL_UPDATE
MSG_ARBGB - Application area (message ID)
Data type: SY-MSGIDOptional: No
Call by Reference: No ( called with pass by value option)
MSG_NR - Message number from T100
Data type: SY-MSGNOOptional: No
Call by Reference: No ( called with pass by value option)
MSG_TY - Message type (S,I,W,E,A)
Data type: SY-MSGTYOptional: No
Call by Reference: No ( called with pass by value option)
MSG_V1 - Message parameter 1
Data type: SY-MSGV1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSG_V2 - Message parameter 2
Data type: SY-MSGV2Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSG_V3 - Message parameter 3
Data type: SY-MSGV3Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSG_V4 - Message parameter 4
Data type: SY-MSGV4Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MESSAGE_TYPE_NOT_VALID - Message type does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_SY_MESSAGE - No system message found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for NAST_PROTOCOL_UPDATE 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_msg_arbgb | TYPE SY-MSGID, " | |||
| lv_message_type_not_valid | TYPE SY, " | |||
| lv_msg_nr | TYPE SY-MSGNO, " | |||
| lv_no_sy_message | TYPE SY, " | |||
| lv_msg_ty | TYPE SY-MSGTY, " | |||
| lv_msg_v1 | TYPE SY-MSGV1, " SPACE | |||
| lv_msg_v2 | TYPE SY-MSGV2, " SPACE | |||
| lv_msg_v3 | TYPE SY-MSGV3, " SPACE | |||
| lv_msg_v4 | TYPE SY-MSGV4. " SPACE |
|   CALL FUNCTION 'NAST_PROTOCOL_UPDATE' "NOTRANSL: Verarbeitungsprogramm Protokoll: Protokoll eines Schrittes |
| EXPORTING | ||
| MSG_ARBGB | = lv_msg_arbgb | |
| MSG_NR | = lv_msg_nr | |
| MSG_TY | = lv_msg_ty | |
| MSG_V1 | = lv_msg_v1 | |
| MSG_V2 | = lv_msg_v2 | |
| MSG_V3 | = lv_msg_v3 | |
| MSG_V4 | = lv_msg_v4 | |
| EXCEPTIONS | ||
| MESSAGE_TYPE_NOT_VALID = 1 | ||
| NO_SY_MESSAGE = 2 | ||
| . " NAST_PROTOCOL_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM NAST_PROTOCOL_UPDATE
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 MSGID FROM SY INTO @DATA(ld_msg_arbgb). | ||||
| "SELECT single MSGNO FROM SY INTO @DATA(ld_msg_nr). | ||||
| "SELECT single MSGTY FROM SY INTO @DATA(ld_msg_ty). | ||||
| "SELECT single MSGV1 FROM SY INTO @DATA(ld_msg_v1). | ||||
| DATA(ld_msg_v1) | = ' '. | |||
| "SELECT single MSGV2 FROM SY INTO @DATA(ld_msg_v2). | ||||
| DATA(ld_msg_v2) | = ' '. | |||
| "SELECT single MSGV3 FROM SY INTO @DATA(ld_msg_v3). | ||||
| DATA(ld_msg_v3) | = ' '. | |||
| "SELECT single MSGV4 FROM SY INTO @DATA(ld_msg_v4). | ||||
| DATA(ld_msg_v4) | = ' '. | |||
Search for further information about these or an SAP related objects