Short dump after AC_FLUSH_CALL

[Former Member]

Hi all,

I'm using Netweaver 04 and I've developed a report that displays a dynpro containing a dynamic document and it auto-refreshes itself through the CL_GUI_TIMER class.

After a period of correct working the report crashes with a short dump about the wrong exit of AC_FLUSH_CALL function module (CL_GUI_CFW->FLUSH method). sy-subrc = 2.

Can you help me? Thanks in advance.

Angelo

[Former Member]

Hi,

U might find some info in SAP Note : 180304

Regards,

GSR.

Symptom

Calls are made to a control. To make sure that this is executed on the frontend, a call of the framework method CL_GUI_CFW=>FLUSH prior to the end of the program is performed. However the calls were not executed on the frontend.

Additional key words

Control Framework, flush, CL_GUI_CFW=>FLUSH, CL_GUI_CFW=UPDATE_VIEW, automation queue

Cause and prerequisites

On the call of the framework method CL_GUI_CFW=>FLUSH only a combination for the frontend is performed if methond calls in the automation queue have return values. Otherwise, it is assumed that the communication with the frontend can also take place at the end of the PBO at the time of the automatic flush. If you want to force the communication, call the CL_GUI_CFW=>UPDATE_VIEW instead of CL_GUI_CFW=>FLUSH.

Solution

To make sure that a flush at the end of the program still transports data in the automation queue to the frontend, use the CL_GUI_CFW=>UPDATE_VIEW method instead of CL_GUI_CFW=>FLUSH.

Source code corrections

[Former Member]

Hi Srinivas, thanks!

Now I'm not using the flush or update_view methods in my code, I'll try to add the second one at the end of the PBO code.

Regards,

Angelo

[Former Member]

Hi all,

I've added the CL_GUI_CFW=>UPDATE_VIEW call at the end of PBO, but I still receive the short dump after a (even long) period of correct working.

Any other odea?

Thanks.

Angelo

[Former Member]

can you give more details from the short dump that you are getting....

I believe you have more controls on the front end is that right ? when refreshing with the timer...are you recreating some objects ?

try freeing unused objects ?

Thanks,

Renjith

[Former Member]

Hi Renjith,

I receive the short dump inside the update_view, after the flush operation.

1

2 METHOD UPDATE_VIEW.

3 * ...

4 CALL FUNCTION 'AC_SYSTEM_FLUSH'

5 exporting CALLED_BY_SYSTEM = called_by_system

6 EXCEPTIONS

7 CNTL_SYSTEM_ERROR = 1

8 CNTL_ERROR = 2

9 OTHERS = 3.

10

11 CASE SY-SUBRC.

12 WHEN 0.

13 WHEN 1. "// system_error

14 RAISE CNTL_SYSTEM_ERROR.

15 WHEN 2. "// method_call_error

>>>>> RAISE CNTL_ERROR.

17 WHEN 3. "// property_set_error

18 RAISE CNTL_ERROR.

19 WHEN 4. "// property_get_error

20 RAISE CNTL_ERROR.

21 WHEN OTHERS.

22 RAISE CNTL_ERROR.

23 ENDCASE.

24

25 ENDMETHOD.

In my dynpro there are 2 data TYPE REF TO cl_dd_document and TYPE REF TO cl_gui_custom_container. I create these objects only the first time and I use the display_document method only for one of these at the end of each PBO. DO I need to create these objects each time?

Thanks.

Angelo

[Former Member]

Hi ,

When you are calling the method "display_document" of CL_DD_DOCUMENT what are you passing for the parameter REUSE_CONTROL ?

try passing "X" to this parameter, for the 2nd call onwards....pass blank first time....

Thanks,

Renjith

[Former Member]

Hi,

I already use 'X' for that parameter to reuse it. I need this value to combine the container and the auto-refresh function.

Thanks,

Angelo

[Former Member]

My monitoring application accesses each second a DB table to check if its contents are changed and dispay a particular record on the dynpro.

FILL_HEADER is fixed and FILL_VALUES can change.

This is most of PBO code:

SET PF-STATUS 'STATUS1100'.

SET TITLEBAR 'TITLE1100'.

CLEAR flag.

IF first = 'X'. " prima display

CLEAR: i_text, is_ma_data.

REFRESH: i_text, is_ma_data.

CREATE OBJECT head_cont

EXPORTING container_name = top_screen.

CREATE OBJECT values_cont

EXPORTING container_name = values.

CREATE OBJECT fill_header

EXPORTING no_margins = 'X'.

CREATE OBJECT fill_values

EXPORTING no_margins = 'X'.

CALL METHOD fill_header->initialize_document.

PERFORM fill_field_names.

CALL METHOD fill_header->merge_document.

CALL METHOD fill_header->display_document

EXPORTING

parent = head_cont

container = 'FILL_HEADER'

reuse_control = 'X'

reuse_registration = 'X'.

first = ' '.

ENDIF.

...

CALL METHOD fill_values->initialize_document

EXPORTING

background_color = bg_color.

PERFORM fill_field_values.

• merge document

CALL METHOD fill_values->merge_document.

CALL METHOD fill_values->display_document

EXPORTING

parent = values_cont

container = 'FILL_VALUES'

reuse_control = 'X'

reuse_registration = 'X'.

ENDIF.

• refresh

CREATE OBJECT gui_timer.

SET HANDLER event_handler->on_finished FOR gui_timer.

gui_timer->interval = timeout.

CALL METHOD gui_timer->run.

CALL METHOD cl_gui_cfw=>update_view.

Thanks.

Angelo

[Former Member]

I have the same issue. Did you ever find out the problem???

[Former Member]

Hi, same isuue here... any help?

Regards.

[Former Member]

HI all ,

same issue ne help???

[Former Member]

Dear All,

I faced the same problem.

The solution is to upgrade your SAP GUI version/ patch to the latest one.

Kind regards,

Martin

[Former Member]

this error is related to the GUI components..

Some of the components are missing or the version is older..

Yes, try to get the latest GUI version and then try..

[kartikrajag]

I faced same short dump in my custom z program ( ALV Tree display using CL_GUI_LIST_TREE) ; in my case the root cause was a blank value passed for a field (treev_ntab-isfolder ) in node table, populating value 'X' for all nodes fixed the issue.

[michal_sporszil]

That solved my problem! Many thanks!