SAP BBPU_RETURN_TAB_FILL_MESSAGE Function Module for









BBPU_RETURN_TAB_FILL_MESSAGE is a standard bbpu return tab fill message 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 bbpu return tab fill message FM, simply by entering the name BBPU_RETURN_TAB_FILL_MESSAGE into the relevant SAP transaction such as SE37 or SE38.

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



Function BBPU_RETURN_TAB_FILL_MESSAGE 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 'BBPU_RETURN_TAB_FILL_MESSAGE'"
EXPORTING
* DELETE_INVALID_MESSAGES = 'X' "

TABLES
RETURN = "
.



IMPORTING Parameters details for BBPU_RETURN_TAB_FILL_MESSAGE

DELETE_INVALID_MESSAGES -

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

TABLES Parameters details for BBPU_RETURN_TAB_FILL_MESSAGE

RETURN -

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

Copy and paste ABAP code example for BBPU_RETURN_TAB_FILL_MESSAGE 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_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_delete_invalid_messages  TYPE BBPSAPNEW-CUSTOMIZED. "   'X'

  CALL FUNCTION 'BBPU_RETURN_TAB_FILL_MESSAGE'  "
    EXPORTING
         DELETE_INVALID_MESSAGES = lv_delete_invalid_messages
    TABLES
         RETURN = lt_return
. " BBPU_RETURN_TAB_FILL_MESSAGE




ABAP code using 7.40 inline data declarations to call FM BBPU_RETURN_TAB_FILL_MESSAGE

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 CUSTOMIZED FROM BBPSAPNEW INTO @DATA(ld_delete_invalid_messages).
DATA(ld_delete_invalid_messages) = 'X'.
 


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!