How to improve performace?

[Former Member]

Is there a way to improve the performance of mass run (e.g., FPY1, FPMA, FP04M)?

Is there a cookbook out there?

Thanks gurus!

[Former Member]

Hello,

To improve the performance, I would suggest to split the customers by creating variant for all the mass programs.

Coming to the cookbook, I do not think there is one... Here is the list of cookbooks available till now

Billing Cookbooks <ISU>

Abrechnung von Hinterschaltungen 

Abrechnung von Leitungs- und Transformatorverlusten 

Anlagengruppen 

Billing Procedure in Brazil 

Billing Procedure in Brazil 

Billing Serial Switchings 

Billing Transmission Losses and Power Transformer Losses 

Dynamic Period Control 

Dynamische Periodensteuerung 

IS-U/CO-PA Integration 

IS-U/CO-PA-Integration 

Installation Groups 

Master Agreements in Sales Process f. Comm. & Ind. Customers 

Payment Scheme 

Rahmenverträge im Verkaufsprozess f. Gewerbe u. Sonderkunden 

Zahlungsschema 

FICA cookbooks

Cookbook Settlement Control 

Collective Bill 

Sammelrechnung 

Cookbook Verrechnungssteuerung 

Präsentation Verrechungssteuerung 

Forderungsabgabe an externe Inkassobüros 

Submission of Receivables to External Collection Agencies 

Reconnecting a Utility Installation (IS-U) 

Wiederinbetriebnahme einer Versorgungsanlage (IS-U) 

Some of them are in German Language to translate them to English.

Hope this helps

Rgds

Rajendra

[RonnyF · Accepted solution]

Hello,

above transactions are mass activities. That means this functionalities have to work with a lot of data. To lower the runtime I recommend you to use more than one job. If you start transaction fpy1 with four jobs then the program needs only a quarter of time (for instance 4 hours instead 16 hours). Reason is the parallel data processing. But for this you have to create a variant with less four intervals. I recommend you that the intervals should be equal.

Best regards,

Ronny

[Former Member]

Hi Blumtain,

What you wan't to know is how to best tune you MA.

Very well, you can't tune without same "real execution" with real data and if possible in the production system.

In order to, get the best performance from a MA, every interval run time has to be between 5 a 10 minutes, this is why you need to "test" in prodution and tune it after a couple of executions.

AAL!