Oracle ADF Master-Detail query

Hi I am using Jdeveloper 11.1.1.3.0, whenever I create master(Form)-detail(Table) relationship on JSF/view, in page defination files of same under the bindings section I found the bindings as
"*attributValue, action, tree*", but according to theory it should appear like "*attributValue,action, table*" so can anybody explain me why I am getting *'tree'* type binding insted of *'table'.*

Hi,
can you please elaborate a bit more on how do you expect to have attributValue, action, table instead of attributValue, action,tree ?
According to the following documentation, you should be expecting a tree:
http://docs.oracle.com/cd/E17904_01/web.1111/b31974/web_masterdetail.htm#BJEHGCFJ
http://docs.oracle.com/cd/E17904_01/web.1111/b31974/web_tables_forms.htm#CJADDIEJ
Can you please elaborate a bit more on your question?
Regards,
Dimitris.

Similar Messages

Adf master -detail data table

Hi,
I have adf master detail data table , I put af:selectbooelancheckbox and autosubmit is true in detail data table .When I click the detail table , valuechangelistener of the af:selectbooelancheckbox is runnig I don't want this situation. Is it possible to prevent this ?
regards,

Hi
I can't remove autosutmit = true because I handle the valuechangeevent in managedbean.Why master table event fire the valuechangeevent in detail table ? I check the submit source in managedbean but It doesn't prevent to fire valuchangeevent ? Is there any way except ignore autosubmit = true ?
thx,

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

Master-details query to XML file?

Hi:
I'm new in XML and Oracle. I want to create XML file from two tables (master-details).
I made a small serach and tried some examples:
Say we have these tables:
CREATE TABLE "TEST_XML"
(     "ID" NUMBER,
     "NAME" VARCHAR2(15),
     "AMOUNT" NUMBER,
     CONSTRAINT "TEST_XML_PK" PRIMARY KEY ("ID") ENABLE
CREATE TABLE "TEST_XML2"
(     "ID2" NUMBER,
     "NAME2" VARCHAR2(20),
     "AMOUNT2" NUMBER
ALTER TABLE "TEST_XML2" ADD CONSTRAINT "TEST_XML2_FK" FOREIGN KEY ("ID2")
     REFERENCES "TEST_XML" ("ID") ENABLE
INSERT INTO TEST_XML VALUES (1,'A',50);
INSERT INTO TEST_XML VALUES (2,'B',30);
INSERT INTO TEST_XML VALUES (3,'C',70);
INSERT INTO TEST_XML2 VALUES (1,'AA',10);
INSERT INTO TEST_XML2 VALUES (1,'AB',20);
INSERT INTO TEST_XML2 VALUES (1,'AC',20);
INSERT INTO TEST_XML2 VALUES (2,'BA',10);
INSERT INTO TEST_XML2 VALUES (2,'BB',20);
INSERT INTO TEST_XML2 VALUES (3,'CA',20);
INSERT INTO TEST_XML2 VALUES (3,'CB',40);
INSERT INTO TEST_XML2 VALUES (3,'CC',10);
I want a query to create XML file contains data from TEST_XML table and for each row the related data from TEST_XML2 table.
I did some tries (working in iSQL*PLUS):
SET SERVEROUTPUT ON
DECLARE
v_ctx DBMS_XMLGEN.ctxType;
v_file Utl_File.File_Type;
v_xml CLOB;
v_more BOOLEAN := TRUE;
BEGIN
-- Create XML document from query.
v_ctx := DBMS_XMLGEN.newContext('select id,name,amount,cursor (select id2,name2,amount2 from test_xml2 t2 where t2.id2=t1.id) val from test_xml t1');
DBMS_XMLGEN.setMaxRows(v_ctx, 10);
DBMS_XMLGEN.setRowsetTag(v_ctx, 'CLAIM');
-- Output XML document to file.
v_file := Utl_File.FOpen('TEST_DIR', 'test1.xml', 'w');
WHILE v_more
LOOP
v_xml := DBMS_XMLGEN.GetXML(v_ctx,0);
EXIT WHEN dbms_xmlgen.getNumRowsProcessed(v_ctx) =0;
Utl_File.Put(v_file,v_xml);
END LOOP;
Utl_File.FClose(v_file);
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE(SUBSTR(SQLERRM,1,255));
Utl_File.FClose(v_file);
END;
But hte output wasn't as I wanted:
<CLAIM>
<ROW>
<ID>1</ID>
<NAME>A</NAME>
<AMOUNT>50</AMOUNT>
<VAL>
<VAL_ROW>
<ID2>1</ID2>
<NAME2>AA</NAME2>
<AMOUNT2>10</AMOUNT2>
</VAL_ROW>
<VAL_ROW>
<ID2>1</ID2>
<NAME2>AB</NAME2>
<AMOUNT2>20</AMOUNT2>
</VAL_ROW>
<VAL_ROW>
<ID2>1</ID2>
<NAME2>AC</NAME2>
<AMOUNT2>20</AMOUNT2>
</VAL_ROW>
</VAL>
</ROW>
<ROW>
<ID>3</ID>
<NAME>C</NAME>
<AMOUNT>70</AMOUNT>
<VAL>
<VAL_ROW>
<ID2>3</ID2>
<NAME2>CA</NAME2>
<AMOUNT2>20</AMOUNT2>
</VAL_ROW>
<VAL_ROW>
<ID2>3</ID2>
<NAME2>CB</NAME2>
<AMOUNT2>40</AMOUNT2>
</VAL_ROW>
<VAL_ROW>
<ID2>3</ID2>
<NAME2>CC</NAME2>
<AMOUNT2>10</AMOUNT2>
</VAL_ROW>
</VAL>
</ROW>
<ROW>
<ID>2</ID>
<NAME>B</NAME>
<AMOUNT>30</AMOUNT>
<VAL>
<VAL_ROW>
<ID2>2</ID2>
<NAME2>BA</NAME2>
<AMOUNT2>10</AMOUNT2>
</VAL_ROW>
<VAL_ROW>
<ID2>2</ID2>
<NAME2>BB</NAME2>
<AMOUNT2>20</AMOUNT2>
</VAL_ROW>
</VAL>
</ROW>
</CLAIM>
Notice that for each details (from TEST_XML2) there is <VAL> tag which I don't need beside i want a query which is applicable on all environments.
May anyone help me please......
Regards,
Saad

The following looks like it produces your desired output. I used the WITH to simulate your two tables so I didn't have to CREATE them. This runs on 10.2.0.1. I'm not sure what bugs you are referring to as SQL/XML is stable in 10g that I have seen. I'm sure some bugs exist somewhere in it, just not with this usage. Just start with the SELECT statement to run on your system.
WITH test_xml AS
(SELECT 1 ID, 'A' name, 50 amount FROM DUAL UNION ALL
SELECT 2, 'B', 30 FROM DUAL UNION ALL
SELECT 3, 'C', 70 FROM DUAL),
test_xml2 AS
(SELECT 1 ID2, 'AA' name2, 10 amount2 FROM DUAL UNION ALL
SELECT 1, 'AB', 20 FROM DUAL UNION ALL
SELECT 1, 'AC', 20 FROM DUAL UNION ALL
SELECT 2, 'BA', 10 FROM DUAL UNION ALL
SELECT 2, 'BB', 20 FROM DUAL UNION ALL
SELECT 2, 'BC', 20 FROM DUAL UNION ALL
SELECT 3, 'CA', 20 FROM DUAL UNION ALL
SELECT 3, 'CB', 40 FROM DUAL UNION ALL
SELECT 3, 'CC', 10 FROM DUAL)
SELECT XMLElement("CLAIM",
         XMLAgg(
           XMLElement("ROW",
             XMLForest(id "ID",
                       name "NAME",
                       amount "AMOUNT"),
             (SELECT XMLAgg(XMLElement("VAL_ROW",
                             XMLForest(id2 "ID2",
                                       name2 "NAME2",
                                       amount2 "AMOUNT2")))
                      FROM test_xml2 t2
                     WHERE t2.id2=t1.id)
FROM test_xml t1This solution works in any environment where you can issue a SQL statement from, be it SQL*Plus, PL/SQL, Java, etc.

ADF Master Detail Forms

Hi,
We have a master detail views and the master detail relationship is working fine between the views. We have a requirement to display one master form and 2 detail forms (user has to see two detail forms) to the user. The default master detail relationships in ADF are displaying one master form and one detail form with the navigation controls. Can you please suggest ideal approach for displaying multiple detail forms.
We tried with the af:iterator for displaying details collection model as multiple forms. But the problem with the current approach, we are unable to get the reference to the detail record when a value is changed in the detail form.
<af:iterator id="i1" varStatus="vs" value="#{bindings.BillDetailVO11.collectionModel}" var="row">
<af:inputDate id="serviceDate"
label="Service Date"
value="#{row.ServiceDate}" *valueChangeListener="#{backingbean.myvaluechangelistener}"*
columns="9"/>
<af:inputText id="it1122" label="POS"
value="#{row.PlaceServiceCode}"
columns="4"/>
</af:iterator>
I am comfortable with the iterator approach if I can get the value of PlaceServiceCode for the same row in the detail form when the ServiceDate value changes. I am ready to try for alternative approaches for displaying multiple detail forms.
Thanks and Regards,
Prasad

Hi Shay,
Thank you for responding to my query. I followed the steps in the blog and created two detail forms. But both the detail forms are representing the same detail record. Our requirement is little different.
We have to create a master detail form (Bill Summary with Bill Lines) to edit the bill summary with lines and display two Bill lines along with summary to the user.If hte number of bill lines are more than 2 then we have to display navigation controls to the user to navigate across the bill lines.
As an example the form data comes from Bill_summary(Master) and Bill_Lines (detail) tables. If the number of Bill Lines are 5 then we have to display the form as follows. if the user selects next the form should display 2,3 lines, 3,4 lines etc.
BILL_SUMMARY
BILL_LINE 1
BILL_LINE 2
<Navigation control for the details>
Thanks and Regards,
S R Prasad

Oracle BI Master Detail RPT

Financials modules
Below is the report format and Example,
Account GRP1(1-4 BU) GRP(5,4) GRP(6-11) TTL GL_ITL DELTA
10121 $92 * 2 90 100 10
BU's are Business Units, Here Company i think,
Description: First column is account number, example is GRP1,BU,Account,Dept,Fiscal period
Account number is at master Level.When i click account number 10121, it should drill down to all the details or child which it makes 92 dollers.
Basically master detail report.But the format should be like this
The question is whether our datware house pre built is supported to do this type of report or we need to custom some thing from the dataware house.
What more information, i need to ask if i need more information from the client

The name of this forum is "Database - General"
The first line of your question indicates your question has nothing to do with the Oracle database.
Please change the subject to "Please Ignore" and repost your question in an E Business Suite forum.
Thank you.

Master/Detail query problem

I have two VO, masterVo and detailVo, which assoicated with a VL.
I create a page to query the masterVo and show the result master data and related detail data.
Can I add a query criteria to filter the detailVo?
Now I can only set where clauses in masterVo, is it possible to set where clauses both in masterVo and detailVo?

I don't use query region for my master/detail data query, because the query result is in hgrid region on the other page.
So I use controller to send the query criteria into AM for query. In masterVoImpl.java, I combine query
criteria to Where clauses to initiate query. I have one query criteria belong to detailVo attr, How can I put the detailVo criteria
and masterVo query criteria at one query?
Thanks a lot.
Louis

Adf Master-detail relationship

As per my requirement i have to use master-detail in my application.....
but we can drag as master-detail relation from Datacontrol palette .....but i don't want inbuilt function ......i want create same master detail relation ship programmatically .....
Thanks in advance

Hi Frank,
I have created master and detail within one form and one submit action to save the master and detail values in the form.Example: i am using oracle schema. i have used DEPT table and EMP table.
<af:form>
Master DEPT:
DEPTNO -- input value
DEPTNAME -- input value
Detail EMP:
EMPNO-inputvalue
EMPNAME-inputvalue
DEPTNO-input value (i[b] dragged the detail table and i included with in form, when i am running the page i am getting this detail dept no textfield prepopulated as deptno 20)
</af:form>
<commit button>(commit for entire master and detail. Need to save the master and detail after user filled the form)
Please guide me or help or provide solution to solve the problem.
Thanks & Regards
Arun

ADF Master Detail Insertion and updation

Dear All
I am developing a web application with the ADF using ADF BC4J as a buisness service and JSP as th view.
I am creating a Master detail page that makes the user add the ,master and the detail(s) information in the same page.
Example:
you may insert the department and the employess in that department in the same transaction (post) also the update

Two questions...
1. Will a future version of Jdeveloper support a drag and drop update-able multirow table?
2. The existing example of doing this (Without Jheadstart) behaves different than a single row input form, as Duncan Mills points out, in that it loses the values that are input if validation errors occur. This same thing happends in the JHeadstart workspace.
a) after running the code and just showing the bindings and form values, it appears a standard input form has the new values immediately after processUpdateModel(). Even if they are in error, and it later fails to make it through validateModelUpdates the values are retained.
b) in the Multi-row example, you can examine the form bean values (for the multiple rows), and examine the values from the rowset obtained through the DCUtil.findSpelObject() and JUCtrlValueBindingRef calls, and the bindings don't change. The validateModelUpdates still manages to produce the error though.
So, with a multi-row update form...
a) How do you get the ROW specific error msg generated from a declarative or method-based validator? - that is, put a msg in for the row like: You can't put XXX into this field.
Right now, we modified the BEAN to include an ErrMsg column and added that as a transient attribute to entity and view, and can display the messages via that by putting them in during the processUpdateModel(). Of course, most of the validation ended up in the processUpdateModel(), with none in the Entity.
b) Where are those values going if they are placed into the bindings as they can't be examined later after processUpdateModel?
Here's a method stub that we used to show values...
   * showFormValues retrieves the array of form beans as well as the
   * EmployeesView1.rangeSet, and displays the form values for Salary
   * and CommissionPct against the JUCtrlValueBindingRef (row-based)
   * bindings from EmployeesView1
   * @param actionContext
private void showFormValues( DataActionContext actionContext )
      DynaActionForm updateForm = (DynaActionForm) actionContext.getActionForm();
      UpdateRowBean[] updatedRows = (UpdateRowBean[])updateForm.get("Row");
      System.out.println("********** showFormValues **********");
      java.util.List origRows =
        (java.util.List) DCUtil.findSpelObject(actionContext.getBindingContainer()
                                             , "EmployeesView1.rangeSet");
      // Now loop through the bean array
      for (int i = 0; i < origRows.size(); i++)
         //Get the rowKey of the submitted updated Row
         String theRowKey = updatedRows.getRowKeyStr();
//Get the corresponding row from the origional set
JUCtrlValueBindingRef oldRow = (JUCtrlValueBindingRef)origRows.get(i);
//Check the update row needs processing and matches the source row
if (oldRow.get(JUCtrlValueBindingRef.RANGESET_ROW_KEY_STR).equals(theRowKey))
// Form value - does not appear to change
System.out.print( i + ": sal=" + updatedRows[i].getSalary() +
", comm=" + updatedRows[i].getCommissionPct() );
System.out.println("....Salary=" + oldRow.get("Salary") +
", CommissionPct=" + oldRow.get("CommissionPct") );
} // match on rowKeyStr
} // for i
System.out.println("************************************");
} // showFormValues

ADF-Master detail-Foreign key generated By Trigger won't propaget to Detail

Hi All,
We have Master-Detail Table where Master table key is generated by DB.
And this key act as Foreign key in detail table.When we Creates Master Table records and commit it .It gets saved correctly But when we navigate to Create Detail record (Cretae button is taken from Detail) It opens in Create mode but does n't poppulate Foreign Key.
Can anybody plz explain..
Regards
Yogesh

Hi Frank,
Thanks for your reply.I don't know "the ADF Business Components tester "
what is this ?
I was able to solve my problem by making "Refresh after insert " Check box selected in Entity object.Now it is generating Master Key and also i am getting it in Detail.
But now problem is, Can we make details record in insert mode by 'Create opration' under Master View.My requirment is insert two records in detail table in background while inserting record in master.Where relationship is maintained by foreign key which generated by trigger.
I want master and detail create form on same page where i will make details from Rendering False i.e both should be in Create mode (Accesser should not retrive record).
In Short
ADF-BC Master Detail - Detail Record insert in Back ground on the same page
Thanks in Adv
RHY

Master Detail Query automatic query ..Urgent help

In my last question, I asked about how to automatically query a form based on table or master detail and gota good answer. What I actually need to do is also query on the detail, for example
select a.user_id, b.week_ending,b.mon_hrs,b.tues_hrs
from emp_profile a, time_reporting_week b
where user_id = portal30.wwctx_api.get_user
and week_ending = '02-JAN-02'
and a.user_id = b.user_id
So I know that I can query on master table which is emp profile, but I also need to query on week ending which is in detail. Do I change the clause in my form pacjage?Or should I change something in Additional Pl/sql ??

There are two ways to achieve this. Both methods have some drawbacks, so please go through them and choose the one that suits you.
Method 1:
=========
This method does not require altering the form package.
Assumptions : The detail table has a column named WEEK_ENDING.
Steps :-
1> Edit the form and select the query button in the left frame of the master section.
2> For the pl/sql button event handler, choose the action as Query and replace the default code with the following :-
declare
l_where varchar2(4000);
l_where_pre varchar2(4000);
l_where_post varchar2(4000);
l_where_pos integer;
l_week_ending varchar2(4000);
l_lang varchar2(4000);
begin
p_session.get_shadow_value(
p_block_name => 'DETAIL_BLOCK',
p_attribute_name => 'A_WEEK_ENDING',
p_index => 1,
p_value => l_week_ending,
p_language => l_lang);
doQuery;
if l_week_ending is not null then
l_where := p_session.get_value_as_varchar2(
p_block_name => 'DEFAULT',
p_attribute_name => '_DETAIL_WHERE_CLAUSE',
p_index => 1
l_where_pos := instr(l_where,' WHERE ');
l_where_pre := substr(l_where,1,l_where_pos+6);
l_where_post := substr(l_where,l_where_pos+7);
l_where_post := 'week_ending = '||l_week_ending||' and '||l_where_post;
l_where := l_where_pre || l_where_post;
p_session.set_value(
p_block_name => 'DEFAULT',
p_attribute_name => '_DETAIL_WHERE_CLAUSE',
p_value => l_where,
p_index => 1);
QueryDetail(
p_mode => 'QUERY' ,
p_session => p_session);
end if;
end;
3> Click on OK to finish editing the form.
4> Run the form - enter query criteria for the master fields and enter the week-ending criterion in the 1st detail
field under Week Ending. Click the Query button.
Advantage:
You will not lose your changes even if you edit the form later on.
Drawback:
In this method, the querying process will be bit slow as we are querying for the detail records twice.
Once through onQuery and the second time after constructing the new where clause with the additional conditon
for the detail rows.
Method 2
========
This method requires altering the form generated package.
Steps :-
1> In the form package, you will find a onQuery procedure. Towards the end of the procedure, you will find a statement like
"_detail_where_cond" := "_detail_where_cond" || ' WHERE ' || ...
2> As the name of the variable suggests, this where condition will be used while querying the detail block. You need to
add a new clause to this for the week_ending column. Prior to that you need to fetch the shadow value for A_WEEK_ENDING.
3> Your altered code should look something like :-
p_session.get_shadow_value(
p_block_name => 'DETAIL_BLOCK',
p_attribute_name => 'A_WEEK_ENDING',
p_index => 1,
p_value => l_week_ending,
p_language => l_lang);
if l_week_ending is not null then
"_detail_where_cond" := "_detail_where_cond" || ' WHERE WEEK_ENDING = ' || l_week_ending || ' AND ' || --existing code
else
--- use the original code here
"_detail_where_cond" := "_detail_where_cond" || ' WHERE ' || ...
end if;
4> Compile the package body and run the form.
Advantage:
In this method we will be querying the detail rows just once. Unlike in method 1.
Disadvantage:
You will lose your alterations once you create a new version of the form by editing it. You need to recompile the package
after re-introducing your changes.

Data Template---master details query--Help

Hi
we are using XML Publisher attached to R12 , we are using data template ( .XML file) in data definition .
we have a requirement for master details report. for that we have parent query and child query .the data coming to parent query should be the parameter to child query
Exp-- Parent Query-- select empno from emp
Child Query --select * from dept where empno=:p_empno (p_empno =empno from Parent query )
For this requirement we are creating a data template (.XML file) . we are successfully to write for the parent query, but we fails when come to child query. Please help us how it can be wrote in data template . You can send any example related to this issue.

Parent Query - select empno as emp_no from emp
Child Query - select * from empno where empno=:emp_no

Oracle Portal master details default value set up.

Hi All,
Using Oracle Portal to create a master details form.
I have tried to set up the details table foreign key. I used the master table primary key as a default value for the details table foreign key.
Does anyone know what the correct syntax is when I fill in the Default Value field on the "Formatting and Validation Options for Detail Row" tab?
Also related to this: What should I choose from the drop down menu for the "Default Value Type"?
Best Regards.
Liviu Minda & Paul Williams
Cape Town City Council.

Hi Liviu & Paul,
NOTE: The following is applicable to Portal version 3.0.8 and above .
Well, if you want that the Detail table Foreign key should get the value of The Mater Table Primary key, then you need not do anything like setting the Default value for the Foreign Key of the Detail section. It works like this :-
Operation INSERT:
When you are INSERTing a master record and the corresponding detail records, just fill up the master form and need not worry about the Foreign key(FK) in the Detail rows. Fill up the other columns for the detail rows and choose the appropriate action for each of the detail rows i.e. INSERT and click on the SAVE button. If the FK in the Detail have been left blank, then while inserting into the detail table, the Primary Key (PK) value of the master will be picked up and inserted . However, if you specify any value in the FK column of the Detail, then the specified value would override the PK value of the master.
Generally, what ppl do is make the FK in the detail of type Hidden.. so users cannot tamper with the FK values.
Hope this helps.
null

ADF: Master Details Page

Hello,
I have just started out trying to develop an application in JDeveloper with ADF and I am coming from a Apex/Forms/PL SQL background. I am trying to develop an online application form for our Grants program.
The problem I am having is I have a master detail type page where I have a section D (Master) and then I have a breakdown of cost (detail). I have created a creation page for the section D and I have then another creation section on the same page for the breakdown of the costs by dragging the view that is under the section D view.
The problem is the detail section seems to be bring back the first record from the table. This is not what I expected as I would assume this to be blank record as we have a blank record in the master part.
Is there anyway around this where on startup the detail section brings up a blank record instead of the first record in the view?
Cheers in advance in any help on this matter.
Paul.

Most likely you dragged the wrong detail structure from the Data Control palette. When you created your Application Module, and added View objects to it, you would have seen a tree structure. Views will be listed separately, but if you have a View Link associating a detail view with its master, you will also see that view in the tree under the master. Something like this:
MyMasterView
MyViewLink
MyDetailView
MyDetailViewMake sure that this structure has been moved to the right side of your Application Module. There you will see something like:
MyMasterView1
MyDetailView2
MyDetailView1This is what creates the tree structure in the Data Control palette. When you created your master/detail page, you dragged MyMasterView1 for the fields from your master view. But you probably dragged MyDetailView1 for the details. This does not use the View Link to associate your details with the current master record. To do this, you must use MyDetailView2, which you will find by expanding the tree under the master.
Now, to get a blank record in the detail, you have to execute a Create action from that data control. You can drag a Create button to the page, and the user can press the button to get a blank record. Or you can cause a create action to happen whenever you enter that page.

ORACLE FORMS MASTER DETAIL HELP

GOT 2 DATA BLOCKS. 1 REPRESENTING ALL EMPLOYEES, THE OTHER REPRESENTING ALL SALARIES. uSING A MASTER - DETAIL RELATIONSHIP WHEN TRYING TO SHOW ALL SALARIES BESIDE ALL EMPLOYEES IN A MULTI-ROW TABULAR VIEW I CAN'T SEEM TO LIST THE SALARY FOR EACH EMPLOYEE ONLY THE FIRST...EG.
EMPLOYEE SALARY
|||||||||||||||||||||||| ||||||||||||||||||||
SMITH _____10000
JONES
REGERG
SDGS
SDFGSR
HOWEVER, AS I MOVE THROUGH THE EMPLOYEES THE SALARY CHANGES BUT STAYS AS THE FIRST ENTRY.... THANKS FOR ANY HELP OFFERED
Message was edited by:
user445629
Message was edited by:
user445629
Message was edited by:
user445629

You have master - detail relationship here. So unless you click on second employee it won't show you salary for second employee.
You can create a control block and capture values in this block through cursor. You can also create a view and get values from view. In both cases you need only one block not two.
Are you showing this only for display or user can also modify these values?

Oracle ADF Master-Detail query

Similar Messages

Maybe you are looking for