3 Level Master-detail-detail data view implementation

Hi OAF Gurus,
I have a requirement, where in I have to show a 3 level master-detail relationship data on a page. Is it possible to implement a master-detail-detail table structure i.e. table-in-table-in-table view. I have done table-in-table ( a 2 level or master-detail ) structure before, but I am running out of ideas on this one. Below is the requirement.
I have queryBean for a customer search, then when searched by a customer, I get the Customer search results in a table below. Then I need to show Customer Sites in an inner table and then in another inner table on the Customer Sites, I need to show the customer contacts, something like this below.
+ Customer Name, Customer Acct.Number ....
+ SiteId , Site Name, BillTo, ShipTo
+ ContactName, Contact Address, Contact Phone Number
Hope you can provide me some ideas. I appreciate all your help. Thanks again.

Anyone any ideas, please let me know. This is really urgent. Please let me know if there is any way we can do this, other than going to a new page. Appreciate your feedback.
Thanks.

Similar Messages

Master/Details Relationship using View Links is not not population data

Hi,
I have problem in generating proper data in master/detail relationship using view links passing three parameters between two custom tables can guide me the steps and process how i will able to generate and acheive this requirement.
very urgent
Please suggest me

Without further details, I'd suggest reviewing the following Section of the Fusion Developers Guide:
http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/web_masterdetail.htm#ADFFD758
I've done this many times without issue.

Post-generating 3-level master-detail-detail screens

Hi all,
for a consulting project, I had to create several three-level master-detail screens using JHeadstart. For the JHS demo app, this would mean for example that a location page contained a list of departments at the location and underneath it a list of employees working at the currently selected department.
From what I have learned so far using JHS, this is not supported by the wizards and should be done by post-generation changes. This forum has a few topics mentioning the problem and possible solutions, but most of the time just fragments of the complete solution/approach. As I had to create several of these 3-level detail screens, I tried to uniformly document them, providing the 7-step guide as outlined below. I only started working with JHS recently, so please let me know where I take a long way round or where my approach is not appropriate at all :o)
NOTE1: Terminology-wise, for the example given above, I will call the departments the 2nd level detail and employees the 3rd level detail, while locations are the first level masters. I hope this is not too confusing ;o)
NOTE2: the example code is not guaranteed to work with the JHSdemo. I just changed the names of variables and classes from my own application to the familiar entities of the demo.
STEP 1: Generate plain MD screens for the first and second level entities (table-form) using the JHS application generator and make sure all generated features you want in your page are OK. Afterwards, switch off the UIX generation in your application structure file. If you want multiple entities at the third detail level,
STEP 2: Add the functional contents of the generated 3rd level detail UIX page to the main master UIX page, right underneath the 2nd level detail-table but still inside the <header> entity of this 2nd level detail. (I'm not too sure whether this really matters, but at least the indentation looks nice). What I call "functional contents" is the <header> entity containing the 3rd level detail table.
STEP 3: Edit the java file of the 3rd level view object, adding a variable storing the identifier (primary key) of the currently selected 2nd level detail row. If you haven't used the java file before, generate it by doubleclicking the view object and checking the generate view object box in the Java screen.
private String $selectedDeptID;
public void setSelectedDeptID(String id) {
$selectedDeptID = id;
STEP 4: Edit the java file of your application module (in the model layer) and add a method for updating the view objects search queries like the example below:
public void updateEmployeeView(String deptID) {
// fetch the view object instance
EmployeeViewImpl view = (EmployeeViewImpl)this.getEmployeeView1();
// register the currently selected departments ID
view.setSelectedDeptID(deptID);
// re-execute the view objects query
view.executeQuery();
// reset the selected ID
view.setSelectedDeptID(null);
STEP 5: Create a java class for handling the event when a user selects a different 2nd level detail row.
package view;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpSession;
import oracle.adf.controller.struts.actions.DataActionContext;
import oracle.adf.model.BindingContext;
import oracle.adf.model.bc4j.DCJboDataControl;
import oracle.adf.model.binding.DCDataControl;
import oracle.adf.model.binding.DCUtil;
import oracle.cabo.servlet.BajaContext;
import oracle.cabo.servlet.Page;
import oracle.cabo.servlet.event.EventResult;
import oracle.cabo.servlet.event.PageEvent;
import oracle.cabo.servlet.ui.data.PageEventFlattenedDataSet;
import oracle.cabo.ui.data.DataObject;
import oracle.cabo.ui.data.DataSet;
import oracle.cabo.ui.beans.table.SelectionUtils;
import oracle.jbo.ApplicationModule;
* USER-DEFINED EVENT-HANDLING CLASS
* this class is triggered after the user selects another row in the Department
* table/form in the Locations.uix screen. It derives the ID (pk) of the
* selected row and launches the AppModule method to update the view objects
* select queries with the selected DeptID.
public class RowSelector
* private variable holding the name of the DataControl module for this
* Application Module
private static final String DATACONTROLNAME = "AppModule" + "DataControl";
* private variable holding the name of the table/form object in the uix page
* from which we want to derive the selected row data.
private static final String TABLEFORMNAME = "DepartmentsView2";
* private variable holding the name of the form field holding the database
* ID (pk) of a row in the ${TABLEFORMNAME} table/form
private static final String IDFIELDNAME = "Dept_ID";
* This method fetches the ID of the user-selected row in the DepartmentsView2
* table/form in the Locations.uix form.
* Afterwards, it fires the ApplicationModule method for updating the view objects
public static EventResult doSelectionEvent(BajaContext bc, Page page, PageEvent event)
try {
// create a new FlattenedDataSet for the table name
DataSet tableInputs = new PageEventFlattenedDataSet(event, TABLEFORMNAME);
// fetch the UI table index from the DataSet (NOT the pk from the db)
int index = SelectionUtils.getSelectedIndex(tableInputs);
// fetch the DataObject representing all the input elements on the current table row.
DataObject row = tableInputs.getItem(index);
// fetch the value of the input field holding the ID (pk) of the selected department row
Object value = row.selectValue(null, IDFIELDNAME);
if (value != null) {
// tell the AppModule to update the appropriate view object(s)
getAppModuleImpl(bc.getServletRequest()).updateEmployeeView(value);
// quick and dirty exception handling. not too many exceptions possible due to
// hard-coded field/table/module names. anyway, taking no action at all is not
// that bad an option for a demo ;o)
} catch (Exception e)
e.printStackTrace();
return null;
* method for fetching the active Application Module
public static AppModuleImpl getAppModuleImpl(HttpServletRequest request)
BindingContext ctx = DCUtil.getBindingContext(request);
DCDataControl dc = ctx.findDataControl(DATACONTROLNAME);
AppModuleImpl service = (AppModuleImpl)dc.getDataProvider();
return service;
STEP 6: Override the executeQueryForCollection method in your view object java file to make sure it uses the selected 2nd level detail rows ID for the bound variable specifying the 3rd level select query. Otherwise, the select query for the 3rd level detail set appears to use the ID of the first 2nd level detail row selected for the currently selected 1st level master. In the example below, no other bound variables are used in the view object, otherwise, the indexing might have to be adjusted.
protected void executeQueryForCollection(Object qc, Object params[], int noUserParams) {
if ($selectedDeptID != null) params[0] = $uur;
super.executeQueryForCollection(qc, params, noUserParams);
STEP 7: In the Locations.uix page, set a primaryClientAction for the radio select input in the 2nd level detail screen. This action should fire an event (fe 'userChoseDepartment') and refresh the 3rd level detail tables using the partial refresh options in the primaryClientAction dialog window. Afterwards, add an event handler to the bottom of your Locations.uix page, linking the event specified before to the doSelectionEvent in the RowSelector class.
So, that's how it worked for me. I hope it does the same for you and please do post any comments or remarks if problems arise or simplifications are possible. The more remarks or bugs appear in the above code, the more the JHS team is hinted to enable auto-generated 3rd level detail screens :-D
Cheers,
benjamin

Benjamin,
Thank you for sharing your expreinces with us!
A few remarks:
1. With JHeadstart 10.1.2.1 you can generate unlimited master-detail levels in the same page when using UIX and table-layout for the detail groups This feature is implemented usin g UIX table detail disclosure: when you click on the "show" link in a row in of the level 2 detail table, you will see in the detail disclosure area the level 3 detail table.
There is a screen shot of this feature in the JHeadstart Developers Guide for 10.1.2.1, chapter 3, section "Creating Table Pages". You can now download the dev guide from the JHeadstart Product Center:
http://www.oracle.com/technology/consulting/9iservices/jheadstart.html
2. You have a lot of steps related to synchronizing the level 3 ViewObject with the level 2 ViewObject. You can leave all this work to ADF Business Components, by adding the l;evel 3 ViewObject as a nested usage to the level 2 ViewObject in your application module data model.
Ths would save you the work you aredoing in steps 3 to 6.
Steven Davelaar,
JHeadstart Team.

Problem in implementing Master-Detail-Detail design in Forms 6i

Hi, all technocrats!!
Here i've problem in Master-Detail-Detail sort of design in
Forms 6i..
This thing i've implemented earlier in one form...and that is
fine...and i could not track the root when i've got a problem in
a new form...which of the same manner...
The problem is that...
When i enter data into the 1st detail block and navigate to the
2nd detail which is a detail block to the 1st detail...and enter
data, there is no problem, but when i navigate back to the 1st
detail block and that to a new record in the 1st detail...form
is showing indefinite behaviour( Hanging )...
But when i navigate back to the same record in the 1st detail
from the 2nd detail...there were no problems and it is working
fine...
And whenever i shift to a new record in the first detail it is
asking to save that record...to solve this problem., i've used
POST in the new block instance of the 1st detail...and i'm
comfortably managing it...if i dont use this POST method...it is
clearing the details in the 1st detail itself when i traverse
back to it from 2nd detail after inserting records...
But this hanging problem is really driving me to Hang myself...
Plz do suggest me to get rid of this problem...

Developing proper transactional behavior with Oracle Forms
in Grandparent-Parent-Child case is a problem.
We must use some 'container' for 'non-visible' Child records
(Child records with Parent different from current record in
Parent block).
I try to solve this problem in 2 different ways:
1. Using POST built-in. In this case 'container' is Child
database table. But, problem can be because POST built-in
actually executes DML statements (this locks records and fires
database triggers - so a deadlock can occur) before COMMIT_FORM.
2. Using a 'temporary container'. 'Temporary container' can be
(for example) temporary database table, PL/SQL table of records
(defined in Forms package or database package), Forms record
group. This variant has not problem with record locks/database
triggers, but is much more complex for programming than 1.
variant.
In my development, when I haven't problem with record locks or
database triggers, then I use POST. In other cases, I use 2.
variant, with PL/SQL table of records (defined in Forms package)
as 'temporary container'.
Further, when we use POST, we can do this in more ways.
One method is to use POST in Forms level WHEN-NEW-RECORD-
INSTANCE trigger.
Different method is to change code in CLEAR_ALL_MASTER_DETAILS.
Instead of:
CLEAR_BLOCK (ASK_COMMIT);
we can write:
IF mastblk = "name_of_master_block" THEN
CLEAR_BLOCK (ASK_COMMIT);
ELSE
POST;
END IF;
Which method you use?
Regards
Zlatko Sirotic

Views master-detail-detail by view links -- ADF UIX

Hi,
I have 3 views: master, detail of master, and detail of detail....then i want to create 2 viewlinks to relate them and so show them in the DATA CONTROL PALETTE....
Any Suggestion ??
Thanks...
S.J.
PD...When i use 3 tables, it is possible because they are foreign keys.

You can find it in
Re: Parent-Child using <messageChoice> to <table>

PRISM Master-Details with navigation between the Master and details view

Hi, I have a Master list with accounts and a Details list containing transactions.
The Master list : has a UserControl (AccountListView) and Viewmodel(AccountListViewModel)
The list is bound to an observable collection of type AccountViewModel and has a SelectedAccount property to get the current selected account. Each AccountViewModel has a collection of type TransactionViewModel.
public AccountListView(IAccountListViewModel viewModel)
//this.DataContext = vm;
InitializeComponent();
ViewModel = viewModel;
public Infrastructure.IViewModel ViewModel
get
return (IAccountListViewModel)DataContext;
set
DataContext = value;
//the viewmodel
public AccountListViewModel(IRegionManager regionManager)
this.regionManager = regionManager;
this.AccountList = GetAccounts(); // gets the list of accounts from another layer
public AccountViewModel SelectedAccount
get { return selectedAccount; }
set
selectedAccount = value;
OnPropertyChanged("SelectedAccount");
And the Details view has a user control(TransactionListView) and a viewmodel(AccountView);
public TransactionListView(IAccountViewModel viewModel)
InitializeComponent();
ViewModel = viewModel;
//this.DataContext = vm.SelectedAccount;
public Infrastructure.IViewModel ViewModel
get
return (IAccountViewModel)DataContext;
set
DataContext = value;
//the viewmodel
public AccountViewModel(Business.Account a)
AccountId = a.AccountId;
accountName = a.AccountName;
I created a hyperlink command so that whenever I click on the name of an account from the master list it will navigate to the detail list and set the as the DataContext the account I clicked on. Before I had both Master and Detail lists displayed at the
same time and set the DataContext of the Detail List as the SelectedAccount property(which is bound to the SelectedItem of the Master List) of the Master List. I am not sure how to pass the SelectedAccount when I navigate to the Detail List and set it as the
DataContext of the Detail List.

>>I'm using the reguestnavigate method, but from what I read you can't pass objects as parameters ?
As I mentioned there is a NavigationParameters class that you can create an instance of and pass as a parameter to the RequestNavigate method in Prism 5:
private void NavigateTransaction(AccountViewModel obj)
var parameters = new NavigationParameters();
parameters.Add("accountViewModel", obj);
regionManager.RequestNavigate(RegionNames.ContentRegion, new Uri(transactionview, UriKind.Relative), parameters);
The TransactionView should then implement the Microsoft.Practices.Prism.Regions.INavigationAware interface and retrieve the parameter in the OnNavigatedTo method:
public partial class TransactionView : UserControl, INavigationAware
public TransactionView()
InitializeComponent();
void INavigationAware.OnNavigatedTo(NavigationContext navigationContext)
AccountViewModel myParameter = navigationContext.Parameters["accountViewModel"] as AccountViewModel;
this.DataContext = myParameter;
public bool IsNavigationTarget(NavigationContext navigationContext)
return true;
public void OnNavigatedFrom(NavigationContext navigationContext)
In Prism 4 there is no NavigationParameters class so you either need to upgrade to Prism 5 if you haven't already done so or you could store the parameters to be passed yourself somewhere else. Please refer to the following links for more information and
examples of how you could do this:
http://stackoverflow.com/questions/9320638/how-to-pass-an-object-when-navigating-to-a-new-view-in-prism
http://visualstudiomagazine.com/articles/2012/08/20/view-communication-in-wpf-and-prism.aspx
Please also remember to mark helpful posts as answer to close the thread and then start a new thread if you have a new question. Please don't ask several questions in the same thread.

Master and Details Tables Data

Hi all
I have two tables one is Master table and other one is Details table.
How to write a query to get Master as well as Details table data.
Detail table contain more than one record for particular Master Record.
Pls Help me.

My version is Oracle 9i
My Tables structures are :
SQL> desc TFMS_CONTRACT_PRICES
Name Null? Type
ITEMNUMBER NOT NULL VARCHAR2(30)
ITEMDESCR VARCHAR2(2000)
PRICE NOT NULL NUMBER
UOM VARCHAR2(30)
UNITSAWARDED NUMBER
DELIVERYPERIOD NUMBER
COMMENTSREASON VARCHAR2(15)
TOTALPOINTSSCORED NUMBER
FREEDELIVERY VARCHAR2(250)
YEAR VARCHAR2(15)
UPDATEDBY NOT NULL NUMBER
UPDATEDON NOT NULL TIMESTAMP(6)
BRANDID NOT NULL NUMBER
CONTRACTORID NOT NULL NUMBER
ISPRICEESCALATED NOT NULL CHAR(3)
SQL> desc TFMS_ACCESSORIES_MASTER
Name Null? Type
ACCESSORYID NOT NULL NUMBER
ACCESSORYNAME NOT NULL VARCHAR2(150)
DESCR VARCHAR2(250)
ISDELETED NOT NULL CHAR(1)
UPDATEDBY NOT NULL NUMBER
UPDATEDON TIMESTAMP(6)
CONTRACTORID NOT NULL NUMBER
Sample Out put:
ITEMNUMBER ACCESSORYNAME
RT57-01-13-01 Truck ToolBoxes,Riding Sun Glass
RT57-01-13-02 Door Guard,Maruthis
For one item number there may be one accessory name or more than one accessory name.i need to display accessory names with delimeter(,).
Pls help me.
Thanks in Advance.

How to set the display ratio of master and detail view

Currently, I use SplitApp that contain the master and detail view. And I would like to show the master view on the left half and detail view on the right half. Is there any proper way to adjust this?
Thank you in advance.

You can set the width ratio by adding css. Check this,
http://jsbin.com/dakir/1

URGENT HELP PLS : Issue with Multi Level Master Detail block

This is an issue someone else had posted in this forum few years back but there was no solution mentioned, I have run into this same issue , The problem is as explained below.
Any help on this is appreciated.
Scenario:
There are 3 Blocks in the form : A (Master Block)
: B (Detail of A )
: C (Detail of B )
There is master detail relation created between A and B and B and C. So initially when we query for a record in Master A, it shows all records properly in B and C.
Now if i navigate to the first record of B , and then second record of B , records corresponding to that record shows up properly in C block.
Till now everything works fine.
Issue 1:
But in case after querying initially on Master Block A,If I go directly to the second record of B block, it clears the whole B block and C block.
Issue 2:
Same thing happens if I am on C block ( corresponding to second record of B block) and then navigate to first record in B block , it again clears the whole B block and C block.
Please Help !!
Thanks !

Thanks Xem for Your reply , I tried those settings but it did not help..here is the original link that to the thread that talks about the same problem ,
Issue with Multi Level Master Detail block
The last update to this was the following :
"I figured out that this is happening because Block Status is set to 'Changed' and this is causing it to clear out the blocks.
But cant figure out why the status is setting to 'Changed' "
Any Help from the form Gurus on this form in this matter is truely appreicated !!
Thanks,
Zid.

Creating master details application with views!

Hi All,
I have a requirement to create the master details with the views, but when I was trying to create the master details its asking me for Master Table name & detail table name. Here I am giving the master table name in place of detail table name I am using view but its not showing my view in query builder, my view is already there in the database
any idea why its not showing my view?
Thanks,
Suma.

Hi Claudia,
I am so sorry, but I do not check the Oracle forums every day. I am under presser, because have to relocate from Bulgaria to the USA through the end of November.
Shortly, any view could be updatable under many restrictions. I suppose, that is the reason for the errors. I don’t know what kind of connection you have between those two tables.
Under all these circumstances, I’ll offer you to build first a form on the base of the first table which all columns are used. Then you can test, refine, and finish all details about it.
Second, you can Create Page Computation retrieving the column (value, if any) from the second table.
Third, you should Create Page Process on Submit of type “PL/SQL anonymous block”, which will INSERT the calculated (entered) value into second table.
You gain:
1. Full power of ApEx to build automatically forms and reports.
2. Min. manual work.
3. You can use the select statement from the view to build your SQL query.
4. You are able to build and test that part of the application step by step.
Konstantin
[email protected]

Master/detail/detail

using jsf/adf bc. I've got a jspx which needs to display data from a master/detail/detail setup. In a 'create' mode, i'm programmatically handling the create/insert stuff for the new master and detail rows. I'll try to explain my problem using a Departments/Employees/EmployeeAddresses example.
I've created a view link between Departments and Employees. I've created a view link between Employees and EmployeeAddresses. These have all been added to the active data model so that it looks like this:
DepartmentView
-Employees via Employees1
-EmployeeAddresses via EmployeeAddresses1
The code i use to create/insert the master and subsequent detail rows is as follows:
//create master (department) row
ViewObjectImpl vo = getDepartmentView();
Row departmentRow = vo.createRow();
vo.insertRow(departmentRow);
//create the detail (Employees) row to be associated with its master (Department)
ViewObjectImpl employeesVO = getEmployees();
Row newEmployeeRow = employeesVO.createRow();
employeesVO.insertRow(newEmployeeRow);
//create the detail/detail (EmployeeAddresses) row to be associated with its master (Employees)
ViewObjectImpl employeeAddressVO = getEmployeeAddresses();
Row newEmployeeAddressRow = employeeAddressVO.createRow();
employeeAddressVO.insertRow(newEmployeeAddressRow);
The problem seems to be with the last level detail row, the one for EmployeeAddresses. creating in this fashion doesn't seem to associate the new EmployeeAddress row to it's master, Employees. Although when the page is rendered, i can see that new rows have indeed been created/inserted for each of these view objects. After filling in valid values and committing, i get the JBO-27014 (Attribute is required) error for each attribute in the EmployeeAddresses table. So, it's as if this EmployeeAddress row that was created is not tied in with the Employees row, which is in turn tied in to the Department row.
Note: if i remove the create/insert code for this last detail row (EmployeeAddress) and simply have a basic master/detail setup between Department and Employee, everything works great when i create new rows this way and save. It seems that my problem stems from the fact that i'm adding another detail level onto my master/detail setup. Is there something different i should be doing?

Hi,
Thanks guys for your response.. i did it myself following way..
created 2 view links. having same source.
added both vos to same source in application module it self.
Regards,
Santosh.

Master and Detail records in the same table

Hi Steve,
I have master and detail address records in the same table (self-reference). The master addresses are used as templates for detail addresses. Master addresses do not have any masters. Detail addresses have three masters: a master address, a calendar reference and a department. Addresses change from time to time and every department has its own email-account, but they refer to the same master to pre-fill some common values.
Now I need to edit the master and detail address records on the same web page simultaneously.
My question is: Can I implement a Master-View and Detail-View which refer to the same Entity-Object? Or should I implement a second Entity-Object? Or can it be done in a single Master-Detail-View?
Thanks a lot.
Kai.

At a high level, wouldn't this be similar to an Emp entity based on the familiar EMP table that has an association from Emp to itself for the Emp.Mgr attribute?
You can definitely build a view object that references two entity usages of the same entity like this to show, say, an employee's ENAME and at the same time their manager's ENAME.
If there are multiple details for a given master, you can also do that with separate VO's both based on the same entity, sure. Again, just like a VO that shows a manager, and a view-linked VO of all the employees that report to him/her.

How to create one Oprations button (Create Button Or CreateInsert Button )for all master And Detail block?

hi
I have master And Detail with 4 level ,I want to have on operations button for all block in data control .
(similar to Oracle form toolbar)
how to do it ?

Well, if you tell us your jdev version and what exactly you try to do, without just telling us 'as in forms' we might be able to help.
Most of us don't know how it's done in forms. So be specific when you describe your use case.
Timo

Master table, detail table, detail table not getting refreshed selection

i have a page where i am displaying data as master table and detail table. both table VOs are based on SQL queries which use bind variables.
i have a view link between vos of type 1:M
i created master table detail table page by dropping detail iterator from data control panel under master and selecting master table detail table
on my page i see detail table records getting populated only for first record of parent table.
on changing parent record, child table shows same records and does not refresh
i am using partial triggers on both tables to be populated on a button click as i need to pass some bind variables to VOs which are taken as input from users
how can i show corresponding rows in detail table when parent record in table changes
will i have to use table selection listener
is it possible declaratively to have master detail table view when both VOs have bind variables
jdev 11 1 1 5

these are the SQLs used
Parent SQL Based VO Query
SELECT to_char(d.status_date,'yyyymmddhh24') TIME123, count(DISTINCT d.c4)
FROM t1 d,
t2 w
WHERE w.c1 = nvl(:ou, w.c1)
AND UPPER(w.c2) = UPPER(nvl(:tt, w.c2))
AND d.c3 >= :startTime AND :startTime IS NOT NULL
AND d.c3 <= :endTime AND :endTime IS NOT NULL
AND d.c4 = w.c4
AND UPPER(d.status) = 'CLOSED'
GROUP BY to_char(status_date,'yyyymmddhh24') ORDER BY to_char(status_date,'yyyymmddhh24') DESC
Child SQL Based VO Query
SELECT w.c1,
w.c5 - w.c6 processing_time,
w.c3,
w.c6,
w.c7,
w.c8,
to_char(d.status_date,'yyyymmddhh24') TIME123 FROM t1 d,
t2 w
WHERE w.c2 = nvl(:ou, w.c2)
AND UPPER(w.c3) = UPPER(nvl(:tt, w.c3))
AND d.c4 >= :startTime AND :startTime IS NOT NULL
AND d.c4 <= :endTime AND :endTime IS NOT NULL
AND d.c1 = w.c1
AND UPPER(d.status) = 'CLOSED' ORDER BY to_char(status_date,'yyyymmddhh24') DESC
view link is based on column TIME123

Master table detail table with SQL based read only VO with bind variables

i have a page where i am displaying data as master table and detail table. both table VOs are based on SQL queries which use bind variables.
i have a view link between vos of type 1:M
i created master table detail table page by dropping detail iterator from data control panel under master and selecting master table detail table
on my page i see detail table records getting populated only for first record of parent table.
on changing parent record, child table shows same records and does not refresh
i am using partial triggers on both tables to be populated on a button click as i need to pass some bind variables to VOs which are taken as input from users
how can i show corresponding rows in detail table when parent record in table changes
is it possible declaratively to have master detail table view when both VOs have bind variables
jdev 11 1 1 5
these are the SQLs used
Parent SQL Based VO Query
SELECT to_char(d.status_date,'yyyymmddhh24') TIME123, count(DISTINCT d.c4)
FROM t1 d,
t2 w
WHERE w.c1 = nvl(:ou, w.c1)
AND UPPER(w.c2) = UPPER(nvl(:tt, w.c2))
AND d.c3 >= :startTime AND :startTime IS NOT NULL
AND d.c3 <= :endTime AND :endTime IS NOT NULL
AND d.c4 = w.c4
AND UPPER(d.status) = 'CLOSED'
GROUP BY to_char(status_date,'yyyymmddhh24') ORDER BY to_char(status_date,'yyyymmddhh24') DESC
Child SQL Based VO Query
SELECT w.c1,
w.c5 - w.c6 processing_time,
w.c3,
w.c6,
w.c7,
w.c8,
to_char(d.status_date,'yyyymmddhh24') TIME123 FROM t1 d,
t2 w
WHERE w.c2 = nvl(:ou, w.c2)
AND UPPER(w.c3) = UPPER(nvl(:tt, w.c3))
AND d.c4 >= :startTime AND :startTime IS NOT NULL
AND d.c4 <= :endTime AND :endTime IS NOT NULL
AND d.c1 = w.c1
AND UPPER(d.status) = 'CLOSED' ORDER BY to_char(status_date,'yyyymmddhh24') DESC
view link is based on column TIME123

Instead of doing the master-detail layout by dragging the details over, can you try a new page where you first drag the master VO over and then drag the detail VO over, and then set partialTrigger from the detail to point to the master?

3 Level Master-detail-detail data view implementation

Similar Messages

Maybe you are looking for