SAP BBP_REC_EXECUTE_UPLOAD Function Module for









BBP_REC_EXECUTE_UPLOAD is a standard bbp rec execute upload 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 rec execute upload FM, simply by entering the name BBP_REC_EXECUTE_UPLOAD into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_REC_UP_AND_DOWNLOAD
Program Name: SAPLBBP_REC_UP_AND_DOWNLOAD
Main Program: SAPLBBP_REC_UP_AND_DOWNLOAD
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BBP_REC_EXECUTE_UPLOAD 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_REC_EXECUTE_UPLOAD'"
EXPORTING
* USERNAME = ' ' "
* UPLOAD_DESCRIPTION = 'X' "
* UPLOAD_ITEMS = 'X' "
* SHOW_MESSAGE = 'X' "
* SHOW_WARNING_POPUP = 'X' "
* NO_PROGRESS_INDICATOR = ' ' "

IMPORTING
NUMBER_OF_CHANNELS = "
SINGLE_SELECTED_CHANNEL = "

TABLES
TRANSFER_TAB = "

EXCEPTIONS
NOT_AUTHORIZED = 1 CHANNEL_ENQUEUED = 2 ILLEGAL_RELEASE = 3 NO_VALID_DATA = 4 ACTION_CANCELLED = 5
.



IMPORTING Parameters details for BBP_REC_EXECUTE_UPLOAD

USERNAME -

Data type: SY-UNAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

UPLOAD_DESCRIPTION -

Data type: BBPSAPNEW-CUSTOMIZED
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

UPLOAD_ITEMS -

Data type: BBPSAPNEW-CUSTOMIZED
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SHOW_MESSAGE -

Data type: BBPSAPNEW-CUSTOMIZED
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SHOW_WARNING_POPUP -

Data type: BBPSAPNEW-CUSTOMIZED
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_PROGRESS_INDICATOR -

Data type: BBPSAPNEW-CUSTOMIZED
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BBP_REC_EXECUTE_UPLOAD

NUMBER_OF_CHANNELS -

Data type: SY-TABIX
Optional: No
Call by Reference: No ( called with pass by value option)

SINGLE_SELECTED_CHANNEL -

Data type: REC_DEFINE-REC_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BBP_REC_EXECUTE_UPLOAD

TRANSFER_TAB -

Data type: BBPTAB3
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_AUTHORIZED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CHANNEL_ENQUEUED -

Data type:
Optional: No
Call by Reference: Yes

ILLEGAL_RELEASE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_VALID_DATA -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ACTION_CANCELLED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BBP_REC_EXECUTE_UPLOAD 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_username  TYPE SY-UNAME, "   SPACE
lt_transfer_tab  TYPE STANDARD TABLE OF BBPTAB3, "   
lv_not_authorized  TYPE BBPTAB3, "   
lv_number_of_channels  TYPE SY-TABIX, "   
lv_channel_enqueued  TYPE SY, "   
lv_upload_description  TYPE BBPSAPNEW-CUSTOMIZED, "   'X'
lv_single_selected_channel  TYPE REC_DEFINE-REC_NAME, "   
lv_upload_items  TYPE BBPSAPNEW-CUSTOMIZED, "   'X'
lv_illegal_release  TYPE BBPSAPNEW, "   
lv_show_message  TYPE BBPSAPNEW-CUSTOMIZED, "   'X'
lv_no_valid_data  TYPE BBPSAPNEW, "   
lv_action_cancelled  TYPE BBPSAPNEW, "   
lv_show_warning_popup  TYPE BBPSAPNEW-CUSTOMIZED, "   'X'
lv_no_progress_indicator  TYPE BBPSAPNEW-CUSTOMIZED. "   SPACE

  CALL FUNCTION 'BBP_REC_EXECUTE_UPLOAD'  "
    EXPORTING
         USERNAME = lv_username
         UPLOAD_DESCRIPTION = lv_upload_description
         UPLOAD_ITEMS = lv_upload_items
         SHOW_MESSAGE = lv_show_message
         SHOW_WARNING_POPUP = lv_show_warning_popup
         NO_PROGRESS_INDICATOR = lv_no_progress_indicator
    IMPORTING
         NUMBER_OF_CHANNELS = lv_number_of_channels
         SINGLE_SELECTED_CHANNEL = lv_single_selected_channel
    TABLES
         TRANSFER_TAB = lt_transfer_tab
    EXCEPTIONS
        NOT_AUTHORIZED = 1
        CHANNEL_ENQUEUED = 2
        ILLEGAL_RELEASE = 3
        NO_VALID_DATA = 4
        ACTION_CANCELLED = 5
. " BBP_REC_EXECUTE_UPLOAD




ABAP code using 7.40 inline data declarations to call FM BBP_REC_EXECUTE_UPLOAD

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_username).
DATA(ld_username) = ' '.
 
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_number_of_channels).
 
 
"SELECT single CUSTOMIZED FROM BBPSAPNEW INTO @DATA(ld_upload_description).
DATA(ld_upload_description) = 'X'.
 
"SELECT single REC_NAME FROM REC_DEFINE INTO @DATA(ld_single_selected_channel).
 
"SELECT single CUSTOMIZED FROM BBPSAPNEW INTO @DATA(ld_upload_items).
DATA(ld_upload_items) = 'X'.
 
 
"SELECT single CUSTOMIZED FROM BBPSAPNEW INTO @DATA(ld_show_message).
DATA(ld_show_message) = 'X'.
 
 
 
"SELECT single CUSTOMIZED FROM BBPSAPNEW INTO @DATA(ld_show_warning_popup).
DATA(ld_show_warning_popup) = 'X'.
 
"SELECT single CUSTOMIZED FROM BBPSAPNEW INTO @DATA(ld_no_progress_indicator).
DATA(ld_no_progress_indicator) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!