BiLog: Ad Hoc Reporting...Record Sets
PamDenny 270000BXV7 Visits (11529)
The record set totals 143. Ranging from jazz, country and rock and roll, the 143 records commander a prime, comfortable spot in our attic.
Your Maximo record set may or may not have the same historical grooves. However, understanding how a Maximo application record set can be applied in Maximo Ad Hoc reporting is critical.
The Ad Hoc report where clause is made up of two components - a Saved Where Clause and a Dynamic Where Clause. If the field 'Apply the Current Query from the application' is enabled - the application where clause becomes the Saved Where Clause. I f the field is disabled - the ad hoc report has no Saved Where Clause.
This field is enabled by default as the most common use cases want the application to apply. For example, if the user created a query in Work Order Tracking for records in WAPPR status, by enabling this field, the filter would apply to the ad hoc report. Its filter of status = WAPPR becomes the 'Save Where Clause' of the Ad hoc report.
However, a power user may disable this field. If they user disables this field, the users active application query will not be applied to the report and the 'Save Where Clause'. is null. The results the user will then see depend on other actions they take in creating their report.
- If the user defines report parameters via the format tab, the parameters become the Dynamic Where Clause.
- If the user does not define report parameters, the application query will become the Dynamic Where Clause
For more information on this specific scenario, access the Ad Hoc report wiki page here. For additional details on Ad Hoc reporting, access the detail guides here for 7.5 or here for 7.1. Additionally, you can find a recorded demo of Ad Hoc reporting click here and the music can be found almost anywhere.....