SAP Function Modules

FILA_MIGRATION_CALL SAP Function module







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

Associated Function Group: FILAMIG
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM FILA_MIGRATION_CALL - FILA MIGRATION CALL





CALL FUNCTION 'FILA_MIGRATION_CALL' "
  EXPORTING
*   id_component = 'FILA'       " fila_component
*   id_event = 'MIGRATION'      " fila_event
    id_bukrs =                  " bukrs
    id_spras =                  " spras
    is_laehead =                " filam_ty_laehead
    is_laeitem =                " filam_ty_laeitem
*   it_values =                 " filam_tb_vals
*   it_laeconds =               " filam_tb_laeconds
*   it_laebill =                " filam_tb_laebill
*   is_legacy_object_header =   " filam_aceds_object_header
*   is_assignments =            " ace_assignments
*   it_legacy_object_items =    " aceds_legacy_object_item_t
*   it_legacy_object_parameters =   " aceds_object_parameter_ext_t
    id_transfer_date =          " aceds_legacy_data_transfr_date
*   is_otp_object =             " filam_otp_object
*   it_otp_param =              " fiotp_param_t
*   it_otp_values =             " fiotp_values_t
*   if_testrun =                " flag
*   if_trace =                  " flag
*   it_laeclass =               " fila_tb_lae_crm_class
  IMPORTING
    et_return =                 " filae_tb_return
  EXCEPTIONS
    CONTRACT_EXISTS = 1         "
    PARAMETER_MISSING = 2       "
    ERROR = 3                   "
    .  "  FILA_MIGRATION_CALL

ABAP code example for Function Module FILA_MIGRATION_CALL





The ABAP code below is a full code listing to execute function module FILA_MIGRATION_CALL 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_et_return  TYPE FILAE_TB_RETURN .

DATA(ld_id_component) = 'Check type of data required'.
DATA(ld_id_event) = 'Check type of data required'.
DATA(ld_id_bukrs) = 'Check type of data required'.
DATA(ld_id_spras) = 'Check type of data required'.
DATA(ld_is_laehead) = 'Check type of data required'.
DATA(ld_is_laeitem) = 'Check type of data required'.
DATA(ld_it_values) = 'Check type of data required'.
DATA(ld_it_laeconds) = 'Check type of data required'.
DATA(ld_it_laebill) = 'Check type of data required'.
DATA(ld_is_legacy_object_header) = 'Check type of data required'.
DATA(ld_is_assignments) = 'Check type of data required'.
DATA(ld_it_legacy_object_items) = 'Check type of data required'.
DATA(ld_it_legacy_object_parameters) = 'Check type of data required'.
DATA(ld_id_transfer_date) = 'Check type of data required'.
DATA(ld_is_otp_object) = 'Check type of data required'.
DATA(ld_it_otp_param) = 'Check type of data required'.
DATA(ld_it_otp_values) = 'Check type of data required'.
DATA(ld_if_testrun) = 'Check type of data required'.
DATA(ld_if_trace) = 'Check type of data required'.
DATA(ld_it_laeclass) = 'Check type of data required'. . CALL FUNCTION 'FILA_MIGRATION_CALL' EXPORTING * id_component = ld_id_component * id_event = ld_id_event id_bukrs = ld_id_bukrs id_spras = ld_id_spras is_laehead = ld_is_laehead is_laeitem = ld_is_laeitem * it_values = ld_it_values * it_laeconds = ld_it_laeconds * it_laebill = ld_it_laebill * is_legacy_object_header = ld_is_legacy_object_header * is_assignments = ld_is_assignments * it_legacy_object_items = ld_it_legacy_object_items * it_legacy_object_parameters = ld_it_legacy_object_parameters id_transfer_date = ld_id_transfer_date * is_otp_object = ld_is_otp_object * it_otp_param = ld_it_otp_param * it_otp_values = ld_it_otp_values * if_testrun = ld_if_testrun * if_trace = ld_if_trace * it_laeclass = ld_it_laeclass IMPORTING et_return = ld_et_return EXCEPTIONS CONTRACT_EXISTS = 1 PARAMETER_MISSING = 2 ERROR = 3 . " FILA_MIGRATION_CALL
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_et_return  TYPE FILAE_TB_RETURN ,
ld_id_component  TYPE FILA_COMPONENT ,
ld_id_event  TYPE FILA_EVENT ,
ld_id_bukrs  TYPE BUKRS ,
ld_id_spras  TYPE SPRAS ,
ld_is_laehead  TYPE FILAM_TY_LAEHEAD ,
ld_is_laeitem  TYPE FILAM_TY_LAEITEM ,
ld_it_values  TYPE FILAM_TB_VALS ,
ld_it_laeconds  TYPE FILAM_TB_LAECONDS ,
ld_it_laebill  TYPE FILAM_TB_LAEBILL ,
ld_is_legacy_object_header  TYPE FILAM_ACEDS_OBJECT_HEADER ,
ld_is_assignments  TYPE ACE_ASSIGNMENTS ,
ld_it_legacy_object_items  TYPE ACEDS_LEGACY_OBJECT_ITEM_T ,
ld_it_legacy_object_parameters  TYPE ACEDS_OBJECT_PARAMETER_EXT_T ,
ld_id_transfer_date  TYPE ACEDS_LEGACY_DATA_TRANSFR_DATE ,
ld_is_otp_object  TYPE FILAM_OTP_OBJECT ,
ld_it_otp_param  TYPE FIOTP_PARAM_T ,
ld_it_otp_values  TYPE FIOTP_VALUES_T ,
ld_if_testrun  TYPE FLAG ,
ld_if_trace  TYPE FLAG ,
ld_it_laeclass  TYPE FILA_TB_LAE_CRM_CLASS .

ld_id_component = 'Check type of data required'.
ld_id_event = 'Check type of data required'.
ld_id_bukrs = 'Check type of data required'.
ld_id_spras = 'Check type of data required'.
ld_is_laehead = 'Check type of data required'.
ld_is_laeitem = 'Check type of data required'.
ld_it_values = 'Check type of data required'.
ld_it_laeconds = 'Check type of data required'.
ld_it_laebill = 'Check type of data required'.
ld_is_legacy_object_header = 'Check type of data required'.
ld_is_assignments = 'Check type of data required'.
ld_it_legacy_object_items = 'Check type of data required'.
ld_it_legacy_object_parameters = 'Check type of data required'.
ld_id_transfer_date = 'Check type of data required'.
ld_is_otp_object = 'Check type of data required'.
ld_it_otp_param = 'Check type of data required'.
ld_it_otp_values = 'Check type of data required'.
ld_if_testrun = 'Check type of data required'.
ld_if_trace = 'Check type of data required'.
ld_it_laeclass = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FILA_MIGRATION_CALL or its description.