Master Detail Table: Please suggest best Layout design:
I have a Header table and linked with detail table. Lets Assume if I have a header table which has data as below:
Header Interface Data:(here I have lot of columns to be added scroll bar needed.
LedgerName , Periodname, Description , Total Count:
Data Eg: usa_ledger Jan-16 Error 10
Detail Interface Data: will have 10 rows with details of the Journals: (Scroll Bar needed)
Detail_Column1 .........................................DetailColumn N
I have single column list box showing Period Years, Period Months: User Upon clicking the mutiple Period Year Month we need the Header interface data to be displayed with Total count. Upon Clicking the Header interface data table we need to display the child records. Please suggest best bossible layout design. I am not sure what could be best to show Straight Table/Pivot Table.
Thanks in Advance and appreciate your suggestions and effort to help.
Thank You. I want to upload the QVW which has the data model of Month End Dash Board. But Actions to upload the file is not found to be enabled.Please advise how can I upload the file. I am so excited to share my qvw with all you people with nice good will to help.
The overview of Dashboard:(we are in Oracle Applications): We are looking for a dashboard build and which displays all details of the current month end closing accounting period status and the errors at one place.
This is Month End Dashboard layout design wherein we are pulling data across from Financials, Inventory and display accounting period status. If the period status is open then there will be Interface errors with summary of the total count and errors will be details. I have the data model ready by pulling the data via QVD and seems to be in good shape. What I struggle is the Layout design acceptable to our users. Can you please review my qvw and advise accordingly.
You have some crosstables within your datamodel which will work in general but the handling of them within the gui could be quite difficult - therefore I suggest to consider if a change of the datamodel wouldn't be more suitable: The Crosstable Load.