Skip to content

README.md

Latest commit

 

History

History
94 lines (64 loc) · 6.18 KB

README.md

File metadata and controls

94 lines (64 loc) · 6.18 KB
layout default
title Blitz Report History | Oracle EBS SQL Report
description History of Blitz Report executions – Oracle E-Business Suite SQL report
keywords Oracle EBS, Oracle E-Business Suite, SQL report, Blitz Report, Enginatics, Blitz, Report, History, xxen_reports_h, fnd_concurrent_requests, xxen_report_runs
permalink /Blitz%20Report%20History/

Blitz Report History – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

History of Blitz Report executions

Report Parameters

Report Name, Category, Type, Report Name starts with, Submitted by User, Started within Days, Start Date From, Start Date To, Show Parameters, Running or Errored, Request Id, Run Id, Exclude System Reports, Exclude Submissions from User, License Exceeded, Incremental Alert Mode

Oracle EBS Tables Used

xxen_reports_h, fnd_concurrent_requests, xxen_report_runs, xxen_reports_v, fnd_responsibility_tl, gv$session, fnd_lookup_values, xxen_report_run_param_values

Report Categories

Enginatics

Related Reports

FND Concurrent Requests 11i, Blitz Upload History, FND Concurrent Requests, GL Account Distribution Analysis, GL Account Analysis (Distributions), CAC Interface Error Summary, DBA ORDS Configuration Validation

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

Download & Import Options

Resource Link
Excel Example Output None
Blitz Report™ XML Import Blitz_Report_History.xml
Full SQL on Enginatics www.enginatics.com/reports/blitz-report-history/

Blitz Report History - Case Study & Technical Analysis

Executive Summary

Blitz Report History is the detailed transaction log of the Blitz Report system. Unlike the "Execution Summary" which aggregates data, this report lists individual execution records. It is the primary tool for troubleshooting specific failed runs, auditing user activity, and analyzing performance at a granular level.

Business Challenge

  • Troubleshooting: "My report failed yesterday at 2 PM." The admin uses this report to find that specific run, see the error message, and view the parameters used.
  • Security Audit: "Who ran the 'Salary Detail' report last week?"
  • Performance Analysis: Identifying exactly which run of a report took 2 hours instead of the usual 2 minutes (e.g., due to a specific parameter combination).

Solution

This report provides a comprehensive view of the XXEN_REPORT_RUNS table, often joined with Oracle's standard concurrent request tables.

  • Status: Shows if a report is Running, Completed, or Errored.
  • Parameters: Can optionally show the specific parameters used for each run (Show Parameters).
  • SQL Snapshot: Some versions might link to the specific SQL used at runtime.

Technical Architecture

Key Tables

  • XXEN_REPORT_RUNS: The core execution log.
  • FND_CONCURRENT_REQUESTS: Links the Blitz Report run to the standard Oracle Concurrent Manager request ID.
  • XXEN_REPORT_RUN_PARAM_VALUES: Stores the parameter values entered by the user for that specific run.

Logic

The query lists execution records, sorted by start date. It includes logic to decode the status and link to the user and responsibility context.

Parameters

  • Report Name / Category / Type: Standard filters.
  • Submitted by User: Audit specific users.
  • Started within Days / Date Range: Time window.
  • Show Parameters: A toggle to include the parameter string in the output (can make the report wider/slower but essential for debugging).
  • Running or Errored: Filter to focus on problem areas.
  • Request Id / Run Id: Search for a specific transaction.

Useful Links

© 2026 Enginatics