How to setup Dimension Attributes in ERPI

Hi All,
      I am currently in process of setting metadata rules in ERPI to extract hierarchies from EBS into EPMA Planning and HFM application. Our hierarchies are already setup in these applications but we need to replace this process with ERPI. I know ERPI does give capability of handling some attributes such as Data Storage Parent, Data Storage, Expense Reporting, Account Type, Time Balance for Balance sheet and income statement OR use system defaults.
My question is how do I define these attributes in a way that it keeps the ones that are currently in the system?. How about +,- aggregation operators, Two Pass Calculation, Smartlist, Data Type, etc?. If I use system defaults, will it overwrite the current ones?.
Please suggest. I need to be able to keep currenty attributes as it is and just update the metadata piece.
Thanks Everyone. Any feedback will be greatly appreciated.

Refer to pages 81-82 of the ERPI Administrator Guide (11.1.2.2)
http://www.oracle.com/technetwork/middleware/epm/documentation/index.html

Similar Messages

  • Defining Dimensions, Attribute Hierarchies for a Link Table(Many to Many)

    I have 3 Tables in the Database
    Table 1: Transactions (Fact Table) - PK(TransactionId)
    Table 2: Relationship (Dimension1) - PK(Relationship Id), FK_TransactionId, FK_CompanyId, RelationshipType
    Table 3: Companies (Dimension 2) - PK(CompanyId)
    Table 2: Relationship table is a link table between Transactions & Companies to facilitate many to many relationship. 
    I defined Fact and Dimension tables accordingly but having issues defining Dimension & Attributes for Relationship tables
    Relationship Dimension:
    I have 3 hierarchy groups defined
    Hierarchy 1 - Relation -Relationship Type,Relationship Id(PK)
    Hierarchy 2 - Transaction - Transaction, Relationship Id(PK)
    Hiearchy 3 - Company - CompanyId, Relationship Id(PK)
    Defined the attribute relationship in the following way
    RelationshipID(PK) ---> CompanyId , RelationshipID(PK) ---> TransactionId, RelationshipID(PK)
    ---> RelationshipTYpe
    I am getting incorrect results when I deploy the cube. Not all the types are being displayed only 4 types are being displayed out of 27 types though there exists Transactions for all the Types.
    To fix the incorrect results, I tried to break the Relationship Dimension into 2 dimensions seperating Transaction(Relationship Dim) & Company,Type (Companies Dim). I tried to configure a many
    to many Relationship type between my  Companies Dim & Fact Table Transaction. But I get the error that says 
    "Companies Dim many to many dimension in the Tansaction measure group requires that the granularity of the Relationship dimension is lower than that of the Relationship measure group "
    Any help regarding how to difine Dimensions & Attribute Hierarchies on a Many to many link table is appreciated.

    Hi Jaya,
    According to your description, you are experiencing the issue when implement many to many relationship by using a bridge table in your SQL Server Analysis Services project, right?
    Generally, a bridge table will have a surrogate key for the dimension and a surrogate key to the fact table or a degenerate dimension based on the fact table. Here are some blogs which describe how to implement many to many relationship using a bridge
    table.
    http://bifuture.blogspot.com/2011/06/ssaskimball-modeling-nm-relation.html
    http://www.sqlchick.com/entries/2012/1/22/data-modeling-tip-when-using-many-to-many-bridge-tables-in-s.html
    http://social.technet.microsoft.com/wiki/contents/articles/22202.a-practical-example-of-how-to-handle-simple-many-to-many-relationships-in-power-pivotssas-tabular-models.aspx
    Regards,
    Charlie Liao
    TechNet Community Support

  • Displaying non-level determining dimension attributes in bibeans with cwm2

    In the bibdemo example (defined using the CWM API), the attributes PROD_COLOR and PROD_SIZE are defined as dimension attributes of the Product dimension. They are then available to bibeans applications for use in the query editor/match condition (as where clauses e.g. where Size = LARGE).
    When I define OLAP metadata objects using the CWM2 API, my non-level determining dimension attributes are not available in the bibeans query editor.
    Has any one exprienced this problem? Is there a work-around or code fragment that explains how to get dimension attributes defined using CWM2 to work in bibeans apps.

    basically there are list and hierarchical dimensions.
    the first type doesnt have a hierarchy, so some sort of special case of the 2nd.
    i used attributes on list dimensions successfully in the past.
    the only thing i had to do is nevertheless define a "artificial" level.
    let me know if you need more,
    thomas

  • How to create an attribute dimension in Essbase Studio?

    I cannot figure out how to create an attribute dimension using Essbase Studio. The online help states that I need to "Find the Attribute settings grouping in the center" of the member properties dialog box. I suspect that I'm having a problem figuring this out because I don't have the attribute dimension properly defined in the relational data source or in the mini-schema. I've tried creating a table with no key relationship to the other tables and with no logical joins defined, but that doesn't seem to help. Any ideas?

    so in the 11.1.1 version you would click on the member name in the hierarchy you added to the Essbase model and in the center pane of the general tab should be the attributes settings section.
    If I had a dimension called stores wth two groupings unser it region and store_type, I would click on store_type and add the attribute info

  • 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

  • How to setup the complex ownership relationship in SAP BPC

    Hi Buddies,
    I am new to SAP BPC. For legal consolidation, I am confused how to setup the ownership in BPC. The senario is following:
        P is the parent company, S1 and S2 are subsidiaries.
        1) P owned S1 80%, ownded S2 90%, meanwhile S1 owned P 20%
            How to setup this?
        2) P owned S1 80%, owned S2 70%, and S1 owned S2 10%.
            How to setup this?
    For above 2 senarioes, how to calculate the Minority Interest? ( Using different consolidation rules?)
    And if there are subgroup, how to see the subgroup result?
    Thanks in advance.
    Maggie Liu

    Hi Will,
    Thanks for reply... Actually, I've tried that before(putting comma after the flag "all," presuming the 71st step shows that I should have 3 members in the memberset under the ICDatasrc dimension. But it also did not work.
    Nope, step 71 did not tell us to use piping and consequently expanding the col key range.
    Thanks...
    Dryan

  • How to setup the access privilege of flash file in Web Intelligence?

    How to setup the access privilege of flash file in Web Intelligence?   WEBI can set access privilege for single WEBI report file, but it seem cano not set access privilege for one flash file.

    Thank you Maksim,
    I did set the "selectionMode" to "Auto". I don't understand where In supply function I have to set lead selection of nested node to first element. Please elaborate on this. Are you talking about the context attribute bound to the second table? OR do I have to change the Importing parameters "Node" and "Parent_Element" of my supply function?
    Thanks for your time.

  • How to report dimension using OLAP_TABLE

    Hello all,
    I am new to the OLAP DML. ANd struggling to make a good use of it.
    A dimension called BU is created in AWM with several hierarchy like BU_2004, BU_2005, BU_2006 etc. These are all value based hierarchies.
    Each hierarchy has the same dimension attributes (member, parent, long_description, short_description).
    How do I report all the attribute values from a hierarchy (example BU_2004).
    I am trying to write a sql with OLAP_TABLE and struggling. Can some of the experts out there help me?
    Thanks a lot.
    Parag.

    Hi Steve,
    Just wanted to check if you are able to resolve this issue? i am in the same boat and wanted to check if you have any solution.
    Thanks

  • Using dimension attributes in the Query Builder Bean

    All...
    I am developing an HTML client based tool using the JSP tags. I wish to create a report that selects the appropriate dimension value based upon an attribute.
    But...
    Using the query builder I can not select dimension values based upon dimension attributes. Is this possible? The only use I have found for the attributes is when I am sorting my selected diemsnion values.
    Thanks in advance
    Dylan.

    1. Java Client QueryBuilder has support for selecting dimension members based on an attribute.
    To use this functionality, go to Dimensional Panel -> Conditions tab. Drill on Match group of conditions. The attribute condition appears as the last available condition, but only for dimensions that have attributes.
    To test this, use BIBDEMO schema supplied with BI Beans and look at conditions for Product dimension.
    2. If you wish to display dimension attributes and their values in the HTML client UI,
    here is how you can retrieve attributes and their values for a dimension:
    (e.g. for Product dimension in BIBDEMO)
    String dimensionID = "MDM!D_BIBDEMO.PRODUCT";
    String hierarchyID = null;
    MDDimension dimension = metadataManager.getDimensionByUniqueID(dimensionID);
    MDHierarchy hierarchy = dimension.getDefaultHierarchy();
    if (hierarchy != null)
    hierarchyID = hierarchy.getUniqueID();
    // Retrieve all the attributes for this dimension
    MDAttribute[] attributes = dimension.getAttributes();
    if (attributes != null && attributes.length > 0)
    String attributeID = null;
    AttributeListStep attrStep = null;
    Selection sel = null;
    MetadataMap map = new MetadataMap(new String[] {MetadataMap.METADATA_VALUE});
    for (int i=0; i<attributes.length; i++)
    // Get the unique ID for the attribute
    attributeID = attributes.getUniqueID();
    // Create and evaluate an AttributeListStep
    attrStep = new AttributeListStep(dimensionID, hierarchyID, attributeID);
    sel = new Selection(dimensionID);
    sel.setHierarchy(hierarchyID);
    sel.addStep(attrStep);
    // Evaluate the AttributeListStep and get the DataAccess
    DataAccess da = query.createQueryAccess().getDataAccess(sel, map);
    // Walk the DataAccess and get the attribute values
    if (da != null)
    int extent = da.getEdgeExtent(DataDirector.COLUMN_EDGE);
    for (int i=0; i<extent; i++)
    // Get the attribute value
    strValue = (String)da.getMemberMetadata(DataDirector.COLUMN_EDGE, 0, i, MetadataMap.METDATA_VALUE);
    // Add the value to a drop down or another UI element...

  • How to Use Dimension Operator

    Hi
    I'm trying to implement SCD Type 2. I have done so using conventional methods.
    I have read in some blogs that dimension operator can be used for SCD. Can any one provide me material on how to use Dimension Operator. I tried OWB User guide. But its not useful.
    I have seen that we need to create levels. But i dont need levels.
    Can somebody please tell me how to use it.
    Regards
    Vibhuti

    Hi Vibhuti,
    using dimensions with OWB 10g R2 isn't that difficult. You just create a number of attributes like an ID, a business key and probably a description and then associate each of the attributes with a level. You need at least one level that all the attributes are associated to. Then you can use the slowly changing dimension wizard (SCD) to track changes. In the SCD settings you can determin for which attribute you want to trigger history and which attributes contain your effective date and your end date (if you want to use SCD type II). Obviously you would need two additional attributes in every level for that purpose.
    Regards,
    Jörg

  • Dimension Attributes

    Hi
    I'm designing a fact table and a dimension table, but the dimension tables are having many level and each level is having many attributes, pls see the following data and pls help me in how to go ahead with this kind of dimension attributes.
    A00001 - All
    BALANCE_SHEET - Balance Sheet Accounts
    ASSETS - Assets
    [110000 - 150317]
    [151610 - 151620]
    [A12110 - A13999]
    [A14214] - Short Term Prepaid Assets
    [A14999] - Capital Leases
    [A15214] - Short Term Prepaid Amort
    [A15999] - ACD Capital Leases
    FIXED_ASSETS - Fixed Assets
    PURCHASED_ASSET - Purchased Assets
    PFURN_MACH_EQ - Purch Furniture Machinery Equi
    [A14001 - A14003]
    [A14099] - Pre-Paid, Maintenance
    [A14100 - A14213]
    [A14500 - A14900]
    PACD_FURN_MACH_EQ - Purch ACD Furn Mach Equip
    [A15001 - A15003]
    [A15099] - ACD: Pre-Paid Maintenance
    [A15100 - A15213]
    [A15300] - ACD: Building Improvements
    [A15500 - A15900]
    LEASE_ASSETS - Lease Assets
    LLAND - Capital Lease Land
    [A14004] - Capital Lease Land
    LINFRA_NONDEP - Capital Lease Infra Non Deprec
    [A14005] - Capital Lease Infra NON DEP
    LCIP - Capital Lease Cnstruct In Proc
    [A14006] - Capital Lease CIP
    LBUILD_IMPROVEMENTS - Capital Lease Building & Impro
    [A14007] - Capital Lease Bldgs & Improv
    LFURN_MACH_EQ - Capital Lease Furn Mach Equip
    [A14008] - Capital Lease Furn Mach Equip
    LINFRA_DEP - Capital Lease Infra Deprec
    [A14009] - Capital Lease Infra DEPREC
    LACD_BUILD_IMPROV - Capital Lease ACD Build Improv
    [A15007] - ACD Cap Lease Bldgs & Improv
    LACD_FURN_MACH_EQ - Capital Lease ACD Furn Mach Eq
    [A15008] - ACD Cap Lease Fur Mach Eq
    LACD_INFRA_DEP - Capital Lease Infra Deprec
    [A15009] - ACDCap Lease Infra DEPREC
    LIABILITIES - Liabilities
    [201000 - 203000]
    [L00001 - L21179]
    FUND_EQUITY - Fund Equity
    [351000] - AR - WRITE OFF
    [370000 - 388890]
    [F00007] - Fund Balance: Restricted,State
    INCOME_STATEMENT - Income Statement
    REVENUE - Revenue
    GENERAL_REVENUE - General Revenue
    [400100 - 496600]
    [900001] - Appropriation Transfer
    STATISTICAL - Statistical
    [S00001 - S00017]
    EXPENSE - Expense
    [E10000] - All Expense Accounts
    PERSONAL_SERVICES - 1 Personal Services
    [E19999] - Point 1 Roll Up
    [E51000] - Roll Up For Personal Services
    SALARIES - 510100 Salaries
    [510100 - 510101]
    [510200 - 510201]
    thanks

    Hi,
    Assuming that when you say " have make BP as DIM ID" it means that you have included it in a dimension. Correct?
    You can make it as "line item" and you will still be able to report with its NavAttr and even with time dependance (ratings) provided you time dependant attr is NAV.
    The only difference between line item dimensions and normal dims is that no dimension table created and you can only have one char in it.
    You should do that for a characteristic having very high granularity (number of records posted of your characteristic divided by the total number of records in your fact tables (F and E) ). Usually document/item numbers are in that case (granularity is more than 50%; other will say 20% but I personally think that with 20 the DIM table still reduces the query time).
    By not having the dimesion table, a query using this kind of characteristic will select the data directly form the cube fact tables instead of first going to the DIM table, gather DIMIDs and go to the E/F tables...
    hope this helps...
    Olivier.

  • Distinct count of role-played dimension attribute

    Needed distinct count of AccountGroup attribute of AccountB dimension which is a role played dimension of Account.
    Added measure distinct count of the dimension attribute (AccountGroup). In dimension usage added the main fact table as intermediate for other dimensions with many2many relationships.
    The two role played Account dimensions must be related to the new AccountFact table with fact relationship.
    But then how will I be able to count distinct attribute of
    certain Account dimension (out of the two role played dimensions)???
    Namnami

    Thanks for the links, they are useful. But still they do not explain how to manage a distinct count of
    certain role played dimension attribute. 
    I gave up on this and added that dimension attribute to the fact table so now I do a regular distinct count on a cube fact measure. 
    Thanks
    Namnami

  • Oracle Express Dimension attributes

    Hi,
    I would like to create a multi-dimensional database with Oracle Express. I don't how to define dimensions with attributes.
    Is anybody can help me?
    Thank you.

    why is it slow even though i acces the site from my own pc where is oracle express is install..Probably because you have too much going on the machine.
    Oracle database works best if it can get 250-400 M Ram to itself. It gets real bad when there is a lot of paging or swapping - which is an OS problem, not really Oracle's problem.

  • How to activate camera attributes in the MAX / LabVIEW

    Hello,
    I have created an icd file for a VieWorks camera. Therefore I used the camera file generator tool of NI. In this tool I can setup camera attributes. After creating the file, I opened the MAX and selected the camera in the IMAQ devices. The attributes I generated where correctly shown. The question now is how to activate the attributes. For instance I created an attribute to activate / deactivate the FAN. When I select the attribute in the MAX and set the value to ON, nothing happens.
    This also fails when I use the SetCameraAttributes.vi in labview. I use LV2009 and IMAQ 4.6.1
    Does anyone have any suggestions?
    Regards,
    Marc Vanmaris

    Hello,
    Just check in MAX that the "Serial Enable" is selected. It seems that the serial command is not send to your camera.
    Hope this helps

  • OLAP Dimension Attributes in a BI Beans Crosstab

    Hello,
    How can I show my custom OLAP dimension attributes in the BI Beans Crosstab?
    Can I compare this attributes with the measures?
    I have a cube with three dimensions and I have defined some limit amounts which are valid only for one of the dimensions. Additionally they are defined only for aggregated levels in this dimension.
    I was wondering whether I could define these limit amounts as dimension attributes and use them to compare with the measures.
    Is there any other possibility?
    Maybe I can create my custom column in the Crosstab?
    Thanks in advance,
    Michal

    I would recommend using the built-in security feature of the analytic workspace. There is a command called PERMIT that can be applied to both dimensions and cubes and controls user access to dimension members.
    There is a document on the OLAP home page that explains how to secure and AW using the permit command
    http://www.oracle.com/technology/products/bi/olap/olap10g_applying_aw_security.doc
    Hope this helps
    Keith Laker
    Oracle EMEA Consulting
    BI Blog: http://oraclebi.blogspot.com/
    DM Blog: http://oracledmt.blogspot.com/
    BI on Oracle: http://www.oracle.com/bi/
    BI on OTN: http://www.oracle.com/technology/products/bi/
    BI Samples: http://www.oracle.com/technology/products/bi/samples/

Maybe you are looking for