SAP MECH_DISPLAY_BW_OBJEKT Function Module for
MECH_DISPLAY_BW_OBJEKT is a standard mech display bw objekt 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 mech display bw objekt FM, simply by entering the name MECH_DISPLAY_BW_OBJEKT into the relevant SAP transaction such as SE37 or SE38.
Function Group: MECH
Program Name: SAPLMECH
Main Program: SAPLMECH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MECH_DISPLAY_BW_OBJEKT 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 'MECH_DISPLAY_BW_OBJEKT'".
EXPORTING
I_OBJNM = "
I_OBJTP = "
I_FLAG = "
EXCEPTIONS
WRONG_OBJEKT_TYPE = 1
IMPORTING Parameters details for MECH_DISPLAY_BW_OBJEKT
I_OBJNM -
Data type: ROAPPL-APPLNMOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJTP -
Data type: RODIOBJ-IOBJTPOptional: No
Call by Reference: No ( called with pass by value option)
I_FLAG -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_OBJEKT_TYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MECH_DISPLAY_BW_OBJEKT 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_i_objnm | TYPE ROAPPL-APPLNM, " | |||
| lv_wrong_objekt_type | TYPE ROAPPL, " | |||
| lv_i_objtp | TYPE RODIOBJ-IOBJTP, " | |||
| lv_i_flag | TYPE C. " |
|   CALL FUNCTION 'MECH_DISPLAY_BW_OBJEKT' " |
| EXPORTING | ||
| I_OBJNM | = lv_i_objnm | |
| I_OBJTP | = lv_i_objtp | |
| I_FLAG | = lv_i_flag | |
| EXCEPTIONS | ||
| WRONG_OBJEKT_TYPE = 1 | ||
| . " MECH_DISPLAY_BW_OBJEKT | ||
ABAP code using 7.40 inline data declarations to call FM MECH_DISPLAY_BW_OBJEKT
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 APPLNM FROM ROAPPL INTO @DATA(ld_i_objnm). | ||||
| "SELECT single IOBJTP FROM RODIOBJ INTO @DATA(ld_i_objtp). | ||||
Search for further information about these or an SAP related objects