SAP SD_WORD_PROCESSING_PUT Function Module for NOTRANSL: Textverarbeitung im Dialog









SD_WORD_PROCESSING_PUT is a standard sd word processing put 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: Textverarbeitung im Dialog 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 word processing put FM, simply by entering the name SD_WORD_PROCESSING_PUT 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_WORD_PROCESSING_PUT 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_WORD_PROCESSING_PUT'"NOTRANSL: Textverarbeitung im Dialog
  EXPORTING
   FI_APPLICATION_DATA =  "
*  FI_DEFAULT_FCODE = ' ' "
   FI_SUBSCREEN_NUMBER =  "Dynpro number of subscreen
*  FIT_EXCL_FCODE =  "
*  FIT_XVBPA =  "Business Partner
*  FI_DEFAULT_ID =  "
*  FI_DEFAULT_SPRAS =  "
*  FI_DISPLAY_FLAG = ' ' "
*  FI_DISPLAY_LANGUAGE = '*' "
   FI_GROUP =  "Text Group
*  FI_NEW_TEXT_LANGUAGE = ' ' "
   FI_OBJECT =  "Text Object
*  FI_RESET_FLAG = ' ' "
*  FI_APPL_OBJECT_IDENT = ' ' "
*  FI_APPL_OBJECT_DESCR = ' ' "

CHANGING
   FCT_XTHEAD =  "Texts
*  FCT_XVBUV =  "Incompleteness

EXCEPTIONS
   ERROR_OCCURED = 1
.



IMPORTING Parameters details for SD_WORD_PROCESSING_PUT

FI_APPLICATION_DATA -

Data type: TVCOM
Optional: No
Call by Reference: Yes

FI_DEFAULT_FCODE -

Data type: T185-FFCODE
Default: SPACE
Optional: Yes
Call by Reference: Yes

FI_SUBSCREEN_NUMBER - Dynpro number of subscreen

Data type: SY-DYNNR
Optional: No
Call by Reference: Yes

FIT_EXCL_FCODE -

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

FIT_XVBPA - Business Partner

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

FI_DEFAULT_ID -

Data type: TTXID-TDID
Optional: Yes
Call by Reference: Yes

FI_DEFAULT_SPRAS -

Data type: T002-SPRAS
Optional: Yes
Call by Reference: Yes

FI_DISPLAY_FLAG -

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

FI_DISPLAY_LANGUAGE -

Data type:
Default: '*'
Optional: Yes
Call by Reference: Yes

FI_GROUP - Text Group

Data type: TTXER-TXTGR
Optional: No
Call by Reference: Yes

FI_NEW_TEXT_LANGUAGE -

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

FI_OBJECT - Text Object

Data type: TTXOB-TDOBJECT
Optional: No
Call by Reference: Yes

FI_RESET_FLAG -

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

FI_APPL_OBJECT_IDENT -

Data type: LV70T-TITLE
Default: SPACE
Optional: Yes
Call by Reference: Yes

FI_APPL_OBJECT_DESCR -

Data type: LV70T-TITLE
Default: SPACE
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for SD_WORD_PROCESSING_PUT

FCT_XTHEAD - Texts

Data type: LV70T_TY_XTHEAD_TABLE
Optional: No
Call by Reference: Yes

FCT_XVBUV - Incompleteness

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

EXCEPTIONS details

ERROR_OCCURED - Errors

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

Copy and paste ABAP code example for SD_WORD_PROCESSING_PUT 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_fct_xthead  TYPE LV70T_TY_XTHEAD_TABLE, "   
lv_error_occured  TYPE LV70T_TY_XTHEAD_TABLE, "   
lv_fi_application_data  TYPE TVCOM, "   
lv_fi_default_fcode  TYPE T185-FFCODE, "   SPACE
lv_fi_subscreen_number  TYPE SY-DYNNR, "   
lv_fit_excl_fcode  TYPE LV70T_TY_EXCL_TABLE, "   
lv_fit_xvbpa  TYPE LV70T_TY_XVBPA_TABLE, "   
lv_fi_default_id  TYPE TTXID-TDID, "   
lv_fi_default_spras  TYPE T002-SPRAS, "   
lv_fct_xvbuv  TYPE LV70T_TY_XVBUV_TABLE, "   
lv_fi_display_flag  TYPE LV70T_TY_XVBUV_TABLE, "   SPACE
lv_fi_display_language  TYPE LV70T_TY_XVBUV_TABLE, "   '*'
lv_fi_group  TYPE TTXER-TXTGR, "   
lv_fi_new_text_language  TYPE TTXER, "   SPACE
lv_fi_object  TYPE TTXOB-TDOBJECT, "   
lv_fi_reset_flag  TYPE TTXOB, "   SPACE
lv_fi_appl_object_ident  TYPE LV70T-TITLE, "   SPACE
lv_fi_appl_object_descr  TYPE LV70T-TITLE. "   SPACE

  CALL FUNCTION 'SD_WORD_PROCESSING_PUT'  "NOTRANSL: Textverarbeitung im Dialog
    EXPORTING
         FI_APPLICATION_DATA = lv_fi_application_data
         FI_DEFAULT_FCODE = lv_fi_default_fcode
         FI_SUBSCREEN_NUMBER = lv_fi_subscreen_number
         FIT_EXCL_FCODE = lv_fit_excl_fcode
         FIT_XVBPA = lv_fit_xvbpa
         FI_DEFAULT_ID = lv_fi_default_id
         FI_DEFAULT_SPRAS = lv_fi_default_spras
         FI_DISPLAY_FLAG = lv_fi_display_flag
         FI_DISPLAY_LANGUAGE = lv_fi_display_language
         FI_GROUP = lv_fi_group
         FI_NEW_TEXT_LANGUAGE = lv_fi_new_text_language
         FI_OBJECT = lv_fi_object
         FI_RESET_FLAG = lv_fi_reset_flag
         FI_APPL_OBJECT_IDENT = lv_fi_appl_object_ident
         FI_APPL_OBJECT_DESCR = lv_fi_appl_object_descr
    CHANGING
         FCT_XTHEAD = lv_fct_xthead
         FCT_XVBUV = lv_fct_xvbuv
    EXCEPTIONS
        ERROR_OCCURED = 1
. " SD_WORD_PROCESSING_PUT




ABAP code using 7.40 inline data declarations to call FM SD_WORD_PROCESSING_PUT

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 FFCODE FROM T185 INTO @DATA(ld_fi_default_fcode).
DATA(ld_fi_default_fcode) = ' '.
 
"SELECT single DYNNR FROM SY INTO @DATA(ld_fi_subscreen_number).
 
 
 
"SELECT single TDID FROM TTXID INTO @DATA(ld_fi_default_id).
 
"SELECT single SPRAS FROM T002 INTO @DATA(ld_fi_default_spras).
 
 
DATA(ld_fi_display_flag) = ' '.
 
DATA(ld_fi_display_language) = '*'.
 
"SELECT single TXTGR FROM TTXER INTO @DATA(ld_fi_group).
 
DATA(ld_fi_new_text_language) = ' '.
 
"SELECT single TDOBJECT FROM TTXOB INTO @DATA(ld_fi_object).
 
DATA(ld_fi_reset_flag) = ' '.
 
"SELECT single TITLE FROM LV70T INTO @DATA(ld_fi_appl_object_ident).
DATA(ld_fi_appl_object_ident) = ' '.
 
"SELECT single TITLE FROM LV70T INTO @DATA(ld_fi_appl_object_descr).
DATA(ld_fi_appl_object_descr) = ' '.
 


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!