SAP Function Modules
1119_TRANSL_EXT_INT SAP Function module
1119_TRANSL_EXT_INT 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 1119_TRANSL_EXT_INT into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
1119
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM 1119_TRANSL_EXT_INT - 1119 TRANSL EXT INT
CALL FUNCTION '1119_TRANSL_EXT_INT' "
* TABLES
* i_hazsub_header = " bapi_1119_md EHS: Hazardous Substance Basic Data
* i_hazsub_textdata = " bapi_1119_dt EHS: Hazardous Substance Additional Data 1 (Text Type)
* i_hazsub_numdata = " bapi_1119_dn EHS: Hazardous Substance Additional Data 2 (Numeric Type)
* e_hazsub_header_api = " hsms_mdapi EHS: API Hazardous Substance Basic Data
* e_hazsub_textdata_api = " hsms_dtapi EHS: API Hazardous Substance Addit. Data 1 (Text Type)
* e_hazsub_numdata_api = " hsms_dnapi EHS: API Hazardous Substance Addit. Data 2 (Numeric Type)
* e_return = " bapiret2 Return Parameter(s)
. " 1119_TRANSL_EXT_INT
ABAP code example for Function Module 1119_TRANSL_EXT_INT
The ABAP code below is a full code listing to execute function module 1119_TRANSL_EXT_INT 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).
| it_i_hazsub_header | TYPE STANDARD TABLE OF BAPI_1119_MD,"TABLES PARAM |
| wa_i_hazsub_header | LIKE LINE OF it_i_hazsub_header , |
| it_i_hazsub_textdata | TYPE STANDARD TABLE OF BAPI_1119_DT,"TABLES PARAM |
| wa_i_hazsub_textdata | LIKE LINE OF it_i_hazsub_textdata , |
| it_i_hazsub_numdata | TYPE STANDARD TABLE OF BAPI_1119_DN,"TABLES PARAM |
| wa_i_hazsub_numdata | LIKE LINE OF it_i_hazsub_numdata , |
| it_e_hazsub_header_api | TYPE STANDARD TABLE OF HSMS_MDAPI,"TABLES PARAM |
| wa_e_hazsub_header_api | LIKE LINE OF it_e_hazsub_header_api , |
| it_e_hazsub_textdata_api | TYPE STANDARD TABLE OF HSMS_DTAPI,"TABLES PARAM |
| wa_e_hazsub_textdata_api | LIKE LINE OF it_e_hazsub_textdata_api , |
| it_e_hazsub_numdata_api | TYPE STANDARD TABLE OF HSMS_DNAPI,"TABLES PARAM |
| wa_e_hazsub_numdata_api | LIKE LINE OF it_e_hazsub_numdata_api , |
| it_e_return | TYPE STANDARD TABLE OF BAPIRET2,"TABLES PARAM |
| wa_e_return | LIKE LINE OF it_e_return . |
"populate fields of struture and append to itab
append wa_i_hazsub_header to it_i_hazsub_header.
"populate fields of struture and append to itab
append wa_i_hazsub_textdata to it_i_hazsub_textdata.
"populate fields of struture and append to itab
append wa_i_hazsub_numdata to it_i_hazsub_numdata.
"populate fields of struture and append to itab
append wa_e_hazsub_header_api to it_e_hazsub_header_api.
"populate fields of struture and append to itab
append wa_e_hazsub_textdata_api to it_e_hazsub_textdata_api.
"populate fields of struture and append to itab
append wa_e_hazsub_numdata_api to it_e_hazsub_numdata_api.
"populate fields of struture and append to itab
append wa_e_return to it_e_return. . CALL FUNCTION '1119_TRANSL_EXT_INT' * TABLES * i_hazsub_header = it_i_hazsub_header * i_hazsub_textdata = it_i_hazsub_textdata * i_hazsub_numdata = it_i_hazsub_numdata * e_hazsub_header_api = it_e_hazsub_header_api * e_hazsub_textdata_api = it_e_hazsub_textdata_api * e_hazsub_numdata_api = it_e_hazsub_numdata_api * e_return = it_e_return . " 1119_TRANSL_EXT_INT
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:
| it_i_hazsub_header | TYPE STANDARD TABLE OF BAPI_1119_MD , |
| wa_i_hazsub_header | LIKE LINE OF it_i_hazsub_header, |
| it_i_hazsub_textdata | TYPE STANDARD TABLE OF BAPI_1119_DT , |
| wa_i_hazsub_textdata | LIKE LINE OF it_i_hazsub_textdata, |
| it_i_hazsub_numdata | TYPE STANDARD TABLE OF BAPI_1119_DN , |
| wa_i_hazsub_numdata | LIKE LINE OF it_i_hazsub_numdata, |
| it_e_hazsub_header_api | TYPE STANDARD TABLE OF HSMS_MDAPI , |
| wa_e_hazsub_header_api | LIKE LINE OF it_e_hazsub_header_api, |
| it_e_hazsub_textdata_api | TYPE STANDARD TABLE OF HSMS_DTAPI , |
| wa_e_hazsub_textdata_api | LIKE LINE OF it_e_hazsub_textdata_api, |
| it_e_hazsub_numdata_api | TYPE STANDARD TABLE OF HSMS_DNAPI , |
| wa_e_hazsub_numdata_api | LIKE LINE OF it_e_hazsub_numdata_api, |
| it_e_return | TYPE STANDARD TABLE OF BAPIRET2 , |
| wa_e_return | LIKE LINE OF it_e_return. |
"populate fields of struture and append to itab
append wa_i_hazsub_header to it_i_hazsub_header.
"populate fields of struture and append to itab
append wa_i_hazsub_textdata to it_i_hazsub_textdata.
"populate fields of struture and append to itab
append wa_i_hazsub_numdata to it_i_hazsub_numdata.
"populate fields of struture and append to itab
append wa_e_hazsub_header_api to it_e_hazsub_header_api.
"populate fields of struture and append to itab
append wa_e_hazsub_textdata_api to it_e_hazsub_textdata_api.
"populate fields of struture and append to itab
append wa_e_hazsub_numdata_api to it_e_hazsub_numdata_api.
"populate fields of struture and append to itab
append wa_e_return to it_e_return.
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 1119_TRANSL_EXT_INT or its description.