SAP MM_ARRANG_EXTERN_DATA_PREPARE Function Module for NOTRANSL: Externe Daten für die Weiterverarbeitung aufbereiten und Kond. z
MM_ARRANG_EXTERN_DATA_PREPARE is a standard mm arrang extern data prepare SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Externe Daten für die Weiterverarbeitung aufbereiten und Kond. z 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 mm arrang extern data prepare FM, simply by entering the name MM_ARRANG_EXTERN_DATA_PREPARE into the relevant SAP transaction such as SE37 or SE38.
Function Group: WNF1
Program Name: SAPLWNF1
Main Program: SAPLWNF1
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MM_ARRANG_EXTERN_DATA_PREPARE 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 'MM_ARRANG_EXTERN_DATA_PREPARE'"NOTRANSL: Externe Daten für die Weiterverarbeitung aufbereiten und Kond. z.
EXPORTING
* ARRANGEMENT = "
* DATASET_NAME_FRONTEND = ' ' "
* READ_DATA_FROM_FRONTEND = ' ' "
EXTERNAL_DATA_STORNO = "
* ARRANGEMENT_NUMBER = "Arrangement No.
* MCKONAB_UPDATE = ' ' "
* MC_MODUS = 'A' "
* MC_VRSIO = '000' "Version update
* CONDITION_TYPE_CHECK = 'X' "
* CHECKRUN = 'X' "Verification Run
* EXTERNAL_DATA_READ = ' ' "
* DATASET_NAME = ' ' "
TABLES
* XEXTERNAL_DATA = "
* T_MCINF = "
* ERROR_MESSAGES = "List of errors which occurred
* XMCKONAB = "
* VARIABLE_KEY = "
* CONDITION = "Condition records (item data)
* CONDITION_HEADER = "Condition records (header data)
EXCEPTIONS
ARRANGEMENT_NOT_FOUND = 1 ARRANG_NO_CONDITIONS = 2 OPEN_FILE_ERROR = 3 FATAL_ERROR = 4 MCKONA_ERROR = 5 KOMG_ERROR = 6 CONDITION_TYP_ERROR = 7 INTERNAL_ERROR = 8 NO_MCKONAB_DATA_CREATE = 9
IMPORTING Parameters details for MM_ARRANG_EXTERN_DATA_PREPARE
ARRANGEMENT -
Data type: KONAOptional: Yes
Call by Reference: No ( called with pass by value option)
DATASET_NAME_FRONTEND -
Data type: RWMF1-FFILENAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
READ_DATA_FROM_FRONTEND -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXTERNAL_DATA_STORNO -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
ARRANGEMENT_NUMBER - Arrangement No.
Data type: KONA-KNUMAOptional: Yes
Call by Reference: No ( called with pass by value option)
MCKONAB_UPDATE -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MC_MODUS -
Data type: MCCONTROL-MODUSDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MC_VRSIO - Version update
Data type: MCCONTROL-VRSIODefault: '000'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CONDITION_TYPE_CHECK -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHECKRUN - Verification Run
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXTERNAL_DATA_READ -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DATASET_NAME -
Data type: RWMF1-AFILENAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MM_ARRANG_EXTERN_DATA_PREPARE
XEXTERNAL_DATA -
Data type: WBON_MCKONA_TAB_WITH_NOOptional: Yes
Call by Reference: No ( called with pass by value option)
T_MCINF -
Data type: MCSOINFOptional: Yes
Call by Reference: No ( called with pass by value option)
ERROR_MESSAGES - List of errors which occurred
Data type: ARRANGEXEROptional: Yes
Call by Reference: No ( called with pass by value option)
XMCKONAB -
Data type: MCKONABOptional: Yes
Call by Reference: No ( called with pass by value option)
VARIABLE_KEY -
Data type: VAKEOptional: Yes
Call by Reference: No ( called with pass by value option)
CONDITION - Condition records (item data)
Data type: KONPOptional: Yes
Call by Reference: No ( called with pass by value option)
CONDITION_HEADER - Condition records (header data)
Data type: KONHOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ARRANGEMENT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ARRANG_NO_CONDITIONS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OPEN_FILE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FATAL_ERROR - Fatal Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MCKONA_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
KOMG_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CONDITION_TYP_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR - Internal System Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_MCKONAB_DATA_CREATE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MM_ARRANG_EXTERN_DATA_PREPARE 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_arrangement | TYPE KONA, " | |||
| lt_xexternal_data | TYPE STANDARD TABLE OF WBON_MCKONA_TAB_WITH_NO, " | |||
| lv_arrangement_not_found | TYPE WBON_MCKONA_TAB_WITH_NO, " | |||
| lv_dataset_name_frontend | TYPE RWMF1-FFILENAME, " SPACE | |||
| lv_read_data_from_frontend | TYPE C, " SPACE | |||
| lv_external_data_storno | TYPE C, " | |||
| lt_t_mcinf | TYPE STANDARD TABLE OF MCSOINF, " | |||
| lv_arrangement_number | TYPE KONA-KNUMA, " | |||
| lv_arrang_no_conditions | TYPE KONA, " | |||
| lt_error_messages | TYPE STANDARD TABLE OF ARRANGEXER, " | |||
| lv_mckonab_update | TYPE C, " SPACE | |||
| lv_open_file_error | TYPE C, " | |||
| lv_mc_modus | TYPE MCCONTROL-MODUS, " 'A' | |||
| lt_xmckonab | TYPE STANDARD TABLE OF MCKONAB, " | |||
| lv_fatal_error | TYPE MCKONAB, " | |||
| lv_mc_vrsio | TYPE MCCONTROL-VRSIO, " '000' | |||
| lv_mckona_error | TYPE MCCONTROL, " | |||
| lt_variable_key | TYPE STANDARD TABLE OF VAKE, " | |||
| lt_condition | TYPE STANDARD TABLE OF KONP, " | |||
| lv_komg_error | TYPE KONP, " | |||
| lv_condition_type_check | TYPE C, " 'X' | |||
| lv_checkrun | TYPE C, " 'X' | |||
| lt_condition_header | TYPE STANDARD TABLE OF KONH, " | |||
| lv_condition_typ_error | TYPE KONH, " | |||
| lv_internal_error | TYPE KONH, " | |||
| lv_external_data_read | TYPE C, " SPACE | |||
| lv_dataset_name | TYPE RWMF1-AFILENAME, " SPACE | |||
| lv_no_mckonab_data_create | TYPE RWMF1. " |
|   CALL FUNCTION 'MM_ARRANG_EXTERN_DATA_PREPARE' "NOTRANSL: Externe Daten für die Weiterverarbeitung aufbereiten und Kond. z |
| EXPORTING | ||
| ARRANGEMENT | = lv_arrangement | |
| DATASET_NAME_FRONTEND | = lv_dataset_name_frontend | |
| READ_DATA_FROM_FRONTEND | = lv_read_data_from_frontend | |
| EXTERNAL_DATA_STORNO | = lv_external_data_storno | |
| ARRANGEMENT_NUMBER | = lv_arrangement_number | |
| MCKONAB_UPDATE | = lv_mckonab_update | |
| MC_MODUS | = lv_mc_modus | |
| MC_VRSIO | = lv_mc_vrsio | |
| CONDITION_TYPE_CHECK | = lv_condition_type_check | |
| CHECKRUN | = lv_checkrun | |
| EXTERNAL_DATA_READ | = lv_external_data_read | |
| DATASET_NAME | = lv_dataset_name | |
| TABLES | ||
| XEXTERNAL_DATA | = lt_xexternal_data | |
| T_MCINF | = lt_t_mcinf | |
| ERROR_MESSAGES | = lt_error_messages | |
| XMCKONAB | = lt_xmckonab | |
| VARIABLE_KEY | = lt_variable_key | |
| CONDITION | = lt_condition | |
| CONDITION_HEADER | = lt_condition_header | |
| EXCEPTIONS | ||
| ARRANGEMENT_NOT_FOUND = 1 | ||
| ARRANG_NO_CONDITIONS = 2 | ||
| OPEN_FILE_ERROR = 3 | ||
| FATAL_ERROR = 4 | ||
| MCKONA_ERROR = 5 | ||
| KOMG_ERROR = 6 | ||
| CONDITION_TYP_ERROR = 7 | ||
| INTERNAL_ERROR = 8 | ||
| NO_MCKONAB_DATA_CREATE = 9 | ||
| . " MM_ARRANG_EXTERN_DATA_PREPARE | ||
ABAP code using 7.40 inline data declarations to call FM MM_ARRANG_EXTERN_DATA_PREPARE
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.| "SELECT single FFILENAME FROM RWMF1 INTO @DATA(ld_dataset_name_frontend). | ||||
| DATA(ld_dataset_name_frontend) | = ' '. | |||
| DATA(ld_read_data_from_frontend) | = ' '. | |||
| "SELECT single KNUMA FROM KONA INTO @DATA(ld_arrangement_number). | ||||
| DATA(ld_mckonab_update) | = ' '. | |||
| "SELECT single MODUS FROM MCCONTROL INTO @DATA(ld_mc_modus). | ||||
| DATA(ld_mc_modus) | = 'A'. | |||
| "SELECT single VRSIO FROM MCCONTROL INTO @DATA(ld_mc_vrsio). | ||||
| DATA(ld_mc_vrsio) | = '000'. | |||
| DATA(ld_condition_type_check) | = 'X'. | |||
| DATA(ld_checkrun) | = 'X'. | |||
| DATA(ld_external_data_read) | = ' '. | |||
| "SELECT single AFILENAME FROM RWMF1 INTO @DATA(ld_dataset_name). | ||||
| DATA(ld_dataset_name) | = ' '. | |||
Search for further information about these or an SAP related objects