Cleaning spool requests - report RSPO1041

[dmp-dmagi_cml]

Hi experts,

We're using SRM 5.5 and we've scheduled the reports

- BBP_GET_STATUS_2 ( every 2 minutes)

- CLEAN_REQREQ_UP

As a consequence, in the SPOOL we are having many requests.

In order to delete the spool requests, we have one job for the report RSPO1041, which is defined to delete spool requests from report bbp_get_status_2. In addition, we have 2 more jobs to clean the spool, using the same report RSPO1041, but with a generic variant.

However, those jobs are not being successfully cleaning the spool, as the spool requests are not being deleted.

So, my question is, is there any reason for the report bbp_get_status_2 generate spool requests?

And if it is really necessary, is there any other way to clean the spool? Or there is any other reason to the RSPO1041 is not cleaning the spool requests as it should?

Many thanks.

Best regards,

Andreia Nascimento

[Former Member · Accepted solution]

- BBP_GET_STATUS_2 ( every 2 minutes)
- CLEAN_REQREQ_UP

Normally CLEAN_REQREQ_UP doesn't generate any spools, BBP_GET_STATUS_2 does and it does have the reason to generate spool as you would want a comprehensive report on the synchronization between SRM and R/3 documents.

In order to delete the spool requests, we have one job for the report RSPO1041, which is defined to delete spool requests from report bbp_get_status_2. In addition, we have 2 more jobs to clean the spool, using the same report RSPO1041, but with a generic variant.

Why having multiple jobs for the same purpose? I would just schedule one job that manage the cleaning of spools with a desired variant for report RSPO1041. And there should not be a reason for it not to be cleaning up accordingly, unless the job itself is not running into the status "finished". Having multiple jobs involving report RSPO1041 with different variants also increases the complexity for your tracking of its effectiveness.

[dmp-dmagi_cml · Accepted solution]

Hi Jay Yang,

Thanks for your reply! The reason why the admin has scheduled multiple jobs for the same report is because the spool requests are not being deleted and once bbp_get_status_2 is running every 2 minutes, the spool requests donu2019t stop increasing.

In fact, the status of all spool requests is u201Cwaitingu201D and the output requests have the information u201CFrontend unavailableu201D.

Any idea? And there is there the possibility to the bbp_get_status_2 report doesnu2019t generate spool requests?

Thanks!!

Best regards,

Andreia Nascimento

[Former Member · Accepted solution]

And there is there the possibility to the bbp_get_status_2 report doesnu2019t generate spool requests?

You could make a copy of BBP_GET_STATUS_2 and modify it to remove all "write" statements. But you have to be sure you won't be in need of a log some time in the future.

As to report RSPO1041 doesn't do the spool cleaning well, I suggest that you try RSPO0041 and see if this one does the job.