SAP MDRD_PACKET_LOAD Function Module for NOTRANSL: Ermittlung Belieferungsbeziehung für mehrere Kombinationen
MDRD_PACKET_LOAD is a standard mdrd packet load 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: Ermittlung Belieferungsbeziehung für mehrere Kombinationen 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 mdrd packet load FM, simply by entering the name MDRD_PACKET_LOAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: MDRD
Program Name: SAPLMDRD
Main Program: SAPLMDRD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function MDRD_PACKET_LOAD 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 'MDRD_PACKET_LOAD'"NOTRANSL: Ermittlung Belieferungsbeziehung für mehrere Kombinationen.
EXPORTING
I_CONTROL_PACKET_LOAD = "Control Structure for Package Processing During AHD Load
I_HEADER_PACKET_LOAD = "Header Stucture for Package Processing When Loading DRD
I_T_MARC_M = "Extract MARC
IMPORTING
E_HEADER_PACKET_LOAD = "Header Stucture for Package Processing When Loading DRD
CHANGING
CH_T_DRD_COUPLES = "Couples for Which DRD Data Is to Be Loaded
CH_T_TMDRD_DOCTP = "Delivery Relationshp: Document Types per Document Category
CH_T_MINUTES = "Log Structure for the Alternative Historical Data Scenario
EXCEPTIONS
NO_DRD_DATA = 1
IMPORTING Parameters details for MDRD_PACKET_LOAD
I_CONTROL_PACKET_LOAD - Control Structure for Package Processing During AHD Load
Data type: MDRD_S_CONTROL_PACKET_LOADOptional: No
Call by Reference: No ( called with pass by value option)
I_HEADER_PACKET_LOAD - Header Stucture for Package Processing When Loading DRD
Data type: MDRD_S_HEADER_PACKET_LOADOptional: No
Call by Reference: No ( called with pass by value option)
I_T_MARC_M - Extract MARC
Data type: MDRD_T_EXTR_MARCOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MDRD_PACKET_LOAD
E_HEADER_PACKET_LOAD - Header Stucture for Package Processing When Loading DRD
Data type: MDRD_S_HEADER_PACKET_LOADOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for MDRD_PACKET_LOAD
CH_T_DRD_COUPLES - Couples for Which DRD Data Is to Be Loaded
Data type: MDRD_T_DRD_COUPLESOptional: No
Call by Reference: No ( called with pass by value option)
CH_T_TMDRD_DOCTP - Delivery Relationshp: Document Types per Document Category
Data type: MDRD_T_TMDRD_DOCTPOptional: No
Call by Reference: No ( called with pass by value option)
CH_T_MINUTES - Log Structure for the Alternative Historical Data Scenario
Data type: MDRD_T_MINUTESOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DRD_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MDRD_PACKET_LOAD 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_no_drd_data | TYPE STRING, " | |||
| lv_ch_t_drd_couples | TYPE MDRD_T_DRD_COUPLES, " | |||
| lv_e_header_packet_load | TYPE MDRD_S_HEADER_PACKET_LOAD, " | |||
| lv_i_control_packet_load | TYPE MDRD_S_CONTROL_PACKET_LOAD, " | |||
| lv_ch_t_tmdrd_doctp | TYPE MDRD_T_TMDRD_DOCTP, " | |||
| lv_i_header_packet_load | TYPE MDRD_S_HEADER_PACKET_LOAD, " | |||
| lv_i_t_marc_m | TYPE MDRD_T_EXTR_MARC, " | |||
| lv_ch_t_minutes | TYPE MDRD_T_MINUTES. " |
|   CALL FUNCTION 'MDRD_PACKET_LOAD' "NOTRANSL: Ermittlung Belieferungsbeziehung für mehrere Kombinationen |
| EXPORTING | ||
| I_CONTROL_PACKET_LOAD | = lv_i_control_packet_load | |
| I_HEADER_PACKET_LOAD | = lv_i_header_packet_load | |
| I_T_MARC_M | = lv_i_t_marc_m | |
| IMPORTING | ||
| E_HEADER_PACKET_LOAD | = lv_e_header_packet_load | |
| CHANGING | ||
| CH_T_DRD_COUPLES | = lv_ch_t_drd_couples | |
| CH_T_TMDRD_DOCTP | = lv_ch_t_tmdrd_doctp | |
| CH_T_MINUTES | = lv_ch_t_minutes | |
| EXCEPTIONS | ||
| NO_DRD_DATA = 1 | ||
| . " MDRD_PACKET_LOAD | ||
ABAP code using 7.40 inline data declarations to call FM MDRD_PACKET_LOAD
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