Under ADABAS or MSSQL, read accesses to the tables COSP and COSS can take a long time. The performance of many CO transactions (such as allocations, overhead calculation, or settlement) and of reporting is poor.
Under certain conditions, when the above tables are accessed records are not found even though they are on the database. This of course has fatal effects in the various transactions. For example, in activity price determination the cost centers that are planned still show a value of zero.
Inappropriate database selection / ADABAS or MSSQL error
If you are working under ADABAS refer to Note 34165. Read errors should not occur any longer after implementation.
For performance improvements, change the source code as follows if you work under ADABAS or MSSQL.
Additional key words
Runtime
DBTUNE, ADATUNE
Transactions: KO88, CJ88, CO88, KK88, KSPI, KSU5, KSV5, KSW5, KSUB,
KSVB, KSII, KP06
No comments:
Post a Comment