JEST table contains object status that is either system status or a user status. Field STAT corresponds to the Object Status. Field INACT identifies whether the status is currently active or inactive and field CHGNR is the change number that identifies the change documents for an object and is incremented serially.
TJ02 table contains the list of system status and description. All statuses in this table are internal. This means they are consistent across objects and clients. A single object can have multiple active system statuses and user statuses & inactive ones.
TJ30 table contains the list of user status and TJ30T contains their description.
You could use function module STATUS_READ read active object status and STATUS_OBJECT_READ to retrieve the status profile of an object number.
Instead of going to transaction code SM30 to maintain your table, why not create your own t-code for that specific table maintenance screen. To do this, here’s the step by step procedure I stumbled upon on some SAP technical forums:
1. Go to t-code SE93.
2. Type in your customized t-code on the transaction code field.
3. Click on Create button.
4. Give it a short description and tick on the “Transaction with Parameters” radio button.
2. On the next screen, type “SM30″ in the transaction field.
3. Check mark the skip initial screen.
4. type “0″ on screen field
5. Under the Classification area, check mark on Inherit GUI attributes
6. Tick all GUI support checkboxes.
7. On the default value section, give this:
Name of Screen Field: VIEWNAME
Value: Your table name
Name of Screen Field: UPDATE
Value: X X
It is very easy to apply a progress indicator on your abap programs. This will enable the
user to determine how much long will he wait until the program finish its processing.
This is done by simply calling the function module SAPGUI_PROGRESS_INDICATOR.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
VALUE(PERCENTAGE) DEFAULT 0
VALUE(TEXT) DEFAULT SPACEPERCENTAGE is where you indicate the percentage of processing time and the TEXT is
where you indicate the text to be displayed on the status bar. This parameters can be
set with static values. But if you want, you could also add a few line of codes to make your
progress indicator dynamic and based on the actual number of records being process. This tip
is applicable when you are querying and processing a record from a database.
First you have to declare three decimal variables, see example below.
DATA: v_percent TYPE p DECIMALS 4, "holds the actual percentage of process time
v_increment TYPE p DECIMALS 4, "holds the increment value per single loop
v_mod TYPE p DECIMALS 4. "used as indicatorNow refer to the lines below for the rest of the codes.
****Your select statement goes here******
* this will determine the increment value based on the result of the select statement
v_increment = 100 / sy-dbcnt.
LOOP AT it INTO wa.
*calculate the progress percentage on every single loop
v_percent = v_percent + v_increment.
*this codes indicates that I want to update my progress indicator every 5% increase
*in percentage. you can change this anytime you want.
v_mod = v_percent MOD 5.
IF v_mod < 1.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
percentage = v_percent
text = 'Processing, please wait.'.
ENDIF.
Go to transaction code RSPFPAR_LOGIN. It will give you a complete list of parameters for Logon Rules. Just refer to the Comment field for the parameter definition.
These parameters can be maintain through Profile Maintenance (RZ10). When SAP startup process reads a profile parameter, it checks first on the Instance Profile. If the parameter cannot be found on the instance profile then it will look on the Default profile. If neither profile contains the parameter, the default value is taken out of the startup program coding. With that, I suggest you to create or maintain parameters in Default Profile. Just ensure that a particular parameter appears only in the default and not in the instance profile.
For the profile to take effect, you have to restart your application server.
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).
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).
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.
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.
Now refer to code #4 to handle the command when a user clicks on the icon button.
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.
sdn blogger
sap blogger
Recent Comments