SAP MDRP_SAVE_CHANGES Function Module for NOTRANSL: Save changes of DRP network
MDRP_SAVE_CHANGES is a standard mdrp save changes 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: Save changes of DRP network 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 mdrp save changes FM, simply by entering the name MDRP_SAVE_CHANGES into the relevant SAP transaction such as SE37 or SE38.
Function Group: MDRP
Program Name: SAPLMDRP
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function MDRP_SAVE_CHANGES 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 'MDRP_SAVE_CHANGES'"NOTRANSL: Save changes of DRP network.
EXPORTING
I_MDRP_CONTROL = "Control Parameters for DRP Network
IMPORTING
E_MDRP_CONTROL = "Control Parameters for DRP Network
SUCCESS_CODE = "ABAP System Field: Return Code of ABAP Statements
TABLES
T_MAP_CHANGES = "All information on a map for exchange
T_NODE_POSITION_CHANGES = "Position of a node in a DRP network
T_ARC_CHANGES = "Arc of a DRP network
T_ARC_INFO_CHANGES = "Information on DRP Arcs like Percentages
T_PATH_INFO = "Information on DRP Arcs like Percentages
T_PATH = "Path of a DRP network
T_ARCD = "Arc details
T_PATHH = "Path of a DRP Network
IMPORTING Parameters details for MDRP_SAVE_CHANGES
I_MDRP_CONTROL - Control Parameters for DRP Network
Data type: MDRP_PARAOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MDRP_SAVE_CHANGES
E_MDRP_CONTROL - Control Parameters for DRP Network
Data type: MDRP_PARAOptional: No
Call by Reference: No ( called with pass by value option)
SUCCESS_CODE - ABAP System Field: Return Code of ABAP Statements
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MDRP_SAVE_CHANGES
T_MAP_CHANGES - All information on a map for exchange
Data type: MDRP_MAP_AOptional: No
Call by Reference: No ( called with pass by value option)
T_NODE_POSITION_CHANGES - Position of a node in a DRP network
Data type: MDRP_NODPAOptional: No
Call by Reference: No ( called with pass by value option)
T_ARC_CHANGES - Arc of a DRP network
Data type: MDRP_ARCOptional: No
Call by Reference: No ( called with pass by value option)
T_ARC_INFO_CHANGES - Information on DRP Arcs like Percentages
Data type: MDRP_ARC_IOptional: No
Call by Reference: No ( called with pass by value option)
T_PATH_INFO - Information on DRP Arcs like Percentages
Data type: MDRP_PATH_IOptional: No
Call by Reference: No ( called with pass by value option)
T_PATH - Path of a DRP network
Data type: MDRP_PATHOptional: No
Call by Reference: No ( called with pass by value option)
T_ARCD - Arc details
Data type: MDRP_ARCDOptional: No
Call by Reference: No ( called with pass by value option)
T_PATHH - Path of a DRP Network
Data type: MDRP_PATHHOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MDRP_SAVE_CHANGES 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: | ||||
| lt_t_map_changes | TYPE STANDARD TABLE OF MDRP_MAP_A, " | |||
| lv_e_mdrp_control | TYPE MDRP_PARA, " | |||
| lv_i_mdrp_control | TYPE MDRP_PARA, " | |||
| lv_success_code | TYPE SY-SUBRC, " | |||
| lt_t_node_position_changes | TYPE STANDARD TABLE OF MDRP_NODPA, " | |||
| lt_t_arc_changes | TYPE STANDARD TABLE OF MDRP_ARC, " | |||
| lt_t_arc_info_changes | TYPE STANDARD TABLE OF MDRP_ARC_I, " | |||
| lt_t_path_info | TYPE STANDARD TABLE OF MDRP_PATH_I, " | |||
| lt_t_path | TYPE STANDARD TABLE OF MDRP_PATH, " | |||
| lt_t_arcd | TYPE STANDARD TABLE OF MDRP_ARCD, " | |||
| lt_t_pathh | TYPE STANDARD TABLE OF MDRP_PATHH. " |
| CALL FUNCTION 'MDRP_SAVE_CHANGES' "NOTRANSL: Save changes of DRP network |
| EXPORTING | ||
| I_MDRP_CONTROL | = lv_i_mdrp_control | |
| IMPORTING | ||
| E_MDRP_CONTROL | = lv_e_mdrp_control | |
| SUCCESS_CODE | = lv_success_code | |
| TABLES | ||
| T_MAP_CHANGES | = lt_t_map_changes | |
| T_NODE_POSITION_CHANGES | = lt_t_node_position_changes | |
| T_ARC_CHANGES | = lt_t_arc_changes | |
| T_ARC_INFO_CHANGES | = lt_t_arc_info_changes | |
| T_PATH_INFO | = lt_t_path_info | |
| T_PATH | = lt_t_path | |
| T_ARCD | = lt_t_arcd | |
| T_PATHH | = lt_t_pathh | |
| . " MDRP_SAVE_CHANGES | ||
ABAP code using 7.40 inline data declarations to call FM MDRP_SAVE_CHANGES
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 SUBRC FROM SY INTO @DATA(ld_success_code). | ||||
Search for further information about these or an SAP related objects