SAP DPE_GET_PARTNER Function Module for Get Bidder
DPE_GET_PARTNER is a standard dpe get partner SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Bidder 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 dpe get partner FM, simply by entering the name DPE_GET_PARTNER into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_DPE_INTEGRATION
Program Name: SAPLBBP_DPE_INTEGRATION
Main Program: SAPLBBP_DPE_INTEGRATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DPE_GET_PARTNER 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 'DPE_GET_PARTNER'"Get Bidder.
EXPORTING
IS_SEL_PARTNER = "Bidder selektion
TABLES
ET_PARTNER = "Bidder company
IMPORTING Parameters details for DPE_GET_PARTNER
IS_SEL_PARTNER - Bidder selektion
Data type: DPE_SEL_BIDDEROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DPE_GET_PARTNER
ET_PARTNER - Bidder company
Data type: DPE_BIDDER_COMPANYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for DPE_GET_PARTNER 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_et_partner | TYPE STANDARD TABLE OF DPE_BIDDER_COMPANY, " | |||
| lv_is_sel_partner | TYPE DPE_SEL_BIDDER. " |
|   CALL FUNCTION 'DPE_GET_PARTNER' "Get Bidder |
| EXPORTING | ||
| IS_SEL_PARTNER | = lv_is_sel_partner | |
| TABLES | ||
| ET_PARTNER | = lt_et_partner | |
| . " DPE_GET_PARTNER | ||
ABAP code using 7.40 inline data declarations to call FM DPE_GET_PARTNER
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