Search performance problem in the SAP Records management

[] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []

Related:

  1. Performance issues during element deletion via BAPIs & APIsSymptom The deletion of documents using the BAPI ‘BAPI_RECORD_DELETEELEMENTS’ takes...
  2. BWA 7.00: Analyzing write performanceSymptom You find that indexing in SAP NetWeaver BW Accelerator...
  3. AS/400: Performance settings for R/3Symptom AS/400: Setting system values for R/3 and BW operation...
  4. Upgrade Performance Problem mit ErweiterungenSymptom Sie beobachten beim Update eines ERP Systems auf ERP2005...
  5. SPPFP: Performance during selection (background mode)Symptom You want to use the report RSPPFPROCESS (transaction SPPFP)...
  6. DB2/390: Performance of the updateSymptom The response time during transactions which use the asynchronous...
  7. DB2-z/OS: Performance Problems with DB2 V8/V9 REOPT(ONCE)Symptom This note will list all known SQL statements that...
  8. DB2-z/OS: Bad performance in method READ_SR_ACTIVITYSymptom DB2 is not using multiple index operation for the...

Symptom

When the customer performs a search on an element type, the search takes lot of time to return the result.
Other terms

Performance,Search,Record,Case,Element type,Document,LOIO Search,Combined Search,Service provider space,SPS_ID
Reason and Prerequisites

The reason for the slow performance is, when a content model is made to host many service provider space (SPS) or Element types then the content model size can grow considerably. When a user performs a direct search on a element type without any search parameter in the search dialog then the records management performs Combined Search both on LOIO and PHIO tables. Since the size of the content model is very huge it takes time to read the records and filter the records based on RMS_ID, SPS_ID etc and build the final result.
Solution

The solution is perform a LOIO search instead of combined search when the user does not enter any attribute in the search dialog. The reason being the SPS_ID is a LOIO attribute and it is good to start the search from LOIO directly.
Also please implement the attached correction instruction to solve the problem.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment