Home › Discussions › Questions & Answers › Reducing Administrative Overhead with Blitz Report

Reducing Administrative Overhead with Blitz Report

Avatar photoCustomer Questions & Answers 9 replies

As a System Administrator, manually registering every new custom report as a Concurrent Program, defining its executable, parameters, and request group membership is a major bottleneck. When we create a report using Blitz Report’s simple SQL interface, do we completely bypass this manual registration overhead?

9 replies

  • Support Enginatics

    Yes, this is a core efficiency feature of Blitz Report. A key benefit is the ability to create new operational reports quickly without the hassle of registering new concurrent programs and reports. The report runs immediately through the concurrent requests mechanism, and you do not need to register the report in system admin.

  • So, how is the report execution actually managed by the Concurrent Manager if it’s not a registered program?

  • Support Enginatics

    Blitz Report is implemented as an add-on that utilizes the application foundation functions, including the Concurrent Request framework. Instead of registering each individual report as a unique program, Blitz Report leverages its own highly optimized execution engine which is already integrated, allowing it to interpret the saved SQL definition and execute it as a concurrent request seamlessly.

  • Does this apply equally to reports created from scratch via SQL, and reports imported from legacy tools like Discoverer or BI Publisher?

  • Support Enginatics

    It applies universally. Whether you create a new report in minutes or import a complex BI Publisher report complete with parameters , the key administrative benefit holds true: there are no new concurrent programs to register per report. This dramatically simplifies the maintenance workload for IT teams.

  • What other administrative functions are automated besides registration?

  • Support Enginatics

    In addition to zero concurrent program registration, Blitz Report handles version control automatically for every report definition, preventing duplication and maintaining a stable codebase with audit history. This is essential for maintaining control over custom SQL assets.

  • If a DBA needs to quickly check patch status using a SQL function like AD_PATCH.IS_PATCH_APPLIED, they can define and save that as a report without registration?

  • Support Enginatics

    Precisely. Defining and saving that utility report within Blitz Report allows the DBA to execute it directly from the Forms interface without needing database login or OAM navigation , showcasing the simplicity Blitz Report brings to DBA tasks.

  • You must be logged in to reply to this post.