Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 9129

Re: Increase performance when using MKPF

$
0
0

If you have no other selection criteria than posting date, there is not much option, once you check index (BUD) activation.

 

You could

  • Only extract required fields (not *)
  • Try to parallelize extraction, as it is the first table extracted, you can only split date range in smaller ranges and execute those in parallel tasks thru RFC enabled FM (doc link)

 

Othersolutionsin the field ofBasis, Database management orIT architecture, not Abap...

 

 

If you also require selection on MSEG movement type (BWART) either

  • Use a JOIN between both tables
  • Implement (if required) note 1516684 - MKPF fields added to MSEG - Performance optimization, and now only select data from MSEG (as MKPF-BUDAT = MSEG-BUDAT_MKPF)
  • Use the two options if some MKPF fields are missing in new MSEG, but you can now test with criteria on any of the two tables for common fields
  • Please, don't use a FOR ALL ENTRIES on MSEG with result of MKPF extraction (if performance were already bad for single MKPF, I refuseto considerthiscase...

 

Regards,

Raymond


Viewing all articles
Browse latest Browse all 9129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>