APO - SNP Alert Macros running too slow

[Former Member]

Hi,

We have created alert macros which run for next 27 weeks for 38000 Product-Location Combinations. They are running too slow.

We are deleting alerts externally using program /sapapo/amon_reorg and then running this macro with "ADD" . This macro slows down once it starts filling up alert table with 100,000 records. What are the best practices for writing the macro so that it runs fast ?.

Thanks.

[Former Member]

Is it necessary to write all the alerts? What I mean is, do you filter the results when you view them through the Alert Monitor?

If your alert profile has a minimum threshold set for an alert type, then you can read this threshold in the macro and only write alerts that fall below the threshold.

e.g.

Step: Get Threshold Values : ( 1 Iterations :Initial;Initial )

Action Box: Get Threshold Value

LAYOUTVARIABLE_SET( 'Alert_Thresh' ;

ALERT_PROFILE_THRESH( SDP_ALERT_PROFILE' ; '4100' ; 'I' ) )

Where SDP_ALERT_PROFILE is the profile that contain sthe minimum threshold you want to use and 4100 is the alert type. The I is for information, can use either W for Warning or E for Error as well.

Then use the variable Alert_Thresh to check if your value falls below this, only then write the alert.

Regards

Ian

[Former Member]

Hi,

We are on APO 4.1, All the notes which Harish outlined are for APO 3.0.

Main issue is the background job is running 3 alert macros and it runs for 8 hours on 38000 Location-Product Combinations . I want to cut down the time of the job. Displaying in Alert Monitor is not the issue. Also there is no threshold value ( for eg. alert when Days of Supply below 14 days . ) .

Are there any good notes for APO 4.1 which can help improve the performance of the background jobs ?.

This are all database alerts and we are running on separate dataview with just 27 weeks of buckets.

Thanks.

Message was edited by:

Ketan Doshi

[Former Member]

Hi

What I meant was, if you filter the writing of alerts the performance increases as most of the time is taken writing to the database in the macro. So the less writes you perform the faster the macro executes.

Regards

Ian

[Former Member]

and one more

500063 - Overview of performance notes for the Alert Monitor

[somnath_manna]

Assuming you are executing this alert macros as a background job, see if you can create a separate data view containing only the relevant keyfigures (those required in the macro computation) and the relevant time horizon (only 27 weeks - no additional future buckets).

That should improve the performance of the job. But if you are seeing slowdown of macro performance after filling up /SAPAPO/AM_ALERT table - you can check with your BASIS consultant to finetune the table parameters (not sure what all).

Thanks,

Somnath

[Former Member]

Ketan

Is it necessary to run the Alerts for all the 27buckets. Am not sure of your business procecess or the kind of alerts(if you have a leadtime of procurement of 27weeks then yhes it makes sense to get an alert for the 28th week )

but I would use alerts only for the nearby buckets. Again if you have a frozen horizon of 4weeks there is no point generating alerts for stock shortage for the 2nd week.

Are these Dynamic or DB alerts?

Are these notes run in interactive planning or in the background?

here is a note(if you ahve not seen it before) that might help you

521639 - Generation of DB Alerts in Background

there is a a whole host of related notes in the bottom of that note