SAP SAPMS_TEXT_EDIT Function Module for

Search SAP Function Modules

SAPMS_TEXT_EDIT is a standard sapms text edit 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 sapms text edit FM, simply by entering the name SAPMS_TEXT_EDIT into the relevant SAP transaction such as SE37 or SE38.

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

Function SAPMS_TEXT_EDIT 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 'SAPMS_TEXT_EDIT'"
  EXPORTING
*  DISPLAY = ' ' "Flag: Display mode
*  EDITOR_TITLE = ' ' "Text for editor title line
   HEADER =  "Text header of the text to be edited
*  SAVE = 'X' "Indicator: Saving by editor

 IMPORTING
   FUNCTION =  "Flag: Processing status
   NEWHEADER =  "Text header (changed)

TABLES
   LINES =  "Lines of text being edited

EXCEPTIONS
   ID = 1    LANGUAGE = 2    LINESIZE = 3    NAME = 4    OBJECT = 5 

.

IMPORTING Parameters details for SAPMS_TEXT_EDIT

DISPLAY - Flag: Display mode

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

EDITOR_TITLE - Text for editor title line

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

HEADER - Text header of the text to be edited

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

SAVE - Indicator: Saving by editor

Data type:
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SAPMS_TEXT_EDIT

FUNCTION - Flag: Processing status

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

NEWHEADER - Text header (changed)

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

TABLES Parameters details for SAPMS_TEXT_EDIT

LINES - Lines of text being edited

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

EXCEPTIONS details

ID - Text ID in text headers is invalid

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

LANGUAGE - Language in text header invalid

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

LINESIZE - Line width in text header invalid

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

NAME - Text name in text header invalid

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

OBJECT - Text object in text header invalid

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

Copy and paste ABAP code example for SAPMS_TEXT_EDIT 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.

ABAP code using 7.40 inline data declarations to call FM SAPMS_TEXT_EDIT

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.

Search for further information about these or an SAP related objects