Time Out Error in Modify statement

[abapdeveloper20]

Hi ,

While executing the following statement in standard program, timeout error occurs.

Program SAPLSBAL_DB_INTERNAL

Include LSBAL_DB_INTERNALU02

Row 72

Module type (FUNCTION)

Module Name BAL_DB_INTERNAL_NO_UPDATE_TASK

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

• update all tables specified

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

IF NOT c_s_db_tables-baldat_u IS INITIAL.

MODIFY baldat CLIENT SPECIFIED FROM TABLE c_s_db_tables-baldat_u.

ENDIF.

Internal Table c_s_db_tables-baldat_u

MANDANT RELID LOG_HANDLE BLOCK SRTF2 CLUSTR CLUSTD

120 AL FYsqIm1SE6hX00002WF87m 112 0 512 hfdfgdfgdfdgd........

120 AL FYsqIm1SE6hX00002WF87m 112 1 512 ...

120 AL FYsqIm1SE6hX00002WF87m 112 2 512

120 AL FYsqIm1SE6hX00002WF87m 112 3 512

120 AL FYsqIm1SE6hX00002WF87m 112 4 370

CLUSTD having values like the one below FF060201020280003431303300000000218F0000121F9D02A37CF3F98DE2C8E2784D777B3CA3A0687E787E705919E3181F38B867EC9E6E8903C6C6369293187B00FB149265132271C0594780C4011C58

Please help.

[Former Member]

How big are the tables BAL* ?

If you need this report a.s.a.p. you might want to consider to change parameter rdisp/max_wprun_time for a little while untile the report has finished or you run it in background (if possible)

In the long run though, I recommend you think about archiving -> here: object BC_SBAL to reduce the number of lines in those tables.

[abapdeveloper20]

Thanks for your reply..

actually the table BALDAT is having 544.405 entries and Backround option is not possible because it is related to appraisal templates via PHAP_ADMIN transaction.

but my doubt is "Modify statement will change the content of the standard table as per the internal table entries" . So, if internal table entries are matched with the standard table then it should change/modify those directly..

also Archiving is good idea. Thanks.

[Former Member]

I am not a developper, so I cannot answer your question about the modify-directly-on-db-issue - but look at the FM BAL_DB_INTERNAL_NO_UPDATE_TASK - as the shorttext says: Application-Log: Database: Internal: Protocolls without Update Task - maybe it has to do with the way this modify is processed?

Just so. It will not help you - of course you can open a Call with SAP on this special function and see if they come up with an explanation and/or a correction - in the meantime, consider my proposals as possible workarounds.

Another thought: if you are so interested in that FM, why not post a question in the Abap-performance forum - there's a tough group of guys over there who might be interested to study that FM.

[abapdeveloper20]

Thanks