Home Discussions Questions & Answers Identifying Unused Reports: Leveraging Blitz Report Usage Statistics for EBS Cleanup

Identifying Unused Reports: Leveraging Blitz Report Usage Statistics for EBS Cleanup

Avatar photoCustomer October 15, 2025 at 12:19 pm

Our EBS environment is cluttered with hundreds of custom reports, many of which were built years ago and appear redundant or unused, increasing our maintenance overhead and technical debt. We are starting a major EBS cleanup initiative and need a systematic, reliable method for Identifying Unused Reports, specifically those that haven’t been run in the last two years. Manually tracking invocation logs or searching through file archives is impractical. What tool can provide comprehensive reporting usage statistics to inform our purging decisions accurately?

Viewing 6 reply threads
  • Author
    Replies
    • Support October 15, 2025 at 4:09 pm  

      For robust usage analysis, particularly in environments facing a Discoverer replacement challenge, tools with built-in metadata reporting are invaluable. Blitz Report is fully equipped with specialized diagnostic reports like the ‘DIS Worksheet Execution History’ designed specifically for tracking report invocation statistics, even if the reports originated elsewhere.

    • Avatar photoCustomer October 15, 2025 at 8:46 pm  

      How does the ‘DIS Worksheet Execution History’ report function if our reports were created natively within the EBS Concurrent Manager framework rather than imported from Discoverer?

    • Support October 16, 2025 at 12:33 am  

      While initially designed for Discoverer migration planning, similar principles apply to any report managed by Blitz Report. Since all Blitz Reports run through the standard concurrent request framework, their execution history, including the last execution date and user, is logged, enabling accurate filtering to find unused assets.

    • Avatar photoCustomer October 16, 2025 at 2:37 am  

      Can we filter these usage reports easily, for instance, to isolate reports that have genuinely never been run versus those that were simply aged out over a long period, helping prioritize our cleanup efforts to reduce technical debt?

    • Support October 16, 2025 at 6:10 am  

      Yes, the diagnostic reports allow filtering based on parameters like the ‘last execution date’ or ‘access count’. This helps IT leads easily segment and prioritize their list of potentially obsolete reports, providing data-driven insights for the EBS cleanup project.

    • Avatar photoCustomer October 16, 2025 at 8:40 am  

      Once identified, how simple is it to retire these unused reports from the Blitz Report repository to declutter the system for end-users?

    • Support October 16, 2025 at 10:45 am  

      The Blitz Report development form provides a centralized interface for managing the report life cycle. Once a report is identified for retirement using the usage statistics, a developer can simply disable or remove the report entry, instantly removing it from user navigators without requiring complex administrative actions or database manipulation.

Viewing 6 reply threads
  • You must be logged in to reply to this post.

Login with: