Restricting dimension values = PERMIT_READ

We have an EPM table which stores user_id and dimension members e.g. Business units user has access to. (e.g. 5 out of master list of 100 members.). When user queries using Excel add-in we would like him to be able to see results only for dimension members based on this table.
Using PERMIT_READ how do we restrict BU dimension to only this list of values for that user session. Any examples?
e.g. Select bu from my_epm_tab where user_id='aa111';
bu101
bu102
bu103
Now we want to restrict the cube bu members for which user can see results via Bi Add-in only to this set.What steps do I follow to initialize BU dimension to these values for this session? Any specific format to to initialize these database values into dimensions?
Thanks,
Sudip

1. This is expected behaviour if you think about it. The user you logon to may not have the very top level of the POS tree (worldwide). SO you get blank and "expand all" gives you what you are supposed to see. For users who have access to the very top lvel of the POS hierarchy will see what they should see.
2. If PERMIT_READ is implemented to filter dim values based on user_id then shared work books should work fine. make sure to save your selection as steps and not values.

Similar Messages

How to limit dimensions values of querybuilder

Hi,
I want to learn how to limit dimension value in query builder. i want, the user who run the querybuilder can not see a dimension value which i do not want to display.
For example,
The time dimension has "2000" and "2001" values as default which is defined in database. Normally when i run the querybuilder for create new presentation or calculation, In the dimensions panel of the querybuilder display all values of each of dimension. The user can select values which she/he want from that list.
But i want to limit values which the user can see in the dimensions panel of the querybuilder. for this time dimension example, i want to hide "2001" value from the user. How can i do it. if there is any sample code, please share.
Thank you very much for your helps.
ilknur

Thanks Thomas, excellent suggestions as always.
If anybody wants more information regarding Thomas' suggestions please refer to
Oracle9i OLAP Developer's Guide to the OLAP DML for the AW Permit command.
In sumamry: To create permission programs, you define two programs with the names permit_read and permit_write. In these programs, you can specify PERMIT commands that grant or restrict access to individual workspace objects. In addition, you write these programs as user-defined functions that return a Boolean value, and the return value indicates to Oracle OLAP whether or not the user has the right to attach the workspace.
For relational security there is an excellent tutorial on the database pages of OTN, follow this link:
http://otn.oracle.com/obe/start/index.html
then follow the links for Oracle9i Database Release 9.2.0.2 - Security - Creating Label-based Access Control. This module describes how to use Oracle Label Security to setup security based on label policies
These security layers should be transparent to the OLAP metadata layer, therefore, once you have implemented your chosen security method your BI Beans application will only need to connect with the appropriate user to inherit the security layer. For more information see the Security section of the BI Beans Help:
http://otn.oracle.com/bibeans/903/help/
BI Beans product Management Team
Oracle Corporation

Limiting Dimension Values to Dimension Values used on Specfic Day

If I have a dimension with thousands of values. And within my cube, on a given day only a few of those dimension values are actually used. How can I limit the scope of my dimension values to be only the values that exist on that given day?

You can check OLAP DML Programs chapter (chapter 4 in 11g doc set) in Oracle OLAP DML Reference document. It's part of the standard olap documentation.
Also regd the parameterization question:
The code as pasted below is already parameterized. By parameterization, do you mean something other than passing value from front-end to the back-end (database)?
Typically the front end report/query will refer to a series of time dimension values -- say, 16-Jul-2012 to 22-Jul-2012 for time. The report would reference a measure with a formula referring to an olap dml program. This program is called repeatedly for each cell and the appropriate dimension member values are passed as input to the program.
argument _tm time <-- implies that the program accepts time dimension value (corresponding to a single cell) as input and works off the same in its calculation.
limit time to _tm <-- usually this is done within a tempstat context to make such changes temporary for calculation w/o affecting external time dimension status. This allows the program to set the context of calculation to current cell (say 18-Jul-2012)
"hence what follows for the rest of the program acts on the restricted status in order to calculate the current cell's value corresponding to time dimension value = 18-Jul-2012.
That's also why the same program can return a different value for each cell (different return value for 18-Jul-2012 compared to return value for 21-Jul-2012) although it's being looped over dimension status implicitly.
HTH
Shankar

Best Practices - Dynamic Ranking, Dimension Values to Return, etc.

The pinned post says non-technical questions belong on the Business Forum. I can't find an Endeca-specific business forum. If there is one, please tell me where to find it.
My question is about dynamic ranking and the initial display of only the top N dimension values with a "More..." option to see the rest of them.
What's the current wisdom on this from a usability point of view? Use it, don't use it? If using it, show how many values initially?
Or, if not using it, you instead set up a hierarchy of dimensions so that the user never has to look at 50 choices for something?
This is not a technical question. What is the current wisdom? What are the best practices?
Thanks!

Dynamic ranking is a good choice only if all choices cannot be further grouped. In my practice most of the content can be normalized and restricted to a very limited set of options. Dynamic ranking with "more" is an easy way out and seems like a lazy take on content management.

How to restrict the values in seach helps

Dear All,
I am new to the BSP concept.I have a requirement
where in the BSP i need to restrict the values of the search help.i.e. 2 values are coming in the help i need to display only 1 value.
can anybody please explain how to do it.
Cheers,
Deepthee Kasal
Edited by: Craig Cmehil on Sep 2, 2008 8:21 AM

Hi,
I assume that you read values for the search help with function 'F4IF_FIELD_VALUE_REQUEST' and in a later step you display values with <htmlb:tableview>. If that is true and the function is delivering too many records as you mention, you could then restrict the output table of values like this:
TABLES mara.
DATA: mytable TYPE TABLE OF ddshretval WITH HEADER LINE.
DATA l_repid TYPE syrepid.
PARAMETERS p_mtart LIKE mara-mtart.
AT SELECTION-SCREEN ON VALUE-REQUEST
FOR p_mtart.
l_repid = sy-repid.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
EXPORTING
tabname = 'MARA'
fieldname = 'MTART'
dynpprog = l_repid
callback_program = l_repid
callback_form = 'F4CALLBACK'
TABLES
return_tab = mytable
EXCEPTIONS
field_not_found = 1
no_help_for_field = 2
inconsistent_help = 3
no_values_found = 4
OTHERS = 5.
START-OF-SELECTION.
blah, blah, blah
* Form F4_form
* Exclude all material types that start with F & H
FORM f4callback
TABLES record_tab STRUCTURE seahlpres
CHANGING shlp TYPE shlp_descr
callcontrol LIKE ddshf4ctrl.
DATA: aux_struc TYPE ddshselopt.
MOVE: 'H_T134' to aux_struc-shlpname,
'MTART' TO aux_struc-shlpfield,
'E' TO aux_struc-sign,
'CP' TO aux_struc-option,
'F*' TO aux_struc-low.
append aux_struc to SHLP-SELOPT.
MOVE: 'H_T134' to aux_struc-shlpname,
'MTART' TO aux_struc-shlpfield,
'E' TO aux_struc-sign,
'CP' TO aux_struc-option,
'H*' TO aux_struc-low.
append aux_struc to SHLP-SELOPT.
ENDFORM. "F4_form
Mark points if helpful

How to restrict Option values for a particular metadata in profile checkin

How to restrict Option values (drop down) for a particular metadata in profile checkin-
Metadata field Color is having options dropdown values (stored in table/views)-
Display name - Blue, Value=1
Display name - Red, Value=2
Display name - Yellow, Value=3
Display name - Green, Value=4
Display name - Black, Value=5
For a particular profile checkin form, for the metadata field Color I want the dropdown value consist of only top three options
Display name - Blue, Value=1
Display name - Red, Value=2
Display name - Yellow, Value=3
But this should be done on profile level only, should not impact the standrad checkin form and other profile checkin forms.
Please help me if any one having any suggestion to implement the above secnario
Thanks,
Sumit

Hi,
Into the rule containing the Color metadata, you can restrict the values of the list.
In "Has restricted list and pane", list the values 1, 2 and 3 (new line for each value) :
1
2
3
Romain.

Few dimension values used in FACT tables.

Hello all,
We are trying to know if somebody faced this issue earlier. We have dimension tables containing 5 million records, but the fact table uses hardly 30k of these dimension values. The fact table contains 350 million records, so is there any way to improve the performance of the query in such a scenario, where hardly 20% of dimension values are actually used by the FACT tables.
Thanks and Regards,
Upendra

nilanjan chatterjee wrote:
Hi,
>
> The data for the parent members should be available in the SQL tables.
> For example, 2011.TOTAL is parent member. You should not have any data for this member in your database. If it is there, it might have come somehow (may be an import). But this is not right. You might want to remove these records. But be sure that you dont delete the records for the base level members.
>
> Hope this helps.
I guess you meant should not, right ?

Dimension values display order and record details

Hi All,
I have explicitly ordered my dimension values to be in a logical order instead of alphabetical. Ex: Small, Medium, Large. This works great in the navigation tree but when I view a specific record and it has those 3 dimvals they are listed in alphabetical order.
Is there a when doing a record query to ask Endeca to respect the same display order as in the nav query?
Thanks,
Luc

We are used to add two dummy records in each dimension.
We add the following data:
We use '-1' (surr-key) for Invalids and '-2' for Unknown.
Easy way to populate these dimensions is to add a script together with all objects when you release new functionality. Beware you use the same descriptions.
Even better is to think of a more general solution (more easy to maintain) and store these values in a support table. In such a table you will be able to add more columns to get more details per row. Use this reference table when you load youre dimension. Also you will find the opportunity to add more error handling cases. Especially when you add the dimension in this support table.
Regards
Moscowic

How do i show descriptions instead of dimension values at presentations ?

We are facing a problem that could be a BIBeans problem or could be an OLAP problem, please inform if to change forum:
We are using jdev 903/BIB903 accessing an AW created at Oracle OLAP 9205 with AWM.
All our dimensions were created at OWB 10g and deployed to RDBMS following the general rules below:
DIM X
ID_X - sequence primary key
CD_X - original key from source systems
DS_X, NM_X, and so on - description fields and hierarchy fields related to this record.
i.e.:
SQL> desc dim_rota
Name Null? Type
ID_ROTA NOT NULL NUMBER(6)
CD_EMPRESA NOT NULL NUMBER(2)
CD_FILIAL NOT NULL NUMBER(2)
CD_ROTA NOT NULL VARCHAR2(3)
NM_FILIAL NOT NULL VARCHAR2(40)
NM_ROTA NOT NULL VARCHAR2(30)
CD_SETOR NOT NULL VARCHAR2(1)
ID_SETOR NOT NULL NUMBER(6)
NM_SETOR NOT NULL VARCHAR2(30)
this dimension has 1 hierarchy with 2 levels called SETOR and ROTA.
when we generated the AW using AWM, each field (except ID) is created as a variable dimensioned by DIM_ROTA, as shown below:
->listby dim_rota
35 objects dimensioned by or related to DIM_ROTA in analytic workspace AW1
DIM_ROTA_CD_EMPRESA
DIM_ROTA_CD_FILIAL
DIM_ROTA_CD_ROTA
DIM_ROTA_CD_SETOR
DIM_ROTA_CREATEDBY
DIM_ROTA_FAMILYREL
DIM_ROTA_GID
DIM_ROTA_INHIER
DIM_ROTA_LEVELCOLMAP
DIM_ROTA_LEVELREL
DIM_ROTA_NM_FILIAL
DIM_ROTA_NM_ROTA
DIM_ROTA_NM_SETOR
DIM_ROTA_ORDER
DIM_ROTA_PARENTREL
ID field was concatenated with level name to generate the dimension value - so, for the following relational record:
SQL> select id_rota, cd_rota, nm_rota from dim_rota where ID_ROTA = 233;
ID_ROTA CD_ROTA NM_ROTA
233 A99 A99-Consig. Sup. Setor A
we have at multidimensional side:
->LIMIT DIM_ROTA TO 'ROTA.233'
->rpr dim_rota
DIM_ROTA
ROTA.233
->dsc dim_rota_nm_rota
DEFINE DIM_ROTA_NM_ROTA VARIABLE TEXT <DIM_ROTA DIM_ROTA_HIERLIST ALL_LANGUAGES>
LD IMPLEMENTATION NM_ROTA Attribute for DIM_ROTA Dimension
->rpr down dim_rota w 30 dim_rota_nm_rota
ALL_LANGUAGES: AMERICAN_AMERICA
-------DIM_ROTA_NM_ROTA-------
------DIM_ROTA_HIERLIST-------
DIM_ROTA ROTA
ROTA.233 A99-Consig. Sup. Setor A
here comes our question: how do we show at BIBeans designer/presentations the related descriptive fields and NOT the dimension values themselves?
thanks in advance,
Flavio

There a re two additional attributes that need to be mapped within OWB for each dimension:
Long Description - this is used by the presentation beans and query and calc builder to replace the dimension values with more meaningful/end-user friendly descriptions
Short Descriptions - this can be used where the long description is too long for display purposes. In BI Beans 10g Release 2 (due out soon) you will be able to select between long/short descriptions when using many of the new tags.
These new attributes will be automatically picked up by the OLAP Bridge in OWB and automatically added to the OLAP catalog.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation

Restrict variable values in the pop-up selection screen

Hi,
I have a variable based on a caracteristic that has 0COMP_CODE as attribute in a Web Report (BW 3.1B).
This variable has to be accessible so that users can select a value.
I need to restrict the values that users can see on the selection screen according to their 0COMP_CODE value, even in the pop-up.
I have tryed authorization variable and user exit, but none worked.
The best I could do was a "several single values" variable that was preselected with the caracteristics of their 0COMP_CODE, but it didn't worked in the pop-up.
Does anybody knows how to handle this?

As far as I could find out, it should be made through customer exit.
The point is : I have to use a customer exit variable that has been check as "ready for input".
I can't find a way to restrict the values displayed in the variable selection screen (in the help pop-up window for this variable).
The exit can pre-fill the selection fields with values, but whenever the user opens the window, he sees all the values.
I have tryed all the values for I_STEP (0,1,2 and 3) but none did it.
Does anybody knows how to limit those values?

How to restrict the values during extraction?

Hi everyone,
I want to restrict the values while extracting data from R/3 Datasource... For example:
I have MATNR, which have around 10 materials out of which i want to extract the data for only 5 materials. My Selection screen is disabled, i mean we cant do anything in selection screen... Can anyone plz tell me how to go abt this issue?
Advance thanks,
chintu..

Hi KJ,
Am saying that its not available in Selection screen in R/3 side.. am not talking abt the BW side.. Then also i want to extract the data.. How to do this? this is an interview question asked by HP today morning..
Regards,
Chintu.

Is it possible to sort dimension values in order different from alphabetic?

Is it possible to sort dimension values in order different from alphabetic. То use this sorting in BI Beans. In 10g r2 with awm 10.2.0.2. I try to add attribute like it was show in this forum, but nothing changes.

Could be usefull if you use java AW api... here's the java code I'm using to create the sort_order attribute
Dimension myDim = yourAW.findDimension("DIMNAME");
Attribute myAttr = myDim.createAttribute();
myAttr.setName("freename");
myAttr.setClassification("DEFAULT_ORDER");
myAttr.setIsDefaultOrder(true); // TO NOT FORGET
myAttr.setDataType("INTEGER");
myAttr.Create(AWConnection);
globalAW.Commit(AWConnection);
It creates a variable - integer - that defines the default order of the dim values. I'm viewing it with AWM and BIBeans. The order is respected with Level-based and Value-based hierarchy but my hierarchies are really simple and unique for all the dimensions.
BUT !!!! Be carefull, if you don't have any hierarchy in your dimension, you must have at least one level - the default NONE level. Otherwise, it won't work ???

Execution of a planning function with the used dimension values in a crosstab

Hello,
would like to execute planning functions within Design Studio but I don't really know how I combine this execution with the used dimension values in a crosstab for the .
Here the requirement:
3 Planning functions which should use the same filter (all values of all dimensions in the crosstab) and which should run one after another:
// open data slice
PF_1.execute();
// generate combinitions
PF_2.execute();
// close data slice
PF_3.execute();
Many thanks in advance.
Kind regards,
Tobias

Hi Arun,
in general it is not possible to nest planning functions. The inner function would update the data in the plan buffer without the outer function knowing about it. Also the inner function might be on a different aggregation level which would make things very tricky.
Alternatively you can include ABAP logic into a FOX formula:
http://help.sap.com/saphelp_nw70/helpdata/en/47/94eb78b6394befe10000000a42189d/frameset.htm
Or just create the complete logic in one ABAP planning function type.
Regards,
Marc
SAP NetWeaver RIG

Need to restrict KFF values on Charge Account Screen in Oracle Apps 11i

Hi,
I have a requirement to restrict KFF values based on certain criteria in the charge account screen in Oracle Apps 11i..
Could you pls advise on how this can be achieved.
Thanks,
Shashank
Edited by: Shashank Senan on May 23, 2012 2:53 PM

Can you please mark my answers correct......if they were helpful to you.....
That would be so nice of you....:-)
and regarding your next requirement, You should create a new table which will contain Date, Worker Number and any other details that you want.
In the form, for every date for which you want to enter the data, you will select the max(date) before the current date and maximum worker number for that selected date and then from that number you can select next 15/20 workers or whatever your number is.
e.g. for the first time if you want to enter data for 01-jul-2010 and you have work for 15 workers, you will select max(date) where date<01-jul-2010, but you will not find any bcoz this is your first entry. So wat you will do is will start popupating your grid from number 1-15.
Next day you will select max(date) where date<02-jul-2010, you will find 01-jul-2010. Then you will select max(number) for 01-jul-2010, you will find 15. So populate your grid from number 16-30 (whatever your number is). and so on.
Hope it helps you...
Please mark my answer Helpful or correct and Please create a new thread for new question
Thanks
Nishu

Restrict the values in the Query Designer

Hi Gurus,
I want to Restrict PLANT or SALES ORG values in the Query Designer, in the Query, PLANT has selected in the rows and having variable and SALES ORG is display attribute of the PLANT. In this scenario How can we Restrict the values?
Thanks in Advance,
Ravi.

Hi Ravi,
You cannot restrict values on the display attributes. Better change it to navigational attribute and check the box as navigational in the cube.
Regards
Ram

Restricting dimension values = PERMIT_READ

Similar Messages

Maybe you are looking for