Description

When installing and maintaining a SAP SRM system, the analyst has to create periodic jobs executing the reports responsible for updating document status:

  • CLEAN_REQREQ_UP
  • BBP_GET_STATUS_2
  • BBP_SC_AUTO_RETRANSFER

I have been working as a Support Engineer for a few years and I have seen several issues related to these settings. For example, it is pretty usual to see table BBP_DOCUMENT_TAB in production with hundreds (or thousands) of entries.

Not maintaining schedule jobs for the status reports causes different issues, Shopping Carts not showing all the related documents, wrong statistical values in Purchase Orders, Confirmations being created for Purchase Orders fully confirmed, etc.

There are a several steps to evaluate the “healthiness” of the system regarding this. I have created the Z_STATUS_CLEAN_TOOL to automatically run this analysis and show some of alerts and issues linked to the proper documentation provided by SAP.

For continuous improvement of this tool, please install it in your development systems and test it by yourselves. Your feedback about this report is highly appreciated!

Environment

It is recommended to run this report in SRM 7.0 and above.

Download

SAP Note 2233889 – Diagnostics of status reports and BBP_DOCUMENT_TAB

Screenshots

Z_STATUS.png

See Also

SAP Help about status reports

SAP Note 1499352 – SRM Transfer: Redesign, bug fixes

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply