SAP SD_TEXT_PREPARE_IF Function Module for NOTRANSL: Texte: Schnittstellenparameter setzen









SD_TEXT_PREPARE_IF is a standard sd text prepare if 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: Texte: Schnittstellenparameter setzen 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 text prepare if FM, simply by entering the name SD_TEXT_PREPARE_IF into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_TEXT_PREPARE_IF 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_TEXT_PREPARE_IF'"NOTRANSL: Texte: Schnittstellenparameter setzen
  EXPORTING
   APPLICATION_DATA =  "Text Communications Block for Copying
*  DISPLAY_FLAG = ' ' "Flag (X or Blank)
*  DISPLAY_LANGUAGE = '*' "Language Key
   GROUP =  "Text Determination Procedure
*  INCOMPLETE_FLAG = ' ' "Flag (X or Blank)
*  NAME_ROUTINE_NUMBER =  "Number of the routine used for copying
*  NEW_TEXT_LANGUAGE = SY-LANGU "Language Key
   OBJECT =  "Texts: Application Object
*  RESET_FLAG = ' ' "Flag (X or Blank)

TABLES
*  YTHEAD =  "Reference Structure for XTHEAD
.



IMPORTING Parameters details for SD_TEXT_PREPARE_IF

APPLICATION_DATA - Text Communications Block for Copying

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

DISPLAY_FLAG - Flag (X or Blank)

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

DISPLAY_LANGUAGE - Language Key

Data type: LV70T-SPRAS
Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

GROUP - Text Determination Procedure

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

INCOMPLETE_FLAG - Flag (X or Blank)

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

NAME_ROUTINE_NUMBER - Number of the routine used for copying

Data type: TFRM-GRPNO
Optional: Yes
Call by Reference: No ( called with pass by value option)

NEW_TEXT_LANGUAGE - Language Key

Data type: LV70T-SPRAS
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT - Texts: Application Object

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

RESET_FLAG - Flag (X or Blank)

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

TABLES Parameters details for SD_TEXT_PREPARE_IF

YTHEAD - Reference Structure for XTHEAD

Data type: THEADVB
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for SD_TEXT_PREPARE_IF 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_ythead  TYPE STANDARD TABLE OF THEADVB, "   
lv_application_data  TYPE TVCOM, "   
lv_display_flag  TYPE LV70T-XFLAG, "   SPACE
lv_display_language  TYPE LV70T-SPRAS, "   '*'
lv_group  TYPE TTXER-TXTGR, "   
lv_incomplete_flag  TYPE LV70T-XFLAG, "   SPACE
lv_name_routine_number  TYPE TFRM-GRPNO, "   
lv_new_text_language  TYPE LV70T-SPRAS, "   SY-LANGU
lv_object  TYPE TTXOB-TDOBJECT, "   
lv_reset_flag  TYPE LV70T-XFLAG. "   SPACE

  CALL FUNCTION 'SD_TEXT_PREPARE_IF'  "NOTRANSL: Texte: Schnittstellenparameter setzen
    EXPORTING
         APPLICATION_DATA = lv_application_data
         DISPLAY_FLAG = lv_display_flag
         DISPLAY_LANGUAGE = lv_display_language
         GROUP = lv_group
         INCOMPLETE_FLAG = lv_incomplete_flag
         NAME_ROUTINE_NUMBER = lv_name_routine_number
         NEW_TEXT_LANGUAGE = lv_new_text_language
         OBJECT = lv_object
         RESET_FLAG = lv_reset_flag
    TABLES
         YTHEAD = lt_ythead
. " SD_TEXT_PREPARE_IF




ABAP code using 7.40 inline data declarations to call FM SD_TEXT_PREPARE_IF

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 XFLAG FROM LV70T INTO @DATA(ld_display_flag).
DATA(ld_display_flag) = ' '.
 
"SELECT single SPRAS FROM LV70T INTO @DATA(ld_display_language).
DATA(ld_display_language) = '*'.
 
"SELECT single TXTGR FROM TTXER INTO @DATA(ld_group).
 
"SELECT single XFLAG FROM LV70T INTO @DATA(ld_incomplete_flag).
DATA(ld_incomplete_flag) = ' '.
 
"SELECT single GRPNO FROM TFRM INTO @DATA(ld_name_routine_number).
 
"SELECT single SPRAS FROM LV70T INTO @DATA(ld_new_text_language).
DATA(ld_new_text_language) = SY-LANGU.
 
"SELECT single TDOBJECT FROM TTXOB INTO @DATA(ld_object).
 
"SELECT single XFLAG FROM LV70T INTO @DATA(ld_reset_flag).
DATA(ld_reset_flag) = ' '.
 


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!