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

Similar Messages

  • Alias for dimension member

    How can you create the alias for the actual dimension name / member.
    We have multiple languages and want to be able to translate the dimension name. The dimension alias in EPMA actually gives it the name for the dimension not the alias so how do you set up the alias? Seems silly they named it an alias when it isn't an alias.
    We tried adding the alias in EAS but no luck there.
    We are on version 11.1.2.1

    The dimension alias in EPMA should not be confused with the aliases asociated to the languague alias tables for members. If you look at the epma you will notice that dimension alias is a system property not a planning property. There is no way to associate that system property to your alias tables in planning. when you look at the planning properties for the dimension you will see that there is no way to indicate an alias for a dimension node, because this is not a property for planning at the dimension node level.
    Instead what happens is that when you first deploy an application you can determine whether you want to display/deploy it with the alias as name, or the actual name or both in one or the other order. That is the use of the alias for dimensions for planning. But you cannot have multiple language aliases for the Dimension.
    Agnete

  • Excel *.xls or *.xlsx for dimension sheet format in Admin Console?

    Dear all:
    We are in the process of upgrading BPC 5.1 to 7.0, and I was prompted a message about the Excel format (2007 or 2003) when I first opened up a dimension in Admin Console, after BPC 7.0 was installed.
    My questions are:
    1. What are the pros and cons?
    2. Excel 2003 has the limitation of 65000 rows, so does that mean once I choose 2003 format, my dimension members can only have 65000 limitation? If not, what is the workaround?
    3. If I select Excel 2007 as my default format, and want to switch to Excel 2003, is there a way to do so?
    Thank you very much!
    Sincerely,
    Brian

    Hi Brian Hsu,
    Please refer to the SAP Note below:
    SAP Note 1265872 - Excel 2007 format template supported in Admin console.
    Summary
    Symptom
    Admin console does not support Excel 2007 format in previous versions.
    Other terms
    BPC 7.0 SP2 Microsoft, BPC 7M SP02, Excel 2007 format(xlsx), Admin console, dimension member sheet,
    Reason and Prerequisites
    The previous version of Admin console supported Excel 2003 file format only. Users could not use Excel 2007 file format ('xlsx').
    Solution
    Implemented in 7.0M SP2.
    BPC Administration console will support both Excel 2003 and Excel 2007
    file format for dimension member sheet. And the BPC Administration
    console uses the value of 'MEMBERSHEET_VERSION' in tblDefaults table
    internally to judge which file format is used for dimension member
    sheet. The value can be "2003" or "2007" and be set by selecting the
    value from popup window as below. Once the value is set via the popup
    window, the value cannot be changed, so we recommend reading the below
    explanation for each case first and then setting the value.
      KeyID and Value in tblDefaults;
        - [KeyID]: MEMBERSHEET_VERSION
        - [VALUE]: "2003" OR "2007"
    Below is the behavior of the Excel version when users try to save a
    dimension member sheet to server or process dimension with member sheet;
    1. No record having MEMBERSHEET_VERSION in tblDefaults after installing
    BPC 7M SP2 or later
       a)Excel 2003 users
         - Download 'xls' file and save to server without any message.
       b)Excel 2007 users
         - A popup window for selecting 2003 or 2007 will come up and if
           user selects 2007, a warning message that Excel 2003 users
           cannot usedimension member sheet file anymore will come up once
           again and then the file format will be changed to 'xlsx'
         - Create, Modify, Copy dimension: The file format of the member
           sheet will be 'xls'.
    2. MEMBERSHEET_VERSION=2003
       a)Excel 2003 users
         - Download 'xls' file and save to server as 'xls'
       b)Excel 2007 users
         - Dimension member sheet file will be saved as 2003 file format by
           'SaveAs'
    3. MEMBERSHEET_VERSION=2007
       a)Excel 2003 users
         - User cannot download dimension member sheet file so cannot use
           dimension member sheet any more.
       b)Excel 2007 users
         - Download 'xlsx' file from server and if there is only 'xls', the
           file will be downloaded from server and then it will be changed         to 'xlsx' when save to server.
         - Create dimension: The file format will be 'xlsx'
         - Modify, Copy dimension: The file format will be followed by the
           downloaded file format.
    [Limitation]
    If the value of MEMBERSHEET_VERSION is set to 2007, users who use Office 2003 cannot access and modify dimension member sheet file any more. Only users who use Office 2007 can access and modify dimension member sheet.

  • 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

  • Dimension build rule file (Sort member)

    I am loading sorted data for one of the dimension. But its is not coming in sorted fashion in outline. New member which i am adding is always coming in The end.Even though that member is in sorted format in the file.
    I am using generation method . I am putting member for only generation 2 and its alias.I tried using ascending option but it is giving me error
    Can any body help me with this

    As Glenn said, the build only builds new members. In order to have FULL control over the order of a resultant dimension's order, you need to blank out the dimension first and then build via the load rule. As Glenn mentioned, you can do "incremental dimension building". You can do this directly in EAS in an interactive manner by using outline/update outline in pull downs. Just do not save the outline until all your changes are done. You can also accomplish incremental builds via Esscmd or via MaxL, but I'll assume for right now you are still testing. The advantages of the incremental changes is that you can do a number of changes before Essbase commits to doing a restructure, which is time consuming, not to mention confusing if you are "deleting" (however temporary) the entire dimension's hierarchy.
    Regarding setting ascending order
    1) in the load rule's Dimension Build Settings prompt
    2) Select Dimension Build Settings tab
    3) highlight the dimension you are changing
    4) select Ascending for sort order
    This should work...I've never had it error out. However, I will say that it sorts the entire dimension...not just the siblings of a new member. Your upper level members will move as well. Because of this, the ascending sort in a load rule is undesirable. Give it a try. If you don't like the results, just don't save the outline.
    Kevin

  • 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.

  • How to define an aggregation rule for a dimension based on bridge table?

    Hello,
    I need a solution for aggregating data correctly when using a dimension based on a set of dimensione tables containing a bridge table. Please find below a description of my business case and the OBIEE model which I’ve created thus far.
    Business Case
    The company involved wants to report on the number of support cases, the different types of actions that were taken and the people involved in those actions. One support case will undergo a number of actions (called ‘handelingen’) until it is closed. For each action at least one person is involved performing a specific role, but there can also be multiple persons involved with 1 action, each performing a different role for that action. This is the N : N part of the model.
    The problem that I face is visible in the two pictures below:
    http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/sample.png
    As long as I don’t include anything from the Dimension Meelezer in my report, I get the correct number of handelingen (7). When I include the person (called ‘Meelezer’), the measuere per action is multiplied by the number of persons/roles involved with that action.
    When I changed the Aggregation rule in the report column #Handelingen to ‘Server Complex Aggregate’ I do get the correct endtotal:
    http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/sample2.png
    I believe it should be possible to define in the repository a different aggregation rule for individual dimensions, but I’ve not been able to achieve this.
    Explained below is what I have created in my Physical and Business Model & Mapping layers:
    The Physical Model is built like this:
    (This is just a small part of a much larger physical model, but I’ve only included the most relevant tables)
    http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/PhysicalDiagram-1.png
    The Fact table (ALS Feit Zaakverloop) contains FK’s for the action (FK_HANDELING, joined to ALS Dim Handeling), the date the action took place (FK_DATUM_ZAAKVERLOOP, joined to ALS Dim Datum Zaakverloop) and the uniqe group of people involved (FK_MEELEZERS, joined to ALS Groep Meelezers) and a measure column (SUM_HANDELINGEN) populated with the value ‘1’ for each row.
    The Bridge table (ALS Brug Meelezer/Reden Meelezen) contains three FK’s: FK_GR_MEELEZERS (joined to ALS Groep Meelezers), FK_MEELEZER (joined to ALS Dim Functionaris) and FK_REDEN_MEELEZEN (joined to ALS Dim Reden Meelezen).
    The Business Model
    In the business model, the four physical tables for the N:N relation have been combined into one logical dimension table.
    http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/BusinessModel-1.png
    DIM Meelezer contains one LTS in which the four physical tables have been combined:
    http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/LTS1.png
    And all the required locical columns have been created:
    http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/LTS2.png
    DIM Meelezer has also been identified as a bridge table and a Business Key has been defined on a combination of the FK’s in the bridge table and business codes of the two dimension tables.
    http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/BMDIM.png
    Next a hierachy was created for Dim Meelezer:
    http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/Hier.png
    In Feit Zaakverloop, a measurement called ‘# Handelingen’ was created using SUM_HANDELINGEN, with an aggregation rule of SUM.
    In the LTS of both the DIM Meelezer and Feit Zaakverloop, the Logical Content Levels have both been set to: LVL Detail – Meelezer.
    Please provide suggestions that will NOT require changes to the physical datamodel as they would require too much time to achieve (or at leats would not be ready before my deadline.
    Thanks!
    Edited by: The_Dutchman on Dec 13, 2011 11:43 AM

    Hmm, no replies yet...
    Am I in 'uncharted territory' with this issue?

  • Remove access for each member of a particular dimension from Hyperion Planning Applciation

    We are trying to remove access for groups for each member of a particular dimension( which has more than 1000 members) of a Hyperion Planning application. We are going through Administration->Manage DImensions -> member , Under security click view and select the group and then remove access But the problem is there are more than 1000 members under this dimension , so it will be time consuming to go to each member and then remove access for the group. Is there any other way we can do this?
    Also is there a way to bulk delete native directory groups from Hyperion Shared services, instead of deleting each native group manually one by one?

    The reaso we want to go for Relational tables is that when we did Exportsecurity utility for that planning application  and imported back the SecFile.txt without doing any changes ,still it errored out giving errors like :
    "The following access not imported:-"PLN-ORG-0278-999 Bureau Strtgc & Oprtnl ""PLNning",0278-999,READWRITE,MEMBER due toInvalid user name found in the file."
    It is erroing out even if we did not do any modifications to the secfile.txt.
    Moreover there are more than 1000 members for which we have to remove access permissions manually one by one. It is a tedious process.
    So we are looking at other options like , which relational tables have got Native directory groups information, and the sql queires we can execute to remove the unwanted Native directory groups from Shared Services?

  • Use short description on OLAP dimension member in disco for OLAP

    Hi All,
    I've noticed in the spreadsheet add-in you can decide under "query options" whether to use the Long or Short Description when displaying a dimension member. How do you do the same in discoverer PLUS for OLAP ? I cant find it anwhere.
    Cheers,
    Brandon

    This feature is not available in Disco :-( Logged as an enhancement request.
    Keith

  • Creating UDA for a dimension member

    Hi All,
    when I am creating UDA for a dimension member in my planning application I get the following error.
    The associated dimension ID has not been set for this property. Do you want to create the association now?
    Can anyone please let me knwo wahts this error?
    Thanks

    I take this is an EPMA application, you have to create dimension association between the UDA property and the UDA dimension.
    Have a read of :- http://download.oracle.com/docs/cd/E17236_01/epm.1112/epma_admin/epma_create_assoc.html
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Performance issue:Show id and Description for same dimension member

    Hi,
    I am connecting a cube to another reporting system and i need to show the id of member resulting of a query.My first thought was to use this kind of code (bellow) however when i do the same thing with many dimension (many cross join ),it slow down a lot
    my query.So how can i have in the same DImension member showing a description and id ? I also have a lot of statement,so i can't have just two columns in the dimension or i will need to duplication the mdx and i could drop down the performance.
    So i am trying to get as a result
    Dim1 | Dim2| Dim3| Measure
    1 50
    32 25.2
    and also be able to get
    Dim1                            |   Dim2                                  |  Dim3  
                                |                Measure
    NameElement1Dim1 NameElement50Dim2
    NameElement32Dim3 25.2
    Thanks in advance
    with MEMBER [Measures].[IdElement] as 
    <element>.currentmember.properties("KEY")
    select
    CROSSJOIN({[Measures].[IdElement]},{[METRIC].[Description].[All]}),
    CROSSJOIN({[Measures].[value]},{<listmetricmdx>})
    } on columns,
    <pointofview>
    <element_and_function>
    <TimeBreakdown>
    } on rows
    <list_filter_clause>
    ) as list
    where ((ElementName is null AND IdElement=0) OR (ElementName is not null))
    <list_condition_metric>
    but i have multiple 

    Hi Vincent,
    In your query, you use CrossJoin in it. Crossjoin function will cause the performance issue if there are a lot of properties that need to be displayed. If you cross-join medium-sized or large-sized sets (e.g., sets that contain more than 100 items each),
    you can end up with a result set that contains many thousands of items—enough to seriously impair performance. For the detail information, please see:
    http://sqlmag.com/data-access/cross-join-performance
    In your MDX query, ensure only retrieval the required data. Here are some useful links for your reference.
    Configure memory setting:
    http://social.msdn.microsoft.com/Forums/en/sqlanalysisservices/thread/bf70ca19-5845-403f-a85f-eac77c4495e6
    Performance Tuning:
    http://www.microsoft.com/downloads/details.aspx?FamilyID=3be0488d-e7aa-4078-a050-ae39912d2e43&displaylang=en
    http://www.packtpub.com/article/query-performance-tuning-microsoft-analysis-services-part2
    Regards,
    Charlie Liao
    TechNet Community Support

  • Delete data for a single dimension member

    Is there anyway to delete all the data for a single dimension member from a particular cube?
    olap version: 11.2.0.3

    Nasar's approach should work, so I would use it so long as it performs well. But I have (several years ago) seen performance issues with CLEAR VALUES when it is applied to something smaller than an entire partition. So here is another method that also uses the FOR...BUILD construct. It clears the value of the PRICE measure in PRICE_COST_CUBE for PRODUCT = '48'. The cube has only two dimensions, TIME and PRODUCT, and I only want to assign to the leaf level of TIME, which is MONTH.
    BEGIN
      DBMS_CUBE.BUILD(Q'!
       "PRICE_COST_CUBE" USING(
        FOR
         "TIME" LEVELS ("TIME"."MONTH"),
         "PRODUCT" WHERE "PRODUCT".DIM_KEY = '48'
        BUILD (SET PRICE_COST_CUBE.PRICE = NULL ))!',
        PARALLELISM=>0,
        ADD_DIMENSIONS=>FALSE);
    END;
    /You can increase parallelism here if your cube is partitioned. If you need to clear out other measures at the same time, then add additional SET command in the central block. E.g.
    BUILD
      SET PRICE_COST_CUBE.PRICE = NULL,
      SET PRICE_COST_CUBE.COST = NULL
    )After this step you can re-aggregate the cube to make the aggregate values reflect the change.
    BEGIN
      DBMS_CUBE.BUILD(Q'!
       "PRICE_COST_CUBE" USING(
        FOR
         "TIME" LEVELS ("TIME"."MONTH"),
         "PRODUCT" WHERE "PRODUCT".DIM_KEY = '48'
        BUILD (SET PRICE_COST_CUBE.PRICE = NULL ),
        SOLVE)!',
        PARALLELISM=>0,
        ADD_DIMENSIONS=>FALSE);
    END;
    /The simple assignment to NULL will generate a simple assignment in the OLAP DML.
    PRICE_COST_CUBE_STORED=NAYou can force the code to loop over the existing composite by replacing NULL with something that evaluates to NULL, but involves the composite.
    SET PRICE_COST_CUBEW.PRICE = NVL2(NULL, PRICE_COST_CUBE.PRICE, NULL)Here is the generated OLAP DML assignment.
    PRICE_COST_CUBEW_STORED=NVL2(NA, GLOBAL.GLOBAL!PRICE_COST_CUBEW_PRICE
    , NA)  ACROSS GLOBAL.GLOBAL!PRICE_COST_CUBEW_COMPOSITE

  • How to copy data for certain member from one dimension to another dimension

    Dear ,
    I want to copy data for certain member ("511102") from one dimension to another combinations of dimensions ,
    I have the following combinations for "511102" :
    _("Budget2012","FY12","Working.V01","SAR","BegBalance","1011","G_10","custom Grades")_
    I want to copy "511102"  to "salary"
    -salary have the following dimensions :
    _("Budget2012","FY12","Working.V01","SAR","BegBalance","General group","All grades","General Employees")_
    , I don't know if I could do it by datacopy of cross dimensional , But I don't HOW >>>
    Thanks in advance

    FIX("Budget2012","FY12","Working.V01","SAR","BegBalance","General group","All grades","General Employees")
    "salary"="511102"->"1011"->"G_10"->"custom Grades";
    ENDFIX
    or
    FIX("Budget2012","FY12","Working.V01","SAR","BegBalance")
    DATACOPY "511102"->"1011"->"G_10"->"custom Grades" to "salary"->"General group"->"All grades"->"General Employees";
    ENDFIX
    Key thing in datacopy is to place the dimensions in cross dimension in the same order. Both sides (before and after "TO") should have equal number of dimension members specified.
    Cheers,
    Alp

  • Deleting comments for multiple dimension member selection

    Hi all,
    When using the package (using /CPMB/CLEAR) to delete data and comments (TASK(/CPMB/CLEAR_COMMENTS_FOR_CLEAR,ENABLETASK,1)), there seems to be a problem to delete comments when using a multiple member selection. When selecting <all> or a single dimension member for a given dimension, data and comments are effectively deleted. However, when selecting eg 2 members, the data is deleted, but the comments remain in the comment tables. Any ideas on how to solve this, without running the package x-times when comments on x members need to be deleted?
    Kind Regards,
    Christophe

    Hi,
    I don't know whether your question is answered or not . Please look into the following which may be helpful to you.
    As far as i know u can
    1. Delete Comments selecting " ALL" member selection.
    2. Delete comment selecting " SINGLE MEMBER "  --> _Multiple member selection is not supported in NW._
    Please look into the following SAP Note on this which may be useful to convince the client:
    1372497 - BPC7NW: Behavior of Clear Comments package
    Chaithanya

  • 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.

Maybe you are looking for

  • Left joins : Case or if statement

    Hi I want to know if one can build in a case or if statement into a left join. I want to multiply a value with -1 if the condition is met.

  • MB Colorista renders interlaced in (AME) APP CS4

    Hey everyone, Everytime I apply colorista to a Clip in Adobe Premiere Pro CS4 and render it out with Adobe Media Encoder (Youtube Widescreen HD, H.264) the parts of the video are interlaced although my footage, sequence as well as my render settings

  • Windows XP non networked laptop

    I would allow it. make sure that you get all the service patches youi can for it and get it as up to date as possible. I would also install a different browser just in case it has to hit the internet for something in the future. XP only goes to IE8 a

  • Displays and Macbook

    Can I use an old Cinema HD Display with a MacBook Pro? If so how?

  • HT4061 I have black and white lines on my screen what is up?

    My screen is displaying black and white lines. How do I fix it?