If you have performance issue for transaction TPM1 - Valuation, you may consider the following points to improve it.
1) Update database statistics for related tables starting with:
SLDT_
TRCT_
TRGT_
TRILT_
TRLT_
TRLIT_
TRPRT_
TRACT_
DIFT_POS_IDENT
You can check in transaction SM50 which table is used.
2) Consider soft modification note 1122623. The code may has been included in the system version, but it has to be activated as described in the long text of the note. Futhermore, there have to be done index changes which might be a bit time consuming to activate. The note should improve the performance in the position management transactions, but please read the long text of the note carefully.
3) You may set parallel processing control for TPM1. The number of task 10 is a SAP default setting. You may set it to be 10 or higher in case you have many positions to process. Customizing path:
Financial Supply Chain Management
Treasury and Risk Management
Transaction Manager
General Settings
-> Parallel Processing Control
4) If the most time is spent during update of the derived business transactions, it is sufficient to use the offline processing for the derived business transactions. This will mean that derived business transactions will firstly stay as "not current"/"not updated". Afterwards the TPM27 has to be executed to update them. This will save lot of runtime in TPM1 and the TPM27 supports parallel processing as well.
The customizing is :
Financial Supply Chain Management
Treasury and Risk Management
Transaction Manager
General Settings
Accounting
Derived Business Transactions
Control of Processing of Derived Business Transactions
Alternative: If you don't want to have offline setting, you can use the update period for derived business transaction and set it to several months (1 or 2) in:
Financial Supply Chain Management
Treasury and Risk Management
Transaction Manager
General Settings
Accounting
Organization
Assign Accounting Codes and Valuation Areas
This will mean that you update the derived business transactions automatically, but only given number of months in the future. This will save the runtime as well. Every time derived flows are generated it will check the customizing take the current date plus the period and generate flows. If you later need the flows afterwards you have to execute TPM19 to generate the following flows. You can plan TPM19 as a regular job then.
These two proposals should speed up the TPM1 processing. The second one is a long term solution. The first one is interim to speed up TPM1.
Additionaly, when you encounter performance issue for other functionalities, e.g. TBB1, you may check the above points as well.
Related notes:
2053772 - Poor performance in TPM1 when selecting OTC transactions
2023161 - SAC: valuation reset not considered in Amortization log II
2010667 - Securities: system logic improvement II
1952964 - Enhancement of the log during parallel processing
1836890 - TPM1: Performance improvement of securities
1821679 - TPM1: Performance improvement of OTC deal selection
1777912 - Performance optimization for TPM1
