This page describes the forms that support definition of execution parameters on the IFS Business Reporter report level, i.e. these forms can be used to define report specific values for the available execution parameters. Execution parameters are either defined to apply for the complete report or only for a specific data set. This means that it is possible to control the execution of a specific data set which might be necessary if only one data set out of all available ones in a report has bad performance.
It is also possible to use these forms in order to look up the total execution time of a report, to look up the execution time for each individual data set, to find out how many data sets a report consists of and also to investigate the current and the next SQL statement for a data set.
The BR Report Level Execution Parameters page presents execution information about an IFS Business Reporter report. The report must be published through IFS Business Reporter to appear. Publishing can be done in two ways:
The report is published for access via the IFS client, i.e. it can be executed via the ordinary report framework in IFS Applications.
The report is published for access only via IFS Business Reporter. After publishing the report, use Order Report in report mode in IFS Business Reporter to run it and then use the BR Report Level Execution Parameters page to look up number of data sets, timings etc.
| Attribute | Description |
|---|---|
| Report ID | The ID of the published report |
| Report Name | The name of the published report |
| Published Date | The date the report was published |
| Published for BA Access Only | Selected if the report is only accessible, possible to execute, via IFS Business Reporter. If not enabled the report can be executed via the IFS client. |
| Created By | The user ID of the report creator. This value is set automatically when the report is saved or published |
| Duration (sec) | Time taken for the latest execution of the report in seconds. |
| Hint | Oracle query hint to be applied to the SQL statement. Format is /*+ <hint(s)>
*/This value will be applied if it is not overridden at the data set level. |
| Execute SQL Statements | Indicates whether the SQL statements corresponding to all data sets of the report should be executed during the next execution of the report. |
| Go to Runtime Log. | Command that navigates to the latest log entries for the current report. Can be very useful in order to in more detail investigate the server execution steps. |
In the EXECUTION PARAMETERS tab it is possible to add execution parameters that should affect the current report only.
| Attribute | Description |
|---|---|
| Parameter Name | The name of the execution parameter. Only execution parameters allowed on report level can be used here. |
| Parameter Value | The value of the execution parameter. Will be applied to all data sets of the report regardless of the global value unless it is overridden at the data set level. |
The DATA SETS tab presents all data sets for the report and gives information about execution time and SQL statement used.
| Attribute | Description |
|---|---|
| Data Set ID | The ID of the data set |
| Hint | Oracle query hint to be applied to the SQL statement. Format is /*+ <hint(s)> */ |
| Execute SQL Statement | Indicates whether the SQL query related to this specific data set in the current report should be executed during the next report execution |
| Duration (sec) | Time taken for the latest execution of the data set in seconds |
| SQL Statement | The SQL statement used for the latest execution of this data set. Statement may change from execution to execution depending on the current values of the execution parameters |
By selecting a data set it is also possible to navigate to the page BR Execution Parameters for Data Set, that supports configuration of the report set level.
This page presents execution information about a specific data set associated with an IFS Business Reporter report. The page enables definition of data set specific parameters in order to control the execution of that specific set. This can be useful in situations where one or a few data sets out of all the report data sets have poor performance. By investigating the associated SQL statement a remedy might be to use the execution parameters to improve the data set execution.
| Attribute | Description |
|---|---|
| Report ID | The ID of the published report. |
| Report Name | The name of the published report |
| Data Set ID | The ID of the data set |
| Duration (sec) | Time taken for the latest execution of the data set in seconds |
| SQL Statement | The SQL statement used for the latest execution of this data set. Statement may change from execution to execution depending on the current values of the execution parameters. |
| Hint | Oracle query hint to be applied to the SQL statement. Format is /*+ <hint(s)> */ |
| Execute SQL Statement | Indicates whether the SQL query related to this specific data set in the current report should be executed during the next report execution |
In the detail section tab it is possible to add execution parameters that should affect the current data set only.
The command Statement for Next Execution can be used to view the SQL statement for the current data set with respect to the current execution parameter settings.
| Attribute | Description |
|---|---|
| Parameter Name | The name of the execution parameter. Only execution parameters allowed on data set level can be used here. |
| Parameter Value | The value of the execution parameter. It will be applied to this data set regardless of the values on global and report level. |
The page supports a way of investigating the affect the execution parameters have on the data set SQL statement.
More information can be found on the Example Usages page and on the Tuning Advice page.