SAP SAPSCRIPT_MESSAGE_GET_NO Function Module for
SAPSCRIPT_MESSAGE_GET_NO is a standard sapscript message get no SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 sapscript message get no FM, simply by entering the name SAPSCRIPT_MESSAGE_GET_NO into the relevant SAP transaction such as SE37 or SE38.
Function Group: STXU
Program Name: SAPLSTXU
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SAPSCRIPT_MESSAGE_GET_NO 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 'SAPSCRIPT_MESSAGE_GET_NO'".
IMPORTING
NO = "Number of the message
V1 = "First parameter of the message
V2 = "Second parameter of the message
V3 = "Third parameter of the message
V4 = "Fourth parameter of the message
EXPORTING Parameters details for SAPSCRIPT_MESSAGE_GET_NO
NO - Number of the message
Data type: ITCRS-MSGNOOptional: No
Call by Reference: No ( called with pass by value option)
V1 - First parameter of the message
Data type: ITCRS-MSGV1Optional: No
Call by Reference: No ( called with pass by value option)
V2 - Second parameter of the message
Data type: ITCRS-MSGV2Optional: No
Call by Reference: No ( called with pass by value option)
V3 - Third parameter of the message
Data type: ITCRS-MSGV3Optional: No
Call by Reference: No ( called with pass by value option)
V4 - Fourth parameter of the message
Data type: ITCRS-MSGV4Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SAPSCRIPT_MESSAGE_GET_NO 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_no | TYPE ITCRS-MSGNO, " | |||
| lv_v1 | TYPE ITCRS-MSGV1, " | |||
| lv_v2 | TYPE ITCRS-MSGV2, " | |||
| lv_v3 | TYPE ITCRS-MSGV3, " | |||
| lv_v4 | TYPE ITCRS-MSGV4. " |
| CALL FUNCTION 'SAPSCRIPT_MESSAGE_GET_NO' " |
| IMPORTING | ||
| NO | = lv_no | |
| V1 | = lv_v1 | |
| V2 | = lv_v2 | |
| V3 | = lv_v3 | |
| V4 | = lv_v4 | |
| . " SAPSCRIPT_MESSAGE_GET_NO | ||
ABAP code using 7.40 inline data declarations to call FM SAPSCRIPT_MESSAGE_GET_NO
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 MSGNO FROM ITCRS INTO @DATA(ld_no). | ||||
| "SELECT single MSGV1 FROM ITCRS INTO @DATA(ld_v1). | ||||
| "SELECT single MSGV2 FROM ITCRS INTO @DATA(ld_v2). | ||||
| "SELECT single MSGV3 FROM ITCRS INTO @DATA(ld_v3). | ||||
| "SELECT single MSGV4 FROM ITCRS INTO @DATA(ld_v4). | ||||
Search for further information about these or an SAP related objects