Setting up Dynamic Attribute dimension.

Hi,I have a dimension for my clients and a measure dimension for sales. I want to set up an attribute dimension called Band for my Client dimension. This should be set to "Band=Large" when the sales total for the client is more than 20000 USD in the previous year (2001) or it should be set to "band=Small" if the total sales for the previous year is less than 5000 USD or else "Band=Mid" if the total sales in the previous year is between 5000 to 20000 USD. Currently, I use excel sheet from the essbase database extrace the total sales for each range and use the same as input to set the attribute dimension. Is there a easy way to do this using calc script.regardssuja.

No, there isn't. Since attributes are member based, there is no way (at least in Essbase) to dynamically assign an attribute to a member based on a data point.However, there are ways around the problem, but I can see one dilema. What if sales for a client is "large" for a member of one dimension but "small" for another? Members are not intersection based, so a client cannot be tagged as "Large" for one intersection and "Small" for another.If you want to go the attribute route, there may be a way to automate the process you described in your post - perhaps running an extract from Essbase similar to your Excel report and having a script assign the attribute value according to the sales figures.If you want to use a calc script, you could create a "BAND" member in your accounts dimension and assign it a 1 (Small) 2(Medium) or 3 (Large) depending on the sales figures.Hope that helps.Regards,Jade-------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Similar Messages

Easy and efficient way to set dynamic attributes

My integration scenario is quite complex involving many different receivers and an integration process. For some receivers I have to set dynamic attributes.
I know that I can set them by using a UDF, however in my case I mostly use XSLT so this is not applicable.
Is there any other way to do this relatively easy so that I can avoid Java Mappings? Problem ist that I would need to use several Java Mappings to set the attributes where no transformation to the payload itself is taking place which seems to be too much for me. Especially when I consider that these Java Mappings are hard to maintain as they have to be imported again and again if any changes occur.
So my question is:
1. Do I really have to go for several Java Mappings just to set some dynamic attributes ?
2. If so, should I use different Java Packages or is it advisable to leave all Java Mappings in one package?

Hi Florian,
yes, you can!
set dyn atts in XSLT:
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:map="java:java.util.Map" xmlns:dyn="java:com.sap.aii.mapping.api.DynamicConfiguration" xmlns:key="java:com.sap.aii.mapping.api.DynamicConfigurationKey">
<xsl:if test="REFERENCEQUALIFIER='MSU'">
     <xsl:variable name="dynamic-conf" select="map:get($inputparam, 'DynamicConfiguration')"></xsl:variable>
     
          <xsl:variable name="dynamic-key" select="key:create('http://sap.com/xi/XI/System/Mail', 'MAILADRESS_SU')"></xsl:variable>
          <xsl:variable name="dummy" select="dyn:put($dynamic-conf, $dynamic-key, $MAILADRESS)"></xsl:variable>
          <xsl:comment>Mailadresse SU ermittelt: <xsl:value-of select="$MAILADRESS"></xsl:value-of>
          </xsl:comment>
Hoffe es hilft.
Grüße
Mario
Edited by: Mario Müller on Oct 15, 2009 1:47 PM

Load hierarchical attribute dimensions with Integration Services?

Hi everybody,
I need to load product dimension which is organized in a relational table like this:
Product (parent_code, member_code, member_alias, brand, consolidation, formula)
Every product has a brand and I need to load brand as attribute dimension. The thing is Brand is not flat but it has it's own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
Brand (brand_parent_code, brand_child_code, brand_child_alias).
I have used in the past Integration Services but with flat attribute dimensions.
Can I load hierarchical attribute dimensions with Integration Services? If yes, how do I do it, how do I specify the hierarchy?
Thank you,
Daniela

Graham,
This is definitely a supported feature in EIS/9.3.1/ASO. I have many models with this type of structure. How you set it up can vary. Usually my Attribute Hierarchies are not that deep, only two to three levels, maybe four in a rare case, so I don't usually use a parent child table to set up the hierarchy (I'm not saying that it won't work, it might, I haven't tried, but same steps should apply). In a typical model I will have my stock table which has a buyer field. Then in another table I will have my attribute structure which will have columns for buyer, teams, and categories.
In EIS OLAP model, you add your attribute hierarchy table and use a join to link it to the main stock table, joining on the buyer field (you are now going from a "star" schema to a "snowflake". Go into the properties and make sure you define all the columns as "Attributes".
Then in Metadata model, drag your categories attribute onto the outline, then drag the teams and set it as a child of categories and finally drag buyer and set as child of teams. You only set the attribute association for the buyer back to the base dimension.
When you run your dim build it will set up your attribute dimension correctly.
Some things to keep in mind, make sure you have a process that ensures for every stock code you have in the main table, you have a matching one in your attribute dim table.
Sometimes, depending on how much manipulation I need to do, instead of joining the tables in EIS I will go back to relational source and create a view that joins the two tables together, then in my OLAP model, I have one table that has three attribute columns, one column for the buyer and then the other two for team and category, from that point setting up in metadata model is the same.
Good luck, let me know if you run into trouble.

Attribute Dimensions with Integration Services

Good evening, I'm creating an ASO Essbase model through Integration Services v9.3.1 and I am having difficulties with creating an Attribute dimension that contains a hierarchy.
We have a list of stock codes which are grouped by vendor in a dimension, each stock code has an attribute assigned to it for the buyer responsible.
The business requirement is to start from the top level of the attribute dimension, drill in to categories, then to drill in to teams, and finally to the buyer... so we effectively require 3 levels within the attribute dimension.
I have successfully created both the vendor (physical) and buyer (attribute) dimensions through EIS without problems, but when I load to Essbase all of the buyers are added at the top level of the dimension and I can't seem to specify that there should be a parent/child hierarchy to build the attribute dimension from.
Is this possible, and if so any advice you can give as to how I achieve this would be greatly appreciated.
Thanks in advance,
Graham

Graham,
This is definitely a supported feature in EIS/9.3.1/ASO. I have many models with this type of structure. How you set it up can vary. Usually my Attribute Hierarchies are not that deep, only two to three levels, maybe four in a rare case, so I don't usually use a parent child table to set up the hierarchy (I'm not saying that it won't work, it might, I haven't tried, but same steps should apply). In a typical model I will have my stock table which has a buyer field. Then in another table I will have my attribute structure which will have columns for buyer, teams, and categories.
In EIS OLAP model, you add your attribute hierarchy table and use a join to link it to the main stock table, joining on the buyer field (you are now going from a "star" schema to a "snowflake". Go into the properties and make sure you define all the columns as "Attributes".
Then in Metadata model, drag your categories attribute onto the outline, then drag the teams and set it as a child of categories and finally drag buyer and set as child of teams. You only set the attribute association for the buyer back to the base dimension.
When you run your dim build it will set up your attribute dimension correctly.
Some things to keep in mind, make sure you have a process that ensures for every stock code you have in the main table, you have a matching one in your attribute dim table.
Sometimes, depending on how much manipulation I need to do, instead of joining the tables in EIS I will go back to relational source and create a view that joins the two tables together, then in my OLAP model, I have one table that has three attribute columns, one column for the buyer and then the other two for team and category, from that point setting up in metadata model is the same.
Good luck, let me know if you run into trouble.

Attributes Dimension

I am having trouble understanding Attributes dimension. Can someone give a clear example and explain this concept to me? Also tell me how to view the Attributes in the Excel add-in.You can respond here or email me directly at [email protected] Lal

The best way to explain attributes are to go by example. Say you have an essbase database that tracks sales of products over time. So you have a Time dimension, a Measures dimension and a Product dimension.A requirement comes along where the business needs to analyze product profitability by package size - the size of the container each product is shipped in. In older versions of Essbase, there were 2 ways to do this:1) New dimension for package type2) Shared rollups in the product dimensionThese approaches work, but they add size and complexity to the database, which increases calc time. Also, the shared rollup idea starts to get cumbersome when you introduce more things - say product color. Now you have products shipped in different packages and in different colors. You can still create shared rollups for the colors, but now the business wants to compare sales of a package/color combination with a different package/color combination. You need even more shared rollups for the comparisons.Adding a new dimension creates all of the possible combinations of product, package type and color, but if you assume that these new properties are product specific, it adds sparsity to the database.In Essbase 6, you can create an attribute dimension - it looks sort of like a real dimension, but it works by piggybacking an existing dimension. You attach package type and color tags to each product, and you can then use the attribute dimensions to slice and dice the data as you would with real dimensions.By default, Essbase will sum all of the like attributes together to give you a total - sales for all red products for example. However, you can choose from Sum, Count, Min, Max and Average, all applied dynamically.Attribute dimensions do not show up in a default Excel retrieval. You can add them to the sheet by typing them into a cell manually or using Member Select. You can then use them as you would normal dimensions.Hope that helps a bit.Regards,Jade----------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Attribute Dimensions and Excel Retrieves

Dear All,<BR><BR>I have a cube that has a sparse dimension with attributes attached (all at the same level). When I retrieve using different attributes in the retrieve the results are not consistent i.e. some of the sparse members with the same attribute are left out of the result. It appears to happen when branches of the dimension in the same area are separated by a branch with an alternate attribute value (from the same attribute dimension). I have cured this by moving the affected branches next to each other, is this something that I need to watch out for on the design side i.e. to do with the way Essbase handles attribute dimensions? Any guidance would be appreciated.

Graham,
This is definitely a supported feature in EIS/9.3.1/ASO. I have many models with this type of structure. How you set it up can vary. Usually my Attribute Hierarchies are not that deep, only two to three levels, maybe four in a rare case, so I don't usually use a parent child table to set up the hierarchy (I'm not saying that it won't work, it might, I haven't tried, but same steps should apply). In a typical model I will have my stock table which has a buyer field. Then in another table I will have my attribute structure which will have columns for buyer, teams, and categories.
In EIS OLAP model, you add your attribute hierarchy table and use a join to link it to the main stock table, joining on the buyer field (you are now going from a "star" schema to a "snowflake". Go into the properties and make sure you define all the columns as "Attributes".
Then in Metadata model, drag your categories attribute onto the outline, then drag the teams and set it as a child of categories and finally drag buyer and set as child of teams. You only set the attribute association for the buyer back to the base dimension.
When you run your dim build it will set up your attribute dimension correctly.
Some things to keep in mind, make sure you have a process that ensures for every stock code you have in the main table, you have a matching one in your attribute dim table.
Sometimes, depending on how much manipulation I need to do, instead of joining the tables in EIS I will go back to relational source and create a view that joins the two tables together, then in my OLAP model, I have one table that has three attribute columns, one column for the buyer and then the other two for team and category, from that point setting up in metadata model is the same.
Good luck, let me know if you run into trouble.

Associating attribute dimensions with the standard dimension in EIS

Hi... we need to bring 2 attribute dimensions in to the Metaoutline of EIS.These 2 attribute dimensions must be associated with lev 0 member of the standard dimension.how to achieve in EIS?
The current status: we did the olap model by mapping all the dimensional tables with the fact table and we are struck up how to bring the 2 attribute dimensions in to the model screen and association with standard dimesnion.
The table structure for the standard dimension is
column1/Gen-1     column2/Gen-2-Alis     consolidation     col3(Attr)     colu 4(Attri)
Reason-1     Reason-1-extension
Reason-2     Reason-2-extension
Reason-3     Reason-3-extension
col3 and col4 are attributes to be associated with column2.
Pls guide us the approach to be done in EIS..

Graham,
This is definitely a supported feature in EIS/9.3.1/ASO. I have many models with this type of structure. How you set it up can vary. Usually my Attribute Hierarchies are not that deep, only two to three levels, maybe four in a rare case, so I don't usually use a parent child table to set up the hierarchy (I'm not saying that it won't work, it might, I haven't tried, but same steps should apply). In a typical model I will have my stock table which has a buyer field. Then in another table I will have my attribute structure which will have columns for buyer, teams, and categories.
In EIS OLAP model, you add your attribute hierarchy table and use a join to link it to the main stock table, joining on the buyer field (you are now going from a "star" schema to a "snowflake". Go into the properties and make sure you define all the columns as "Attributes".
Then in Metadata model, drag your categories attribute onto the outline, then drag the teams and set it as a child of categories and finally drag buyer and set as child of teams. You only set the attribute association for the buyer back to the base dimension.
When you run your dim build it will set up your attribute dimension correctly.
Some things to keep in mind, make sure you have a process that ensures for every stock code you have in the main table, you have a matching one in your attribute dim table.
Sometimes, depending on how much manipulation I need to do, instead of joining the tables in EIS I will go back to relational source and create a view that joins the two tables together, then in my OLAP model, I have one table that has three attribute columns, one column for the buyer and then the other two for team and category, from that point setting up in metadata model is the same.
Good luck, let me know if you run into trouble.

How to Build Attribute Dimension Dynamically & Load with LCM?

Hi, I'm trying to modify the existing outline at cilent's site. For some reason, when I pulled the outline with extractor, it didnt come out in the format that is compatible with Outline Load Utility. I was told to use LCM so I may still load with minimal to no modification to the existing structure of outline.
So can I build dimensions dynamically in EXCEL then load with LCM and push to Planning?

The log came back with many unrecognized headers in the outline. I spoke to Oracle Support many times, and they said that the format of our outline is improper for Outline Load Utility to read.
Since the outline has already been incorporated, we are not allowed to many any significant changes. That is why we were advised to use LCM.
I tried to use a sample of one of the existing attribute dimensions in XML as the base and build the new attribute but it failed. I would appreciate if you can provide steps by steps resources to show how to add new attributes to the existing outline.

Dynamically setting the vo attribute Update property

Hi All,
Can we set the vo attribute update property dynamically.if so please let me know how can we achieve this.
I have a read only view..But in my process request i need to set the value for that attribute based on some condition.
How can i achieve this.I cant set at bean level.only row level i need to set.
Its a dynamically created seeded vo.
Please help.
Thanks
Bharat

Hi,
Capture the VO row and then set the value on the view attribute.
OAViewObject vo = (OAViewObject)am.findViewObject("viewinstance");
If(vo!=null)
Row row = (Row)vo.first();
row.setAttribute("Attribute Name", "Value");
Thanks,
Gaurav

Calculation issue on attribute dimension

The issue that I'm facing with is as below. I have two pass calc on some of the measures in the outline. Since I'm not doing any calculation on the attribute dimension, when I drill down using this dimension it pops up an error message
"Two-pass calc skipped on member [X] in attribute calc"
Please advise on how to resolve this.
Thr formula has @CURRMBR. The DBAG says that If a member formula contains a run-time dependent function associated with an attribute member name, and the member with the formula is tagged as two-pass, calculation skips the member and issues a warning message.
It also says that Two-pass calculation member property is unavailable for attribute dimensions.
So does it mean that every two pass calc member is skipped?
I'm a bit confused.. how does it work?
Is there a resolution for my issue? Please confirm if there is a way to get this two pass calc done for the formula with @CURRMBR.
Thanks.
null
.

Hello,
I will give it a try:
<< I assume you have the two-pass calc member on the accounts dimension and the associated dimension of the attribute dimension is not the accounts dimension either. >>
Attribute dimensios are calculated dynamically. They provide a different view on the members of the associated dimension which they belong to. There are 5 different calculation functions in the rollup of the members on the base dimension (sum, min, max, count, average).
So this is within the associated dimension (sparse) which is linked to the attribute dimension (virtual).
The accounts dimension is always involved in displaying figures. The attribute calculation e.g. sum is done last. So the dynamic calculations have to be done first. This message is likely a warning message that the value displayed is not the result of the two-pass calculation, but from the attribute calculation.
You might review the storage setting of the member. Often the @currmbr is also not necessary in the formula when considering the calculation order of the members.
Hope this helps a bit.
Regards,
Philip Hulsebosch
www.trexco.nl

Can we set the dynamic data source when using getReportParameters() ?

Hello!
I have a report where one of its parameters refers to a list of values (LOVs). This list of values is an SQL Query type. When the data source used in the report is defined in the BI Publisher server, I'm able to get the report parameters using the getReportParameters() function in my application. However, if the data source is not defined the function throws an exception, which is understandable.
I decided to dynamically set the data source so that even if the data source used by the report is not defined in the BI Publisher server, it still will be able to get the LOVs for the parameter. I tried setting the JDBCDataSource of the dynamicDataSource for the ReportRequest object that I passed to the getReportParameters() function. Please see the sample code below:
reportRequest.dynamicDataSource = new BIP10.BIPDataSource();
reportRequest.dynamicDataSource.JDBCDataSource = new BIP10.JDBCDataSource();
setReportDataSource(reportRequest.dynamicDataSource.JDBCDataSource, connectstr, jdbc, dc); //function to set the values for JDBCDataSource object
reportParams = webrs.getReportParameters(reportRequest, uid, pwd); //call the getReportParameters
I was expecting this to work as this is what I did to dynamically set the data source before calling the runReport function. So, my question is -- can we set the dynamic data source when using getReportParameters() ? I tried this both in versions 10g and 11g. It does not seem to work on both versions.
Regards,
Stephanie

report_id column of apex_application_page_ir_rpt can help us uniquely identify each saved report.
We can assign this report_id value to a page item and this page item can be put in the Report ID Item text box of the Advanced section of the Report Attributes page of the IR.
This should load the saved report identified by report_id and you can get rid of javascript
Regards,
Vishal
http://obiee-oracledb.blogspot.com
http://www.packtpub.com/oracle-apex-4-2-reporting/book
Kindly mark the reply as helpful/correct if it solves your problem

Dynamic Attribute in AS2 Receiver

Hello,
in the Seeburger AS2 Receiver channel I have found "AS Message ID" in the last of possible Dynamic Attributes. How do I set this one, so what is the name of the dynamic configuration key. Any idea on this?

Let me expalin you the complete thing.
In mapping i m using this UDF for dynamic subject.
DateFormat dfCurrentDate = new SimpleDateFormat("yyyy-MM-dd");
DateFormat dfCurrentTime = new SimpleDateFormat("HH:mm:ss.SS");
Date dCurrentDate = new Date();
String strCurrentDate = dfCurrentDate.format(dCurrentDate) + "T" + dfCurrentTime.format(dCurrentDate) + "Z";
String strSubject="Literal"+ "_" + strCurrentDate;
// Dynamic Subject
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey keySubject = DynamicConfigurationKey.create( "http://seeburger.com/xi/common/dtSubject", "DYNSUBJECT");
conf.put(keySubject,strSubject);
return "";
In receiver service I have used "localejbs/Seeburger/AttribMapper" module.
Parameter name http://seeburger.com/xi/common/dtSubject
Parameter value @http://seeburger.com/xi/common/dtSubject/DYNSUBJECT
In moni I can see the dynamic configuration tab(neither Tab nor value)
But in RWB comm. channel monitoring I can see in Audit log but not in SOAP document.
Hope i have cleared you..
Thanks
Jaideep

Need Dynamic attributes for XI adapter to use in Dynamic Configuration ..!!

Hi Friends,
We are planning send message to different receivers through XI adapter by using Dynamic Configuration.
Can anyone please tell me what are the dynamic attributes used for XI adapter.
In my scenario, I want to pass the Service Number and Path prefix of XI adpater dynamically by using sender ID from Idoc payload.
I know how to use the dynamic configuration UDF in message mapping. But I don't know the dynamic attributes which we can pass to Service Number and Path prefix of XI adpater.
Kindly suggest ..
Thanks
Deepthi.

Hi Sourabh,
>> You need to set these attributes explicitly in the adapter configuration..
Can you please elaborate on this like how to implement this? Do we need to use any module configuration in the adapter?
We will use XI adapter only while sending the data directly from IE without using any feautures of AE (like adapters, modules etc). It is like directly sending data from ABAP stack without using J2EE stack. That is the reason we can't use any Modules in XI adpater and it is in disabled by default.
When I checked in SXMB_MONI.. as you said details are found in
- <SAP:Attribute>
<SAP:Name>host</SAP:Name>
<SAP:Value>10.190.25.16</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>httpDestination</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>path</SAP:Name>
<SAP:Value>/rcvA/receiver</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value>8210</SAP:Value>
</SAP:Attribute>
XI adapter uses mainly three parameters Host, Port and Path.
I want to pass any two of these values dynamically to achieve my solution. Can you please suggest your solution how we can implement it.
-Deepthi.

Dynamic Attributes with UDF - NullPointerException

Hello,
I want to set the file name of an file receiver by means of setting dynamic attributes in an UDF.
I use the following code and map the output to the root node of the target message (one input variable is var1)
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String myFileName = var1;
conf.put(key, myFileName);
return "";
When I want to test the mapping using the test tab I get a null pointer exception:
Exception:[java.lang.NullPointerException] in class com.sap.xi.tf
Could the reason be, that setting dynamic attributes does not work when testing a mapping as the mapping has to be called by the IE runtime or is there any other reason?

Hi Florain,
I can understand, but that is how it is designed because the filename paramter can be picked up only during the runtime. But if you use other parameters like interface, sender name etc you can test it in mapping. Please go to test tab and click on parameters tab. There you see few parameters for runtime also. You can put some value there and then you can test the mapping and you will not receive that error. You dont have filename there, so thats the reason why you are getting error. Hope in next release SAP would come up with this option.
Regards,
---Satish

Extended receiver determination and Dynamic attributes

Hello,
is it possible to access dynamic attributes within an extended receiver determination? Can I modify / set dynamic attributes of an XI message within an UDF in the extended receiver determination mapping?
In detail: In my scenario I want to use an extended rec. determination, make a lookup in a DB inside the determination in order to define the receiver, and based on the lookup result I want to add some information as dynamic attributes to the XI message, which then can be accessed in the interface determination as conditions.
Thanks,
Chris

Hi,
In my scenario I want to use an extended rec. determination, make a lookup in a DB inside the determination in order to define the receiver, and based on the lookup result I want to add some information as dynamic attributes to the XI message, which then can be accessed in the interface determination as conditions - See you can do a DB lookup in a msg mapping........but by the time you have reached msg mapping your receiver determination will be done......so your receiver is already decided............Extended recever determination is for dynamically choosing a recever based on source msg's data.........
Regards,
Rajeev Gupta

Setting up Dynamic Attribute dimension.

Similar Messages

Maybe you are looking for