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

Function BBP_CND_UI_BAPI_GETDETAIL 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_CND_UI_BAPI_GETDETAIL'".
EXPORTING
* IV_BBP_HEADER_GUID = "
* IV_BBP_OBJECT_ID_QUOT = "
* IV_NEW_OBJECT_ID = "
IV_LOGSYS = "
* IV_FILTER_LOCATION = "
* IV_SPLIT_INTERVALS = 'X' "
* IT_ITEMS = "
* IT_ITEMS_EXCLUDE = "
* IV_DISP_CURRENCY = "
TABLES
* ET_COND_CT = "
* ET_COND_HD = "
* ET_COND_IT = "
* ET_COND_QS = "
* ET_COND_VS = "
* ET_MESSAGES = "
IMPORTING Parameters details for BBP_CND_UI_BAPI_GETDETAIL
IV_BBP_HEADER_GUID -
Data type: CRMD_ORDERADM_H-GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_BBP_OBJECT_ID_QUOT -
Data type: CRMD_ORDERADM_H-OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NEW_OBJECT_ID -
Data type: CRMD_ORDERADM_H-OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_LOGSYS -
Data type: LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
IV_FILTER_LOCATION -
Data type: BU_PARTNEROptional: Yes
Call by Reference: Yes
IV_SPLIT_INTERVALS -
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IT_ITEMS -
Data type: BBPT_PDEXT_CTR_ITEM_DOptional: Yes
Call by Reference: Yes
IT_ITEMS_EXCLUDE -
Data type: BBPT_PDEXT_CTR_ITEM_DOptional: Yes
Call by Reference: Yes
IV_DISP_CURRENCY -
Data type: WAERSOptional: Yes
Call by Reference: Yes
TABLES Parameters details for BBP_CND_UI_BAPI_GETDETAIL
ET_COND_CT -
Data type: BBPBAPICONDCTOptional: Yes
Call by Reference: Yes
ET_COND_HD -
Data type: BBPBAPICONDHDOptional: Yes
Call by Reference: Yes
ET_COND_IT -
Data type: BBPBAPICONDITOptional: Yes
Call by Reference: Yes
ET_COND_QS -
Data type: BBPBAPICONDQSOptional: Yes
Call by Reference: Yes
ET_COND_VS -
Data type: BBPBAPICONDVSOptional: Yes
Call by Reference: Yes
ET_MESSAGES -
Data type: BBP_PDS_MESSAGESOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_CND_UI_BAPI_GETDETAIL 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_cond_ct | TYPE STANDARD TABLE OF BBPBAPICONDCT, " | |||
| lv_iv_bbp_header_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lt_et_cond_hd | TYPE STANDARD TABLE OF BBPBAPICONDHD, " | |||
| lv_iv_bbp_object_id_quot | TYPE CRMD_ORDERADM_H-OBJECT_ID, " | |||
| lt_et_cond_it | TYPE STANDARD TABLE OF BBPBAPICONDIT, " | |||
| lv_iv_new_object_id | TYPE CRMD_ORDERADM_H-OBJECT_ID, " | |||
| lv_iv_logsys | TYPE LOGSYS, " | |||
| lt_et_cond_qs | TYPE STANDARD TABLE OF BBPBAPICONDQS, " | |||
| lt_et_cond_vs | TYPE STANDARD TABLE OF BBPBAPICONDVS, " | |||
| lv_iv_filter_location | TYPE BU_PARTNER, " | |||
| lt_et_messages | TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, " | |||
| lv_iv_split_intervals | TYPE FLAG, " 'X' | |||
| lv_it_items | TYPE BBPT_PDEXT_CTR_ITEM_D, " | |||
| lv_it_items_exclude | TYPE BBPT_PDEXT_CTR_ITEM_D, " | |||
| lv_iv_disp_currency | TYPE WAERS. " |
|   CALL FUNCTION 'BBP_CND_UI_BAPI_GETDETAIL' " |
| EXPORTING | ||
| IV_BBP_HEADER_GUID | = lv_iv_bbp_header_guid | |
| IV_BBP_OBJECT_ID_QUOT | = lv_iv_bbp_object_id_quot | |
| IV_NEW_OBJECT_ID | = lv_iv_new_object_id | |
| IV_LOGSYS | = lv_iv_logsys | |
| IV_FILTER_LOCATION | = lv_iv_filter_location | |
| IV_SPLIT_INTERVALS | = lv_iv_split_intervals | |
| IT_ITEMS | = lv_it_items | |
| IT_ITEMS_EXCLUDE | = lv_it_items_exclude | |
| IV_DISP_CURRENCY | = lv_iv_disp_currency | |
| TABLES | ||
| ET_COND_CT | = lt_et_cond_ct | |
| ET_COND_HD | = lt_et_cond_hd | |
| ET_COND_IT | = lt_et_cond_it | |
| ET_COND_QS | = lt_et_cond_qs | |
| ET_COND_VS | = lt_et_cond_vs | |
| ET_MESSAGES | = lt_et_messages | |
| . " BBP_CND_UI_BAPI_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CND_UI_BAPI_GETDETAIL
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_bbp_header_guid). | ||||
| "SELECT single OBJECT_ID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_bbp_object_id_quot). | ||||
| "SELECT single OBJECT_ID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_new_object_id). | ||||
| DATA(ld_iv_split_intervals) | = 'X'. | |||
Search for further information about these or an SAP related objects