Level attributes

Hi,
i want to create level attributes in AWM. I see the definition of level attributes and dimension attributes in the below link:
http://docs.oracle.com/cd/A97630_01/olap.920/a95295/designd6.htm
how do i create a level attribute in AWM? pls help

Choose the dimension, right click on "Attributes" within the dimension to create a new attribute.
Now choose the level or levels that the attribute is applicable to.
If the attribute applies to all hierarchies and all levels of the dimension, then its a dimension attribute else its a level attribute (1 or more levels).
The same screen creates both types of attributes.
Uncheck the default option on the check box "Apply Attributes to" and expand, choose the hierarchy/level the new attribute applies to.
Read help on "Create Attribute" screen of AWM for more details.
HTH.

Similar Messages

Multi level attribute form LDAP

multi level attribute form LDAP
I am trying to write an custom mapping to use to retrieve a value from a multialued field in LDAP (nsRole). Has anyone done this before?
Rigth now all my mappings are 1:1. However the goal is to get a 1 : M and parse thru it till i get the desied value (1:1)

Darwin Hammons - Assurant
2:44pm, May 17
Great conversation. I have a very similar question about the use of the custom JAVA mappings with the LDAP Login process. I want to include an additional (event) step in the login process. Does anyone have an example or experience with a custom Java Class mapping that can use an LDAP attribute (location) queriing the data to execute an event that populates an RequestCenter OU or Group if the person login location equal say " Argentina" ? Looking for a way to manage / build catalog entitlements during login. Suggestions ?
Great conversation. I have a very similar question about the use of the custom JAVA mappings with the LDAP Login process. I want to include an additional (event) step in the login process. Does anyone have an example or experience with a custom Java Class mapping that can use an LDAP attribute (location) queriing the data to execute an event that populates an RequestCenter OU or Group if the person login location equal say " Argentina" ? Looking for a way to manage / build catalog entitlements during login. Suggestions ?
Anthony Erickson
2:52pm, May 18
Hi Darwin,
We're about to embark on a piece of work with newScale which would be similar to this to support our Multilingual catalogue. I'll provide any updates I'm able.
Thanks,
Ant
Darwin Hammons - Assurant
3:25pm, May 18
Great, Thanks Anthony ! I hope our bringing up this topic will spark a bit of interest. The Custom Java Mapping / Directory integration is documented more with RC 9.1. It will be good to hear more about your project and use of Java mappings with LDAP Directories.

OWB 10.2.0.1: Level attribute prefix

Hi all,
I am currently working on a project to convert an existing OWB 9.2 project to OWB 10.2.
In 9.2 (and 10.2), when you create a dimension, the underlying table has columns with the level of the dimension as a prefix. In 10.2, OWB only does this when a dimension attribute is used in more than one level. To minimize impact, I would like to have the prefix at all times in my new environment as well.
What can I do to achieve that? Is there a way (setting) in OWB 10.2 to always prefix level attributes with the level name? Or should I edit all the level attribute names manually? Or should I edit them in the Table object?
Thanks
Paul

Hi Paul,
I think it is "standard" behavior of dimension wizard and autobinding operation.
I don't know how to change this behavior but you can modify column name (rename column) of table object without any impact (in this case level attribute still binded to this column).
Regards,
Oleg

Read only page level attribute

Are there any plans to add a 'Read only' conditional attribute at the page level. It would save a lot of time if a page level read only attribute was available which was overrriden at the item level.
The page level attribute would allow a page with lots of items to be rendered read only at the click of one option rather than having to go through each item on the page. (It would also be nice to be able to programatically set this via a function call)

i know you can do this at the item level. Lets say you have 50 items on a page and you want to set the same condition for making each item read only. It would be a little tedious to have to go into each item to do this. Whereas a page level attribute would cascade down, being overrriden by the item level setting if a few of the items had different conditions or were not to be made read only.
just think it would be a nice to have feature

Dimension's levels and level attributes

Hi guys,
Let's say I have following situation:
Creating dimension CUSTOMERS with unique key CUS_ID.
Levels: L_CUSTOMER and L_COUNTRY.
One hierarchi: H_CUSTOMER_REGIONAL with levels L_COUNTRY -> L_CUSTOMER.
Now the question: What level attributes should I create?
For level L_CUSTOMER obviously CUS_ID, which is a key level attribute, and CUS_NAME.
For level L_COUNTRY what attributes should I create?
I see two variants:
1. COUN_ID (key level attribute) and COUN_NAME
2. just one COUN_NAME and this will be my key level attribute.
What guidelines should I follow here? I intend to use model in Discoverer later if it influences the design here.
Please advice.
Thanks,
Alex

Alexandre,
It depends whether you plan to use the COUN_ID in a join with a summarized fact table - if yes, I would suggest to have the ID, if not (pure star schema), there might not be a great use for it.
Regards:
Igor
Hi guys,
Let's say I have following situation:
Creating dimension CUSTOMERS with unique key CUS_ID.
Levels: L_CUSTOMER and L_COUNTRY.
One hierarchi: H_CUSTOMER_REGIONAL with levels L_COUNTRY -> L_CUSTOMER.
Now the question: What level attributes should I create?
For level L_CUSTOMER obviously CUS_ID, which is a key level attribute, and CUS_NAME.
For level L_COUNTRY what attributes should I create?
I see two variants:
1. COUN_ID (key level attribute) and COUN_NAME
2. just one COUN_NAME and this will be my key level attribute.
What guidelines should I follow here? I intend to use model in Discoverer later if it influences the design here.
Please advice.
Thanks,
Alex

Level Attributes using DML

Is there a way to list the attributes that are applied to a particular level using DML?

This program will produce a formatted listing of all dimensions, hierarchies, attributes, and levels, and show whether or not the attribute is defined within a given level.
Define a program named SHOW_ATTRIB_LEVELS with this program code:
"Program: Show_Attrib_Levels
"Purpose: Display level/attribute associations
"Author: Mark Thompson - Vlamis Software Solutions - July, 2008
vrb _dim text
vrb _hier text
vrb _lvl text
vrb _attr text
vrb _dimcolwid int
vrb _hiercolwid int
vrb _lvlcolwid int
vrb _attrcolwid int
trap on haderror
pushlevel 'SHOW_ATTRIB_LEVELS'
push all_dimensions all_attributes all_levels all_hierarchies
limit all_dimensions to all
limit all_hierarchies to all
_dimcolwid = largest(numchars(all_dimensions))-10
_hiercolwid = largest(numchars(all_hierarchies))-10-_dimcolwid
_lvlcolwid = largest(numchars(all_levels))-6-_dimcolwid
_attrcolwid = largest(numchars(all_attributes))-10-_dimcolwid
row under '-' < w _dimcolwid 'DIMENSION' -
w _hiercolwid 'HIERARCHY' -
w _attrcolwid 'ATTRIBUTE' -
w _lvlcolwid 'LEVELS' -
w 7 'InHier?'>
sort all_dimensions a convert(all_dimensions,text)
for all_dimensions
do
_dim = extchars(all_dimensions 1 findchars(all_dimensions,'.DIMENSION')-1)
limit all_attributes to dim_attributes
limit all_levels to dim_levels
limit all_levels remove findchars(all_levels,'AW$NONE') ne 0
limit all_hierarchies to dim_hierarchies
limit all_hierarchies remove findchars(all_hierarchies,'AW$NONE') ne 0
for all_hierarchies
do
_hier = extchars(all_hierarchies findchars(all_hierarchies '.')+1)
_hier = extchars(_hier 1 numchars(_hier)-10)
for all_attributes
do
_attr = extchars(all_attributes findchars(all_attributes '.')+1)
_attr = extchars(_attr 1 numchars(_attr)-10)
for all_levels
do
_lvl = extchars(all_levels findchars(all_levels '.')+1)
_lvl = extchars(_lvl 1 numchars(_lvl)-6)
row w _dimcolwid _dim -
w _hiercolwid _hier -
w _attrcolwid _attr -
w _lvlcolwid _lvl -
w 7 r across all_levels: nafill(convert(attr_visible,text) '-')
doend
blank
doend
doend
doend
haderror:
poplevel 'SHOW_ATTRIB_LEVELS'

LEVEL attribute for the NavigationPane in ADF11g

Hi All,
I am working in ADF11g. I have a requirement to develop page hierarchy using NavigationPanes and NavigationCommanditems. I have to show/nottoshow few navigationpanes.
Can anyone give me an example for LEVEL attribute for the NavigationPane and how it can be used.
Thanks in Advance,
Melissa
Edited by: user10942366 on Mar 31, 2009 1:56 PM

Please follow cuecards at:
http://www.oracle.com/technology/products/jdev/11/cuecards/adf_set_43/ccset43_ALL.html

Displaying Entity Level Attributes on Summary screen

Hi
Is there a way to show the value of an entity level attribute on the summary screen?
I need the attribute values for all entity instances to be listed on the summary screen.
For example, I have a household member entity and I need to display on the summary screen the names of all
the household members who are above 18 years of age.Is this possible?
Thanks,
Lokesh

Out-of-the-box in version 10, no, you can't attach entity level attributes to the summary screen.
The new InstanceValueIf function in 10.1 can be used to partially address the issue of wanting to display entity level information on the summary screen. Basically, you can use this function to move a text value from an entity level to the Global level, and that new Global attribute can then be attached to the summary screen.
Rule syntax:
InstanceValueIf(<the relationship>, <the value expression>, <the condition expression>)
Example rule:
the name of the oldest child = InstanceValueIf(the children, the child's name, the child's age = the age of the oldest child)
InstanceValueIf: http://www.oracle.com/technology/products/applications/policy-automation/help/opm10_1/Content/Reference/Rule%20syntax%20reference/Entity_and_relationship_functions.htm
However, this function only works where there is only one entity instance which satisfies the conditional expression. Therefore it wouldn't work for your example as presumably there could be multiple household members who are above 18 years of age.
You could consider attaching a Global level attribute on the summary screen ("there are household members who are above 18 years") which has a decision report listing the people who satisfy the criteria, e.g.
there are household members who are above 18 years if
…..ForAll(the household members, the household member's age is known) and [invisible]
…..Exists(the household members, the household member is above 18 years of age) [silent]
the household member is above 18 years of age if
.....the household member's age > 18
(Note that I've used the silent and invisible parameters in the first rule to trim the decision report.)
Imagine the following 4 household members:
Homer, aged 38
Marge, aged 36
Bart, aged 10
Lisa, aged 8
Assuming you've set up name substitution in the rule project, the decision report will say "Homer is above 18 years of age" and "Marge is above 18 years of age". As this is the decision report, it won't be displayed directly on the summary screen, but will be accessible via the [Why?] link. This might be as close as you'll get using only out-of-the-box functionality and no customisation.

EAS load rule (multi level attributes)

Hi All,
I'm trying to build multi level attributes at the same time associating it to the base dimension same time building the base dimension.
because I'm building the multi level attributes...I specified all levels of attributes then base dimension then associations!!
The question is how to set the dimension build property?
whether I need to set it as building the base dimension or attribute dimension!!
I studied the Dbag page 308...
but getting the verification error!!
suggestions pls!!
Thanks,
Jeeth

Hi Glenn,
I was able to create a multiple level attribute hierarchy, base dimension and its associations in the same load rule.
I created attribute dimension and its descendents in the load rule it self!!
may be I'm not clear before!!
I found a way to create as per Rahul's post!!
I'm facing another issue over here!!
I successfully created multi level numeric attribute but not able to create multilevel text attribute!!
getting the following error!!
*\\ATTRPARENT column 8 must precede a numeric or date/time attribute association column\\Column 8 Validation* Failure
Thanks,
Jeeth
Edited by: Jeeth on May 18, 2010 10:04 AM

Which level attribute ASCP will follow for Purchased Item

Hi All,
We have a Purchased Item for which attribute - "Fixed Lot multiplier" is defined at item level as 32 however at ASL level attribute - Fixed Lot multiplier is null or different,
Could you please help me to know which level Attribute ASCP will follow while creating planned order, Item level or ASL level
Regards

Hi Nilesh,
It should consider first from ASL and then Organization Item attributes.
Thanks,
Abhishek Sharma
Please mark the post correct or helpful, if answered

How to map levels attributes in "Analytic Workspace Manager"?

In the dimension table created by OWB I have a dimension with 2 levels of 1 hierarchy:
in the lowest level I have 2 attribute (ID (Key), Name) and the highest level just 1 attribute (Name). So 3 column to map!
In the target dimension in AWM, It gives me a dimension with 2 members (that i must map), how I have to map the source column?
thanks

Maybe map both the top level "name" and "id" fields in AWM back to the single relational column?
HTH,
Scott

Service level attribute

Hi gurus,
i want to display the attribute in my query. but when right click the char and select the attribute, ( it is in the service level - unit of measure attribute) not giving the values. it is giving the 0.00 values.
but in the master maintenance it is showing the values.
how can i display the attribute of char in the query.
thanks.

Hi Binu,
The multiprovider on which this report is based contains 4 cubes. This query is restricted on 3 out of 4 cubes. These 3 cubes have same structure. One is current year data cube and other 2 are history cubes.
The current output format is
A/P doc No.--A/P Line item--
Service Amount
Result----
300
10000001--001--
100
10000001--002--
100
10000001--003--
100
The expected output format is
A/P doc No.--A/P Line item--
Service Amount
Result----
100
10000001--001--
100
10000001--002--
Blank
10000001--003--
Blank
We are trying to find out if we can achieve this at query level with conditions etc.
Regards,
Jeethendra

Displaying only relevant base level attributes in the decision report

Hi,
I am running OPA 10.2 determinations server on weblogic. The service I am using is Assess. The following is a node within my decision report:
<ns0:attribute-node id="dn:88" entity-id="global" instance-id="global" hypothetical-instance="false" attribute-id="b2@Rules_ExternalCalls_EXCommon_doc" type="boolean" text="The information for making motor voter calls have been collected." inferred="true" start-relevance="" end-relevance="">
<ns0:boolean-val>true</ns0:boolean-val>
<ns0:attribute-node id="dn:89" entity-id="global" instance-id="global" hypothetical-instance="false" attribute-id="q_Register_To_Vote" type="boolean" text="The applicant does not want to register to vote." inferred="false" start-relevance="" end-relevance="">
<ns0:boolean-val>false</ns0:boolean-val>
</ns0:attribute-node>
<ns0:attribute-node id="dn:90" entity-id="global" instance-id="global" hypothetical-instance="false" attribute-id="Political_Party" type="text" text="The applicant's political party is unknown." inferred="false" start-relevance="" end-relevance="">
<ns0:unknown-val/>
</ns0:attribute-node>
<ns0:already-proven-node id="dn:13"/>
</ns0:attribute-node>
As can be seen, although the goal has evaluated to "true" since "q_Register_To_Vote" is false, it is still showing "Political_Party" is unknown. However when I debug in OPM without screens setting "relevant only" to true and provide false to " q_Register_To_Vote", "Political_Party" is hidden from the resulting tree/decision report. How can this behavior be simulated in the determinations server's assess service's decision report?
Thanks
Sam

The reason that political_party shows up in the decision report is because it is actually relevant. For more information on relevance in decision reports see http://docs.oracle.com/html/E24270_01/Content/Decision%20reports/Hide_an_attribute_from_decision_report.htm.
You can suppress attributes in a decision report by using the Silent and/ or Invisible operators. For more information on that see http://docs.oracle.com/html/E24270_01/Content/Reference/Definition_of_relevant_in_decision_reports.htm.

Prod No validation at the field level attribute

Hi,
I have a qualifying table, whose field refers to one of the product number in main table. It means, I can have a product number linked to another product number defined in the main table. Hence, I have defined the text field in the qualifying table to capture this related product number.
Now, how do I validate, if the product number entered is valid within Data Manager. Basically, it needs to validate if the product number specified is present in the main table.
Please let me know, if any suggestions to define such validations on a free-form text field.
Thanks,
Surendra

Hi Surendra,
Make the prdt no as a unique field.If when ur gng to add any new record with the prdt no already in the main table then it will pop -up a message that record already present.
I think this may solve the issue (acc to my understanding)
If problem persists kindly explain the scenario in simple manner.
Hope this amy help u.
Rgds
Ankit

Reporting Level - Can someone please explain this attribute?

All - I am a relative newbie to Siebel on Demand but creating reports with other tools for years. I recently came across some reports that I have inherited that are constantly giving us trouble. They are basic reports that look at the count of calls, meetings, etc. for a given user. What we are finding is that we have used this reporting level attribute to filter but depending on the level of manager logging in it is causing problems. Some people can't see the data and some get a massive amount of duplicated data.
When it is all said and done we are looking for a simple manager-to-rep list of the counts of these activities. After looking at the reporitng level value it would look like an indicator of relative position from the lowest level in the reports-to heirarchy. We will generally filter for a level = 0 (or maybe 1) in most reports but what I want is a way to control that based on the user. My requirement is to have the level they can see and the detail at one level lower but I dont' fully understand how that gets created or how I can use system variables to find the user's level to control it.
Anyone that has any background info on this or how I can control a basic anaylytic report in a more maintainable fashion to show my stuff and subtotals at one level lower that would be greatly appreciated.

Not sure if I can help with the specific report, but I will try to shed some more light on Reporting Level.
In any report where the Owned By User dimension is exposed, you can find the Reporting Level field. Each user is part of a reporting hierarchy, derived from the "Reports To" value in their user profile.
The best way to see this is to create a simple report with the User Email, Reporting Level, and Manager Email. This will show you the manager at each level. You can use this to expose and filter on the full management hierarchy.
Level 0 = the user. All users have a value of themselves as Manager at Level 0.
Level 1 = Reports To - who the user directly reports to.
Level 2+ = Up the chain...
You may want to take a look at some of the pre-built reports to see how this can be used to achieve Team based reports, such as "Team Pipeline Analysis", "Team Sales Effectiveness Analysis", and "Team Activity Analysis". You can open any of the pre-buiilt reports to use as starting points as well.

Level attributes

Similar Messages

Maybe you are looking for