Please someone help me on this
Whlie executing an archiving job (Preprocessing, Write, or Delete) allocates very much memory and has a long runtime.
kindly share your valuable views here.
Thanks in advance.
High memory consumption and long runtime can of course have many reasons. One easy solution, which is highly recommented, is to execute archiving batch jobs with a system user having T_TM_ALL authorization. This special authorization is deactivating any authorization checks in SAPTM layer, and so avoids superfluous and expensive data retrieval and memory allocation. Since archiving jobs are in general executed by system users (no dialog users), which have all TM authorizations to be able to archive SAP TM documents, there is no risk to completely turn off the SAP TM authorization check for such users.
Sign up for STechies
All the site contents are Copyright © www.stechies.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies. The site www.stechies.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity. Information used on this site is at your own risk.
The content on this site may not be reproduced or redistributed without the express written permission of
www.stechies.com or the content authors.