Monthly Archive for March, 2009

SAP: Clickable Icon Button in ALV fields

Published
by
rs
on March 26, 2009
in ABAP, ALV, SAP and Technical
. 3 Comments


Adding a button inside an ALV fields is a very simple task to do which needs only a few line of codes. what I always do is I create a field on ALV and populate that field with an Icon of my choice and declare it as a Hotspot so it will react on a single click and it works perfectly just like a button.

First Thing to do is to specify a field in our internal table that we will use to hold the Icon(refer to code #1).

CODE #1
 
TYPES: BEGIN OF t_alvbutton,
          icon TYPE string,      "icon field
          kunnr LIKE kna1-kunnr,
	  name1 LIKE kna1-name1,
	END OF t_alvbutton.
 
DATA: it_alvbutton    TYPE STANDARD TABLE OF t_alvbutton,
      wa_alvbutton	TYPE t_alvbutton.

Proceed to the data retrieval and populate the it_alvbutton. I assume you know how to retrieve data from database so there’s no need to show you the select statement for our example. After that, loop on every records of it_alvbutton to specify the Icon that we want to display(refer to code #2).

CODE #2
 
LOOP AT it_alvbutton INTO wa_alvbutton.
	wa_alvbutton-icon =  '@0X@'.
	MODIFY it_alvbutton FROM wa_alvbutton.
ENDLOOP.

@0X@ is the code for print icon. For the complete list of icons, check it out here.

Now the important part is to define a field in ALV that will hold the icon. To show you how simple it is to do that, please refer to code #3.

CODE #3
 
DATA:	ls_fieldcat TYPE slis_fieldcat_alv,
	lt_fieldcat TYPE slis_t_fieldcat_alv.
 
DEFINE m_fieldcat.
	add 1 to ls_fieldcat-col_pos.
	ls_fieldcat-fieldname = &1.
	ls_fieldcat-seltext_l = &2.
	ls_fieldcat-outputlen = &3.
	ls_fieldcat-hotspot = &4.   "X to declare the field as a hotspot
	ls_fieldcat-icon = &5.      "X to declare the field as an icon
	append ls_fieldcat to lt_fieldcat.
END-OF-DEFINITION.
 
m_fieldcat 'ICON' 'Print' '20' 'X' 'X'.  "this specific field is a hotspot and an icon
m_fieldcat 'KUNNR' 'Customer No.' '10'.
m_fieldcat 'NAME1' 'Customer Name' '35'.
m_fieldcat . . .
m_fieldcat . . .
 
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
	. . .
	. . .

The figure below shows an example of print icon as a button.

Icon Button in ALV

Now refer to code #4 to handle the command when a user clicks on the icon button.

CODE #4
 
FORM f_user_command USING ucomm LIKE sy-ucomm
		  v_selfld TYPE slis_selfield.
 
IF ucomm = '&IC1' AND v_selfld-fieldname = 'ICON'.
	"code goes in here when user clicks on our print button
ENDIF.

Creative Commons License

SAP: List of Icons

Published
by
rs
on March 24, 2009
in ABAP, General, SAP and Technical
. 0 Comments

I could show you here the complete list of icons with its corresponding code but I rather show you a couple line of codes that will provide you the list of icons. So please refer to the code #1.

CODE #1

TABLES: icon.
DATA: icontext(4) TYPE c.
SELECT * FROM icon.
  WRITE: / icon-id+1(2).
  CONCATENATE '@' icon-id+1(2) '@' INTO icontext.
  WRITE: 10 icontext AS ICON, icon-name.
ENDSELECT.

Create a blank program on transaction SE38 and add the code above. Just activate it and execute. You now have your own list of icons for your reference whenever you need it.

SAP: Basic of Lock Objects

Published
by
rs
on March 23, 2009
in ABAP, BASIS, SAP and Technical
. 0 Comments

Data inconsistency occurs when two or more users are editing/changing the same record on the same table at exactly the same time. To avoid this, we use Lock Objects.

Lock Objects enables the user to request a lock on a specific record before accessing it. In this way, changing/editing of records is only possible one at a time, thus avoiding data inconsistency.

There are three different lock modes:

exclusive lock/Write Lock (Mode ‘E’)
allow you to prevent data from being changed while you are changing it yourself. An exclusive lock, as its name suggests, locks an application object for exclusive use by the program that sets it. No other program can then set either a shared lock or an exclusive lock for the same application object.

Shared Lock/Read Lock (Mode ‘S’)
allow you to prevent data from being changed while you are reading it. They prevent other programs from setting an exclusive lock (write lock) to change the object. It does not, however, prevent other programs from setting further read locks.

Enhanced write lock (Mode ‘X’)
works like a write lock but are not accumulated while a program is being executed. It protects from further accesses within the same transaction.

To create a Lock Object, got to transaction SE11, click on Lock Object radio button and enter any name that starts with EZ or EY. (Example EZSAMPLE_LOCK)

When you activate a lock object, the system generates an ENQUEUE_ and a DEQUEUE_ function module that you can use on your ABAP programs.

ENQUEUE_<lockobject name> - adds the requested object in a queue(lock)
DEQUEUE_<lockobject name> - remove the requested object from being queued(unlock).

The basic procedure on requesting a lock:
1. Enqueue and lock the object for editing.
2. Read/write the data from the database.
4. dequeue and release the object.

To implement Lock Objects in ABAP programs, please refer to this post.

SAP: How to use Lock Objects in ABAP

Published
by
rs
on March 23, 2009
in ABAP, BASIS, SAP and Technical
. 3 Comments

Let say we have a customized table ZCUST_INFO that holds a specific customer information with MANDT(client number) and KUNNR(customer number) as the key field.

So let’s create a Lock Object for our customized table:
1. Go to transaction SE11
2. Click on Lock Object radio button and type-in EZCUST_INFO on name field and click on create button.
3. On Tables Tab, type-in ZCUST_INFO on name field and choose Write Lock on Lock Mode.
4. Go to Lock Parameter Tab and on the first row, type-in mandt on lock parameter, zcust_info on
table, and mandt on field.
5. On second row, type-in custnum on lock parameter, zcust_info on table, and kunnr on field.
6. Click save and activate.

Now let say we also have a dialog program for managing this the content of this table. We have screen 100 for our selection screen with customer number as selection parameter, screen 200 for editing screen, and screen 300 for display screen.

On the PBO of screen 200, let’s add the code below.

  CALL FUNCTION ‘ENQUEUE_EZCUST_INFO’
    EXPORTING
    MODE_ZCUST_INFO = ‘X’
    MANDT = sy-mandt
    CUSTNUM = <customer number from screen 100>
  EXCEPTIONS
    FOREIGN_LOCK = 1
    SYSTEM_FAILURE = 2
    OTHERS = 3.
  IF sy-subrc = 1.
    MESSAGE ‘This record is currently locked by another user!’ type ‘I’.
leave to screen 300.
  ENDIF.

The code above will request for lock on the table zcust_info specifically on the record specified on
the mandt and custnum parameter. If the record is already locked by another user, the user will be
prompted and will be redirected to screen 300 which is the display screen.

Lastly, on the PAI of screen 200, add the code below to release and unlock the object queued on the PBO:

  CALL FUNCTION ‘DEQUEUE_EZCUST_INFO’
    EXPORTING
    MODE_ZCUST_INFO = ‘X’
    MANDT = sy-mandt
    CUSTNUM = <customer number from screen 100>
  EXCEPTIONS
    FOREIGN_LOCK = 1
    SYSTEM_FAILURE = 2
    OTHERS = 3.

SAP: Changing ALV Row Color

Published
by
rs
on March 19, 2009
in ABAP, ALV, SAP and Technical
. 0 Comments

Changing the color of an ALV row is very simple. First you have to add a field on your internal table that will holds the color attribute (Refer to the sample code below).

TYPES: BEGIN OF t_rowcolor,
column1 TYPE string,
column2 TYPE string,
column3 TYPE string,
rowcolor(4) TYPE c,
END OF t_rowcolor.

DATA:  it_rowcolor TYPE STANDARD TABLE OF t_rowcolor,
wa_rowcolor TYPE t_rowcolor.

Next step is to Set the layout field for color attributes. In our case, that field is “rowcolor” (Refer to the sample code below).

DATA: gd_layout TYPE slis_layout_alv.

gd_layout-info_fieldname = ‘ROWCOLOR’.

Lastly, you have to populate the rowcolor field with the color attributes of your choice. You can do this when you loop at your internal table into your work area table (Refer to the sample code below).

LOOP AT it_row INTO wa_row.
wa_row-rowcolor = ‘C100′
MODIFY it_row FROM wa_row.
ENDLOOP.

In the code above, ‘C100′ is the color attribute. For the complete list of different color attributes, please refer to the figure below.

ALV color attributes