Purpose
This page is created to identify the root cause of BBP_PDVIEW_IAP view performance problems and provides further recommendations to improve system performance.
Overview
BBP_PDVIEW_IAP performance issues can be identified via trace analysis and also in TIME_OUT dumps which can caused by:
- obsolete DB statistics,
- amount of data,
- improper usage of the functionality,
- missing code corrections (SAP Notes).
Usually these kind of issues are occurring in Include LBBP_PDF58, which is related SRM search functionalities like: Sourcing Cockpit search, POWL search, Advanced Search, etc..
Technical Background
Database view BBP_PDVIEW_IAP join tables BBP_PDIGP and CRMD_ORDERADM_I.
The size of these item tables generally affect SMR system performance. Huge amount of item level data is a possible performance bottleneck.
Update DB statistics
Always make sure that the database statistics (tables BBP_PDIGP and CRMD_ORDERADM_I) are up-to-date. With an obsolete database statistics the access path will not optimal. For DB specific information you will find detailed information in the following SAP Notes/Documentation:
SAP Note 588668 - FAQ: Database statistics
SAP Note 927882 - FAQ: SAP MaxDB UPDATE STATISTIC
SAP Note 1764611 - FAQ: SAP Sybase ASE Update Statistics
SAP Note 434495 - DB6: Maintaining table statistics via transaction DB13
SAP Documentation - Database Administration Guide (DB2)
Amount of data
Generally "amount of data" problems can caused by improper archiving in SRM system. The amount of data (table size) can reduced with regular archiving. For more details about SAP SRM recommendations read SAP Wiki page SRM Archiving Process.
Archiving Objects for Table wiki page describes which archiving objects are related to BBP_PDIGP and CRMD_ORDERADM_I tables.
Improper usage of the functionality can also affect the amount the data. You will find detailed information about the affected functionalities in the following Wiki pages:
Expected search parameter
SELECT on BBP_PDVIEW_IAP table without any restriction can also caused by search functionality errors even user searched with criteria. In some cases the used criteria is not mapped properly during the search. To identify the affected codepart (which will help in SAP Note Search) use SRM debugging guides:
Further performance improvement - index tables
Index tables are help to improve the system performance when you create or display a large document lists. If these tables are not in use, the system needs to read unnecessarily large volumes of data in staggered database accesses. In case of SRM search (Advanced Search, SOCO, POWL) is important to make sure that the indexes are used properly. For more information, check SAP Wiki page Index Tables.
Related Content
Related Documents
SAP SCN Wiki - Sourcing Cockpit Performance
SAP SCN Wiki - POWL Performance
SAP SCN Wiki - Advanced Search Performance
SAP SCN Wiki - Index Tables
SAP Documentation - Database Administration Guide (DB2)
Related SAP Notes/KBAs
SAP Note 588668 - FAQ: Database statistics
SAP Note 927882 - FAQ: SAP MaxDB UPDATE STATISTIC
SAP Note 1764611 - FAQ: SAP Sybase ASE Update Statistics
SAP Note 434495 - DB6: Maintaining table statistics via transaction DB13