When creating, you can specify two types of parameters before running a report:
Use these to filter the SQL results. Data View result rows that do not match the filter will not be sent from Unifier to BI Publisher.
Use these to pass additional parameters for BI Publisher to consume at runtime. All values are sent from Unifier to BI Publisher for further operation.
Search parameters allow the report runner to filter the data that gets sent to BI Publisher. For example, a Contract Report may need to be filtered by Vendor or Contract Type. A Ball-in-court report may be filtered for a specific task assignee, or task type.
At runtime, the report runner can select or multi-select from a list of values based on the search parameters specified in the report configuration. This means that Unifier basically runs the Data View before the report is run to give the report runner a list of the SQL results. He can then select or multi-select values from this initial run to filter what will appear in the report output. For more information on the Search Parameters, see "Add query parameters to custom report (Query tab)" in the Unifier Help.
Example
The following are instructions for filtering your Invoices Report on Invoice Vendor:
Note: You can only add queries on your Main View (not Sub Report Views).
Upon running the report, the report runner display the Invoice Query window. When you click Select, Unifier runs the Data View that you selected (Invoices) to get a list of all the VENDORS that would be returned if there were not filters. Multi-select your Vendors by using the Ctrl key. Enter text in your report to indicate that it was run using a query. We can access the value specified by the report runner via a top-level field.
Additional parameters allow the report runner to specify parameters that can be used at report runtime to alter how the data is displayed.
Unlike Search Parameters:
A good example of where to use Additional Parameters is for calculations, for example, when you enter a target future exchange rate. You can also use Additional Parameters for conditional highlighting so that only rows over/under a certain value are highlighted.
Note: In the section Conditional Formatting, You need to hard-code a value (for example, 10,000).
The following are instructions for conditionally highlighting Invoices based on amount in our Invoices Report:
Note: When running the report, the selections add parameter called ‘Amount’, with label ‘Highlight Amount’ and an editable value of 10000 in the Additional Parameters box.
If you run the report at this stage, you see no changes because unlike Search Parameters, all the same data is passed to BI Publisher. You need to add some additional logic to your RTF template to use this new ‘Amount’ parameter.
<uuu_p_Amount>10000</uuu_p_Amount>
<?variable@begin:uuu_p_Amount;(.//uuu_p_Amount)[1]?>
To use the variable, you can call $uuu_p_Amount
instead of your hard-coded 10000 in our conditional statement (assuming you already followed the instructions in Conditional Formatting).
<?if@row:number(INV_AMOUNT)>10000?><?attribute@incontext:background-color;'#F8DADB'?><?end if?>
<?if@row:number(INV_AMOUNT)>$uuu_p_Amount?><?attribute@incontext:background-color;'#F8DADB'?><?end if?>
If you run the report, you see the same behavior as before because the value in your Sample XML is the same as the value you hard-coded before (10000).To test:
uuu_p_Amount
to a value lower (for example, 5000). Creating a Custom Report in Primavera Unifier
Download and Install BI Publisher Desktop for Microsoft Office
Review Unifier Database Table Structure
Creating a Report with Line Items
Advanced BI Publisher Functions
Legal Notices
Copyright © 2016, 2018,
Oracle and/or its affiliates. All rights reserved.
Last Published Wednesday, March 28, 2018