diff between at line selection and HIDE technique

[Former Member]

hi all,

wht is the diff between at-line-selection and HIDE technique.

wht r code instructor

wht is extended testing

how can we find selected error records in session method ex:-if there r errors in 4th 9th 13th record.

tthnx in advance

[Former Member]

HIDE

Syntax

HIDE dobj.

Effect

This statement stores - in the current list level - the content of the variable dobj together with the current list line whose line number is contained in sy-linno. The data type of the variables dobj must be flat and no field symbols can be specified that point to rows of internal tables, and no class attributes can be specified. The stored values can be read as follows:

For each user action in a displayed screen list that leads to a list result, all the row values stored using HIDE - that is, the row on which the screen cursor is positioned at the time of the event - are assigned to the respective variables.

If a list row of an arbitrary list level is read or modified using the statements READ LINE or MODIFY LINE, all the values of this row stored using HIDE are assigned to the respective variables.

Notes

The HIDE statement works independently of whether the list cursor was set. In particular, variables for empty list rows can be stored - that is, rows in which the list cursor was positioned using statements like SKIP.

The HIDE statement should be executed immediately at the statement that has set the list cursor in the row.

Outside of classes, constants and literals that cannot be read in list results and in the statement READ LINE can be specified for dobj outside of classes.

Example

Storing square numbers and cubic numbers for a list of numbers. The example shows that arbitrary variables can be stored independently of row content. In the real situation, one would more likely store only the number and execute the calculation, when required, in the the event block for AT LINE-SELECTION.

REPORT ... 

DATA: square TYPE i, 
      cube   TYPE i. 

START-OF-SELECTION. 
  FORMAT HOTSPOT. 
  DO 10 TIMES. 
    square = sy-index ** 2. 
    cube   = sy-index ** 3. 
    WRITE / sy-index. 
    HIDE: square, cube. 
  ENDDO. 

AT LINE-SELECTION. 
  WRITE: square, cube.

AT LINE-SELECTION

Syntax

AT LINE-SELECTION.

Effect

This statement defines an event block whose event is triggered by the ABAP runtime environment during the display of a screen list - provided the scren cursor is on a list line and you select a function using the function code PICK. Through the definition of this event block, the standard list status is automatically enhanced in such a way that the function code F2 and, with it, the double-click mouse function is linked up to the function code PICK.

Note

If the function key F2 is linked with a function code different than PICK, each double click will trigger its even, usually AT USER-COMMAND, and not AT LINE-SELECTION.

Example

This program works with the standard list status. A line selection with the left mouse key causes the event AT LINE-SELECTION and creates details lists.

REPORT demo_at_line_selection. 

START-OF-SELECTION. 
  WRITE 'Click me!' COLOR = 5 HOTSPOT. 

AT LINE-SELECTION. 
  WRITE: / 'You clicked list', sy-listi, 
         / 'You are on list',  sy-lsind. 
  IF sy-lsind < 20. 
    SKIP. 
    WRITE: 'More ...' COLOR = 5 HOTSPOT. 
  ENDIF.

Thanks,

[Former Member]

Hi Amar,

i think you wanted to know abt code inspector and extended check.

Code insepctor is a tool used for checking syntax but is a advanced over normal synatx check tool. It gives u performance details. Its is called thru txn SCI.

It can be used for:

· ABAP Dictionary (SE11) for DDIC tables

· Class Builder (SE24) for classes and interfaces

· Function Builder (SE37) for function groups

· ABAP Editor (SE38) for programs or reports

· ABAP Workbench (SE80)

Pls go thru this link :

http://help.sap.com/saphelp_nw04/helpdata/en/56/fd3b87d203064aa925256ff88d931b/content.htm

Extended check is used to check for synatx but it again is advanced as it will tell u some errors and warnings which were not covered under normal check. It will tell u if there is violation of SAP standards. U can call it thru Utilities -> Extended check

Pls go thru below link :

http://help.sap.com/saphelp_nw2004s/helpdata/en/d1/801dd2454211d189710000e8322d00/content.htm

When you execute error record in session, you can process all error records using Process error transactions option. SM35 session will take care of and you can see same using analysis option in SM35.

Cheers,

Vikram

Pls reward for helpful replies!!

[Former Member]

hi vikram,

thnx for the reply. actually i was asked in an interview how can we see only selected errors ex :- there r errors in 3rd record 6th record and 11th record. and said without using session log. is it possible.

thank you bye

[Former Member]

Hello,

In traditional ALV they used this concept of HIDE and AT-LINE SELECTION.

Assumption:

===========

Assume that you have an output. Containing employee number and you want to display the employee information on double-clicking the employee number. Then the usage of HIDE comes in to pictire.

HIDE:

=====

When you loop at the internal table just use the statement HIDE to store the key attribute about the user.

AT-LINE SELECTION:

==================

This is an event which triggers when you click anything on the displayed output.

Now assume that you have hided the atribute EMPLOYEE NUMBER while looping as mentioned above. Now when you douuble-click on the any row, now you can use the attribute that you have hided using the HIDE (U can say this is primary attribute to select a unique record) and get the other information of that employee and display it.

I hope this helps.

Regs,

Venkat Ramanan N

Message was edited by: Venkat Ramanan Natarajan

[Former Member]

Hi amar,

1. wht is the diff between at-line-selection and HIDE technique.

Both are primarily used for same purpose - interactive list.

2. The old technique is of AT line selection,

where we get the contents of line (clicked by user)

as a Full CHARACTER Format of 132 or more characters.

(After that we have to get the required

value using OFFSET eg. 10 characters from left for some purchase order number)

3. This technique of using OFFSET,

has the basic flaw that if we change

the format/alignment of records,

then we need to change the OFFSET coding also.

4. If we use HIDE,

the field (eg.purchase order no) which

we WRITE on the screen

(no matter in which position we write),

gets back into the HIDE variable,

for further action.

regards,

amit m.