BORLES_MERGE_TEXTS SAP Function module

BORLES_MERGE_TEXTS is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BORLES_MERGE_TEXTS into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BORLES
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM BORLES_MERGE_TEXTS - BORLES MERGE TEXTS

CALL FUNCTION 'BORLES_MERGE_TEXTS' "
  EXPORTING
    i_tdobject =                " tdobject      Texts: Application Object
    i_tdname =                  " tdobname      TDIC Text Name
    it_xthead =                 " lv70t_ty_xthead_table
    it_texth =                  " bor_t_texth   Table Type for TEXH, Automotive-specific
    it_textl =                  " bor_t_textl
*   i_lang_specific = SPACE     " xfeld
  IMPORTING
    et_inserted_texts =         " lv70t_ty_xthead_table
    et_sprot =                  " sprot_u_tab   Table Type for SPROT_U (Log Interface)
    et_no_text =                " lv70t_ty_xthead_table
    .  "  BORLES_MERGE_TEXTS

ABAP code example for Function Module BORLES_MERGE_TEXTS

The ABAP code below is a full code listing to execute function module BORLES_MERGE_TEXTS including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_et_inserted_texts  
 
 TYPE LV70T_TY_XTHEAD_TABLE
,
ld_et_sprot  
 
 TYPE SPROT_U_TAB
,
ld_et_no_text  
 
 TYPE LV70T_TY_XTHEAD_TABLE
.


DATA(ld_i_tdobject) = 'Check type of data required'.

DATA(ld_i_tdname) = 'Check type of data required'.

DATA(ld_it_xthead) = 'Check type of data required'.

DATA(ld_it_texth) = 'Check type of data required'.

DATA(ld_it_textl) = 'Check type of data required'.

DATA(ld_i_lang_specific) = 'Check type of data required'.
.

CALL FUNCTION 'BORLES_MERGE_TEXTS'
  EXPORTING
    i_tdobject =                 ld_i_tdobject
    i_tdname =                   ld_i_tdname
    it_xthead =                  ld_it_xthead
    it_texth =                   ld_it_texth
    it_textl =                   ld_it_textl
*   i_lang_specific =            ld_i_lang_specific
  IMPORTING
    et_inserted_texts =          ld_et_inserted_texts
    et_sprot =                   ld_et_sprot
    et_no_text =                 ld_et_no_text
    .  "  BORLES_MERGE_TEXTS

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_et_inserted_texts
 
 TYPE LV70T_TY_XTHEAD_TABLE ,
ld_i_tdobject
 
 TYPE TDOBJECT ,
ld_et_sprot
 
 TYPE SPROT_U_TAB ,
ld_i_tdname
 
 TYPE TDOBNAME ,
ld_et_no_text
 
 TYPE LV70T_TY_XTHEAD_TABLE ,
ld_it_xthead
 
 TYPE LV70T_TY_XTHEAD_TABLE ,
ld_it_texth
 
 TYPE BOR_T_TEXTH ,
ld_it_textl
 
 TYPE BOR_T_TEXTL ,
ld_i_lang_specific
 
 TYPE XFELD .


ld_i_tdobject = 'Check type of data required'.
ld_i_tdname = 'Check type of data required'.
ld_it_xthead = 'Check type of data required'.
ld_it_texth = 'Check type of data required'.
ld_it_textl = 'Check type of data required'.
ld_i_lang_specific = 'Check type of data required'.