SAP RS_MSG_EDTR_MSID_ADD Function Module for









RS_MSG_EDTR_MSID_ADD is a standard rs msg edtr msid add 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 rs msg edtr msid add FM, simply by entering the name RS_MSG_EDTR_MSID_ADD into the relevant SAP transaction such as SE37 or SE38.

Function Group: WBMESSAGES
Program Name: SAPLWBMESSAGES
Main Program: SAPLWBMESSAGES
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RS_MSG_EDTR_MSID_ADD 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 'RS_MSG_EDTR_MSID_ADD'"
EXPORTING
* MESSAGE_ID = ' ' "

IMPORTING
MESSAGE_ID = "

EXCEPTIONS
ACTION_CANCELLED = 1 NOT_EXECUTED = 2
.



IMPORTING Parameters details for RS_MSG_EDTR_MSID_ADD

MESSAGE_ID -

Data type: T100A-ARBGB
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RS_MSG_EDTR_MSID_ADD

MESSAGE_ID -

Data type: T100A-ARBGB
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ACTION_CANCELLED - Processing terminated

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_EXECUTED - Editing Not Executed

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RS_MSG_EDTR_MSID_ADD 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_message_id  TYPE T100A-ARBGB, "   
lv_message_id  TYPE T100A-ARBGB, "   SPACE
lv_action_cancelled  TYPE T100A, "   
lv_not_executed  TYPE T100A. "   

  CALL FUNCTION 'RS_MSG_EDTR_MSID_ADD'  "
    EXPORTING
         MESSAGE_ID = lv_message_id
    IMPORTING
         MESSAGE_ID = lv_message_id
    EXCEPTIONS
        ACTION_CANCELLED = 1
        NOT_EXECUTED = 2
. " RS_MSG_EDTR_MSID_ADD




ABAP code using 7.40 inline data declarations to call FM RS_MSG_EDTR_MSID_ADD

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 ARBGB FROM T100A INTO @DATA(ld_message_id).
 
"SELECT single ARBGB FROM T100A INTO @DATA(ld_message_id).
DATA(ld_message_id) = ' '.
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!