Incorrect values with AGO function

Hi,
I am trying to fix a problem where my AGO function is producing close but not 100% correct values.
I have:
Fact Table (pk is by date, employee, and measure keys)
Dim Date Table (only date, month, quarter, year - very simple) Month and quarter are just numbers (not identified by year)
Dim Emp Table
I have a logical dimension hierarchy for Dim Date: Total > Year > Quarter > Month > Date
In my Logical Fact table, I have a SUM column for the measure. My AGO column is just AGO(Measure (SUM), Dim Date.Month, 1)
For my report, I have tried a few things.
If I just use the Month column from my Date table, the AGO numbers are way off. If I do MONTH(Date) instead, the AGO numbers are close, and even accurate most of the time, but sometimes they will be a little bit off, by only 1 or 2 usually.
I'm having the hardest time trying to figure this out, but one thing I'm suspicious of is the Date table - should Month and Quarter be like 2008-01, 2008-02, instead of just 01, 02?

It would come as no surprise to me if the datetime dim is incorrect. I have been cleaning up someone else's mess.
The date dim is just this:
desc date_dim;
Name                           Null     Type
DATE_KEY                       NOT NULL NUMBER(8)
D_YEAR                         NOT NULL NUMBER(4)
D_MON                          NOT NULL NUMBER(2)
D_DAY                          NOT NULL NUMBER(2)
DATE_VALUE                     NOT NULL DATE
D_QUARTER                      NOT NULL NUMBER(1)
6 rows selectedFor today's date:
DATE_KEY               D_YEAR                 D_MON                  D_DAY                  DATE_VALUE                D_QUARTER
20090417               2009                   4                      17                     17-APR-09                 2
1 rows selectedI tried making the logical columns for D_YEAR||D_MON and D_YEAR||D_QUARTER, and added them as non-drillable chronological keys in my hierarchy, but still getting the same results.
Any ideas?
Edited by: KevinC_VA on Apr 17, 2009 2:40 PM

Similar Messages

Incorrect parameter with CALL FUNCTION - WE19

hi! All
while creating IDOC through WE19 - Start Inbound it creates IDOC with Status - 64."IDoc ready to be transferred to application" "No filters , No conversion , No version change ."
Incorrect parameter with CALL FUNCTION
This parameter was "MASSAVEINFOS".
but i have Included this parameter in my Function module.
INPUT_METHOD TYPE INPUTMETHD
MASS_PROCESSING TYPE MASS_PROC
NO_APPLICATION_LOG LIKE SY-DATAR
MASSAVEINFOS LIKE MASSSAVINF
whats the mistake i have done.
Regards
Kv

That will not be possible KV, as the call to the FM is not being made, as far as i see you have completed the needed settings.
As i do not have access to an SAP system, i suggest that you try below,
1) Go to WE19, enter the IDOC number and F8.
2) In this screen, click on Inbound function module.
3) In the field for inbound function module press F4, it should list your FM name here if all the necessary we42/82/57, BD51 and WE20 have been done correctly.
Another thing that you can try is, on WE19,
1) Idoc Number F8
2) /h - to start Debug
3) Now click on Standard inbound, in the debug mode press F5 once.
4) Now put a break point on all message statement
See where exactly the message of wrong FM is being thrown, it will most probably be after a select statement on one of the tables associated with WE42/82/57/BD51 etc. With this you will where you have missed out.
All the best !!!
Regards,
Chen
Edited by: Chen K V on Mar 18, 2010 8:55 AM

Problem with AGO function in OBIEE

Hi I am new to OBIEE,
I am working on Trend Analysis of ETL Mappings,
I am using AGO Function to get the Previous day Elapse Time of a mapping but while generating the report its behaving in a strange way.
like
AGO("BI Performance"."Map Val Fact"."Elapse Time Minutes","BI Performance".ETLStartDim."Day",1) -- Day Ago Elapse time
AGO("BI Performance"."Map Val Fact"."Elapse Time Minutes","BI Performance".ETLStartDim."Day",2) -- Two Day Ago Elapse time
For example, in database there is date like
Date Elapse Time
2nd June 10 min
1st June 11 min
30th may 10 min
My date in Report should be like
Date Elapse Time Day Ago Elapse Time Two Day Ago Elapse Time
2nd June 10 11 10
But the date coming over here is
Date Elapse Time Day Ago Elapse Time Two Day Ago Elapse Time
2nd June 10
3rd June 10
4th June 10
So if any one could help me out of this, it would of great help.
With Regards
Chaitanya

This is posted to the incorrect forum. Please post to an OBIEE forum.

Incorrect value with Script Logic

Hello,
From initial value called 2008.ORC we want to calculate for each month the percentage , from child DIASMES.
Now, with the script logic ( I´ll put down later) we have an incorrect value in the column 2008.TOTAL.
In other words, I´m sure I´m wrong with "WHAT" or "WHERE sentence or maybe the operation "FACTOR=USING/TOTAL" fails because the crossing between dimensions it´s incorrect.
*RUNALLOCATION
*FACTOR = USING/TOTAL
*DIM FABRICA_MAQ WHAT=BAS(FABRICAFF); WHERE=BAS(FABRICAFF); USING=BAS(FABRICAFF);
*DIM PRODUTOS WHAT=BAS(TOTALPROD); WHERE=BAS(TOTALPROD); USING=SP;
*DIM TIME WHAT=2008.ORC;WHERE=BAS(2008.TOTAL); USING=BAS(2008.TOTAL);
*DIM TIPO WHAT=BAS(TOT); WHERE=BAS(TOT); USING=ST;
*DIM VARIAVEIS WHAT=MIXACABADA; WHERE=MIXACABADA; USING=DIASMES;
*DIM DATASRC WHAT=INPUT; WHERE=INPUT; USING=INPUT;
*DIM VERSAO WHAT=BUDGET; WHERE=BUDGET; USING=BUDGET;
*ENDALLOCATION
*COMMIT
The Key is to see in the column 2008.TOTAL ( when we selected "BAS") the value of parent divided into "DIASMES" !
Thanks !!

Your factor statment references a TOTAL, but you don't reference the total in your DIM statements. If you look at the debug log carefully, you should notice that there's no calculation of a TOTAL value.
Try something like this. The only reason I move some dimensions from the *RUNALLOCATION up to the *XDIM's is for legibility, since the allocation makes no shifts to these dimensions. The logic should produce the same results, either way.
// These dimensions have no shift of data.
*XDIM_MEMBER VERSAO=BUDGET
*XDIM_MEMBER DATASRC=INPUT
// I'm assuming here that FACRICAFF is the top member of this dimension.
*XDIM_MEMBERSET FABRICA_MAQ = <ALL>
*RUNALLOCATION
*FACTOR = USING/TOTAL
*DIM PRODUTOS WHAT=BAS(TOTALPROD); WHERE=BAS(TOTALPROD); USING=SP; TOTAL=<<<
*DIM TIME WHAT=2008.ORC;WHERE=BAS(2008.TOTAL); USING=BAS(2008.TOTAL); TOTAL=<<<
*DIM TIPO WHAT=BAS(TOT); WHERE=BAS(TOT); USING=ST; TOTAL=<<<
*DIM VARIAVEIS WHAT=MIXACABADA; WHERE=MIXACABADA; USING=DIASMES; TOTAL=<<<
*ENDALLOCATION
*COMMIT

How to assign to variable from XML type values with extract function?

Hi ,
I have XMLTYPE variable LeXml having below record
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<AddListing xmlns="http://www.christielites.com/">
<sComCode>string</sComCode>
<sLocCode>string</sLocCode>
<dStart>dateTime</dStart>
<dEnd>dateTime</dEnd>
<sEcode>string</sEcode>
<iAvail>int</iAvail>
<iOwned>int</iOwned>
<sPostTrans>string</sPostTrans>
</AddListing>
</soap:Body>
</soap:Envelope>
I want to get sEcode value string into one varialbe using extract function or alternate?
can any one give me syntax fro it?
I tried with Mstring:=LeXml.extract('AddListing/scomcode/text()').getStringval(); but iam getting error
ERROR at line 1:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00601: Invalid token in: 'soap:Envelope/text()'
ORA-06512: at "SYS.XMLTYPE", line 111
ORA-06512: at "BLUEWATER.CREATELERESPONSELOG", line 12
ORA-06512: at line 1
Please guide Me..

Hi Ravi kumar,
I have similar type of problem like above . My xml file is like below:
<doSingleRecordResponse xmlns="urn:mdWebService">
<doSingleRecordResult xsi:type="ResponseRecord" id="1" version="2.30" action="Response" timeout="10" timestamp="12-17-2009" transmissionReference="ABCDEF" TimeToProcess="31.25" xmlns:xsi="http://www
.w3.org/2001/XMLSchema-instance">
<CustomerCredentials>
<CustomerID>111111</CustomerID>
</CustomerCredentials>
<ServiceResult>
<ErrorCode> </ErrorCode>
<ErrorDesc>OK;</ErrorDesc>
</ServiceResult>
<Address version="2.30">
<Faults count="0"/>
<Result>
<ErrorCode> </ErrorCode>
<ErrorDesc>OK</ErrorDesc>
<StatusCode>9</StatusCode>
<StatusD
esc>(U.S.) The address was fully coded.</StatusDesc>
</Result>
<Company/>
<Urbanization>
<Name/>
<Code/>
</Urbanization>
<Type>
<String>Highrise</String>
<Code>H</Code>
</Type>
<Street>XXXXXXXXXXXXX</Street>
<Street2/>
<Suite/>
<PrivateMailBox/>
<CarrierRoute>C048</CarrierRoute>
<Lacs> </Lacs>
<LacsLink>
<LacsStatusCode/>
<LacsReturnCode/>
</LacsLink>
<DeliveryPointCode>99</DeliveryPointCode>
<DeliveryPointCheckDigit>6</DeliveryPointCheckDigit>
<DPV>
<Footnotes/>
<CMRA/>
<AddressStatus/>
</DPV>
<DeliveryIndicator>
<Code/>
</DeliveryIndicator>
<City>
<Name>String</Na
me>
<Abbreviation>Memphis</Abbreviation>
</City>
<County>
<Name>String</Name>
<Fips>41111</Fips>
</County>
<State>
<Name>Tennessee</Name>
<Abbreviation>TN</Abbreviation>
</State>
<Zip>
<Type> </Type>
<Zip5>38111</Zip5>
<Plus4>1111</Plus4>
</Zip>
<GeoCode>
<Latitude/>
<Longitude/>
</GeoCode>
<TimeZone>
<Name/>
<Code/>
</TimeZone>
<Msa>
<Code/>
</Msa>
<Pmsa>
<Code/>
</Pmsa>
<Census>
<Block/>
<Tract/>
</Census>
<CongressionalDistrict>
<Code/>
</CongressionalDistrict>
<Parsed>
<StreetName/>
<AddressRange/>
<Suffix/>
<Direction>
<Post/>
<Pre/>
</Direction>
<Suite>
<Name/>
<Range/>
</Suite>
<PrivateMailBox>
<Name/>
<Range/>
</PrivateMailBox>
<Garbage/>
</Parsed>
<Country>
<Abbreviation>US</Abbreviation>
<Name>United St
ates of America</Name>
</Country>
</Address>
<Telephone version="" action="">
<Result>
<ErrorCode/>
<ErrorDesc/>
<StatusCode/>
<StatusDesc/>
</Result>
<Number/>
<PhoneAreaCode/>
<NewAreaCode/>
<Prefix/>
<Suffix/>
<Extension/>
<City>
<Name/>
</City>
<State>
<Name/>
<Abbreviation/>
</State>
<GeoCode>
<Latitude/>
<Longitude/>
</GeoCode>
<TimeZone>
<Name/>
<Code/>
</TimeZone>
<Msa>
<Code/>
</Msa>
<Pmsa>
<Code/>
</Pmsa>
<County>
<Name/>
<Fips/>
</County>
<Country>
<Abbreviation/>
<Name/>
</Country>
</Telephone>
<Name version="" action="">
<Result>
<ErrorCode/>
<ErrorDesc/>
<StatusCode/>
<StatusDesc/>
</Result>
<Company/>
<Prefix/>
<Suffix/>
<Full/>
<First/>
<Middle/>
<Last/>
<Gender/>
</Name>
</doSingleRecordResult>
</doSingleRecordResponse>
This is the response i got from a webservice , from this i need to extract customer id .
I tried like this :
response := UTL_DBWS.invoke ( l_call,request);
if RESPONSE.extract('/doSingleRecordResponse/doSingleRecordResult/CustomerCredentials/CustomerID/text()','xmlns:xsi="http://www
.w3.org/2001/XMLSchema-instance" xmlns="urn:mdWebService"') is not NULL
then
errorcode :=RESPONSE.extract('/doSingleRecordResponse/doSingleRecordResult/CustomerCredentials/CustomerID/text()','xmlns:xsi="http://www
.w3.org/2001/XMLSchema-instance" xmlns="urn:mdWebService"').getStringVal;
end if;
I am getting null value into errorcode,
Can youplease let me know what i am doing wrong?
Thanks

OBIEE: Incorrect SQL - with count function uses ORDER BY instead GROUP BY

I made a basic report that is a client count; I want to know how many clients the company have.
But, when I run this report, OBIEE generates a ORDER BY sentence, instead a GROUP BY. Remember that I'm using count function, that is a agregation.
The SQL generated was:
select 'N0' as c1,
count(*) as c2
from
(select distinct T1416.CLIENT_INTER_KEY as c1
from
(select *
from prd.D_SERVICE where SOURCE_SYS in ('ARBOR','PPB') and DW_SERV_ST_ID in (100000003,100000009)) T1836,
(select *
from prd.D_CLIENT) T1416,
(select *
from prd.D_CUSTOMER_ACCOUNT where SOURCE_SYS In ('ARBOR','PPB')) T1515
where ( T1416.DW_CLIENT_ID = T1515.DW_CLIENT_ID and T1515.DW_CUST_ACCT_ID = T1836.DW_CUST_ACCT_ID and T1836.MSISDN = '917330340' )
) D1
order by c1
The error that I receive is:
"Query Status: Query Failed: [nQSError: 16001] ODBC error state: S1000 code: -1005018 message: [Sybase][ODBC Driver][Adaptive Server Anywhere]Illegal ORDER BY item Order Item: 'N0',
-- (opt_OrderBy.cxx 429) .
[nQSError: 16011] ODBC error occurred while executing SQLExtendedFetch to retrieve the results of a SQL statement."
If I substitute ORDER BY with GROUP BY and test it in Sybase, Ithe query runs without any problem.
select 'N0' as c1,
count(*) as c2
from
(select distinct T1416.CLIENT_INTER_KEY as c1
from
(select *
from prd.D_SERVICE where SOURCE_SYS in ('ARBOR','PPB') and DW_SERV_ST_ID in (100000003,100000009)) T1836,
(select *
from prd.D_CLIENT) T1416,
(select *
from prd.D_CUSTOMER_ACCOUNT where SOURCE_SYS In ('ARBOR','PPB')) T1515
where ( T1416.DW_CLIENT_ID = T1515.DW_CLIENT_ID and T1515.DW_CUST_ACCT_ID = T1836.DW_CUST_ACCT_ID and T1836.MSISDN = '917330340' )
) D1
group by c1
Do you know why OBIEE generates this SQL??? Why uses, with a aggregation function, a ORDER BY and not a GROUP BY? How can I resolve this problem???
Regards,
Susana Figueiredo

Verify your repository design and make sure that you have defined count aggregate on fact column. You would also need to define the content level of each dimension in fact table.

Extract negative values with @JExport function in Essbase version 9.0.1

I'm currently trying to extract values using the @JExport but I noticed that negative values weren't extracted.
Is there something to do to make it work?
Thanks for your help.
BR,
Andy

Thanks for confirming things Vivek.Wilfred.
FYI, for future others with this problem: After a couple hours of playing around it was fixed, though I'm not sure what finally did it. Be sure that you try Google's "Sign Out of All Accounts", and not just the regular sign out option.

The problem with AGO function

Oracle BI 11g
Hi!
In repositiry I created time hierarchy:
1. Year
- YearID (Primary Key)
- YearName (Use For display)
1.1 Month
- MonthID (Primary Key)
- MonthName (Use For display, Sorted By MonthID)
1.1.1 Date
- DateID (Primary Key)
- Date (Use For display, Chronological Key).
After that I create calculated logical column "Revenue (1 year ago)": Ago("DB"."Table"."Revenue" , "DB"."Calendar"."Year" , 1)
But when I use created column in Analysis, I get strange results (Date, Revenue, Revenue (1 year ago)):
09.02.2007..........1000....................
09.03.2007..........3000....................
06.04.2007..........5000....................
08.02.2008..............................1000
07.03.2008..............................3000
11.04.2008..............................5000
As you can see dates in 2008 year are different that in 2007! Why it can be???
Edited by: 849986 on 21.04.2011 6:01

I thought that I made mistake when I created my repository or something else. But I got this problem in Oracle demo-repository SampleAppLite as well! I created Analysis: Calendar Date, Revenue, Year Ago Revenue:
07.01.2008..........2167
08.01.2008..........1920
05.01.2009...........................2167
06.01.2009...........................1920
It's a bug in Oracle BI 11 or I do something wrong?

Applescript returns incorrect value with blank cell

Imagine there is a column of numbers, some which might have the value 0.0 and some which are blank. Imagine wanting to append a data set at the first blank cell using Applescript. As Applescript is currently implemented in Numbers, this is not possible. See the following test.
1. In Numbers, create a new blank spreadsheet.
2. Select cell "A1".
3. Format as text.
4. Execute the following line of Applescript,
tell application "Numbers" to get value of cell "A1" of table 1 of sheet 1 of front document
It returns "0.0".
I would expect a return "" since it is a empty cell formated as text, no less.
Because of this, there is no way to find a blank cell since a blank cell returns a value of 0.0 which might be a valid entry.
Anyone have any ideas for a work around?

The value of a blank (empty) cell IS zero.
The value of a cell containing a string whose length is zero contains "".
Given that, I will post a report because I'm not sure than the value returned in AppleScript is the good choice.
In AppleWorks for a blank cell, the returned value was "".
Yvan KOENIG (from FRANCE dimanche 11 janvier 2009 16:31:35)
+Your tracking number for this issue is Bug ID# 6487875.+
Hello
+(1) May I know if the fact than+
+set v to value of cell "B12"+
+returns 0.0 when the cell is blank is the designed result.+
+In AppleWorks in this case, we are accustomed to get an empty string.+
+(2) In version 1, a cell containing an empty string was accepted in an arithmetic operation.+
+In version 2, it is rejected.+
+Is it a design choice or is it a bug ?+
+Your tracking number for this issue is Bug ID# 6487879.+
Hello
+In Numbers, as long as we are referencing cells of the current row (200 for instance), we may use short references like:+
=(BC)*(DE)
+When we save as iWork '08 document, the formula is expanded as+
=(B200C200)*(D200E200)
+Is it a design choice or a bug ?+

PDETextGetBBox returns incorrect value with Italic font

Hello,
I use PDETextGetBBox to retrieve the BBox of PDETextRun which are created with an italic font (in my case Arial Italic). Unfortuantely the returned AsFixedRect is not correct because it doesn't take into account the skewing of the char.
Is it normal? A bug? A wrong usage of the SDK method?
Thanks in advance,
Joe

Ok but the bounding box should contain all the TextRun. By the way I have the same behavior with the Quad.
The solution is to use the PDEElementGetBBox but in this case it's too large.
Any idea?
Thanks in advance,
Joe

How can I use AGO function with aggregates

I use aggregated table and a detailed table
I have time hierarchy whose lowest level is date. For sales I
created year-to-year (YTD) comparision with AGO function. It
works OK.
BUT, I want to speed it up, so I used aggregates. I created new
time table grouped by MONTH and corresponding agg_SALES table. I
created connections and mapped the fields. It works OK for
normal queries, that means my queries at month level use
aggregates. BUT when I add YTD measures or YAGO measure in query, it goes to
then SALES table whose grain is date.
How can I force BI Server to use AGO function with aggregates?
I use OBIEE 10.1.3.4
Thank you
Ishaq
(Question originally taken from ITtoolbox and posted by Gorazd)
SORRY - THE QUESTION IS IN THE WRONG FORUM
Edited by: ishaq12 on Nov 19, 2008 12:21 PM

Hi,
you can not do it in Administration tool but you can set agregation for that field in Answers (fx->Agregation rule->Sum) and effect should be the same. Note that it may not work properly on Oracle 10g as generated SQL is not 100% recognized, on 11g everything is OK (at least in my case).
Regards,
Marko
Edited by: user10449532 on 2008.11.19 06:29

Ago-function in BISE1

Hey!
Is it possible to use the AGO aggregate function in the standard edition? I've been trying to do it, but all I get are errors about using "standard aggregate functions."
More info here: Comparing successive years in a report
Regards,
Erik

Hello Erik,
I just started figuring out things on obise1. But I got things working with ago functions.
Did you create a new logical column with ago funcionality? That works just fine for me! And it uses the original colum aggregate function

AGO function problem 10.1.3.4

Hi,
Anyone have any suggestions on this please???
Still hoping for suggestions from anyone who has had similar problem with AGO function yielding strange results at certain levels of hierarchy??
I have a facts folder with both AGO and 'regular' columns of data.
I create a simple query with filters on period name and expense type.
When I add 'regular' columns (default aggregate SUM) - it works okay.
I then remove all 'regular' facts columns.
When I add AGO based columns - it works fine.
When I try any combination of AGO and 'regular' suddenly a lot of my data disappears.
I have tried experimenting with report based totals off and setting the function aggregation to SUM for the AGO columns, but nothing works.
i.e. AGO is pointing at previous period, so I have Yr, Qtr, Period in my time dimension and the AGO is linked to Period level (like a calendar month, but financial) and the AGO is -1.
Filter is on period name - so for example "PERIOD NAME" is equal to / is in 'NOV-11'
Any suggestions please??
thanks,
Robert.
Edited by: Robert Angel on 08-Dec-2011 06:02 to clarify ago usage
Further information; -
I have just discovered that this strange behaviour only manifests when the 2nd segment of our five segment chart of accounts structure is present.
I have checked the properties of this field and can see nothing strange, when compared to its (working) peers.
Could it be a problem related to the dimension hierarchy that is associated with this chart of accounts dimension>??
thanks for your input,
Robert.
Edited by: Robert Angel on 08-Dec-2011 07:30 additional detail
Edited by: Robert Angel on 12-Dec-2011 07:33
Edited by: Robert Angel on 19-Dec-2011 08:07

To explain the structure first; -
Chart of Accounts Dimension
Trust Id
Cost Centre
Expense Type
Sub Expense Type
External Organisation
Each level of the hierarchy is from the same phyical table 'Chart of Accounts'. The dimension references the underlying field as the Key at each level.
Financial Periods Dimension
Year
Quarter
Period
Again all are from the same physical table, again all use the underlying field as the key at each level.
FACTS table has; -
Actual in Month, Budget In Month, Month Ago Actual in Month
Working scenario ; -
Add; -
Cost Centre, Actual in Month, Budget In Month, Month Ago Actual in Month
Filter on period_name = 'NOV-11'
Cost Centre in ('801040','801041')
results; - (works fine!)
Cost Centre, Actual in Month, Budget In Month, Month Ago Actual in Month
801040                 50000          65000                    55000
801041                 15000          18000                    19000To the above scenario I can add any of the other Chart of accounts segments and it works.
When I add Expense Type I get
Cost Centre,   Expense Type, Actual in Month, Budget In Month, Month Ago Actual in Month
801040                3001                    50000          65000                   55000i.e. I still get results, but less cost centres than I had when only cost centre was included.... all other things being equal??!!
I can workaround this by pulling my concatenated version of all codes to get the full chart of account 'string' and then use substring to pull expense type only out of it, but this is less than ideal to suggest to a user community when it should work as is...
Anyone seen anything like this before, can give me anything to investigate that might be making the difference??
Edited by: Robert Angel on 13-Dec-2011 02:20
Edited by: Robert Angel on 14-Dec-2011 08:28

Ago function with two dates

I use OBIEE and I got some difficulties with the times dimensions and the function AGO because I used two differents dates for my measure.
My fact table:
Ordered ||Delivered||Amount
12/21/2008 ||1/20/2009||30000
1/1/2009 ||2/1/2009 ||20000
1/1/2009 ||3/1/2009 ||10000
2/1/2009 ||2/1/2009 ||50000
2/1/2009 ||3/1/2009 ||50000
12/25/2009||1/15/2010||10000
1/1/2010 ||2/1/2010 ||25000
1/1/2010 ||3/1/2010 ||20000
1/1/2010 ||2/1/2010 ||20000
1/1/2010 ||3/1/2010 ||15000
I have two Times Dimensions (Ordered Times AND Delivered Times) and one fact table. I already tried with 2 facts table and 1 time table without success too cause they not link the value for delivered and ordered
I want to compare the delivered situation (Amount Qty) for the same ordered day last year
I created a prompt with a date (ex.: Ordered date <=1/1/2010 AND Delivered date >=1/1/2010) and I want to compare one year ago with 1/1/2009 (Ordered Date situation…)
I wish the results below:
Delivered Month||Amount||Previous Amount Year Ago
1 || 10000 || 30000
2 || 45000 || 20000
3 || 35000 || 10000
I got some problem cause I had the 100 000 in my previous year (Ago) and I don’t want it because it was ordered after 1/1/2009 (Previous year). I know that the ago function concerns the Sum of Amount by Delivered Date, Year -1 ...
Does somebody has a solution for this ? Thank you

Hi,
The problem is that I only know the offset values at row level, i.e., when I run my answer report some records use a certain offset value (offset1) while others use another offset value (offset2)
The offset value can be determinate by a logical column.
Is it possible?
Thanks.

Ago function not working properly with time dimension

Hi all,
In OBIEE 11g we have the following issue:
We have a fact which contains transaction's sum for the last day of each month.
We use ago function like this : ago(<fact.column>,1)When we want to see the result from the time hierarchy the fact with the ago function works properly for quarters and half years but for the months shorter than the previous one can't take the right value /equals to NULL/.
For example :
sum for YEAR: 10000
sum for Half Year 1 : 4000
sum for Half Year 2 : 6000
sum for Quarter 1: 1000
sum for Quarter 2: 3000
sum for Quarter 3: 2000
sum for Quarter 4: 4000
sum for month... - here the ago function is confused with the last day of previous month if it's shorter than itself: For example - for march it cannot take value for end of February ..etc.
Any ideas?
Thanks in advance,
Alexander.

Hi,
I faced some issues previously with month, so I used month+year as id instead of month id. Instead of tragging month id 1-12 into your hierarchy, create another column into your table like month+year - 201201, 201202 which creates unique month_year_id and drag this column into month level instead of month_id. So the problem might be solved.
Regards,
Anitha.B

Incorrect values with AGO function

Similar Messages

Maybe you are looking for