Master-detail-detail-detail-detail relationship.

Dear All,
I have 4 tables one is master and rest are details. I need to create master and detail grid display in single page. But the problem is that view link allows me to give one source and one destination.. i tried for one source and multiple destination but it disables the 'ADD' button in create view link wizard..
Pls can any one tell me is there any work around for this problem...
Regards,
Santosh.
Component     Version
=========     =======
ADF Business Components     11.1.1.59.23
Java(TM) Platform     1.6.0_21
Oracle IDE     11.1.1.4.37.59.23
Versioning Support     11.1.1.4.37.59.23

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

Similar Messages

  • Master-detail form (my detail is in a new canevas-- new window)

    Hello,
    I have a Master-detail form, in my detail when i select a row i want to show an other canevas that becomes a detail for this selected row. i constructed the relationship between my first detail block and my new canevas that contains the detail for the selected row. When I select a row Oracle didn't show me the deatil for this row in the other canevas, i wondered me why? because I thought the relationship between them should atomatically drive the data for the other canevas. If i 'm wong, does someone could tell me what to do to call my canevas detail.
    Master--->details(selected row become master)--->new canevas(contains details)
    the relationship is done between my first detail block and my new details block.
    Charly

    Hi,
    POST-QUERY is definitly the wrong trigger to do what you want to achieve.
    1. The usage of GO_BLOCK in POST-QUERY is not allowed and it will not work.
    2. The detail must be synchronized when navigating in the master-record, not when populating the block
    So the right trigger to do what you want to is the ON-POPULATE-DETAILS-Trigger.
    Problem on this: It will only work if you have a relation on the master-block to the detail block.
    But that's also possible even if you do not have a "direct" relation between the master and the detail block.
    Just create a relation between the blocks based on some dummy-item and then go to the item in the detail-block and set its property "Copy value from" to NULL.
    Now you can add your logic in the ON-POPULATE-DETAILS-Trigger.
    Still one problem left: Where is the window you're going to show placed? If it's on to of the window where the items from the master-block are displayed, then immediately after querying the records in the detail-block the navigation back to the master-block will cause the other window to be shown again (and therefore your detail-window to be hidden again).
    hope this helps

  • 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

  • How to create one master table and two detail for it

    I have one table , imagine it like mastertable( empid,deptid );
    and two different tables like employeetable(empid ) , departmenttable ( deptid )....
    I dont have any relation on database side. I need to create view link and ı need to use only one master table for two detail tables.
    How can ı manage this scenerio ?
    thanks...

    yes Shay ı really want to use two detail table in one UI as you suggest in your blog. But in that scenerio probably tables have link in database side with foreign key. My detail tables dont have any connection in database side with my master table. How can ı link them under one mastertableVO ?
    I am really sorry about my bad explanation. I am a newbie and probably ı dont know the correct words to tell my problem.
    Thanks for your time...

  • How I can acess to master entity object from detail entity object

    If I have two Entities Object, master and detail. How I can to access to any value in the master entity from the detail entity?

    User,
    If you create an association between them, you can go to the association editor (double-click the association) and use the Association Properties section to click the "Expose Accessor" checkbox(es). If you expose the accessor in the detail entity, the java class for your entity implementation will have a getMaster() method (named after your master entity) created for you.
    Hope this helps,
    John

  • How to delete the master records when corresponding details records exist.

    What is the SQL statement to delete the records of master when the corresponding detail records are present.
    Note: No Cascade clause was used at the time of creation of referential integrity constraint.
    "M"- Master Table
    "D"- Detail Table
    I used, "Delete from M cascade". This statement is not working.
    Your favour in this will be deeply appreciated.
    Cheers
    PremChin

    Hi folk,
    i appreciate your suggestion,
    my crux of the situation is to know whether there is a way to make it without disabling,removing or modifying the referential integrity constraint.
    If so, modifying, please help me out how to modify the constraint in order to remove the master records keeping detail records in-tact.
    Cheers
    Premz

  • Master Detail - Insert in Detail Table is not Working

    I am using Jdeveloper 11.1.2
    I have a very simple Master Detail Page with Masster Form and Detail Table. I have used Page fragments and called it from DynamicTab Shell. If I click on the button of CreateInsert Row in Detail Table, the detail Table stops rendering.
    If I use the same in a JSPX page it works fine but not in page fragments which I call in from DynamicTab Shell.
    The same forms worked well in JDeveloper 11g PS4 - 11.1.1.5.0
    Any help please ?
    Edited by: user465666 on Aug 9, 2011 6:35 PM
    Edited by: user465666 on Aug 9, 2011 6:40 PM

    Please explain clearly your problem

  • Oracle Forms : Master Detail : Cannot query detail block

    MY requirement is: when user enters records in master block, the corresponding records should be displayed in the detail block. (Detail block is just for viewing).
    Master block is a database block based on a custom table. All fields are enetereble in this block.
    Detail block is a a database block based on view which is built joining the custom table(on which master block is built) & a standard table. None of the fields in detail block are editable. they are just display only. For detail block, set the Key Mode=Non-Updatable, Enabled a field as Primary Key.
    I have created a relation between the 2 blocks. (Deferred=No, AutoQuery=No, Delete Record Behaviour=Isolated.). There is a join between master table & this view.
    But when I enter record in master block & save. the detail block records are not displayed. (Message : No Navigable Items in Detail Block).
    Yes, there are no navigable items in detail block, because its just for viewing purpose. How can this be achieved.
    Thanks,
    Naveen

    Thanks for your inputs. I got the solution for this. Earlier all items in the block were DISPLAY_ONLY. Now, I have selected them as TEXT_ITEMS (even though they are not updatable). It is working fine now. Thanks.

  • Is it possible to delete bank details in Mantain Insurance Relationships Proposal Pool?

    Hello,
    We are on SAPK-60614INISH (SAP healtchare Support Package 14)
    is it possible to delete bank details in Mantain Insurance Relationships Proposal Pool?
    In Mantain Insurance Relationships Proposal Pool, there is no button to erase bank details
    It is easier for the user to delete bank details in Mantain Insurance Relationships Proposal Pool than in FD02 Change
    Thanks in advance
    Best Regards

    To the best of my knowledge, not on an unjailbroken phone using the stock Messages app.

  • Master-detail report, hide detail on new search

    Hi, I'm newbie, so I need help. I have Master-detail report on same page. Master is interactive report, detail is SQL report which use hidden item as condition.
    For display detail data I use edit link. But I have problem when I make new search on master, detail still shows the old data.
    Can somebody tell me, how can I hide details , when I make new search on master? Or set hidden item to null, when I make new search?
    Example you can see in http://htmldb.oracle.com/pls/otn/f?p=51834:4 . Login : demo/demo
    Thanks
    Igor
    PS: Sorry on my broken English

    Hi,
    This can be achieved by doing something like the following:
    Have a single SQL statement that joins the two tables together. eg,
    select p.project_title,
    d.project_detail1,
    d.project_detail2,
    etc
    from projects p
    inner join details d on d.project_id = p.project_id
    This will provide a flat table with the project title in the first column for all records.
    Then, in the Report Attributes, you need to switch on Column Breaks:
    In the Break Formatting section, set Breaks to "First Column"
    In the When displaying a break column use this format, enter #project_title#
    In the Identify how you would like your breaks to be displayed, select "Repeat headings on break"
    Finally, clear the "Show" tick for the project_title column
    There's probably something you could do to improve formatting etc, but this should give you a start.
    Regards
    Andy

  • Matser Table/Detail Table -- Hide detail panel when no row

    Hi,
    I would like to hide the detail panel when the user selects a row in the master table without detail.
    I try to put something like this:
    <af:panelHeader
    rendered="#{bindings.MyView2.estimatedRowCount>0}">
    But it does not work, instead the previous detail rows are display when there is no detail rows for the master row.
    I need to to press a button <af:commandButton text="Apply change"/> , to render the page correctly.
    The selection facet used in the master table is defined as follow:
    <f:facet name="selection">
    <af:tableSelectOne autoSubmit="true"></af:tableSelectOne>
    </f:facet>
    Where am I wrong, it is my first project with ADF ?
    Any help will be appreciate,
    Thanks,

    Well not really clear if it's a bug or not, but here's two workarounds:
    1- the table is surrounded by a panelCollection, if we add a partial trigger from the panelCollection to the table, on every change of row selection the table refreshes itself.
    2- The second option was to remove the primary keys from the entity, and force it to use RowId as the primary key.
    This is such a weird behavior in ADF, it's one of the basic things that one will do in an application. We tried to do a test on a smaller app and it gave the same results.
    Here's the scenario:
    Master/detail linked by two keys
    Master PK (key1, key2)
    Detail PK (key1, key2, key3) => key1 and key2 are the link between the tables.
    If anyone can reproduce this and confirm if it's a bug, it would be greatly appreciated.
    Mo

  • Give me details about rule details functions conversion, currency etc in bi

    give me details about rule details functions conversion, currency etc in bi  when creating transformation

    Rule Type
    Use
    The rule type determines whether and how a characteristic or key figure, or a data field or key field is updated into the target.
    Direct Assignment:
    The field is filled directly from the selected source InfoObject. If the system does not propose a source InfoObject, you can assign a source InfoObject of the same type (amount, number, integer, quantity, float, time) or you can create a routine.
    If you assign a source InfoObject to a target InfoObject that has the same type but a different currency, you have to translate the source currency into the target currency using a currency translation, or apply the source currency.
    If you assign a source InfoObject to a target InfoObject that has the same type but a different unit of measure, you have to convert the source unit of measure into the target unit of measure using a unit of measure conversion, or apply the unit of measure from the source.
    Constant:
    The field is not filled by the InfoObject; it is filled directly with the value specified.
    Formula:
    The InfoObject is updated with a value determined using a formula.
    Read Master Data:
    The InfoObject is updated by reading the master data table of a characteristic that is included in the source with a key and a value and that contains the corresponding InfoObject as an attribute. The attributes and their values are read using the key and are then returned.
    The Financial Management Area characteristic is included in the target but does not exist in the source as a characteristic. However, the source contains a characteristic (cost center, for example) that has the Financial Management Area characteristic as an attribute. You can read the Financial Management Area attribute from the master data table and use it to fill the Financial Management Area characteristic in the target.
    It is not possible to read recursively, that is, to read additional attributes for the attribute. To do this, you have to use routines.
    If you have changed master data, you have to execute the change run. By reading the master data, the active version is read. If this is not available, an error occurs.
    If the attribute is time dependent, you also have to define when it should be read: at the current date (sy-date), at the beginning or end of a period (defined by a time characteristic in the InfoSource), or at a constant date that you enter directly. Sy-date is used as the default.
    Routine:
    The field is filled by the transformation routine you have written.
    The system allows you to select whether the routine is to be valid for all attributes for this characteristic, or only for the attributes displayed.
    Transformation rules generally only have one return value. If you select Return Table, the corresponding key figure routine no longer has a return value; it has a return table. You can then generate any number of values from a data record.
    For DataStore objects and InfoObjects: you cannot use the return code in the routine for data fields that are updated by being overwritten. If you do not want to update specific records, you can delete these from the start routine.
    If, for the same characteristic, you generate different rules for different key figures or data fields, a separate data record can be created for each key figure from a data record of the source.
    With InfoCubes: You can also select Routine with Unit. The return parameter 'UNIT' is then also added to the routine. You can store the required unit of the key figure, such as 'ST', in this parameter. You can use this option, for example, to convert the unit KG in the source, into tons in the target.
    If you fill the target key figure from a transformation routine, currency translation has to be performed using the transformation routine. This means that automatic calculation is not possible.
    Time Update:
    When performing a time update, automatic time conversion and time distribution are available.
    Direct Update: the system automatically performs a time conversion.
    Time Conversion:
    You can update source time characteristics to target time characteristics using automatic time conversion. This function is not available for DataStore objects, since time characteristics are treated as normal data fields. The system only displays the time characteristics for which an automatic time conversion routine exists.
    Time Distribution:
    You can update time characteristics with time distribution. All the key figures that can be added are split into correspondingly smaller units of time. If the source contains a time characteristic (such as 0CALMONTH) that is not as precise as a time characteristic of the target (such as 0CALWEEK), you can combine these characteristics with one another in the rule. The system then performs time distribution in the transformation.
    The time distribution is always applied to all key figures.
    Initial:
    The field is not filled. It remains empty.
    No Transformation:
    The key figures are not written to the InfoProvider.
    Unit of Measure Conversion and Currency Translation
    You can convert data records into the unit of measure or currency in the target transformation.
    Assigning InfoObjects for Converting Amounts or Currencies
    Use
    An InfoObject has to be assigned to a source field of a DataSource if currencies or units of measure need to be converted. The translation types require InfoObjects as input fields to carry out a conversion. You therefore have to assign the appropriate InfoObject to the source field.
    If the target has a fixed unit, you only have to assign an InfoObject if you want to carry out a conversion. Otherwise, you can select the No Conversion option.
    Procedure
    1.      You are in the rule details. Select the rule type Direct Assignment.
    2.      Select an appropriate key figure in the InfoObject Assignment field in the Source Fields of Rule area.
    3.      Choose the required conversion in the Currency field.
    4.      Choose Transfer Values.
    Example
    In your transformation, you want to assign the AMOUNT field of the DataSource to the FIX_EUR InfoObject in your target, carrying out a currency conversion. To do so, you assign the FIX_EUR InfoObject to the AMOUNT field in the rule details so that the currency can be read from the InfoObject.
    Hope this helps u...
    Regards,
    KK.

  • Report to display PO details and download details in an excel fil

    Hi,
    I have been asked to develop a report for "Develop report to display PO details and download details in an excel file".
    Could any one guide me technically what are the different tables i need to take to generate the report. Treat this is very urgent. Pls provide sample code too....
    Thanks in advance....

    Purchase Order PO
    Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO.
    refer this program
    REPORT ZPOCHANGE.
    This is a subroutine perform in the Purchase order Layout sets.
    Description :  To retreive the details of changed remarks in PO output and to capture the retrival date
                         Additional features with the previous changed appearing.  e.g. from .... to
    Note        :  If the latest modification details required
    Please Uncomment the lines mentioned under  'Last Modified Remarks only'
    Information
    /: PERFORM CHDATE IN PROGRAM ZPOCHANGE
    /:               USING &EKKO-EBELN&
    /:               CHANGING &RVDATE2&
    /: ENDPERFORM.
    /: IF &RVDATE2& EQ ' '.
    /  Revision Date: NIL
    /: ELSE.
    /  Revision Date: &RVDATE2&
    /: ENDIF.
    Main Window
    /E CHANGE_REMARKS
    /: PERFORM CHDET IN PROGRAM ZPOCHANGE
    /:            USING &EKPO-EBELP&
    /:            USING &EKKO-EBELN&
    /:            USING &T166T-CHTXT&
    /:            USING &T166T-CTXNR&
    /:            CHANGING &ITAB1-F_NEW&
    /:            CHANGING &ITAB1-F_OLD&
    /:ENDPERFORM.
    /:IF &ITAB1-F_NEW& NE ' '
    =  &ITAB1-F_OLD(C)& CHANGED TO &ITAB1-F_NEW(C)&
    /:ENDIF
    You might need to apply Note 373524 - Message determination and printing
    TABLES : CDSHW , "Change documents, formatting table
             CDHDR , "Change document header
             EKPO  , "Purchasing Document Item
             EKKO  , "Purchasing Document Header
             T166C . "Print-Relevant Purchasing Document Changes
    DATA   : ITAB1 LIKE CDSHW OCCURS 100 WITH HEADER LINE.
    DATA   : ITAB2 LIKE EKPO  OCCURS 100 WITH HEADER LINE.
    DATA   : DOCUM LIKE EKKO OCCURS 100 WITH HEADER LINE.
    DATA   : TABKEY LIKE CDSHW-TABKEY.
    data    : begin of ctab occurs 10,
              tname like t166c-tname,
              fname like t166c-fname,
              TABKEY LIKE CDSHW-TABKEY,
              FLAG(3),
              end of ctab.
    DATA   : VAL1(15), VAL2(15).
    DATA : M1(20), M2(10), M3(10),M4(5).
    DATA : RVDATE(10),RVDATE2(10) , EBELN LIKE EKKO-EBELN, COUNT TYPE I.
    Text number for change text(CTXNR), CHANGE TEXT(CHTXT), Purchase order
    Number and item number are passed from Layoutset
          FORM CHDET                                                    *
    -->  ITAB                                                          *
    -->  OTAB                                                          *
    FORM CHDET TABLES ITAB STRUCTURE  ITCSY
                      OTAB STRUCTURE  ITCSY.
      LOOP AT ITAB.
        CASE ITAB-NAME.
          WHEN 'T166T-CHTXT'.
            MOVE ITAB-VALUE TO M1.
          WHEN 'T166T-CTXNR'.
            MOVE ITAB-VALUE TO M2.
          WHEN 'EKKO-EBELN'.
            MOVE ITAB-VALUE TO M3.
          WHEN 'EKPO-EBELP'.
            MOVE ITAB-VALUE TO M4.
        ENDCASE.
      ENDLOOP.
    Throught this function change details are retrived into itab1.
      CALL FUNCTION 'ME_CHANGES_READ'
           EXPORTING
                DOCUMENT_CATEGORY = 'F'
                DOCUMENT_NUMBER   = M3
           TABLES
                XCDSHW            = itab1.
      SELECT SINGLE * FROM T166C WHERE CTXNR = M2.
      IF SY-SUBRC = 0.
        CONCATENATE M3 M4  INTO TABKEY.
    ********Last Modified Remarks only**********************
       read table ctab with key  tname  = T166C-TNAME
                                         tabkey  = tabkey
                                         fname   = T166C-FNAME.
       if sy-subrc ne 0.
        LOOP AT ITAB1 WHERE TABNAME = T166C-TNAME
                                      AND   TABKEY+3(15) = TABKEY
                                      AND   FNAME = T166C-FNAME.
    *********Last Modified Remarks only**********************
           ctab-tname  = t166c-tname.
           ctab-fname  = t166c-fname.
           ctab-tabkey = tabkey.
           append ctab.
          delete itab1.
          exit.
        endloop.
    Captured details are exported to Layoutset
        LOOP AT OTAB.
          CASE OTAB-NAME.
            WHEN 'ITAB1-F_OLD'.
              OTAB-VALUE = ITAB1-F_OLD.
              MODIFY OTAB.
              CLEAR : ITAB1-F_OLD.
            WHEN 'ITAB1-F_NEW'.
              OTAB-VALUE = ITAB1-F_NEW.
              MODIFY OTAB.
              CLEAR : ITAB1-F_NEW.
          ENDCASE.
        endloop.
      endif.
    ******Last Modified Remarks only****************
    ENDIF.
      clear ctab.
    ENDFORM.
          FORM CHDATE                                                   *
    -->  ITAB                                                          *
    -->  OTAB                                                          *
    Form for revision date retrival. PO no. is passed from layoutset
    and in the change document header latest modified date is captured
    and passed to revision date field in Layoutset.
    FORM CHDATE TABLES ITAB STRUCTURE  ITCSY
                      OTAB STRUCTURE  ITCSY.
      CLEAR : RVDATE, EBELN.
      LOOP AT ITAB.
        CASE ITAB-NAME.
          WHEN 'EKKO-EBELN'.
            MOVE ITAB-VALUE TO EBELN.
        ENDCASE.
      ENDLOOP.
    SELECT UDATE INTO CDHDR-UDATE FROM CDHDR WHERE OBJECTCLAS = 'EINKBELEG'
                                                       AND OBJECTID = EBELN.
        IF RVDATE < CDHDR-UDATE.
          RVDATE = CDHDR-UDATE.
        ENDIF.
        COUNT = COUNT + 1.
      ENDSELECT.
      LOOP AT OTAB.
        CASE OTAB-NAME.
          WHEN 'RVDATE2'.
         CONCATENATE RVDATE6(2) '.' RVDATE4(2) '.' RVDATE(4) INTO RVDATE2.
            IF COUNT = 1.
              RVDATE2 = ''.
            ENDIF.
            MOVE RVDATE2 TO OTAB-VALUE.
            MODIFY OTAB.
        ENDCASE.
      ENDLOOP.
    CLEAR : COUNT.
    ENDFORM.
    Message was edited by:
            Karthikeyan Pandurangan

  • How to getLine Details from Invoice Details window inside Service Contracts

    Working on 11.5.10.2 Service Contracts Module.
    Trying to retrieve Line Details from Invoice Details tab. Service Contracts Authoring > Invoice Details > Line Details. I have tried creating a join to oks_bill_transactions but this returns too many records, thousand of records for one contract. I then tried a join to oks_bill_sub_lines obsl,
    OKS_BILL_TXN_LINES obtl but this was returning too many records as well. Seeing if these are the correct tables to pull the line detail for Invoices from in the Service Contract module or if I may be setting up my joins incorrectly and that is why I am getting so many records returned?
    FROM OKC_K_HEADERS_B OKHB,
    OKC_K_PARTY_ROLES_B OKPRB,
    HZ_PARTIES P,
    OKX_CUST_SITE_USES_V C_BILL_TO,
    OKX_CUST_SITE_USES_V C_SHIP_TO,
    ra_customer_Trx_all rcta,
    okc_contacts oc,
    OKC_K_LINES_B oklb,
    OKC_K_LINES_B oklbs,
    --oks_bill_sub_lines obsl,
    --OKS_BILL_TXN_LINES obtl,
    oks_bill_transactions obt,
    okx_resources_v orv
    WHERE OKHB.ID = OKPRB.CHR_ID
    AND OKPRB.JTOT_OBJECT1_CODE = 'OKX_PARTY'
    AND OKPRB.OBJECT1_ID1 = P.PARTY_ID
    AND okhb.id = oc.dnz_chr_id(+)
    AND oc.jtot_object1_code (+) = 'OKX_RESOURCE'
    AND oc.object1_id1 = orv.ID1(+)
    AND OKHB.ship_to_site_use_Id = C_SHIP_TO.ID1(+)
    AND OKHB.bill_to_site_use_Id = C_BILL_TO.ID1(+)
    AND C_SHIP_TO.SITE_USE_CODE(+) = 'SHIP_TO'
    AND C_BILL_TO.SITE_USE_CODE(+) = 'BILL_TO'
    AND OKHB.SHIP_TO_SITE_USE_ID = C_SHIP_TO.ID1(+)
    AND OKHB.BILL_TO_SITE_USE_ID = C_BILL_TO.ID1(+)
    AND OKHB.STS_CODE = 'ACTIVE'
    AND p.party_id = C_SHIP_TO.party_id
    AND okhb.contract_number(+) = rcta.interface_header_attribute1
    AND rcta.cust_trx_type_id(+) = oklbs.attribute8
    AND oklbs.cle_id = oklb.id
    -- and oklbs.id = obsl.cle_id(+)
    -- and obsl.id = obtl.bsl_id(+)
    and obt.trx_number = rcta.trx_number(+)
    and oklb.line_number||'.'||oklbs.line_number <> '1.1'
    and nvl(okhb.contract_number_modifier,'-') = nvl(rcta.interface_header_attribute2,0)
    and OKHB.CONTRACT_NUMBER = 'VO-7128'

    You can redirect the resultos to a txt file:
    Open a command prompt as Administrator
    Enter the command and redirect it to a file, here is an example:
    tasklist /v > c:\results.txt
    When you Open the file, you should able to see the Process name, PID, User, etc.
    Good luck on that.

  • Report to get Asset Line item details & user id details

    HI All,
    Is there any report to get Asset No, Assets line item details & user Id details.
    Thanks in advance.
    Ava

    Hi,
    which user ID? User created? User last changed?
    You can enhance any standard report with individual fields, see WIKI entry [Include additional fields in Standard Fixed Asset ALV reports|https://wiki.sdn.sap.com/wiki/display/ERPFI/IncludeownfieldsinFI-AAstandardALV] and/or SAP note 335065.
    User who created the asset is field ANLAV-ERNAM.
    Regards,
    Markus

  • Employee Contact details and Project Details

    Hello Experts,
    I need some information about the Employee Contact details, its project details. i.e. The tables from which I can retrieve the required data.
    Is there any built in BAPI for the same??
    Please reply.
    Thanks,
    Prashant

    Hi Prashant,
    Contact details of the employee is hold in info type 105; i.e. table PA0105.
    For the project details, if you're using PS module, CNR2 transaction -> Capacity -> HRMS Button is used.
    Regards,
    Dilek

Maybe you are looking for