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

Function BBP_HDRPROC_GET_CHANGE_VERSION 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_HDRPROC_GET_CHANGE_VERSION'".
EXPORTING
IV_HEADER_GUID = "
IMPORTING
EV_CHANGE_VERSION_GUID = "
IMPORTING Parameters details for BBP_HDRPROC_GET_CHANGE_VERSION
IV_HEADER_GUID -
Data type: BBP_GUIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BBP_HDRPROC_GET_CHANGE_VERSION
EV_CHANGE_VERSION_GUID -
Data type: BBP_GUIDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_HDRPROC_GET_CHANGE_VERSION 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 BBP_GUID, " | |||
| lv_ev_change_version_guid | TYPE BBP_GUID. " |
|   CALL FUNCTION 'BBP_HDRPROC_GET_CHANGE_VERSION' " |
| EXPORTING | ||
| IV_HEADER_GUID | = lv_iv_header_guid | |
| IMPORTING | ||
| EV_CHANGE_VERSION_GUID | = lv_ev_change_version_guid | |
| . " BBP_HDRPROC_GET_CHANGE_VERSION | ||
ABAP code using 7.40 inline data declarations to call FM BBP_HDRPROC_GET_CHANGE_VERSION
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