SAP BBP_PDCND_CREATE_VERSION Function Module for Anlegen bzw. Referezenzieren eines Partnersets für Versionen
BBP_PDCND_CREATE_VERSION is a standard bbp pdcnd create version SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Anlegen bzw. Referezenzieren eines Partnersets für Versionen 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 pdcnd create version FM, simply by entering the name BBP_PDCND_CREATE_VERSION into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PDCND
Program Name: SAPLBBP_PDCND
Main Program: SAPLBBP_PDCND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_PDCND_CREATE_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_PDCND_CREATE_VERSION'"Anlegen bzw. Referezenzieren eines Partnersets für Versionen.
EXPORTING
IV_NEW_GUID = "GUID eines CRM-Order-Objekts
IV_HGUID_VERSION = "GUID eines CRM-Order-Objekts
IV_PGUID_ACTIVE_VERSION = "GUID eines CRM-Order-Objekts
IV_HGUID_ACTIVE_VERSION = "GUID eines CRM-Order-Objekts
* IV_PGUID_OLD_VERSION = "GUID eines CRM-Order-Objekts
IV_NEW_KIND = "Objektart
IV_OBJECT_TYPE = "Geschäftsvorgangstyp
IT_CONDITIONS = "Tabellentyp zu BBP_PDS_CND_DIFF
IT_HIST_CONDITIONS = "
IMPORTING Parameters details for BBP_PDCND_CREATE_VERSION
IV_NEW_GUID - GUID eines CRM-Order-Objekts
Data type: CRMD_ORDERADM_H-GUIDOptional: No
Call by Reference: Yes
IV_HGUID_VERSION - GUID eines CRM-Order-Objekts
Data type: CRMT_OBJECT_GUIDOptional: No
Call by Reference: Yes
IV_PGUID_ACTIVE_VERSION - GUID eines CRM-Order-Objekts
Data type: CRMD_ORDERADM_H-GUIDOptional: No
Call by Reference: Yes
IV_HGUID_ACTIVE_VERSION - GUID eines CRM-Order-Objekts
Data type: CRMT_OBJECT_GUIDOptional: No
Call by Reference: Yes
IV_PGUID_OLD_VERSION - GUID eines CRM-Order-Objekts
Data type: CRMD_ORDERADM_H-GUIDOptional: Yes
Call by Reference: Yes
IV_NEW_KIND - Objektart
Data type: CRMT_OBJECT_KINDOptional: No
Call by Reference: Yes
IV_OBJECT_TYPE - Geschäftsvorgangstyp
Data type: CRMD_ORDERADM_H-OBJECT_TYPEOptional: No
Call by Reference: Yes
IT_CONDITIONS - Tabellentyp zu BBP_PDS_CND_DIFF
Data type: BBPT_PD_CND_DIFFOptional: No
Call by Reference: Yes
IT_HIST_CONDITIONS -
Data type: BBPT_PD_CND_DIFFOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_PDCND_CREATE_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_new_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lv_iv_hguid_version | TYPE CRMT_OBJECT_GUID, " | |||
| lv_iv_pguid_active_version | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lv_iv_hguid_active_version | TYPE CRMT_OBJECT_GUID, " | |||
| lv_iv_pguid_old_version | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lv_iv_new_kind | TYPE CRMT_OBJECT_KIND, " | |||
| lv_iv_object_type | TYPE CRMD_ORDERADM_H-OBJECT_TYPE, " | |||
| lv_it_conditions | TYPE BBPT_PD_CND_DIFF, " | |||
| lv_it_hist_conditions | TYPE BBPT_PD_CND_DIFF. " |
|   CALL FUNCTION 'BBP_PDCND_CREATE_VERSION' "Anlegen bzw. Referezenzieren eines Partnersets für Versionen |
| EXPORTING | ||
| IV_NEW_GUID | = lv_iv_new_guid | |
| IV_HGUID_VERSION | = lv_iv_hguid_version | |
| IV_PGUID_ACTIVE_VERSION | = lv_iv_pguid_active_version | |
| IV_HGUID_ACTIVE_VERSION | = lv_iv_hguid_active_version | |
| IV_PGUID_OLD_VERSION | = lv_iv_pguid_old_version | |
| IV_NEW_KIND | = lv_iv_new_kind | |
| IV_OBJECT_TYPE | = lv_iv_object_type | |
| IT_CONDITIONS | = lv_it_conditions | |
| IT_HIST_CONDITIONS | = lv_it_hist_conditions | |
| . " BBP_PDCND_CREATE_VERSION | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PDCND_CREATE_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.| "SELECT single GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_new_guid). | ||||
| "SELECT single GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_pguid_active_version). | ||||
| "SELECT single GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_pguid_old_version). | ||||
| "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