Output field length issue in OO ALV

Hello Experts,
I have an requirement to download ALV grid output into Excel but some of columns having more than 128 characters, as per standard SAP will not support so I have included one more button and I have written the below code.
field-symbols: <fs_table> type standard table,
 <fs_wa>.
* Get the current fields of the layout
CALL METHOD ALV_GRID->GET_FRONTEND_FIELDCATALOG
 IMPORTING
 ET_FIELDCATALOG = it_fcat.
* Generate dynamic internal table
CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
 EXPORTING
 IT_FIELDCATALOG = it_fcatn
 IMPORTING
 EP_TABLE = dyn_table
assign dyn_table->* to <fs_table>.
create data dyn_line like line of <fs_table>.
assign dyn_line->* to <fs_wa>.
loop at lt_final into ls_final.
 if ls_final-EBELP is not INITIAL.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
 EXPORTING
 INPUT = ls_final-EBELP
 IMPORTING
 OUTPUT = ls_final-EBELP.
 endif.
 MOVE-CORRESPONDING ls_final to <fs_wa>.
 append <fs_wa> to <fs_table>.
endloop.
CALL FUNCTION 'GUI_DOWNLOAD'
 EXPORTING
 FILENAME = FULLPATH
 FILETYPE = 'DAT'
 WRITE_FIELD_SEPARATOR = 'X'
 CONFIRM_OVERWRITE = 'X'
 TABLES
 DATA_TAB = <fs_table>
 FIELDNAMES = LT_HEADING
Now my problem is some of field output value getting truncated(in excel) but it displayed in Grid output.
eg.
lt_final having one text field(Doc. Type description) and the length is 20, actually printing 17 characters but we are not defining the output length.
Can you please anyone faced the problem earlier? Basically the SAP version is R/3 4.7.
Regards,
Vadamalai A

Hello All,
Before calling CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
we can define the length
WHEN 'BATXT'. wa_fcatn-OUTPUTLEN =
20.
Regards,
Vadamalai A.
We can close this thread.

Similar Messages

Display output fields in Hierarchy format in ALV report

Hi,
I have a requirement to display the output fileds in ALV report, the output format is like this . The output field should be in ALV format, under each purchase order its corresponding line item should appear.
Pruchase Order 4700000581
company code item
 9001 10
 9001 20.
 9001 30.
Pruchase Order 4700000174
 9001 10
 9001 20.
Can any one please help me how to do this in ALV report.

Hi
This can be achieved using the Heirarchial ALV list
see the sample and do it
REPORT ZALV5_OBJECTS.
TABLES : EKKO.
TYPE-POOLS : SLIS.
TYPES : BEGIN OF TY_EKKO,
EBELN TYPE EKPO-EBELN,
EBELP TYPE EKPO-EBELP,
STATU TYPE EKPO-STATU,
AEDAT TYPE EKPO-AEDAT,
MATNR TYPE EKPO-MATNR,
MENGE TYPE EKPO-MENGE,
MEINS TYPE EKPO-MEINS,
NETPR TYPE EKPO-NETPR,
PEINH TYPE EKPO-PEINH,
END OF TY_EKKO.
DATA: IT_EKKO TYPE STANDARD TABLE OF TY_EKKO INITIAL SIZE 0,
IT_EKPO TYPE STANDARD TABLE OF TY_EKKO INITIAL SIZE 0,
IT_EMPTYTAB TYPE STANDARD TABLE OF TY_EKKO INITIAL SIZE 0,
WA_EKKO TYPE TY_EKKO,
WA_EKPO TYPE TY_EKKO.
DATA: OK_CODE LIKE SY-UCOMM, "OK-Code
SAVE_OK LIKE SY-UCOMM.
*ALV data declarations
DATA: FIELDCATALOG TYPE LVC_T_FCAT WITH HEADER LINE.
DATA: GD_FIELDCAT TYPE LVC_T_FCAT,
GD_TAB_GROUP TYPE SLIS_T_SP_GROUP_ALV,
GD_LAYOUT TYPE SLIS_LAYOUT_ALV.
*ALVtree data declarations
CLASS CL_GUI_COLUMN_TREE DEFINITION LOAD.
CLASS CL_GUI_CFW DEFINITION LOAD.
DATA: GD_TREE TYPE REF TO CL_GUI_ALV_TREE,
GD_HIERARCHY_HEADER TYPE TREEV_HHDR,
GD_REPORT_TITLE TYPE SLIS_T_LISTHEADER,
GD_LOGO TYPE SDYDO_VALUE,
GD_VARIANT TYPE DISVARIANT.
*Create container for alv-tree
DATA: GD_TREE_CONTAINER_NAME(30) TYPE C,
GD_CUSTOM_CONTAINER TYPE REF TO CL_GUI_CUSTOM_CONTAINER.
*Includes
*INCLUDE ZDEMO_ALVTREEO01. "Screen PBO Modules
*INCLUDE ZDEMO_ALVTREEI01. "Screen PAI Modules
*INCLUDE ZDEMO_ALVTREEF01. "ABAP Subroutines(FORMS)
*Start-of-selection.
START-OF-SELECTION.
ALVtree setup data
PERFORM DATA_RETRIEVAL.
PERFORM BUILD_FIELDCATALOG.
PERFORM BUILD_LAYOUT.
PERFORM BUILD_HIERARCHY_HEADER CHANGING GD_HIERARCHY_HEADER.
PERFORM BUILD_REPORT_TITLE USING GD_REPORT_TITLE GD_LOGO.
PERFORM BUILD_VARIANT.
Display ALVtree report
CALL SCREEN 100.
*& Form data_retrieval
text
--> p1 text
<-- p2 text
FORM DATA_RETRIEVAL .
SELECT EBELN
UP TO 10 ROWS
FROM EKKO
INTO CORRESPONDING FIELDS OF TABLE IT_EKKO.
LOOP AT IT_EKKO INTO WA_EKKO.
SELECT EBELN EBELP STATU AEDAT MATNR MENGE MEINS NETPR PEINH
FROM EKPO
APPENDING TABLE IT_EKPO
WHERE EBELN EQ WA_EKKO-EBELN.
ENDLOOP.
ENDFORM. " data_retrieval
*& Form build_fieldcatalog
text
--> p1 text
<-- p2 text
FORM BUILD_FIELDCATALOG .
Please not there are a number of differences between the structure of
ALVtree fieldcatalogs and ALVgrid fieldcatalogs.
For example the field seltext_m is replace by scrtext_m in ALVtree.
FIELDCATALOG-FIELDNAME = 'EBELN'. "Field name in itab
FIELDCATALOG-SCRTEXT_M = 'Purchase Order'. "Column text
FIELDCATALOG-COL_POS = 0. "Column position
FIELDCATALOG-OUTPUTLEN = 15. "Column width
FIELDCATALOG-EMPHASIZE = 'X'. "Emphasize (X or SPACE)
FIELDCATALOG-KEY = 'X'. "Key Field? (X or SPACE)
fieldcatalog-do_sum = 'X'. "Sum Column?
fieldcatalog-no_zero = 'X'. "Don't display if zero
APPEND FIELDCATALOG TO GD_FIELDCAT.
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'EBELP'.
FIELDCATALOG-SCRTEXT_M = 'PO Iten'.
FIELDCATALOG-OUTPUTLEN = 15.
FIELDCATALOG-COL_POS = 1.
APPEND FIELDCATALOG TO GD_FIELDCAT..
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'STATU'.
FIELDCATALOG-SCRTEXT_M = 'Status'.
FIELDCATALOG-OUTPUTLEN = 15.
FIELDCATALOG-COL_POS = 2.
APPEND FIELDCATALOG TO GD_FIELDCAT..
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'AEDAT'.
FIELDCATALOG-SCRTEXT_M = 'Item change date'.
FIELDCATALOG-OUTPUTLEN = 15.
FIELDCATALOG-COL_POS = 3.
APPEND FIELDCATALOG TO GD_FIELDCAT..
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'MATNR'.
FIELDCATALOG-SCRTEXT_M = 'Material Number'.
FIELDCATALOG-OUTPUTLEN = 15.
FIELDCATALOG-COL_POS = 4.
APPEND FIELDCATALOG TO GD_FIELDCAT..
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'MENGE'.
FIELDCATALOG-SCRTEXT_M = 'PO quantity'.
FIELDCATALOG-OUTPUTLEN = 15.
FIELDCATALOG-COL_POS = 5.
APPEND FIELDCATALOG TO GD_FIELDCAT..
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'MEINS'.
FIELDCATALOG-SCRTEXT_M = 'Order Unit'.
FIELDCATALOG-OUTPUTLEN = 15.
FIELDCATALOG-COL_POS = 6.
APPEND FIELDCATALOG TO GD_FIELDCAT..
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'NETPR'.
FIELDCATALOG-SCRTEXT_M = 'Net Price'.
FIELDCATALOG-OUTPUTLEN = 15.
FIELDCATALOG-COL_POS = 7.
FIELDCATALOG-DATATYPE = 'CURR'.
APPEND FIELDCATALOG TO GD_FIELDCAT..
CLEAR FIELDCATALOG.
FIELDCATALOG-FIELDNAME = 'PEINH'.
FIELDCATALOG-SCRTEXT_M = 'Price Unit'.
FIELDCATALOG-OUTPUTLEN = 15.
FIELDCATALOG-COL_POS = 8.
APPEND FIELDCATALOG TO GD_FIELDCAT..
CLEAR FIELDCATALOG.
ENDFORM. " build_fieldcatalog
*& Form build_layout
text
--> p1 text
<-- p2 text
FORM BUILD_LAYOUT .
GD_LAYOUT-NO_INPUT = 'X'.
GD_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
GD_LAYOUT-TOTALS_TEXT = 'Totals'(201).
gd_layout-totals_only = 'X'.
gd_layout-f2code = 'DISP'. "Sets fcode for when double
"click(press f2)
gd_layout-zebra = 'X'.
gd_layout-group_change_edit = 'X'.
gd_layout-header_text = 'helllllo'
ENDFORM. " build_layout
*& Form build_hierarchy_header
text
<--P_GD_HIERARCHY_HEADER text
FORM BUILD_HIERARCHY_HEADER CHANGING
P_HIERARCHY_HEADER TYPE TREEV_HHDR.
P_HIERARCHY_HEADER-HEADING = 'Hierarchy Header'(013).
P_HIERARCHY_HEADER-TOOLTIP = 'This is the Hierarchy Header !'(014).
P_HIERARCHY_HEADER-WIDTH = 30.
P_HIERARCHY_HEADER-WIDTH_PIX = ''.
ENDFORM. " build_hierarchy_header
*& Form build_report_title
text
-->P_GD_REPORT_TITLE text
-->P_GD_LOGO text
FORM BUILD_REPORT_TITLE USING PT_REPORT_TITLE TYPE SLIS_T_LISTHEADER
P_GD_LOGO TYPE SDYDO_VALUE.
DATA: LS_LINE TYPE SLIS_LISTHEADER,
LD_DATE(10) TYPE C.
List Heading Line(TYPE H)
CLEAR LS_LINE.
LS_LINE-TYP = 'H'.
ls_line-key "Not Used For This Type(H)
LS_LINE-INFO = 'PO ALVTree Display'.
APPEND LS_LINE TO PT_REPORT_TITLE.
Status Line(TYPE S)
LD_DATE(2) = SY-DATUM+6(2).
LD_DATE+2(1) = '/'.
LD_DATE3(2) = SY-DATUM4(2).
LD_DATE+5(1) = '/'.
LD_DATE+6(4) = SY-DATUM(4).
LS_LINE-TYP = 'S'.
LS_LINE-KEY = 'Date'.
LS_LINE-INFO = LD_DATE.
APPEND LS_LINE TO PT_REPORT_TITLE.
Action Line(TYPE A)
CLEAR LS_LINE.
LS_LINE-TYP = 'A'.
CONCATENATE 'Report: ' SY-REPID INTO LS_LINE-INFO SEPARATED BY SPACE.
APPEND LS_LINE TO PT_REPORT_TITLE.
ENDFORM. " build_report_title
*& Form build_variant
text
--> p1 text
<-- p2 text
FORM BUILD_VARIANT .
Set repid for storing variants
GD_VARIANT-REPORT = SY-REPID.
ENDFORM. " build_variant
Reward points for useful Answers
Regards
Anji

Field Length issue in ALV Report

Hi,
I am using FM REUSE_ALV_GRID_DISPLAY to display few fields. Among them I have a field with length 200 characters text.
During ALV report display I am able to see only 128 characters, But when I download it and see the field, the it is showing complete text.
Can anybody help me out?
Thanks,
Ramakrishna

Check out the last answer of this post.
Re: ALV Grid Display - 255 characters
I found a SAP document called "Using ALV for list display.pdf" that says the following:
"Size of data fields: While the list-based ALVList can display only tables of up to 90 columns, the control-based ALVGrid and ALVFullscreen have the limitation of 128 characters per data cell."
Please make sure to award point for helpful answers and mark the post as solved. Thanks.
Regards,
Rich HEilman

Field length issue

Hello,
i have WAD report and a chart in it.In this chart we have dates being displayed on the X axis.i date format is 01/01/2008.
Our requirement is to have the date being displayed as
01-jan-2008.
For that i have written a customer exit variable .we have used a funfction module which passes the input as date and converts it in the required format.
FM input:01012008
FM output:01-jan-2008
i concatenated it to format 01jan2008.
But now whn i run the report it gives me the message that the length of field (ZVDAPRD-my variable name) is short
ZVDAPRD(customer exit) is made on the info obj Z_period which is of 8 length(date type). info object output length 10. reference characteristic 0date.
just to try i did format 01jan2008 to 01jan08,but still it gave me some wrong value like '1ja08" is invalid.
please help me to solve this!
also let me know if any other method to achive this.
thanks,
Pallavi

Hi Pallavi,
try to use text variables.
Processing by: Replacement Path
Replace Variable With: Name (Text)
regards Sven

Custom infotype - field length issue

Hi experts,
We have a requirement of keeping so much free text fields in the custom infotype. However, the system doesnu2019t allow having these many fields in the PS structure. We got the information from the error description as- The maximum length of PS structures for infotypes is 1000; this is the length of the general infotype header in bytes. Could you please suggest some way to solve this issue?
Thanks,
Rahul

Give a field and try to enter some decription for large text in that field .
Create a table for that field and give F4 for that .
Maintain the text in SO10 and call that text using read_text fn module .
Try this way

Sql*loader field length issue

so I'm loading a file and it's rejected a record where "field in data file exceeds maximum length" the record it's failing on has data length of 625 characters. I'm loading it into a table with a field type of varchar2(1024).
for the life of me, I can't figure out why it's failing. I've even gone and manually copy and pasted the rogue record into the table (via Toad) and it works fine, but I need it to load via SQL*loader.
there is no white space that i'm not counting. Can anyone suggest where to look next?

Hi,
Just change the problematic field in the control file as
load
field char(1000),
If you give the length in the control file, ur problem ll be solved.
- karthik

TCURR field TCURR_UKURS - field length is too short

Has ECC6 addressed the field length issue of 9 characters (5 decimals) in table TCURR field UKURS to cater for weak currencies, to avoid using ratios of 1000:1

Hi,
I don't see any issue. UKURS field has 9 characters, that's right; but, as you rightly mentioned, it should not pose any problem considering the ratio. Why ratio of 1000:1 is posing a problem for you?
Regards,
Eli

Field Catelog Issue for ALV Grid

Hi,
I have generated the ALV Dynamically based on the Date Range entered on the selection screen, now I am able to fill the values into the structure also, here my problem is date is like S858-spbup ( mm/yyyy format), what ever the values I have moved is S858-umwavwr(Currency values), now I want to sub total these values. Since my field catelog is date format that is why it is not doing subtotals.
code is
    gs_fc-seltext_l = date.
    gs_fc-seltext_m = date.
    gs_fc-seltext_s = date.
    gs_fc-ref_fieldname = 'umwavwr'.
    gs_fc-ref_tabname = 'S858'.
    gs_fc-do_sum = 'X'.
    gs_fc-outputlen = 20.
    APPEND gs_fc TO gt_fc.
it is doing subtotal but the issue is in ALV header it is not displaying like date (for example 06/2005),instead it is displaying the name as ref_fieldname text. How to resolve this issue. Please help me.
Thanks & Regards,
Sivaram Kandula

Hi Rich,
Thanks for your speedy reply. But in my case scenario is different.
if i remove the ref_fieldname = date means it is dumping bcz,
output is like this
suppose my input is 06/2005 to 08/2005
CSR   District 06/2005 07/2005 08/2005 totals
xxx   newyork    30.00    3.00   5.00    38.00
xxx   newyork    40.00    5.00   6.00    20.00
xxx              70.00    8.00 11.00    58.00
now I am able to display the output like this, but the problem here is i am unable to subtotal these, bcz my field catelog is date type that is why do_sum is not working, that is why I took ref_feield name as UMWAVWR and S858, it is subtotaling but I am unable to see the header like above, instead it is displaying like
CSR District   invoice:Cost invoice:Cost Invoice:cost tot
so please advise me how to proceed further.
Thanks & Regards,
Sivaram Kandula

How to control the output fields in ALV

Hi Pals,
I have a Z program which outputs around 400 characters length. It is working fine when we run in foreground(online).. But i have the problem with the length of the output of the report when i run in BACKGROUND mode. That is, only 255 characters are being displayed.
So, i have decided to supress some of the unwanted output fields being diplayed, so that the total output length becomes 255 characters.
How can i handle this situation in the ALV's?
Someone please send me some sample code.
Thanks in advance,
Ram.

Hi
   Better create the Layout Variants with the desired columns.
ALV is providing that functionality.
Use
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      is_variant = alv_variant
      i_save     = 'A'
    IMPORTING
      es_variant = alv_variant
    EXCEPTIONS
      not_found = 2.
Regards,
Kumar

ALV (Factory class) field length problem

Hi experts!
I build an ALV report using the Factory method. But I can't set the field length.
When I set the field length in a column attributes it doesn't change nothing
What is the problem?
My column attributes are like that:
TRY.
 lr_column ?= lr_columns->get_column( 'NAME1' ).
 lv_text_s = text-103.
 lv_text_m = text-103.
 lv_text_l = text-103.
 lr_column->set_long_text( text-103 ).
 lr_column->set_short_text( lv_text_s ).
 lr_column->set_medium_text( lv_text_m ).
 lr_column->set_output_length( 30 ) .
 lr_column->set_active_for_rep_interface( gc_default ).
 CATCH cx_salv_not_found.
ENDTRY.
Thanks forehead,
Dani

Hi,
In ur fieldcat populate the output length field.
CLEAR x_fieldcat.
x_fieldcat-fieldname = 'FLAG'.
x_fieldcat-seltext_l = 'Text' .
 x_fieldcat-outputlen = 30.
x_fieldcat-col_pos = 1.
APPEND x_fieldcat TO it_fieldcat.

How to slection screen fields in output of the report by using alv classe

hi all,
i want to get all the fields in the selection screen to be displayed in the output layout.i am developing report by using alv grid classes can any one help me.
answers are rewarded

Hello
u first place some dictionary input/output fields in your screen and
below that u place ur custom control,
so what ever input u are giving in those fields , u seelct data accordingly,
for example.
in screen there is one icon 'dictionary/program fields, click that and give some table , suppose u want to extract data from kna1 table using kunnr, select kunnr and press enter, then along withn cursor u get one frame, take that on to screen and place it ,
now in the program write
tables: kna1.
select * from kna1 into it_kna1 where kunnr = kna1-kunnr.
now u get the data into it_kna1.
it will work , try this.
bye.

Editable field with F4 help in alv tree output using cl_gui_alv_tree

HI
i need Editable field with F4 help in alv tree output using cl_gui_alv_tree
Regards
Naresh

Hi Naresh,
Pass the field catalog with the additional parameter (ls_fcat-edit = 'X'.).
for F4 help if the data element have the search help it automatically will come. other wise include the additional parameter in the field catalog (ls_fcat-F4AVAILABL = 'X')
Reward if found helpful.
Regards,
Boobalan Suburaj

ALV OUTPUT FIELD LEANTH

HI EXPERTS,
IN ALV OUTPUT FIELD LENTH IS MAX 128?
IN MY REQUIRMENT THE FIELD HAS 500 CHARTERS
Moderator Message: So where is the question? And why type in CAPITAL letters? Do some research before you post a question here. Also, please read the Rules of Engagement of this forum
Edited by: kishan P on Apr 1, 2011 10:10 AM

Hi,
Linking F4 Help to Fields
For the last section, we will deal with linking F4 help to fields. It is easy. As usual, define, implement and register the event onf4 at proper places in your code. For F4 help, you must register the fields whose F4 request will trigger the onf4 event. For this you must prepare a table of type LVC_T_F4 and register this table using the method register_f4_for_fields. While preparing table you must include a line for each field which will trigger F4 event. For each field in the structure;
Pass the fieldname to FIELDNAME
Set REGISTER to make the field registered,
Set GETBEFORE to provide field content transport before F4 in editable mode
Set CHNGEAFTER to make the data changed after F4 in editable mode.
Preparing table for the fields to be registered to trigger F4 event
DATA: lt_f4 TYPE lvc_t_f4 WITH HEADER LINE .
lt_f4-fieldname = 'PRICE'.
lt_f4-register = 'X' .
lt_f4-getbefore = 'X' .
APPEND lt_f4 .
CALL METHOD gr_alvgrid->register_f4_for_fields
EXPORTING
it_f4 = lt_f4[] .
A sample onf4 method implementation
METHOD handle_on_f1 .
PERFORM f4_help USING e_fieldname es_row_no .
er_event_data->m_event_handled = 'X' .
Again, we set the attribute er_event_data->m_event_handled to prevent further processing of standard F4 help.
Regards,
Ranjit Thakur.
Please Mark The Helpful Answer.
ENDMETHOD .

Regardig Field Length in ALV

I am trying to set the field length in ALV
so i wrote
<fs_fcat>-outputlen = 15.
and in layout...
wa_layout-colwidth_optimize = space . tried by commenting this statment also
But it doesnt show any effect
" in fact field length is depend on field lable and on its content..."
so plz help me some buddy.....
Edited by: anurodh_t on Sep 29, 2010 3:58 PM

Hello,
Try updating the description fields of the Fieldcat records prior to defining the outputlen field. Depending on the way you are implementing your ALV, try updating the following fields:
scrtext_l
scrtext_m
scrtext_s
or
seltext_l
seltext_m
seltext_s
Best regards,
Mário Espinheira

Field output trancated regardless of the field length assigned

i have assigned 1000 characters to the output field in the output structure. Now in the report output, the field only displays upto 128 characters, it doesnt go beyond that. what could be the cause of this. Even when i put it on debug mode, this field is reading data by concatenating diffrent fields, but the concatenation goes only up to 128 characters, after that it does not concatenate further.

hi,
this is how my code reads:
data: t_descript like tline-tdline occurs 0,
      wa_descript like tline-tdline.
data: begin of itab occurs 0.
        include structure zhap_s_alv_reporting_pms_rej.
data: end of itab.
-------zhap_s_alv_reporting_pms_rej - notes = 1000 char
loop at t_descript into wa_descript.
        if use_flag = 'X'.
          if not wa_descript is initial.
            concatenate itab-notes wa_descript
                                       into itab-notes separated by space.
          endif.
        endif.
        if wa_descript = 'Below are the comments'.
          use_flag = 'X'.
        endif.
      endloop.
t_descript returns 6 lines of (67, 71, 33, 74, 76, 37 characters)
Edited by: Lorato Ludo Kenosi on Mar 14, 2011 12:17 PM
Edited by: Lorato Ludo Kenosi on Mar 14, 2011 12:20 PM

Output field length issue in OO ALV

Similar Messages

Maybe you are looking for