Blitz Report Parameter Default Value Validation – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™. Oracle EBS module: Blitz Report · all Blitz Report reports
Overview
Lists report parameters whose LOV returns an id that differs from the displayed value, and shows whether the parameter’s default value is stored as that id or as the display text.
Default Value Correct is the id the LOV resolves the stored default to. Where it differs from Default Value, the default was entered as the display value instead of the id. Use the ‘Show non matching defaults only’ parameter to list those cases.
The framework binds the id for such LOVs, so a report level default given as display text only works through a fallback validation, which costs an additional LOV execution every time the run screen opens and is ambiguous if the same text also exists as an id. Template and user level defaults are matched against the id only, so there the display text does not resolve at all.
Is Function and Is Select show whether the default is expressed as a function, e.g. fnd_profile.value, or as a select statement, and Dupl Count how many of the listed parameters share the identical default expression.
Use the Category and Report Name parameters to limit the scope.
Run this report in Excel in seconds: download Blitz Report™ free (your first 30 reports are free) or try it in the online demo.
Report Parameters
Category, Report Name, Show non matching defaults only, Show functions ony, Show selects only
Oracle EBS Tables Used
Report Categories
Related Reports
Blitz Report Parameter Link Validation, GL Account Distribution Analysis, Blitz Report Comparison between environments, Blitz Report LOV Comparison between environments, CAC Cost vs. Planning Item Controls, AP Invoices and Lines, Blitz Upload Dependencies, Blitz Report Parameter Comparison between reports, CAC AP Accrual IR ISO Match Analysis
Running This SQL Without Blitz Report
The SQL source can be run in any SQL client. Some Oracle EBS SQL reports in this library use functions from the utility package xxen_util – install it first. Blitz Report™ adds parameters, Excel output with pivots, scheduling and security on top.
Download & Import Options
| Resource | Link |
|---|---|
| Excel Example Output | Example |
| Blitz Report™ XML Import | Blitz_Report_Parameter_Default_Value_Validation.xml |
| SQL Source | Blitz Report Parameter Default Value Validation.sql |
| Full Report on Enginatics | www.enginatics.com/reports/blitz-report-parameter-default-value-validation/ |
Case Study & Technical Analysis: Blitz Report Parameter Default Value Validation
Executive Summary
This report lists the parameters of Blitz Report definitions whose list of values returns an identifier that differs from the displayed value, and shows whether each stored default value is held as that identifier or as display text. Administrators maintaining a Blitz Report library use it to find defaults that will not resolve cleanly when a report opens. It is run in Excel through Blitz Report™, with the Category and Report Name parameters limiting the scope.
Business Challenge
- Silent default failures: A report default that does not resolve to the identifier the list of values expects can leave a parameter blank or wrong when the run screen opens.
- Hidden cost: A default given as display text needs a fallback validation, which adds an extra list of values execution each time the run screen opens.
- Ambiguous text: The same display text can exist as an identifier elsewhere, so a text default can resolve to the wrong value.
- Scale: A library with many reports and parameters cannot be checked by opening each parameter by hand.
The Solution
- Compares the stored default with the identifier that the list of values resolves it to, and shows both, so that differences are visible on one row.
- Filters to non-matching defaults only when Show non matching defaults only is requested, which isolates the cases that need correction.
- Flags whether each default is a function, such as a profile lookup, or a select statement, so the two forms can be reviewed separately.
- Counts how many listed parameters share the identical default expression, which shows where one default is repeated across reports.
Technical Architecture (High Level)
Primary Tables
XXEN_REPORT_PARAMETERS_V: the parameter definitions of every Blitz Report, with the parameter name, type, list of values, default value, display sequence and last update details.
Logical Relationships
- The parameter view is restricted to rows that have a display sequence and a stored default value.
- Parameters whose list of values already returns the identifier are excluded by a test on whether the list of values equals its identifier.
- The remaining rows are classified with the function and select tests from the Blitz Report framework, and the default is resolved to an identifier with the value-to-identifier function.
- An analytic count over the default value gives the number of parameters that share the same default expression.
- The outer query applies the optional filters for functions and selects and sorts by report, category and display sequence.
Parameters & Filtering
- Category and Report Name: limit the scope to one category or one report.
- Show non matching defaults only: lists only the parameters where the default is not the identifier the list of values returns.
- Show functions ony: restricts the list to defaults expressed as a function, such as a profile value lookup.
- Show selects only: restricts the list to defaults expressed as a select statement.
Performance & Optimization
- Each row calls the list of values framework once to test whether the list returns identifiers, so the report’s run time grows with the number of parameters that have defaults.
- The analytic count over the default value is computed in the same pass as the rest of the row, avoiding a second query for the duplicate count.
- The filters on Category and Report Name reduce the parameter set before the identifier resolution is run for each row.
- The row set is read from the parameter view alone, so the cost is set by the number of parameters in the library.
FAQ
Q: Why does a report default need to be stored as an identifier rather than as display text? A: A default stored as an identifier resolves directly when the run screen opens, whereas a default stored as display text needs an extra list of values execution and can be ambiguous.
Q: How do I list only the defaults that need correcting? A: Set Show non matching defaults only to Yes, optionally with Category or Report Name, and the report returns the parameters whose default differs from the identifier the list of values resolves.
Q: What does Dupl Count show? A: Dupl Count gives the number of listed parameters that share the identical default expression, which helps find one default repeated across several reports.
Useful Links
- Blitz Report™ – World’s Fastest Oracle EBS Reporting Tool
- Oracle Discoverer Replacement – Import Worksheets into Blitz Report™
- Oracle EBS Reporting Toolkits by Blitz Report™
- Blitz Report™ FAQ & Community Q&A
- Supply Chain Hub by Blitz Report™
- Blitz Report™ Customer Case Studies
- Oracle EBS Reporting Blog
- Oracle EBS Reporting Resource Centre
© Enginatics GmbH