ENH_GET_SCWB_TEXT SAP Function module

ENH_GET_SCWB_TEXT 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 ENH_GET_SCWB_TEXT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SEEF_CWB
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM ENH_GET_SCWB_TEXT - ENH GET SCWB TEXT

CALL FUNCTION 'ENH_GET_SCWB_TEXT' "
  EXPORTING
    i_docuid =                  " enhdocuobject
*   i_langu =                   " sy-langu
    i_docu_type =               " sychar01
  IMPORTING
    v_text_tab =                " enh_cwb_stext_tab
    v_string_tab =              " enh_cwb_ltext_tab
    v_header =                  " enh_cwb_htext
  EXCEPTIONS
    CONCEPT_NOT_FOUND = 1       "
    TEXT_NOT_FOUND = 2          "
    ERROR = 3                   "
    .  "  ENH_GET_SCWB_TEXT

ABAP code example for Function Module ENH_GET_SCWB_TEXT

The ABAP code below is a full code listing to execute function module ENH_GET_SCWB_TEXT 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_v_text_tab  
 
 TYPE ENH_CWB_STEXT_TAB
,
ld_v_string_tab  
 
 TYPE ENH_CWB_LTEXT_TAB
,
ld_v_header  
 
 TYPE ENH_CWB_HTEXT
.


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

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

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

CALL FUNCTION 'ENH_GET_SCWB_TEXT'
  EXPORTING
    i_docuid =                   ld_i_docuid
*   i_langu =                    ld_i_langu
    i_docu_type =                ld_i_docu_type
  IMPORTING
    v_text_tab =                 ld_v_text_tab
    v_string_tab =               ld_v_string_tab
    v_header =                   ld_v_header
  EXCEPTIONS
    CONCEPT_NOT_FOUND =          1
    TEXT_NOT_FOUND =             2
    ERROR =                      3
    .  "  ENH_GET_SCWB_TEXT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
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_v_text_tab
 
 TYPE ENH_CWB_STEXT_TAB ,
ld_i_docuid
 
 TYPE ENHDOCUOBJECT ,
ld_v_string_tab
 
 TYPE ENH_CWB_LTEXT_TAB ,
ld_i_langu
 
 TYPE SY-LANGU ,
ld_v_header
 
 TYPE ENH_CWB_HTEXT ,
ld_i_docu_type
 
 TYPE SYCHAR01 .


ld_i_docuid = 'some text here'.
ld_i_langu = 'Check type of data required'.
ld_i_docu_type = 'Check type of data required'.