Skip to Content

unable to tcode LT22 without transaction time out

Hi All,

Users are unable to run LT22 without transaction timing out. They were running this with the parameters in the attachment previously with no issue now it times out. After running for about an hour following message, "work process re-started, session terminated". Anyone have any idea why it is being timed out. Please advice.

Thanks,

Haritha

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Aug 07, 2013 at 10:00 AM

    Hi Haritha,

    In most the cases, this is due to the more number of entries in the tables LTAK & LTAP from which system is trying to fetch the data.

    Could you please use the tCode LT23 instead of LT22 with the same search criteria as because LT23 selects via LTAK first and then LTAP.

    Also, please refer the SAP note 534135 in SMP which could be helpful to optimize the performance of the LT22 tCode.

    Thanks & Regards,

    Balaji

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 07, 2013 at 11:33 AM

    Hi Haritha,

    Just another idea, please ask your Basis-guys if the statistics-update is running daily, if not, ask them to run this, and especially make sure that this statistics-update will run against those tables you are using when calling this LT22 transaction (check via SM50 during the run you will see which tables are being called).

    If this is not helping, then try to create an extra index on those tables.

    Maybe you (and Basis guys) need to analyze the used SQL-statement first, to check the execution-plan.

    I hope this will help you.

    Regards,

    Andre

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Haritha P

      Hi Haritha,

      Does your LTAK table have indexes as well?

      Try to check in the execution plan, is this query using your LTAK-index or "TABLE ACCESS FULL LTAK"?

      If there is and index(es) and your query still doesn't use this, maybe you can try to drop and rebuild those indexes on LTAK. Assuming that those tables are getting statistics update as well.

      I hope this will help you.

      Regards,

      Andre