Running time of FPVB transaction

[Former Member]

We are facing one problem. Running time of FPVB transaction has been increased after migration. In 2009, it used to take 1 hr and now it takes 2 hrs. What could be possibilities of this increase in time?

[Former Member]

Hi

I would suggest the use of parallelization of the dunning activity. The processing time of the transaction FPVB depends mostly on the dunning activities that are triggered from the dunning procedure. Usualy is the dunning proposal that is more time consuming than dunning run.

I am sure you will see improvement when you use parallelization.

Let me know how it goes.

regards,

David

[Former Member]

Thanks David.. Parallization is Parallelization is already in place. Main concern is why there is increase in time. Basically why it is taking more time this year compared to last year.

Regards,

Minal Nigade

[AmlanBanerjee]

Hi Minal,

There can be two possible reasons as to why the processing time for the dunning run has increased over a year-

(a) Increase in the volume of transactions subsequently leading to the database growth.

(b) New enhancements being plugged into the user exits (Event 300, 303 etc) for dunning which are not retrieving the information from the database in a correct manner.

Point (a)

Delete the FI-CA mass activity runs

Tables FKKDIPOTMP and FKKDIPOTMPCOUNT contains entries with run information of all mass activities. It is normally recommended to only keep about 3 months (or less) of these at a time. You need to discuss with the client on what a reasonable retention times should be.

It is possible to delete entries of these tables by scheduling the SAP reports-

u2022 RFKK_MASS_ACT_PARAMETER_HIDE

u2022 RFKK_MASS_ACT_PARAMETER_DELETE

You need to run them on one after another starting with RFKK_MASS_ACT_PARAMETER_HIDE.

Note-The run identification of the relevant mass activities is also deleted. In SAP note 355685 you'll find more information about the named reports. RFKK_MASS_ACT_PARAMETER_DELETE deletes the old mass activities parameters.

Point (b)

Check whether the enhancements (if any) has been coded in such a way that it is taking longer time to retrieve the data from the database tables.

Hope it helps.....

Thanks,

Amlan

[william_eastman]

Minal:

Check your parallelization variants - FICA variants as used by dunning and other processes do not get refreshed such that the objects might after awhile become disproportionately allocated to individual intervals, usually the last one in the list. You can solve this by re-generating the intervals or by creating new ones.

regards,

bill.