SAP SAVE_TEXT Function Module for SAPscript: Save text
SAVE_TEXT is a standard save text SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAPscript: Save text 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 save text FM, simply by entering the name SAVE_TEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: STXD
Program Name: SAPLSTXD
Main Program: SAPLSTXD
Appliation area:
Release date: 16-Jan-1995
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SAVE_TEXT 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 'SAVE_TEXT'"SAPscript: Save text.
EXPORTING
* CLIENT = SY-MANDT "Client
HEADER = "Text header of text to be saved
* INSERT = ' ' "Indicator: Text is new
* SAVEMODE_DIRECT = ' ' "Indicator: Save text immediately
* OWNER_SPECIFIED = ' ' "Flag: Apply Owner Information from Header
* LOCAL_CAT = ' ' "Text catalog local
IMPORTING
FUNCTION = "Save status
NEWHEADER = "Text header (changed)
TABLES
LINES = "Lines of text to be saved
EXCEPTIONS
ID = 1 LANGUAGE = 2 NAME = 3 OBJECT = 4
IMPORTING Parameters details for SAVE_TEXT
CLIENT - Client
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
HEADER - Text header of text to be saved
Data type: THEADOptional: No
Call by Reference: No ( called with pass by value option)
INSERT - Indicator: Text is new
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SAVEMODE_DIRECT - Indicator: Save text immediately
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OWNER_SPECIFIED - Flag: Apply Owner Information from Header
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LOCAL_CAT - Text catalog local
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SAVE_TEXT
FUNCTION - Save status
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NEWHEADER - Text header (changed)
Data type: THEADOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SAVE_TEXT
LINES - Lines of text to be saved
Data type: TLINEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ID - Text ID in text header 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)
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 SAVE_TEXT 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_id | TYPE STRING, " | |||
lt_lines | TYPE STANDARD TABLE OF TLINE, " | |||
lv_client | TYPE SY-MANDT, " SY-MANDT | |||
lv_function | TYPE SY, " | |||
lv_header | TYPE THEAD, " | |||
lv_language | TYPE THEAD, " | |||
lv_newheader | TYPE THEAD, " | |||
lv_name | TYPE THEAD, " | |||
lv_insert | TYPE THEAD, " SPACE | |||
lv_object | TYPE THEAD, " | |||
lv_savemode_direct | TYPE THEAD, " SPACE | |||
lv_owner_specified | TYPE THEAD, " SPACE | |||
lv_local_cat | TYPE THEAD. " SPACE |
  CALL FUNCTION 'SAVE_TEXT' "SAPscript: Save text |
EXPORTING | ||
CLIENT | = lv_client | |
HEADER | = lv_header | |
INSERT | = lv_insert | |
SAVEMODE_DIRECT | = lv_savemode_direct | |
OWNER_SPECIFIED | = lv_owner_specified | |
LOCAL_CAT | = lv_local_cat | |
IMPORTING | ||
FUNCTION | = lv_function | |
NEWHEADER | = lv_newheader | |
TABLES | ||
LINES | = lt_lines | |
EXCEPTIONS | ||
ID = 1 | ||
LANGUAGE = 2 | ||
NAME = 3 | ||
OBJECT = 4 | ||
. " SAVE_TEXT |
ABAP code using 7.40 inline data declarations to call FM SAVE_TEXT
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 MANDT FROM SY INTO @DATA(ld_client). | ||||
DATA(ld_client) | = SY-MANDT. | |||
DATA(ld_insert) | = ' '. | |||
DATA(ld_savemode_direct) | = ' '. | |||
DATA(ld_owner_specified) | = ' '. | |||
DATA(ld_local_cat) | = ' '. | |||
Search for further information about these or an SAP related objects