Solution : https://service.sap.com/sap/support/notes/17617 (Connexion à SAP Service Marketplace requise)
Résumé :
Long response times identified for matchcode F4 help stem from improper matchcode ID usage and indexing inefficacies. For non-transparent matchcodes (types "A", "P", "S"), the absence of first field specification in matchcode dialog requires full table reads, slowing the system. For transparent matchcodes (type "I"), poor response times arise from missing database indices for specified table fields, also necessitating full table reads. Solutions involve duplicating matchcode IDs for non-transparent types, with correct field sequencing and activation, and creating necessary database indices for transparent types via SE11 Transaction and DB utility functions, ensuring field arrangement follows client fields in multi-table environments.
Mots Clés :
search field directly afterthe client field, symptom long response times, client dependent tables, main search field, end user specifies, function db utility, additional key words, matchcode id consists, -transparent matchcode id, transparent matchcode id
Notes associées :
| 27122 | Converting customer matchcode IDs to transparent IDs |