BDCPV optimization
You are using change pointers for master data distribution to external system. Then for you it’s no secret how large can become BDCPV table. If you are running program RBDMIDOC (transaction BD21) as a background job, you know how long time often it takes for program to find specific change pointers for your IDoc message type.
Below I compiled couple of good advices taken from SAP Marketplace:
1) Deactivating change pointer MEREP_DELTABO at BD50 (Note 1376267)
The change pointer for ‘MEREP_DELTABO’ is active at BD50 transaction even though no SAP mobile solution is used in the ERP system
2) Improve change pointer reading by implementing correction code (Note 863744)
During the generation of IDocs from change pointers for message categories of the basic types MATMAS01, MATMAS02, MATMAS03, MATMAS04 or MATMAS05 (according to the release you are using), the change pointers are not read using a corresponding index that exists for improving the performance.
3) For change pointer reading improvement SAP will use new table starting from BASIS 701 (Note 1244159)
Table BDCP2 is used to read the change pointers instead of using function module
4) If you don’t want to wait when your system BASIS will be upgraded to 701, migrate to BDCP2 manually (Note 305462)
5) Also there are other suggestions made by SAP towards optimization (Note 513454)
I) Deactivate change pointers for message types that don’t need them using transaction BD61
II) Reorganize obsolete and processed change pointers periodically using transaction BD22
Hope this helps!
