Solution : https://service.sap.com/sap/support/notes/551133 (SAP Service marketplace login required)
Summary :
Extended runtimes have been observed when selecting notifications by status even when combined with other criteria, such, as date. This issue stems from the inability to effectively use status information for notification retrieval. Transactions related to IW28, IW29, and other specified transactions experience this inefficiency. The advised solution is the implementation of an advance correction. Users are discouraged from manually applying this fix, instead recommended to import the corresponding support package after ensuring the prerequisite conditions, including the creation of specific system messages and the setup of new data elements and program adjustments, are met to ensure system integrity.
Key words :
reference type i_first_qmnum type qmnum i_last_qmnum type qmnum, length field label 10 phase 15 notification phase 20 notification phase 15 notification phase, process 4 completed 5 deletion flag, system responsethe transaction terminates, short text 1 open 2 postponed 3, sap standard production program, message short text 'notification &1, 'notification processing phase', add field phase, inconsistency phase / status management'
Related Notes :
| 1554293 | Poor performance in EAM lists due to missing phase |
| 1269950 | Maintenance/service notification: Phase not set correctly |
| 983752 | BAPI notification list: selection with phase |
| 846210 | PM/CS notification: Phase set incorrectly |
| 557557 | Phase + selection via costs in claim reports |
| 554474 | Inconsistencies notification phase / status management |
| 393393 | Performance improvement of the operation list |