Home › Discussions › Questions & Answers › Achieving EBS Report Version Control for Concurrent Programs with Blitz Report

Achieving EBS Report Version Control for Concurrent Programs with Blitz Report

Avatar photoCustomer Questions & Answers 7 replies

As development standards evolve, we frequently modify the underlying SQL queries embedded within our custom concurrent programs. However, managing this lifecycle through decentralized file storage or relying solely on outdated LDT file backups for auditing has become chaotic and non-compliant, providing a poor audit trail. We desperately need an integrated Version Control for Concurrent Programs that resides natively within EBS, offering a clear history of SQL code changes, including who made the modification and the associated descriptive comments, improving our overall EBS governance strategy.

7 replies

  • Support Enginatics

    This need highlights a critical deficiency addressed directly by Blitz Report, which integrates robust version control directly into the EBS application framework. Every time a query is modified within the Blitz Report setup form, the system automatically assigns a new version number and mandates recording comprehensive audit comments, ensuring a clear, centralized history.

  • Avatar photoCustomer

    That sounds far superior to manual file management. If a team member mistakenly pushes a flawed SQL change, can we easily revert to a previous working version using this built-in mechanism?

  • Support Enginatics

    Yes, the centralized repository maintains all previous versions of your report SQLs, allowing developers to quickly review the version history and restore a preceding working copy when necessary, significantly mitigating risks associated with continuous change.

  • Avatar photoCustomer

    Does this system track changes only for reports created within Blitz Report, or can it extend version control capabilities to our existing standard or BI Publisher concurrent programs?

  • Support Enginatics

    While Blitz Report manages versions for reports developed or imported into its environment, it also features import tools that allow you to bring in the SQL definitions from existing BI Publisher and Discoverer reports. Once imported, those critical queries immediately benefit from the robust versioning and auditing features built into the Blitz framework.

  • Avatar photoCustomer

    Does maintaining this version history require us to manually register dozens of concurrent programs, adding administrative overhead for every new report or version iteration?

  • Support Enginatics

    No, this is a core efficiency feature: regardless of the number of reports or versions managed, there is only a single registered concurrent program called Blitz Report that executes all report requests. This drastically reduces administrative maintenance for your IT team.

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