Solution : https://service.sap.com/sap/support/notes/1009808 (SAP Service marketplace login required)
Summary :
When archiving materials in SAP, issues arise due to reads from OBJK or EQUI tables during write and deletion phases, even after implementing SAP Notes 566984, 605760, and 634197. This typically happens when there are many entries in these tables, but few have values in the MATNR field, which is crucial for archiving. The preferred database index does not focus on the MATNR field due to its sparse population. To resolve this, apply a correction that includes database hints for Oracle and DB2 databases, ensuring the usage of the correct index by updating database statistics and verifying the existence and activity of specific indexes.
Key words :
correction includes database hints, correct database index, equi table index, suitable index, equi table, database access, database system, database statistics, oracle database, db2 database
Related Notes :
| 1524912 | MM_MATNR: Performance problems during existence checks 2 |
| 998448 | MM_MATNR: Performance problems when reading table AFIH |
| 770471 | MM_MATNR: Performance problems reading AFVC |
| 634197 | MM_MATNR: Performance improvement for Note 605760 |
| 605760 | MM_MATNR: Performance problems after Note 566984 |
| 566984 | MM_MATNR: missing checks for PM data |
| 512031 | MM_MATNR: Long runtime when reading table EQUZ |
| 162034 | DB2/390: Database hints in Open SQL |
| 130480 | Database Hints in Open SQL for Oracle |
| 129385 | Database hints in Open SQL |