SAP MDG_BS_BP_DRF_EXTRACT_READ Function Module for MDG: Read BP data by DRF outbound impl. (w/o send)
MDG_BS_BP_DRF_EXTRACT_READ is a standard mdg bs bp drf extract read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MDG: Read BP data by DRF outbound impl. (w/o send) 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 mdg bs bp drf extract read FM, simply by entering the name MDG_BS_BP_DRF_EXTRACT_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: MDG_BUPA_OUTBOUND
Program Name: SAPLMDG_BUPA_OUTBOUND
Main Program: SAPLMDG_BUPA_OUTBOUND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function MDG_BS_BP_DRF_EXTRACT_READ 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 'MDG_BS_BP_DRF_EXTRACT_READ'"MDG: Read BP data by DRF outbound impl. (w/o send).
EXPORTING
IV_PARTNER = "Business Partner Number
IV_LOGSYS = "Logical system-id of the receiving system
* IV_MSG_LINK = "Message Number
* IV_READ_BPREL = ABAP_FALSE "Flag: Read Business Partner Relationships too
IMPORTING
ES_BP_DATA = "Business Partner data
ET_BP_REL_DATA = "Business Partner Relationship Data
ET_MESSAGES = "Return parameter table
ET_BAL_MESSAGES = "Application log: log message
IMPORTING Parameters details for MDG_BS_BP_DRF_EXTRACT_READ
IV_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
IV_LOGSYS - Logical system-id of the receiving system
Data type: LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
IV_MSG_LINK - Message Number
Data type: DRF_MESSAGE_LINKOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_READ_BPREL - Flag: Read Business Partner Relationships too
Data type: BOOLE_DDefault: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MDG_BS_BP_DRF_EXTRACT_READ
ES_BP_DATA - Business Partner data
Data type: MDG_BP_BPSUITEBULK_RPLCT_REQ_MOptional: No
Call by Reference: No ( called with pass by value option)
ET_BP_REL_DATA - Business Partner Relationship Data
Data type: MDG_BP_RELSUITERQ_MSG_TOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGES - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: No ( called with pass by value option)
ET_BAL_MESSAGES - Application log: log message
Data type: BALM_TOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MDG_BS_BP_DRF_EXTRACT_READ 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_es_bp_data | TYPE MDG_BP_BPSUITEBULK_RPLCT_REQ_M, " | |||
| lv_iv_partner | TYPE BU_PARTNER, " | |||
| lv_iv_logsys | TYPE LOGSYS, " | |||
| lv_et_bp_rel_data | TYPE MDG_BP_RELSUITERQ_MSG_T, " | |||
| lv_et_messages | TYPE BAPIRET2_T, " | |||
| lv_iv_msg_link | TYPE DRF_MESSAGE_LINK, " | |||
| lv_iv_read_bprel | TYPE BOOLE_D, " ABAP_FALSE | |||
| lv_et_bal_messages | TYPE BALM_T. " |
|   CALL FUNCTION 'MDG_BS_BP_DRF_EXTRACT_READ' "MDG: Read BP data by DRF outbound impl. (w/o send) |
| EXPORTING | ||
| IV_PARTNER | = lv_iv_partner | |
| IV_LOGSYS | = lv_iv_logsys | |
| IV_MSG_LINK | = lv_iv_msg_link | |
| IV_READ_BPREL | = lv_iv_read_bprel | |
| IMPORTING | ||
| ES_BP_DATA | = lv_es_bp_data | |
| ET_BP_REL_DATA | = lv_et_bp_rel_data | |
| ET_MESSAGES | = lv_et_messages | |
| ET_BAL_MESSAGES | = lv_et_bal_messages | |
| . " MDG_BS_BP_DRF_EXTRACT_READ | ||
ABAP code using 7.40 inline data declarations to call FM MDG_BS_BP_DRF_EXTRACT_READ
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.| DATA(ld_iv_read_bprel) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects