SAP MATERIAL_UPDATE_LOGISTIC_DATA Function Module for NOTRANSL: Massenänderung für Logistikdaten
MATERIAL_UPDATE_LOGISTIC_DATA is a standard material update logistic data 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: Massenänderung für Logistikdaten 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 material update logistic data FM, simply by entering the name MATERIAL_UPDATE_LOGISTIC_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: MGUV
Program Name: SAPLMGUV
Main Program: SAPLMGUV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MATERIAL_UPDATE_LOGISTIC_DATA 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 'MATERIAL_UPDATE_LOGISTIC_DATA'"NOTRANSL: Massenänderung für Logistikdaten.
EXPORTING
* IV_BLOCK_SIZE = 100 "
* IV_LOCK_MODE = 'G' "
* IV_NO_CHANGE_DOC = "
* IV_NO_CHANGE_PTR = "
* IV_CHECK_ONLY_FIRST_SITE = "
* IV_NO_COMMIT = "
TABLES
IT_UPD_FIELD_NAMES = "
* IT_T001W = "
* IT_NEW_MARC_DATA = "
* IT_NEW_WRPL_DATA = "
* IT_NEW_MPOP_DATA = "
* IT_SITE_KEYS = "
OT_MESSAGES = "
* OT_PROCESSED_MARC_DATA = "
* OT_PROCESSED_WRPL_DATA = "
* OT_PROCESSED_MPOP_DATA = "
EXCEPTIONS
WRONG_INPUT_DATA = 1 WRONG_REFERENCE_HANDLING = 2 LOCK_PROBLEMS = 3 FOREIGN_KEY_CHECK_ERROR = 4 SPECIAL_CHECK_ERROR = 5
IMPORTING Parameters details for MATERIAL_UPDATE_LOGISTIC_DATA
IV_BLOCK_SIZE -
Data type: MDAT1-MAX_COMMDefault: 100
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_LOCK_MODE -
Data type: MDAT1-SPERADefault: 'G'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_CHANGE_DOC -
Data type: SY-DATAROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_CHANGE_PTR -
Data type: SY-DATAROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CHECK_ONLY_FIRST_SITE -
Data type: SY-DATAROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_COMMIT -
Data type: SY-DATAROptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MATERIAL_UPDATE_LOGISTIC_DATA
IT_UPD_FIELD_NAMES -
Data type: UPD_FIELD_TABOptional: No
Call by Reference: Yes
IT_T001W -
Data type: T001WOptional: Yes
Call by Reference: Yes
IT_NEW_MARC_DATA -
Data type: MARCOptional: Yes
Call by Reference: Yes
IT_NEW_WRPL_DATA -
Data type: WRPLOptional: Yes
Call by Reference: Yes
IT_NEW_MPOP_DATA -
Data type: MPOPOptional: Yes
Call by Reference: Yes
IT_SITE_KEYS -
Data type: PRE01Optional: Yes
Call by Reference: Yes
OT_MESSAGES -
Data type: BAPIRET2Optional: No
Call by Reference: Yes
OT_PROCESSED_MARC_DATA -
Data type: MARCOptional: Yes
Call by Reference: Yes
OT_PROCESSED_WRPL_DATA -
Data type: WRPLOptional: Yes
Call by Reference: Yes
OT_PROCESSED_MPOP_DATA -
Data type: MPOPOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
WRONG_INPUT_DATA - Incorrect input data
Data type:Optional: No
Call by Reference: Yes
WRONG_REFERENCE_HANDLING -
Data type:Optional: No
Call by Reference: Yes
LOCK_PROBLEMS -
Data type:Optional: No
Call by Reference: Yes
FOREIGN_KEY_CHECK_ERROR -
Data type:Optional: No
Call by Reference: Yes
SPECIAL_CHECK_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MATERIAL_UPDATE_LOGISTIC_DATA 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_iv_block_size | TYPE MDAT1-MAX_COMM, " 100 | |||
| lv_wrong_input_data | TYPE MDAT1, " | |||
| lt_it_upd_field_names | TYPE STANDARD TABLE OF UPD_FIELD_TAB, " | |||
| lt_it_t001w | TYPE STANDARD TABLE OF T001W, " | |||
| lv_iv_lock_mode | TYPE MDAT1-SPERA, " 'G' | |||
| lt_it_new_marc_data | TYPE STANDARD TABLE OF MARC, " | |||
| lv_wrong_reference_handling | TYPE MARC, " | |||
| lv_lock_problems | TYPE MARC, " | |||
| lt_it_new_wrpl_data | TYPE STANDARD TABLE OF WRPL, " | |||
| lv_iv_no_change_doc | TYPE SY-DATAR, " | |||
| lt_it_new_mpop_data | TYPE STANDARD TABLE OF MPOP, " | |||
| lv_iv_no_change_ptr | TYPE SY-DATAR, " | |||
| lv_foreign_key_check_error | TYPE SY, " | |||
| lt_it_site_keys | TYPE STANDARD TABLE OF PRE01, " | |||
| lv_special_check_error | TYPE PRE01, " | |||
| lv_iv_check_only_first_site | TYPE SY-DATAR, " | |||
| lt_ot_messages | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_iv_no_commit | TYPE SY-DATAR, " | |||
| lt_ot_processed_marc_data | TYPE STANDARD TABLE OF MARC, " | |||
| lt_ot_processed_wrpl_data | TYPE STANDARD TABLE OF WRPL, " | |||
| lt_ot_processed_mpop_data | TYPE STANDARD TABLE OF MPOP. " |
|   CALL FUNCTION 'MATERIAL_UPDATE_LOGISTIC_DATA' "NOTRANSL: Massenänderung für Logistikdaten |
| EXPORTING | ||
| IV_BLOCK_SIZE | = lv_iv_block_size | |
| IV_LOCK_MODE | = lv_iv_lock_mode | |
| IV_NO_CHANGE_DOC | = lv_iv_no_change_doc | |
| IV_NO_CHANGE_PTR | = lv_iv_no_change_ptr | |
| IV_CHECK_ONLY_FIRST_SITE | = lv_iv_check_only_first_site | |
| IV_NO_COMMIT | = lv_iv_no_commit | |
| TABLES | ||
| IT_UPD_FIELD_NAMES | = lt_it_upd_field_names | |
| IT_T001W | = lt_it_t001w | |
| IT_NEW_MARC_DATA | = lt_it_new_marc_data | |
| IT_NEW_WRPL_DATA | = lt_it_new_wrpl_data | |
| IT_NEW_MPOP_DATA | = lt_it_new_mpop_data | |
| IT_SITE_KEYS | = lt_it_site_keys | |
| OT_MESSAGES | = lt_ot_messages | |
| OT_PROCESSED_MARC_DATA | = lt_ot_processed_marc_data | |
| OT_PROCESSED_WRPL_DATA | = lt_ot_processed_wrpl_data | |
| OT_PROCESSED_MPOP_DATA | = lt_ot_processed_mpop_data | |
| EXCEPTIONS | ||
| WRONG_INPUT_DATA = 1 | ||
| WRONG_REFERENCE_HANDLING = 2 | ||
| LOCK_PROBLEMS = 3 | ||
| FOREIGN_KEY_CHECK_ERROR = 4 | ||
| SPECIAL_CHECK_ERROR = 5 | ||
| . " MATERIAL_UPDATE_LOGISTIC_DATA | ||
ABAP code using 7.40 inline data declarations to call FM MATERIAL_UPDATE_LOGISTIC_DATA
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 MAX_COMM FROM MDAT1 INTO @DATA(ld_iv_block_size). | ||||
| DATA(ld_iv_block_size) | = 100. | |||
| "SELECT single SPERA FROM MDAT1 INTO @DATA(ld_iv_lock_mode). | ||||
| DATA(ld_iv_lock_mode) | = 'G'. | |||
| "SELECT single DATAR FROM SY INTO @DATA(ld_iv_no_change_doc). | ||||
| "SELECT single DATAR FROM SY INTO @DATA(ld_iv_no_change_ptr). | ||||
| "SELECT single DATAR FROM SY INTO @DATA(ld_iv_check_only_first_site). | ||||
| "SELECT single DATAR FROM SY INTO @DATA(ld_iv_no_commit). | ||||
Search for further information about these or an SAP related objects