Cumulative totals question

Hi
I have a design question on cumulative totals.
I have Material, Plant and 0CALDAY as Characteristics and Total receipts and Total demand as key figures coming from data source.
On day1 I get beginning inventory from Material master. Ending inventory for day1 is Beginning inventory+Total receipts u2013 Total demand.
On day2 beginning inventory will be day1u2019s ending inventory.
I have to use Beginning inventory and Ending inventory in other calculations. I couldnu2019t do directly in BEx directly.
Please give your suggestions how I can achieve this.
Thank you
Sree

Hi Sree,
This is the Forum ....
I wud suggest this way...
1)Create a query Via APD (Go thru APDs in case you are not aware)
2)Store the data in a WO-DSO
3)Create a cube and push the data to cube via STD DSO with Key fields as Material, Plant and 0CALDAY.
4)Do reporting from there.
5)Create a PC and trigger the data daily ,store the data in this flow.
By this way we can store the data and do reporting on this.
Cube>Query>APD>WO-DSO>STD-DSO>Cube>Query..
Come back if u hve any issues....
Rgds
SVU123

Similar Messages

Performance of cumulative total and caching

Hi all
I'm having some trouble with performance when using the cumulative total function from AWM in derived measures.
For some of our measures we store a delta, i.e. the change from the previous actual and an initial state as the first delta. From this we can work out the actual value at any point by doing a cumulative total across the entire range. For this i've used the cumulative total function in the calculated measure wizard in the AWM.
Would any one know the implementation specs for this algorithm?
In the AWM XML it does not have an OLAP DML formula, instead it seems to use a bibeans definition with oracle.dss.selection.calcStep.TimeCumulativeTotalStep as some sort of working class.
I expected from the 'step' function that the cumulative total would be worked out as we go i.e. work out total for 1st month, then for the second month take this result and add the delta from the second month. For third month add third month's delta to second month and so on. This would make the performance linear as you do one cache hit (for previous total) one read (for delta) and one calculation per month added.
However i get these kind of numbers for years returned against query time.
1 year- 1 second
2 years - 5 seconds
5 years - 46 seconds
The results show non linear growth which when you do query over 10 years cripples the system.
Its looking like the cube is either working out each total from scratch and as such later years must add up more deltas or the cached total is being missed (if using the algorithm above) and hence must be recalculated, resulting in the same behavior as above.
NB i've fully aggregated my cube so no aggregation is being done up to the month/week level.
Can anyone tell me what's going on here, is it a poorly coded algorithm or are there some settings in olap that i need to modify to improve performance?
My recourse at the moment is to retrieve all the deltas and do my own linear cumulative total in pl/sql, however as other calculated measures rely on these totals, I'd have to recode all of our calculated measures in pl/sql which seems wholly redundant.
I'm on 10.2.0.1, using an all sparse cube with compressed composites, time is my first dimension in the order.
PS on my first run of doing the cumulative total in pl/sql i retrieved 10 years worth of deltas and totalled them in 0.2 seconds.
This is opposed to 395 seconds for 10 years using the inbuilt olap function!
Message was edited by:
Block

I think have seen this type of issue before where the calculated measures do create performance issues. This does seem to mainly affect time based calculations and I think this is because there is specific processing that occurs for time based calculations to manage the default time levels of day, week, month, quarter and year.
It is possible to create your own custom formula via DML to perform a cum. total. However, you will need to create some additional objects within your AW to manage the relationships between the levels within your time dimension.
Using the common schema sample that is shipped with BI10g I produced the following report:
limit time to '1803';
limit time add descendants;
limit time keep time_levelrel 'CAL_MONTH';
RPR DOWN TIME -
W 30 TIME_LONG_DESCRIPTION -
W 10 D 0 <CUMSUM(SALES_REVENUE, TIME, TIME.QTR) -
CUMSUM(SALES_REVENUE, TIME, TIME.YR)>;
This creates a running total for both quarter and years.
January 03 2,077,440 2,077,440
February 03 4,435,069 4,435,069
March 03 6,093,747 6,093,747
April 03 1,573,273 7,667,020
May 03 3,285,001 9,378,748
June 03 4,925,472 11,019,219
July 03 1,891,216 12,910,434
August 03 3,796,132 14,815,351
September 03 5,827,050 16,846,269
October 03 1,722,615 18,568,884
November 03 3,441,748 20,288,017
December 03 5,373,679 22,219,948
this requires two additional dimensions and associated relations to manage the reset process:
If you need quarterly balances:
DEFINE time_quarter text dimension
DEFINE TIME.QTR RELATION TIME_QUARTER <TIME>
limit time to time_levelrel 'CAL_QTR'
MNT TIME_QUARTER MERGE VALUES(TIME)
limit time to time_levelrel 'CAL_MONTH'
TIME.QTR=time_parentrel
If you need yearly balances:
DEFINE TIME_YEAR TEXT DIMENSION
DEFINE TIME.YR RELATION TIME_YEAR <TIME>
limit time to time_levelrel 'CAL_YEAR'
MNT TIME_YEAR MERGE VALUES(TIME)
limit time to time_levelrel 'CAL_MONTH'
TIME.YR=TIME_PARENTREL(TIME TIME_PARENTREL)
LIMIT TIME TO TIME_LEVELREL 'CAL_QTR'
TIME.YR=TIME_PARENTREL(TIME TIME_PARENTREL)
If you just need to create totals reset at the year level then the formula would be:
CUMSUM(SALES_REVENUE, TIME, TIME.YR)
I don't think I can post the XML for the custom calculation template into this posting as I think it gets filtered out. Send me an email ([email protected]) and I will send you the XML template for creating a custom calculation that can be imported into AWM.
Hope this helps
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/

Creating a cumulative total by day measure which resets each month.

Hi,
I need to creative a cumulative total measure (or calculated column) which accumulates my revenue sales for each day in a month, but resets each month.
I've created an example below:
The dates are from a linked date table and are based on a fiscal year. When the months are collapsed the months can either accumulate or stay fixed to the max for the month, that does not affect me.
I have tried various attempts using the guides below and I'm sure the answer is there but I can't get the filtering right.
I can get it to work but accumulate since the start of my data but this is not what I need.
http://www.daxpatterns.com/cumulative-total/
http://javierguillen.wordpress.com/2012/11/28/running-total-techniques-in-dax/
Thanks.

It appears that your months align with the standard calendar's months. I.e. your fiscal calendar's October always aligns with regular October. If this is the case, then you can simply use the built-in time intelligence function TOTALMTD().
MTD Measure:=
TOTALMTD(
[Measure]
, DimDate[Date Field]
If this is not the case and your month does not always line up with the standard calendar month, you can implement identical behavior with this FILTER():
Custom MTD Measure:=
CALCULATE(
[Measure]
, FILTER( ALL( DimDate )
, DimDate[Month Number] = MAX( DimDate[MonthNumber] )
&& DimDate[Date Field] <= MAX( DimDate[Date Field] )
Both of these will give identical behavior:
At the day level, they will show the running total for the current month, including the current day.
At the month level, they will show the total for the month.
At the quarter level and above (semester, year, decade, ...) they will show the total for the last month in that period. E.g. for a standard year, they will show December's total.
If these don't work, please provide more details about your date dimension, your data model, and how you are constructing your pivot table, preferably all in the form of a copy of your workbook on OneDrive or similar.

Cumulative totals in report

Hi,
I've a table having customer code, customer name, dr_cr, amount fields
SELECT a.CUCODE, a.cuname, a.DR_CR,
decode(a.DR_CR,'D',a.AMOUNT) Debit,
decode(a.DR_CR,'C',a.AMOUNT) Credit,
nvl(decode(a.DR_CR,'D',a.AMOUNT),0)-nvl(decode(a.DR_CR,'C',a.AMOUNT),0) Total,
a.narration1
FROM Tablename a
ORDER BY a.CUCODE
I want to show cumulative totals for each row that is debit-credit amount. Is that possible, if yes, how?
Thanks and Regards,
Sudha.

Sudha,
You must have missed the analytical query that Denes had mentioned. You need to use SUM( ) OVER () to make things work. I have modified your query as below. There could be syntax issues, which you may have to fix.
SELECT x.CUCODE, x.cuname, x.DR_CR,
       decode(x.DR_CR,'D',x.AMOUNT) Debit,
       decode(x.DR_CR,'C',x.AMOUNT) Credit,
       x.Total,
       x.narration1,
       SUM(x.total) OVER () running_total
FROM (
    SELECT a.CUCODE, a.cuname, a.DR_CR, a.amount,
           decode(a.DR_CR,'D',a.AMOUNT) Debit,
           decode(a.DR_CR,'C',a.AMOUNT) Credit,
           nvl(decode(a.DR_CR,'D',a.AMOUNT),0)-nvl(decode(a.DR_CR,'C',a.AMOUNT),0) Total,
           a.narration1
    FROM Tablename a
) x
ORDER BY x.CUCODEYou may also want to read this article:
http://www.oracle.com/technology/oramag/code/tips2005/062005.html
Thanks.
Ravi

How to calculate a cumulative total in HANA

Hello,
I have a detail table (e.g. GL line item table) which has entries for 'posting date', account number, year, month, posting amount (single key figure) and account type (whether the account is a profit & loss account or a balance sheet account.
The requirement is to create a view which shows balance of month for profit and loss accounts and cumulative balance per month for balance sheet accounts (i.e. total of all line items till end of the month, not just for the month).
Currently I am able to get only balance for the month , but not the cumulative balance.
How can I calculate a cumulative amount column/key figure - either through Analytical view or calculation view?
Thanks,
Ninad

The Window Functions should help. Here is a sample query in SPS06 using a sum over function against an SAP HANA Live standard view.
SELECT Year("BillingDocumentDate_E") as "Invoice_Year", "BillingDocumentDate_E" as "Invoice_Date", round("TotalNetAmount_E") as "Billed_Amount",
round(Sum("TotalNetAmount_E") OVER (partition by Year("BillingDocumentDate_E") order by "BillingDocumentDate_E")) as "YTD_Amount"
FROM "_SYS_BIC"."sap.hba.ecc/BillingDocumentQuery"
WHERE "SAPClient" = '004' and "SoldToPartyName" = 'Becker Berlin' and "BillingDocumentDate_E" >= '2002-01-01'
GROUP BY Year("BillingDocumentDate_E"), "BillingDocumentDate_E", "TotalNetAmount_E"
ORDER BY 1, 2
Message was edited by: Marc Daniau

General Ledger: Cumulative balance question on G/L account balance.

Hi SAP friends,
I had a question about cumulative balance.
If I see ending balance of xyz account of abc company code $5000 in 2007.
Now this is carried forward.
When I beginning balance in 2008 . It is different number say $100000.
How is the system calculating that and where is it storing (what table).
This new balance is probably due to adjustments, asset posting etc etc.
But is there a table or a way the transaction is storing this change of balance from 2007 to 2008 because from bseg the result varies.
Thanks
Kavita

U would have to rerun F.16 again, and also this time look at FS10N for the account whetehr there are any balances in period 13-16. There might be some adjustments done in between these periods.
Usually these control values per company, per period, per accounts are stored in table GLT0.

Form with Cumulative Total

Im new to this website and have built a couple of forms pretty easily. This is a great resource to get feedback. I need to build a form that along with their multi-choice answer function gives me a point total. For example:
Question 1: =1 point
Question 2: =1 point
Question 3: =1 point
And then at the end you automatically get a point total. Is that possible and if so what how do I make that happen?
Thanks in advance

On your side in the View Responses tab you can add formulas that do calculations. We do not support calculations in the actual form while it is being filled out.
Randy

How do I create a cumulative total for 3 or more cells in a new column

Ok so in brief I have a formula in column E that goes C3+C5+D4
what I would like is for column E to keep a running total , at the moment all it does is do the same indidual sum in each E cell
I apologise as there is most likely something stupid I am missing but I am new to number
any advice please
Louise

Louise,
I am not following the formula you presented. When you say running total my brain thinks of the math as :
add all previous values up to, and including, the latest row.
Like this:
the result in cell C1 is just the sum of B1
the result in cell C2 is the sum of B1 and B2
the result in cell C3 is the sum of B1, B2 and B3
the result in cell C4 is the sum of B1, B2, B3 and B4
etc
this can be realized with the formula:
C1=SUM($B$1:B1)
this is shorthand for... select cell C1, then type (or copy and paste from here) the formula:
=SUM($B$1:B1)
the formula means... sum all the cells from the absolute cell B1 ($B$1) to the relative cell B1.
as you fill this formula down the absolute cell reference will not change but the relative cell reference will adjust
to fill down... select cell C1, copy
now select column C, paste

I need some help Regarding Cumulative totals

Hi ,
i have a requirement
1) we have columns calender Periods and actual to date. The requirement is we need cumulate the actual to date. i have applyed RSUM function in column formula.
2) it is working fine. But again the requirement is this cumulative solution is changed based on selected calender periods. but this is not expected.
3) ex:-
calender period actual Units Cumulative Units
oct - 2010 10 10
Nov-2010 9 19
Dec-2010 15 34
Jan-2011 25 59
Feb-2011 12 71
March-2011 19 90
April - 2011 13 103
May - 2011 18 121
June - 2011 24 145
this is the reqiurement but i have a Prompt Like
i hve selected resource categery some xyz and stert period is Jan -2011 and end period is May - 2011
the values disply's like bellow
Resource Category start Period End Period
xyz Jan - 2011 May - 2011
Jan-2011 25 25
Feb-2011 12 37
March-2011 19 58
April - 2011 13 71
May - 2011 18 89
But this is not actual cumulative units the actual value for Jan 2011 cumulative value is 59 not 25
can any one help me regarding this issue
regards,
ramesh

Hi,
Refer this link abt iview properties & set authorization ...
http://help.sap.com/saphelp_nw04/helpdata/en/13/81a66d100011d7b84b00047582c9f7/frameset.htm
Color- you have to change portal theme...
Width- create a new Loyout..
Regards,
Senthil K.

Cumulative total - how to have a footer cell give running total

I'm working on a gas mileage spreadsheet. One column shows how many miles I went between gas fill ups. I'd like the footer cell in that column to show the running total. I'm running into a problem with the empty cells - they're causing a red triangle error in the footer cell. What's the formula to keep a running total of a set of cells, but ignore any blank cells?
Thanks,
Don

Hi Yvan,
Thanks for your response. The cells in C are output from other formulas. I used =SUM(C) for the cell (which happened to be the C column, by the way) and got the red triangle error. Is there a way for the footer cell in C to disregard the embedded formulas and take the output of each column cell instead, and get a running total of that?
Thanks,
Don

Could I add Cumulative Totals in pivot table?

for example
08-1-1 08-2-1 08-3-1
A 1 2 2
B 1 2 2
C 1 2 2
Total 3 6 6
CumuTotal 3 9 15

I add a cummulative column in a table.
In this column, I calculate the accumulated turnover for 2000 and 2001.
But the function don't stop at the end of the year 2000.
I want the function restart for 2001
Turnover : Accumulated turnover :
October : 5 : 5 :
2000 November : 5 : 10 :
December : 10 : 20 :
January : 6 : 26 : <= I want 6 for this value
2001 February : 20 : 46 :
March : 10 : 56 :
Thanks

Account 'Running Total' question

I have a request where an Account needs to keep a 'running total'. I don't think Time Balancing will work. Requirement is the account would just growing each month, then Jan of Year two equals Dec from Year one and so on...... Does DTS handle this? Not quite sure DTS keeps running tally forever....
Thanks for any input.

Using DTS to achieve a rolling balance across Years would likely not work in a Planning app. This is because Planning requires two separate time-related dimensions ("Years" and "Period"). Only one of these can be tagged as "Time", which is the dimension that DTS uses. Therefore, I can't see how you would get DTS to cross years AND roll up data within Periods.
From where is your data sourced? Is it from a source system (like a GL)? If so, just send the rolling balance from there. Is it entered by users, and the rolling balance must be calculated? If so, I'd consider having the users enter the activity (delta from period to period) and develop a calc to perform the rolling balance across years and months, perhaps in a separate account. You'll need a beginning balance to get this started.
Hope this helps,
- Jake

Retention policy for incremental cumulative backup question

Hi,
I have a production database configured with retention policy for 30 days window. No catalog is used.
The backup plan is:
Sunday - Level 0 backup.
Weekdays - Incremental 1 cumulative backup.
I also noticed that some archive logs since Mar 07 2010 has become obsolete in the recent few days.
Cannot figure out why the backup of Mar 07 2010 is going to be obsolete today.
Thanks for your help!
RMAN> list backup summary;
using target database control file instead of recovery catalog
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
*14 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
*15 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
*17 B F A SBT_TAPE 07-MAR-10 1 1 NO*
21 B F A SBT_TAPE 08-MAR-10 1 1 NO
24 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
25 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
27 B F A SBT_TAPE 08-MAR-10 1 1 NO
35 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
36 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
38 B F A SBT_TAPE 09-MAR-10 1 1 NO
46 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
47 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
49 B F A SBT_TAPE 10-MAR-10 1 1 NO
57 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
58 B 1 A SBT_TAPE 11-MAR-10 2 1 NO
60 B F A SBT_TAPE 11-MAR-10 1 1 NO
66 B A A SBT_TAPE 12-MAR-10 1 1 NO
67 B A A SBT_TAPE 12-MAR-10 1 1 NO
68 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
69 B 1 A SBT_TAPE 12-MAR-10 2 1 NO
70 B A A SBT_TAPE 12-MAR-10 1 1 NO
71 B F A SBT_TAPE 12-MAR-10 1 1 NO
77 B A A SBT_TAPE 14-MAR-10 1 1 NO
78 B A A SBT_TAPE 14-MAR-10 1 1 NO
79 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
80 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
81 B A A SBT_TAPE 14-MAR-10 1 1 NO
82 B F A SBT_TAPE 14-MAR-10 1 1 NO
88 B A A SBT_TAPE 15-MAR-10 1 1 NO
89 B A A SBT_TAPE 15-MAR-10 1 1 NO
90 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
91 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
92 B A A SBT_TAPE 15-MAR-10 1 1 NO
93 B F A SBT_TAPE 15-MAR-10 1 1 NO
99 B A A SBT_TAPE 16-MAR-10 1 1 NO
100 B A A SBT_TAPE 16-MAR-10 1 1 NO
101 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
102 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
103 B A A SBT_TAPE 16-MAR-10 1 1 NO
104 B F A SBT_TAPE 16-MAR-10 1 1 NO
109 B A A SBT_TAPE 17-MAR-10 4 1 NO
110 B F A SBT_TAPE 17-MAR-10 1 1 NO
111 B A A SBT_TAPE 17-MAR-10 1 1 NO
112 B F A SBT_TAPE 17-MAR-10 1 1 NO
113 B A A SBT_TAPE 17-MAR-10 1 1 NO
114 B A A SBT_TAPE 17-MAR-10 1 1 NO
115 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
116 B 1 A SBT_TAPE 17-MAR-10 2 1 NO
117 B A A SBT_TAPE 17-MAR-10 1 1 NO
118 B F A SBT_TAPE 17-MAR-10 1 1 NO
123 B A A SBT_TAPE 18-MAR-10 2 1 NO
124 B F A SBT_TAPE 18-MAR-10 1 1 NO
125 B A A SBT_TAPE 18-MAR-10 2 1 NO
126 B F A SBT_TAPE 18-MAR-10 1 1 NO
127 B A A SBT_TAPE 18-MAR-10 1 1 NO
128 B F A SBT_TAPE 18-MAR-10 1 1 NO
129 B A A SBT_TAPE 18-MAR-10 1 1 NO
130 B F A SBT_TAPE 18-MAR-10 1 1 NO
131 B A A SBT_TAPE 18-MAR-10 1 1 NO
132 B A A SBT_TAPE 18-MAR-10 1 1 NO
133 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
134 B 1 A SBT_TAPE 18-MAR-10 2 1 NO
135 B A A SBT_TAPE 18-MAR-10 1 1 NO
136 B F A SBT_TAPE 18-MAR-10 1 1 NO
142 B A A SBT_TAPE 19-MAR-10 2 1 NO
143 B F A SBT_TAPE 19-MAR-10 1 1 NO
144 B A A SBT_TAPE 19-MAR-10 1 1 NO
145 B F A SBT_TAPE 19-MAR-10 1 1 NO
146 B A A SBT_TAPE 19-MAR-10 1 1 NO
147 B F A SBT_TAPE 19-MAR-10 1 1 NO
148 B A A SBT_TAPE 19-MAR-10 1 1 NO
149 B F A SBT_TAPE 19-MAR-10 1 1 NO
150 B A A SBT_TAPE 19-MAR-10 1 1 NO
151 B A A SBT_TAPE 19-MAR-10 1 1 NO
152 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
153 B 1 A SBT_TAPE 19-MAR-10 2 1 NO
154 B A A SBT_TAPE 19-MAR-10 1 1 NO
155 B F A SBT_TAPE 19-MAR-10 1 1 NO
161 B A A SBT_TAPE 21-MAR-10 1 1 NO
162 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
163 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
164 B A A SBT_TAPE 21-MAR-10 1 1 NO
165 B F A SBT_TAPE 21-MAR-10 1 1 NO
171 B A A SBT_TAPE 22-MAR-10 1 1 NO
172 B F A SBT_TAPE 22-MAR-10 1 1 NO
173 B A A SBT_TAPE 22-MAR-10 1 1 NO
174 B F A SBT_TAPE 22-MAR-10 1 1 NO
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.ccbprod)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_ccbprod.f'; # default
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 30 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Control File Copy 108 19-FEB-10 /ccbprod/oradata/ccbprod/arc/control.bak.100219.21.21
Backup Set           8      07-MAR-10                                                                                     Backup Piece       19     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_5_1
Backup Set           8      07-MAR-10                                                                                     Backup Piece       18     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_4_1
Backup Set           8      07-MAR-10                                                                                     Backup Piece       17     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_3_1
Backup Set           8      07-MAR-10                                                                                     Backup Piece       16     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_2_1
Backup Set           8      07-MAR-10                                                                                     Backup Piece       15     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_1_1
Backup Set           7      07-MAR-10                                                                                     Backup Piece       14     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_5_1
Backup Set           7      07-MAR-10                                                                                     Backup Piece       13     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_4_1
Backup Set           7      07-MAR-10                                                                                     Backup Piece       12     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_3_1
Backup Set           7      07-MAR-10                                                                                     Backup Piece       11     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_2_1
Backup Set           7      07-MAR-10                                                                                     Backup Piece       10     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_1_1
Backup Set 10 07-MAR-10 Backup Piece 21 07-MAR-10 c-2894189962-20100307-00
Edited by: user12019850 on 22-Mar-2010 10:53 AM

Another database with the same configuration and same plan seems fine:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.cisconf)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_cisconf.f'; # default
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
774 B 0 A SBT_TAPE 19-FEB-10 1 1 NO
775 B 0 A SBT_TAPE 19-FEB-10 2 1 NO
795 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
796 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
797 B A A SBT_TAPE 20-FEB-10 1 1 NO
803 B A A SBT_TAPE 20-FEB-10 1 1 NO
804 B F A SBT_TAPE 20-FEB-10 1 1 NO
805 B A A SBT_TAPE 20-FEB-10 1 1 NO
806 B F A SBT_TAPE 20-FEB-10 1 1 NO
807 B A A SBT_TAPE 20-FEB-10 1 1 NO
808 B F A SBT_TAPE 20-FEB-10 1 1 NO
809 B A A SBT_TAPE 21-FEB-10 1 1 NO
810 B 0 A SBT_TAPE 21-FEB-10 1 1 NO
811 B 0 A SBT_TAPE 21-FEB-10 2 1 NO
812 B A A SBT_TAPE 21-FEB-10 1 1 NO
813 B F A SBT_TAPE 21-FEB-10 1 1 NO
818 B A A SBT_TAPE 21-FEB-10 1 1 NO
819 B F A SBT_TAPE 21-FEB-10 1 1 NO
820 B A A SBT_TAPE 21-FEB-10 1 1 NO
821 B F A SBT_TAPE 21-FEB-10 1 1 NO
822 B A A SBT_TAPE 21-FEB-10 1 1 NO
823 B F A SBT_TAPE 21-FEB-10 1 1 NO
824 B A A SBT_TAPE 22-FEB-10 1 1 NO
825 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
826 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
827 B A A SBT_TAPE 22-FEB-10 1 1 NO
828 B F A SBT_TAPE 22-FEB-10 1 1 NO
833 B A A SBT_TAPE 22-FEB-10 1 1 NO
834 B F A SBT_TAPE 22-FEB-10 1 1 NO
835 B A A SBT_TAPE 22-FEB-10 1 1 NO
836 B F A SBT_TAPE 22-FEB-10 1 1 NO
837 B A A SBT_TAPE 22-FEB-10 1 1 NO
838 B F A SBT_TAPE 22-FEB-10 1 1 NO
839 B A A SBT_TAPE 22-FEB-10 1 1 NO
840 B F A SBT_TAPE 22-FEB-10 1 1 NO
841 B A A SBT_TAPE 23-FEB-10 1 1 NO
842 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
843 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
844 B A A SBT_TAPE 23-FEB-10 1 1 NO
845 B F A SBT_TAPE 23-FEB-10 1 1 NO
850 B A A SBT_TAPE 23-FEB-10 1 1 NO
851 B F A SBT_TAPE 23-FEB-10 1 1 NO
852 B A A SBT_TAPE 23-FEB-10 1 1 NO
853 B F A SBT_TAPE 23-FEB-10 1 1 NO
854 B A A SBT_TAPE 23-FEB-10 1 1 NO
855 B F A SBT_TAPE 23-FEB-10 1 1 NO
856 B A A SBT_TAPE 24-FEB-10 1 1 NO
857 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
858 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
859 B A A SBT_TAPE 24-FEB-10 1 1 NO
860 B F A SBT_TAPE 24-FEB-10 1 1 NO
865 B A A SBT_TAPE 24-FEB-10 1 1 NO
866 B F A SBT_TAPE 24-FEB-10 1 1 NO
867 B A A SBT_TAPE 24-FEB-10 1 1 NO
868 B F A SBT_TAPE 24-FEB-10 1 1 NO
869 B A A SBT_TAPE 24-FEB-10 1 1 NO
870 B F A SBT_TAPE 24-FEB-10 1 1 NO
871 B A A SBT_TAPE 24-FEB-10 1 1 NO
872 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
873 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
874 B A A SBT_TAPE 24-FEB-10 1 1 NO
875 B F A SBT_TAPE 24-FEB-10 1 1 NO
880 B A A SBT_TAPE 24-FEB-10 1 1 NO
881 B F A SBT_TAPE 24-FEB-10 1 1 NO
882 B A A SBT_TAPE 25-FEB-10 1 1 NO
883 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
884 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
885 B A A SBT_TAPE 25-FEB-10 1 1 NO
886 B F A SBT_TAPE 25-FEB-10 1 1 NO
891 B A A SBT_TAPE 25-FEB-10 1 1 NO
892 B F A SBT_TAPE 25-FEB-10 1 1 NO
893 B A A SBT_TAPE 25-FEB-10 1 1 NO
894 B F A SBT_TAPE 25-FEB-10 1 1 NO
895 B A A SBT_TAPE 25-FEB-10 1 1 NO
896 B F A SBT_TAPE 25-FEB-10 1 1 NO
897 B A A SBT_TAPE 25-FEB-10 1 1 NO
898 B F A SBT_TAPE 25-FEB-10 1 1 NO
899 B A A SBT_TAPE 25-FEB-10 1 1 NO
900 B F A SBT_TAPE 25-FEB-10 1 1 NO
901 B A A SBT_TAPE 25-FEB-10 1 1 NO
902 B F A SBT_TAPE 25-FEB-10 1 1 NO
903 B A A SBT_TAPE 26-FEB-10 1 1 NO
904 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
905 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
906 B A A SBT_TAPE 26-FEB-10 1 1 NO
907 B F A SBT_TAPE 26-FEB-10 1 1 NO
912 B A A SBT_TAPE 26-FEB-10 1 1 NO
913 B F A SBT_TAPE 26-FEB-10 1 1 NO
914 B A A SBT_TAPE 26-FEB-10 1 1 NO
915 B F A SBT_TAPE 26-FEB-10 1 1 NO
916 B A A SBT_TAPE 26-FEB-10 1 1 NO
917 B F A SBT_TAPE 26-FEB-10 1 1 NO
918 B A A SBT_TAPE 27-FEB-10 1 1 NO
919 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
920 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
921 B A A SBT_TAPE 27-FEB-10 1 1 NO
922 B F A SBT_TAPE 27-FEB-10 1 1 NO
927 B A A SBT_TAPE 27-FEB-10 1 1 NO
928 B F A SBT_TAPE 27-FEB-10 1 1 NO
929 B A A SBT_TAPE 27-FEB-10 1 1 NO
930 B F A SBT_TAPE 27-FEB-10 1 1 NO
931 B A A SBT_TAPE 27-FEB-10 1 1 NO
932 B F A SBT_TAPE 27-FEB-10 1 1 NO
933 B A A SBT_TAPE 28-FEB-10 1 1 NO
934 B 0 A SBT_TAPE 28-FEB-10 1 1 NO
935 B 0 A SBT_TAPE 28-FEB-10 2 1 NO
936 B A A SBT_TAPE 28-FEB-10 1 1 NO
937 B F A SBT_TAPE 28-FEB-10 1 1 NO
942 B A A SBT_TAPE 28-FEB-10 1 1 NO
943 B F A SBT_TAPE 28-FEB-10 1 1 NO
944 B A A SBT_TAPE 28-FEB-10 1 1 NO
945 B F A SBT_TAPE 28-FEB-10 1 1 NO
946 B A A SBT_TAPE 28-FEB-10 1 1 NO
947 B F A SBT_TAPE 28-FEB-10 1 1 NO
948 B A A SBT_TAPE 01-MAR-10 1 1 NO
949 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
950 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
951 B A A SBT_TAPE 01-MAR-10 1 1 NO
952 B F A SBT_TAPE 01-MAR-10 1 1 NO
957 B A A SBT_TAPE 01-MAR-10 1 1 NO
958 B F A SBT_TAPE 01-MAR-10 1 1 NO
959 B A A SBT_TAPE 01-MAR-10 1 1 NO
960 B F A SBT_TAPE 01-MAR-10 1 1 NO
961 B A A SBT_TAPE 01-MAR-10 1 1 NO
962 B F A SBT_TAPE 01-MAR-10 1 1 NO
963 B A A SBT_TAPE 02-MAR-10 1 1 NO
964 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
965 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
966 B A A SBT_TAPE 02-MAR-10 1 1 NO
967 B F A SBT_TAPE 02-MAR-10 1 1 NO
970 B A A SBT_TAPE 02-MAR-10 1 1 NO
971 B F A SBT_TAPE 02-MAR-10 1 1 NO
972 B A A SBT_TAPE 02-MAR-10 1 1 NO
973 B F A SBT_TAPE 02-MAR-10 1 1 NO
974 B A A SBT_TAPE 02-MAR-10 1 1 NO
975 B F A SBT_TAPE 02-MAR-10 1 1 NO
976 B A A SBT_TAPE 03-MAR-10 1 1 NO
977 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
978 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
979 B A A SBT_TAPE 03-MAR-10 1 1 NO
980 B F A SBT_TAPE 03-MAR-10 1 1 NO
983 B A A SBT_TAPE 03-MAR-10 1 1 NO
984 B F A SBT_TAPE 03-MAR-10 1 1 NO
985 B A A SBT_TAPE 03-MAR-10 1 1 NO
986 B F A SBT_TAPE 03-MAR-10 1 1 NO
987 B A A SBT_TAPE 03-MAR-10 1 1 NO
988 B F A SBT_TAPE 03-MAR-10 1 1 NO
989 B A A SBT_TAPE 04-MAR-10 1 1 NO
990 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
991 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
992 B A A SBT_TAPE 04-MAR-10 1 1 NO
993 B F A SBT_TAPE 04-MAR-10 1 1 NO
996 B A A SBT_TAPE 04-MAR-10 1 1 NO
997 B F A SBT_TAPE 04-MAR-10 1 1 NO
998 B A A SBT_TAPE 04-MAR-10 1 1 NO
999 B F A SBT_TAPE 04-MAR-10 1 1 NO
1000 B A A SBT_TAPE 04-MAR-10 1 1 NO
1001 B F A SBT_TAPE 04-MAR-10 1 1 NO
1002 B A A SBT_TAPE 05-MAR-10 1 1 NO
1003 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
1004 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
1005 B A A SBT_TAPE 05-MAR-10 1 1 NO
1006 B F A SBT_TAPE 05-MAR-10 1 1 NO
1009 B A A SBT_TAPE 05-MAR-10 1 1 NO
1010 B F A SBT_TAPE 05-MAR-10 1 1 NO
1011 B A A SBT_TAPE 05-MAR-10 1 1 NO
1012 B F A SBT_TAPE 05-MAR-10 1 1 NO
1013 B A A SBT_TAPE 05-MAR-10 1 1 NO
1014 B F A SBT_TAPE 05-MAR-10 1 1 NO
1015 B A A SBT_TAPE 06-MAR-10 1 1 NO
1016 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
1017 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
1018 B A A SBT_TAPE 06-MAR-10 1 1 NO
1019 B F A SBT_TAPE 06-MAR-10 1 1 NO
1022 B A A SBT_TAPE 07-MAR-10 1 1 NO
1023 B 0 A SBT_TAPE 07-MAR-10 1 1 NO
1024 B 0 A SBT_TAPE 07-MAR-10 2 1 NO
1025 B A A SBT_TAPE 07-MAR-10 1 1 NO
1026 B F A SBT_TAPE 07-MAR-10 1 1 NO
1029 B A A SBT_TAPE 07-MAR-10 1 1 NO
1030 B F A SBT_TAPE 07-MAR-10 1 1 NO
1031 B A A SBT_TAPE 07-MAR-10 1 1 NO
1032 B F A SBT_TAPE 07-MAR-10 1 1 NO
1033 B A A SBT_TAPE 07-MAR-10 1 1 NO
1034 B F A SBT_TAPE 07-MAR-10 1 1 NO
1035 B A A SBT_TAPE 08-MAR-10 1 1 NO
1036 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1037 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1038 B A A SBT_TAPE 08-MAR-10 1 1 NO
1039 B F A SBT_TAPE 08-MAR-10 1 1 NO
1042 B A A SBT_TAPE 08-MAR-10 1 1 NO
1043 B F A SBT_TAPE 08-MAR-10 1 1 NO
1044 B A A SBT_TAPE 08-MAR-10 1 1 NO
1045 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1046 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1047 B A A SBT_TAPE 08-MAR-10 1 1 NO
1048 B F A SBT_TAPE 08-MAR-10 1 1 NO
1054 B A A SBT_TAPE 09-MAR-10 1 1 NO
1055 B A A SBT_TAPE 09-MAR-10 1 1 NO
1056 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
1057 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
1058 B A A SBT_TAPE 09-MAR-10 1 1 NO
1059 B F A SBT_TAPE 09-MAR-10 1 1 NO
1065 B A A SBT_TAPE 10-MAR-10 1 1 NO
1066 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
1067 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
1068 B A A SBT_TAPE 10-MAR-10 1 1 NO
1069 B F A SBT_TAPE 10-MAR-10 1 1 NO
1075 B A A SBT_TAPE 11-MAR-10 1 1 NO
1076 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
1077 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
1078 B A A SBT_TAPE 11-MAR-10 1 1 NO
1079 B F A SBT_TAPE 11-MAR-10 1 1 NO
1085 B A A SBT_TAPE 12-MAR-10 1 1 NO
1086 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
1087 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
1088 B A A SBT_TAPE 12-MAR-10 1 1 NO
1089 B F A SBT_TAPE 12-MAR-10 1 1 NO
1094 B A A SBT_TAPE 13-MAR-10 1 1 NO
1095 B A A SBT_TAPE 13-MAR-10 1 1 NO
1096 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
1097 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
1098 B A A SBT_TAPE 13-MAR-10 1 1 NO
1099 B F A SBT_TAPE 13-MAR-10 1 1 NO
1105 B A A SBT_TAPE 14-MAR-10 1 1 NO
1106 B 0 A SBT_TAPE 14-MAR-10 1 1 NO
1107 B 0 A SBT_TAPE 14-MAR-10 2 1 NO
1108 B A A SBT_TAPE 14-MAR-10 1 1 NO
1109 B F A SBT_TAPE 14-MAR-10 1 1 NO
1115 B A A SBT_TAPE 15-MAR-10 1 1 NO
1116 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
1117 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
1118 B A A SBT_TAPE 15-MAR-10 1 1 NO
1119 B F A SBT_TAPE 15-MAR-10 1 1 NO
1125 B A A SBT_TAPE 16-MAR-10 1 1 NO
1126 B A A SBT_TAPE 16-MAR-10 1 1 NO
1127 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
1128 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
1129 B A A SBT_TAPE 16-MAR-10 1 1 NO
1130 B F A SBT_TAPE 16-MAR-10 1 1 NO
1136 B A A SBT_TAPE 17-MAR-10 1 1 NO
1137 B A A SBT_TAPE 17-MAR-10 1 1 NO
1138 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
1139 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
1140 B A A SBT_TAPE 17-MAR-10 1 1 NO
1141 B F A SBT_TAPE 17-MAR-10 1 1 NO
1147 B A A SBT_TAPE 18-MAR-10 1 1 NO
1148 B A A SBT_TAPE 18-MAR-10 1 1 NO
1149 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
1150 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
1151 B A A SBT_TAPE 18-MAR-10 1 1 NO
1152 B F A SBT_TAPE 18-MAR-10 1 1 NO
1158 B A A SBT_TAPE 19-MAR-10 1 1 NO
1159 B A A SBT_TAPE 19-MAR-10 1 1 NO
1160 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
1161 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
1162 B A A SBT_TAPE 19-MAR-10 1 1 NO
1163 B F A SBT_TAPE 19-MAR-10 1 1 NO
1169 B A A SBT_TAPE 20-MAR-10 1 1 NO
1170 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
1171 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
1172 B A A SBT_TAPE 20-MAR-10 1 1 NO
1173 B F A SBT_TAPE 20-MAR-10 1 1 NO
1179 B A A SBT_TAPE 21-MAR-10 1 1 NO
1180 B 0 A SBT_TAPE 21-MAR-10 1 1 NO
1181 B 0 A SBT_TAPE 21-MAR-10 2 1 NO
1182 B A A SBT_TAPE 21-MAR-10 1 1 NO
1183 B F A SBT_TAPE 21-MAR-10 1 1 NO
1189 B A A SBT_TAPE 22-MAR-10 1 1 NO
1190 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
1191 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
1192 B A A SBT_TAPE 22-MAR-10 1 1 NO
1193 B F A SBT_TAPE 22-MAR-10 1 1 NO
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 30 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Control File Copy 47 20-FEB-10 /dbbackup/cisconf/control.bak.20100220
Backup Set 804 20-FEB-10
Backup Piece 551 20-FEB-10 c-3316101807-20100220-01
Edited by: user12019850 on 22-Mar-2010 11:03 AM

Cumulative Totals...

I'm not quite the seasoned pro, but have been working with CF for about 5 years and usually can get it to do what I want. I thought this would be relatively easy (and prob is to you) to add cumulative costs in the right column of a balance sheet type output, but it's kicked my butt long enough..lol
Just need it to sum cumulative costs of the items selected, in the order sorted. I've tried varying ways to get this to add and display like I need, dbqueries, loop indexes, using recordcount/currentrow calculations, etc, etc...no joy
Appreciate your time...really!
<form...select...etc>
<cfquery name="getcosts" datasource="xxx">
SELECT *
FROM costs
ORDER by '#form.sortby#'
</cfquery>
<cfoutput query="getcosts">
*displays columns for #item_name#, #item_cost#, and cumulative cost* based on output sort order
</cfquery>

RLByrd78240 wrote:
<cfquery name="getcosts" datasource="xxx">
SELECT *
FROM costs
ORDER by '#form.sortby#'
</cfquery>
<cfoutput query="getcosts">
*displays columns for #item_name#, #item_cost#, and cumulative cost* based on output sort order
</cfquery>
I have some doubts about the clause ORDER by '#form.sortby#'. Does it actually work? should it at least be ORDER by #form.sortby# (without the quotes)? Test by dumping getcosts.
When grouping a set of records, you should use the order-by column of the query as the group attribute of the cfoutput tag. In other words, something like
<cfoutput query="getcosts" group="#form.sortby#">
To get cumulative costs, you could use a construction like
<cfset cumulative = 0>
<cfoutput>
blah blah blah
<cfset cumulative = cumulative + item_cost>
</cfoutput>

Rating - Play count totals question ...

Hi,
I'd like to transfer the Rating & Play count totals to another computer (that has hopefully the same play list).
How do I do this?
Thanks.

As you probably know, the rating and playcount are not stored in the song file itself; they are stored in the library and will be lost if you move the songs separately from the entire library.
So, to preserve them, first consolidate your library (if it isn't already) using the command File > Library > Organize Library... > Consolidate Files, and then copy the entire iTunes folder to the new machine.

Cumulative totals question

Similar Messages

Maybe you are looking for