SAP ISU_M_SAMPLE_CONVERT Function Module for Example for Creating Import File from Text File
ISU_M_SAMPLE_CONVERT is a standard isu m sample convert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Example for Creating Import File from Text File processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for isu m sample convert FM, simply by entering the name ISU_M_SAMPLE_CONVERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: EMIG_SAMPLE_CONVERT
Program Name: SAPLEMIG_SAMPLE_CONVERT
Main Program: SAPLEMIG_SAMPLE_CONVERT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_M_SAMPLE_CONVERT pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'ISU_M_SAMPLE_CONVERT'"Example for Creating Import File from Text File.
EXPORTING
* X_FIRMA = "Company (Client) for Migration
* X_OBJECT = "Migration Object
* X_REF_OBJECT = "Migration Object
* X_DTTYP = "
* X_OCCURENCE = "Loop Index
IMPORTING
Y_OLDKEY = "Object key of legacy system
Y_ACTION_STRUCTURE = "Processing Type
Y_ACTION_OBJECT = "Processing Type
Y_ACTION_FILE = "Processing Type
CHANGING
XY_CUSTOMER = "
TABLES
* XT_HEADER_TAB = "
* XT_DATA_TAB = "
* XT_ADD_DATA_1 = "
* XT_ADD_DATA_2 = "
* XT_ADD_DATA_3 = "
* XT_ADD_DATA_4 = "
* XT_ADD_DATA_5 = "
IMPORTING Parameters details for ISU_M_SAMPLE_CONVERT
X_FIRMA - Company (Client) for Migration
Data type: EMG_FIRMAOptional: Yes
Call by Reference: Yes
X_OBJECT - Migration Object
Data type: EMG_OBJECTOptional: Yes
Call by Reference: Yes
X_REF_OBJECT - Migration Object
Data type: EMG_OBJECTOptional: Yes
Call by Reference: Yes
X_DTTYP -
Data type: EMG_DTTYPOptional: Yes
Call by Reference: Yes
X_OCCURENCE - Loop Index
Data type: SYINDEXOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISU_M_SAMPLE_CONVERT
Y_OLDKEY - Object key of legacy system
Data type: EMG_OLDKEYOptional: No
Call by Reference: Yes
Y_ACTION_STRUCTURE - Processing Type
Data type: EMG_WMODEOptional: No
Call by Reference: Yes
Y_ACTION_OBJECT - Processing Type
Data type: EMG_WMODEOptional: No
Call by Reference: Yes
Y_ACTION_FILE - Processing Type
Data type: EMG_WMODEOptional: No
Call by Reference: Yes
CHANGING Parameters details for ISU_M_SAMPLE_CONVERT
XY_CUSTOMER -
Data type:Optional: No
Call by Reference: Yes
TABLES Parameters details for ISU_M_SAMPLE_CONVERT
XT_HEADER_TAB -
Data type:Optional: Yes
Call by Reference: Yes
XT_DATA_TAB -
Data type:Optional: Yes
Call by Reference: Yes
XT_ADD_DATA_1 -
Data type:Optional: Yes
Call by Reference: Yes
XT_ADD_DATA_2 -
Data type:Optional: Yes
Call by Reference: Yes
XT_ADD_DATA_3 -
Data type:Optional: Yes
Call by Reference: Yes
XT_ADD_DATA_4 -
Data type:Optional: Yes
Call by Reference: Yes
XT_ADD_DATA_5 -
Data type:Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for ISU_M_SAMPLE_CONVERT Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_x_firma | TYPE EMG_FIRMA, " | |||
| lv_y_oldkey | TYPE EMG_OLDKEY, " | |||
| lv_xy_customer | TYPE EMG_OLDKEY, " | |||
| lt_xt_header_tab | TYPE STANDARD TABLE OF EMG_OLDKEY, " | |||
| lv_x_object | TYPE EMG_OBJECT, " | |||
| lt_xt_data_tab | TYPE STANDARD TABLE OF EMG_OBJECT, " | |||
| lv_y_action_structure | TYPE EMG_WMODE, " | |||
| lv_x_ref_object | TYPE EMG_OBJECT, " | |||
| lt_xt_add_data_1 | TYPE STANDARD TABLE OF EMG_OBJECT, " | |||
| lv_y_action_object | TYPE EMG_WMODE, " | |||
| lv_x_dttyp | TYPE EMG_DTTYP, " | |||
| lt_xt_add_data_2 | TYPE STANDARD TABLE OF EMG_DTTYP, " | |||
| lv_y_action_file | TYPE EMG_WMODE, " | |||
| lv_x_occurence | TYPE SYINDEX, " | |||
| lt_xt_add_data_3 | TYPE STANDARD TABLE OF SYINDEX, " | |||
| lt_xt_add_data_4 | TYPE STANDARD TABLE OF SYINDEX, " | |||
| lt_xt_add_data_5 | TYPE STANDARD TABLE OF SYINDEX. " |
|   CALL FUNCTION 'ISU_M_SAMPLE_CONVERT' "Example for Creating Import File from Text File |
| EXPORTING | ||
| X_FIRMA | = lv_x_firma | |
| X_OBJECT | = lv_x_object | |
| X_REF_OBJECT | = lv_x_ref_object | |
| X_DTTYP | = lv_x_dttyp | |
| X_OCCURENCE | = lv_x_occurence | |
| IMPORTING | ||
| Y_OLDKEY | = lv_y_oldkey | |
| Y_ACTION_STRUCTURE | = lv_y_action_structure | |
| Y_ACTION_OBJECT | = lv_y_action_object | |
| Y_ACTION_FILE | = lv_y_action_file | |
| CHANGING | ||
| XY_CUSTOMER | = lv_xy_customer | |
| TABLES | ||
| XT_HEADER_TAB | = lt_xt_header_tab | |
| XT_DATA_TAB | = lt_xt_data_tab | |
| XT_ADD_DATA_1 | = lt_xt_add_data_1 | |
| XT_ADD_DATA_2 | = lt_xt_add_data_2 | |
| XT_ADD_DATA_3 | = lt_xt_add_data_3 | |
| XT_ADD_DATA_4 | = lt_xt_add_data_4 | |
| XT_ADD_DATA_5 | = lt_xt_add_data_5 | |
| . " ISU_M_SAMPLE_CONVERT | ||
ABAP code using 7.40 inline data declarations to call FM ISU_M_SAMPLE_CONVERT
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects