SAP BBP_PROCDOC_GETCOND_RFC Function Module for Lesen Procurement Document
BBP_PROCDOC_GETCOND_RFC is a standard bbp procdoc getcond rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Lesen Procurement Document 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 bbp procdoc getcond rfc FM, simply by entering the name BBP_PROCDOC_GETCOND_RFC into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PD_RFC
Program Name: SAPLBBP_PD_RFC
Main Program: SAPLBBP_PD_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BBP_PROCDOC_GETCOND_RFC 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_PROCDOC_GETCOND_RFC'"Lesen Procurement Document.
EXPORTING
IV_GUID = "
CHANGING
ET_CONDITIONS = "Table Type for BBP_PDS_CND
IMPORTING Parameters details for BBP_PROCDOC_GETCOND_RFC
IV_GUID -
Data type: CRMD_ORDERADM_H-GUIDOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for BBP_PROCDOC_GETCOND_RFC
ET_CONDITIONS - Table Type for BBP_PDS_CND
Data type: BBPT_PD_CNDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_PROCDOC_GETCOND_RFC 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_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lv_et_conditions | TYPE BBPT_PD_CND. " |
|   CALL FUNCTION 'BBP_PROCDOC_GETCOND_RFC' "Lesen Procurement Document |
| EXPORTING | ||
| IV_GUID | = lv_iv_guid | |
| CHANGING | ||
| ET_CONDITIONS | = lv_et_conditions | |
| . " BBP_PROCDOC_GETCOND_RFC | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PROCDOC_GETCOND_RFC
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_guid). | ||||
Search for further information about these or an SAP related objects