topic Time Out Error in Modify statement in Application Development and Automation Discussions

Time Out Error in Modify statement

abapdeveloper20 — Wed, 28 Apr 2010 10:32:29 GMT

Hi ,

While executing the following statement in standard program, timeout error occurs. The situation occurs during when some appraisals documents are changed/deleted via PHAP_ADMIN transaction.

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 is having these 5 entries. These 5 entries are actually present in the table with exact primary keys.

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.

Re: Time Out Error in Modify statement

abapdeveloper20 — Wed, 28 Apr 2010 12:18:16 GMT

Any inputs please.

Re: Time Out Error in Modify statement

Former Member — Wed, 28 Apr 2010 13:18:57 GMT

time out can always occur if you program is long running, and then it will stop somewhere randomly.

A modify with 5 entries in the internal table can not need long.

Try to run a SQL trace and stop it after 10min, or check the SM50 and start the debugger randomly, where do you end.

Come back when you know which statement actually causes the problem.

Siegfried

Re: Time Out Error in Modify statement

ravi_lanjewar — Fri, 21 May 2010 11:52:18 GMT

Hi,

Some time this happend due to lock entries. That program inserting 5 entries but some of entries having lock.

That create problem while executive modify or update.

Check table name exist in SM12 transaction. Delete that entries using sm12 transaction and execute the program.

Rgds

Ravi Lanjewar

Re: Time Out Error in Modify statement

Former Member — Fri, 21 May 2010 13:23:30 GMT

This is a standard SAP program - search for notes or send it to OSS.

Rob