SAP BDT_CHECK_MESSAGES_DISPLAY Function Module for









BDT_CHECK_MESSAGES_DISPLAY is a standard bdt check messages display 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 bdt check messages display FM, simply by entering the name BDT_CHECK_MESSAGES_DISPLAY into the relevant SAP transaction such as SE37 or SE38.

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



Function BDT_CHECK_MESSAGES_DISPLAY 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 'BDT_CHECK_MESSAGES_DISPLAY'"
EXPORTING
* IV_POPUP = "
IV_OBJAP = "BDT: Application Object
.



IMPORTING Parameters details for BDT_CHECK_MESSAGES_DISPLAY

IV_POPUP -

Data type: C
Optional: Yes
Call by Reference: Yes

IV_OBJAP - BDT: Application Object

Data type: TBZ0A-OBJAP
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BDT_CHECK_MESSAGES_DISPLAY 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_iv_popup  TYPE C, "   
lv_iv_objap  TYPE TBZ0A-OBJAP. "   

  CALL FUNCTION 'BDT_CHECK_MESSAGES_DISPLAY'  "
    EXPORTING
         IV_POPUP = lv_iv_popup
         IV_OBJAP = lv_iv_objap
. " BDT_CHECK_MESSAGES_DISPLAY




ABAP code using 7.40 inline data declarations to call FM BDT_CHECK_MESSAGES_DISPLAY

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 OBJAP FROM TBZ0A INTO @DATA(ld_iv_objap).
 


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!