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

Function BBP_CFOLDER_UI_DATA_BUILD 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_CFOLDER_UI_DATA_BUILD'".
EXPORTING
IV_BBP_HEADER_GUID = "
* IV_USERNAME = SY-UNAME "
IMPORTING
EV_CFX_NAME = "
EV_REDIRECT_URL = "
EV_IS_TEMPLATE = "
EV_OPEN_DATE_REACHED = "
* EV_CLOSED_DATE_REACHED = "
EV_CFX_NAME_LONG = "
EV_CFX_WA_NAME = "
EV_CFX_WA_NAME_LONG = "
EV_RETURN_URL = "
EV_RETURN_URL_TEXT = "
EV_SZENARIO = "
EV_TCODE_WA_CREATE = "
EV_DOCTYPE_RELEVANCE = "
IMPORTING Parameters details for BBP_CFOLDER_UI_DATA_BUILD
IV_BBP_HEADER_GUID -
Data type: BBP_GUIDOptional: No
Call by Reference: Yes
IV_USERNAME -
Data type: SY-UNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_CFOLDER_UI_DATA_BUILD
EV_CFX_NAME -
Data type: BBP_TEXTOptional: No
Call by Reference: Yes
EV_REDIRECT_URL -
Data type: STRINGOptional: No
Call by Reference: Yes
EV_IS_TEMPLATE -
Data type: COptional: No
Call by Reference: Yes
EV_OPEN_DATE_REACHED -
Data type: COptional: No
Call by Reference: Yes
EV_CLOSED_DATE_REACHED -
Data type: COptional: Yes
Call by Reference: Yes
EV_CFX_NAME_LONG -
Data type: BBP_TEXTOptional: No
Call by Reference: Yes
EV_CFX_WA_NAME -
Data type: BBP_TEXTOptional: No
Call by Reference: Yes
EV_CFX_WA_NAME_LONG -
Data type: BBP_TEXTOptional: No
Call by Reference: Yes
EV_RETURN_URL -
Data type: STRINGOptional: No
Call by Reference: Yes
EV_RETURN_URL_TEXT -
Data type: BBP_TEXTOptional: No
Call by Reference: Yes
EV_SZENARIO -
Data type: STRINGOptional: No
Call by Reference: Yes
EV_TCODE_WA_CREATE -
Data type: SY-UCOMMOptional: No
Call by Reference: Yes
EV_DOCTYPE_RELEVANCE -
Data type: CHAR10Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_CFOLDER_UI_DATA_BUILD 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_ev_cfx_name | TYPE BBP_TEXT, " | |||
| lv_iv_bbp_header_guid | TYPE BBP_GUID, " | |||
| lv_ev_redirect_url | TYPE STRING, " | |||
| lv_ev_is_template | TYPE C, " | |||
| lv_ev_open_date_reached | TYPE C, " | |||
| lv_ev_closed_date_reached | TYPE C, " | |||
| lv_iv_username | TYPE SY-UNAME, " SY-UNAME | |||
| lv_ev_cfx_name_long | TYPE BBP_TEXT, " | |||
| lv_ev_cfx_wa_name | TYPE BBP_TEXT, " | |||
| lv_ev_cfx_wa_name_long | TYPE BBP_TEXT, " | |||
| lv_ev_return_url | TYPE STRING, " | |||
| lv_ev_return_url_text | TYPE BBP_TEXT, " | |||
| lv_ev_szenario | TYPE STRING, " | |||
| lv_ev_tcode_wa_create | TYPE SY-UCOMM, " | |||
| lv_ev_doctype_relevance | TYPE CHAR10. " |
|   CALL FUNCTION 'BBP_CFOLDER_UI_DATA_BUILD' " |
| EXPORTING | ||
| IV_BBP_HEADER_GUID | = lv_iv_bbp_header_guid | |
| IV_USERNAME | = lv_iv_username | |
| IMPORTING | ||
| EV_CFX_NAME | = lv_ev_cfx_name | |
| EV_REDIRECT_URL | = lv_ev_redirect_url | |
| EV_IS_TEMPLATE | = lv_ev_is_template | |
| EV_OPEN_DATE_REACHED | = lv_ev_open_date_reached | |
| EV_CLOSED_DATE_REACHED | = lv_ev_closed_date_reached | |
| EV_CFX_NAME_LONG | = lv_ev_cfx_name_long | |
| EV_CFX_WA_NAME | = lv_ev_cfx_wa_name | |
| EV_CFX_WA_NAME_LONG | = lv_ev_cfx_wa_name_long | |
| EV_RETURN_URL | = lv_ev_return_url | |
| EV_RETURN_URL_TEXT | = lv_ev_return_url_text | |
| EV_SZENARIO | = lv_ev_szenario | |
| EV_TCODE_WA_CREATE | = lv_ev_tcode_wa_create | |
| EV_DOCTYPE_RELEVANCE | = lv_ev_doctype_relevance | |
| . " BBP_CFOLDER_UI_DATA_BUILD | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CFOLDER_UI_DATA_BUILD
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 UNAME FROM SY INTO @DATA(ld_iv_username). | ||||
| DATA(ld_iv_username) | = SY-UNAME. | |||
| "SELECT single UCOMM FROM SY INTO @DATA(ld_ev_tcode_wa_create). | ||||
Search for further information about these or an SAP related objects