SAP BBP_CTR_UI_EXCEL_DOWNLOAD Function Module for Erstellen und versenden des Kontrakts als Excel
BBP_CTR_UI_EXCEL_DOWNLOAD is a standard bbp ctr ui excel download SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Erstellen und versenden des Kontrakts als Excel 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 ctr ui excel download FM, simply by entering the name BBP_CTR_UI_EXCEL_DOWNLOAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_CTR_UI
Program Name: SAPLBBP_CTR_UI
Main Program: SAPLBBP_CTR_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_CTR_UI_EXCEL_DOWNLOAD 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_CTR_UI_EXCEL_DOWNLOAD'"Erstellen und versenden des Kontrakts als Excel.
EXPORTING
IV_HEADER_GUID = "Globally Unique Identifier
* IS_EXTERNAL_CALL = "Externer Aufruf des Kontraktes aus PO, WF, etc.
* IV_GIVE_ATTACHMENT = ' ' "
* IS_HEADER = "Purchase Contract Header Structure
IMPORTING
ET_EXCELTAB = "Inhalt Exceltabelle Zellen werden durch Tab (chr9) getr
EV_XL_CONTENT = "
ET_MESSAGES = "Error Message for Procurement Document Methods
CHANGING
* CV_DISP_VARIANT = "Anzeigevariante
* CT_FILE_OPTIONS = "Tabelle für Datei-Optionen
IMPORTING Parameters details for BBP_CTR_UI_EXCEL_DOWNLOAD
IV_HEADER_GUID - Globally Unique Identifier
Data type: BBP_GUIDOptional: No
Call by Reference: Yes
IS_EXTERNAL_CALL - Externer Aufruf des Kontraktes aus PO, WF, etc.
Data type: BBPS_CTR_EXTERNAL_CALLOptional: Yes
Call by Reference: Yes
IV_GIVE_ATTACHMENT -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: Yes
IS_HEADER - Purchase Contract Header Structure
Data type: BBPS_CTR_UI_HEADEROptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_CTR_UI_EXCEL_DOWNLOAD
ET_EXCELTAB - Inhalt Exceltabelle Zellen werden durch Tab (chr9) getr
Data type: BBPT_QUOT_EXCELTABOptional: No
Call by Reference: Yes
EV_XL_CONTENT -
Data type: XSTRINGOptional: No
Call by Reference: Yes
ET_MESSAGES - Error Message for Procurement Document Methods
Data type: BBP_PDT_MESSAGESOptional: No
Call by Reference: Yes
CHANGING Parameters details for BBP_CTR_UI_EXCEL_DOWNLOAD
CV_DISP_VARIANT - Anzeigevariante
Data type: BBP_DISP_VARIANTOptional: Yes
Call by Reference: Yes
CT_FILE_OPTIONS - Tabelle für Datei-Optionen
Data type: BBPT_FILE_OPTIONSOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_CTR_UI_EXCEL_DOWNLOAD 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_et_exceltab | TYPE BBPT_QUOT_EXCELTAB, " | |||
| lv_iv_header_guid | TYPE BBP_GUID, " | |||
| lv_cv_disp_variant | TYPE BBP_DISP_VARIANT, " | |||
| lv_ev_xl_content | TYPE XSTRING, " | |||
| lv_ct_file_options | TYPE BBPT_FILE_OPTIONS, " | |||
| lv_is_external_call | TYPE BBPS_CTR_EXTERNAL_CALL, " | |||
| lv_et_messages | TYPE BBP_PDT_MESSAGES, " | |||
| lv_iv_give_attachment | TYPE C, " SPACE | |||
| lv_is_header | TYPE BBPS_CTR_UI_HEADER. " |
|   CALL FUNCTION 'BBP_CTR_UI_EXCEL_DOWNLOAD' "Erstellen und versenden des Kontrakts als Excel |
| EXPORTING | ||
| IV_HEADER_GUID | = lv_iv_header_guid | |
| IS_EXTERNAL_CALL | = lv_is_external_call | |
| IV_GIVE_ATTACHMENT | = lv_iv_give_attachment | |
| IS_HEADER | = lv_is_header | |
| IMPORTING | ||
| ET_EXCELTAB | = lv_et_exceltab | |
| EV_XL_CONTENT | = lv_ev_xl_content | |
| ET_MESSAGES | = lv_et_messages | |
| CHANGING | ||
| CV_DISP_VARIANT | = lv_cv_disp_variant | |
| CT_FILE_OPTIONS | = lv_ct_file_options | |
| . " BBP_CTR_UI_EXCEL_DOWNLOAD | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CTR_UI_EXCEL_DOWNLOAD
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.| DATA(ld_iv_give_attachment) | = ' '. | |||
Search for further information about these or an SAP related objects