GET_CONVERTED_TABLE SAP Function module

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

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

Pattern for FM GET_CONVERTED_TABLE - GET CONVERTED TABLE

CALL FUNCTION 'GET_CONVERTED_TABLE' "
  EXPORTING
    im_rfc_destination =        " rfcdest       Logical Destination (Specified in Function Call)
    im_table_name =             " tabnam        Table Name
    im_expressions =            " rsds_expr
  IMPORTING
    ex_rfc_message =            " crmrfcmsg     Check Results Management: RFC Explanation for Exceptions
    ex_table_ref =              " data
  EXCEPTIONS
    NOT_AUTHORIZED = 1          "
    RFC_FAILED = 2              "
    LOCAL_TABLE_NOT_FOUND = 3   "
    DATA_COMPRESSION_FAILED = 4  "
    CONVERSION_FAILED = 5       "
    REMOTE_TABLE_NOT_FOUND = 6  "
    .  "  GET_CONVERTED_TABLE

ABAP code example for Function Module GET_CONVERTED_TABLE

The ABAP code below is a full code listing to execute function module GET_CONVERTED_TABLE 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_ex_rfc_message  
 
 TYPE CRMRFCMSG
,
ld_ex_table_ref  
 
 TYPE DATA
.


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

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

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

CALL FUNCTION 'GET_CONVERTED_TABLE'
  EXPORTING
    im_rfc_destination =         ld_im_rfc_destination
    im_table_name =              ld_im_table_name
    im_expressions =             ld_im_expressions
  IMPORTING
    ex_rfc_message =             ld_ex_rfc_message
    ex_table_ref =               ld_ex_table_ref
  EXCEPTIONS
    NOT_AUTHORIZED =             1
    RFC_FAILED =                 2
    LOCAL_TABLE_NOT_FOUND =      3
    DATA_COMPRESSION_FAILED =    4
    CONVERSION_FAILED =          5
    REMOTE_TABLE_NOT_FOUND =     6
    .  "  GET_CONVERTED_TABLE

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
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "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_ex_rfc_message
 
 TYPE CRMRFCMSG ,
ld_im_rfc_destination
 
 TYPE RFCDEST ,
ld_ex_table_ref
 
 TYPE DATA ,
ld_im_table_name
 
 TYPE TABNAM ,
ld_im_expressions
 
 TYPE RSDS_EXPR .


ld_im_rfc_destination = 'Check type of data required'.
ld_im_table_name = 'Check type of data required'.
ld_im_expressions = 'Check type of data required'.