SAP Function Modules

FVD_LOS_MAP_CREATE_RESP SAP Function module - Mapping Reply to Proxy Structure







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

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


Pattern for FM FVD_LOS_MAP_CREATE_RESP - FVD LOS MAP CREATE RESP





CALL FUNCTION 'FVD_LOS_MAP_CREATE_RESP' "Mapping Reply to Proxy Structure
  EXPORTING
    i_input =                   " fvd_loan_contract_create_requ3  Proxy Structure (Generated)
    i_control =                 " rlos_control  Control Structure for Loan
    i_inbound =                 " rlos_inbound  Inbound Structure for Loans
    i_tab_bapirettab =          " bapirettab    Table with BAPI Return Information
  IMPORTING
    e_message =                 " fvd_loan_contract_create_conf2  Proxy Structure (Generated)
    .  "  FVD_LOS_MAP_CREATE_RESP

ABAP code example for Function Module FVD_LOS_MAP_CREATE_RESP





The ABAP code below is a full code listing to execute function module FVD_LOS_MAP_CREATE_RESP 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_e_message  TYPE FVD_LOAN_CONTRACT_CREATE_CONF2 .

DATA(ld_i_input) = 'Check type of data required'.
DATA(ld_i_control) = 'Check type of data required'.
DATA(ld_i_inbound) = 'Check type of data required'.
DATA(ld_i_tab_bapirettab) = 'Check type of data required'. . CALL FUNCTION 'FVD_LOS_MAP_CREATE_RESP' EXPORTING i_input = ld_i_input i_control = ld_i_control i_inbound = ld_i_inbound i_tab_bapirettab = ld_i_tab_bapirettab IMPORTING e_message = ld_e_message . " FVD_LOS_MAP_CREATE_RESP
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_e_message  TYPE FVD_LOAN_CONTRACT_CREATE_CONF2 ,
ld_i_input  TYPE FVD_LOAN_CONTRACT_CREATE_REQU3 ,
ld_i_control  TYPE RLOS_CONTROL ,
ld_i_inbound  TYPE RLOS_INBOUND ,
ld_i_tab_bapirettab  TYPE BAPIRETTAB .

ld_i_input = 'Check type of data required'.
ld_i_control = 'Check type of data required'.
ld_i_inbound = 'Check type of data required'.
ld_i_tab_bapirettab = '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 FVD_LOS_MAP_CREATE_RESP or its description.