Scenario - Navigate from Report A to Report B and Report B data should get filtered based on the selection made in Report A.
Solution -
Note -Report A and Report B should have some common tables and fields. Data filtering upon navigation will only happen on the common tables and columns.
Example 1 - We have a Order header report and want to navigate to Order details, where user will click on Order Number and will be navigated to a detail report with order line information. a. Create Report A with attributes Order Number from table1. b. Create Repprt B with attribute Order Number from table1 and line number from table2 and make a filter Order Number "is prompted" c. Modify Report A, add value level navigation in column order number to report B. d. Once you click on order number column in report A, it will open a new window with order and lines details for the order selected in Report A
Example 2 - Same two reports as mentioned in the above example. Navigation will be based on order number but the target report will be filtered for the customer of the order in Report A a. Create Report A with attributes order number and customer number rom table 1 b. Create Report B with attributes order number and customer number form table 1 and line number from table2 and make a filter customer number "is prompted" c. Modify report A, add value level naviation on column Order Number to report B d. Once you click on Order Number in Report A, it will open Report B where data might be filtered by the customer. Wierd! Right?
Answer is in the ordering of the columns in the report A. Note - All the columns in Report A, which are required to pass values to Report B, should be placed to the left of the column on which navaigation link will be placed.
Thursday, April 7, 2011
Passing values across pages using report navigation
Labels:
business intelligence,
obiee,
oracle,
parameters,
prompts,
variables
Subscribe to:
Post Comments (Atom)

No comments:
Post a Comment