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

Similar Messages

Master-Detail query problem with composite key

I have tested a MD form with EMP and DEPT tables and the MD query works okay.
I have created two tables both with two fields EMP_ID and REPORT_DATE as a composite key. The problem I am having with the MD form is that it does not query back the results when I select the QUERY button. I have verified that the join is setup during the creation of the form.

I have recreated the form and the MD query works fine.

Master /Detail create problem

hi,everyone:
Firstly to say sorry for my bad English.
Now I have a question:
I'm working in JDeveloper 10.1.3 .The model layer is SessionEJB /Toplink ,and the view layer is JSF. I have a data structure :
HrUnit : Master
HrHuman : detail
HrKnowledge : detail
the <HrHuman>'s PRIMARYKEY is <ID>,and the <HrKnowledge>'s FOREIGN KEY is <RYID>.
and I want to make a page to insert a new row on <HrKnowledge>. I drag the <hrKnowledgeCollectionIterator> into the page as <ADF Creation Form>, the page run fine.
next step, I make <persistEntity> binding to the <submit button> and the parameters(entity) is
${bindings.hrKnowledgeCollectionIterator.currentRow.dataProvider}.
when i run the page , i get a wrong . i get the SQL in the <Unit of work > is
"INSERT INTO HrUnit ....."
i create a direct mapping for the detail's foreginkey in toplink,and when i "rebuild" the map ,it gives me a warning. This warning affect my custom code in EJB,it can't work correctly. So i can't use this way in my question.
Re: Master /Detail create problem
I beg your help.
Thanks. and very very thanks.

Hi,
I am not an expert in TopLink, but it appears to me that the TopLink model is causes your problems not ADF. There is a TopLink forum here on OTN that could give you a helping hand on this issue.
The following tutorial explains the use of TopLink in ADF
http://www.oracle.com/technology/obe/obe1013jdev/10131/10131_adftoplink/master-detail-edit_page_adf_toplink.htm
Frank

Binds in Master/Detail Reports: Problems and Solutions

I've been trying to use bind variables in the master report of master/detail reports with multiple detail reports; but, I've been getting a problem with the detail reports not displaying data.
Here's a sample sequence of events:
1) Select the master/detail report under User Defined Reports.
2) Connect to a DB (if necessary).
3) Enter any value(s) for the bind(s) for the master report.
4) Select a row in the master report.
5) The currently selected detail report displays column names and data.
6) Select a different detail report.
7) Nothing displays except column names.
8) Select a different detail report.
9) Nothing displays except column names.
10) Click the currently selected row in the master report.
11) Now the current selected detail report displays (column names and) data.
I have found that if, I am more selective with my bind variable names, I can get things to work as expected.
First, let me show an example of some SQL that was giving me problems.
Master Report:
select distinct OWNER
from SYS.ALL_OBJECTS
where (OWNER like :OWNER or :OWNER is NULL)
Detail Reports:select *
from SYS.ALL_OBJECTS
where OWNER = :OWNER
and OBJECT_TYPE = 'INDEX'replacing 'INDEX' with other values for the other detail reports.
(I did have this problem with other SQL too but hopefully this SQL will run on everyone's DB.)
The first solution I found was to change the name of the bind in the master to something like OWNER_BIND.
The second solution I found was to change the master to
select distinct OWNER as POWNERand change the detail reports to
where OWNER = :POWNERAnother solution might be to adjust the bind variable names' case, but I didn't look at that.
While I was trying different things to get this to work, one of the goofy things that SQL Developer did was add <binds>s to the <query>s of the detail reports in my UserReports.xml. IIRC, it even did this to a master/detail report that I was not editing. So, if you run into this problem, you might want to open your UserReports.xml and clean it up by hand. (Actually, that might be good advice for other problems too.)
Tip: I've had other problems with my User Reports such as disappearing reports; so, not only do I regularly make copies my UserReports.xml, I also save report(s) into separate XML files and use Tools > Preferences... > Database > User Defined Extensions to add REPORT-type extensions to SQL Developer. (Kris Rice talked a bit about REPORT-type extensions in this blog entry: http://krisrice.blogspot.com/2006/11/xml-extension-points-reports.html)
FYI: I'm using sqldeveloper-1.1.2.2579 on Windows XP w/ SP2. The DB is Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production.

Here is the complete XML exported from a problem report. If you want to use this, save it as an XML file then import that file from within SQL Developer (ie, right-click on User Defined Reports and choose Import).
Notice that there are <binds>s on the detail reports. They don't belong there; only the one on the master report belongs. (The <binds> is specified by the Binds tab when creating a report. They are for prompting the user for value(s) and you cannot do that in child reports.) Even if I removed the <binds>s from the detail reports before importing the XML file, I still see the problem. SQL Developer also ends up putting them back. I think that it might happen to each detail report individually as it is visited when using (ie, not editing) the master/detail report.
<?xml version="1.0" encoding="UTF-8" ?><displays><display id="" type="" style="Table" enable="true">
     <name><![CDATA[Sad]]></name>
     <description><![CDATA[]]></description>
     <tooltip><![CDATA[]]></tooltip>
     <drillclass><![CDATA[null]]></drillclass>
     <CustomValues>
          <TYPE>horizontal</TYPE>
     </CustomValues>
     <query>
          <sql><![CDATA[select distinct OWNER as OWNER
from SYS.ALL_OBJECTS
where (OWNER like :OWNER or :OWNER is NULL)]]></sql>
          <binds>
               <bind id="OWNER">
                    <prompt><![CDATA[OWNER (like)]]></prompt>
                    <value><![CDATA[NULL_VALUE]]></value>
               </bind>
          </binds>
     </query>
     <display id="null" type="Detail" style="Table" enable="true">
          <name><![CDATA[INDEX]]></name>
          <description><![CDATA[]]></description>
          <tooltip><![CDATA[]]></tooltip>
          <drillclass><![CDATA[null]]></drillclass>
          <CustomValues>
          </CustomValues>
          <query>
               <sql><![CDATA[select *
from SYS.ALL_OBJECTS
where OWNER = :OWNER
and OBJECT_TYPE = 'INDEX']]></sql>
               <binds>
                    <bind id="OWNER">
                         <prompt><![CDATA[OWNER]]></prompt>
                         <tooltip><![CDATA[OWNER]]></tooltip>
                         <value><![CDATA[NULL_VALUE]]></value>
                    </bind>
               </binds>
          </query>
     </display>
     <display id="null" type="Detail" style="Table" enable="true">
          <name><![CDATA[PACKAGE]]></name>
          <description><![CDATA[]]></description>
          <tooltip><![CDATA[]]></tooltip>
          <drillclass><![CDATA[null]]></drillclass>
          <CustomValues>
          </CustomValues>
          <query>
               <sql><![CDATA[select *
from SYS.ALL_OBJECTS
where OWNER = :OWNER
and OBJECT_TYPE = 'PACKAGE']]></sql>
               <binds>
                    <bind id="OWNER">
                         <prompt><![CDATA[OWNER]]></prompt>
                         <tooltip><![CDATA[OWNER]]></tooltip>
                         <value><![CDATA[NULL_VALUE]]></value>
                    </bind>
               </binds>
          </query>
     </display>
     <display id="null" type="Detail" style="Table" enable="true">
          <name><![CDATA[PACKAGE BODY]]></name>
          <description><![CDATA[]]></description>
          <tooltip><![CDATA[]]></tooltip>
          <drillclass><![CDATA[null]]></drillclass>
          <CustomValues>
          </CustomValues>
          <query>
               <sql><![CDATA[select *
from SYS.ALL_OBJECTS
where OWNER = :OWNER
and OBJECT_TYPE = 'PACKAGE BODY']]></sql>
               <binds>
                    <bind id="OWNER">
                         <prompt><![CDATA[OWNER]]></prompt>
                         <tooltip><![CDATA[OWNER]]></tooltip>
                         <value><![CDATA[NULL_VALUE]]></value>
                    </bind>
               </binds>
          </query>
     </display>
     <display id="null" type="Detail" style="Table" enable="true">
          <name><![CDATA[SEQUENCE]]></name>
          <description><![CDATA[]]></description>
          <tooltip><![CDATA[]]></tooltip>
          <drillclass><![CDATA[null]]></drillclass>
          <CustomValues>
          </CustomValues>
          <query>
               <sql><![CDATA[select *
from SYS.ALL_OBJECTS
where OWNER = :OWNER
and OBJECT_TYPE = 'SEQUENCE']]></sql>
               <binds>
                    <bind id="OWNER">
                         <prompt><![CDATA[OWNER]]></prompt>
                         <tooltip><![CDATA[OWNER]]></tooltip>
                         <value><![CDATA[NULL_VALUE]]></value>
                    </bind>
               </binds>
          </query>
     </display>
     <display id="null" type="Detail" style="Table" enable="true">
          <name><![CDATA[TABLE]]></name>
          <description><![CDATA[]]></description>
          <tooltip><![CDATA[]]></tooltip>
          <drillclass><![CDATA[null]]></drillclass>
          <CustomValues>
          </CustomValues>
          <query>
               <sql><![CDATA[select *
from SYS.ALL_OBJECTS
where OWNER = :OWNER
and OBJECT_TYPE = 'TABLE']]></sql>
               <binds>
                    <bind id="OWNER">
                         <prompt><![CDATA[OWNER]]></prompt>
                         <tooltip><![CDATA[OWNER]]></tooltip>
                         <value><![CDATA[NULL_VALUE]]></value>
                    </bind>
               </binds>
          </query>
     </display>
</display>
</displays>

Master-Detail commit problem

I have master detail scenario. I have two forms. First one for the master and the second for the detail. I am first inserting the master data and then i navigate to the other form to insert the detail data. If i make commit from the second form it works just fine, but i need to go back(using JSF navigation) to the first form and commit from there. When I'm doing that i get the following error: JBO-27102: Attempt to access dead view row
I need solution to this problem
Thanks
Edited by: user2136329 on Dec 3, 2009 3:44 AM

JBO-27102: DeadViewRowAccessExceptionReason: Trying to access a ViewRow which is part of an obsolete/invalid collection. This could happen if a reference to the ViewRow is held by some business logic while the containing view object was removed.
Solution: Find the referenced ViewRow either by re-querying or using findByKey methods to get a valid reference to the ViewRow.
>
How are you creating your detail row - when you are navigating back are you doing a form submit to make sure that the data is submitted to view object..? If yes, try to get the handle to detail viewobject instance to check it holds new rows before commit..?
~Krithika

Master Detail performance problem

I have a demo master detail application which was built using the Application Express Wizard (APEX v3.2) which is performing badly under a particular situation.
The master detail is a workers table (46000 rows, pk index on id) and a licence table (48000 rows, fk index on wkr_id)
The generated application opens with a multi row report from a workers table. Clicking on the edit button on a worker record takes you to a master detail page which is the worker record and one or more licence records.
If the report page is run and you click the edit button to go to the master detail page, then you click on the next and previous records buttons the performance is fast - around 0.3 seconds.
However if you use a search term in the report page to find workers by name. The report page renders quite fast but then clicking on the edit button to go to the master detail worker record page is slow - around 5.5 seconds at best. This scales badly too. Clicking next and previous buttons at this point is similarly very slow.
4 sql statements are appearing in V$SQLAREA when the next button is clicked as follows:
1. SELECT "ID", LEAD("ID",1) over (order by "ID") next, LAG("ID",1) over (order by "ID") prev
FROM "PROD"."WORKERS"
2. SELECT "ID","LIC_ID","SURNAME", "FIRST_NAME","OTHER_NAME",
FROM "PROD"."WORKERS" WHERE "ID" = :B1 FOR UPDATE;
3. SELECT "ID","LIC_ID","SURNAME", "FIRST_NAME","OTHER_NAME",
FROM "PROD"."WORKERS" WHERE "ID" = :B1;
4. SELECT NULL "CHECK$01", "ID" "ID", "WKR_ID" "WKR_ID", "LIC_NO" "LIC_NO", "ISSUING_STATE" "ISSUING_STATE"
FROM ( SELECT /*+(WORKER_LICENCES eli_wli_wkr_fk) */
"ID", "WKR_ID", "LIC_NO", "ISSUING_STATE"
FROM "PROD"."WORKER_LICENCES"
WHERE "WKR_ID" = :P2_ID)
These queries run like lightning when executed directly on the database and are as generated by the APEX wizard.
The same application generated in Oracle Forms 10 on the same database is super fast (< 0.2 seconds.)
Can anyone advise where the problem may lie.
Thanks
Phil Gray
Edited by: graypz on Aug 18, 2009 6:50 PM

Thanks for that Andy
This got me to thinking. The number of columns that I have shown is pruned down drastically from the actual 50 columns in the table - which would make indexing out of the question.
The classic presentation of the home page of the generated application allows a search field which does searching in any column for a search term :P1_REPORT_SEARCH. The region source query has a monster "where clause" to cater for that, something like this:
where (
instr(upper("LIC_ID"),upper(nvl(:P1_REPORT_SEARCH,"LIC_ID"))) > 0 or
instr(upper("SURNAME"),upper(nvl(:P1_REPORT_SEARCH,"SURNAME"))) > 0 or
instr(upper("FIRST_NAME"),upper(nvl(:P1_REPORT_SEARCH,"FIRST_NAME"))) > 0 ... etc for the whole 50 columns
Sure enough, when I run that query direct in the database it performs badly - around 4.5 seconds.
My first cut of a workaround is to restrict the columns that can be searched to those with an index (LIC_ID, SURNAME) and to remove the rest of the generated where clause. Then to edit the P1_REPORT_SEARCH label to say "Search for Lic Id or Surname".
This brings about an immediate sudden increase in speed of the query.
The next part is still unresolved. The master detail form "next" "previous" buttons do not perform too well - and the records are not in context of the search that was run on the home page. My workaround is to remove the buttons as I don't have enough knowledge to attack that yet.
I may be expecting too much of the APEX wizard, but hopefully someone can direct me to a way of resolving this.
Regards
Phil Gray

Master-detail form problem after upgrading to 4.1

Hello,
I have running Apex 4.0.2 instance on 11g2 database.
After upgrading to Apex 4.1 I have a problem with all Master-detail forms.
I'm able to open the one but detail region shows error 'failed to parse SQL query:
ORA-00923: FROM keyword not found where expected'.
All forms work correctly on 4.0.2 version.
If I migrate that 'SQL Query (updateable report)' region to 'Interactive report',
the form works fine on 4.1
What could be a problem?
Thanks
Sasa

Hi Patrick,
I tried to make test application (the one master-detail page).
But when I copy the page from my application to test application, copied page in test
application works fine and because of that I didn't import test application to apex.oracle.com
Strange thing is that the column in detail table FAK_ID in the page of original application has
defined default value (P108_ID) but in the copied page in test application that column doesn't have
defined default value!?
I don't know if it's expected behavior...
Anywav, even if I set default value of FAK_ID column in test application, application works as expected.
I tried upgrade to 4.1 Apex version for three time but unfortunately I always got the same error in the master-detail page.
BR
Sasa

Master/detail blocks problem

hi friends
i have a problem with master/detail blocks in my form.
i have two blocks one is master and the other one is detail
i made a relation between these two blocks
and my form works corectly
but when i am in enter_query mode ,my cursor cannot go to detail block.
so i can't search special records in detail block.
is there any way to search detail block's value in form builder?
is it true that in master/detail blocks we can serach records only in master records?
any help would be appretiated.
regards,
shoja.

When a Block is in Query Mode the cursor is restricted to it - there is nothing to stop you from Querying the Master and then navigating to the Detail and going into Enter Query mode in that block afterwards.
If you need to enter Query Criteria that applies to both the Master And Detail then you'll need to build a specialist query screen using a Non DB block that gathers all of the criteria and then uses SET_BLOCK_PROPERTY on both the master and the detail to define the required results.

Master detail refreshing problem

Hi,
below is my master - detail structure
main master(level1) based IDCODE table
   |
    -->sub master(level2) based on IDCODE table
           |
           -->detail(level 3) based on IDSUBCODE table
idno is the link between all three levelsnow iam getting problem at level2.when i create a record at level2...level1 is not pointing to my new record after commiting the record(even if query also manually)
thanks
KM

ok.
thereare two ways.
foriegn key in db. if u had means, it may exposed as view link in model layer. (as u know)
and if does not had that key means,.u may make associations or viewlink. to catch that.
so you are using viewlink.
that link based on same table.
make tie up like this
table1                        table1
||                               ||
    eid attribute                eid attribute.
    Did attribute                Did attribute.eid , Did should be primary key. no duplicates should not be there.
like this you can try.

Master-Detail Relationship problem

I've spent 1.5 days already trying to solve this problem. I'm creating a JClient application using BC4J with a Master-Detail relationship. The relationship between tables is a many-to-many thru an intersection table. I've gotten my master and detail data to show with columnar form data in the top(master) panel and table data in the lower(detail) panel. My problem is that each time I get a master record that contains more than one detail record, each time I click the next navigation button in the master pane it will remain on the master record for the number of detail entries. For example, if a master record has 3 children, then I must click the next button 3 times to move to the next master record. I know that it has something to do with the way the entities are joined but I can't figure out how to join them any other way. Can anyone give me a hint how I can make the master panel only show one record for each Master-Detail relationship (even though the intersection table says its a many-to-many)?
Thanks,
Mark

Apparently, I was making things much more complicated than they needed to be (rather, JDev was). My first attempt at MD relationships, I followed the examples in the help files. JDev created VO's, Entities, Assoc's, View Links, etc... Everything but the kitchen sink! After researching a bunch more, I found that the only thing I needed to do was to create my view objects to display exactly what I wanted to see in my panel regardless of whether it was a parent or a child. Once I had the view objects straight, then I could connect them using a view link and JDev handled the rest. Pretty slick but, I wish there was some better documentation. My next problem is that I'm trying to make this a Master-Detail-Detail-Detail window. The master needs to be a JComboBox, displays only a date, and needs to appear in the same panel as it's child. The 1st child will have a navbar that cycles through a bunch of orders based on the date from the combo box. The order panel's child is in the lower panel and displays the order detail items. It also has a navbar. The lower detail panel needs to have a split pane with the upper part showing the order detail and the lower part showing the materials used in making up that order detail item.
So far, I've got the first 3 parts done (ie. combobox, orders, and details). For the combobox, I used a JComboBox navigationbinding. It shows the correct date, but my control is always disabled. I can't figure out why the combobox is always disabled. The enabled property is set to true. Anbody have any clues?
Thanks,
Mark

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.

Master Detail Form - Problem using built in wizard

Hi There
We are working on Application express 2.2.
We are facing problems for a master detail form using Wizard. The
details are as follows : >>
1) Master table : TS_ENTRY_TXN
trans_id P.K.
2) Detail table : TS_ENTRY_TXN_DETAIL
a)trans_id
b)sub_trans_id Composite P.K.(trans_id,sub_trans_id) & these are
based on sequences.
If i try to build a master detail form using the Wizard, the options
for providing P.K. for master & detail are listed which we used.
As it is a master detail form, we want to carry trans_id to the detail
for updations/insertions which doesn't happen.
The MRU fails with oracle error :
Error in mru internal routine: ORA-20001: Error in MRU: row= 1,
ORA-01400: cannot insert NULL into
("TS_APEX"."TS_ENTRY_TXN_DETAIL"."ENTRY_ID"), insert into
"TS_APEX"."TS_ENTRY_TXN_DETAIL" ( "ENTRY_ID", "SUB_ENTRY_ID",
"SMR_ID", "TASK_ID", "SUB_TASK_ID", "TIME_SPENT", "REMARKS") values (
:b1, :b2, :b3, :b4, :b5, :b6, :b7)
Is there any other way to build master detail wihout wizard.
Could you please suggest us better way to complete this task.

If I'm reading this correctly, then one of the columns in your detail tables' primary key is also the foreign key pointing to your master table? If that's the case, then that's not supported by the wizard. For the wizard generated master-detail form to work properly, you'll have to have a foreign key column in your detail table which is not part of your detail table's primary key.
Hope this helps,
Marc

Master - Detail application problem navigation

Hello everyone
i have a problem with my proyect Master - Detail Application, i can't show more DetailViewController in the xcode 4.2.
in the MasterViewController have 4 options the first option show me a DetailViewController in the second option show me other DetailViewController, but the masterView must not do any navigation to DetailViewController only in the right of DetailViewController
best regards

What application?

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

Master/Detail query problem

Similar Messages

Maybe you are looking for