Hyperion Dimension & Member Naming Rules.

Hi
what is Hyperion dimension and member naming rules?
Thanks

When naming applications in Essbase, follow these rules:
● For non-Unicode mode applications and databases, use no more than 8 bytes; for Unicodemode applications and databases, use no more than 30 characters.
● Do not use spaces.
● Do not use these special characters:
❍ asterisks
❍ backslashes
❍ brackets
❍ colons
❍ commas
❍ equal signs
❍ greater than signs
❍ less than signs
❍ periods
❍ plus signs
❍ question marks
❍ quotation marks (double and single)
❍ semicolons
❍ slashes
❍ tabs
❍ vertical bars
● For Planning application names in relational database environments, do not use extended characters (except for underscores).
● For aggregate storage databases, do not use DEFAULT, LOG, METADATA, or TEMP as application names.
Also, avoid use some of the reserve words that smartlist uses:
abstract, assert, boolean, break, byte, case, catch, char, class,
const, continue, default, do, double, else, enum, extends, false,
final, finally, float, for, if, goto, implements, import,
instanceof, int, interface, long, native, new, null, private,
protected, public, return, short, static, strictfp, super, switch,
synchronized, this, throw, throws, transient, true, try, void,
volatile, while.
Or not to use dynamic time series (DTS) codes:
❍ H-T-D: History-to-date
❍ Y-T-D: Year-to-date
❍ S-T-D: Season-to-date
❍ P-T-D: Period-to-date
❍ Q-T-D: Quarter-to-date
❍ M-T-D: Month-to-date
❍ W-T-D: Week-to-date
❍ D-T-D: Day-to-date
When naming dimensions, members, and aliases, follow these rules:
● For non-Unicode mode dimensions, members, or aliases, use no more than 80 bytes. For Unicode-mode dimensions, members, or aliases, use no more than 80 characters.
● Distinguish between upper and lower case only if case sensitivity is enabled.
● Do not use HTML tags in member names, dimension names, aliases, and descriptions.
● Do not use quotation marks, brackets, backslashes, or tabs. Brackets are permitted but not recommended in block storage outlines. They cause errors when converting to aggregate storage outlines.
● To begin dimension or member names, do not use these characters:
❍ at signs
❍ backslashes
❍ brackets
❍ commas
❍ dashes, hyphens, or minus signs
❍ equal signs
❍ less than signs
❍ parentheses
❍ periods
❍ plus signs
❍ quotation marks
❍ underscores
❍ vertical bars
● Do not place spaces at the beginning or end of names. Essbase ignores such spaces.
● Do not use forward slashes in member names.
● For time periods in custom calendars, do not use spaces in prefixes.

Similar Messages

  • Dimension Member Naming Constraints

    SSM Forum,
    Are there any constraints for identifying dimension member names? 
    For example, "No asteriks or semi-colons are allowed, and dimension member names must be less than 20 characters long."
    Thanks a lot,
    Jason

    Jason,
    I am going to suggest a 60 character limit, but certainly encourage fewer characters. An issue here is when displaying in various areas of the interface, especially when building metric sets in Entry and Approval, you may get the member name truncated to fit the available real estate in the interface.
    My recommendation, especially when having similiar member names that are very long, is to place the differentiator at the beginning rather than the end of the name of the name.
    Regards,
    Bob

  • Syntax rules for dimension member?

    What are the rules regarding a dimension member? Is there a character limit? I keep getting an Incorrect Syntax for member error (3305).
    Error log looks like this(I know it's hard to read):
    \\Record #25621 - Incorrect Syntax For Member XTO 20 PIPELINE (USE 707702) UNIT 073919     U073919     XTO 20 PIPELINE (USE 707702) U073919 (3305)
    ETX      '
    65600     '
    EAST TX-OP '
    65600     '
    65600.0001     '
    UNIT 073919     '
    XTO 20" PIPELINE (USE 707702) UNIT 073919     '
    U073919     '
    XTO 20" PIPELINE (USE 707702) U073919'
    ('-designates end of line)

    from the dbag:
    When naming dimensions, members, and aliases in the database outline, follow these rules:
    Use no more than the maximum lengths that are specified in Appendix A, “Limits”.
    Names are not case-sensitive unless case-sensitivity is enabled. See “Setting Outline Properties” in the Essbase Administration Services Online Help.
    Do not use " (quotation marks) or tabs anywhere in a name.
    Do not place spaces at the beginning or end of a name. Analytic Services ignores spaces at the beginning or end of a name.
    Do not use the following characters at the beginning of a name:
    @ at signs
    () parentheses
    \ backslashes
    . periods
    { } braces
    + plus signs
    , commas
    - dashes hyphens, or minus
    _ underscores
    = equal signs
    | vertical bars
    < less than signs
    'single quotation marks
    Do not use the following words as dimension or member names:
    Calculation script commands, operators, and keywords. For a list of commands, see the Technical Reference.
    Report writer commands. For a list of commands, see the Technical Reference.
    Function names and function arguments. For a list of functions, see the Technical Reference.
    Names of other dimensions, members (unless the member is shared), generation names, level names, and aliases in the database.
    Any of the following words:
    Note: If you enable Dynamic Time Series members, do not use the associated generation names—History, Year, Season,
    Period, Quarter, Month, Week, or Day. See “Applying Predefined Generation Names to Dynamic Time Series
    Members” on page 436.
    Any of the following words:
    ALL
    AND
    ASSIGN
    CALC
    CALCMBR
    COPYFORWARD
    CROSSDIM
    CURMBRNAME
    DIM
    DIMNAME
    DIV
    DYNAMIC
    EMPTYPARM
    EQ
    EQOP
    EXCEPT
    EXP
    EXPERROR
    FLOAT
    FUNCTION
    GE
    GEN
    GENRANGE
    GROUP
    GT
    ID
    IDERROR
    INTEGER
    LE
    LEVELRANGE
    LOOPBLOCK
    LOOPPARMS
    LT
    MBR
    MBRNAME
    MBRONLY
    MINUS
    MISSING
    MUL
    MULOP
    NE
    NON
    NONINPUT
    NOT
    OR
    PAREN
    PARENPARM
    PERCENT
    PLUS
    RELOP
    SET
    SKIPBOTH
    SKIPMISSING
    SKIPNONE
    SKIPZERO
    TO
    TOLOCALRATE
    TRAILMISSING
    TRAILSUM
    UMINUS
    UPPER
    VARORXMBR
    XMBRONLY
    $$$UNIVERSE$$$
    #MISSING
    #MI

  • How to migrate dimension member text files from ODI to Hyperion Planning

    Hi
    We are having an issue with ODI that it was not connecting to planning.
    Later with some instructions from oracle, we have tried to set some RMI path in websphere and we tested the RMI connectivity test.
    It was successfully connecting to planning.
    Then we want to test that ODI is connecting to planning or not.
    For this I think if anyone can send the doc relating to dimension member upload thru ODI to hyperion planning using text files, it will be helpful.
    Appreciate if anyone can help us on this.
    Please communicate to [email protected] for doc sending.
    Thanks
    Rajesh Reddy

    Go through His(John's) earlier blogs which very clearly explains how to get connected & keep the ball rolling.
    If you're so scared to use the existing connections, you may want to-
    i) Set up new Master & work repository;
    ii) Do few quick configurations from Topology Manager;
    iii) Create your project, models, Interface;
    Let us know if something isn't still clear.
    - Natesh

  • How to export data from Elimination Value dimension member by HAL HFM adapter?

    Good day!<BR><BR>Is it possible to export HFM 4.0.5 data with HAL from the <Elimination> Value dimension member?<BR><BR>In 3.* versions it wasn't and there is Known Issue in the "HFM 3.* Adapter Read Me" file: "The Hyperion Financial Management Adapter exports data using the <entity currency> Value dimension member. The documentation erroneously states that there is a port available for the Value dimension"<BR>But there is not such point in the same file for HFM 4.0.5 AND there is Value port in the HFM 4.0.5. Adapter.<BR><BR>Thanks!<BR><BR>Regards,<BR>Georgy<BR>

    In the first approch, try to change the exporting parameter type REF TO DATA.
    Try like:
    CLASS lcl_test DEFINITION.
      PUBLIC SECTION.
        DATA: t_mara TYPE HASHED TABLE OF mara WITH UNIQUE KEY matnr.
        METHODS:
          constructor,
          get
            IMPORTING
              if_matnr TYPE matnr
            EXPORTING
              ea_mara  TYPE REF TO data.
    ENDCLASS.                    "lcl_test DEFINITION
    START-OF-SELECTION.
      DATA: lo_test TYPE REF TO lcl_test,
            lr_data TYPE REF TO data.
      FIELD-SYMBOLS: <fa_mara> TYPE ANY,
                     <f_field> TYPE ANY.
      CREATE OBJECT lo_test.
      lo_test->get(
        EXPORTING
          if_matnr = '000000000077000000'   " << Replace Your Material
        IMPORTING
          ea_mara  = lr_data ).
      ASSIGN lr_data->* TO <fa_mara>.
      ASSIGN COMPONENT 'ERSDA' OF STRUCTURE <fa_mara> TO <f_field>.
      <f_field> = space.
      WRITE: 'Done'.
    CLASS lcl_test IMPLEMENTATION.
      METHOD constructor.
        SELECT * INTO TABLE t_mara
               FROM mara
               UP TO 10 ROWS.
      ENDMETHOD.                    "constructor
      METHOD get.
        FIELD-SYMBOLS: <lfs_mara> LIKE LINE OF me->t_mara.
        READ TABLE me->t_mara ASSIGNING <lfs_mara> WITH KEY matnr = if_matnr.
        GET REFERENCE OF <lfs_mara> INTO ea_mara.
      ENDMETHOD.                    "get
    ENDCLASS.                    "lcl_test IMPLEMENTATION
    Regards,
    Naimesh Patel

  • ORA-35563: Multiple values exist for an attribute of this dimension member

    After following the tutorial Building OLAP Cubes I was trying to make a cube with aggregation down to the day instead of down to the month.
    I created a times table pretty similar to the one used in the tutorial:
    CREATE TABLE EVENT_TIMES (
            HOUR_KEY        DATE NOT NULL,
            DAY_ID          VARCHAR2(10),
            DAY_NAME        VARCHAR2(10),
            DAY_END_DATE    DATE,
            DAY_TIME_SPAN   NUMBER,
            MONTH_ID        VARCHAR2(30) NOT NULL,
            MONTH_NAME      VARCHAR2(40),
            MONTH_END_DATE  DATE,
            MONTH_TIME_SPAN NUMBER,
            YEAR_ID         VARCHAR2(30) NOT NULL,
            YEAR_NAME       VARCHAR2(40),
            YEAR_END_DATE   DATE,
            YEAR_TIME_SPAN  NUMBER
    As you can see, instead of a DAY_KEY like in the tutorial, I now use an HOUR_KEY.
    This is a sample of the data I inserted in this table:
    select to_char(hour_key,'YYYYMMDDHH24MISS'),DAY_ID,DAY_NAME,DAY_END_DATE,DAY_TIME_SPAN,MONTH_ID,MONTH_NAME,MONTH_END_DATE,MONTH_TIME_SPAN,YEAR_ID,YEAR_NAME,YEAR_END_DATE,YEAR_TIME_SPAN from event_times;
    TO_CHAR(HOUR_KEY,'YYYYMMDDHH24MISS') DAY_ID     DAY_NAME   DAY_END_DATE DAY_TIME_SPAN MONTH_ID                       MONTH_NAME                               MONTH_END_DATE MONTH_TIME_SPAN YEAR_ID                        YEAR_NAME                                YEAR_END_DATE YEAR_TIME_SPAN
    20140104050000                       Y2014M1D4  Y2014M1D4  04-JAN-14                1 Y2014M1                        Y2014M1                                  31-JAN-14                   31 Y2014                          Y2014                                    31-DEC-14                365
    20140104060000                       Y2014M1D4  Y2014M1D4  04-JAN-14                1 Y2014M1                        Y2014M1                                  31-JAN-14                   31 Y2014                          Y2014                                    31-DEC-14                365
    I then created my TIME dimension with DAY as the lowest level.
    When I try the maintain cube option it fails at the 'LOAD NO SYNCH' step with the rejected records having an error message that says:
    ORA-35563: (XSRWLD17) Multiple values exist for an attribute of this dimension member.
    To me, this is a very cryptic message and the only explanation I find online is:
    Cause
    Multiple source table rows containing different values for a dimension attribute were found. Only the first of the multiple rows has been loaded.
    Action
    Fix the mapping or remove the rows with conflicting attribute values..
    This confuses me. In the tutorial the lowest level was day and the TIMES table contained 1 record for each day.
    In my example, the lowest level is hour and the TIMES table contains 1 record for each hour.
    Which attribute has multiple values? And which values?
    The rejected records (101) are not very clear:
    ALIAS_1 = 'MONTH_Y2014M1' AND ALIAS_3 = to_date('31JAN14') AND ALIAS_4 = 31 AND ALIAS_5 = 'Y2014M1' AND ALIAS_6 = 'Y2014M1' AND ALIAS_7 = 'YEAR_Y2014'
    If anyone can help point me in the right direction, it would be greatly appreciated.

    I have seen this recently. The issue is with the dimension load itself.  You have a hour level record table but the rules relating to hierarchy/attribute values etc are checked/reinforced during the load and this error comes up sometimes.
    I would guess that the issue seems to be with your month level information present in the higher level month columns. There are many records corresponding to a single month in ur case, month of Y2014M1. Information relating to Month level member Jan 2014 or member MONTH_Y2014M1 is present in these records: 31 (days) *24 (hours) = 744 records. The data in these 744 records for columns - MONTH_ID, MONTH_NAME, MONTH_END_DATE, MONTH_TIME_SPAN need to be exactly the same in order for the single member MONTH_Y2014M1 to have month attributes loaded with valid values.
    For e.g: if records #1 to #743 contain month_timespan=31 but for some unknown reason record #744 contains month_timespan=30 then this error will come up. OLAP does not know which value to load (31 or 30), and only 1 value can be loaded onto the month level member corresponding to month Y2014M1.
    A quick check of the data should give you the answer. Typically there may be some mistake/invalid assumptions made with the boundary records (in your case, check for values for records corresponding to hour=0 or hour=23/24) which is causing the issue.
    HTH
    Shankar

  • Validation: more than one Other Source Dimension Member

    Hi BPC Experts,
    Is it possible to identify more than one Other Source Dimension Member in Validation Business Rules settings? For example, we need to use all DataSources that belong to IFRS roll up. If yes, what is the format?
    Thanks.
    Mila

    Resolved. The format is DIMENSION=MEMBER OR DIMENSION=MEMBER.
    For example,
    C_DATASRC=MJ_MANJE OR C_DATASRC=GAAP_03 OR LOB_IFRS=TEST OR LOB_IFRS=IFRS_INSD.

  • Dimension Member

    Hi All,
    I am having an issue with one dimension member which is not accepting any data from the dataform. So if the users try to submit a number it just goes back to zero. I tried copying data from another member and that works but if I try to again delete/update the number it again doesn't happen. I also check the property of the dimension member and it is no different from other dimension members.
    The application is on Hyperion Planning 9.3.0.1.
    Thanks in advance,
    Amol

    From the DBAG
    Understanding Implied Sharing
    The shared member property defines a shared data relationship explicitly. Some members are shared even if you do not explicitly set them as shared. These members are said to be implied shared members.
    Essbase assumes (or implies) a shared member relationship in the following situations:
    A parent has only one child.
    A parent has only one child that consolidates to the parent.

  • How to get the ID of a dimension member in script logic?

    Hi everybody,
    I am working in some logic scripts and I wonder if exists any option to get the current member ID of a dimension in order to concatenate a string using the member referred and an additional set of caracters such as: MEMBER_ID&"_ccccc".
    Moreover, I would like to use this ID dimension member in order to filter members of another dimension whose attribute is equal to the ID of the desired member. Is it feasible?
    In conclusion, is it possible to get a variable which is referred to a member ID of a dimension, and using it in order to filtering other dimensions?
    Many thanks in advance,
    Antonio

    Hi Antonio,
    You ask if it is possible compare a dimension id with a property value.. yes it is posible , for doing that you will have to do something like this,
    *FOR %ACC1%=ThisA,ThisB,ThisC
          *WHEN DIMENSION.PROPERTY=%ACC1%
                  *REC(............)
           *ENDWHEN
    *NEXT
    if you want to concatenate using a filter theres a posibility, like this example using the time dimension.
    *xdim_memberset time=%year%.jan -
    >2011.jan
    hope it helps

  • Error: Invalid dimension member with special character / in BPC NW 7.5 SP7

    Hi experts,
    We are encountering the following problem in our Financial Planning application.
    We are migrating our existing BPC solution from one server to another through backup and restore. The existing solution was on BPC NW 7.5 SP 5. The profit_centre dimension in the existing solutions has several member ids with special character '/' (forward slash). The dimension never threw an error when processed in the existing solution and there is planning transactional data against these member ids.
    While the entire configration , appset , files were successfully restored through UJBR on the new system (BPC 7.5 SP7) through UJBR (backup and restore), the masterdata could not be restored only for this Profit_centre (masterdata for other dimensions were processed successfullu). All the member ids with / are rejected for this dimension. The same error is thrown if processed through the admin client from the member sheet. 
    Error: Dimension member PC_FF/WS/NT is an invalid member ID
              Error in Admin module
    Is there any setting which need to be made to allow / character in member ids? Any suggestion to get around this problem would be much appreciated.
    Thanks
    Abhiman

    Hi Abhiman,
    Yes, you need to maintain the transformation file to correct all dimension member IDs. Can you please refer to the following link with a similar issue:
    conversion file formula not working
    Hope this helps.
    Rgds,
    Poonam

  • How to tag attribute member with standard dimension member in EIS

    hi,
    would any one please help me how to tag attribute member with standard dimension member in EIS
    THANK U IN ADVANCE

    In your OLAP model, view columns for the base dimension table. Go into the column properties and for the columns that have Attribute values highlight them and click the Attribute button.
    Go into Metadata Model and those fields will be available to drag into your outline as attribute members.
    Once in the outline, go into the properties of the attribute and assign the level of the base dimension they associate with.

  • Reading data from a text file into PAS - Dimension member names truncated

    Hi,
    I created a procedure to dump variables and data into a text file to load into another model. I used a semicolon as a field seperator.
    The data, measures and dimension members are dumped properly into a text file and no dimension member names are truncated .
    However when I read the data into  a measure, and I issue a peek command, dimension meber names are read in truncated
    and remain full names in the text file. Any reason for this? What do I need to do to prevent this from happening?
    THanks.
    Lungile

    Hi Lungile,
    The problem that you're likely having is that you haven't created a file description for the file from which you're reading.  When loading data into Application Server from a text file, you would normally go through three steps:
    1. Enter the ACCESS EXTERNAL subsystem
    2. Specify the name of the file to be read
    3. Specify the format of the file field names, types, widths, and positions.
    If you go into the Application Server help, select "Application Server Help", then "Application Server at the command level", then "Variables and reading in data", and then "Reading an external file", you will have the process of the steps you need to follow outlined for you, including links to the help topic for each command you need to issue.
    So what I think you need to do is use the DESCRIPTION command to specify the names of your fields, their type, and also their width, in order to ensure no truncation of data on the load.
    The same DESCRIPTION statement is required if you want to use your text file as the source of a dimension.
    Hope this helps,
    Robert

  • Error selecting a dimension member in BPC EPM report - The given key was not present in the dictionary

    Hi,
    We are currently running SAP BPC 10.1 NW on Hana
    Version:
    CPMBPC  810 SP 4
    SAP_BW  740 SP 9
    HANABPC 810 SP 4
    EPM Excel Add-in 10 SP 21 .NET 4 build 9094.
    On my embedded model. I have a BEX query on a aggregation level which I access in a report using the EPM Add-in Excel .
    When I edit my report in EPM Add-in Excel , and I try to select the dimension members for a selected dimension member, I get the following error.
    "The given key was not present in the dictionary"
    Any assistance to help resolve the problem will be appreciated.
    Regards
    Gavin

    Hi Shrikant,
    I had a look at MBR_SEQ , it is a attribute on the dimension member in BW , this relates to a past version of BPC 7.5. We are currently on BPC 10.1 Embedded model , and the MBR_SEQ does not exist on any of the characteristics I have in my info cube.
    When I create a web report I am able to access the dimension members using the select dimensions options, the problem seems to be on the EPM Add-in Excel client only.
    Thanks
    Gavin

  • Moving a parent in a Dimension using a rules file

    I would like too move a parent in one of my dimensions to the bottom of that Dimension using a rule file
    Please advise

    I have a confusion over here. For instance:
    If I have Margin (parent) Sales (child) and COGS (child) defined in the data source in that order, than how will I change it to sales, cogs and than margin in the data source.
    Parent child build method has the following statndard format, if i am not wrong:
    PARENT (say accounts) DIMENSION NAME (code say A10001) ALIAS (Margin) AGGREGATION (+) and DATA STORAGE (The code for store)
    Thanks in advance

  • Why to open Block only with Dense dimension Member ???

    Hi All,
    I want to understand the logic behind opening the block with dense member. Generally we open the block with member of dense dimension by fixing the sparse members
    e.g. below considering C1, P1,Working,Actual are members of sparse dimension customer, product, Version, Scenario.
    Fix(C1,P1,Working,Actual)
    Jan
    IF(Some condition)
    Calculation on Account Member
    ENDIF
    Now if i change the code as below making Jan in FIX and opening the block with Actual. How it will affect the performance. The Number of iterations in total number of datacells will be same in bothe cases above and below then why to give priority to dense dimension member for opening the block.
    Fix(C1,P1,Working,Jan)
    Actual
    IF(Some condition)
    Calculation on Account Member
    ENDIF
    ENDFIX
    I know the logic behind keeping sparse dimension member in FIX but here i think keeping 'Actual' member for opening the block is also a type of fix which will tell the code to do the calculation only for blocks of 'Actual'.
    In 1st case i have fixed the number of blocks containing members C1,P1,Working,Actual and by keeping Jan for opening block means Jan is also fixed for the particular application means code will not run for feb march etc.
    Means code will run for C1->P1->Working>Actual->Jan
    In 2nd case also i have fixed C1,P1,Working,Jan and by keeping Actual for opening block means Actual is also fixed for the particular application means code will not run for other members of Scenarion dimension.
    Means code will run for C1->P1->Working>Jan->Actual
    Then what is the difference??? Why it will effect performance???

    when using an IF statement in a calc script you have to specify a member to associate it with for the calc member block. This is like temporarily assigning it to that member as a formula in the outline. In most cases calculations on dense dimensions can work faster as the block is in memory. Remember that a block statement can have multiple calculation statements in it. When this occurs, having the calculations on a dense member can speed it up as it may not have to swap blocks to do the calculation.
    Also consider that if a sparse combination of members does not exist, the block will not exist and there will be no attempt to do the calculations. If a sparse member is on the calc member block, it will cycle through all of the sparse members looking to do the calculation.

Maybe you are looking for

  • Regarding PR and PO Creation - updation of PO in PR in Status tab

    I have created a PR , initially in PR in Item details in status tab Processing status is N Not edited after block id empty screen. Then after creation PR creation i created PO with reference to that PR and i kept that PO in hold and i checked the PR

  • 2wire and airport extreme

    I have a 2wire modem for att uverse, and I want to turn it into simply a modem only so I can use a airport extreme base station. I talked to a "tier 2" tech support rep at u-verse who said there is no way to do it, and that the 2wire router has no br

  • What is the best case for the iPhone 5c

    What is the best iPhone 5c case?

  • How to start over in lightroom?

    I really have never learned how to maximize this program and normally use Adobe Bridge and Photoshop for my workflow.  I have imported over 100,000 photos in lightroom over time.  I would like to know how to wipe the slate clean so I can start over. 

  • VerifyError: Error #1063: Argument count mismatch on mx.core::RSLItem(). Expected 1, got 3.

    Im getting the following error when trying to run my application, which was migrated from 3.5 to 3.6A: VerifyError: Error #1063: Argument count mismatch on mx.core::RSLItem(). Expected 1, got 3. The original application was built with Flash Builder 4