Manage Day Level in BPC Dimension

Hi Experts,
Need your external point of view and analysis,
A client need to manage their Gross Sales at Day Level.
we though to manage this in a specific model , by using  a standard Time Dimension , and then a User defined Dimension to manage the day level by using generic day.
With this way of working, we could avoid duplicating 365 day split by year, considering that the calendar should be managed by transactional data to,for example, take in consideration bixestil year or calendar day offset between years, using EVCOM function to make dynamic description.
What should be your recommandations ?
Tks a lot,

Try this:
1) Select "Month" in your Column Selector.
2) Now go to Criteria mode. The "Month" column from the Column Selector should be there. Click on the Column Properties of the column and set Value Interaction to "No Interaction."
3) Save your report.
4) Go back to Results tab and re-select your "default" column in the column selector and Save report again.
Edited by: David_T on May 17, 2010 12:03 PM

Similar Messages

  • Need idea on how to implement this - repeating monthly data on day level

    Hi all, i had run into the following thing, this may soung easy, but i'm searching for the best solution:
    i have a dataset per the stores of the customer, the dataset is an asset count on the end of the specific month. I must not sum the data between two/N months.
    We they need to do several querries like
    sales/assets/day
    Sales/itemgroup/asset/day
    sales/salesperson/asset/day
    etc.
    My problem is that i have this data on a month&store level, but i need to provide a solution, so it could be handled as a "global" value on that, so they can query it "almost any ways".
    I don't really want to generate day/other level data based on this, so any tricks, how to repeat the data in all lines for that specific month on presentation/Business level?
    All ideas are welcome.
    Thanks&Regards,
    D
    Edited by: user8113564 on 2012.09.11. 4:52

    Sorry if I took this wrong but are you try to do level based measured
    Take the same physical column in the fact and have one aggregated at a month level and the other at a day level.
    If yes, make sure you build a date dimension hierarchy and mapped at the correct level to the fact. Then take your measure and correctly define them at the correct level, day, month etc
    This should sort it out

  • Why does OWB 9.2 generate UK's on higher levels of a dimension?

    When you specify levels in a dimension, OWB 9.2 generates unique key constraints in the table properties for every level, but only the UK on the lowest level is visible in the configuration properties. Why then are these higher level UK's generated? Is this a half baked attempt to implement the possiblility to generate a snow flake model in OWB?
    Jaap.

    Piotr, Roald and others,
    This is indeed a topic we spend a lot of our time on these past months. We are addressing this as (in my old days I had the same problem as a consultant) we know that this is a common problem.
    So the solution is one that goes in 2 directions:
    - Snowflake support
    - Advanced dimension data loading
    Snowflake is obvious, may not be desired for various reasons but we will start supporting this and loading data for it in mapping.
    If you want a star table, you will know that a completely flattened table with day at the lowest level will not be able to get you a unique entry for month. So what people tend to do is one of the following:
    - Proclaim the first of the month the Month entry point (this stays closest to the star table and simply relies on semantics on both ETL and query side).
    - Create extra day level entries which simbolize the month, so you have a day level with extra entries
    - Create views, extra tables etc to cover the extra data
    - Create a data set within the tables that solves the key problem
    We have opted for the last one. What you need to do for this is a set of records that uniquely identify any record in any level. Then you add a key which links to the dimension at the same point (a dimension key), so all facts always use this surrogate key to link (makes life in query tools easier).
    For a time dimension you will have a set of day records with their months etc in them (the regular star). Then you add a set of records with NULL in the day having months and up. And you go up the hierarchy. For this we will have the ETL logic (in other words you as a designer do not worry about this!). On the query tool you must be a little cautious on counts but this is doable and minor.
    As you can see none of the solutions are completely transparent, but we believe this is one that solves a lot of problems and gives you the best of all worlds. We will also support the same data structure in the OLAP dimensions for the database as well in the relational dimension. NOTE that there are some disclaimers with this as we are doing software here...
    In principal however we will solve your problem.
    Hope this explains some of our plans in this area.
    Jean-Pierre

  • Naming of top level in a dimension

    Hi,
    I was wondering if the naming of the top level in a dimension. Earlier I have just named the top levels whatever suited me the best, and haven't had any problems with that. A couple of days ago I came a across an article on Mark Rittmans weblog where it said that Discoverer and BI beans expect a total level.
    Should all the top levels be named total_***** ?
    What is the consequence of not naming them total_****?
    Anyone have any thoughts on this?
    Regards Ragnar

    Level names can be reused across dimensions. This is common. For example, detail level data is very often shared across levels. When is comes to summary levels, you need decide whether this makes sense. Consider two hierarchies:
    Shipping Hierarchy, with levels:
    Total Product
    Region Shipments
    Country Shipments
    Warehouse
    Item
    Product Type hierarchy, with levels:
    Total Product
    Brand
    Group
    Item
    In the above case, Total Product in each hierarchy should yield the same values because it is the aggregation of all items. So, you might decide that is ok. A different case might not be ok. Consider:
    Shipping Hierarchy, with levels:
    Total Product
    Region Shipments
    Country Shipments
    Warehouse
    Items shipped
    Product Type hierarchy, with levels:
    Total Product
    Brand
    Group
    Items sold
    Since Items Shipped and Items Sold are likely to have different values, the aggregation of each level will yield a different value. In this case, Total Product as the top of each hierarchy doesn't make sense.
    A different twist would be (note the display names):
    Shipping Hierarchy, with levels:
    Total Shipments with 'Total Product' as display name
    Region Shipments
    Country Shipments
    Warehouse
    Items shipped
    Product Type hierarchy, with levels:
    Total Product Types with 'Total Product' as display name
    Brand
    Group
    Items sold
    In this case there will be different levels with different values, but the user will see each as 'Total Product'. Only your user community can tell you if this is want they want.

  • Creating sublevels under levels for a dimension in AWM Oracle 10g

    In Analytic Workspace Manager Oracle 10g, How can I create more sublevels under a particular level in a dimension?
    for eg. Year is a dimension.It has 2 levels , Quarter and Month.
    Under Quarter level I want to have Qtr1 and Qtr2 as sublevels.
    Under Month level I want to have Jan,Feb,Mar,Apr,May,June as sublevels.
    so that Qtr1 has Jan,Feb,Mar, and Qtr2 has Apr,May,June

    You need to do this in your source table.
    The source table can look something like this
    qtr_id, qtr_name, month_id, month_name
    1 , Qtr1 , 101 , january
    1 , Qtr1 , 102 , febuary
    1 , Qtr1 , 103 , march
    2 , Qtr2 , 104 , april
    2 , Qtr2 , 105 , may
    2 , Qtr2 , 106 , june
    Then map it to the dimension, and maintain it.
    Keep in mind that the member(id) fields need to be unique. I.E january 2007 and january 2006 cannot have the same id.
    Ragnar

  • Authentication on local SQL Server 2008 R2 Express server fails after Lan Manager authentication level changed to "Send NTLMv2 response only\refuse LM & NTLM"

    I'm upgrading my organisation's Active Directory environment and I've created a replica of our environment in a test lab.
    One medium-priority application uses a SQL server express installation on the same server that the application itself sits on.
    The application itself recently broke after I changed the following setting in group policy:
    "Send LM & NTLM - use NTLMv2 session security if negotiated"
    to
    "Send NTLMv2 response only\refuse LM & NTLM"
    The main intent was to determine which applications will break if any - I was very surprised when troubleshooting this particular application to find that the issue was actually with SQL Server express itself.
    The errors I get are as follows (note that there are hundreds of them, all the same two):
    Log Name:      Application
     Source:        MSSQL$SQLEXPRESS
     Date:          1/19/2015 2:53:28 PM
     Event ID:      18452
     Task Category: Logon
     Level:         Information
     Keywords:      Classic,Audit Failure
     User:          N/A
     Computer:      APP1.test.dev
     Description:
     Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 127.0.0.1]
     Event Xml:
     <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
       <System>
         <Provider Name="MSSQL$SQLEXPRESS" />
         <EventID Qualifiers="49152">18452</EventID>
         <Level>0</Level>
         <Task>4</Task>
         <Keywords>0x90000000000000</Keywords>
         <TimeCreated SystemTime="2015-01-19T22:53:28.000000000Z" />
         <EventRecordID>37088</EventRecordID>
         <Channel>Application</Channel>
         <Computer>APP1.test.dev</Computer>
         <Security />
       </System>
       <EventData>
         <Data> [CLIENT: 127.0.0.1]</Data>
         <Binary>144800000E00000017000000570053004C004400430054004D00540052004D0053005C00530051004C0045005800500052004500530053000000070000006D00610073007400650072000000</Binary>
       </EventData>
     </Event>
    Log Name:      Application
     Source:        MSSQL$SQLEXPRESS
     Date:          1/19/2015 2:53:29 PM
     Event ID:      17806
     Task Category: Logon
     Level:         Error
     Keywords:      Classic
     User:          N/A
     Computer:      APP1.test.dev
     Description:
     SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure.  [CLIENT:
    127.0.0.1].
    Event Xml:
     <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
       <System>
         <Provider Name="MSSQL$SQLEXPRESS" />
         <EventID Qualifiers="49152">17806</EventID>
         <Level>2</Level>
         <Task>4</Task>
         <Keywords>0x80000000000000</Keywords>
         <TimeCreated SystemTime="2015-01-19T22:53:29.000000000Z" />
         <EventRecordID>37089</EventRecordID>
         <Channel>Application</Channel>
         <Computer>APP1.test.dev</Computer>
         <Security />
       </System>
       <EventData>
         <Data>8009030c</Data>
         <Data>14</Data>
         <Data>AcceptSecurityContext failed. The Windows error code indicates the cause of failure.</Data>
         <Data> [CLIENT: 127.0.0.1]</Data>
         <Binary>8E4500001400000017000000570053004C004400430054004D00540052004D0053005C00530051004C004500580050005200450053005300000000000000</Binary>
       </EventData>
     </Event>
    All of the documentation that I have followed suggests that the errors are caused by incorrect SPN configuration- I figured that they were never correct and it has always failed over to NTLM in the test environment (I can't look at production - we couldn't
    replicate the setup due to special hardware and also RAM considerations), but only NTLMv2 has issues.
    So I spent some time troubleshooting this.  We have a 2003 forest/domain functional level, so our service accounts can't automatically register the SPN.  I delegated the write/read service principle name ACEs in Active Directory.  SQL Server
    confirms that it is able to register the SPN.
    So next I researched more into what is needed for Kerberos to work, and it seems that Kerberos is not used when authenticating with a resource on the same computer:
    http://msdn.microsoft.com/en-us/library/ms191153.aspx
    In any scenario that the correct username is supplied, "Local connections use NTLM, remote connections use Kerberos".  So the above errors are not Kerberos (since it is a local connection it will use NTLM).  It makes sense I guess - since
    it worked in the past when LM/NTLM were allowed, I don't see how changing the Lan Manager settings would affect Kerberos.
    So I guess my question is:
    What can I do to fix this? It looks like the SQL server is misconfigured for NTLMv2 (I really doubt it's a problem with the protocol itself...).  I have reset the SQL service or the server a number of times.  Also - all of my other SQL applications
    in the environment work.  This specific case where the application is authenticating to a local SQL installation is where I get the failure - works with LAN Manager authentication set to "Send LM & NTLM - use NTLMv2 session security if negotiated",
    but not "Send NTLMv2 response only\refuse LM & NTLM".
    Note also - this behaviour is identical whether I set the Lan Manager authentication level at the domain or domain controller level in Active Directory - I did initially figure I had set up some kind of mismatch where neither would agree on the authentication
    protocol to use but this isn't the case.

    Maybe your application doesn't support "Send NTLMv2 response only. Refuse LM & NTLM".
    https://support.software.dell.com/zh-cn/foglight/kb/133971

  • How to create a custom measure for each level of a dimension

    Hi all!
    Can Anyone please explain me with an example, how to create a custom measure for each level for a dimension? I dont mine if you use
    one or more measures.
    thanks in advance
    hope someone helps me.

    For example:I create a dimension for product_dim witch has 4 levels:total, class, family and item:
    d_aben18
    n1_aben18
    n2_aben18
    n3_aben18
    n4_aben18
    herarchy:h_aben18
    cube:cubo_aben18
    measure:med_aben18
    I create this code to fetch the data to the dimension:
    TRAP ON CLEANUP
    SQL DECLARE c1 CURSOR FOR SELECT-
    total_product_id,1,'N1_ABEN18',total_product_dsc,-
    class_id,1,'N2_ABEN18',total_product_id,class_dsc,-
    family_id,1,'N3_ABEN18', class_id, family_dsc,-
    item_id,1,'N4_ABEN18',family_id,item_dsc-
    FROM PRODUCT_DIM
    "OPEN THE CURSOR
    SQL OPEN c1
    "FETCH THE DATA
    SQL FETCH c1 LOOP INTO-
    :APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N1_aben18_LEVELDEF,:D_ABEN18_long_description,-
    :APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N2_aben18_LEVELDEF,:D_ABEN18_parentrel,-
    :D_ABEN18_long_description,-
    :APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N3_aben18_LEVELDEF,:D_ABEN18_parentrel,-
    :D_ABEN18_long_description,-
    :APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N4_aben18_LEVELDEF,:D_ABEN18_parentrel,-
    :D_ABEN18_long_description,-
    "SAVE THE CHANGES
    UPDATE
    COMMIT
    CLEANUP:
    SQL CLOSE c1
    SHOW 'KK2'
    Then I create a cube with use compression off, and in rules sum for example.
    After, I create a measure and I select Override the aggregation specification for the cube, in rules I put nonadditive and I would like to create aprogram to assign distinct values to each level of the dimension. For example, I put 1, 2 3, and 4 values, but at the end I would like to put count(distinct(values)).
    for that I create another program:
    VRB D_RETURN DECIMAL
    if D_ABEN18_N1_ABEN18_LEVELDEF eq 'N1_ABEN18'
    then D_RETURN = 1
    if D_ABEN18_N2_ABEN18_LEVELDEF eq 'N2_ABEN18'
    then D_RETURN = 2
    if D_ABEN18_N3_ABEN18_LEVELDEF eq 'N3_ABEN18'
    then D_RETURN = 3
    if D_ABEN18_N4_ABEN18_LEVELDEF eq 'N4_ABEN18'
    then D_RETURN = 4
    else d_return=26
    return d_return
    "SHOW D_RETURN
    cubo_aben18_med_aben18_stored=d_return
    but it doesnt work.I dont know how to put to assign or to see what I want.
    I report the measure, or I report the program, but then how can I see the values of the measure?
    thanks in advance

  • Mapping the Fact table to different levels of a dimension

    Hi,
    I have a fact table which stores the data for 4 levels of the dimensions. The aggregation method was taken care by PL/SQL and the fact table will have the data for all the 4 levels. When im trying to map all the levels to a column in the fact table using the OEM, it is generating the F KEY constraints referncing the columns mapped for the various levels of the dimension.
    The problem is that im using a denormalised table for maintaing the values of the dimension. So the columns mapped for the levels(Except for the lowest) can't have the unique key defined on it. The cube is not getting created because of the error in creating the F KEY.
    Can u please suggest how to map this fact table.
    Thnks,
    Manohar Vanama

    I am not exactly clear on your schema but I believe you are trying to map tables which are not strict star or snowflake. This means that you cannot use CWM1 (and OEM), unless you change the structure of the tables. You might be able to map the tables with CWM2. The document below will assist you:
    Oracle9i OLAP User's Guide
    Chapter 4. Designing Your Database for OLAP
    Chapter 5. Creating OLAP Catalog Metadata

  • Batch Management @ Plant level in ECC 6.0

    Hi,
        I want activate the Batch Management @ Plant level in ECC 6.0 and when select the Plant level and save it , i am getting the information error like " THIS Type of conversion is not Yet Activated" .
    So i needs to activat @ plant level , what i needs to do for further.........
    Thanks & Regards

    Defining Batch Level
    Use
    This transaction enables you to set the batch level for batch management. Three unique options for a material are available:
    u2022     At plant level
    u2022     At material level
    u2022     At client level
    Prerequisites
    If the material or client level for a material is chosen, check that no materials exist in stock. If a material exists in stock, the level may not be changeable.
    IMG Menu     Logistics - General >  Batch Management > Specify Batch Level and Activate Status Management
    Transaction Cod >> OMCE

  • Does ago function works at day level in obiee 11g

    Hi,
    I want to know does AGO function works well at day level in Obiee 11.1.1.6 .
    Edited by: user12635494 on May 8, 2012 2:58 AM

    Yes, it will work. Just double click the Time level (say year/month/week), mark it as a chronological key (on keys tab). Use that in your AGO function

  • Network security:LAN manager authentication level setting on GPO

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

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

  • Managing "Access Levels" on a domain level from Lync 2010 client

    Hello,
    Our company moved from Office Communicator 2007 R2 clients to Lync 2010 clients.
    Previously in Office Communicator 2007 R2 client, it was possible to set default Access Levels for complete domains (instead of individual users only), using the Access Level Management view.
    In the Lync 2010 this options seems to be missing. The management options per user are still there (by right-clicking a user), but the access to manage it for a domain is no longer visible.
    Is there any way to manage Access Levels for domains, in a similar way we had in Communicator 2007? It appears that Lync 2010 stilluses the Access Levels set previously for domains, but users do no longer have any possibility to make further updates,
    and are stuck (from their perspective at least) with the settings made in 2007 before.
    Thanks.

    Lync 2010 doesn’t have the feature natively.
    With Lync Server 2010, by default, the contacts from federated domains are added as External Contacts.
    Lisa Zheng
    TechNet Community Support

  • How to Enable Week Level Planning instead of Day Level with ATPM

    Hello Experts,
    We've a requirement wherein, we would like to do Week Level Planning instead of Day Level.
    But as soon as, we remove CALDAY from the DSO/aggregation level, the planning layout doesn't get rendered.
    Hence we need to always add CALDAY in Planning DSO and Aggregation level.
    How can we get rid of this?
    We are on BW SP7.4 SP6.
    It would be great, if you can share your expert opinion on this.
    Thanks & regards,
    Jomy

    Hello Experts,
    I was able to figure out how can we enable the week level planning. There are some more finer aspects which needs to be flushed out but atleast I can see that planning is possible on Week Level.
    Thanks & regards,
    Jomy

  • Listing attributes of a particular level in a dimension via API call

    Hi,
    We are using the Oracle OLAP Java api's to browse the metadata and contents of an OLAP schema. We need to be able to access an api that lists just the Attributes that are mapped to a particular Level within a dimension.
    Note the following snippet of code can be added to the OLAP Java examples. This displays a list of key value pairs. The keys are the unique level identifier in the form "HIERARCHY::LEVEL::ID", the value is the contents of the specified attribute. The result would be suitable for input to a combo box control in a JSP or similar.
    public static void getFilters(String dimension, String hierarchy, String level, String attribute) throws Exception {
    MdmPrimaryDimension mdmDimension = getMdmPrimaryDimension(dimension);
    MdmHierarchy mdmHierarchy = getContext().getHierarchyByName(mdmDimension, hierarchy);
    MdmLevel mdmLevel = getContext().getLevelByName((MdmLevelHierarchy) mdmHierarchy, level);
    MdmAttribute mdmAttribute = getContext().getAttributeByName( mdmDimension, attribute);
    StringSource levelSource = (StringSource)mdmLevel.getSource();
    StringSource attributeSource = (StringSource)mdmAttribute.getSource();
    Source querySource = attributeSource.join(levelSource);
    try {
    prepareAndCommit();
    getContext().displayResult(querySource);
    } catch (oracle.olapi.data.source.UnmatchedInputsException e) {
    System.out.println("UNMATCHED ID's " + e.getUnmatchedInputIDs());
    Prior to calling this we need a way of prompting the user to select the appropriate attribute to display in the value field of the list. We can get the full list of attributes for the Dimension with the following code snippet:
    MdmPrimaryDimension mdmDimension = getMdmPrimaryDimension(dimension);
    List attributes = mdmDimension.getAttributes();
    However calling the code below returns an empty attribute list.
    MdmPrimaryDimension mdmDimension = getMdmPrimaryDimension(dimension);
    MdmHierarchy mdmHierarchy = getContext().getHierarchyByName(mdmDimension, hierarchy);
    MdmLevel mdmLevel = getContext().getLevelByName((MdmLevelHierarchy) mdmHierarchy, level);
    List attributes = mdmLevel.getAttributes();
    What api's can we call that would let us list just the attributes mapped to the Level in question?
    Any help is appreciated.
    Regards,
    Ed

    <LINK (<IDESCENDANTS (PutMemberNameHere) AND <DIMBOTTOM (PutDimNameHere)

  • Integration BPC-BW: BPC Dimensions = CHAR 20

    Hi,
    When creating BPC dimensions, by default they are created as CHAR 20 info objects. This could give problems when loading from a BPC cube to a BW cube having info-objects with less number of characters ...
    - I presume this cannot be changed (but confirmation is always nice to know)
    - Did anyone already came accross this problem and how did you solve it
    - Is there a way to insert a validation in BPC that the length of an ID of a dimension member should not exceed a certain length when creating these members manually in BPC ...
    I know the situation above will be rather be exceptional, but we have a case where we faced this issue ... Anyone has a best practise for this
    D

    Hi Dries,
    Oddly enough we came across the same issue yesteday when loading WBS elements from the regular Info Object into a BPC dim.  To prevent issues on the front-end we normally add pre-fixes to Dim Members to ensure all members are unique e.g. WBS_ for WBS elements.  Unfortunately the WBS elements can be up-to 18 characters long in our ECC system.
    Unfortuantely I don't have a solution in this case which makes this response pretty useless, we took the risk that no WBS Elements would ever be identical to other Dim Members in the same Application i.e. removed the pre-fix.  Push comes to shove we could have used W_ or W, but if a longer WBS comes along we'd be stuffed.
    Our BW developer was wondering whether we could manually change the 20 character limit without impacting any functionality elsewhere.  Has anyone tried this?
    Cheers
    Stuart

Maybe you are looking for