/SAPAPO/AM_ALERT table has over 2 million entries

[AA3]

Hi

We are currently scheduling a deletion program SAPAPO/AMON_REORG on a regular basis included in our process chain ABAP process type for database alert deletion. The next step after this is execution of Macros. The Variant for this program has type SD (APO Demand and Supply) and the Day interval is empty.

Currently our process chain has failed with a short dump, which relates to "No Space to increase Internal table" , BASIS intervened and they say that the Memory parameters are fine and set up according to Standards.

However when I saw the SAPAPO/AM_ALERT database table it has over 2million entries.

Question 1: I would like to find if the database alerts are actually getting deleted ? is there a way to confirm this

Question 2 : How do I avoid this Memory relevant short dump, are there any settings needed for config or Indexing on the relevant Tables ?

[Former Member · Accepted solution]

AAL,

If you have 2M records, something is probably not right. You are either generating a huge number of alerts every day, or your reorg job is not agressive enough. Or, as you suspect, the reorg step is not completing.

Question 1: I would like to find if the database alerts are actually getting deleted ? is there a way to confirm this?

Sure. SE16 > /SAPAPO/AM_ALERT > click Number of Entries. Execute. Write down the results. Run the PC. Repeat the SE16 task. Compare the results.

For an immediate solution, I would manually start deleting the oldest records. The interactive transaction code is the same as the program: /SAPAPO/AMON_REORG. You can either run your variant (this will show you the effectivity of your variant as well) or just manually start selecting all records before a certain date.

Best Regards,

DB49

[AA3]

Hi

Thanks for the response. There is an Option of Simulate Check Box , Is it required to be checked or unchecked.

[Former Member]

123,

Checking this box means the program will create a list, but not actually delete the records. Leave it blank if you wish to actually delete.

Of course, like any program you have never run before, you should try it in your test system first.

Best Regards,

DB49

[AA3]

Hi,

Even when I try to select it with the SIMULATE option , it is throwing a SHORT DUMP (ST22, log gives the same memory error for internal table). Selection option is for SD application , 4000 Alert Object type and 101 as Alert types

Can you please explain the options below , I would like to find out if the options below need to be set?

Absolute time

Relative time

I also came across another program /SAPAPO/AMODAL_DELETE , will that help me to delete the alerts for a single day ?

[Former Member]

Hi,

We are experiencing the same issue, as the deletion program do not consider the selection parameters. So it retrieves all the entries irrespective of the time you mention in the selection screen. We have raised a message to SAP explaining the details and they are working on it.

Will let you know if we get any solution.

Thanks,

Krishna

[Former Member]

AAL,

I have never tried to delete alerts under the condition where there are several million entries, so I cannot speak from memory. I had a similar problem once with BackOrder Processing logs, which caused me all kinds of grief to reorg....

If you have an old version of APO (3.1 and previous) there are some notes that may be helpful. Search on OSS under /SAPAPO/AMON_REORG. Particularly http://service.sap.com/sap/support/notes/513553. These problems have mostly been corrected in later versions.

As far as your question, the two 'times' you asked about refer to the record creation date. Records that are older than the absolute date/time will be deleted. Relative Date time refer to 'difference from today'. I would start with a very old value under 'absolute', say around the date that your first alerts were created. To avoid session timeout issues, I would create a variant which selected only the oldest records, and then run in background. I would try first to select only one alert monitor application, preferably one that has the smallest number of records, to start. Once these are fully reorg'ed, move to another A/M application.

For internal table storage, there are settings that your Basis Team can make, that may improve the situation. Print the error log and take it to your Basis team.

Best Regards,

DB49

[AA3]

We are currently on SCM 7.0 , and the logs refer to only one application (SD)- APO Supply and Demand planning

more than 95% of the entries are of Application Obj type = 4000 and

Application type - 101 (Target stock exceded) with priority = Error

. Is it good option to delete with /SAPAPO/AMODAL_DELETE ?

[Former Member]

AAl,

. Is it good option to delete with /SAPAPO/AMODAL_DELETE ?

I don't know. The version I am currently working on is SCM 5.0. . /SAPAPO/AMODAL_DELETE did not appear until 7.0.

I would try it in a test environment. If .you run /SAPAPO/AMODAL_DELETE and you still get a dump, make sure you have reviewed the contents of https://service.sap.com/sap/support/notes/1400234 before giving up.

Best Regards,

DB49