EHSWA_270_MN_MAP_API_2_DATA_SE SAP Function module

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

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

Pattern for FM EHSWA_270_MN_MAP_API_2_DATA_SE - EHSWA 270 MN MAP API 2 DATA SE

CALL FUNCTION 'EHSWA_270_MN_MAP_API_2_DATA_SE' "
* EXPORTING
*   i_api_mn =                  " ehswas_mnapi  Begleitschein: Header Data
*   i_api_mnpos_tab =           " ehswa_mnposapi_tab_type  Item Data
*   i_api_mnwakey_tab =         " ehswa_mnwakeyapi_tab_type  Waste Code Data
*   i_api_mnbp_tab =            " ehswa_mnbpapi_tab_type  Business Partner Data
*   i_api_mntxt1_tab =          " ehsw_tt_mntxt  Disposal Documents: Table Type for SAPscript Texts
*   i_api_mntxt2_tab =          " ehsw_tt_mntxt  Disposal Documents: Table Type for SAPscript Texts
*   i_api_mntxt3_tab =          " ehsw_tt_mntxt  Disposal Documents: Table Type for SAPscript Texts
*   i_api_mntxt4_tab =          " ehsw_tt_mntxt  Disposal Documents: Table Type for SAPscript Texts
*   i_api_mntxtdg_tab =         " ehsw_tt_mntxt
  IMPORTING
    e_mn_data_se =              " ehswas_mn_data_se  Disposal Documents: Complex Structure Disposal Document Data
    e_message_tab =             " ehsw_tt_message  Message Table Waste Management
    e_flg_error =               " esp1_boolean  Error Indicator
    .  "  EHSWA_270_MN_MAP_API_2_DATA_SE

ABAP code example for Function Module EHSWA_270_MN_MAP_API_2_DATA_SE

The ABAP code below is a full code listing to execute function module EHSWA_270_MN_MAP_API_2_DATA_SE 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_mn_data_se  
 
 TYPE EHSWAS_MN_DATA_SE
,
ld_e_message_tab  
 
 TYPE EHSW_TT_MESSAGE
,
ld_e_flg_error  
 
 TYPE ESP1_BOOLEAN
.


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

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

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

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

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

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

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

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

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

CALL FUNCTION 'EHSWA_270_MN_MAP_API_2_DATA_SE'
* EXPORTING
*   i_api_mn =                   ld_i_api_mn
*   i_api_mnpos_tab =            ld_i_api_mnpos_tab
*   i_api_mnwakey_tab =          ld_i_api_mnwakey_tab
*   i_api_mnbp_tab =             ld_i_api_mnbp_tab
*   i_api_mntxt1_tab =           ld_i_api_mntxt1_tab
*   i_api_mntxt2_tab =           ld_i_api_mntxt2_tab
*   i_api_mntxt3_tab =           ld_i_api_mntxt3_tab
*   i_api_mntxt4_tab =           ld_i_api_mntxt4_tab
*   i_api_mntxtdg_tab =          ld_i_api_mntxtdg_tab
  IMPORTING
    e_mn_data_se =               ld_e_mn_data_se
    e_message_tab =              ld_e_message_tab
    e_flg_error =                ld_e_flg_error
    .  "  EHSWA_270_MN_MAP_API_2_DATA_SE

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_mn_data_se
 
 TYPE EHSWAS_MN_DATA_SE ,
ld_i_api_mn
 
 TYPE EHSWAS_MNAPI ,
ld_e_message_tab
 
 TYPE EHSW_TT_MESSAGE ,
ld_i_api_mnpos_tab
 
 TYPE EHSWA_MNPOSAPI_TAB_TYPE ,
ld_e_flg_error
 
 TYPE ESP1_BOOLEAN ,
ld_i_api_mnwakey_tab
 
 TYPE EHSWA_MNWAKEYAPI_TAB_TYPE ,
ld_i_api_mnbp_tab
 
 TYPE EHSWA_MNBPAPI_TAB_TYPE ,
ld_i_api_mntxt1_tab
 
 TYPE EHSW_TT_MNTXT ,
ld_i_api_mntxt2_tab
 
 TYPE EHSW_TT_MNTXT ,
ld_i_api_mntxt3_tab
 
 TYPE EHSW_TT_MNTXT ,
ld_i_api_mntxt4_tab
 
 TYPE EHSW_TT_MNTXT ,
ld_i_api_mntxtdg_tab
 
 TYPE EHSW_TT_MNTXT .


ld_i_api_mn = 'Check type of data required'.
ld_i_api_mnpos_tab = 'Check type of data required'.
ld_i_api_mnwakey_tab = 'Check type of data required'.
ld_i_api_mnbp_tab = 'Check type of data required'.
ld_i_api_mntxt1_tab = 'Check type of data required'.
ld_i_api_mntxt2_tab = 'Check type of data required'.
ld_i_api_mntxt3_tab = 'Check type of data required'.
ld_i_api_mntxt4_tab = 'Check type of data required'.
ld_i_api_mntxtdg_tab = 'Check type of data required'.