SAP BBP_CM_API_PD_CREATE_REF Function Module for Create with reference
BBP_CM_API_PD_CREATE_REF is a standard bbp cm api pd create ref SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create with reference 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 cm api pd create ref FM, simply by entering the name BBP_CM_API_PD_CREATE_REF into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_CM_COM_INF_PROCDOCS
Program Name: SAPLBBP_CM_COM_INF_PROCDOCS
Main Program: SAPLBBP_CM_COM_INF_PROCDOCS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_CM_API_PD_CREATE_REF 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_CM_API_PD_CREATE_REF'"Create with reference.
EXPORTING
IV_OBJECT_GUID = "GUID in character format
IV_FROM_TYPE = "Business Transaction Category
IV_TO_TYPE = "Business Transaction Category
IV_TO_PROCESS_TYPE = "Business Process Types
IV_INIT_GUID = "GUID in character format
* IV_COMMIT = "Checkbox
* IV_COPY = "Checkbox
IV_CALLER = "Business Process Types
IMPORTING
EV_PDREF_URL = "Return URL
ES_INIT_PROCDOC = "RFx/Ctr Document Information for Initiative
TABLES
ET_MESSAGES = "Return Parameter
IMPORTING Parameters details for BBP_CM_API_PD_CREATE_REF
IV_OBJECT_GUID - GUID in character format
Data type: BBP_CM_GUID_DOptional: No
Call by Reference: No ( called with pass by value option)
IV_FROM_TYPE - Business Transaction Category
Data type: BBP_CM_OBJECT_CATEGORYOptional: No
Call by Reference: No ( called with pass by value option)
IV_TO_TYPE - Business Transaction Category
Data type: BBP_CM_OBJECT_CATEGORYOptional: No
Call by Reference: No ( called with pass by value option)
IV_TO_PROCESS_TYPE - Business Process Types
Data type: BBP_CM_PROCESS_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
IV_INIT_GUID - GUID in character format
Data type: BBP_CM_GUID_DOptional: No
Call by Reference: No ( called with pass by value option)
IV_COMMIT - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_COPY - Checkbox
Data type: XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CALLER - Business Process Types
Data type: BBP_CM_PROCESS_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_CM_API_PD_CREATE_REF
EV_PDREF_URL - Return URL
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
ES_INIT_PROCDOC - RFx/Ctr Document Information for Initiative
Data type: BBPS_CM_INIT_PROCDOCS_DOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_CM_API_PD_CREATE_REF
ET_MESSAGES - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_CM_API_PD_CREATE_REF 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: | ||||
| lt_et_messages | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_ev_pdref_url | TYPE STRING, " | |||
| lv_iv_object_guid | TYPE BBP_CM_GUID_D, " | |||
| lv_iv_from_type | TYPE BBP_CM_OBJECT_CATEGORY, " | |||
| lv_es_init_procdoc | TYPE BBPS_CM_INIT_PROCDOCS_D, " | |||
| lv_iv_to_type | TYPE BBP_CM_OBJECT_CATEGORY, " | |||
| lv_iv_to_process_type | TYPE BBP_CM_PROCESS_TYPE, " | |||
| lv_iv_init_guid | TYPE BBP_CM_GUID_D, " | |||
| lv_iv_commit | TYPE XFELD, " | |||
| lv_iv_copy | TYPE XFELD, " | |||
| lv_iv_caller | TYPE BBP_CM_PROCESS_TYPE. " |
|   CALL FUNCTION 'BBP_CM_API_PD_CREATE_REF' "Create with reference |
| EXPORTING | ||
| IV_OBJECT_GUID | = lv_iv_object_guid | |
| IV_FROM_TYPE | = lv_iv_from_type | |
| IV_TO_TYPE | = lv_iv_to_type | |
| IV_TO_PROCESS_TYPE | = lv_iv_to_process_type | |
| IV_INIT_GUID | = lv_iv_init_guid | |
| IV_COMMIT | = lv_iv_commit | |
| IV_COPY | = lv_iv_copy | |
| IV_CALLER | = lv_iv_caller | |
| IMPORTING | ||
| EV_PDREF_URL | = lv_ev_pdref_url | |
| ES_INIT_PROCDOC | = lv_es_init_procdoc | |
| TABLES | ||
| ET_MESSAGES | = lt_et_messages | |
| . " BBP_CM_API_PD_CREATE_REF | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CM_API_PD_CREATE_REF
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