Material attributes in separate dimension?

Hi BW experts,
As a new member I have been looking for a similar topic but unfortunately I can't find anything on it so I was hoping one of you could help me out.
I want to redesign our stock/movement cube due to performance issues. One step is to have the 0MAT_PLANT as a separate (line-item) dimension as opposed to a charateristic of 0MATERIAL. I assume this will help a great deal since 0MAT_PLANT has over 8.5 M entries which does not really help to speed up any queries. (fact table has about 40M records)
Another thing is that I would like to create a separate dimension with 0MAT_PLANT navigational attributes like service level, ABC indicator etc. These fields are now in the material dimension and I reckon these nav attr blow up the dimension massively since one material has multiple service levels and ABC indicators. Can I just drag in these field into a new dimension, say Material Attributes and still have them in there as master data?!
In other words, can I create a dimension with only 0MAT_PLANT navigational attributes and what are the consequences of this?
Thanks heaps!
Cheers,
Niels

Thanks Pizzaman.
I do not think it will be a good idea to physically put the master data in the cube in my case so I have to keep it as master data.
Can you explain to me what happens when I take the following steps:
I take out the 0MAT_PLANT characteristic (which has 8.5M records) and create a separate (line item) dimension for it and I leave the NA for 0MAT_PLANT (like service level and ABC indicator) in the Material dimension.
Would this have any impact on the number of records to be read when I run a query for plant, material and ABC indicator?
Doesn't the query still have to read the 8.5M records which are now in the 0MAT_PLANT dimension instead of the 0MATERIAL dimension?
So does creating a separate 0MAT_PLANT dimension have any impact on query performance?
I do understand you point about the indexes and that might work.
Hope you can help me with this
Thanks.
Cheers

Similar Messages

When should an attribute be placed in a separate dimension

heyyyyy
when should an attribute be placed in separte dimension

HI,
you can't keep any attribute in separe dimension, but you can keep Charecter in separate dimension, i.e. Line Item Dimension. See the following link
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Thanks
Reddy

Force OBIEE to display attribute as dimension property and not separate dimension

Hello,
I have following question - in my project which utilizes Essbase and OBIEE I am interested in display of attribute as a characteristic of dimension and not as separate dimension.
OBIEE generates following mdx statement:
With
set [_Prod.Manufacturer2] as '[Prod.Manufacturer].Generations(2).members'
set [_Product6] as 'Filter(Descendants([Product], 8), (([Product].CurrentMember.MEMBER_Name = "P3336" OR [Product].CurrentMember.MEMBER_ALIAS = "P3336")))'
select
{ [Measure].[Volume] } on columns,
NON EMPTY {crossjoin({[_Prod.Manufacturer2]},{[_Product6]})} properties MEMBER_NAME, GEN_NUMBER, [Prod.Manufacturer].[MEMBER_UNIQUE_NAME], [Prod.Manufacturer].[Memnor], [Product].[MEMBER_UNIQUE_NAME], [Product].[Memnor], [Product].[Alias_table_1] on rows
from [APP.DB]
while I am interested in achieving following - where attribute Prod.Manufacturer is displayed as property of Product dimension and not as separate attribute
With
set [_Axis1Set] as '{Filter(Descendants([Product], 8), (([Product].CurrentMember.MEMBER_Name = "P3336" OR [Product].CurrentMember.MEMBER_ALIAS = "P3336")))}'
select
{[Measure].[Volume]} on columns, {[_Axis1Set]} properties [Product].[Prod.Manufacturer],MEMBER_NAME, GEN_NUMBER, [Product].[Memnor], [Product].[Alias_table_1] on rows
from [APP.DB]
OBIEE generates expected syntax for Alias tables, is same possible with attributes?
How ?
thx
Tomek

Thanks heaps for your answer, Vladim!
That's funny, huh? As mentioned, in respect to the Workstatus control, SAP made that functionality available for the Owner property of the Entity dimension (i.e. more than one user can be declared as an owner of a e.g. Cost Center and could hence change a particular Work Status).
Any ideas for a workaround ?
Have a good weekend...
Claus

Can not see the attributes of the dimension added in an existing structure

I have to add a formula on the attributes of a dimension that i included in anexisting structure. But when i try to create the formula it does not show the attributes or that dimension. Early help would be appreciated.
Thanks in Advance
Murali

Hi Manish
Yes this is a display attr. if i change it to Nav attri. will this not effect business as this is being used.
Thanks
Murali

Material Attribute value display based on cost center value

Hi,
Is it possible to display the material attribute value based on cost center value. I mean for some cost centers I would like to display the value of other characteristic in place of material attribute. I am trying to create a query on MP.
Any info in this regard will be appreciated.
Thank you.
Harshan

Hi Adi,
In Rows, Create a struture. Using New Selection, You can restrict the New Value to the cost center (Restrict again on those some cost centers) and material. And for this New Characteristic, you can have a attribute.

Copying one material attributes to another material thro' FM or BAPI

Hi,
My requirement is :
To copy a material attributes from one material(old) to an another material(new). Can anybody suggest a FM or BAPI for this?
Thanks,
Kaarthick

Hi,
These answers never helped me. I can reformat my quesion : Pls. suggest a BAPI/RFC/FM used to create a new material with reference to an old material.
Hope this is understandable one.
Thanks,
Kaarthick

Compound Attributes&Line item Dimensions

Hi,
Plesae can anyone expalin me about compound attributes & Line item dimensions
Thanks,
Gal

Please search...there are many threads about this in the BI forums.

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

ORA-35563: Multiple values exist for an attribute of this dimension member

After following the tutorial Building OLAP Cubes I was trying to make a cube with aggregation down to the day instead of down to the month.
I created a times table pretty similar to the one used in the tutorial:
CREATE TABLE EVENT_TIMES (
        HOUR_KEY        DATE NOT NULL,
        DAY_ID          VARCHAR2(10),
        DAY_NAME        VARCHAR2(10),
        DAY_END_DATE    DATE,
        DAY_TIME_SPAN   NUMBER,
        MONTH_ID        VARCHAR2(30) NOT NULL,
        MONTH_NAME      VARCHAR2(40),
        MONTH_END_DATE DATE,
        MONTH_TIME_SPAN NUMBER,
        YEAR_ID         VARCHAR2(30) NOT NULL,
        YEAR_NAME       VARCHAR2(40),
        YEAR_END_DATE   DATE,
        YEAR_TIME_SPAN NUMBER
As you can see, instead of a DAY_KEY like in the tutorial, I now use an HOUR_KEY.
This is a sample of the data I inserted in this table:
select to_char(hour_key,'YYYYMMDDHH24MISS'),DAY_ID,DAY_NAME,DAY_END_DATE,DAY_TIME_SPAN,MONTH_ID,MONTH_NAME,MONTH_END_DATE,MONTH_TIME_SPAN,YEAR_ID,YEAR_NAME,YEAR_END_DATE,YEAR_TIME_SPAN from event_times;
TO_CHAR(HOUR_KEY,'YYYYMMDDHH24MISS') DAY_ID     DAY_NAME   DAY_END_DATE DAY_TIME_SPAN MONTH_ID                       MONTH_NAME                               MONTH_END_DATE MONTH_TIME_SPAN YEAR_ID                        YEAR_NAME                                YEAR_END_DATE YEAR_TIME_SPAN
20140104050000                       Y2014M1D4 Y2014M1D4 04-JAN-14                1 Y2014M1                        Y2014M1                                  31-JAN-14                   31 Y2014                          Y2014                                    31-DEC-14                365
20140104060000                       Y2014M1D4 Y2014M1D4 04-JAN-14                1 Y2014M1                        Y2014M1                                  31-JAN-14                   31 Y2014                          Y2014                                    31-DEC-14                365
I then created my TIME dimension with DAY as the lowest level.
When I try the maintain cube option it fails at the 'LOAD NO SYNCH' step with the rejected records having an error message that says:
ORA-35563: (XSRWLD17) Multiple values exist for an attribute of this dimension member.
To me, this is a very cryptic message and the only explanation I find online is:
Cause
Multiple source table rows containing different values for a dimension attribute were found. Only the first of the multiple rows has been loaded.
Action
Fix the mapping or remove the rows with conflicting attribute values..
This confuses me. In the tutorial the lowest level was day and the TIMES table contained 1 record for each day.
In my example, the lowest level is hour and the TIMES table contains 1 record for each hour.
Which attribute has multiple values? And which values?
The rejected records (101) are not very clear:
ALIAS_1 = 'MONTH_Y2014M1' AND ALIAS_3 = to_date('31JAN14') AND ALIAS_4 = 31 AND ALIAS_5 = 'Y2014M1' AND ALIAS_6 = 'Y2014M1' AND ALIAS_7 = 'YEAR_Y2014'
If anyone can help point me in the right direction, it would be greatly appreciated.

I have seen this recently. The issue is with the dimension load itself. You have a hour level record table but the rules relating to hierarchy/attribute values etc are checked/reinforced during the load and this error comes up sometimes.
I would guess that the issue seems to be with your month level information present in the higher level month columns. There are many records corresponding to a single month in ur case, month of Y2014M1. Information relating to Month level member Jan 2014 or member MONTH_Y2014M1 is present in these records: 31 (days) *24 (hours) = 744 records. The data in these 744 records for columns - MONTH_ID, MONTH_NAME, MONTH_END_DATE, MONTH_TIME_SPAN need to be exactly the same in order for the single member MONTH_Y2014M1 to have month attributes loaded with valid values.
For e.g: if records #1 to #743 contain month_timespan=31 but for some unknown reason record #744 contains month_timespan=30 then this error will come up. OLAP does not know which value to load (31 or 30), and only 1 value can be loaded onto the month level member corresponding to month Y2014M1.
A quick check of the data should give you the answer. Typically there may be some mistake/invalid assumptions made with the boundary records (in your case, check for values for records corresponding to hour=0 or hour=23/24) which is causing the issue.
HTH
Shankar

Material attribute assigned to a DSO field

Hello All,
A Material attribute needs to be filled with a field from the DSO and should not consider the value which it actually holds in the InfoObject Material.
Is it possible to assign this attrbiute without adding a individual field in the Cube?
Regards,
NK

Hi,
Write a routine in Transformation of Info Object to read data from active table of DSO. To ignore the value from source, nothing to do except not to map.
Thanks
BVR

Material Attributes - cFolder

Hi All,
I could access Material Attribute file through webDAV and make the changes for additional material types..
There are many fields maintained in Material Master in R3 as Class and Characteristic values..
Is there any way to export these values too to cFolders when we export Material, BOM from R3
Regards,
Aby

Hi Ulf,
What kind of classification data would you like to export?
I need to explain the scenario, and am not sure the approach is correct
We are trying to map Agile PLM functionality here.. Ultimate aim is to export BOM as PDX package. For this
1) We are exporting BOM from R3 to cFolders using CFE02
2) From cFolders , extracting as PDX
When I went though customizing we have "Specify Field Mapping Profile for PDX Package Import and Exp"
Inside 0SAP_CFX Profile for Master Data Item , there are many XML attributes like
- Code of Lifecycle phase
- Product line
-Unique Label of Item
-Make or buy decision and many more
Where can we map these attributes in cFolders?
As the BOM's are exported from R3, we thought we will put the above attributes as CHARS in Classification
Regards,
Aby

Dynamically adding more attributes to cube dimension in SSAS 2008 R2

I need to dynamically add more attributes to cube dimension in SSAS 2008 R2 because the dimension table the cube is based on is updated using dynamic pivoting and there is need to update the cube dimension attributes as more columns are added to the dimension
table without making the changes through BIDS. Is there a way to dynamically adding more attributes to cube dimension in SSAS 2008 R2?
Thanks
BI Developer

Definitely. You can use AMO to add dimension attributes on the server. I have definitely done this a few times for different clients of mine. Here is a generic AMO sample:
http://msftasprodsamples.codeplex.com/wikipage?title=SS2008%21Readme_AMOAdventureWorks&referringTitle=Home
Notice the parts which add attributes to a dimension.
http://artisconsulting.com/Blogs/GregGalloway

Update new material master weight and dimension in open sales orders and de

Hi,
Iu2019m maintaining gross weight, net weight, volume in material master. When the time of sales order entry in VA01 its calculating weight and dimensions based on material master and order quantity. And I create deliveries in VL01N.
If I made a correction in the net and gross weight in material master after I created the sales order will the correct net and gross weight will pick up at the delivery creation.
In other term is the VL01N net and gross weight is taking from which is available in SO or Material master.
Is there any standard transaction to update already existing open sales order, delivery net and gross weight once it is corrected in material master?
Please advice.
Sam

Is there any standard transaction to update
No it is not possible to update the weight in existing sale order or delivery. You have to change it manually or create a new sale order. Weight in delivery will be fetched from sale order only and hence, whatever delivery you create referencing a sale order, system will copy whatever is there.
thanks
G. Lakshmipathi

OLAP query returning "name" rather than "key" attribute for a dimension

Hello,
I am busy with a project that involves drawing data from an OLAP cube (in SAP BW), then transforming and contextualising for use in an EMI environment. The project runs on MII 12.1.
The standard OLAP connector and OLAP queries have been used (would prefer not to go the route of creating a call to the OLAP XMLA web service directly). One of the important dimensions is returned as a name (descriptive text) rather than a key (the cost element code itself), preventing us from reliably applying business rules to classify cost elements. Categorising cost elements based on their text descriptions is not a sustainable solution.
The output needs to allow for two dimensions (cost element and an equipment identifier) against which individual cost values will be listed. It appears that the two dimensions must both be on the "x-axis", as result columns are automatically renamed, e.g. C000001, C000002, etc. If anyone knows of a way to suppress this renaming behaviour, please let me know.
Is it possible to force the "key" attribute to be returned instead of the "name" attribute? I have identified two preferred options:
1. MDX syntax of the query itself
2. configuration of the OLAP connector
I have not found a way to do this through MDX syntax, but would welcome any suggestions.
Alternatively, perhaps there is a non-standard way of configuring the OLAP connector so that the key rather than the name attribute is returned for all dimensions. Has anyone anything, e.g. chosen a non-standard ColumnNameAttribute or DataTypeAttribute, in this regard?
Thanks,
Marc Chaplin

<b>Apologies for the formatting above</b>
Part 1:
Hello,
I am busy with a project that involves drawing data from an OLAP cube (in SAP BW), then transforming and contextualising for use in an EMI environment. The project runs on MII 12.1.
The standard OLAP connector and OLAP queries have been used (would prefer not to go the route of creating a call to the OLAP XMLA web service directly). One of the important dimensions is returned as a name (descriptive text) rather than a key (the cost element code itself), preventing us from reliably applying business rules to classify cost elements. Categorising cost elements based on their text descriptions is not a sustainable solution.
The output needs to allow for two dimensions (cost element and an equipment identifier) against which individual cost values will be listed. It appears that the two dimensions must both be on the <i>x-axis</i>, as result columns are automatically renamed, e.g. C000001, C000002, etc. If anyone knows of a way to suppress this renaming behaviour, please let me know.

Error occured whenever adding an attribute to a dimension

After I added an attribute to a new dimension, I encountered the error as below.
I also cannot read the metadata from Jdeveloper after I create a cube using AWM.
Please kindly help!!
BI Beans Diagnostics(v1.0.2.0) 2005/9/15
===============================================================================
JDEV_ORACLE_HOME .......................... = C:\jdev1012_base
JAVA_HOME ................................. = c:\j2sdk1.4.2_02
JDeveloper version ........................ = 10.1.2.0.0.1811
BI Beans release description .............. = BI Beans 10.1.2 Production Release
BI Beans component number ................. = 10.1.2.52.0
BI Beans internal version ................. = 3.2.1.0.13
Connect to database ....................... = Successful
JDBC driver version ....................... = 10.1.0.3.0
JDBC JAR file location .................... = C:\jdev1012_base\jdbc\lib
Database version .......................... = 10.2.0.1.0
OLAP Catalog version ...................... = 10.2.0.1.0
OLAP AW Engine version .................... = 10.2.0.1.0
OLAP API Server version ................... = 10.2.0.1.0
BI Beans Catalog version .................. = N/A; not installed in BI_TEST
OLAP API JAR file version ................. = "10.1.0.2.0"
OLAP API JAR file location ................ = C:\jdev1012_base\jdev\lib\ext
Load OLAP API metadata .................... = Successful
java.lang.NullPointerException
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.setDimAttributes(MDMMetadataDriverImpl_92.java:1733)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.getChildren(MDMMetadataDriverImpl_92.java:197)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.addChildren(MDMMetadataDriverImpl_92.java:2687)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.fillOlapObjectModel(MDMMetadataDriverImpl_92.java:2571)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92$LoadOlapObjectModel.run(MDMMetadataDriverImpl_92.java:3013)

I've got it resolved.
I have to add levels and hierarchies before adding any attribute.
That's strong!

Material attributes in separate dimension?

Similar Messages

Maybe you are looking for