Solved: alv

Former Member · ‎2007 Apr 27

what are ALV reports? how they are different from normal reports? what are the main events that are used in an ALV report? what is the use of SLIS type pool in alv reports?

Former Member · ‎2007 Apr 27

I have send one ALV Document ... hope that may solve all your problem s regarding ALV Reports.

Regards,

Jayant Sahu.

Please Reward If Helpful.

Former Member · ‎2007 Apr 27

Hi ,

refer

http://www.sap-img.com/abap/what-is-alv-programming.htm

Hope this will solve your problem.

Award points if it helps.

-Gaurang

Former Member · ‎2007 Apr 27

hi,

chk this.

http://www.geocities.com/mpioud/Abap_programs.html

http://www.sapdevelopment.co.uk/reporting/reportinghome.htm

Simple ALV report

http://www.sapgenie.com/abap/controls/alvgrid.htm

http://wiki.ittoolbox.com/index.php/Code:Ultimate_ALV_table_toolbox

<u>ALV EVENTS</u>

1. Slis_ev_item_data_expand TYPE slis_formname VALUE 'ITEM_DATA_EXPAND'.

2. Slis_ev_reprep_sel_modify TYPE slis_formname VALUE 'REPREP_SEL_MODIFY'.

3. Slis_ev_caller_exit_at_start TYPE slis_formname VALUE 'CALLER_EXIT'.

4. Slis_ev_user_command TYPE slis_formname VALUE 'USER_COMMAND'.

5. Slis_ev_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.

6. Slis_ev_top_of_coverpage TYPE slis_formname VALUE 'TOP_OF_COVERPAGE'

7. Slis_ev_end_of_coverpage TYPE slis_formname VALUE 'END_OF_COVERPAGE'.

8. Slis_ev_foreign_top_of_page TYPE slis_formname VALUE ‘FOREIGN_TOP_OF_PAGE'.

9. Slis_ev_foreign_end_of_page TYPE slis_formname VALUE 'FOREIGN_END_OF_PAGE'.

10. Slis_ev_pf_status_set TYPE slis_formname VALUE 'PF_STATUS_SET'.

11. Slis_ev_list_modify TYPE slis_formname VALUE 'LIST_MODIFY'.

12. Slis_ev_top_of_list TYPE slis_formname VALUE 'TOP_OF_LIST'.

Information output at the start of the list

13. Slis_ev_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.

Information output at the end of a page. This is only called for printing.

14. Slis_ev_end_of_list TYPE slis_formname VALUE 'END_OF_LIST'.

15. Slis_ev_after_line_output TYPE slis_formname VALUE 'AFTER_LINE_OUTPUT'.

16. Slis_ev_before_line_output TYPE slis_formname VALUE 'BEFORE_LINE_OUTPUT'.

17. Slis_ev_subtotal_text TYPE slis_formname VALUE 'SUBTOTAL_TEXT'.

Regards

Reshma

Former Member · ‎2007 Apr 27

Hi,

ALV is Application List viewer. Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length. In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output. The report output can contain up to 90 columns in the display with the wide array of display options.

Advantages.

Collapse multiple reports into one, drastically cutting down your report development time

Save many hours using built-in ALV sorting, subtotaling and filtering capabilities

Add conditional structures into your ALV report: No programming required!

Combine ALV with display variants to meet a wide range of reporting requirements more easily

Dynamically reorder column layouts and add/subtract fields

Enable users and analysts to save their own personalized variants

Go & view this link for further Info,

http://help.sap.com/saphelp_46c/helpdata/en/99/49b844d61911d2b469006094192fe3/frameset.htm

Regards,

Padmaa.

Former Member · ‎2007 Apr 27

Hi Pinky,

I'm having nice alv material if u want i will send to your mail please send me your mail id

regards,

Pavan

Former Member · ‎2007 Apr 27

hi pavan,

my mail id is pinky24_reddy@yah..co.in plz send me the material

Former Member · ‎2007 Apr 27

hi

Message was edited by:

d pinky

Former Member · ‎2007 Apr 27

hi pavan,

my mail id is pinky24_reddy@yah..co.in plz send me the material

Former Member · ‎2007 Apr 27

hi pavan,

my mail id is pinky24_reddy@yah..co.in plz send me the material

Former Member · ‎2007 Apr 27

Sent 2 ALV files

Former Member · ‎2007 Apr 27

hi pinky

I had forwrded u material plz reward points if helpfull

Regards

Pavan

Former Member · ‎2007 Apr 27

hi,

ABAP List Viewer

The common features of report are column alignment, sorting, filtering, subtotals, totals etc. To implement these, a lot of coding and logic is to be put. To avoid that we can use a concept called ABAP List Viewer (ALV).

This helps us to implement all the features mentioned very effectively.

Using ALV, We can have three types of reports:

1. Simple Report

2. Block Report

3. Hierarchical Sequential Report

There are some function modules which will enable to produce the above reports without much effort.

All the definitions of internal tables, structures and constants are declared in a type-pool called SLIS.

1. SIMPLE REPORT.

The important function modules are

a. Reuse_alv_list_display

b. Reuse_alv_fieldcatalog_merge

c. Reuse_alv_events_get

d. Reuse_alv_commentary_write

e. Reuse_alv_grid_display

A. REUSE_ALV_LIST_DISPLAY : This is the function module which prints the data.

The important parameters are :

I. Export :

i. I_callback_program : report id

ii. I_callback_pf_status_set : routine where a user can set his own pf status or change the functionality of the existing pf status

iii. I_callback_user_command : routine where the function codes are handled

iv. I_structure name : name of the dictionary table

v. Is_layout : structure to set the layout of the report

vi. It_fieldcat : internal table with the list of all fields and their attributes which are to be printed (this table can be populated automatically by the function module REUSE_ALV_FIELDCATALOG_MERGE

vii. It_events : internal table with a list of all possible events of ALV and their corresponding form names.

II. Tables :

i. t_outtab : internal table with the data to be output

B. REUSE_ALV_FIELDCATALOG_MERGE : This function module is used to populate a fieldcatalog which is essential to display the data in ALV. If the output data is from a single dictionary table and all the columns are selected, then we need not exclusively create the field catalog. Its enough to mention the table name as a parameter(I_structure name) in the REUSE_ALV_LIST_DISPLAY. But in other cases we need to create it.

The Important Parameters are :

I. Export :

i. I_program_name : report id

ii. I_internal_tabname : the internal output table

iii. I_inclname : include or the report name where all the dynamic forms are handled.

II Changing

ct_fieldcat : an internal table with the type SLIS_T_FIELDCAT_ALV which is

declared in the type pool SLIS.

C. REUSE_ALV_EVENTS_GET : Returns table of possible events for a list type

Parameters :

I. Import :

Et_Events : The event table is returned with all possible CALLBACK events

for the specified list type (column 'NAME'). For events to be processed by Callback, their 'FORM' field must be filled. If the field is initialized, the event is ignored. The entry can be read from the event table, the field 'FORM' filled and the entry modified using constants from the type pool SALV.

II. Export :

I_List_type :

0 = simple list REUSE_ALV_LIST_DISPLAY

1 = hierarchcal-sequential list REUSE_ALV_HIERSEQ_LIST_DISPLAY

2 = simple block list REUSE_ALV_BLOCK_LIST_APPEND

3 = hierarchical-sequential block list

REUSE_ALV_BLOCK_LIST_HS_APPEND

D. REUSE_ALV_COMMENTARY_WRITE : This is used in the Top-of-page event to print the headings and other comments for the list.

Parameters :

I. it_list_commentary : internal table with the headings of the type slis_t_listheader.

This internal table has three fields :

Typ : ‘H’ – header, ‘S’ – selection , ‘A’ - action

Key : only when typ is ‘S’.

Info : the text to be printed

E. REUSE_ALV_GRID_DISPLAY : A new function in 4.6 version, to display the results in grid rather than as a preview.

Parameters : same as reuse_alv_list_display

2. BLOCK REPORT

This is used to have multiple lists continuously.

The important functions used in this report are:

A. REUSE_ALV_BLOCK_LIST_INIT

B. REUSE_ALV_BLOCK_LIST_APPEND

C. REUSE_ALV_BLOCK_LIST_HS_APPEND

D. REUSE_ALV_BLOCK_LIST_DISPLAY

A. REUSE_ALV_BLOCK_LIST_INIT

Parameters:

I. I_CALLBACK_PROGRAM

II. I_CALLBACK_PF_STATUS_SET

III. I_CALLBACK_USER_COMMAND

This function module is used to set the default gui status etc.

B. REUSE_ALV_BLOCK_LIST_APPEND

Parameters :

Export :

I. is_layout : layout settings for block

II. it_fieldcat : field catalog

III. i_tabname : internal table name with output data

IV. it_events : internal table with all possible events

Tables :

i. t_outtab : internal table with output data.

This function module adds the data to the block.

Repeat this function for all the different blocks to be displayed one after the other.

C. REUSE_ALV_BLOCK_LIST_HS_APPEND

This function module is used for hierarchical sequential blocks.

D. REUSE_ALV_BLOCK_LIST_DISPLAY

Parameters : All the parameters are optional.

This function module display the list with data appended by the above function.

Here the functions REUSE_ALV_FIELDCATALOG_MERGE, REUSE_ALV_EVENTS_GET, REUSE_ALV_COMMENTARY_WRITE can be used.

3. Hierarchical reports :

Hierarchical sequential list output.

The function module is

A. REUSE_ALV_HIERSEQ_LIST_DISPLAY

Parameters:

I. Export:

i. I_CALLBACK_PROGRAM

ii. I_CALLBACK_PF_STATUS_SET

iii. I_CALLBACK_USER_COMMAND

iv. IS_LAYOUT

v. IT_FIELDCAT

vi. IT_EVENTS

vii. i_tabname_header : Name of the internal table in the program containing the

output data of the highest hierarchy level.

viii. i_tabname_item : Name of the internal table in the program containing the

output data of the lowest hierarchy level.

ix. is_keyinfo : This structure contains the header and item table field

names which link the two tables (shared key).

II. Tables

i. t_outtab_header : Header table with data to be output

ii. t_outtab_item : Name of the internal table in the program containing the

output data of the lowest hierarchy level.

slis_t_fieldcat_alv : This internal table contains the field attributes. This internal table can be populated automatically by using ‘REUSE_ALV_FIELDCATALOG_MERGE’.

Important Attributes :

A. col_pos : position of the column

B. fieldname : internal fieldname

C. tabname : internal table name

D. ref_fieldname : fieldname (dictionary)

E. ref_tabname : table (dictionary)

F. key(1) : column with key-color

G. icon(1) : icon

H. symbol(1) : symbol

I. checkbox(1) : checkbox

J. just(1) : (R)ight (L)eft (C)ent.

K. do_sum(1) : sum up

L. no_out(1) : (O)blig.(X)no out

M. outputlen : output length

N. seltext_l : long key word

O. seltext_m : middle key word

P. seltext_s : short key word

Q. reptext_ddic : heading (ddic)

R. ddictxt(1) : (S)hort (M)iddle (L)ong

S. datatype : datatype

T. hotspot(1) : hotspot

**********************************************************************************************

some theory regarding alv:

This table tells ALV which events are processed by the caller by CALLBACK.

The table of possible events per list type can be initialized using the module REUSE_ALV_EVENTS_GET.

You can display the names of the constants in the type pools SLIS which represent the individual events using the individual test function in the function module

REUSE_ALV_EVENT_NAMES_GET. Only events with a form routine name are processed.

The table structure contains the fields:

• IT_EVENTS-NAME

Name of the Callback event.

Possible Callback events:

• Action

USER_COMMAND USING R_UCOMM LIKE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD

Process actions on the list

As this is a frequently-used Callback event, the form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_USER_COMMAND.

PF_STATUS_SET USING RT_EXTAB TYPE SLIS_T_EXTAB

If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).

The STANDARD status of the function group SALV should be used as a template for a user-specific status.

As this is a frequently-used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.

ITEM_DATA_EXPAND USING RS_SELFIELD TYPE SLIS_SELFIELD RFLG_ALL TYPE C

Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT.

Exit for passing item entries (ITEM table) for a header record which was expanded interactively by the user.

RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header which is to be expanded.

RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table. RS_SELFIELD is initial in this case.

CALLER_EXIT USING RS_DATA Is called at the beginning of the function module to make special settings. It is not usually used.

• List processing events

IMPORTANT: The application Callback routine must not manipulate the internal output table and/or its header record. This restriction applies to all Callbacks which are called in the list output and run under the 'List processing events'.

TOP_OF_LIST no USING parameter. Information output at the start of the list

END_OF_LIST no USING parameter. Information output at the end of the list

TOP_OF_PAGE no USING parameter

Equivalent to the list processing TOP-OF-PAGE event

END_OF_PAGE no USING parameter. Not available for hierarchical-sequential lists.

Information output at the end of a page. This is only called for printing.

TOP_OF_COVERPAGE no USING parameter

The selection information and list status are output together (if they exist) on a separate page by default. See also the documentation of the parameters:

IS_PRINT-NO_COVERPAGE

IS_PRINT-NO_PRINT_SELINFOS

IS_PRINT-NO_PRINT_LISTINFOS

IS_LAYOUT-GET_SELINFOS

The user can format the header area of the 'cover page' himself or herself by specifying a Callback routine for this event.

END_OF_COVERPAGE no USING parameter

Analogously to TOP_OF_COVERPAGE the user can add other information to the information output by ALV (selection information, list status) at this event.

FOREIGN_TOP_OF_PAGE no USING parameter

The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).

In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.

FOREIGN_END_OF_PAGE no USING parameter

The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).

In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.

BEFORE_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO

Output information before each output line. Should only be used in justified cases because it costs a lot of performance.

AFTER_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO

Output information after each output line. Should only be used in justified cases because it costs a lot of performance.

• Internal use only

LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME

R_INDEX LIKE SY-TABIX

R_INDEX_ITEM LIKE SY-TABIX

R_INDEX_SUM LIKE SY-TABIX

• IT_EVENTS-FORM

Name of the form routine which should be called in the calling program at the event.

Field_catalog:

Field catalog with field descriptions

2.7.1. Description

Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields). A field catalog is required for every ALV list output.

The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module

See also the documentation of the function module REUSE_ALV_FIELDCATALOG_MERGE.

The minimal field catalog is documented under 'default'. The caller can use the other optional parameters to assign output attributes to a field which differ from the default.

A field catalog need not be built-up and passed explicitly only under the following conditions:

• The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE.

• all fields in this structure are to be output

• the structure name is passed to ALV in the parameter I_STRUCTURE_NAME.

See also the documentation of the IMPORTING paramter I_STRUCTURE_NAME.

Positioning

• row_pos (row position)

value set: 0, 1 - 3

Only relevant if the list output is to be multi-line (two or three lines) by default.

A multi-line list can also be defined by the user interactively if the default list is one-line.

The parameter specifies the relative output line of the column in a multi-line list.

• col_pos (column position)

value set: 0, 1 - 60

only relevant when the default relative column positions differ from the field catalog field sequence. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the field catalog field sequence.

Identification

• fieldname (field name)

value set: internal output table field name (required parameter)

Name of the internal output table field which is described by this field catalog entry

• tabname (internal output table)

value set: SPACE, internal output table name

This parameter is used in 'manual' field catalog build-up only for hierarchical-sequential lists.

Name of the internal output table which contains the field FIELDCAT-FIELDNAME.

Data Dictionary reference

• ref_fieldname (reference field name)

value set: SPACE, Data Dictionary field name

Name of the Data Dictionary field referred to.

This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.

• ref_tabname (reference table/structure field name)

value set: SPACE, name of a Data Dictionary structure or table

Structure or table name of the referred Data Dictionary field.

This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).

Reference to fields with currency/measurement unit

Each internal output table sum or quantity field whose decimal places are to be formatted appropriately for the unit in the list must follow the convention:

• the field is of data type QUAN or CURR (internal type P) (the field must really have this physical data type. Overwriting the physical data type with the parameter FIELDCAT-DATATYPE has no effect)

• There is a field in the internal output table which contains the associated unit.

• There is also an entry in the field catalog for the unit field.

(If the unit is not to appear as a column in the list, and cannot be interactively displayed as a column, e.g. because it is always unambiguous and is therefore explicitly output by the caller in the list header, the field catalog units field entry can take the parameter FIELDCAT-TECH = 'X'.

The association of a value field to a unit affects the output as follows:

• appropriate decimal places display for the unit

• an initialized field with a link to a non-initial unit is output as '0' for the unit (if FIELDCAT-NO_ZERO is initial). When this field is summed, this unit affects whether the units are homogeneous.

• an initialized field with a link to an initial unit is output as SPACE. When this field is summed, the unit SPACE does not affect the homogeneity of the units.

• When non-initial fields with an initial unit are summed, the unit SPACE is considered to be a unit.

Link to currency unit

• cfieldname (currency unit field name)

value set: SPACE, output table field name

Only relevant for amount columns with associated unit.

Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.

• ctabname (internal currency unit field output table)

value set: SPACE, output table field name

only relevant for hierarchical-sequential lists

Name of the internal output table containing the FIELDCAT-CFIELDNAME field.

Link to measurement unit

• qfieldname (measurement unit field name)

value set: SPACE, output table field name

only relevant for quantity columns with unit link.

Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.

The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.

• qtabname (internal measurement unit field output table)

value set: SPACE, output table field name

only relevant for hierarchical-sequential lists

Name of the internal output table containing the FIELDCAT-QFIELDNAME field.

Column output options

• outputlen (column width)

value set: 0 (initial), n

For fields with a Data Dictionary link this parameter can be left initial.

For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).

initial = column width is the output length of the referred Data Dictionary field (domain).

n = column width is n characters

• key (key column)

value set: SPACE, 'X' 'X' = kex field (key field output in color)

Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.

For exceptions see the documentation of the FIELDCAT-KEY_SEL parameter.

• key_sel (hideable key column)

value set: SPACE, 'X'

only relevant when FIELDCAT-KEY = 'X'

Key field which can be hidden interactively.

The key column sequence cannot be changed interactively by the user.

The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.

• no_out (field in field list)

value set: SPACE, 'X' 'X' = field is not displayed in the current list.

The user can interactively choose the field for output from the field list.

The user can display the contents of these fields at line level using the 'Detail' function.

See also the 'Detail screen' documentation of the parameter IS_LAYOUT.

• tech (technical field)

value set: SPACE, 'X' 'X' = technical field

Field cannot be output in the list and cannot be displayed interactively.

Field can only be used in the field catalog (not in IT_SORT, ...).

• emphasize (highlight columns in color)

value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)

'X' = column is colored with the default column highlight color.

'Cxyz' = column is colored with a coded color:

• C: Color (coding must begin with C)

• x: color number

• y: bold

• z: inverse

• hotspot (column as hotspot)

value set: SPACE, 'X'

'X' = column cells are output as hotspots

• fix_column (fix column)

value set: SPACE, 'X'

Not relevant for block lists (output of several lists consecutively)

'X' = column fixed (does not scroll horizontally)

All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively. See also the documentation of the Layout parameter

IS_LAYOUT-NO_KEYFIX of the IMPORTING paramter IS_LAYOUT.

• do_sum (sum over column)

value set: SPACE, 'X' 'X' = a sum is to be calculated over this internal output table field.

This function can also be called by the user interactively.

• no_sum (sums forbidden)

value set: SPACE, 'X' 'X' = no sum can be calculated over this field, although the data type of the field would allow summing.

• input (column ready for input)

Function not available

Format column contents

• icon

value set: SPACE, 'X' 'X' = column contents to be output as an icon.

The caller must consider the printability of icons.

• symbol

value set: SPACE, 'X' 'X' = column contents are to be output as a symbol.

The internal output table column must be a valid symbol character.

The caller must consider the printability of symbols.

Symbols can usually be printed, but may not always be output correctly, depending on the printer configuration.

• just (justification)

value set: SPACE, 'R', 'L', 'C'

Only relevant for fields of data type CHAR or NUMC

' ' = default justification for this data type

'R' = right-justified output

'L' = left-justified output

'C' = centered output

The justification of the column header always follows the justification of the columns. Independent justification of the column neader is not possible.

• lzero (leading zeros)

value set: SPACE, 'X'

Only relevant for fields of data type NUMC

ALV outputs NUMC fields right-justified without leading zeros by default.

'X' = output with leading zeros

Note: If a NUMC field is output left-justified or centered by FIELDCAT-JUST, leading zeros are output. If the output of leading zeros is suppressed by a Data Dictionary reference ALPHA conversion exit, the output is always left-justified.

• no_sign (no +/- sign) Only relevant for value fields

value set: SPACE, 'X' 'X' = value output without +/ sign

• no_zero (suppress zeros) Only relevant for value fields

value set: SPACE, 'X' 'X' = suppress zeros

• edit_mask (field formatting)

value set: SPACE, template

template = see documentation of WRITE formatting option USING EDIT MASK template

The output conversion conv can be made by template = '== conv'.

Texts

The following text parameters should be specified for program fields without a Data Dictionary reference. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored. If the user changes the column width interactively, the column header text with the appropriate length is always used. The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.

The 'long field label' is also used in display variant definition, sort, etc. popups.

• seltext_l (long field label)

• seltext_m (medium field label)

• seltext_s (short field label)

• reptext_ddic (header)

analogous to the Data element maintenance 'Header'

The specified text is not necessarily output in the list, an optimum among all texts is sought.

• ddictxt (specify text)

value set: SPACE, 'L', 'M', 'S'

You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.

Parameters for program fields without Data Dictionary reference

see also 'Text' parameters

• datatype (data type)

value set: SPACE, Data Dictionary data type (CHAR, NUMC,...)

Only relevant for fields without Data Dictionary reference

Program field data type

• ddic_outputlen (external output length)

value set: 0 (initial), n

Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.

Prerequisites:

• FIELDCAT-EDIT_MASK = '==conv'

see also the documentation of the parameter FIELDCAT-EDIT_MASK

• FIELDCAT-INTLEN = n

see also the documentation of the parameter FIELDCAT-INTLEN

n = external format field output length

The column width FIELDCAT-OUTPUTLEN need not be the same as the external format output length (FIELDCAT-DDIC_OUTPUTLEN).

• intlen (internal output length)

value set: 0 (initial), n

Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.

Prerequisites:

• FIELDCAT-EDIT_MASK = '==conv'

see also the documentation of the parameter FIELDCAT-EDIT_MASK

• FIELDCAT-DDIC_OUTPUTLEN = n

see also the documentation of the parameter FIELDCAT-DDIC_OUTPUTLEN

n = internal format field output length

• rollname (data element)

value set: SPACE, Data Dictionary data element name

F1 help can be provided for a program field without a Data Dictionary reference, or F1 help which differs from the Data Dictionary help can be provided for a field with a Data Dictionary reference, using this parameter.

When F1 help is called for this field, the documentation of the specified data element is displayed.

If the FIELDCAT-ROLLNAME is initial for fields with a Data Dictionary reference, the documentation of the data element of the referred Data Dictionary field is output.

Others

• sp_group (field group key)

value set: SPACE, CHAR(1)

Field group key.

Keys are assigned to group names in the IT_SPECIAL_GROUPS parameter (see also the documentation of the parameter IT_SPECIAL_GROUPS).

When such an assignment is made in the field catalog and in IT_SPECIAL_GROUPS, the fields are grouped correspondingly in the display variant popup.

• reprep (Report/Report interface selection criterion)

value set: SPACE, 'X'

Prerequisites:

• The system contains the Report/Report interface (function group RSTI, table TRSTI)

• Parameter LAYOUT-REPREP = 'X'

(see also the documentation of the parameter LAYOUT-REPREP of the IMPORTING parameter IS_LAYOUT )

'X' = When the Report/Report interface is called, the value of this field is passed in the selected interface start record as a selection criterion.

2.7.2. Default

• The following entries are usually sufficient for internal table fields with a reference to a field defined in the Data Dictionary :

• fieldname

• ref_tabname

Notes:

ALV gets the remaining information from the Data Dictionary.

If no relative column position (COL_POS) is specified, the fields are output in the list in the order in which they were added to the field catalog.

REF_FIELDNAME need only be specifid when the name of the internal table field differs from the name of the referred Data Dictionary field.

Information which is explicitly entered in the field catalog is not overwritten by information from the Data Dictionary.

Priority rule:

Entries in the field catalog have priority over differing entries in the Data Dictionary.

• The following entries are usually sufficient for internal table fields without a reference to the Data Dictionary (program fields):

• fieldname

• outputlen

• datatype

• seltext_s

• seltext_m

• seltext_l

Notes:

F1 help can be provided for program fields by assigning a data element to the parameter ROLLNAME.

If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and REPTEXT_DDIC contain appropriate field labels, the program field column headers are also adjusted appropriately when the column width changes

sites :

http://www.sapdevelopment.co.uk/reporting/alv/alv_variousfcat.htm

check below sites.

alv material and sites :

http://www.geocities.com/mpioud/Abap_programs.html

http://www.sapdevelopment.co.uk/reporting/reportinghome.htm

Simple ALV report

http://www.sapgenie.com/abap/controls/alvgrid.htm

ALV

1. Please give me general info on ALV.

http://www.sapfans.com/forums/viewtopic.php?t=58286

http://www.sapfans.com/forums/viewtopic.php?t=76490

http://www.sapfans.com/forums/viewtopic.php?t=20591

http://www.sapfans.com/forums/viewtopic.php?t=66305 - this one discusses which way should you use - ABAP Objects calls or simple function modules.

2. How do I program double click in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=11601

http://www.sapfans.com/forums/viewtopic.php?t=23010

3. How do I add subtotals (I have problem to add them)...

http://www.sapfans.com/forums/viewtopic.php?t=20386

http://www.sapfans.com/forums/viewtopic.php?t=85191

http://www.sapfans.com/forums/viewtopic.php?t=88401

http://www.sapfans.com/forums/viewtopic.php?t=17335

4. How to add list heading like top-of-page in ABAP lists?

http://www.sapfans.com/forums/viewtopic.php?t=58775

http://www.sapfans.com/forums/viewtopic.php?t=60550

http://www.sapfans.com/forums/viewtopic.php?t=16629

5. How to print page number / total number of pages X/XX in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=29597 (no direct solution)

6. ALV printing problems. The favourite is: The first page shows the number of records selected but I don't need this.

http://www.sapfans.com/forums/viewtopic.php?t=64320

http://www.sapfans.com/forums/viewtopic.php?t=44477

7. How can I set the cell color in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=52107

8. How do I print a logo/graphics in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=81149

http://www.sapfans.com/forums/viewtopic.php?t=35498

http://www.sapfans.com/forums/viewtopic.php?t=5013

9. How do I create and use input-enabled fields in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=84933

http://www.sapfans.com/forums/viewtopic.php?t=69878

10. How can I use ALV for reports that are going to be run in background?

http://www.sapfans.com/forums/viewtopic.php?t=83243

http://www.sapfans.com/forums/viewtopic.php?t=19224

11. How can I display an icon in ALV? (Common requirement is traffic light icon).

http://www.sapfans.com/forums/viewtopic.php?t=79424

http://www.sapfans.com/forums/viewtopic.php?t=24512

12. How can I display a checkbox in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=88376

http://www.sapfans.com/forums/viewtopic.php?t=40968

http://www.sapfans.com/forums/viewtopic.php?t=6919

Go thru these programs they may help u to try on some hands on

ALV Demo program

BCALV_DEMO_HTML

BCALV_FULLSCREEN_DEMO ALV Demo: Fullscreen Mode

BCALV_FULLSCREEN_DEMO_CLASSIC ALV demo: Fullscreen mode

BCALV_GRID_DEMO Simple ALV Control Call Demo Program

BCALV_TREE_DEMO Demo for ALV tree control

BCALV_TREE_SIMPLE_DEMO

BC_ALV_DEMO_HTML_D0100

Former Member · ‎2007 Apr 27

I have send one ALV Document ... hope that may solve all your problem s regarding ALV Reports.

Regards,

Jayant Sahu.

Please Reward If Helpful.

Former Member · ‎2007 Apr 27

Hi pinky,

Go through this Urls It is very useful.

1. Please give me general info on ALV.

http://www.sapfans.com/forums/viewtopic.php?t=58286

http://www.sapfans.com/forums/viewtopic.php?t=76490

http://www.sapfans.com/forums/viewtopic.php?t=20591

http://www.sapfans.com/forums/viewtopic.php?t=66305 - this one discusses which way should you use - ABAP Objects calls or simple function modules.

2. How do I program double click in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=11601

http://www.sapfans.com/forums/viewtopic.php?t=23010

3. How do I add subtotals (I have problem to add them)...

http://www.sapfans.com/forums/viewtopic.php?t=20386

http://www.sapfans.com/forums/viewtopic.php?t=85191

http://www.sapfans.com/forums/viewtopic.php?t=88401

http://www.sapfans.com/forums/viewtopic.php?t=17335

4. How to add list heading like top-of-page in ABAP lists?

http://www.sapfans.com/forums/viewtopic.php?t=58775

http://www.sapfans.com/forums/viewtopic.php?t=60550

http://www.sapfans.com/forums/viewtopic.php?t=16629

5. How to print page number / total number of pages X/XX in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=29597 (no direct solution)

6. ALV printing problems. The favourite is: The first page shows the number of records selected but I don't need this.

http://www.sapfans.com/forums/viewtopic.php?t=64320

http://www.sapfans.com/forums/viewtopic.php?t=44477

7. How can I set the cell color in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=52107

8. How do I print a logo/graphics in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=81149

http://www.sapfans.com/forums/viewtopic.php?t=35498

http://www.sapfans.com/forums/viewtopic.php?t=5013

9. How do I create and use input-enabled fields in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=84933

http://www.sapfans.com/forums/viewtopic.php?t=69878

10. How can I use ALV for reports that are going to be run in background?

http://www.sapfans.com/forums/viewtopic.php?t=83243

http://www.sapfans.com/forums/viewtopic.php?t=19224

11. How can I display an icon in ALV? (Common requirement is traffic light icon).

http://www.sapfans.com/forums/viewtopic.php?t=79424

http://www.sapfans.com/forums/viewtopic.php?t=24512

12. How can I display a checkbox in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=88376

http://www.sapfans.com/forums/viewtopic.php?t=40968

http://www.sapfans.com/forums/viewtopic.php?t=6919

Go thru these programs they may help u to try on some hands on

ALV Demo program

BCALV_DEMO_HTML

BCALV_FULLSCREEN_DEMO ALV Demo: Fullscreen Mode

BCALV_FULLSCREEN_DEMO_CLASSIC ALV demo: Fullscreen mode

BCALV_GRID_DEMO Simple ALV Control Call Demo Program

BCALV_TREE_DEMO Demo for ALV tree control

BCALV_TREE_SIMPLE_DEMO

BC_ALV_DEMO_HTML_D0100

Regards,

P.Naganjana Reddy

Former Member · ‎2007 Apr 27

check in the transaction LIBS -- u will get all kinds of reports

Former Member · ‎2007 Apr 27

Hi, This is eashwar.

Check this sample prg which i did,

Actually ALV is used to display the output

in a grid.

Reward if it is useful to you.

REPORT zeasproject .

TABLES : bkpf,

bseg.

TYPE-POOLS : slis.

************************************************************************

DECLARATION PART *

************************************************************************

DATA: w_repid LIKE sy-repid. "Program name.

DATA: w_title TYPE lvc_title VALUE 'ALV PROGRAM'.

DATA: w_layout TYPE slis_layout_alv. "Layout setup.

DATA: w_fieldcat TYPE slis_t_fieldcat_alv. "Field Catlog.

*DATA: w_events TYPE slis_t_event. "Events.

*DATA: w_header TYPE slis_t_listheader. "Header.

************************************************************************

INTERNAL TABLE AND WORK AREA FOR THE FIELDS IN BKPF TABLE *

************************************************************************

DATA : BEGIN OF itab_bkpf OCCURS 0,

bukrs LIKE bkpf-bukrs, "Company Code.

gjahr LIKE bkpf-gjahr, "Fiscal Year.

budat LIKE bkpf-budat, "Posting Date in the Document.

belnr LIKE bkpf-belnr, "Accounting document number.

blart LIKE bkpf-blart, "Document Type.

END OF itab_bkpf.

DATA : wa_bkpf LIKE LINE OF itab_bkpf.

************************************************************************

INTERNAL TABLE AND WORK AREA FOR THE FIEDLS IN BSEG TABLE *

************************************************************************

DATA : BEGIN OF itab_bseg_debit OCCURS 0,

bukrs LIKE bseg-bukrs, "Company Code.

gjahr LIKE bseg-gjahr, "Fiscal Year.

belnr LIKE bseg-belnr, "Accounting Document Number.

buzei LIKE bseg-buzei, "Line Item.

hkont LIKE bseg-hkont, "General Leadger Account.

shkzg LIKE bseg-shkzg, "Credit/Debit Indicator.

wrbtr LIKE bseg-wrbtr, "Amount in Document Currency.

pswsl LIKE bseg-pswsl, "Update Currency for Gen.Ledger

dmbtr LIKE bseg-dmbtr, "Amount in local currency.

sgtxt LIKE bseg-sgtxt, "Item Text.

zuonr LIKE bseg-zuonr, "Assignment Number.

END OF itab_bseg_debit.

DATA : itab_bseg_credit LIKE STANDARD TABLE OF itab_bseg_debit WITH

HEADER LINE.

************************************************************************

FINAL OUTPUT INTERNAL TABLE *

************************************************************************

DATA : BEGIN OF itab_output OCCURS 0,

belnr LIKE bseg-belnr, "(15),

bukrs LIKE bseg-bukrs, "(04),

budat LIKE bkpf-budat, "(08),

buzei LIKE bseg-buzei, "(03),

hkont LIKE bseg-hkont, "(10),

blart LIKE bkpf-blart, "(02),

shkzg LIKE bseg-shkzg, "(01),

wrbtr LIKE bseg-wrbtr, "(15),

pswsl LIKE bseg-pswsl, "(05),

dmbtr LIKE bseg-dmbtr, "(15),

sgtxt LIKE bseg-sgtxt, "(20),

zuonr LIKE bseg-zuonr, "(18),

END OF itab_output.

************************************************************************

CONSTANTS : c_debit TYPE c VALUE 'S',

c_credit TYPE c VALUE 'H'.

************************************************************************

SELECT-OPTIONS *

************************************************************************

SELECTION-SCREEN BEGIN OF BLOCK input WITH FRAME TITLE text-t01.

SELECT-OPTIONS : s_bukrs FOR bkpf-bukrs OBLIGATORY.

PARAMETERS : p_year LIKE bkpf-gjahr OBLIGATORY.

SELECT-OPTIONS : s_budat FOR bkpf-budat OBLIGATORY,

s_dbacct FOR bseg-hkont OBLIGATORY,

s_cracct FOR bseg-hkont OBLIGATORY,

s_amt FOR bseg-dmbtr .

SELECTION-SCREEN END OF BLOCK input.

************************************************************************

SELECTING RECORDS FROM BKPF TABLE BASED ON THE CONDITION *

************************************************************************

SELECT bukrs gjahr budat belnr blart

FROM bkpf INTO TABLE itab_bkpf

WHERE bukrs IN s_bukrs AND

gjahr EQ p_year AND

budat IN s_budat.

************************************************************************

SELECTING DEBIT LINE ITEMITEMS FROM BSEG FOR THE DOCUMENT *
NUMBER SELECTED FROM BKPF *

************************************************************************

IF NOT itab_bkpf[] IS INITIAL.

SELECT bukrs gjahr belnr buzei

hkont shkzg wrbtr pswsl

dmbtr sgtxt zuonr

FROM bseg INTO TABLE itab_bseg_debit

FOR ALL ENTRIES IN itab_bkpf

WHERE bukrs EQ itab_bkpf-bukrs AND

belnr EQ itab_bkpf-belnr AND

gjahr EQ itab_bkpf-gjahr AND

hkont IN s_dbacct AND

shkzg EQ c_debit AND

dmbtr IN s_amt.

************************************************************************

SELECTING CREDIT LINE ITEMITEMS FROM BSEG FOR THE DOCUMENT *
NUMBER SELECTED FROM BKPF *

************************************************************************

SELECT bukrs gjahr belnr buzei

hkont shkzg wrbtr pswsl

dmbtr sgtxt zuonr

FROM bseg INTO TABLE itab_bseg_credit

FOR ALL ENTRIES IN itab_bkpf

WHERE bukrs EQ itab_bkpf-bukrs AND

belnr EQ itab_bkpf-belnr AND

gjahr EQ itab_bkpf-gjahr AND

hkont IN s_cracct AND

shkzg EQ c_credit AND

dmbtr IN s_amt.

ENDIF.

SORT itab_bkpf BY bukrs gjahr belnr.

SORT itab_bseg_credit BY bukrs gjahr belnr.

************************************************************************

LOOPING THE DEBIT ENTRIES *

************************************************************************

LOOP AT itab_bseg_debit.

READING THE CREDIT ENTRIES WHICH MATCHES WITH HE CURRENT DOC. NUMBER *

READ TABLE itab_bseg_credit WITH KEY

bukrs = itab_bseg_debit-bukrs

gjahr = itab_bseg_debit-gjahr

belnr = itab_bseg_debit-belnr BINARY SEARCH.

IF sy-subrc EQ 0.

*READING THE POSTING DATE AND DOCUMENT TYPE FOR THE CURRENT DOUCMENT *

AND APPENDING THE DEBIT AND CREDIT ENTRIES *

READ TABLE itab_bkpf INTO wa_bkpf WITH KEY

bukrs = itab_bseg_debit-bukrs

gjahr = itab_bseg_debit-gjahr

belnr = itab_bseg_debit-belnr BINARY SEARCH.

itab_output-belnr = itab_bseg_debit-belnr.

itab_output-bukrs = itab_bseg_debit-bukrs.

itab_output-budat = wa_bkpf-budat.

itab_output-buzei = itab_bseg_debit-buzei.

itab_output-hkont = itab_bseg_debit-hkont.

itab_output-blart = wa_bkpf-blart.

itab_output-shkzg = itab_bseg_debit-shkzg.

itab_output-wrbtr = itab_bseg_debit-wrbtr.

itab_output-pswsl = itab_bseg_debit-pswsl.

itab_output-dmbtr = itab_bseg_debit-dmbtr.

itab_output-sgtxt = itab_bseg_debit-sgtxt.

itab_output-zuonr = itab_bseg_debit-zuonr.

APPEND itab_output.

itab_output-belnr = itab_bseg_credit-belnr.

itab_output-bukrs = itab_bseg_credit-bukrs.

itab_output-budat = wa_bkpf-budat.

itab_output-buzei = itab_bseg_credit-buzei.

itab_output-hkont = itab_bseg_credit-hkont.

itab_output-blart = wa_bkpf-blart.

itab_output-shkzg = itab_bseg_credit-shkzg.

itab_output-wrbtr = itab_bseg_credit-wrbtr.

itab_output-pswsl = itab_bseg_credit-pswsl.

itab_output-dmbtr = itab_bseg_credit-dmbtr.

itab_output-sgtxt = itab_bseg_credit-sgtxt.

itab_output-zuonr = itab_bseg_credit-zuonr.

APPEND itab_output.

ENDIF.

ENDLOOP.

SORT itab_output BY belnr budat shkzg.

************************************************************************

PERFORM FUNCTION *

************************************************************************

w_repid = sy-repid.

PERFORM i_fieldcat CHANGING w_fieldcat.

PERFORM i_layout CHANGING w_layout.

*PERFORM i_header CHANGING w_header.

*PERFORM i_events CHANGING w_events.

************************************************************************

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

i_callback_program = 'ZEASPROJECT_ALV' " w_repid

i_grid_title = w_title

is_layout = w_layout

it_fieldcat = w_fieldcat

i_save = 'A'

TABLES

t_outtab = itab_output

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

************************************************************************

*&----

*& FORM i_fieldcat

*&----

FORM i_fieldcat CHANGING p_w_feildcat.

DATA: l_line_fieldcat TYPE slis_fieldcat_alv.

CLEAR l_line_fieldcat.

l_line_fieldcat-fieldname = 'BELNR'.