Time Dimension Type allows different values in attributes - Bug or Feature?

Not sure if this is a bug or a feature.
But if one has multiple hierarchies on a Time dimension. You have the ability to specify different values for member attributes in different hierarchies.
Example.
Hierarchy A has MIN_ID for it's Member and uses MIN_END_DATE for it's END_DATE
Hierarchy B has MIN_ID for it's Member and uses SESS_END_DATE for it's END_DATE
As per this post and David Greenfield's comment:
Dimension Sort issue when multiple mappings for different hierarchies
"Are you attempting to map the same attribute, SORT, to different columns in the two hierarchies? Put another way, do you expect the same member to have different values for the attribute in the two different hierarchies? If so, then this is a problem since a member must have the same value for the attribute regardless of the hierarchy."
Unlike a user dimension, a time dimension appears to allow this and it appears to work as intended. Is the behavior in this case intended to be different between a user and time dimension?

I think that this is not a bug. There is an incompatibility in design which prevents you from using the same attribute differently for both hierarchies.
NOTE: Unlike parent relationship which depends on <dimension, dimension hierarchy>, Dimension Attribute is dependent on <dimension> alone, not dependent on <dimension, dimension hierarchy> combination. Hence it can only take on 1 value for 1 dimension member.
I think that the time dimension only appears to allow this. The key thing to check is for Time Dimension members which are common to both the hierarchies. Only one of the mappings will take effect (usually the hierarchy which is loaded last will remain in the aw/usable for queries, reports.. it would have over-written the earlier attribute value loaded as per the earlier hierarchy load).
Visualize a dimension as a long list of members which are built up contiguously on a per hierarchy, per level process using the mapping information saved. Once a member is defined (created) via Hierarchy A, it wont be created once again while loading Hierarchy B but is instead updated or redefined based on Hierarchy B's mapping info.
Assuming the dimension load attempts to load Hierarchy A first and then Hierarchy B,
* Dimension load for Hierarchy A will define the various members using MIN_ID and set the END_DATE attribute to value=MIN_END_DATE
* Dimension load for Hierarchy B will re-define the various members using MIN_ID and re-set or over-write the END_DATE attribute to value=SESS_END_DATE
* In this case, it looks like all members are common for both hierarchies (as both members are mapped to same column MIN_ID) and you would end up with END_DATE=SESS_END_DATE.
Actually whether all members are common to both hierarchies or not depends on the quality of data in your snowflake/star table: if parent level for Hierarchy A as well as Hierarchy B is setup fine then the members will be same set (overlapping in whole). If some rows for MIN_ID have parent column for Hierarchy A setup correctly but parent column for Hierarchy B =null or invalid value then that member will exist in Hierarchy A alone and would contain END_DATE=MIN_END_DATE as the corresponding update along Hierarchy B would fail due to hierarchy data quality issues (join from current level to parent level).
As regards a solution to your problem, you should not use the same attribute "SORT" for dual purpose (both hierarchies). Instead define attributes SORT_A and SORT_B and make them enabled for Hierarchy A, Hierarchy B respectively and map/use them appropriately in your reports.
HTH
Shankar

Similar Messages

Setup time dimension in some different fiscal calendars

I have the different fiscal calendars.
Then, I wanna compare the current month fiscal amount and the previous month fiscal amount with AGO function.
The calendars are like below.
Calendar A : fiscal month start April
Calendar B : fiscal month start January
In this case, how should I define the chronological key in the time dimension?
For example, I try the below setup in the calendar period hierarchy.
Year 2008
Half 1H 2H
Quarter 1Q 2Q 3Q 4Q
Month 1Q = {Apr-08 in CAL_A, May-08 in CAL_A, Jul-08 in CAL_A, Jan-08 in CAL_B, Feb-08 in CAL_B, Mar-08 in CAL_B}
and some.
In this examle, the number of MONTH level members are 24.
Then I make a column for sort.
The sort number is below.
For CAL_A
Month SortNo.
Apr-08 1
May-08 2
Jun-08 3
Jul-08 4
Aug-08 5
Sep-08 6
Oct-08 7
Nor-08 8
Dec-08 9
Jan-09 10
Feb-09 11
Mar-09 12
For CAL_B
Month SortNo.
Jan-09 13
Feb-09 14
Mar-09 15
Apr-08 16
May-08 17
Jun-08 18
Jul-08 19
Aug-08 20
Sep-08 21
Oct-08 22
Nor-08 23
Dec-08 24
In this case, if I try to get the previous month of Jan-09 in CAL_B with AGO function, the system get Mar-09 for CAL_A. Because the record of Mar-09 for CAL_A is 12 in SortNo. column.
As far as possible, I wanna use AGO function.
Does anyone have good ider for this problem?
Edited by: user3532462 on 2008/08/28 2:57

Hi,
I guess it's easier to setup two different time dimensions; one for calendar A and one for calendar B. Use aliases in the Physical Layer.
Good Luck,
Daan Bakboord

COPA - Split of Value from condition type into different value fields

Dear All,
Customer is having several free schemes to customer the same is set up by SD and Cost of free goods is attached to One Z condition type, this flows along with Main product as characteristic. So we have Main product cost in VPRS and Scheme cost in Z Condition and there is possibility of more than one scheme cost flowing in one Z condition for single billing document. Whereas customer request is to see the each scheme cost separately in COPA. Since Value from SD will be flowing through only one condition type , it will be difficult to me to Split this in COPA. We have given a thought of having more than one condition type from SD ( one Z condition for one scheme) but this resolve our issue at hand. If we look at long term whenever customer introduces new Scheme new condition type need to be created and related COPA changes etc, Which doesn't seem to be working out.
Request Experts help in this, thanks in advance for the help.

Hi Santosh
Having a Z cond type for each scheme is preferrable.... This would address the issue with Standard SAP itself...
Reason being, if you dont do that, then you will have to maintain a mapping somewhere in a Z Table where by system would come to know of the ratio between the schemes... This will be more cumbersome to develop and maintain... Still you wanna do that, here is the logic....
Maintain the schemes in a Z Table... Where each scheme will have a scheme ID - The ratio applicable to various schemes and also the relevant value fields of COPA to be updated for each scheme....
Now, add a Custom Field to the Sales Order and while creating the SO this field needs to be updated with the scheme ID(Relevant Exit to make it mandatory MV45AFZZ / ZB).... If Scheme ID is populated, your Billing should read the Split from Z Table using Exit RV60AFZZ and Update COPA using Exit COPA0002
br, Ajay M

IT0041 : Same date type with different values in the same infotype

Hi,
Is it possible to store in the 0041 infotype, the same type date but with a diffentent date.
Example :
IT0041
employee 1000:
date type : xx 01.05.10
date type : xx 02.05.10.....
Thanks

Hi there,
My two cents.
I don't think it can be done in standard. Also copying IT 0041 would limit you to enter only 12 dates.
My suggestion:
Create a custom infotype with subtype field and a date field like IT 0015.
On the screen you will only be seeing subtype and date. And assign time constraint 3 to it.
In this way with the same subtype you can record several dates.
cheers
Ajay

Polar chart type: show different values

Hello,
I have a polar chart type it would be work pretty good but I have a question. For the chart type I created a query and the result looks so:
<b>Region</b> <b> real Value   calValue</b>
EMEA                 -5%                 95
LATIN                  8,3%               108,3%
For the chart type itself is the calValue e.g. 95 important. But I want to see the Value -5%.
That means the chart type pictures works with the calValue but the User should see the realValues. Is it possible?
Thanks a lot for your help
CU
patty

Check out our sample reports by downloading them. Most have charts to show you how to use them.

Time Dimension - Additional Attributes..

Hi
We are building a Financial Services BI Applications. In one of my Cube, for Time Dimension, i need to add more attributes like
for Month Level i need the following
a) End Date of the Month
b) No of Days in the Month
at Quarter Level
a) End Date of the Quarter
b) No of Days at the Quarter
and likewise.
I can do this in AWs using attributes, however in essbase since i have to tag the TIME dimension as DENSE, it is not allowing me to create any attributes. Has somebody solved this problem in the past. Please help.
Thanks
bala

Any more recommendations please..
I cannot use UDAs as it expects that the consumer of the UDA knows the value set.
i.e. in Time Dimension assume the leaf is
200701 (UDA 31)
I would want something like this
if provided 200701 then the server should return 31 as the number of days.. However if i use UDA then i can only check (if @UDA(200701) = 31) then
here it assumes that i know the attribute value before hand which i would not know..
Please help as we are reaching a critical stage in our project
Thanks
bala

Multiple time dimension hierarchies ?

Hi, is it possible to easily define multiple hierarchies in a time based dimension ?
I know the time dimension wizard allows the definition of only 1 hierarchy but I need to have a time dimension that has both a calendar based and a fiscal calendar hierarchy.
It is possible to modify the dimension definition after using the wizard but I don't think the original mapping automatically generated by the wizard is updated.
Anyone done this ?
Thanks
Paul

Hi,
Did any of you manage to create the extra hierarchy in the time dimension?
I also created the standard time dimension with only one fiscal hierarchy first, but later found the need to add another fiscal hierarchy that has month as the leaf level (does not include day level). However, when deploying, I get the message "ORA-00957: duplicate column name"...
(Reason for defining other hierarchy without the day level is that it seems that when using auto-solve on a compressed cube, it tries to solve from all leaf levels upward, but one cube I have is loaded at the month level of the time dimension... day level is not applicable in this specific cube. Using the standard fiscal hierarchy in this case does not work on that cube.)
Thanks,
Ed
PS Looking at the ddl script from the Job Details window, the duplicate columns are in the auto generated stage tables/views (for month and quarter level; not for year level(?)). How can we influence OWB to generate the correct things???
Create table "OWB$STGTBL_D_DI_FISCAL__2B6926" (
FISCAL_QUARTER_F_2B69262B6934 number,
FISCAL_QUARTER_F_2B69262B6934 number);
Create table "OWB$STGTBL_D_DI_FISCAL__2B6915" (
FISCAL_MONTH_FI_2B69152B6926 number,
FISCAL_MONTH_FI_2B69152B6926 number);
Message was edited by:
EdSp

OLAP time dimension - how are the weeks allocated

Could someone please help me understand what logic Oracle uses when one makes use of Oracles OLAP time dimension based on weeks.
I am use Oracle OLAP 11.2
I have a Time dimension that has the following hierarchy:-
YEAR
QUARTER
MONTH
WEEK
For calculating the weeks ID I make use ISO week and year i.e. IYYYIW
For calculating the end date I use the following:- NEXT_DAY( l_date, 'MON' ) -1
i.e. the weeks end date is the Sunday.
According to me this is the required result.
Problem is that for some months there are 3 weeks allocated which makes no sense to me.
I cannot understand the logic used in allocating the weeks.
The following is an example:-
the following weeks were allocated to the month February
201306 (end date= 10-2-2013)
201307 (end date= 17-2-2013)
201308 (end date= 24-2-2013)
but the following week was allocated to January which makes no sence to me,
I would have expected it to be found in February
201305 (end date= 3-2-2013)
Week 201309 (end date= 3-3-2013) was allocated to March which according to me is correct..
Another example is week *201030 (end date= 1-8-2010)* that is allocated to July while I would have expected that it should be August.
I would have thought that it uses the end date that is placed in the mapping to determine the month to place it in.
Could some one please explain what the reason for this could be.

Oracle OLAP model/design (in this case, at least) cannot compensate to coverup existing flaws in the relational model/design.
I dont think this is a valid hierarchy even considering relational model/design.
Weeks do not fit in below Months (calendar months).
You can force fit them by making Weeks the source of truth and making all Months logical Months like "Business Month", "Business Quarter", "Business Year" etc. which will be composed of whole weeks but differ significantly from the calendar definition of Month, Quarter, Year etc.
You are better off modeling time as composed of two hierarchies:
H1: DAY -> MONTH -> QUARTER -> YEAR and
H2: DAY -> WEEK
Alternately if you dont want to introduce DAY level (lower granularity), you can split up the Time dimension into 2 different dimensions. And also modify your star schema to add an additional time dimension key to fact table - one key pointing to WEEK and another pointing to MONTH (independently).
TIME_MO: MONTH -> QUARTER -> YEAR
TIME_WK: WEEK
The fact data will need to be split up to correctly identify the coirrect MONTH-WEEK combination for the relational record.
E.g:
Fact table should have 2 dimension Fks for WK_KEY as well as MO_KEY so that a fact figure of 1000 evaluated over 7 days is split up into 300 from 29-31st of previous month and attached to MO_KEY of previous month and another record of 700 covering days from 1-4 and recorded/tied to same WK_KEY but next month (next month's MO_KEY).
HTH
Shankar

SAP HR: What r TIME WAGE Types

Hi Gurus,
What r TIME WAGE TYPES.how to create them.i came to know that they r used to create Overtime only.
plz let me know the purposes of Time wage types and different ways to use them.

Hi,
Time Type
A time type is a grouping of times according to various aspects such as payment regulations, internal company requirements and control tasks.
A time type assigns a meaning to a time interval. The balances formed in time evaluation are posted to the time types.
When you customize the system, you can define for each time type whether
it should be transferred to the day/period totals
it should be taken over from the previous period/year
it should be transferred to cluster B1 (for entry data)
Not necessay for OT but for all u can mantain with table T555A.
Thanks

Update from ATP timeseries indicator different values in APO DB & Livecache

Hello experts,
Our Basis team has ran the Livecache and DB consistency check (OM17) transaction and all the inconsistencies has been removed,but we are encounturing an error "The update from ATP time series indicator has different values in APO DB and Livecache " in 000 version. I have checked the version managemet for 000 and under ATP tab the option Update from ATP time series is unchecked. Can you please let me know the reason for this error and what else i.e. the configuration settings i have to check to wipe out this error.
Quick help is appreciated.
Thanks.
Dhanunjay.

Hello Kaushik,
Thanks for your reply.
The indicator update update from ATP time series is only set during the creation of active version for product availability check time series update, but we are not using any ATP time series.
How ever it's unchecked for active version 000, but when i checked for the entries in the table /SAPAPO/APO01 there the ATP time series activation indicator is set. Iam confused about the differences, i guess this might be causing the error,if so i have to alter the table or delete the version and recreate. Can you please guide me which would be the better option.
Thanks.
Dhanunjay .

What are the different values available for type attribute

Hi,
    I am working with IDOC to Stored Procedure. For each field we need to give the values for 'isInput' and 'type' attributes. I need to pass values for 'datetime' and 'numeric' fields. What are the list of values availabIe for 'type' attribute. I know only about 'CHAR' attribute.
     Can anybody please tell me what all the values availabe for attribute 'type'. I am facing this problem while giving the value for type attribute.
Thanks in Advance,
Murthy.

Does this help
tring
    Data that contains a combination of letters, numbers, and special characters. String data types are listed below:
CHARACTER: Fixed-length character strings. The common short name for this data type is CHAR.
VARCHAR: Varying-length character strings.
CLOB: Varying-length character large object strings, typically used when a character string might exceed the limits of the VARCHAR data type.
GRAPHIC: Fixed-length graphic strings that contain double-byte characters.
VARGRAPHIC: Varying-length graphic strings that contain double-byte characters.
DBCLOB: Varying-length strings of double-byte characters in a large object.
|BINARY: A sequence of bytes that is not associated with a |code page.
|VARBINARY: Varying-length binary strings.
BLOB: Varying-length binary strings in a large object.
|XML: Varying-length string that is an internal representation |of XML.
Numeric
    Data that contains digits. Numeric data types are listed below:
SMALLINT: for small integers.
|INTEGER: for large integers.
|BIGINT: for bigger values.
DECIMAL(p,s) or NUMERIC(p,s), where p is precision and s is scale: for packed decimal numbers with precision p and scale s. Precision is the total number of digits, and scale is the number of digits to the right of the decimal point.
|DECFLOAT: for decimal floating-point numbers.
REAL: for single-precision floating-point numbers.
DOUBLE: for double-precision floating-point numbers.
Datetime
    Data values that represent dates, times, or timestamps. Datetime data types are listed below:
DATE: Dates with a three-part value that represents a year, month, and day.
TIME: Times with a three-part value that represents a time of day in hours, minutes, and seconds.
TIMESTAMP: Timestamps with a seven-part value that represents a date and time by year, month, day, hour, minute, second, and microsecond.
Regards
Ravi

In billing document VAT condition type flowing 2 times with Different value

Hi,
1. In my requirement, In order creation time , in the pricing procedure ZPROJT (Proj Material Sales) VAT condition type (JLST) is flowing one time with the condition record of 5% for one line item and the same we changed manually to 12.75 %, for the same condition type (JLST) and we saved the order. After that we created delivery with reference to the same order, final the billing document creation time with reference to the delivery (in the pricing procedure ZPROJT (Proj Material Sales))for the same line item VAT condition type (JLST) is flowing 2 times with 2 different values ( 5% and 12.75%) and it is calculating the 2 different values to the final value. But normally only the manually changed (12.75%) value should be taken to the account. Please help me How to stop the condition type (VAT C Type "JLST") from flowing two times for the same line item in the billing - and we need to take the value of (12.75% manually changed value) to the final calculation.
2. In one pricing procedure normally if you add the same "C Type" for two times it will throw the error message like "Duplication Of C type" and you can't save the order with out deleting the same. Please tell me, where is the contole for the same.

Hi,
Check copy control settings in VTFL
At item level make pricing type as D - Copy pricing elements unchanged
KAPIL

TIME_DSO_1 attribute in Time Dimension

Hi,
We are using Oracle Analytic Workspace Manager version 10.2.0.3.0A for creating a cube.
We have defined a dimension as "Time" dimension and have also specified the dimension type as "Time".
This dimension has the levels: Year, Quarter, Month, Week and Day. These levels are for the one and only hierarchy of the Time dimension.
The attributes of the dimension (applicable to all the levels) are: END_DATE, LONG_DESCRIPTION, SHORT_DESCRIPTION, and TIME_SPAN.
In this structure, we are having a strange observation : During the process of defining this TIME dimension, there were some problems with the machine (it got hanged) and so we had to exit (kill) the AWM and come in again. When we logged in to AWM again, we could see a new attribute called TIME_DSO_1 defined within the Time dimension by itself.
Can anyone let us know what is this attribute all about ? And can we go ahead and just delete this from our dimension structure without creating problems for ourselves?
Many thanks in advance for the kind inputs of the forum.
Regards,
Piyush

Hi,
I can't say that I really understand how your data shows up, but I do see an error in your hierarchy.
What you should do is split it up into two hierarchies.
Year-> Quarter-> Month-> Day
and
Year-> Week-> Day
And here is the reason:
A day can easily have a week as a parent and month. But week cannot. Since a month can end on any given day in a week, that means that a week can have two parents. If I take the next week as an example. Mon, tue, wed, thu and fri would belong to the august month, while the rest of the week would belong to september. But the entire week would still be week 35. And its the same issue with quarter. Months can be added into a quarter, but weeks can not.
Now, I'm not sure if this would solve all your problems, but there might be a few other things you might check out and thats what ID's you populate your member fields with.
say that you have used the month numbers (or at least the same id for every january and so on)to populate your months. If that is the case things will also behave extremely weird and slow. What you need to do is to create unique IDs for every month (and any other level) so that you are sure that january 2007 don't have any child records that really should belong to january 2006.
As a general rule, the member field needs to contain a completely unique value across on from all levels. The "generate surrogate key" functionality helps you a bit along the way as it adds the name of your level in front of the value that you load. If the values you load doesn't have unique values within the level it won't help you any.
Hope this can help you some more... ;)
regards Ragnar

Aggregation mode along one dimension (product) different than along the time dimension

Dear All,
In IBP S&OP, Is it possible that the aggregation mode along one dimension (product) could be different than along the time dimension?
For a demo, a customer has an input at the product family level (vehicle production) which we just “copy” for disaggregation purposes, to the product level (parts), see attached. So for aggregation we used average.
However, time-wise, we need to sum it up.
Thanks for your insight and help.
Kind Regards,
Omar

Hi Omar,
Yes it is possible.
1. Create a new planning level (say PERPRODCUST1) which will be a copy of PERPRODCUST (you base planning level).
2. In the PER section of PERPRODCUST1, do NOT mark any period attribute as root. In other words, the roots for this PL will only be PRDID and CUSTID.
3. Now your KF calculations will be:
VEHICLEPRODUCTION@PERPRODCUST1 = SUM(VEHICLEPRODUCTION@PERPRODCUST)
VEHICLEPRODUCTION@REQUEST = AVG(VEHICLEPRODUCTION@PERPRODCUST1)
Since your KF is editable, it is worth mentioning that, following the above steps has trade-offs. Since your KF is editable, you will have issues with disaggregation when you enter the values at an aggregated level of both time and other attributes. My recommendation (for your configuration) is that this will work fine as long you enter the values at the root level of you time attribute.
Hope this helps,
Chendur

TIME dimension processing fails saying "..attribute key cannot be found.." in EPM 10

After upgrading from version 7.5 to EPM 10, when we ran a ‘Full Process’ on the TIME dimension, it ran into an error saying “Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'dbo_tblFactCapEx', Column: 'TIMEID', Value: '20090013'. The attribute is 'Time_TIMEID'. (1/13/2015 2:41:02 PM)”.
Full error message is attached herewith – ‘Time Dimension Error.txt’
After researching, we did discover that MONTHNUM needed to be converted to BASE_PERIOD. Re-processed which produced the same error.
Prior to migration to version 7.5, we ran a full process on TIME dimension there. It completed successfully, confirming the issue is only with version 10.
Confirmed we could see the TIMEID value of 20090013 in the following places:
Time Dimension in the appropriate TIMEID attribute column.
Confirmed mbrTIME table had base member ID with TIMEID attribute filled out correctly.
Data in tblFactFINANCE could be pulled using that TIMEID
We truncated all the records in all the fact tables associated to this TIME dimension.
Eventually, when none of the tables had any records, the TIME dimension then processed successfully.
We this began to suspect the issue may not really be related to bad records.
We conducted one more test to confirm this.
Using an input form in EPM 10, we manually entered data in one of the models (at this point none of the fact tables have any records)
Ran Full Optimize on that model with Compress Database and Index Defragmentation checked – This step failed with the error attached in ‘MatrixRateFullOptimize.txt’
Ran Full process on Time Dimension – Failed indicating issue with TimeID 2012001 (that’s my manual entry). Attached error report ‘TimeDim Error MatrixRate.txt’
At this point, the table only contains the manually entered records (no suspected bad records)
We then suspected there could have been an issue with the upgrade process.
So we reprocessed all the dimension and optimized all the models in version 7.5, made a new backup and restored it to version 10.
The issue still persisted!
At this point, we have tried all the possibilities we could think of. Each time the fact table is populated with records, the TIME dimension process fails indicating ‘the attribute key’ cannot be found.
There is probably something in the OLAP partition that is not able to link the dimension attributes to the cubes.
Additional Information:
Please find attached the existing Time Dimension – TimeDimensionMembers.xlxs
Version of Excel used: Excel 2007, SP3 MSO (12.0.6683.5000)
System Specs: Please see screenshot below.

Thank you all for responding! This issue is resolved.
Here’s what the issue was:
The time structure is TOTAL >> Years >> Quarters >> Months (e.g. T.ALL >> 2012.TOTAL >> 2012.Q1 >> 2012.P01)
As shown in the screenshot below, the LEVEL for ‘T.ALL’ member was set to YEAR, which is incorrect (we can’t have Year rolling up to a Year)
We changed the LEVEL to ‘TOTAL’ and this fixed the issue!!
If only it gave a better error message than the “..attribute key not found” message

Time Dimension Type allows different values in attributes - Bug or Feature?

Similar Messages

Maybe you are looking for