SAP BBP_PDLINK_GET Function Module for
BBP_PDLINK_GET is a standard bbp pdlink get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bbp pdlink get FM, simply by entering the name BBP_PDLINK_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PDLINK_OW
Program Name: SAPLBBP_PDLINK_OW
Main Program: SAPLBBP_PDLINK_OW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_PDLINK_GET 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 'BBP_PDLINK_GET'".
EXPORTING
IV_P_GUID = "
IV_KIND = "
IV_SET_NAME = "
IMPORTING
EV_SET_GUID = "
ET_LINK = "
IMPORTING Parameters details for BBP_PDLINK_GET
IV_P_GUID -
Data type: CRMD_ORDERADM_H-GUIDOptional: No
Call by Reference: Yes
IV_KIND -
Data type: CRMT_OBJECT_KINDOptional: No
Call by Reference: No ( called with pass by value option)
IV_SET_NAME -
Data type: CRMT_OBJECT_NAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BBP_PDLINK_GET
EV_SET_GUID -
Data type: CRMD_ORDERADM_H-GUIDOptional: No
Call by Reference: Yes
ET_LINK -
Data type: BBPT_LINK_COMOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_PDLINK_GET 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_p_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lv_ev_set_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lv_et_link | TYPE BBPT_LINK_COM, " | |||
| lv_iv_kind | TYPE CRMT_OBJECT_KIND, " | |||
| lv_iv_set_name | TYPE CRMT_OBJECT_NAME. " |
|   CALL FUNCTION 'BBP_PDLINK_GET' " |
| EXPORTING | ||
| IV_P_GUID | = lv_iv_p_guid | |
| IV_KIND | = lv_iv_kind | |
| IV_SET_NAME | = lv_iv_set_name | |
| IMPORTING | ||
| EV_SET_GUID | = lv_ev_set_guid | |
| ET_LINK | = lv_et_link | |
| . " BBP_PDLINK_GET | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PDLINK_GET
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 GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_p_guid). | ||||
| "SELECT single GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_ev_set_guid). | ||||
Search for further information about these or an SAP related objects