Adf master/detail-master/details

In my jspx page i have to use 3 adf table....(the relationship like first one is master and second is detail and third one should be act as a detail for 2nd table (master) )
like College id (1 st table)
dept id (second table )
students_id (third table )
i can create first two relationship with no issues ......but i dont know how to create this one deptid <----->students_id ?

Hi,
double click the ApplicationModule (assuming you use ADF BC) and select the data model entry. Then select the DepartmentsVO shown under the CollegeVO (right hand side). Now select the StudentsVO under the DepartmentVO in on theleft hand side and shuffle it over
Frank

Similar Messages

  • ADF master-detail master selection not updating detail tables properly

    Hi All,
    I am using JDev version : 11.1.2.0.0
    I created new Fusion Web Application Module. In that module I created a master-detail data model and added them to a page fragment with a query panel. When I run it as a separate module, It works perfectly and Master selection correctly updates detail tables.
    But when I integrate that module to another Fusion Application(Add application jar file to the Master Application libraries), Master-details master selection not updating detail tables properly. This problem occurred sequentially.
    The problem is that.
    After the page load, first selection of the Master Table works correctly and detail tables update correctly.
    But second selection doesn't work, means detail table doesn't get update according to the Master table.
    And again in the third selection works correctly.
    This happens in a sequential manner. I monitor the behavior using Firebug. Observations are as follows,
    When running correctly, Response of the Post Definition is
    <?xml version="1.0" ?> <partial-response><changes><update id="pt1:t1"><![CDATA[<div tabindex="0" id="pt1:t1" class="xpa xpi" _leafColClientIds="['pt1:t1:c1','pt1:t1:c2','pt1:t1:c3','pt1:t1:c4','pt1:t1:c5','pt1:t1:c6','pt1:t1:c7','pt1:t1:c8','pt1:t1:c9','pt1:t1:c10','pt1:t1:c11','pt1:t1:c12','pt1:t1:c13']"><div id="pt1:t1::ch" style="overflow:hidden;position:relative;width:1365px;" _afrColCount="13" class="xz4"><table class="xz6" summary="This table contains column headers corresponding to the data body table below" id="pt1:t1::ch::t" style="position:relative;table-layout:fixed;width:1365px" cellspacing="0"><tr><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th></tr><tr><th id="pt1:t1:c1" _d_index="0" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c1::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">DateFormat</div></th><th id="pt1:t1:c2" _d_index="1" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c2::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">DefinisionId</div></th><th id="pt1:t1:c3" _d_index="2" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c3::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldId</div></th><th id="pt1:t1:c4" _d_index="3" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c4::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldLabel</div></th><th id="pt1:t1:c5" _d_index="4" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c5::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldLength</div></th><th id="pt1:t1:c6" _d_index="5" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c6::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldOffset</div></th><th id="pt1:t1:c7" _d_index="6" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c7::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldOrder</div></th><th id="pt1:t1:c8" _d_index="7" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c8::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldStatus</div></th><th id="pt1:t1:c9" _d_index="8" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c9::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldType</div></th><th id="pt1:t1:c10" _d_index="9" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c10::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldTypeLen</div></th><th id="pt1:t1:c11" _d_index="10" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c11::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">IgnoreField</div></th><th id="pt1:t1:c12" _d_index="11" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c12::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">IsMandatory</div></th><th id="pt1:t1:c13" _d_index="12" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c13::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">RecordType</div></th></tr></table></div><div id="pt1:t1::db" class="xyx" style="position:relative;width:100%;overflow:hidden" _afrColCount="13"></div><div id="pt1:t1::sm" class="xzt" style="position:absolute;display:none"></div><div id="pt1:t1::ri" class="xyz" style="position:absolute;display:none;overflow:hidden"></div><div id="pt1:t1::dataW" style="display:none"></div></div>]]></update><update id="f1::postscript"><![CDATA[<span id="f1::postscript"><span id="f1::postscript:st"><input type="hidden" name="javax.faces.ViewState" value="!-75cc188st"></span></span>]]></update><update id="d1::iconC"><![CDATA[<span id="d1::iconC" style="display:none"><span id="af_table::disclosed-icon"></span><span id="af_table::undisclosed-icon"></span></span>]]></update><update id="javax.faces.ViewState"><![CDATA[!-75cc188st]]></update><eval><![CDATA[AdfPage.PAGE.__handleRichResponseAction('/MillenniumCSD-ViewController-context-root/faces/FileDefinition?_adf.ctrl-state=cmpl0ptfg_7');]]></eval><eval><![CDATA[AdfPage.PAGE.sendStreamingRequest("pt1:t1");]]></eval><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/dnd-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/nav-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/menu-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/table-SHERMAN-1147.js</extension><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/jquery-1.7.1.min.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/dis_contx.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/js/floating_bar_bottom.js');</eval><eval>if(self.window.name != "MillenniumDepository"){   self.location = "mcsd.html";   }</eval><eval><![CDATA[AdfDhtmlLookAndFeel.addSkinProperties({"af|table-tr-column-scroll-animation-duration":"300","af|table-tr-column-reorder-animation-duration":"600","af|table-tr-hover-highlight-row":"true"});AdfPage.PAGE.addComponents(new AdfRichTable('pt1:t1',{'rowSelection':'single','rowBandingInterval':0,'editingMode':'none','afrSelListener':true}),new AdfRichColumn('pt1:t1:c1',{'sortProperty':'DateFormat','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c2',{'sortProperty':'DefinisionId','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c3',{'sortProperty':'FieldId','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c4',{'sortProperty':'FieldLabel','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c5',{'sortProperty':'FieldLength','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c6',{'sortProperty':'FieldOffset','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c7',{'sortProperty':'FieldOrder','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c8',{'sortProperty':'FieldStatus','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c9',{'sortProperty':'FieldType','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c10',{'sortProperty':'FieldTypeLen','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c11',{'sortProperty':'IgnoreField','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c12',{'sortProperty':'IsMandatory','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c13',{'sortProperty':'RecordType','sortable':true,'minimumWidth':12,'rowHeader':false}));AdfPage.PAGE.__recordSessionTimeout(1800000, 120000, "http://127.0.0.1:7101/MillenniumCSD-ViewController-context-root/faces/FileDefinition");AdfPage.PAGE.__initPollingTimeout(600000);AdfPage.PAGE.clearMessages();AdfPage.PAGE.clearSubtreeMessages('pt1:t1');AdfPage.PAGE.clearSubtreeMessages('pt1:resId1');]]></eval></changes></partial-response>
    When not running correctly, Response of the Post Definition is
    <?xml version="1.0" ?> <partial-response><changes><update id="f1::postscript"><![CDATA[<span id="f1::postscript"><span id="f1::postscript:st"><input type="hidden" name="javax.faces.ViewState" value="!-75cc188st"></span></span>]]></update><update id="javax.faces.ViewState"><![CDATA[!-75cc188st]]></update><eval><![CDATA[AdfPage.PAGE.__handleRichResponseAction('/MillenniumCSD-ViewController-context-root/faces/FileDefinition?_adf.ctrl-state=cmpl0ptfg_7');]]></eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/jquery-1.7.1.min.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/dis_contx.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/js/floating_bar_bottom.js');</eval><eval>if(self.window.name != "MillenniumDepository"){   self.location = "mcsd.html";   }</eval><eval><![CDATA[AdfPage.PAGE.__recordSessionTimeout(1800000, 120000, "http://127.0.0.1:7101/MillenniumCSD-ViewController-context-root/faces/FileDefinition");AdfPage.PAGE.__initPollingTimeout(600000);AdfPage.PAGE.clearMessages();AdfPage.PAGE.clearSubtreeMessages('pt1:t1');AdfPage.PAGE.clearSubtreeMessages('pt1:resId1');]]></eval></changes></partial-response>
    I could not figure out what went wrong when integrating to another module.
    Can you please help me to rectify this problem.
    Thanks
    dk

    Hi,
    sound to be an implementation specific issue that is hard to comment on without knowing how to reproduce it. If you have a rerooducible test case based on the Oracle HR schema using JDeveloper 11.1.1.6, zip it up, rename the "zip "extension to "unzip" and sent it to the mail address you find in my OTN profile. If you don't have that test case, explain how this can be reproduced
    Frank

  • ADF BC - One Master and Two Detail pages How To?

    I have an existing ADF BC .jspx master-detail page that works fine. It shows one product as the master (read-only; no navigation controls) and assocatied customer feedback as the detail (multiple records; read-only.) Now I also want to compute some averages from the same table used to create the detail view object. I have created a second view object because this requires a separate query that calculates aggregate values. I want to take advantage of using view links so that this 2nd view object is automatically linked to the master record via the primary key.
    My question is how can I link this into the existing master-detail data control so that I can drag/drop it to include id on the existing .jspx page and the primary key linkages will be handled automatically?
    Tables
    Product
    Feedback
    View Objects
    ProductView
    FeedbackView
    FeedbackAVGView
    Current ViewLink
    ProductFeedbackViewLink = ProductView + FeedbackView
    Current DataControl
    ProductFeedbackViewLink-Instance
    Data Control is displayed on .jspx page; want to also include 3rd View Object, FeedbackAVGView, in the Master-Detail relationship and display on the .jspx page

    Thanks for the reply. The existing customer feedback view object displays the customer's text feedback (testimonials) - these will be displayed in a read-only table with multiple records.
    The new view object aggregates the ratings score from the customer feedback (same FEEDBACK database table) and will use a form to display the results (not multiple rows.) The PK is included in the aggregate view object query.
    Note there is already an existing viewlink between the PK (Master) and FK (Feedback) - in the data control, this viewlink is an instance of the Master View Object and the Customer Feedback View object. Now that I have created a third view object, should I create another View Link between the Master View Object and the Customer Feedback AVERAGES View Object? If I do this, how do I include it in the existing .jspx page? If I add this new View Link to the Application Module I will have two different Data Controls:
    Data Control #1: Master (Product) View Object + Customer Feedback View Object #1 (implemented as a master-detail read-only form/table on a .jspx page)
    Data Control #2: Master (Product) View Object + Customer Feedback AVG View Object #2
    I'm confused as to how to integrate the second customer feedback view object into the existing Data Control / Master-Detail read-only form/table on my .jspx page?
    thanks

  • ADF Master Table, Inline Detail Table - How to Scroll Range/Disclose Row

    JDev 10.1.3.2 ADF/BC
    I really need some help here. I've tried as many things as I could think of and I still cannot get this to work.
    Scenario: I have query/result page. User clicks a link in the result table to take him to another page. This page has a Master table, Inline detail table component (bound to a tree in the pageDef). Before the page renders, all I want to do is scroll the Master table to the current row (based on the previous query/result via invokeAction in pageDef) and disclose the inline detail. Simple, right? In addition, I'll need to scroll the inline detail to the current row as well.
    I would like to do this prior to the components rendering but would be interested in any coding to scroll and disclose.
    Thanks in advance,
    Tom

    I've come up with a solution to my problem. Unfortunately I'm not able to manipulate the table prior to rendering but this solution is probably the closest I'm going to get. Here is my code:
    I set up a af:poll component to fire once on my jspx.
        public void poll_PollListener(PollEvent pollEvent) {
            if (this.getFromProcess("unitRowKeyValue") != null) {
                int curIndx = this.getIteratorBinding("UnitsIterator").getRowSetIterator().getCurrentRowIndex();
                this.getUnitTree().setFirst(curIndx);
                if (this.getFromProcess("systemRowKeyValue") != null) {
                    this.getUnitTree().setRowIndex(curIndx);
                    DisclosureEvent de = new DisclosureEvent(this.getUnitTree(), true);
                    this.getUnitTree().queueEvent(de);
                this.storeOnProcess("renderPoll", false);
        }The setFirst method scrolls the table to the index specified. If the user, in my case, has selected a detail item (system), I want to disclose the detail. First I need to setRowIndex to the current index and then I fire a disclose event.
        public void unitTreeDisclosureListener(DisclosureEvent disclosureEvent) {
             if (disclosureEvent.isExpanded()) {
                 CoreTable coreTable = (CoreTable)disclosureEvent.getSource();
                 RowKeySet rks = new RowKeySet();
                 Object test = coreTable.getRowKey();
                 rks.getKeySet().add(coreTable.getRowKey());
                 coreTable.setDisclosureState(rks);
          }If I don't set the rowKey via the setRowIndex method above, the getRowKey does not return a valid rowKey. In my case, I only want one master row to be disclosed at a time.
    This all works great except for a bit of flicker to process the PPR request for the component.
    Next step is to see if I can scroll the Inline Detail table to the detail row selected in the Query/Result page.
    Tom

  • ADF 10.1.3: Simultaneous insert of Master and Multiple detail records

    Hi,
    I'm trying to implement an Insert page (JSP document) having a Master table form and Multiple detail records grid with a Pop up to insert Detail records into the grid.
    The user should be able to input Master record details, then Detail records one by one, and finally insert all into the database.
    I'm wondering how this could be done using the Drag n drop feature of ADF (with ADF faces, JSF and Toplink) to the maximum extent.
    Please give me a rough guideline on how this could be done.
    Thanks in advance
    Vikas

    Anyone???

  • 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 with multiple details

    (JHeadstart release 10.1.2.) I can make a master with multiple detail pages work (displayed on the same page or different pages), except under one condition. Assume the following situation:
    Master: View object A based on entity A
    Detail 1: View object B based on entity B with a modified WHERE clause
    Detail 2: View object C based on entity B (yes, same entity object as view object B) with a WHERE clause different than the one for view object B
    A one-to-many view link exists between view object A and view object B, and another exists between view object A and view object C. The query for each of the view objects is standard (i.e., no expert-mode queries). The master and the two detail view objects (via their respective view links) are assigned to an application module.
    I created a JHeadstart application structure file for the application module with Struts and UIX. I added view object A as the top group (table-form layout). I next added view object B as a detail group (form layout, same page) beneath view object A. I finally added view object C as a detail group (form layout, same page) beneath view object A (i.e., parallel to view object B). The module generated and built cleanly.
    I ran the application, entered a master record, and saved the data. When I pressed the button to create a new record for detail 1 (view object B), fields appeared for the pages for detail 1 and detail 2 (view object C), not just detail 1. Also, the value of the Descriptor Attribute from the master record that linked it to the two detail pages populated the corresponding field in both of the displayed pages for the detail records.
    This behavior does not occur if view object C (detail 2) is based on an entity different than view object B. Will JHeadstart allow a master to have multiple details where the details are based on the same entity object? Thanks.
    Ray

    Ray,
    Unfortunately I cannot reproduce the problem. I filled in the A, B and C using a scott/tiger schema as follows:
    A: Departments
    B: All employees having a salary &lt; 1000
    C: All employees having a salary &gt;= 1000
    Then I created an application module with one group having two subgroups everything same page, just like you specified. Everything seemed to work fine. Do you have any idea what's different in your situation.
    Aard-Jan van Kesteren
    JHeadstart Team
    Oracle Consulting

  • Creating a Master with Two Detail report style

    In a Group-Above report data model, how does one add a 2nd detail group appearing at the same hierarchial level as the 1st group?
    The report already exists with MASTER and detailA. I need to add detailB and tie it to MASTER just like detailA.
    |MASTER|
    |detailA||detailB|
    \-------/\-------/

    Amjad,
    Thanks for the reply. My question relates to your suggestion #1: How does one create detailB in the data model?
    The only thing I have been able to do is to create a 2nd query linked to the 1st query. This makes the data model look like it has two masters each with one detail. What I want is a single MASTER with two details.
    Are you suggesting that the only way to accomplish this is by having two queries, one linked to the other, as in the crude rendering shown below?
    |MASTER1||MASTER2|
    |DETAIL1||DETAIL2|
    The above would be displayed in the data model as follows:
    |__Q_1___||__Q_2___|
    |G_DETAIL1||G_DETAIL2|
    \----------------/\----------------/

  • Master-Detail and Detail-SubDetail navigation.

    Hi!
    I am facing an issue regarding navigation in a second (subDetail) level child table.
    I have Master-Detail-subDetail like lilnks of three VOs.
    I have created 2 VLs for Master-Detail and Detail-SubDetail.
    Now on my custom page, navigation is fine for Master-Details but for 2nd level navigation between Details-SubDetails is dependent on SingleSelection that i have used to display related reocrds in SubDetail table.
    Is there any way to display subDetails automatically (without using single selection) just like in Master-Detaills. Or at least on page load it display related records in all the tablelayouts.
    I'm using Header Layout for Master , Table layout for both Deatil and Sub Details VOs.
    Kindly help
    Regards.
    Abbasi

    Hi All!
    I think there is no solution to this problem, only single selection is the solution.
    If any one has anyother solution plz let me know.
    Thanks and regards.
    Abbasi

  • Master-Detail Relation- Detail records not displaying

    Hi All,
    I am working forms(10g) customization for an oracle applications. our requirement is to develop a new window(screen) which should display all the related child records for the master record in the main form on a button press.
    i have developed a new database block based on a vew and provided the relation with master block, and done the required customization.
    But, when i run the form, and clicked on button, it is giving an error
    FRM-40350 Query caused no records to be retrieved.below is the code that i have written on button click
    BEGIN
              IF event = 'WHEN-BUTTON-PRESSED'
              THEN
              SHOW_VIEW('XXSCP_GBL_CUST_PEGGING_CON');
              SHOW_VIEW('XXSCP_GBL_CUST_PEGGING_STK');
              app_window.set_window_position('XXSCP_GBL_CUST_PEGGING_WIN',
                                             'CASCADE',
                                             'XXSCP_GBL_EXCEP_DETAILS_WIN');
          SET_BLOCK_PROPERTY('XXSCP_GBL_EXP_DETAIL_V',NEXT_NAVIGATION_BLOCK,'XXSCP_GBL_CUST_PEG_V');                                        
          GO_BLOCK('XXSCP_GBL_CUST_PEG_V');
         -- fnd_message.DEBUG('before execute');
          EXECUTE_QUERY;
          :parameter.p_excep_detail := 'FALSE';
              ELSE
                   NULL;
              END IF;
              EXCEPTION
                   WHEN OTHERS
                   THEN
                   fnd_message.DEBUG('other error at button press'||SQLERRM);
              --     NULL;
    END;I am able to query records in my view from database, but not working when i run the form.
    ANy suggestion will be helpful.
    Thanks in advance,
    pavan

    Duplicate post -- Re: Master-Detail Relation- Detail records not displaying

  • Master-Details-Another Details doesn't display correctly

    Hi All,
    I'm currently encountering a problem when displaying the 'Another Details' in my page. Let me elaborate.
    I have this MotherVO which I linked with the ChildVO, and then I linked the ChildVO to the GrandChildVO. In my AM, I have added something like below.
    MotherVO
    --> ChildVO through MotherChildVL (1 to *)
    --> GrandChildVO through ChildGrandChildVL (1 to *)
    I have 2 pages, the first page I displayed the MotherVO and the ChildVO (everything display only), which is working fine. Then I'll go to the next page to add new row for the ChildVO. The second page have header region for the childVO and a tableRN for the grandchildVO. First time I add, its OK. The second time, I still displays the grandChildVO that I added previously. That's the problem.
    Since it is connected with the VL I assume that it can retrieve rows via the link attributes . Did I missed anything in setting it? Please help. Need to demo my pages asap.
    Thanks in advance.
    Message was edited by:
    maeve
    Message was edited by:
    maeve

    Thanks for the reply George.
    I have 2 pages, first page contains 2 table regions, one for master, one for detailA, it is working fine. In the detailA table region there's add new row button. when I clicked on the add button it will go to the second page. This second page contains the detailA header region and the detailB table region with the add action. Everything works fine in the first time I add a record for the detailA and detailB, then will go back to the first page. But when I would like to add another record, the detailB table region displays the previous record I added but the detailA is OK and is a new row.
    The detailB region retain what is previously added, but when I try to add new row for detailB, the id will be the same as the id of the new detailA, which is correct. DetailB region is displaying all the records. It doesn't filter the records thru the id given in the VL. VL should automatically detects it, right?

  • Master - some records : Detail - for only a few i(not all)records in master

    Hi
    I have a requirement like master and detail. However I do not wish to see the details of everything that is there in the master but only a few records (based on some criteria). Example:
    Id Desc Col3 Col4
    1 1 desc 1col3 1col4
    2 2 desc 2col3 2col4
    3 3 desc 3col3 3col4
    id col5 col6 col7
    3 abc def ghi
    4 4 desc 4col3 4col4
    How can I have such a layout in which detail shows details of only selected records present in the master?
    Any help appreciated big time.
    Thx!

    1. create two queries. master and detail and link on the fields of interest.
    2. on the layout, have repeating frames. one for the master and inside the master frame, a repeating frame for the detail.
    hope this is what you are looking for..

  • Master with many details

    Hello Marvel team and Others,
    Is it possible with thee html db wizard to create a page contaning a master with more than one details ?, I think no , please if No, can I do it manually ? Any ideas are welcome.
    This is my need :
    The same page mmust contain :
    udpatable items for the master
    updatabee report for each detail
    insert details for an existeing master
    delete details from an existing master
    insert a new master with his details
    deletee a master, of course with his details
    Jina.

    The Add Rows button submits the page and re-renders it with additional N rows in that region. Any changes made in that region will be saved.
    Perhaps what you need is some client-side DHTML/Javascript to dynamically add some rows in your tabular form.
    See
    Re: Copy Values From Tabular Form for a discussion about that and an example at http://htmldb.oracle.com/pls/otn/f?p=24317:227
    But all this is straying far outside the out of the box functionality and you have to write everything yourself. You should re-evaluate some of your business requirements before going down this path.
    In other words, having a master-detail-detail, all of them editable, one global SAVE button for all of them, client-side Add Rows functionality, and all on the same page...is a highly unusual UI.
    Good luck.

  • Examples of Master with multiple details

    Hi Leo,
    I want to create Master with multiple details
    I have been trying for the similar example (Master with multiple details) for long time.
    It seems in the following link, you have mentioned that you have done such examples.
    Examples/Demos of APEX applications with Master with Multiple Details.
    Can you please share the solution to my emaid address [email protected]
    Or can anybody help me to get such solution with examples step by step.
    I would highly appreciate for any help.
    Thanks.

    Ok, so here's the rundown.
    Create a page with one "master" html region. In that region create your standard text/date/etc. items. Make sure that one of these is a hidden key field that is the key linking the master and details portions. Use a calculation to pre-populate the field from a sequence (or whatever uniqueness generator you choose). It is important to generate this key up front for the processing.
    Next I created one report region for each detail table I wanted to link in. Make sure to count the total number of fields you want to work with and that the total is LESS than 50. This is critical. The report should be selecting the columns from APEX_COLLECTIONS for display and manipulation on the screen. It is best to explicitly associate these to the Javascript column numbers now. I used a process to pre-populate my detail entry areas with default values for ease. I also included a button to add a row to each area, but you have to be careful here to use a good combination of form attributes so that the page refreshes don't SUBMIT yet.
    Once you have a report region generated from APEX_COLLECTIONS, you have to create the update processes that pull the information from the user modifications into the collection. This is the trickiest part of the whole thing. You have to use the APEX_COLLECTION.UPDATE_ITEM method, and you have to refer to the JavaScript column numbers for the source value and the collection column number for the destination. It is really easy to get these confused - I advise putting this all into a document or on a whiteboard for reference.
    Once you have the update processes written (I prefer writing one update process per detail section), write your processes to write the data to the database. Again, I suggest one process for each detail table. Trigger them to fire on submit.
    I also suggest creating a debug page to display all of the various collections and to help keep things straight. Once you have one detail area working, it is easier to get the others working.
    If you need actual code snippets, let me know and I'll see what I can do.

  • Master Recipe details\ Inspection details based on the ECR number

    HI All,
    Could you please help me in finding one FM which gives Master Recipe details\ Inspection details based on the ECR number which is created in CC31.
    In the Transaction CC31 for a given Change Number,  there is a Master Recipe and Inspection in the Objects button -> Task list . We need Master Recipe and Inspection details associated with that particular change number.
    Awaiting your response
    Thanks,
    Chetan

    HI,
    Check this FM MRTRS300_MASTER_RECIPE_READ

  • Master with two details(child) relation?

    Hi guys,
    I 'd like to have a Form with one master table and two detail tables.
    The business component wizard doesn't allow
    me to create this relation.
    Although these two details table are logically children of the master but have not defined specifically Foreign key for them on table/database level.
    I created Associations via JDev3.1 to join
    these master with details, but still business
    component wizard didn't allow me to have
    one master and two details.
    Do i have to create foreign keys to join children to master on database level or
    I can create an association with JDev? How?
    Thx
    Ali
    null

    You could use "New"/"BC" and create a ViewLink with the same name as the FK Assoc. If you edit the PackageModule, you should be able to see your FK link in there.

Maybe you are looking for