Summary-Detail Report

Hi Friends,
I have a Summary-Detail report.
The report has minimum 2 pages.
First page is Summary and 2nd onwards detail...
In the first page, i will print the summary of goods despatched along with the description of goods.
eg:
To
company
..address
Subject...
Body....
Package Type | Qty | Description
Carton | 10 | Contains 100 packs in each carton
............................................ To be delivered as separate packs
..............................................Handle with care.
Despatched date is 12-sep-2009
Pallets | 250 | Despatched date is 12-sep-2009
Tins | 2100 | Despatched date is 12-sep-2009
Signatory..... Date...........................
This is my report structure....Usually one id will have only one package type. But the description against
that ID is stored in a separate table and the each letter in the description is precious. The length of the description
can be 40 to 4000..User is allowed to enter the description as a multi -record or a single record.
In the report, pkg_type and qty is one repeating frame and description is another repeating frame.
I have to print as many characters in the first page can enclose and the remaining characters i need to print after the detail part.
As the description column can contain any no.of characters, i cannot handle it using no.of records...Because if i set to print
first 5 records in the first page and the remaining in last page using serial no.column, then there is a posssibility that the when it reached the third record, whole space is consumed and
report will get extended to second page, this should not happen...summary cannot be given in 2 pages...
Am new to reports..Kindly help me to solve this problem..
Regards
Dora
Edited by: Dora on Sep 30, 2009 8:50 AM

Thanks Lalitk,
As u said...I created a db procedure...becoz i want to make several this kind of report using same table.
For the proc. I gave max.no.of characters as parameter and it returns the two strings ,first with max. no of characters (concatenating the records if it does not reach the max.no) for first page and the other with remainging of the record(s) as string for second page...
Regards
Dora.

Similar Messages

Navigating from Summary Report to Detail Report in OBIEE 11g

Hi,
I have creted two reports.One corresponds to Summary and the other Detail.By clicking on one of the fields in
the Summary report the values are captured and then the detail report is displayed based on the values selected.
Now,What I need to know is whether I can populate the values I have selected in Summary Report(values correspond to only a single field) as some text in the Detail report.
I am using 11.1.5 just in case you need to know,but any help would be greatly appreciated.
Regards
Navin.G

another way if you want to stay in one document and continue to use drilling is to build 2 blocks and hide/unhide as you drill
block1 - shows your totals
block2 - shows the details
then use block hiding (see below) to cause block1 to disappear when you drill past a certain level. using the same (but opposite logic) you would have block2 appear
block hiding in webi - how to:
sadly webi doesnt have this feature directly the way that Crystal does but you can emulate it using SHOW WHEN EMPTY,block filtering and DrilFilters. The latter detects your level of drill.
block1 filter formula - return a TRUE result when DrillFilters tell you that you havent drilled into detail yet. Set SHOW WHEN EMPTY=No
when you do drill Block1's formula will be FALSE, the block will then technically be EMPTY and therefor wont show
Block2's filter logic will return FALSE when DrillFilters tells you that you are still on Block1's level of drilling. But when you drill Block2's level of drill, DrillFilters in Block2's filter formula will return TRUE and its rows will be returned. It wont be empty so it will show.

Report with Summary & Detail - Exporting to PDF in Crystal Report

Hi,
I am using Crystal Reports XI (release 2). I am trying out a report with Summary and Detail sections.
Requirement:
1.     Report should display both Summary and Detail Sections
2.     Summary section should be displayed first followed by Detail Section
3.     A field in summary section should have a hyperlink to Detail Section
4.     On clicking the hyperlink the user should be navigated to the corresponding detail record
5.     User should be able to download the whole report as a single PDF (i.e., both summary and detail together)
Implementation in Crystal Report:
This feature could be implemented using
a.     Linked On Demand Sub report
b.     Using Hide (Drill down ok) option
c.     Hyperlinks
Issue Faced:
I used the on demand sub report option. When i clicked on the sub report (hyperlink), the details get displayed. But the details get displayed in separate viewer and hence when we export to PDF both summary and detail are not getting exported together. User has to select each detail report and export to PDF. Is this a limitation in CR XI? - proprietary Crystal Report features, such as drill-down and on-demand subreports, are supported only in the native Crystal Report format. These special features are ignored when exporting a report to a non-Crystal format like pdf.
Is there any workaround for exporting both the summary and detail (in subreport) as a single PDF file?
Any help will be greatly appreciated.
Thanks,
Viji.

Hi
Hyperlink would not be a solution to what you are asking for.
If you want to see the records related to a particular employee id by clicking on emp id, you can try the below:
- Apply a group on employee id on the main report.
- Insert a subreport with the required fields and place it on the Employee id Group header. You can put a name of the subreport as "Check Employee details" or something else as per requirement and make it a on demand subreport.
- Link the subreport on Employee id.
Hope this helps!!!
Regards
Sourashree

Summary to Detail report

Main Report
======================================
Agent                                  10/27/10     11/12/10     11/22/10     12/16/10     Sum:
Agency ACH Correction                                                                             1          1
Agency Address Change                                              1     1
Agency Benefit                1                                         1
Agency Compliance                1                                         1
Agency New Contract                                    2               2
Sum:                                     2                               2     1     1     6
Detail Report
===================================================
WPS ID          Worklist          Account Number     Status     Team Code
8a888a44          Agency Compliance     316650011                          Complete     DFTINF
8a888a05          Agency Benefit     316649906                          Complete     CLMB
8a800013          Agency New Contract     483704070                          Complete     IMO
8a810032          Agency New Contract     483704070                          Complete     IMO
8a800001          Agency Address Change     000000000                          Complete     SYSTEM
8aa0000a          Agency ACH Corrections     999334444                          Complete     DSM
6
Will it be possible to achieve in xcelsius?For the Agent and Date in the "summary report" above it should display corrosponding number of Records in detail report in a spreadsheet component..
Can you tell me the steps..

User,
What is your name?
You could move the parameter/item to the detail page. Perhaps change it from a hidden item (if it is) to a visible item that users could select from. Then all you're doing when you come from the summary to the detail is setting that item's value.
Note that if the item changes pages you'll want to change the name of the item and therefore any references to it. To make sure you don't miss anything you'll want to run the app though Patrick's APEX Essentials: http://www.inside-oracle-apex.com/apex-essentials/ (this will be integrated in APEX 4)
Regards,
Dan
Blog: http://DanielMcGhan.us/
Work: http://SkillBuilders.com/apex/

Create Summary Report w/Detail Reports

I have created a detail report (or tab within the document) that shows the monthly revenue per customer & calculates average monthly revenue per customer. How can I create a summary report (tab within the document) that only shows the customer & the average revenue per customer (so it does not bring back multiple lines for each customer)? This would allow my users a quick view of the average rev per customer and then could go into the detail to see the monthly rev per customer.

Thanks everyone, sorry for not being more descriptive (obviously I'm new to this!). So in my document I have a simple table that looks something like this:
Name               Contract Date           Month                  Revenue
John Doe          3/1/2011                   April 2011            $1.00
John Doe          3/1/2011                   May 2011             $1.00
                                                                 Monthly Ave:     $1.00
Jane Doe          1/1/2011                   March 2011           $1.00
Jane Doe          1/1/2011                   April 2011              $1.00
Jane Doe          1/1/2011                   March 2011           $1.00
                                                                 Monthly Ave:     $1.00
The monthly Ave is a simple calculation (=ave) that I added when I split the table.
What I'd like to do is have another "tab" (report) in the same document that summarizes that data to be something like this:
Name          Contract Date          Monthly Ave
John Doe          3/1/2011              $1.00
Jane Doe          1/1/2011              $1.00

Hoe top create summary and detail report using ABAP QUERY

Hi ,
Can any one suggest me how to create summary and detailed report using ABAP Quey.
Regards,
Raghu.

Hi,
Table Declaration
tables:mara,mast.
*Declaring the internal table
data: begin of itab_new occurs 0,
      matnr like mara-matnr,     "Material No
      ernam like mara-ernam,     "Material Created by
      mtart like mara-mtart,     "Material Type
      matkl like mara-matkl,     "Material Desc
      werks like mast-werks,     "Plant
      aenam like mast-aenam,     "BOM created
      stlal like mast-stlal,     "Alternative BOM
      end of itab_new.
select-options: p_matnr for mara-matnr.
CODE A : Retrieving the data from the database
     select f~matnr f~ernam f~mtart f~matkl m~werks m~aenam m~stlal
     into table itab_new
     from mara as f inner join mast as m
     on f~matnr = m~matnr
     where f~matnr in p_matnr.
CODE B : Retrieving the data from the database.
    SELECT FMATNR FERNAM FMTART FMATKL MWERKS MAENAM M~STLAL
    INTO TABLE ITAB_NEW
    FROM MARA AS F INNER JOIN MAST AS M
    ON FMATNR = MMATNR
    WHERE F~MATNR = P_MATNR.
    SORT ITAB_NEW BY ERNAM.
loop at itab_new.
write:/5 itab_new-matnr,itab_new-ernam,itab_new-mtart,itab_new-matkl,itab_new-werks,itab_new-aenam,itab_new-stlal.
endloop.
*TABLES: MARA , MAST.
*DATA:BEGIN OF ITAB_NEW OCCURS 0,
             MATNR LIKE MARA-MATNR,
             ERNAM LIKE MARA-ERNAM,
             MTART LIKE MARA-MTART,
             MATKL LIKE MARA-MATKL,
             END OF ITAB_NEW.
   SELECT MATNR ERNAM MTART MATKL
   INTO TABLE ITAB_NEW
   FROM MARA
   WHERE MTART = 'T'
   ORDER BY MATNR ERNAM MTART MATKL.
*DATA: BEGIN OF ITAB OCCURS 0,
     MATNR LIKE MARA-MATNR,
     END OF ITAB.
Thank U,
Jay....

E-Mail Summary Report and Detailed Report Automatically

Hi, I have just started a new job (1st IT job since leaving college) and I've been told that our Small Business Server 2011 used to email a Summary Report directly to a specified email address, as well as a weekly Detailed Report to the same email address,
but that has stopped sending reports now. How do i make sure that the reports are automatically generated and sent out via email to the specified address. Any help would be great.

Hi,
Based on your description, I understand that there some issue occurred in Report feature in the SBS 2011.
On current situation, please refer to following steps and troubleshoot this issue. Then check if can help you.
1. Login the SBS server. Please open Windows SBS Console and select
Reports tab. In the Reports panel, select a report (Summary or Detailed), then View report properties. In Report Properties page, please select
E-Mail Options to check if had added the correct user account or e-mail address. Also please select Schedule tab, and check if had configured correctly.
2. Then manually click
Generate report option in Tasks. Please check if successfully generated the report. If not, please refer to following TechNet article and repair Monitoring and Reporting features in the SBS server. Then monitor the result.
Repair Monitoring and Reporting Features
in Windows Small Business Server 2011 Standard
3. If generated the report successfully, please manually click
Generate report and e-mail report option in Tasks. Then check if run successfully. Or any error message occurred?
4. If this issue still exists, please refer to following path: C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs and check if there has some log files
which be related to Report (Summary or Detailed). If has, please check if can find some more clues. Meanwhile, please open Event Viewer and check if find some relevant errors. Those may hope us to go further analyze.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Drilling down from Summary to detailed reporting.

Hello all,
I am sure this can be done in BW but I just dont know how we can do it.
My client requirement is when we run a report on the cube we see all the totals for commitement item (we have cmmt item hierarchy that we are using) and then we are at a particular cmmt item for eg Office supplies the total being $1000 they want to double click on the cmmt item (drill down) to see all the transaction for that particular cmmt item.
How can this be achieved ? Can we use RRI for this?
Someone please share some advice
Thanks in adavnce.
KM

Hello,
When I am done with rsbbs. And I open the summary report in Bex Analyzer now I want to see detailed transactions for a particular cmmt item. Do I have to double click on it or Do i have to right mouse click and say Go to -> Detailed report?
I tried both the things, when I double click it says no applicable data available. and when i do go to-> detailed report it takes me to the report but it shows me everything rather than only transaction for that particular cmmt item. How do we make that happen so that it should know I want to see data only for the cmmt item i click on?
Thanks,
KM

Summary and the Detail Report

Hi All,
I want to create a summary and detail report in two different layouts on one single report,based the input summary or the detail report shoud execute...,how to do the same.
Thanks in advance
C.Somasundaram

Hi,
bring your two different layouts in seperate frames and write format triggers on this frames to show or suppress them (depending on your input). Connect the two frames with an collabsing anchor.
Regards
Rainer

Drill down from Summary to Detail Report

BI Publisher 11g
I creating a set of reports consisting of a single summary report and several detail reports. The user should be able to click on a row in the Summary report and this will pass those parameters to the detail report. Detail report will now show with corresponding values selected in Summary report. Thanks in Advance!

Explain exactly how you create your 2 reports.
The second one must have "is prompted" filters if you want it to use the values of the first one.

Datawarehouse query detail report result doesn't match summary report.

Hello,
In our DW, we run a detail report query ( like below No. 1) , while in the summary report, in which the query is partially based on aggregated table T_AGG_UNC_GROSS (like below No.2), the query result doesn' match the query result of the details report. (supposed to match exactly)
To pick out the problem why summary report (like below NO.3) doesn't match details report. I put two filters in the details query with the filter is "year 2007", filter location is "California")
I can get 295 selected.
while I put above two filters in summary report, get no row selected.
I suspect aggregation table has some problem (wrong aggregated).
Is there any method I can pick out the problem behind?
thanks a lot in advance.
--1.detail report
select D1.c14 as c1,
D1.c13 as c2,
D1.c12 as c3,
D1.c11 as c4,
D1.c10 as c5,
D1.c15 as c6,
D1.c9 as c7,
D1.c8 as c8,
D1.c7 as c9,
D1.c6 as c10,
D1.c5 as c11,
D1.c16 as c12,
D1.c17 as c13,
D1.c18 as c14,
D1.c19 as c15,
D1.c4 as c16,
D1.c3 as c17,
D1.c20 as c18,
D1.c2 as c19,
D1.c21 as c20,
D1.c22 as c21,
D1.c1 as c22
from
(select /*+ full(T278878) full(T144662) full(T144546) full(T144557) full(T144665) full(T155155) */ sum(T144442.FINAL_BILL_AMOUNT) as c1,
sum(T144400.WRITE_OFF_AMOUNT) as c2,
case when T144416.FMCI_IND = 'Y' then 'Yes-fMCI' else 'No-fMCI' end as c3,
T144442.IS_FIOS_FLAG as c4,
T314105.DATE_DESC as c5,
T144442.CYCLES_DELINQUENT as c6,
T144590.DATE_DESC as c7,
T144564.DATE_DESC as c8,
T144557.LOB_CODE as c9,
case when T144442.IS_NEVER_PAY_FLAG = 1 then 'Yes-NP' else 'No-NP' end as c10,
T144416.CLASS_OF_SERVICE as c11,
T144416.ACCOUNT_NAME as c12,
T144416.BTN as c13,
T144416.ACCOUNT_NUMBER as c14,
T144634.ACCOUNT_STATUS as c15,
T144687.CSG_ID as c16,
T441666.DISCONNECT_REASON_DESC as c17,
T144612.LOB_CODE as c18,
T144612.STATE_CODE as c19,
T144640.DATE_DESC as c20,
T144586.PRIMARY_CIC_CATEGORY as c21,
T144586.SECONDARY_CIC_DESC as c22
from
V_D_STATE T144612 /* V_D_STATE_UNCGRO */ ,
D_DISCONNECT_REASON T441666 /* D_DISCONNECT_REASON_UNCG */ ,
D_CUSTOMER_SERVICES_GROUP T144687 /* D_CUSTOMER_SERVICES_GROUP_UNCGRO */ ,
V_D_ACCOUNT_STATUS_FINAL T144634 /* V_D_ACCOUNT_STATUS_UNCGRO */ ,
D_DATE T144640 /* D_DATE_UNCGRO */ ,
V_D_CARRIER_CODES T144586 /* V_D_CARRIER_CODES_UNCGRO */ ,
F_UNCOLLECTIBLES T144400 /* F_UNCOLLECTIBLES_UNCGRO */ ,
D_ACCOUNT T144416 /* D_ACCOUNT_UNCGRO */ ,
D_ACCOUNT_DETAIL T144442 /* D_ACCOUNT_DETAIL_UNCGRO */ ,
D_LINE_OF_BUSINESS T144557 /* D_LINE_OF_BUSINESS_UNCGRO */ ,
D_DATE T144564 /* D_DATE_UNCGRO_CONNECT */ ,
D_DATE T144590 /* D_DATE_UNCGRO_FINAL */ ,
D_DATE T314105 /* D_DATE_UNCGRO_DISCONNECT */
where ( T144400.ORGANIZATION_ID = T144612.ORGANIZATION_ID and T144416.ACCOUNT_STATUS_ID = T144634.ACCOUNT_STATUS_ID and T144400.WRITE_OFF_DATE = T144640.DATE_ID and T144400.CIC_CODE_ID = T144586.CIC_CODE_ID and T144416.CUSTOMER_SERVICE_GROUP = T144687.CSG_CD and T144400.ACCOUNT_ID = T144442.ACCOUNT_ID and T144400.ACCOUNT_ID = T144416.ACCOUNT_ID and T144400.DISCONNECT_DATE = T314105.DATE_ID and T144400.WRITEOFF_REFERRAL_IND = 'WRO' and T144416.DISCONNECT_REASON = T441666.DISCONNECT_REASON and T144612.U_STATE_DESC = 'California - BUSINESS' and T144640.YEAR_DESC = 'Year 2007' and T441666.DISCONNECT_REASON_DESC <> 'G' and T144416.FINAL_BILL_DATE = T144590.DATE_ID and T144416.CONNECTION_DATE = T144564.DATE_ID and T144416.LOB_ID = T144557.LOB_ID and T441666.DISCONNECT_REASON_DESC <> 'H' )
group by T144416.ACCOUNT_NAME, T144416.ACCOUNT_NUMBER, T144416.BTN, T144416.CLASS_OF_SERVICE, T144442.IS_FIOS_FLAG, T144442.CYCLES_DELINQUENT, T144557.LOB_CODE, T144564.DATE_DESC, T144586.PRIMARY_CIC_CATEGORY, T144586.SECONDARY_CIC_DESC, T144590.DATE_DESC, T144612.LOB_CODE, T144612.STATE_CODE, T144634.ACCOUNT_STATUS, T144640.DATE_DESC, T144687.CSG_ID, T314105.DATE_DESC, T441666.DISCONNECT_REASON_DESC, case when T144416.FMCI_IND = 'Y' then 'Yes-fMCI' else 'No-fMCI' end , case when T144442.IS_NEVER_PAY_FLAG = 1 then 'Yes-NP' else 'No-NP' end
) D1;
295 rows selected.
--2. aggregation table T_AGG_UNC_GROSS
create table T_AGG_UNC_GROSS parallel nologging as
SELECT a.account_id,a.ORGANIZATION_ID,a.UNC_LOB_ID,
MAX (a.WRITEOFF_REFERRAL_IND) AS WRITEOFF_REFERRAL_IND,
MAX (a.WRITE_OFF_DATE) AS WRITE_OFF_DATE,
COUNT (1) AS NO_OF_UNC,
MAX(a.DISCONNECT_DATE) as DISCONNECT_DATE,
sum(a.WRITE_OFF_AMOUNT) as WRITE_OFF_AMOUNT
FROM f_uncollectibles a
GROUP BY a.account_id,a.ORGANIZATION_ID,a.UNC_LOB_ID;
---3. sumarry resport (query)
select SUBSTR (f.WRITE_OFF_DATE, 5, 2)
|| '/'
|| SUBSTR (f.WRITE_OFF_DATE, 7, 2)
|| '/'
|| SUBSTR (f.WRITE_OFF_DATE, 0, 4)
writeoff_date,
'ALL CIC',
o.U_STATE_DESC,
s.U_ACCOUNT_STATUS,
rl.RISK_LEVEL,
d.Amount_Range_ID || ' - WR',
f.WRITEOFF_REFERRAL_IND,
fi.fios_flag_desc,
DR.DISCONNECT_REASON || '-' || DR.DISCONNECT_REASON_DESC,
b.BEHAVIOR_SCORE || ' - B',
cs.csg_cd || ' - CG',
CASE WHEN d.IS_NEVER_PAY_FLAG = 1 THEN 'Yes-NP' ELSE 'No-NP' END
AS Neverpay_Ind,
CASE WHEN u.FMCI_IND = 'Y' THEN 'Yes-fMCI' ELSE 'No-fMCI' END
AS FMCI_IND,
lob.DESCRIPTION,
COUNT (f.Account_id) No_of_Accounts,
SUM (d.NO_DENIAL_NOTICES) NO_DENIAL_NOTICES,
SUM (d.CYCLES_DELINQUENT) CYCLES_DELINQUENT,
sum(f.WRITE_OFF_AMOUNT) WRITE_OFF_AMOUNT ,
sum(d.FINAL_BILL_AMOUNT) FINAL_BILL_AMOUNT
FROM t_agg_unc_gross f,
d_account u,
d_account_detail d,
D_DISCONNECT_REASON DR,
d_writeoff_amount_range a,
v_d_account_status_final s,
D_BEHAVIOR_RANGE b,
v_d_state o,
d_Fios_Indicator fi,
d_risk_level rl,
d_customer_services_group cs,
D_UNCOLLECTIBELS_LOB lob,
D_DATE
WHERE f.account_id = u.account_id
AND u.account_id = d.account_id
AND d.Amount_Range_ID = a.wo_range_id
AND d.IS_FIOS_FLAG = fi.FIOS_FLAG
AND u.Account_Status_ID = S.ACCOUNT_STATUS_ID
AND u.RISK_LEVEL_ID = rl.risk_level_id
AND o.organization_id = f.organization_id
AND dr.DISCONNECT_REASON = u.DISCONNECT_REASON
AND d.BEHAVIOR_SCORE12 = b.BEHAVIOR_SCORE
AND u.CUSTOMER_SERVICE_GROUP = cs.csg_cd
AND Dr.disconnect_reason NOT IN ('H', 'G')
AND lob.LOB_UNC_ID =f.UNC_LOB_ID
AND o.U_STATE_DESC = 'California - BUSINESS'
AND D_DATE.YEAR_DESC = 'Year 2007'
and u.FINAL_BILL_DATE = D_DATE.DATE_ID
--and u.CONNECTION_DATE = D_DATE.DATE_ID
GROUP BY SUBSTR (f.WRITE_OFF_DATE, 5, 2)
|| '/'
|| SUBSTR (f.WRITE_OFF_DATE, 7, 2)
|| '/'
|| SUBSTR (f.WRITE_OFF_DATE, 0, 4),
'ALL CIC',
o.U_STATE_DESC,
s.U_ACCOUNT_STATUS,
rl.RISK_LEVEL,
d.Amount_Range_ID || ' - WR',
f.WRITEOFF_REFERRAL_IND,
fi.fios_flag_desc,
DR.DISCONNECT_REASON || '-' || DR.DISCONNECT_REASON_DESC,
b.BEHAVIOR_SCORE || ' - B',
cs.csg_cd || ' - CG',
lob.DESCRIPTION,
CASE WHEN d.IS_NEVER_PAY_FLAG = 1 THEN 'Yes-NP' ELSE 'No-NP' END,
CASE WHEN u.FMCI_IND = 'Y' THEN 'Yes-fMCI' ELSE 'No-fMCI' END;
no row selected.
Edited by: ROY123 on Jul 23, 2010 12:17 PM

fixed.

Passing parameter from Summary to Detail report

Hi,
I have a summary report that has ID. Clicking on ID leads ot detail report. However, the parameter stays on the detail report. I also want to enable stand alone viewing of the detail rpeort. How can that be achieved?
Regards

User,
What is your name?
You could move the parameter/item to the detail page. Perhaps change it from a hidden item (if it is) to a visible item that users could select from. Then all you're doing when you come from the summary to the detail is setting that item's value.
Note that if the item changes pages you'll want to change the name of the item and therefore any references to it. To make sure you don't miss anything you'll want to run the app though Patrick's APEX Essentials: http://www.inside-oracle-apex.com/apex-essentials/ (this will be integrated in APEX 4)
Regards,
Dan
Blog: http://DanielMcGhan.us/
Work: http://SkillBuilders.com/apex/

Grand total values are not matching with Detail report

Report has grand totals and when I drill to the detail report, grand total values are NOT matching with parent report totals, I did some analysis but I'm clueless on this issue.
Please provide your thoughts and insight on this issue..
Thanks

is your summary and detail reports hitting different facts, like summary hitting aggregate and detail report hitting it's corresponding detail level fact..?
if then,
From Front-end:
Fix the filter values in detail report that are passing from master report then try delete each columns then check the grand total. If you found your values is matching by deleting particular column then you need to investigate what is the issue around with that dimension table..
From Database side:
1. check first aggregate table has proper aggregate data of it's detail..
2. Take the detail report obiee generated query and try to comment each dimension table and it's corresponding joins to the facts, (before, this delete all the dimensional columns and other measures from select statement and put only that measure where you are getting wrong value, so that you need not to comment all the select and group by columns which saves your time.. ). Need to check by commenting each dimensional wid and it's table from clause, if you found that values is matching then there is some problem with wid columns data population in your ETL.
Is that BI-Apps project?
btw, whtz ur name?

How to get summary wise report?

hi experts,
i have report, AR Aging analysis, in this i have Base Date and Current date, based on these it calculates age and it shows that amount in that age column, in my report it showing detailed report, but i want summary report.
for example:
cust no., Bdate, Curr.date, Age,0-30,31-60
100,3/1/2008,3/31/2008,30,5000,0
100,3/12/2008,3/31/2008,19,2000,0
100,3/3/2008,3/31/2008,28,2000,0
like this it showing, but i want summary wise, that means it should be summarized based on customer number,
is it possible or not,
if it is possible please help to do this,
thanks in advance
venkat

Hi Venkat,
Summarization of report depends on the data and query structure, as the example you have stated in this you can see although its for the same customer but somewhere down the line for other fields its having distinct values. So this way's you cann not get the summraized data for customer.
if the report is somewhat like this :
cust no.,Age, 0-30,31-60
Then ur output wil be summarized for a particular customer.
100, 77, 90000, 0
Thanks
Dipika

How to display summary details at then end of a alv grid?

Hi.
i have a ALV grid with 4 columns.
also i need to print summary details at the end of the grid..
eg..
Total material cost 15.111
total labor cost        5.4444
total material burden 267.88
toal labor burden    253.66
How do i prinbt these details at then eend of a grid?/

Hi
Populate event END_OF_LIST into IT_EVENTS tab and use in the fun module
see the doc for population of different events to display the totals after grid
REUSE_ALV_EVENTS_GET
Description
This table tells ALV which events are processed by the caller by CALLBACK.
The table of possible events per list type can be initialized using the module REUSE_ALV_EVENTS_GET.
You can display the names of the constants in the type pools SLIS which represent the individual events using the individual test function in the function module
REUSE_ALV_EVENT_NAMES_GET. Only events with a form routine name are processed.
The table structure contains the fields:
     IT_EVENTS-NAME
Name of the Callback event.
Possible Callback events:
     Action
USER_COMMAND USING R_UCOMM LIKE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD
Process actions on the list
As this is a frequently-used Callback event, the form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_USER_COMMAND.
PF_STATUS_SET USING RT_EXTAB TYPE SLIS_T_EXTAB
If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
The STANDARD status of the function group SALV should be used as a template for a user-specific status.
As this is a frequently-used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
ITEM_DATA_EXPAND USING RS_SELFIELD TYPE SLIS_SELFIELD RFLG_ALL TYPE C
Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT.
Exit for passing item entries (ITEM table) for a header record which was expanded interactively by the user.
RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header which is to be expanded.
RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table. RS_SELFIELD is initial in this case.
CALLER_EXIT USING RS_DATA Is called at the beginning of the function module to make special settings. It is not usually used.
     List processing events
IMPORTANT: The application Callback routine must not manipulate the internal output table and/or its header record. This restriction applies to all Callbacks which are called in the list output and run under the 'List processing events'.
TOP_OF_LIST no USING parameter. Information output at the start of the list
END_OF_LIST no USING parameter. Information output at the end of the list
TOP_OF_PAGE no USING parameter
Equivalent to the list processing TOP-OF-PAGE event
END_OF_PAGE no USING parameter. Not available for hierarchical-sequential lists.
Information output at the end of a page. This is only called for printing.
TOP_OF_COVERPAGE no USING parameter
The selection information and list status are output together (if they exist) on a separate page by default. See also the documentation of the parameters:
IS_PRINT-NO_COVERPAGE
IS_PRINT-NO_PRINT_SELINFOS
IS_PRINT-NO_PRINT_LISTINFOS
IS_LAYOUT-GET_SELINFOS
The user can format the header area of the 'cover page' himself or herself by specifying a Callback routine for this event.
END_OF_COVERPAGE no USING parameter
Analogously to TOP_OF_COVERPAGE the user can add other information to the information output by ALV (selection information, list status) at this event.
FOREIGN_TOP_OF_PAGE no USING parameter
The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
FOREIGN_END_OF_PAGE no USING parameter
The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.
BEFORE_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
AFTER_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
     Internal use only
LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
R_INDEX LIKE SY-TABIX
R_INDEX_ITEM LIKE SY-TABIX
R_INDEX_SUM LIKE SY-TABIX
     IT_EVENTS-FORM
Name of the form routine which should be called in the calling program at the event.
Field_catalog:
Field catalog with field descriptions
2.7.1.     Description
Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields). A field catalog is required for every ALV list output.
The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module
See also the documentation of the function module REUSE_ALV_FIELDCATALOG_MERGE.
The minimal field catalog is documented under 'default'. The caller can use the other optional parameters to assign output attributes to a field which differ from the default.
A field catalog need not be built-up and passed explicitly only under the following conditions:
     The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE.
     all fields in this structure are to be output
     the structure name is passed to ALV in the parameter I_STRUCTURE_NAME.
See also the documentation of the IMPORTING paramter I_STRUCTURE_NAME.
Positioning
     row_pos (row position)
value set: 0, 1 - 3
Only relevant if the list output is to be multi-line (two or three lines) by default.
A multi-line list can also be defined by the user interactively if the default list is one-line.
The parameter specifies the relative output line of the column in a multi-line list.
     col_pos (column position)
value set: 0, 1 - 60
only relevant when the default relative column positions differ from the field catalog field sequence. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the field catalog field sequence.
Identification
     fieldname (field name)
value set: internal output table field name (required parameter)
Name of the internal output table field which is described by this field catalog entry
     tabname (internal output table)
value set: SPACE, internal output table name
This parameter is used in 'manual' field catalog build-up only for hierarchical-sequential lists.
Name of the internal output table which contains the field FIELDCAT-FIELDNAME.
Data Dictionary reference
     ref_fieldname (reference field name)
value set: SPACE, Data Dictionary field name
Name of the Data Dictionary field referred to.
This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
     ref_tabname (reference table/structure field name)
value set: SPACE, name of a Data Dictionary structure or table
Structure or table name of the referred Data Dictionary field.
This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
Reference to fields with currency/measurement unit
Each internal output table sum or quantity field whose decimal places are to be formatted appropriately for the unit in the list must follow the convention:
     the field is of data type QUAN or CURR (internal type P) (the field must really have this physical data type. Overwriting the physical data type with the parameter FIELDCAT-DATATYPE has no effect)
     There is a field in the internal output table which contains the associated unit.
     There is also an entry in the field catalog for the unit field.
(If the unit is not to appear as a column in the list, and cannot be interactively displayed as a column, e.g. because it is always unambiguous and is therefore explicitly output by the caller in the list header, the field catalog units field entry can take the parameter FIELDCAT-TECH = 'X'.
The association of a value field to a unit affects the output as follows:
     appropriate decimal places display for the unit
     an initialized field with a link to a non-initial unit is output as '0' for the unit (if FIELDCAT-NO_ZERO is initial). When this field is summed, this unit affects whether the units are homogeneous.
     an initialized field with a link to an initial unit is output as SPACE. When this field is summed, the unit SPACE does not affect the homogeneity of the units.
     When non-initial fields with an initial unit are summed, the unit SPACE is considered to be a unit.
Link to currency unit
     cfieldname (currency unit field name)
value set: SPACE, output table field name
Only relevant for amount columns with associated unit.
Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
     ctabname (internal currency unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
Link to measurement unit
     qfieldname (measurement unit field name)
value set: SPACE, output table field name
only relevant for quantity columns with unit link.
Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.
The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
     qtabname (internal measurement unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
Column output options
     outputlen (column width)
value set: 0 (initial), n
For fields with a Data Dictionary link this parameter can be left initial.
For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
initial = column width is the output length of the referred Data Dictionary field (domain).
n = column width is n characters
     key (key column)
value set: SPACE, 'X'           'X' = kex field (key field output in color)
Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
For exceptions see the documentation of the FIELDCAT-KEY_SEL parameter.
     key_sel (hideable key column)
value set: SPACE, 'X'
only relevant when FIELDCAT-KEY = 'X'
Key field which can be hidden interactively.
The key column sequence cannot be changed interactively by the user.
The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
     no_out (field in field list)
value set: SPACE, 'X'          'X' = field is not displayed in the current list.
The user can interactively choose the field for output from the field list.
The user can display the contents of these fields at line level using the 'Detail' function.
See also the 'Detail screen' documentation of the parameter IS_LAYOUT.
     tech (technical field)
value set: SPACE, 'X'          'X' = technical field
Field cannot be output in the list and cannot be displayed interactively.
Field can only be used in the field catalog (not in IT_SORT, ...).
     emphasize (highlight columns in color)
value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)
'X' = column is colored with the default column highlight color.
'Cxyz' = column is colored with a coded color:
     C: Color (coding must begin with C)
     x: color number
     y: bold
     z: inverse
     hotspot (column as hotspot)
value set: SPACE, 'X'
'X' = column cells are output as hotspots
     fix_column (fix column)
value set: SPACE, 'X'
Not relevant for block lists (output of several lists consecutively)
'X' = column fixed (does not scroll horizontally)
All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively. See also the documentation of the Layout parameter
IS_LAYOUT-NO_KEYFIX of the IMPORTING paramter IS_LAYOUT.
     do_sum (sum over column)
value set: SPACE, 'X'           'X' = a sum is to be calculated over this internal output table field.
This function can also be called by the user interactively.
     no_sum (sums forbidden)
value set: SPACE, 'X'          'X' = no sum can be calculated over this field, although the data type of the field would allow summing.
     input (column ready for input)
Function not available
Format column contents
     icon
value set: SPACE, 'X'           'X' = column contents to be output as an icon.
The caller must consider the printability of icons.
     symbol
value set: SPACE, 'X'          'X' = column contents are to be output as a symbol.
The internal output table column must be a valid symbol character.
The caller must consider the printability of symbols.
Symbols can usually be printed, but may not always be output correctly, depending on the printer configuration.
     just (justification)
value set: SPACE, 'R', 'L', 'C'
Only relevant for fields of data type CHAR or NUMC
' ' = default justification for this data type
'R' = right-justified output
'L' = left-justified output
'C' = centered output
The justification of the column header always follows the justification of the columns. Independent justification of the column neader is not possible.
     lzero (leading zeros)
value set: SPACE, 'X'
Only relevant for fields of data type NUMC
ALV outputs NUMC fields right-justified without leading zeros by default.
'X' = output with leading zeros
Note: If a NUMC field is output left-justified or centered by FIELDCAT-JUST, leading zeros are output. If the output of leading zeros is suppressed by a Data Dictionary reference ALPHA conversion exit, the output is always left-justified.
     no_sign (no +/- sign)           Only relevant for value fields
value set: SPACE, 'X'     'X' = value output without +/ sign
     no_zero (suppress zeros)           Only relevant for value fields
value set: SPACE, 'X'          'X' = suppress zeros
     edit_mask (field formatting)
value set: SPACE, template
template = see documentation of WRITE formatting option USING EDIT MASK template
The output conversion conv can be made by template = '== conv'.
Texts
The following text parameters should be specified for program fields without a Data Dictionary reference. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored. If the user changes the column width interactively, the column header text with the appropriate length is always used. The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
The 'long field label' is also used in display variant definition, sort, etc. popups.
     seltext_l (long field label)
     seltext_m (medium field label)
     seltext_s (short field label)
     reptext_ddic (header)
analogous to the Data element maintenance 'Header'
The specified text is not necessarily output in the list, an optimum among all texts is sought.
     ddictxt (specify text)
value set: SPACE, 'L', 'M', 'S'
You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
Parameters for program fields without Data Dictionary reference
see also 'Text' parameters
     datatype (data type)
value set: SPACE, Data Dictionary data type (CHAR, NUMC,...)
Only relevant for fields without Data Dictionary reference
Program field data type
     ddic_outputlen (external output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
     FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
     FIELDCAT-INTLEN = n
see also the documentation of the parameter FIELDCAT-INTLEN
n = external format field output length
The column width FIELDCAT-OUTPUTLEN need not be the same as the external format output length (FIELDCAT-DDIC_OUTPUTLEN).
     intlen (internal output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
     FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
     FIELDCAT-DDIC_OUTPUTLEN = n
see also the documentation of the parameter FIELDCAT-DDIC_OUTPUTLEN
n = internal format field output length
     rollname (data element)
value set: SPACE, Data Dictionary data element name
F1 help can be provided for a program field without a Data Dictionary reference, or F1 help which differs from the Data Dictionary help can be provided for a field with a Data Dictionary reference, using this parameter.
When F1 help is called for this field, the documentation of the specified data element is displayed.
If the FIELDCAT-ROLLNAME is initial for fields with a Data Dictionary reference, the documentation of the data element of the referred Data Dictionary field is output.
Others
     sp_group (field group key)
value set: SPACE, CHAR(1)
Field group key.
Keys are assigned to group names in the IT_SPECIAL_GROUPS parameter (see also the documentation of the parameter IT_SPECIAL_GROUPS).
When such an assignment is made in the field catalog and in IT_SPECIAL_GROUPS, the fields are grouped correspondingly in the display variant popup.
     reprep (Report/Report interface selection criterion)
value set: SPACE, 'X'
Prerequisites:
     The system contains the Report/Report interface (function group RSTI, table TRSTI)
     Parameter LAYOUT-REPREP = 'X'
(see also the documentation of the parameter LAYOUT-REPREP of the IMPORTING parameter IS_LAYOUT )
'X' = When the Report/Report interface is called, the value of this field is passed in the selected interface start record as a selection criterion.
2.7.2.     Default
     The following entries are usually sufficient for internal table fields with a reference to a field defined in the Data Dictionary :
     fieldname
     ref_tabname
Notes:
ALV gets the remaining information from the Data Dictionary.
If no relative column position (COL_POS) is specified, the fields are output in the list in the order in which they were added to the field catalog.
REF_FIELDNAME need only be specifid when the name of the internal table field differs from the name of the referred Data Dictionary field.
Information which is explicitly entered in the field catalog is not overwritten by information from the Data Dictionary.
Priority rule:
Entries in the field catalog have priority over differing entries in the Data Dictionary.
     The following entries are usually sufficient for internal table fields without a reference to the Data Dictionary (program fields):
     fieldname
     outputlen
     datatype
     seltext_s
     seltext_m
     seltext_l
Notes:
F1 help can be provided for program fields by assigning a data element to the parameter ROLLNAME.
If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and REPTEXT_DDIC contain appropriate field labels, the program field column headers are also adjusted appropriately when the column width changes.
Reward points for useful Answers
Regards
Anji

Summary-Detail Report

Similar Messages

Maybe you are looking for