SAP BBP_PDCV_UPDATE Function Module for
BBP_PDCV_UPDATE is a standard bbp pdcv update 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 pdcv update FM, simply by entering the name BBP_PDCV_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PDCV
Program Name: SAPLBBP_PDCV
Main Program: SAPLBBP_PDCV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_PDCV_UPDATE 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_PDCV_UPDATE'".
EXPORTING
IV_HEADER_GUID = "
IV_OBJECT_TYPE = "
* IV_BAPIMODE = "
IV_WITH_CHANGE_VERSION = "
IS_ITM_ICOM = "
IMPORTING
EV_CV_HEADER_GUID = "
IMPORTING Parameters details for BBP_PDCV_UPDATE
IV_HEADER_GUID -
Data type: CRMD_ORDERADM_H-GUIDOptional: No
Call by Reference: Yes
IV_OBJECT_TYPE -
Data type: CRMD_ORDERADM_H-OBJECT_TYPEOptional: No
Call by Reference: Yes
IV_BAPIMODE -
Data type: XFELDOptional: Yes
Call by Reference: Yes
IV_WITH_CHANGE_VERSION -
Data type: XFELDOptional: No
Call by Reference: Yes
IS_ITM_ICOM -
Data type: BBP_PDS_ITM_ICOMOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BBP_PDCV_UPDATE
EV_CV_HEADER_GUID -
Data type: CRMD_ORDERADM_H-GUIDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_PDCV_UPDATE 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_header_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lv_ev_cv_header_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lv_iv_object_type | TYPE CRMD_ORDERADM_H-OBJECT_TYPE, " | |||
| lv_iv_bapimode | TYPE XFELD, " | |||
| lv_iv_with_change_version | TYPE XFELD, " | |||
| lv_is_itm_icom | TYPE BBP_PDS_ITM_ICOM. " |
|   CALL FUNCTION 'BBP_PDCV_UPDATE' " |
| EXPORTING | ||
| IV_HEADER_GUID | = lv_iv_header_guid | |
| IV_OBJECT_TYPE | = lv_iv_object_type | |
| IV_BAPIMODE | = lv_iv_bapimode | |
| IV_WITH_CHANGE_VERSION | = lv_iv_with_change_version | |
| IS_ITM_ICOM | = lv_is_itm_icom | |
| IMPORTING | ||
| EV_CV_HEADER_GUID | = lv_ev_cv_header_guid | |
| . " BBP_PDCV_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PDCV_UPDATE
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_header_guid). | ||||
| "SELECT single GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_ev_cv_header_guid). | ||||
| "SELECT single OBJECT_TYPE FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_object_type). | ||||
Search for further information about these or an SAP related objects