Solution : https://service.sap.com/sap/support/notes/52539 (SAP Service marketplace login required)
Summary :
The SAP Note addresses an issue with the secondary index COEP__1 which is configured with excessively numerous fields (16 in total) and an excessive character count (127), leading to bloating and performance inefficiencies during COEP accesses. The index's oversized design causes maintenance overhead without providing substantial performance gains. For optimizing, a detailed custom analysis is recommended to define a more efficient index based on specific customer data patterns. Proposed default indexes are smaller, potentially more efficient configurations. Execution of all changes should be initially tested in a non-production environment, and appropriate adjustments should be made during system upgrades.
Key words :
additional key words coep, symptom secondary index coep__1, prerequisites secondary index coep__1, native db system directly, adding field gjahr perio, mandt objnr perio gjahr, mandt objnr kstar, db utility se14, standard sap release, create view view
Related Notes :
| 213098 | Index switch for table COEP |
| 44341 | Customer-specific indexes |
| 36407 | Long response times for line item documents |