EFG_TRANSPORT_TEXT_INFO SAP Function module

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

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

Pattern for FM EFG_TRANSPORT_TEXT_INFO - EFG TRANSPORT TEXT INFO

CALL FUNCTION 'EFG_TRANSPORT_TEXT_INFO' "
  EXPORTING
    x_request =                 " trkorr
    x_text_name =               " c
*   x_tdid = 'ST'               " tdid          Text ID
    x_langu =                   " tdspras       Language Key
  IMPORTING
    y_str_e071 =                " e071
    y_str_e071k =               " e071k
  EXCEPTIONS
    NOT_QUALIFIED = 1           "
    FAILED = 2                  "               The process could not be executed
    CANCELLED = 3               "               Canceled by user
    .  "  EFG_TRANSPORT_TEXT_INFO

ABAP code example for Function Module EFG_TRANSPORT_TEXT_INFO

The ABAP code below is a full code listing to execute function module EFG_TRANSPORT_TEXT_INFO 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_y_str_e071  
 
 TYPE E071
,
ld_y_str_e071k  
 
 TYPE E071K
.


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

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

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

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

CALL FUNCTION 'EFG_TRANSPORT_TEXT_INFO'
  EXPORTING
    x_request =                  ld_x_request
    x_text_name =                ld_x_text_name
*   x_tdid =                     ld_x_tdid
    x_langu =                    ld_x_langu
  IMPORTING
    y_str_e071 =                 ld_y_str_e071
    y_str_e071k =                ld_y_str_e071k
  EXCEPTIONS
    NOT_QUALIFIED =              1
    FAILED =                     2
    CANCELLED =                  3
    .  "  EFG_TRANSPORT_TEXT_INFO

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_y_str_e071
 
 TYPE E071 ,
ld_x_request
 
 TYPE TRKORR ,
ld_y_str_e071k
 
 TYPE E071K ,
ld_x_text_name
 
 TYPE C ,
ld_x_tdid
 
 TYPE TDID ,
ld_x_langu
 
 TYPE TDSPRAS .


ld_x_request = 'Check type of data required'.
ld_x_text_name = 'Check type of data required'.
ld_x_tdid = 'Check type of data required'.
ld_x_langu = 'Check type of data required'.