topic Re: T-CODE LT22 when executed takes long time ? in Application Development and Automation Discussions

T-CODE LT22 when executed takes long time ?

Former Member — Fri, 10 Apr 2009 10:20:10 GMT

Hi,

Currently we are facing a issue . In transaction LT22, depending on selection criteria, the report will time out. Need to know why if the ''source'' and ''dest'' buttons are not checked, the program takes so long. Also, if ''all TO items'' is checked, the program also takes too long.

Please guide me how to improve the performance of the program.

Thanks in advance.

Vengal Rao

Re: T-CODE LT22 when executed takes long time ?

Former Member — Fri, 10 Apr 2009 17:59:18 GMT

Hi Vengalrao,

Since when has your SAP system being running production? If your answer is a long time (> 4 years or so), then you might want to consider archiving your SAP installation.

If you have millions of transfer orders in your SAP tables, then the program would but naturally take for ever to retrieve all the TO items.

Based on your IT policies, you might want to look into archiving which will improve the performance of your WM and other day to day transactions also.

Also, consult your DB administrator to check the system through the monitoring transactions like ST** etc.

Oh yeah, almost forgot - if you want to view the contents now (and cant wait for archiving and cant resolve the performance issue ASAP) then try running your LT22 in Background. Instead of F8 click F9 and schedule a job and come back after some time to view the job results in SM37.

Cheers,

Adi

Re: T-CODE LT22 when executed takes long time ?

Former Member — Fri, 17 Apr 2009 07:45:38 GMT

check this [977674|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=977674] and this [534135|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=534135]

Rhea.

Re: T-CODE LT22 when executed takes long time ?

Former Member — Fri, 17 Apr 2009 10:08:12 GMT

Thanks Rhea,

I am looking into the SAP NOTES suggested by you.

If any doubts shall write back to you.

Thanks,

Vengal Rao.

Re: T-CODE LT22 when executed takes long time ?

Former Member — Fri, 17 Apr 2009 12:25:09 GMT

Hi Rhea

I reviewed both the SAP notes ( and also referred the other notes like 170183,977674) related to performance improvement of LT22, and as per note no 977674, the checked the SAP BASIS RELEASE and it is lower than RELEASE 6.4, so I can implement as per the note and as per the note I have to refer to sap note no 534135, and the said note does not clearly says exactly what I have to implement.

Please help me in this matter.

Thanks and regards,

Vengal rao

Re: T-CODE LT22 when executed takes long time ?

Former Member — Mon, 20 Apr 2009 07:52:23 GMT

Implement Note 360044 before you implement this note 534135.

download the note 534135 in snote transaction it has the corrections in [SAPDBT3L|javascript:displayCorr('0120061532','0000426882','1','LIMU','REPS','SAPDBT3L')] and [RLLT2200|javascript:displayCorr('0120061532','0000426882','1','LIMU','REPS','RLLT2200')]

Basis people can help you if u never did it before, Only thing is you have to check whether this note is applicable to your current system check your latest support packs.

Rhea.

Re: T-CODE LT22 when executed takes long time ?

Former Member — Mon, 20 Apr 2009 14:57:28 GMT

Hi Rhea,

I checked with my Basis team and found the Basis Release is 620 , so the related SAP notes cannot be implemented, due to which the table index is not being considered.

Please refer to the LDB Program T3L and I noticed that the max package size for internal table for LTAP Table is 300 and as the above table has millions of records , I think the select statement in T3L program is called thousands of times , involving enormous time and also at the delaration stage the internal table is restricted to 300 entries only.

Can this be the reason. please guide.

Thanks and Regards,

Vengal Rao.

Re: T-CODE LT22 when executed takes long time ?

Former Member — Thu, 29 Jul 2010 14:06:56 GMT

This issue has been forwarded to Basis guys as the release is not upto mark.