Creating shared members through EAS load rule with duplicates allowed

I'm building my first Essbase cube where I need to activate "allow duplicate member name" in the outline. I have trouble finding a way to get the shared members added to the outline via a rule of the load. I tried to run my load of rules that I used before I activated the "allow duplicates" setting, but it does not work now. It creates members in double, which makes sense to me. I don't see a setting that I can turn to get the shared members added via load rules however.

Help?

Thank you...

Bill

In your workload file, you will need to use full qualified member names or load rule allows to transform members to the full qualified member names.

Go to this link and read the sections below

http://download.Oracle.com/docs/CD/E10530_01/doc/EPM.931/html_esb_dbag/frameset.htm?dotdimb.htm

Strengthening of the members to double outlines
Identifies the members via the rules file
File qualified member names through the rules of construction

Tags: Business Intelligence

Similar Questions

  • Migration of Essbase loading rules with source RDBMS from Windows to Linux

    Hello

    We have essbase load rule with the sql data source. In windows, it linked through ODBC created using the ODBC Manager in Windows. The Essbase server in the Production environment is now on the linux machine. How to connect the rule files essbase with the SQL data source now?

    Kindly help.

    Kind regards
    SS

    You must configure the odbc.ini file to add a data source - http://docs.oracle.com/cd/E17236_01/epm.1112/esb_sql_interface/frameset.htm?ch02s03.html
    If you have problems have a search for odbc.ini on this forum and you will see a few posts on the subject.

    See you soon

    John
    http://John-Goodwin.blogspot.com/

  • Assign attributes through data load rule?

    Hello

    I created a dimension attribute 'status' with two members: temp and perm

    Then, I associated the dimension for the Customer dimension.

    Then, I created a text file with:

    Customer1, Temp
    Customer2, Perm

    I am creating a loading rule that assign the attribute wished the customer wanted through this file. For the life of me I can't make it work... What exactly is the step in the DLR? I have tried everything I can think about and I can't make it work... I am doing something fundamentally wrong, but can't find anything on how to do it. Or is this even possible?

    As MetMed said, you must do as a rule of generation of dimension, so I'll assume that's what you try. Suppose that your Custiomer1 and 2 are members of zero (it facilitates this example). Together the build properties from dimension to dimension to be level build, then column 1 set to level 0, clients for RL second column (attribute) set the customer dimension and scroll to the bottom of the column for the name of the attribute definition.
    Then when loading through EAS, make sure you load to change only the value (or are - this only metadata). At anyway is not only

  • Is it possible: Loading SQL with generic rule file?

    Hello
    When you load a flat file into Essbase, can be defined in the header of the data load domain names. In the load data, dimension names given and at the end of the data. In the file rule under Options > properties of data source > header reference could be made to this line. It works very well.

    We want to load the data with SQL in the same way. A load rule with a variable substitution for the selection view and we can use it for every load of data. We specified the name of dimension in the table column header. The data column has been defined as 'data' - without the quotes.

    The result is so far, it does not load.
    The question is - did someone tried this before and can help me on this?

    Thanks in advance.

    Kind regards
    Philip Hulsebosch
    www.trexco.nl

    the data column can be repersented in several ways, as I do usually is to set for the Member, it belongs to. In my example where your variable substitution & currmth is "Jan" then "Jan" would be the name of the column. The next month when the var void changes to Feb, on Feb.

  • Moving shared members

    Gurus,

    Background:

    I update the metadata in application of ASO using loading rules. We use 2 rules of loading for a dimension

    1. for principal members of updating\creating (movements to allow is enabled)

    2. for members shared (Allow moves is OFF, as when turned on, it will move members)

    I have a single source file and how these rules of 2 load the distinction between primary & shared members is by checking 'StorageField' in the source file. (Select / option in the State of load rejection)

    v (11.1.2.2)

    Question:

    I need to move the members in the hierarchy. 'Allow the movement' moves the main members of the place where I want to create shared members.

    Please let me know if there is a way to move the members shared through charge rule above scenario or I have to do it manually.

    Thank you

    ~ RN.

    In the first rule load are reload you the hierarchy full (excluding the shared members), if you are then you could use delete option not specified in the rule of the load then it will remove all members not to load and you can rebuild shared members.

    See you soon

    John

  • Essbase dimension build shared members

    Hello

    I will have questions and he drives me crazy!

    I'm building a dimension using parent child references. The first generation of dimension puts members stored in place. The second generation implements the shared members. I am not getting any errors and still 'shared' members are not being built with shared member label. Documentation, I was under the impression that essbase should realize that they are shared and mark them accordingly during the generation of dimension?

    I can go through and manually set the shared in EA after than the build... but it kind of defeats the object.

    I feel I missed something just really hehe. Any help would be appreciated.

    Thank you

    Russell

    The only time where the outline you would save with members not be labeled as hared, is that if you have names of members in double lit in the sketch, otherwise you will get errors.  One thing you can check in the generation of dimension properties is that you do shared members is more verified and allow moves is not checked

  • Error loading data with a rule in 11.1.2.1 file loading

    When I do the dim the Parent child build and alias will not load?

    Rule reading information SQL for the database [DP]
    Rule of reading of the purpose of the database rule [DP]
    Active parallel loading: [1] block to prepare the discussions, block [1] write discussions.
    DATAERRORLIMIT reached [1000]. Rejected records will be is more connected
    No value data modified by this data file loading
    Data load time for [Accounts01.txt] with [ACCOUNT.rul]: [0.512] seconds
    There were errors, look in C:\Oracle\Middleware\EPMSystem11R1\products\Essbase\eas\client\dataload.err
    Completed import data ['RPIWORK'.'] [DP ']
    Out of the prepared columns: [0]

    Outline = measurement Demension

    Measure
    Balance sheet
    Profit & loss

    Data file

    is a SQL query
    to Excel and save it as a text (delimited by tabs)

    Account.txt

    Parent | Child | Alias
    Total assets of the balance sheet 10000
    Total liabilities of the balance sheet 20000
    Balance Sheet Total 30000 of the owner
    Profit & loss 40000 recipes
    Profit & loss 50000 cost of goods sold
    Profits & losses 60000 S.G./A.
    Profit & loss 70000 other operating income
    Profit & loss 80000 other expenses
    Profit & loss 85000 interest income/expenses
    Profit & loss 90000 taxes
    Profit & loss 99000 capitalized Contra
    10000 10100 short-term assets
    10000-14000 «wood, forest and roads land»
    10000 17000 "goods, materials and equipment.
    10000 to 19000 active other long-term
    10000 19750 deferred tax assets
    20000 20001 short-term liabilities
    20000 21200 other Long term liabilities
    20000-22000 timber contracts
    20000 25100 long-term debt
    20000-26000 deferred tax liability
    30000 Equity subsidiary 30001
    30000 30250 voting common shares
    30000 30350 according to Common Stock
    30000 30450 capital paid in additional
    30000 30550 retained earnings
    30000 30610 other comprehensive income items
    30000 30675 tax distribution to Shareholde
    40000 40055 wholesales
    40000 41500 chips recipes
    40000 43000 power sales
    40000 nursery 45000 income
    40000 46000 transfer logs
    40000 47000 Intraco sales
    40000-49000 sale deduction
    50000 Labor 51000
    50000 52000 raw
    50000 rental 52800
    50000 53000 operating expenses
    50000 53900 forestry supplies
    50000 capitalized 53999 Contra-forestry
    50000 maintenance 54000
    50000 55000 fuels & lubricants
    50000-56000 utilities
    50000 57000 cost of direct registration
    50000 57500 personalized services
    50000 impoverishment 57700
    50000 58000 cost allocations of goods sold
    fixed cost 50000 59000
    50000 59510 changes in inventories
    60000 60100 salaries
    60000 60300 maintenance of PC hardware
    60000 60400 other G & A
    61000 60000 licenses/fees/charges
    60000 61400 benefits not
    60000 61550 furniture/fixtures
    60000 legal 61750
    60000 62000 fresh office
    60000 62500 professional services
    60000 63000 activities pre & Post jobs
    60000 63200 telecommunication costs
    60000 63550 employee activities
    60000 63800 sales & Promotions
    60000 63900 banking questions
    60000 64000 Admin depreciation
    60000 64500 insurance and property taxes
    60000 65000 allowances S G & A
    60000 66000 outside management
    70000 70100 rental income
    70000 disposals of fixed assets 70200
    70000 70400 Misc income
    80000 80200 factory inactive
    85000 85001 interest expense
    85000 85200 interest income
    90000-90100 income tax charges

    error file

    ------20000 not found in the database members
    20000 25100 long-term debt

    ------20000 not found in the database members
    20000-26000 deferred tax liability

    ------Member 30000 not found in the database
    30000 Equity subsidiary 30001

    ------Member 30000 not found in the database
    30000 30250 voting common shares

    ------Member 30000 not found in the database
    30000 30350 according to Common Stock

    ------Member 30000 not found in the database
    30000 30450 capital paid in additional

    ------Member 30000 not found in the database
    30000 30550 retained earnings

    ------Member 30000 not found in the database
    30000 30610 other comprehensive income items

    ------Member 30000 not found in the database
    30000 30675 tax distribution to Shareholde

    ------Member 40000 not found in the database
    40000 40055 wholesales

    ------Member 40000 not found in the database
    40000 41500 chips recipes

    ------Member 40000 not found in the database
    40000 43000 power sales

    ------Member 40000 not found in the database
    40000 nursery 45000 income

    ------Member 40000 not found in the database
    40000 46000 transfer logs

    ------Member 40000 not found in the database
    40000 47000 Intraco sales

    ------Member 40000 not found in the database
    40000-49000 sale deduction

    ------Member 50000 not found in the database
    50000 Labor 51000

    ------Member 50000 not found in the database
    50000 52000 raw

    ------Member 50000 not found in the database
    50000 rental 52800

    ------Member 50000 not found in the database
    50000 53000 operating expenses

    ------Member 50000 not found in the database
    50000 53900 forestry supplies

    ------Member 50000 not found in the database
    50000 capitalized 53999 Contra-forestry

    ------Member 50000 not found in the database
    50000 maintenance 54000

    ------Member 50000 not found in the database
    50000 55000 fuels & lubricants

    ------Member 50000 not found in the database
    50000-56000 utilities

    ------Member 50000 not found in the database
    50000 57000 cost of direct registration

    ------Member 50000 not found in the database
    50000 57500 personalized services

    ------Member 50000 not found in the database
    50000 impoverishment 57700

    ------Member 50000 not found in the database
    50000 58000 cost allocations of goods sold

    ------Member 50000 not found in the database
    fixed cost 50000 59000

    ------Member 50000 not found in the database
    50000 59510 changes in inventories

    ------Member 60000 not found in the database
    60000 60100 salaries

    ------Member 60000 not found in the database
    60000 60300 maintenance of PC hardware

    ------Member 60000 not found in the database
    60000 60400 other G & A

    ------Member 60000 not found in the database
    61000 60000 licenses/fees/charges

    ------Member 60000 not found in the database
    60000 61400 benefits not

    ------Member 60000 not found in the database
    60000 61550 furniture/fixtures

    ------Member 60000 not found in the database
    60000 legal 61750

    ------Member 60000 not found in the database
    60000 62000 fresh office

    ------Member 60000 not found in the database
    60000 62500 professional services

    ------Member 60000 not found in the database
    60000 63000 activities pre & Post jobs

    ------Member 60000 not found in the database
    60000 63200 telecommunication costs

    ------Member 60000 not found in the database
    60000 63550 employee activities

    ------Member 60000 not found in the database
    60000 63800 sales & Promotions

    ------Member 60000 not found in the database
    60000 63900 banking questions

    ------Member 60000 not found in the database
    60000 64000 Admin depreciation

    ------Member 60000 not found in the database
    60000 64500 insurance and property taxes

    ------Member 60000 not found in the database
    60000 65000 allowances S G & A

    ------Member 60000 not found in the database
    60000 66000 outside management

    ------Member 70000 not found in the database
    70000 70100 rental income

    ------Member 70000 not found in the database
    70000 disposals of fixed assets 70200

    ------Member 70000 not found in the database
    70000 70400 Misc income

    ------Member 80000 not found in the database
    80000 80200 factory inactive

    ------Member 85000 not found in the database
    85000 85001 interest expense

    ------Member 85000 not found in the database
    85000 85200 interest income

    ------Member 90000 N
    t database
    90000-90100 income tax charges


    That's how I build my loading rules file

    Create-> rules file
    File-> opendatafile->

    account01.txt

    Field-> Dimension Build Properties properties

    Dimension =
    Field 1 measure; Type = Parent
    Measurement of field 2; Type = child
    Measurement of field 2; Type = Alais

    Click the Dimension Build field
    Click on setting Dimension build - Parent\Child
    Ok

    Validate - rule is correct

    Save as account

    Load the data file = Acciount.txt
    Rule file = account

    Ok

    Published by: level following December 11, 2011 06:24

    Published by: level following December 11, 2011 06:25

    Published by: level following December 11, 2011 06:27

    The drop-down list in the EA when you right click on the database and select load data. I have a question, the Member that already in outline? If this isn't the case, you will have problems. You would have to add it or have a line in the file to load at the top, with something like account, balance sheet in it. Also in the State of charge have you changed the load parameters of dimension for the dimension of accounts to be parent/child for the dimension of accounts. Often enough, the people don't realize they have to double-click the dimension name to make sure it gets set as the dimension that gets changed.

    I'm sure that your question is she trying to make loading the data and not the generation dim, but it might just be the first problem

  • Cannot create shared using generation members reference build, method

    Hi all

    Is there a limitation on Essbase Dimension build rules which disables you to create members shared using the generation of reference build method? I think I've tested all possible scenarios, including using the property of field duplicate generation without success. Please see my test below folder. Just for info, I was able to create members shared with the build Parent/child method. I've read a few threads on this forum, who in fact recommend method Parent/child to create members shared, but I wanted to check with you guys.

    Generation (isn't work)

    Gen2 | Gen3 | Gen4
    Home | M0001 | 00001_0002
    Alternative | A0001 | 00001_0002

    Parent/child (of work)

    Parent | Child
    Home | M0001
    M0001 | 00001_0002
    Alternative | A0001
    A0001 | 00001_0002

    Thank you very much!

    Mehmet

    Yes, you can build members shared using generations. In my view, there is a sample of the file and of the rule of the load in the base sample

  • Essbase do not move members but creates rather shared members

    Suddenly, this problem appeared for the November statement. I've never met before.

    Updated structures from flat files using rule Essbase files do not move members to their new parents but creates rather shared members.
    Previously, Essbase moved members.

    In the rules file, we have the 'Allow moves' disabled option because some shared members need to be created. If we choose this no shared members are created since Essbase moves key members at the locations of where the shared members are supposed to be.

    Any help would be appreciated.

    That's why you need two sources of metadata:
    (1) only members. Linking to a modified charge rule allowing movements.
    (2) only members with their shared summaries. Use the same rule of ancient office which does not allow for movements and thus pushing them towards a shared hierarchy.

    I still wonder how it still worked. Something changed - what is it?

    Kind regards

    Cameron Lackpour

  • Do we need to re - create data load rules if we move from EBS 11 to 12?

    If so, please explain why. Thank you.

    If you switch from EBS 11-12 of the EBS, you need to create a new entry in the source system in ERPi.

    Once the new source system is created, you then need to initialize the source system in ERPi.

    From there, you need to associate it with a format of import and localities in ERPI and your data load rules are then based on location.

  • Multiple hierarchies with shared members

    Hello

    is it just a common practice to have single parents for hierarchies that are built on the same size of Essbase, or it is a restriction of system-level?
    Only in Hyperion Planning, or this is true also on Essbase level?

    Is it true that only the terminal nodes can be shared members?

    (automatic shared members are created on levels higher for parents with 1 child, then why the other shared not allowed?)

    Thank you for your answer!

    I'm not sure I follow your question completely, but for running sums of shared member, the lowest level of the rollup shared can be one zero level or upper limb or from another dimension. The condition is that a shared member can not have descendants in the shared rollup, it would be the level low.
    For example if I have the cumulative following primer

    Geography
    East
    NJ
    NY
    PA
    West
    It
    OR
    WA

    I have a cumulative alternamte as

    Total of Bob
    NY (shared)
    West (shared)

    You see thar NY is a level zero member and the West is a member of level 1, but under the cumulative replacement are both level zero members

  • When exporting data to essbase with L0 members, shared members are also get exported.

    Hi, when exporting data to essbase with L0 members, shared members are also get exported.

    But I don't want to export another hierarchy!

    Example:

    project

    XYZ +.

    ABCD +.

    P00001 +.

    p00002 +.

    GFE +.

    p00003 +.

    p00004 +.

    all the xyz (Label only)

    ABCD (shared member)

    EFG (shared member)

    I want data to be exported only with P00001, 2, 3, 4.

    I think that the OP cannot use Level0 in DATAEXPORTOPTIONS, because not all dimensions are zero-level.

    Cameron, thanks - Yes, it's the behavior of the OP is seen (and disliking).  The share of 'level zero' which is in fact not level zero (in the primary hierarchy) is included in the output.  I think it's the problem rather than replication / repetition.

  • EAS 11: Rule of load is not using 32-bit ODBC Driver

    Hi all

    Problem: I want to build a Dimension with a rule of the load. Load rule gets data from an Access database then I mounted a 32-bit ODBC connection on a Win 2003 64 bit server. Essbase 64 Bit is only looking at the connection ODBC 64 bits-so, how do I use the 32 ODBC connection or ist there a 64-bit - ODBC-driver for MS Access?

    Thx for your help and brgds,

    Maik

    I don't think that there is a 64-bit Access ODBC driver.

    See you soon

    John
    http://John-Goodwin.blogspot.com/

  • ASO load rule error

    Hello

    I need help from you all to get this hierarchy in a cube ASO. Dimension entity type is supposed to be "multiple hierarchies enabled.

    ! Entity! Alias entity! O H!
    Entity! ABC! Alias ABC! + !
    ABC! DIV0! Alias DIV0! + !
    DIV0! DVT12! Alias DIV12! + !
    Entity! NotFound! ~ O !
    NotFound! E9! TMS! ~ !

    Here are the errors I get...


    + \\Record #5 - error adding the Label attributes only to Member NotFound (3320) +.
    Entity! NotFound! ~ O!!!!!
    + \\Outline of verification errors: +.
    + E9 \\Member has an incorrect aggregation operator. Contours of global storage require all members of hierarchies stored to have add (+) aggregation, with the exception of the single label members and their children.
    + \\Member NotFound has an incorrect aggregation operator. Contours of global storage require all members of hierarchies stored to have add (+) aggregation, with the exception of the single label members and their children.

    I tried to change the properties of Member in various ways, but the same mistakes arise. The hierarchy is AS-IS from an existing schema that validates correctly. I don't understand why it fails through loading rules.

    Please, share your ideas.

    Thanks to you all

    My man in California helped me (much) with that the construction of the part of the dimension of it, then maybe Glenns should get points. :)

    Giving credit where it is most certainly due:
    (1) and it's the strawberry that Glenn talked to me and I yes I should remembered sound will have KScope - you cannot load a don't-be-in-Essbase dimension with the first line of the dimension as the cornerstone. Instead, go to EAS and the rule of the load, then Options, then the Dimension definition, and then click rules daughter type "entity". You have now defined a dimension. Now right-click on the word entity and select "Edit properties". Scroll down and you can select several activated hierarchy. Interestingly, once the entity is responsible, this selection in the rule of the load goes because of course that entity is now in the hierarchy and you can build is more in the rule file. Remove the dimension and the ability to define the entity dimension in the rules file is back.
    (2) this worked for me:
    Entity! ABC! Alias ABC! +
    ABC! DIV0! Alias DIV0! +
    DIV0! DVT12! Alias DIV12! +
    Entity! Not found! ~ O
    Not found! E9! TMS! ~
    (3) the State of data load was Parent/child for the hierarchy of entities and fairly simple.

    Kind regards

    Cameron Lackpour

  • Member not found when loading data with SQL

    Hello everyone:

    I created a cube map extract all information with SQL statements and it works perfectly. Now I'm trying to load data in the same way, but I can't.

    I created a view that returns data in this format:

    Dimension 1 < tab > axis 2 < tab > member... Member of dimension 5 < tab > measure 1 < tab > 2 < tab > measure 3

    I designed a new rule, indicating for each column in the dimension; and for each measure which specific member of dimension of accounts must be used. I have check and everything is ok, but when I try to load data, it does not work and tells me error:

    + "Data value [3.5] met before that all the selected Dimensions, [1] Records duly filled.
    + Essbase error unexpected 1003007 "+"

    If I get the names of the members with quotes (because they contain spaces, and it is perhaps the reason for the previous error, although the rule analysis correctly) with the SQL statement, when Essbase import, it deletes these quotes. I must use another symbol, and as a rule change this another symbol quotes. Is this normal? I know that this issue when importing formulas, but not here.

    Why in 'Dimension building' I don't have this problem with quotes?

    And when changing the symbols of quotes, this error occurs:

    + "Member x not found in the database" +. " But I check the Member and there are in general terms. What's wrong with that? »


    Thanks in advance

    Concerning

    Javier

    Published by: Javi M on 26-mar-2011 05:52

    Yes, the SQL files and data (of all kinds) are supported by more than one column of data. As you noted, you just point to the Member that represents the column.

    That said, I bet that if you look at your view/table and load the rule against your outline, I bet you find a dimension be mismapped, for example, you think that this column 4 points to the scenario, but you really repointe it produces and which purported to be the column 1, or you missed a dimension. Happens to me all the time.

    Kind regards

    Cameron Lackpour

Maybe you are looking for