SAP BITMAP_CREATE Function Module for









BITMAP_CREATE is a standard bitmap create 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 bitmap create FM, simply by entering the name BITMAP_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function BITMAP_CREATE 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 'BITMAP_CREATE'"
  EXPORTING
   OWNER_REPID =  "
*  SHELLSTYLE =  "
*  PARENTID =  "
*  REGISTER_EVENT_CLICK =  "
   DYNNR =  "
   LEFT =  "
   TOP =  "
   HEIGHT =  "
   WIDTH =  "
*  METRIC = CNTL_METRIC_DYNPRO "
*  NO_FLUSH =  "
*  LINK_REPID =  "

CHANGING
   HANDLE =  "

EXCEPTIONS
   CREATE_ERROR = 1
.



IMPORTING Parameters details for BITMAP_CREATE

OWNER_REPID -

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

SHELLSTYLE -

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

PARENTID -

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

REGISTER_EVENT_CLICK -

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

DYNNR -

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

LEFT -

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

TOP -

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

HEIGHT -

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

WIDTH -

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

METRIC -

Data type: CNTL_METRIC
Default: CNTL_METRIC_DYNPRO
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_FLUSH -

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

LINK_REPID -

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

CHANGING Parameters details for BITMAP_CREATE

HANDLE -

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

EXCEPTIONS details

CREATE_ERROR -

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

Copy and paste ABAP code example for BITMAP_CREATE 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_handle  TYPE CNTL_HANDLE, "   
lv_owner_repid  TYPE SY-REPID, "   
lv_create_error  TYPE SY, "   
lv_shellstyle  TYPE I, "   
lv_parentid  TYPE I, "   
lv_register_event_click  TYPE C, "   
lv_dynnr  TYPE SY-DYNNR, "   
lv_left  TYPE I, "   
lv_top  TYPE I, "   
lv_height  TYPE I, "   
lv_width  TYPE I, "   
lv_metric  TYPE CNTL_METRIC, "   CNTL_METRIC_DYNPRO
lv_no_flush  TYPE C, "   
lv_link_repid  TYPE SY-REPID. "   

  CALL FUNCTION 'BITMAP_CREATE'  "
    EXPORTING
         OWNER_REPID = lv_owner_repid
         SHELLSTYLE = lv_shellstyle
         PARENTID = lv_parentid
         REGISTER_EVENT_CLICK = lv_register_event_click
         DYNNR = lv_dynnr
         LEFT = lv_left
         TOP = lv_top
         HEIGHT = lv_height
         WIDTH = lv_width
         METRIC = lv_metric
         NO_FLUSH = lv_no_flush
         LINK_REPID = lv_link_repid
    CHANGING
         HANDLE = lv_handle
    EXCEPTIONS
        CREATE_ERROR = 1
. " BITMAP_CREATE




ABAP code using 7.40 inline data declarations to call FM BITMAP_CREATE

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 REPID FROM SY INTO @DATA(ld_owner_repid).
 
 
 
 
 
"SELECT single DYNNR FROM SY INTO @DATA(ld_dynnr).
 
 
 
 
 
DATA(ld_metric) = CNTL_METRIC_DYNPRO.
 
 
"SELECT single REPID FROM SY INTO @DATA(ld_link_repid).
 


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!