IV93935: PROVIDE CONFIGURABLE FIELD FOR PASSING ACTIVE APPLICATION QUERY TO SAVED AD HOC REPORT.

APAR status

• Closed as program error.

Error description

• With Maximo 76 Ad Hoc (QBR) reporting, unexpected record results
  may be received.
  
  PROBLEM:
  Maximo 76 introduced report record limits for QBR reports.  With
  this feature, the active application query is passed at run time
  to a saved QBR report when the 'Saved Application query' is
  selected.  In some scenarios, the combination of both the Saved
  and Dynamic queries in the ad hoc report ? may cause the user to
  receive less records than expected.
  
  PERFORMANCE ISSUE:
  Report record limits prevent the user from inadvertently running
  a report against very large record sets and impacting system
  performance.   Carefully review the configuration changes this
  new feature enables to avoid potential performance issues.
  
  STEPS TO REPRODUCE:
  1. Go to Work Order Tracking.
  2. Create query called 'XYZ Work' with query = (istask = 0 and
  siteid = 'xyz')
  3. Save the query and select it.
  4. Create an ad hoc report.
  5. Confirm the ?Apply Application Query? field is selected.
  6. Input a title and save the report.
  7. The report runs against the saved XYZ site query you created.
  This can be seen by viewing the results on the last page of the
  report.
  
  8. Close any dialogs and the report viewer.
  9.  With the ?XYZ Work? query still active in Work Order
  Tracking, add an additional filter on status.   Note the number
  of records.
  10. Select the ?Run Report? action.
  11. Select the ad hoc report you created from above
  12. Run the report.
  
  13. Navigate to the last page of the report.
  14. Note the ?XYZ Work? query displays in the Saved Where Clause
  section.
  15. Note the new status filter created in step 9 displays in the
  ?Run Time Where Clause? section
  
  CURRENT ERRONEOUS RESULT:
  The user may only expect his saved application query to display
  when running the saved report.
  
  EXPECTED RESULT:
  The user should be able to configure if the dynamic application
  query should pass to his saved ad hoc report or not.
  
  ADDITIONAL INFO:
  
  ENVIRONMENT (SYSTEM INFO):
  Maximo 7.6
  
  LOCAL FIX:
  The property setting, mxe.report.adhoc.UserSelectDynamicQuery,
  is available.   If the property is set to true, a configurable
  field on the Ad Hoc creation dialog will be available.   The
  field enables the creator of the QBR report to specify if the
  active application query will be passed to the saved QBR report
  when the ?Saved Application Query? is selected.   If the active
  application query is not passed to the Ad Hoc report, it will be
  noted on the last of the report.
  

Local fix

• No
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Ad hoc report users.                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In Maximo 76 Ad Hoc (QBR) reporting, unexpected record       *
  * results may be received.                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In Maximo 7.6, the application query is included in the SQL of
  an ad hoc report even when the report includes a saved where
  clause.  This behavior is changed from prior versions.
  

Problem conclusion

• The behavior is now configurable via a property
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  AD HOC REPORTIN

• Fixed component ID

  5724R46AH

Applicable component levels

• R760 PSN

     UP