ISU_INTERNET_USER_MIGRATION SAP Function module - INTERNAL: Conversion of BAPIUSW01 User -> System User

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

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

Pattern for FM ISU_INTERNET_USER_MIGRATION - ISU INTERNET USER MIGRATION

CALL FUNCTION 'ISU_INTERNET_USER_MIGRATION' "INTERNAL: Conversion of BAPIUSW01 User -> System User
  EXPORTING
    objtype =                   " oj_name       Object Category
    usergroup =                 " bapilogond-class  User Group in User Master Maintenance
    ref_user =                  " bapirefus     User Name
    referenz =                  " string        Reference Type
  TABLES
    user_table =                " usinetmig     Migrated Internet user transfer structure
    return =                    " bapiret2      Return Parameter(s)
    .  "  ISU_INTERNET_USER_MIGRATION

ABAP code example for Function Module ISU_INTERNET_USER_MIGRATION

The ABAP code below is a full code listing to execute function module ISU_INTERNET_USER_MIGRATION 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_user_table  
 
 TYPE STANDARD TABLE OF USINETMIG,"TABLES PARAM
wa_user_table
 
 LIKE LINE OF it_user_table
,
it_return  
 
 TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM
wa_return
 
 LIKE LINE OF it_return
.


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


DATA(ld_usergroup) = some text here

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

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

"populate fields of struture and append to itab
append wa_user_table to it_user_table.
 

"populate fields of struture and append to itab
append wa_return to it_return.
.

CALL FUNCTION 'ISU_INTERNET_USER_MIGRATION'
  EXPORTING
    objtype =                    ld_objtype
    usergroup =                  ld_usergroup
    ref_user =                   ld_ref_user
    referenz =                   ld_referenz
  TABLES
    user_table =                 it_user_table
    return =                     it_return
    .  "  ISU_INTERNET_USER_MIGRATION

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_objtype
 
 TYPE OJ_NAME ,
it_user_table
 
 TYPE STANDARD TABLE OF USINETMIG ,
wa_user_table
 
 LIKE LINE OF it_user_table,
ld_usergroup
 
 TYPE BAPILOGOND-CLASS ,
it_return
 
 TYPE STANDARD TABLE OF BAPIRET2 ,
wa_return
 
 LIKE LINE OF it_return,
ld_ref_user
 
 TYPE BAPIREFUS ,
ld_referenz
 
 TYPE STRING .


ld_objtype = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_user_table to it_user_table.

ld_usergroup = some text here 

"populate fields of struture and append to itab
append wa_return to it_return.
ld_ref_user = 'Check type of data required'.
ld_referenz = 'Check type of data required'.