Security at a dimension level in a Planning Application (ver 9.3.1)

Hi,
I'm dealing with the Assign Access process in the Dimensions pane.
Is it possible set access at dimension level?
How can I set the member Account (root of Account Dimension) visible for only a subset of user?
Thanks in advance.
Stefano

Hi Stefano,
I'm currently using Hyperion Planning version 4.0.2. I tried using the ImportSecurity.exe file to update the security for the top member in Entities dimension (ie the dimension name itself) but it kept giving me this error:
Record not processed -Finance,Entities,READ,MEMBER- Invalid Member name.
All lines in Import Security file were successfully parsed.
No records inserted into the database.
1 Lines were not processed by the application due to errors.
My secfile.txt file looks like this:
Finance,Entities,READ,MEMBER
Am I doing anything wrongly?
Thanks for your help!
Michelle

Similar Messages

  • Load dimensions and members in Planning application via outline load

    it is a classic planning application, after I load dimensions and members into classic Planning application, I can't see new members I added in csv file.
    How could I confirm whether it was successfully loaded.
    This is the log. Please refer to it.
    Successfully logged into "予算応用" application, Release 11.121, Adapter Interface Version 5, Workforce supported and enabled, CapEx supported and enabled, CSS Version 3
    "Account" dimension properties and information:
    Account, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Account Type, Time Balance, Skip Value, Exchange Rate Type, Variance Reporting, Source Plan Type, Plan Type (PL), Aggregation (PL), Plan Type (BS), Aggregation (BS), Plan Type (Plan3), Aggregation (Plan3), Plan Type (Wrkforce), Aggregation (Wrkforce), Plan Type (Capex), Aggregation (Capex)
    UDA's bound to "Account" dimension: HSP_NOLINK
    "Period" dimension properties and information:
    Period, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Type, Start Period, End Period, Aggregation (PL), Aggregation (BS), Aggregation (Plan3), Aggregation (Wrkforce), Aggregation (Capex)
    No UDA's defined on "Period"
    "Year" dimension properties and information:
    Year, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation
    No UDA's defined on "Year"
    "Scenario" dimension properties and information:
    Scenario, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Start Year, Start Period, End Year, End Period, Exchange Table, Include BegBal, Process Management Enabled, Aggregation (PL), Aggregation (BS), Aggregation (Plan3), Aggregation (Wrkforce), Aggregation (Capex)
    UDA's bound to "Scenario" dimension: ACTUAL
    "Version" dimension properties and information:
    Version, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Version Type, Process Management Enabled, Aggregation (PL), Aggregation (BS), Aggregation (Plan3), Aggregation (Wrkforce), Aggregation (Capex)
    No UDA's defined on "Version"
    "Currency" dimension properties and information:
    Currency, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Symbol, Scale, Triangulation Currency, Reporting Currency, Thousands Separator, Decimal Separator, Negative Style, Negative Color
    No UDA's defined on "Currency"
    "Entity" dimension properties and information:
    Entity, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Base Currency, Plan Type (PL), Aggregation (PL), Plan Type (BS), Aggregation (BS), Plan Type (Plan3), Aggregation (Plan3), Plan Type (Wrkforce), Aggregation (Wrkforce), Plan Type (Capex), Aggregation (Capex), NumericAttrib
    No UDA's defined on "Entity"
    "NumericAttrib" attribute dimension (on base dimension "Entity"). NO attributes defined on the "NumericAttrib" dimension.
    NumericAttrib, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Operation
    "Employee" dimension properties and information:
    Employee, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Aggregation (Wrkforce)
    No UDA's defined on "Employee"
    "Line Item" dimension properties and information:
    Line Item, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Aggregation (Capex)
    No UDA's defined on "Line Item"
    "Asset Class" dimension properties and information:
    Asset Class, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Aggregation (Capex)
    No UDA's defined on "Asset Class"
    Exchange Rates properties:
    Table, Description, To Currency, From Currency, Operation, Method, Historical, Beg Balance, Year, Period, Average, Ending
    UDA properties:
    Dimension, UDA, Operation
    Smartlist properties:
    SmartList Name, Operation, Label, Display Order, Missing Label, Use Form Missing Label, Entry ID, Entry Name, Entry Label
    No Planning Unit Hierarchies are defined in this application.
    Translation input file fields:
    Value, Driver Member, Point-of-View, Data Load Cube Name
    [Thu Oct 27 18:16:18 JST 2011]Successfully located and opened input file "C:\TEMP\PLNentityバージョンのエクスポート.csv".
    [Thu Oct 27 18:16:18 JST 2011]Input file being read with UTF-8 encoding.
    [Thu Oct 27 18:16:18 JST 2011]Detected a UTF-8 BOM marker in input file "C:\TEMP\PLNentityバージョンのエクスポート.csv".
    [Thu Oct 27 18:16:18 JST 2011]Header record fields: Entity, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Base Currency, Plan Type (PL), Aggregation (PL), Plan Type (BS), Aggregation (BS), Plan Type (Plan3), Aggregation (Plan3), Plan Type (Wrkforce), Aggregation (Wrkforce), Plan Type (Capex), Aggregation (Capex)
    [Thu Oct 27 18:16:18 JST 2011]Located and using "Entity" dimension for loading data in "予算応用" application.
    [Thu Oct 27 18:16:18 JST 2011]Load dimension "Entity" has been unlocked successfully.
    [Thu Oct 27 18:16:18 JST 2011]A cube refresh operation will not be performed.
    [Thu Oct 27 18:16:18 JST 2011]Create security filters operation will not be performed.
    [Thu Oct 27 18:16:18 JST 2011]Examine the Essbase log files for status if Essbase data was loaded.
    [Thu Oct 27 18:16:18 JST 2011]Planning Outline load process finished (with no data load as specified (/N)). 9 data records were read, 9 data records were processed, 9 were accepted, 0 were rejected.

    Thank you for your reply.
    With your help, I can verify it easier rather than creating dataform to verify it.
    I have resolved the question now, the root cause is I had used the wrong parameter, shouldn't add '/N' in the command. for /N is a dry run to check whether there are error in CSV file, it won't perform metadata load.
    If no error occured, run the command without /N, then the metadata load will be performed.
    I refer to this artical,
    http://john-goodwin.blogspot.com/2008/08/time-to-look-in-bin.html
    Best regards,
    Samantha
    Edited by: Samantha on 2011-10-31 下午4:39

  • How can we delete a dimension from the classic planning applications

    Hi Friends,
    I am trying to delete a dimension from the planning classic application but i am unable to find out the delete option to delete a dimension. I created the dimension from the Administration -->dimensions --> Add dimension.
    If we want to delete a dimension how we can delete that dimension, I heard meta data is stored in the RDBMS so that why if we want delete dimension we need to delete in RDBMS so please tell me the location in RDBMS to delete dimension. i am using sql is RDBMS.
    Thanks in advance......

    As John mentioned, it is not supported and advisiable to delete a dimension from Planning application. but yes you can take a chance with some risk if you need to do so.. this opertaion is tested in 9.2 but i never tried in EPM V11.
    You will need to delete all the children first, then the dimension.
    BE SURE YOU HAVE A BACKUP OF YOUR APPLICATION BEFOREATTEMPTING THIS PROCEDURE.
    You will need to delete all the children first, then the dimension.
    If you have the dimension in forms, you may also need to (after step 5) go into the hsp_formobj_def_mbr table and delete all references of that object ID. Then delete the dim id in thehsp_form_layout table. Recycle services of Planning.
    Procedure: If you create a custom dimension in planning and wish to delete it, here is how you might remove it from SQL manually.
    it is recommended that only someone familiar with relational databases attempt this.The following assumptions are being made about the dimension: No forms have any references to thedimension. Any and all attribute dimensions have been removed from the dimension. Any and all members have been removed from the dimension. All security access has been removed from dimension. Any Alias associated with the dimension has been removed.
    1. Open the Enterprise Manager for SQL server
    2. Open the database that has your planning application
    3. Open the table HSP_OBJECT
    4. You need to find the row that has the dimension name you want to delete:
    5. Take note of the OBJECT_ID in my example it is50051, don't delete it yet.
    6. Open the table HSP_MEMBER
    7. Find and delete any rows that have a MEMBER_ID equal to the OBJECT_ID from step 5.
    8. Close the Table HSP_MEMBER
    9. Open the table HSP_MRU_MEMBERS.
    10. Find and delete any rows that have a DIM_ID equal to the OBJECT_ID from step 5.
    11. Close the table HSP_MRU_MEMBERS.
    12. Open the table HSP_DIMENSION
    13. Find and delete any rows that have a DIM_ID equal to the OBJECT_ID from step 5.
    14. Close the table HSP_DIMENSION
    15. Also delete it's reference from the HSP_UNIQUE_NAMES table.
    16. Delete the row in the HSP_OBJECT table that you found in step 4.
    17. Close the HSP_OBJECT table.
    18. Open Essbase Application Manager for the application and remove the dimension from the necessary Essbase outlines
    19. Restart the application server.
    good luck!!!
    -KP

  • How to load dimensions and members in Planning application

    Hello Everyone,
    I am trying to load dimensions and members in planning. I know that loading dimension is not recommended through Essbase but I wanted to give it a try. I tried to load the dimensions through rule files but it threw an error that the "members do not exist in database." Is that an indication that data cant be loaded at all in planning application through Essbase.
    Thanks is advance for all the replies !!

    If this is a planning application, you need to load metadata/dimension to planning first. You cannot load metadata directly to Essbase as it will be overwritten when you refresh planning.
    You should read documentation to understanding how planning works. Planning is an interface which sits on top on Essbase. However, Planning metadata is stored in database tables and it is synch'd with Essbase through Hyperion Planning refresh.
    In order to load metadata to planning, I would suggest to log on to planning and try to build dimensions manually first to know how planning interacts with Essbase. You could load metadata into planning through:
    1. Manually
    2. ODI: You will need to reverse planning application and then use it to load metadata
    3. Outline load utility on planning server.
    Remember, all Planning maintenance is done through planning interface and not through Essbase.

  • How to load Dimensions in Planning Application

    Hi,
    Please can someone help me loading dimensions and Data in Planning application using Loading Metadata Using the Outline Load Utility.
    Please guide.... you can email at [email protected]

    Hi Mohammed,
    Please check John's blog: http://john-goodwin.blogspot.com/2008/08/time-to-look-in-bin.html
    This is how I learned to use the OLU.
    I'd also check the admin guide.
    To load data: http://download.oracle.com/docs/cd/E17236_01/epm.1112/hp_admin/ch05s02s01.html
    To load metadata: http://download.oracle.com/docs/cd/E17236_01/epm.1112/hp_admin/ch05s02s02.html
    Cheers,
    Mehmet

  • Dimension level Security

    Hi All,
    Can anyone help me in providing Dimension level security for some members in a dimension? I have given planning application access as "Interactive User" and Reporting Level as "Explorer and Viewer".
    I am using Hyperion 11.1.1.3.
    Thanks in advance

    No the roles in Shared Services are not for defining member access in the planning application, if you want more information on the planning roles in shared services have a look at http://docs.oracle.com/cd/E12825_01/epm.111/epm_security/apas07.html
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • How to implement Dimension Level Security on Tabular?

    Not possible on SQL Server 2014 SSAS Tabular? How to work around?
    Kenny_I

    Hi Kenny_l,
    According to your description, you want to implement dimension security in SSAS 2014 tabular. Right?
    In Analysis Services Tabular mode, dimension level security (based on role permission) is not supported. This security can only used in Multi-dimension mode. In tabular mode, we can only use row-level security based on role permission.
    Please refer to links below:
    Implement Dynamic Security by Using Row Filters
    Reference:
    Comparing Tabular and Multidimensional Solutions (SSAS)
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou
    TechNet Community Support

  • Security on Year dimension in Hyperion Planning.

    Need to enable security on Year dimension on Hyperion Planning for below requirement. I know that we cannot enable security on year dimenison in Hyperion Planning, but want know if there is any custom solution.
    Requirement:
    IT users to have write access to Scenario: FY12FCSTJUN for year FY12 for period JUN to DEC & FY13 for Period OCT to SEP. (Calender year starts at OCT of every year)
    Normall users they want to have read access to Scenario: FY12FCSTJUN for year FY12 for period JUN to DEC and write access to Scenario: FY12FCSTJUN for Year FY13 for Period OCT to DEC
    1)we can modify the start period, end period, start yr and End yr for FY12FCSTJUN Scenario dimension to make FY12 FY12FCSTJUN as read/write for Specific year, but it won't meet the requirement.
    2)I have already tried making modification to the Planning respository table ( changed the value for ENFORCE_SECURITY parameter to 1 for DIM_ID 38 for Year in the HSP_Dimension table)on one of VM environments,but it won't enable security on the Year dimension.
    3)We can create a Budget scenario to achieve above, but it involves too many changes accross all the webforms and B rules, so we want to see if there is any custom solution available.
    Any suggestion/workaround to resolve the issue?

    Oracle will be releasing a patch in dec 2012 to fix/enable the security on year dimension. this patch is applicable for 11.1.2.2 version.

  • Remove security on Company Dimension

    Hyperion Planning 9.3.1
    We currently have security implemented on the company and entity dimensions. Security is granted to users based on being assigned to the appropriate company group and entity group(facility/location). We would like to remove the security on the company dimension and only have security at the entity level(facility/location). Does anyone know the best way to do this?

    If it is a custom dimension and you don't want to use security on the dimension anymore then you can go to the dimension administration and untick "Apply Security"
    otherwise
    I would probably use the ExportSecurity utility to export all the current access permissions :- http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_hp_admin/ch03s07.html
    Update the file it produces, then use the import security utility :- http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_hp_admin/ch03s06.html
    You may need to use the SL_CLEARALL security to remove all the security first or just set security to none in the file for the company dimension members.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Is there anyway migrate security defined on members via web client Planning

    Hello there,
    Can somebody help me , I have migrated dimensions and everything, except security from 9.2 to 11.1.1.3.
    I see that the security defined on the members using the web client is not migrated which is causing the updateusers uitility to fail! I guess.
    Can somebody suggest how I can migarte security without fail.
    Thanks
    Vince

    Hi,
    Couple questions:
    1. Are you using the same Shared services or new shared services?
    2. Have you provisioned all users to the new Planning application
    Migrating security for Planning application has below steps: --
    SHARED SERVICES STEPS: --
    1. Make sure all users are migrated in shared services. [If you are using the same shared services, then this is not valid]
    2. If you are migrating MSAD, make user that MSAD is correctly configured in new Shared services.
    3. Since you are directly assigning access to users in Planning, all users need to be provisioned to minimum "Planner" access to the new planning application in Shared services. Do this for for native users as well as MSAD users.
    PLANNING STEPS: --
    4. Export planning security in old planning application v9 to a text file using ExportSecurity.cmd utility in $PLANNINGHOME\bin folder. A new fileSecFile.txt will be created in the same folder
    ExportSecurity.cmd /A=AppName,/U=adminuser,/P=password,/TO_FILE=SecFile
    5. Check the file for any access that needs to be revoked and manually edit the file.
    6. Copy the security file to bin directory on new instance.
    7. Goto new Planning application in V11 and migrate identities in web front end.
    8. Import security in Hyperion Planning using ImportSecurity.cmd utility in $PLANNINGHOME\bin folder in new planning application.
    ImportSecurity.cmd "AppName,adminuser,password,SL_COMMA,,SL_CLEARALL"
    9. Generate security filters by going in Planning app and "Administration" -> "manage security filters"
    10. Refresh database and security filters in v11
    Lets me know if this helps.
    Cheers,
    RS

  • Any utility or tool which extracts/exports security from planning application

    <p>Hi Everyone,<br><br>Would like to know if there is any utility or tool whichextracts/exports security from planning application.<br>By security i mean dimensional level security plus users andgroups.<br>Or SQL queries to fire on planning repository.<br>Or any workaround.<br><br>Thanks,</p>

    I'm not 100% certain, but you can try the ESD tool on the hyperion community portal (www.hyped.biz). It was designed for Essbase, but it's possible that it will work properly on a planning cube. Besides dumping security, it captures server, app, and db settings, flags user and group exceptions, validates filters, and generally gives some nice feedback.<BR><BR>-Doug.

  • Row level security at universe design level

    Hi,
    I am creating a Universe layer on top of non SAP OLAP cube ( from MS Analysis Services 2005 ) .
    My concern is that can we maintain the row level or data level security at universe design level or if i am using that universe in creation of WEBI report so is there any possiblity to maintain this security at WEBI level.
    Regards,
    Mishra Vibhav.

    Thanks for the reply.
    Much Appriciated.
    My only concern is that i read in the Universe Designer developer guide that it does the row level security so can eloborate a bit about how we maintain at Universe level.
    Warm Regrads,
    Mishra Vibhav

  • EPMA 11.1.2.1 : A non-desired dimension is created in Planning with EPMA

    When a new Hyperion Planning application is deployed with EPMA 11.1.2.1, a 'Cut-off' dimension is created in the newly deployed applications.
    'Cut-Off' was a local dimension for an application deployed from EPMA. But we do not know how this dimension is deployed in all new applications even without adding it to the library of the application. ' Cut 'Off' has been removed and the application where it was also presented. But in the EPMA tables, there's elements of the old application where 'Cut'Off' was present.
    How to solve this problem?
    How to remove problems in EPMA? Thank you for your help.
    Cyril

    its not.Here is the support matrix:
    https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CB4QFjAA&url=http%3A%2F%2Fwww.oracle…
    For 2012 its 11.1.2.4
    Cheers..!!
    Rahul S.

  • Join fact table with higher dimension level

    how do i join fact tables with higher dimension levels with discoverer?
    fact with detail at level C
    measure X
    dimension with
    D->C->B->A
    E->C
    level
    A B C
    1------1------1
    2------2------1
    3------2------1
    join between fact X and dimension level C
    X=3*C because of sum(X) in discoverer and 3xC in dimension
    is there a way to get correct values for X without creating a dimension like
    D->C
    E->

    another way of asking this is whether you can create a summary table in Discoverer at a higher level than a dimension's fundamental grain. In other words - the summary examples in the documentation all describe leaving out one or more of your dimensions... they are either left in or completely taken out. But, some of the most effective summarization occurs when you summarize daily data to a monthly level. Assuming that I have a sales table (at a daily level, and a key value sales_date), and a table date_dim (primary key sales_date), I would like to create a summary sales_month_summary where the sales are grouped on month_year (which is a field in the sales_date table).
    How is this done? I suspect that we can't use the date_dim table with the summary (due to the problems noted by the poster above). Do we have to create another table "month_dim"? Do we have to fold all of the desired date attributes (month, quarter, year) into the summary? Obviously we'd like to re-use all of the pertinent already existing date items (quarter, month, year, etc.), not recreate them over again, which would result in essentially two sets of items in the EUL. [One used for this month summary, and another used for the detail.]
    I searched the forum - someone asked this same question back in 2000 - there was no answer provided.
    The only other thought I have is to "snowflake" the date_dim into two tables and two folders, one at a date level, another at the month level. Then the detail tables can connect to date_dim (which is linked to month_dim), while the summary data can connect directly to month_dim.

  • Network security:LAN manager authentication level setting on GPO

    Hi,
    We have a requirement from project team to change the one of the security setting on default domain policy for all computers in domain. Below are the security setting which we need to modify.
    computer configuration-->windows settings-->security settings-->local policies-->security options-->
    Network security: LAN manager authentication level 
    this setting need to be changed to - Send LM & NTLM - use NTLMv2 session security if negotiated.
    The project team facing issue with Apache web server and they found the solution on below link.(we have tested this  by changing local group policy and this solution works as expected)
    https://www.sysaid.com/Sysforums/posts/list/9065.page 
    We need to know what is the impact after enabling this on domain computers.
    Need help on this to go-head on this.

    Hi,
    you have a weaker domain security overall. "
    LM Hash Generation 
    The algorithm introduces several weaknesses that attackers can exploit. First, all lowercase characters are set to uppercase, reducing the number of possible characters. Second, it splits a long, strong, password into two seven-character chunks.
    Both the LM and NTLM protocols operate essentially the same way; the only difference is the password hash.
    REF: The Most Misunderstood Windows Security Setting of All Time
    This post is provided AS IS with no warranties or guarantees, and confers no rights.
    ~~~
    Questo post non fornisce garanzie e non conferisce diritti

Maybe you are looking for