SAP SD_SAVE_TEXT Function Module for NOTRANSL: Verbuchung der im Dialog bearbeiteten Texte









SD_SAVE_TEXT is a standard sd 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 NOTRANSL: Verbuchung der im Dialog bearbeiteten Texte 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 sd save text FM, simply by entering the name SD_SAVE_TEXT into the relevant SAP transaction such as SE37 or SE38.

Function Group: V70T
Program Name: SAPLV70T
Main Program: SAPLV70T
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SD_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 'SD_SAVE_TEXT'"NOTRANSL: Verbuchung der im Dialog bearbeiteten Texte
EXPORTING
* TEXT_KEEP = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
* RENAME_REFERENCES = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION

TABLES
TEXTNAMES = "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
NEW_TEXTNAME_ILLEGAL = 1 NO_TEXTOBJECT_FOUND = 2
.



IMPORTING Parameters details for SD_SAVE_TEXT

TEXT_KEEP - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

RENAME_REFERENCES - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for SD_SAVE_TEXT

TEXTNAMES - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EXCEPTIONS details

NEW_TEXTNAME_ILLEGAL - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

NO_TEXTOBJECT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

Copy and paste ABAP code example for SD_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:
lt_textnames  TYPE STANDARD TABLE OF TVNAM, "   
lv_text_keep  TYPE TVNAM, "   SPACE
lv_new_textname_illegal  TYPE TVNAM, "   
lv_rename_references  TYPE C, "   SPACE
lv_no_textobject_found  TYPE C. "   

  CALL FUNCTION 'SD_SAVE_TEXT'  "NOTRANSL: Verbuchung der im Dialog bearbeiteten Texte
    EXPORTING
         TEXT_KEEP = lv_text_keep
         RENAME_REFERENCES = lv_rename_references
    TABLES
         TEXTNAMES = lt_textnames
    EXCEPTIONS
        NEW_TEXTNAME_ILLEGAL = 1
        NO_TEXTOBJECT_FOUND = 2
. " SD_SAVE_TEXT




ABAP code using 7.40 inline data declarations to call FM SD_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.

 
DATA(ld_text_keep) = ' '.
 
 
DATA(ld_rename_references) = ' '.
 
 


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!