topic Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY in Application Development and Automation Discussions

Problem with SET_TABLE_FOR_FIRST_DISPLAY

michael_fallenbchel — Tue, 03 Nov 2009 12:07:01 GMT

Hi experts,

I've got a problem I can't explain:

I call the class SET_TABLE_FOR_FIRST_DISPLAY to set my ALV.

  CALL METHOD gs_container-o_grid->set_table_for_first_display
    EXPORTING
      is_variant      = g_variant  " Übergabe wegen Speichern Layout
      i_save          = g_save     " Varianten-Speicher-Modi (User/Global/Beides)
      is_layout       = gt_layout  " Übergabe für Layout
    CHANGING
      it_fieldcatalog = gt_fieldcat
      it_outtab       = output_tab.

IN our development-system everything works perfect, but in the live-system, the ALV is empty. I debugged (live and development system), so I can say the variants are exactly the same...

What can be the problem? I don't understand what is going wrong here - the only difference between the systems is the name

Thanks in advance

Michael

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

Former Member — Tue, 03 Nov 2009 12:12:26 GMT

where are u calling the screen for display, before or after calling this method?

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

Former Member — Tue, 03 Nov 2009 12:13:05 GMT

Hi,

Can you check if the screen in your live system has the container in SE51.

It could be some screen problem in live system.

Also can you check if output_Tab has data.

Regards,

Subhashini

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

Former Member — Tue, 03 Nov 2009 12:14:51 GMT


only difference between the systems is the name

and data as well !

Is output_tab populated in live system ?

Regards

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

michael_fallenbchel — Tue, 03 Nov 2009 12:19:54 GMT

@ vijetasap

logic is this:

PROCESS BEFORE OUTPUT.
  MODULE status_1000.
  MODULE init_1000.
  MODULE create_alv_1000.

First, the status, then filling the table and at last I create the ALV - so, the calling of the method is the last step before output.

@ Subhashini K

The dynpro exists in SE51

@ Subhashini K & Subhashini K

All 5 variants (g_variant, g_save, g_layout, gt_fieldcat & output_tab) have exatctly the same data.

Other ideas?

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

Former Member — Tue, 03 Nov 2009 12:27:00 GMT

Hi,

You can debug inside the method SET_TABLE_FOR_DISPLAY in both development and production system.

Some condition or some difference will be there.

That may give some idea how to proceed.

Regards,

Subhashini

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

agnihotro_sinha2 — Tue, 03 Nov 2009 12:55:47 GMT

hi,

dint get why you are using "gs_container-o_grid", i mean shouldnt it be only "o_grid" and then call the method?

i think you are using the container object as a table which has o_grid as a field?? is it right. so basically you are generating object dynamically. am i right??

ags.

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

michael_fallenbchel — Tue, 03 Nov 2009 12:59:25 GMT

I transported the whole package from the development in the productive system onve more.

So I know it MUST be the same in both system (in the coding).

Nothing happened - I also checked in our integration-system /(between productive and development) - here everything works perfect.

I asked our baasis-administrator if he had changed something since last thuersday (this day everything works fine).

The only the he changed was an reboot of the system.

Can this be a problem?

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

michael_fallenbchel — Tue, 03 Nov 2009 13:07:02 GMT

@ ags

You're absolutly right, I'm doing everything dynamically.

I made a function which calles the method...I know this works fine (I use this function in different programs - but since last thursday something happened I absolutly can't understand - because I don't change anything there)...

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

agnihotro_sinha2 — Tue, 03 Nov 2009 13:08:25 GMT

hi,

can you just pass the PARAMETER "i_consistency_check" to this method and check the return value in debugging mode??

I think it should tell you if something is really wrong technically.

also did you goto the screen and check all the prperties of the screen like 'vertical' and ' horizontal' resizing??

ags.

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

agnihotro_sinha2 — Tue, 03 Nov 2009 13:13:19 GMT

I know this is irritating to ask you to check your code since its working on one system and not on another, but since you are doing it dynamically can you just let me know few things:

1: are you checking whether the object is initial or not??

2: inside the METHOD call , just check if the 'ME' object is refering to the same 'O_GRID'

3: could you plz paste a larger snippet of your code for better understanding?

ags.

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

michael_fallenbchel — Tue, 03 Nov 2009 13:36:50 GMT

Hi ags,

I will help you to understand:

1. sure, the object is not initial

2. I will check later

3. I will show you some coding:

calling the function:

  CALL FUNCTION 'ZZ_CREATE_ALV'
  EXPORTING
   container_name       = 'ALV'
    tab_name             = 'GT_ZLVS'
*     ALV_ID               = 1
  CHANGING
    output_tab           = gt_zlvs.

container name is the name of the container on the dynpro

tab_name is the name of the tab (as string) - need it for dynamically searching in customizing-tabs for settings like which buttons to show, setting the fieldcat etc.

alv_id is the id of the ALV - need htis if I use more than one ALV on one dynpro

output_tab is the tab which I want to show in the ALV

function itself:

FUNCTION zz_create_alv.
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*"  IMPORTING
*"     REFERENCE(CONTAINER_NAME) TYPE  C DEFAULT 'ALV'
*"     REFERENCE(TAB_NAME) TYPE  UDTAB
*"     REFERENCE(ALV_ID) TYPE  INTEGER DEFAULT 1
*"  CHANGING
*"     REFERENCE(OUTPUT_TAB) TYPE  ANY TABLE
*"----------------------------------------------------------------------

  IF alv_id IS INITIAL.
    g_alv_id = 1.
  ELSE.
    g_alv_id = alv_id.
  ENDIF.
  gt_tabname = tab_name.

*  CREATE DATA gref LIKE output_tab.
*  ASSIGN gref->* TO <itab>.
*
*  LOOP AT output_tab ASSIGNING <wa>.
*    APPEND <wa> TO <itab>.
*  ENDLOOP.

* Layout lesen
  PERFORM get_layout.

get_layout -> if the ALV should be in edit mode, user should save layouts...

  READ TABLE gt_container INTO gs_container WITH KEY alv_id = g_alv_id.
  IF sy-subrc = 0.
    IF gs_container-o_container IS INITIAL.
      CREATE OBJECT gs_container-o_container
        EXPORTING
          container_name = container_name.
      CREATE OBJECT gs_container-o_grid
        EXPORTING
          i_parent = gs_container-o_container.
      MODIFY TABLE gt_container FROM gs_container.
    ENDIF.
* ============================================
    CREATE DATA gs_container-itab LIKE output_tab.
    ASSIGN gs_container-itab->* TO <itab>.

    LOOP AT output_tab ASSIGNING <wa>.
      APPEND <wa> TO <itab>.
    ENDLOOP.

    CREATE OBJECT gs_container-ref_alv_events.
* Handler für Reaktion auf Änderungen, nur im Editmode aktiv
    IF gt_layout-edit_mode = 'X'.
*    SET HANDLER ref_alv_events->handle_data_changed FOR grid.
      SET HANDLER gs_container-ref_alv_events->handle_data_changed FOR gs_container-o_grid.
    ENDIF.
* Toolbar
*  SET HANDLER ref_alv_events->toolbar FOR grid.
    SET HANDLER gs_container-ref_alv_events->toolbar FOR gs_container-o_grid.

    MODIFY gt_container INDEX sy-tabix FROM gs_container.
* ============================================
  ELSE.
    CLEAR gs_container.
* ============================================
    CREATE DATA gs_container-itab LIKE output_tab.
    ASSIGN gs_container-itab->* TO <itab>.

    LOOP AT output_tab ASSIGNING <wa>.
      APPEND <wa> TO <itab>.
    ENDLOOP.
* ============================================

    CREATE OBJECT gs_container-o_container
      EXPORTING
        container_name = container_name.
    CREATE OBJECT gs_container-o_grid
      EXPORTING
        i_parent = gs_container-o_container.
    gs_container-alv_id = g_alv_id.

    CREATE OBJECT gs_container-ref_alv_events.
* Handler für Reaktion auf Änderungen, nur im Editmode aktiv
    IF gt_layout-edit_mode = 'X'.
*    SET HANDLER ref_alv_events->handle_data_changed FOR grid.
      SET HANDLER gs_container-ref_alv_events->handle_data_changed FOR gs_container-o_grid.
    ENDIF.
* Toolbar
*  SET HANDLER ref_alv_events->toolbar FOR grid.
    SET HANDLER gs_container-ref_alv_events->toolbar FOR gs_container-o_grid.

    APPEND gs_container TO gt_container.
  ENDIF.

* Felder der internen Tabelle lesen
  PERFORM get_fieldcat USING output_tab
                    CHANGING gt_fields.

get_fieldcat -> reading the fileds of the table

* Feldkatalog für ALV schreiben
  PERFORM set_fieldcat.

* set the fieldcat

Edit-Event extra registrieren, nur wenn im Edit-Modus

IF gt_layout-edit_mode = 'X'.

CALL METHOD grid->register_edit_event

CALL METHOD gs_container-o_grid->register_edit_event

EXPORTING

i_event_id = cl_gui_alv_grid=>mc_evt_enter.

Edit-Mode aktiv setzen
CALL METHOD grid->set_ready_for_input

CALL METHOD gs_container-o_grid->set_ready_for_input

EXPORTING

i_ready_for_input = 1.

ENDIF.

g_variant-report = sy-repid.

g_variant-username = sy-uname.

ALV ausgeben
CALL METHOD grid->set_table_for_first_display

CALL METHOD gs_container-o_grid->set_table_for_first_display

EXPORTING

is_variant = g_variant " Übergabe wegen Speichern Layout

i_save = g_save " Varianten-Speicher-Modi (User/Global/Beides)

is_layout = gt_layout " Übergabe für Layout

CHANGING

it_fieldcatalog = gt_fieldcat

it_outtab = output_tab.

Fokus auf das Grid setzen

CALL METHOD cl_gui_alv_grid=>set_focus
EXPORTING
control = grid
EXCEPTIONS
cntl_error = 1
cntl_system_error = 2
OTHERS = 3.

Flush

CALL METHOD cl_gui_cfw=>flush.

IF g_doubleclick IS NOT INITIAL.

set event handler

SET HANDLER lcl_events=>on_double_click FOR gs_container-o_grid.

ENDIF.

ENDFUNCTION.

That's it - hope this will help...

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

agnihotro_sinha2 — Tue, 03 Nov 2009 13:53:40 GMT

okie........

everything seems to be done very properly..

just a doubt whether you are using the 'refresh_table_display' method call.. since it seems you have commented 'FLUSH' call...

other than that presently i hv very less clue on the issue

ags.

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

michael_fallenbchel — Tue, 03 Nov 2009 13:57:04 GMT

Sorry, I don't knwo why it's shown so "supid"

OK, I don't use the flush - at the beginning I thought I have to use it - but now it's not in use anymore...

As you can see it's nothing other than making the container etc in the program itself.

I'm just wondering - is there a system-parameter than can be setted after rebooting the system?

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

rainer_hbenthal — Tue, 03 Nov 2009 14:44:41 GMT

Did you do the [ALV consistency check|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/15961] [original link is broken] [original link is broken] [original link is broken]; ?

And please have a look at the further markup possibilities on the right side of the screen if you want to post code....

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

Sm1tje — Tue, 03 Nov 2009 14:49:07 GMT

In addition to Rainer;

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

michael_fallenbchel — Tue, 03 Nov 2009 14:50:41 GMT

I tried this check, with the follwing messages:

Field-catalog - Correct

Layout:

The field CNTR_DDID does not exist in the output table

The field COL_DDID does not exist in the output table

The field FIELDNAME does not exist in the output table

The field GRID_DDID does not exist in the output table

The field ROW_DDID does not exist in the output table

Field LANGUAGE has a wrong value LANG in FCAT-DATATYPE

Sort Sequence, Filter, Field Groups and Output Table:

Output table contains no entries (?)

Variant

No inconsistencies were found

And sure, I tried to work with the markup possibilities - but something went wrong...sorry for that

@ Micky Oestreich - OK, that would be the problem

Edited by: Michael Fallenbüchel on Nov 3, 2009 3:51 PM

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

Former Member — Tue, 03 Nov 2009 15:28:24 GMT

try editing the post with the code snippet...place hard return after { }




Data: foo type i.

Nevermind....I see the char limit

Edited by: Ryan Quackenboss on Nov 3, 2009 10:28 AM

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

Former Member — Tue, 03 Nov 2009 15:51:46 GMT

Do you have any layouts created in your PRD system, perhaps marked as the "default layout" that has somehow become invalid?

Just something more to check...

-Mark

Re: Problem with SET_TABLE_FOR_FIRST_DISPLAY

Former Member — Tue, 03 Nov 2009 16:22:44 GMT

Hello Michael,

Could you please delete the screen once and recreate once again.

and also make sure that you use REFRESH_TABLE_DISPLAY~

After REFRESH you can also use pointer->CHECK_CHANGED_DATA

Regards

Dinesh