UNICODE_RFC4 SAP Function module - RFC container with language field, move characterlike structure

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

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

Pattern for FM UNICODE_RFC4 - UNICODE RFC4

CALL FUNCTION 'UNICODE_RFC4' "RFC container with  language field, move characterlike structure
  EXPORTING
    username =                  " syuname       R/3 System, user logon name
    exercise =                  " ted_a_exercise  Exercise
    source =                    " sysysid       source system
    logon_langu =               " sylangu       logon language in the source system
  TABLES
    container =                 " uni_s_rfc_container_lang  Unstructured data container with language key
  EXCEPTIONS
    MODIFY_ERROR = 1            "               could not modify database entries
    .  "  UNICODE_RFC4

ABAP code example for Function Module UNICODE_RFC4

The ABAP code below is a full code listing to execute function module UNICODE_RFC4 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:
it_container  
 
 TYPE STANDARD TABLE OF UNI_S_RFC_CONTAINER_LANG,"TABLES PARAM
wa_container
 
 LIKE LINE OF it_container
.


DATA(ld_username) = 'some text here'.

DATA(ld_exercise) = 'some text here'.

DATA(ld_source) = 'some text here'.

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

"populate fields of struture and append to itab
append wa_container to it_container.
.

CALL FUNCTION 'UNICODE_RFC4'
  EXPORTING
    username =                   ld_username
    exercise =                   ld_exercise
    source =                     ld_source
    logon_langu =                ld_logon_langu
  TABLES
    container =                  it_container
  EXCEPTIONS
    MODIFY_ERROR =               1
    .  "  UNICODE_RFC4

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_username
 
 TYPE SYUNAME ,
it_container
 
 TYPE STANDARD TABLE OF UNI_S_RFC_CONTAINER_LANG ,
wa_container
 
 LIKE LINE OF it_container,
ld_exercise
 
 TYPE TED_A_EXERCISE ,
ld_source
 
 TYPE SYSYSID ,
ld_logon_langu
 
 TYPE SYLANGU .


ld_username = 'some text here'. 

"populate fields of struture and append to itab
append wa_container to it_container.
ld_exercise = 'some text here'.
ld_source = 'some text here'.
ld_logon_langu = 'Check type of data required'.