Problem in sorting Detail Level of hierarchy

Hi,
I have a Calendar table having calendar_dmk as a primary key. (Month is stored as a first day of a month).
---Calendar_DMK------Date(dd/mm/yyyy)-------Calendar_Month---------Calendar_Year
----------1111111--------------------12/01/1997----------------01/01/1997----------------------1997---------
----------1111112--------------------13/01/1997----------------01/01/1997----------------------1997---------
----------1111113--------------------14/01/1997----------------01/01/1997----------------------1997---------
----------1111145--------------------21/02/1997----------------01/02/1997----------------------1997---------
I have created a logical column *"Month Name"* in BMM layer as monthname(Calendar.Calendar_Month) which extracts month from the calendar table. I have created another column *"Month"* as month(Calendar.Calendar_Month).
I have created Hierarchy following way....
Calendar_Year_Dim
|
|*Calendar Total*
|--Year contains Year as (key=Year and Drill Down = "Year")
|--------Month Contains Month and Monthname (pk="Month+Year" and drill down= "Month Name")
|--------------Day contains Calendar_dmk and date (pk = Calendar_dmk and drill down=date)
I have created one request in pivot table where I have taken "Month" in column area. When I drill down on Month, the data comes datewise, but date is not sorted. (I have set sort order property of Date column to calendar_dmk)
Is there anything I'm missing?

Make date the first column in pivot.

Similar Messages

  • WAD Problem: data below 6th level of Hierarchy is not displaying.

    Hello Experts,
    I am executing a template in the portal and while giving selections for particular 'cost element' in the selection screen, the message is coming saying no records available.
    There are 9 levels of hierarchy and up to 6 levels the data is coming properly but for the remaining three levels the data is not coming although records are present for the other three levels as well. While the same query with same selection is working fine in RSRT/ Analyzer.
    Please help me out.
    I am new to WAD also please let me know if there is any settings for dispalying hier. node in WAD.
    Thanks in advance.

    If you just want to display the Hierarchy Level (not filter or sort by it), try just turning on the display of the attribute on the query and/or report, instead of making it a navigational attribute.
    Hope this helps...
    Bob

  • Problem with Sorting Detail Records

    Hello All,
    I have an ODBC connection to our AS400 System and I am able to retrieve records in Crystal. I am trying to perform a sort on the Cost Center field and then on the Salaries Account field. These two fields are Alpha Numeric fields. I went to the Record Sort Expert and selected these two fields. However,the Salaries Account field does not sort. When I do Browse data for the Salaries Account (field 2) it is in Ascending Order. When the report prints the detail records within each cost center (the primary sort) the Salaries accounts do not appear sequentially. For example account 510110 appears before 510105. I do not understand why the Salaries Account would not sort?
    I appreciate you input as to why this could be happening and how  I could resolve this? I have exhausted evey thing I could think of but I just cant' get it to sort. You input is much appreicated.
    thanks in advance.
    Imty.

    Hi Abhiash,
    I don't see any dashes. The Cost Center sorts fine and is also Alphanumeric. The accounts are 6 digits. When I do Browse Data they appear in ascending order. So, It baffles me why it would be out of sequence when the detail prints out. See output below. Account 510110 appears before account 510105. This is in the account group view.
    THIS IS BY COST CENTER AND ACCOUNT GROUPING  *********
    11002001     510100     LEE,DONNA R     01/29/2012
    Sub Total     510100          
    11002001     510110     BEKKAIR,RADIA     01/29/2012
    11002001     510110     BROWN,JILLEE S     01/29/2012
    11002001     510110     SASPA,MADONNA T     01/29/2012
    11002001     510110     THOMPSON,LISA Y     01/29/2012
    11002001     510110     VAIL,SHEENA M     01/29/2012
    11002001     510110     VANG,CHEN T     01/29/2012
    Sub Total     510110          
    11002001     510105     COURTRIGHT,EMILY E     01/29/2012
    11002001     510105     HUMPHRIES,CHRISTINA L     01/29/2012
    11002001     510105     KALIFA-MAMAE,SILEPA T     01/29/2012
    11002001     510105     MARTIN,KATHRYN M     01/29/2012
    11002001     510105     MEYER,TRACY L     01/29/2012
    11002001     510105     RODRIGUEZ,MICHELLE     01/29/2012
    11002001     510105     SEXTON,JASMINE N     01/29/2012
    11002001     510105     WILLARD,LISA     01/29/2012
    Sub Total     510105          
    "Total11002001
    THESE ARE THE DETAIL RECORDS. YOU CAN SEE  CENTER 510110 APPEARS BEFORE 510105 EVEN THOUGH I HAVE
    SPECIFIED COST CENTER AND SALARIES ACCOUNT IN THE RECORD SORT *******
    11002001     510100     LEE,DONNA R
    11002001     510110     BEKKAIR,RADIA
    11002001     510110     BROWN,JILLEE S
    11002001     510110     SASPA,MADONNA T
    11002001     510110     THOMPSON,LISA Y
    11002001     510110     VAIL,SHEENA M
    11002001     510110     VANG,CHEN T
    11002001     510105     COURTRIGHT,EMILY E
    11002001     510105     HUMPHRIES,CHRISTINA L
    11002001     510105     KALIFA-MAMAE,SILEPA T
    11002001     510105     MARTIN,KATHRYN M
    11002001     510105     MEYER,TRACY L
    11002001     510105     RODRIGUEZ,MICHELLE
    11002001     510105     SEXTON,JASMINE N
    11002001     510105     WILLARD,LISA

  • Navigating from detail level column in an hierarchy  to another report

    I have a requirement as folllows:
    In one report,i have a drill-down feature enabled on "TIME DIM".
    At The detail level of this dimension is "DAY" column.
    SO,from this detail level,when i click on "DAY" column, navigation should be done to another report..
    Is it possible to navigate so from detail report..
    pls let me know the solution for this requirement..
    thanks,
    seeusass

    Instead of Drill down,Give Navigation in first report to child report.But for this you need to create n reports if you are having n number of levels in hierarchy.Then at the detail level report you can give navigation at day level.
    Thanks
    Don

  • Custom Drill from the last level of Hierarchy

    I have a dimension hierarchy STAGE which has five levels L1 -> L2 -> L3 -> L4 -> L5
    and my fact table have 5 measure columns say M1 , M2 , M3 , M4 , M5 along with the dimension columns .
    My requiremetn is to show only the top level hierarchy and one measure column initially:
    L1 -- M1
    now user have to drill from L1 to L5
    L1 L2 M1
    L1 L2L3-- M1
    L1 L2L3--L4-- M1
    L1 L2L3--L4--L5-- M1
    by default when the user comes at the last level of hierarchy or the hyperlink to drill futrter gets disabled.
    Now my requirement is to show the detail report when the user comes at the last level and the there should be a link on it. when the user will clink on the last level link it should open below report :
    L1 L2L3--L4--L5--D1--D2--D3--D4--D5--M1--M2--M3--M4--M5
    D1-D5 are other dimension columns which are connected to Fact Table.
    Any suggestions??

    Abhiiiiiii wrote:
    Navigation is also a problem here since the column is coming coming runtime(after drill).What i told u is to use the navigation option insted of drill. So you need to create five reports each one for the particular hierarchy. and set the navigartion target as next level report in the hierarchy. Yes it is not the optiumum solution. But if you dont want the other two solutions given above you need to go with this only.

  • OBIEE BI Answers: Wrong Aggregation Measures on top level of hierarchy

    Hi to all,
    I have following problem. I hope to be clear in my English because it's a bit complicated to explain.
    I have following fact table:
    Drug Id Ordered Quantity
    1 9
    2 4
    1 3
    2 2
    and following Drug Table:
    Drug Brand Id Brand Description Drug Active Ingredient Id Drug Active Ingredient Description
    1 Aulin 1 Nimesulide
    2 Asprina 2 Acetilsalicilico
    In AWM i've defined a Drug Dimension based on following hierarchy: Drug Active Ingredient (parent) - Drug Brand Description (leaf) mapped as:
    Drug Active Ingredient = Drug Active Ingredient Id of my Drug Table (LONG DESCRIPTION Attribute=Drug Active Ingredient Description)
    Drug Brand Description = Drug Brand Id of my Drug Table (LONG DESCRIPTION Attribute = Drug Brand Description)
    Indeed in my cube I've mapped leaf level Drug Brand Description = Drug Id of my fact table. In AWM Drug Dimension is mapped as Sum Aggregation Operator
    If I select on Answers Drug Active Ingredient (parent of my hierarchy) and Ordered Quantity I see following result
    Drug Active Ingredient Description Ordered Quantity
    Acetilsalicilico 24
    Nimesulide 12
    indeed of correct values
    Drug Active Ingredient Description Ordered Quantity
    Acetilsalicilico 12
    Nimesulide 6
    EXACTLY the double!!!!!!! But if I drill down Drug Active Ingredient Description Acetilsalicilico I see correctly:
    Drug Active Ingredient Description Drug Brand Description Ordered Quantity
    Acetilsalicilico
    - Aspirina 12
    Total 12
    Wrong Aggregation is only on top level of hierarchy. Aggregation on lower level of hierarchy is correct. Maybe Answers sum also Total Row????? Why?????
    I'm frustrated. I beg your help, please!!!!!!!!
    Giancarlo

    Hi,
    in NQSConfig.ini I can't find Cache Section. I post all file. Tell me what I must change. I know your patient is quite at limit!!!!!!! But I'm a new user of OBIEE.
    # NQSConfig.INI
    # Copyright (c) 1997-2006 Oracle Corporation, All rights reserved
    # INI file parser rules are:
    # If values are in literals, digits or _, they can be
    # given as such. If values contain characters other than
    # literals, digits or _, values must be given in quotes.
    # Repository Section
    # Repositories are defined as logical repository name - file name
    # pairs. ODBC drivers use logical repository name defined in this
    # section.
    # All repositories must reside in OracleBI\server\Repository
    # directory, where OracleBI is the directory in which the Oracle BI
    # Server software is installed.
    [ REPOSITORY ]
    #Star     =     samplesales.rpd, DEFAULT;
    Star = Step3.rpd, DEFAULT;
    # Query Result Cache Section
    [ CACHE ]
    ENABLE     =     YES;
    // A comma separated list of <directory maxSize> pair(s)
    // e.g. DATA_STORAGE_PATHS = "d:\OracleBIData\nQSCache" 500 MB;
    DATA_STORAGE_PATHS     =     "C:\OracleBIData\cache" 500 MB;
    MAX_ROWS_PER_CACHE_ENTRY = 100000; // 0 is unlimited size
    MAX_CACHE_ENTRY_SIZE = 1 MB;
    MAX_CACHE_ENTRIES = 1000;
    POPULATE_AGGREGATE_ROLLUP_HITS = NO;
    USE_ADVANCED_HIT_DETECTION = NO;
    MAX_SUBEXPR_SEARCH_DEPTH = 7;
    // Cluster-aware cache
    // GLOBAL_CACHE_STORAGE_PATH = "<directory name>" SIZE;
    // MAX_GLOBAL_CACHE_ENTRIES = 1000;
    // CACHE_POLL_SECONDS = 300;
    // CLUSTER_AWARE_CACHE_LOGGING = NO;
    # General Section
    # Contains general server default parameters, including localization
    # and internationalization, temporary space and memory allocation,
    # and other default parameters used to determine how data is returned
    # from the server to a client.
    [ GENERAL ]
    // Localization/Internationalization parameters.
    LOCALE     =     "Italian";
    SORT_ORDER_LOCALE     =     "Italian";
    SORT_TYPE = "binary";
    // Case sensitivity should be set to match the remote
    // target database.
    CASE_SENSITIVE_CHARACTER_COMPARISON = OFF ;
    // SQLServer65 sorts nulls first, whereas Oracle sorts
    // nulls last. This ini file property should conform to
    // that of the remote target database, if there is a
    // single remote database. Otherwise, choose the order
    // that matches the predominant database (i.e. on the
    // basis of data volume, frequency of access, sort
    // performance, network bandwidth).
    NULL_VALUES_SORT_FIRST = OFF;
    DATE_TIME_DISPLAY_FORMAT = "yyyy/mm/dd hh:mi:ss" ;
    DATE_DISPLAY_FORMAT = "yyyy/mm/dd" ;
    TIME_DISPLAY_FORMAT = "hh:mi:ss" ;
    // Temporary space, memory, and resource allocation
    // parameters.
    // You may use KB, MB for memory size.
    WORK_DIRECTORY_PATHS     =     "C:\OracleBIData\tmp";
    SORT_MEMORY_SIZE = 4 MB ;
    SORT_BUFFER_INCREMENT_SIZE = 256 KB ;
    VIRTUAL_TABLE_PAGE_SIZE = 128 KB ;
    // Analytics Server will return all month and day names as three
    // letter abbreviations (e.g., "Jan", "Feb", "Sat", "Sun").
    // To use complete names, set the following values to YES.
    USE_LONG_MONTH_NAMES = NO;
    USE_LONG_DAY_NAMES = NO;
    UPPERCASE_USERNAME_FOR_INITBLOCK = NO ; // default is no
    // Aggregate Persistence defaults
    // The prefix must be between 1 and 8 characters long
    // and should not have any special characters ('_' is allowed).
    AGGREGATE_PREFIX = "SA_" ;
    # Security Section
    # Legal value for DEFAULT_PRIVILEGES are:
    # NONE READ
    [ SECURITY ]
    DEFAULT_PRIVILEGES = READ;
    PROJECT_INACCESSIBLE_COLUMN_AS_NULL     =     NO;
    MINIMUM_PASSWORD_LENGTH     =     0;
    #IGNORE_LDAP_PWD_EXPIRY_WARNING = NO; // default is no.
    #SSL=NO;
    #SSL_CERTIFICATE_FILE="servercert.pem";
    #SSL_PRIVATE_KEY_FILE="serverkey.pem";
    #SSL_PK_PASSPHRASE_FILE="serverpwd.txt";
    #SSL_PK_PASSPHRASE_PROGRAM="sitepwd.exe";
    #SSL_VERIFY_PEER=NO;
    #SSL_CA_CERTIFICATE_DIR="CACertDIR";
    #SSL_CA_CERTIFICATE_FILE="CACertFile";
    #SSL_TRUSTED_PEER_DNS="";
    #SSL_CERT_VERIFICATION_DEPTH=9;
    #SSL_CIPHER_LIST="";
    # There are 3 types of authentication. The default is NQS
    # You can select only one of them
    #----- 1 -----
    #AUTHENTICATION_TYPE = NQS; // optional and default
    #----- 2 -----
    #AUTHENTICATION_TYPE = DATABASE;
    # [ DATABASE ]
    # DATABASE = "some_data_base";
    #----- 3 -----
    #AUTHENTICATION_TYPE = BYPASS_NQS;
    # Server Section
    [ SERVER ]
    SERVER_NAME = Oracle_BI_Server ;
    READ_ONLY_MODE = NO;     // default is "NO". That is, repositories can be edited online.
    MAX_SESSION_LIMIT = 2000 ;
    MAX_REQUEST_PER_SESSION_LIMIT = 500 ;
    SERVER_THREAD_RANGE = 40-100;
    SERVER_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
    DB_GATEWAY_THREAD_RANGE = 40-200;
    DB_GATEWAY_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
    MAX_EXPANDED_SUBQUERY_PREDICATES = 8192; // default is 8192
    MAX_QUERY_PLAN_CACHE_ENTRIES = 1024; // default is 1024
    MAX_DRILLDOWN_INFO_CACHE_ENTRIES = 1024; // default is 1024
    MAX_DRILLDOWN_QUERY_CACHE_ENTRIES = 1024; // default is 1024
    INIT_BLOCK_CACHE_ENTRIES = 20; // default is 20
    CLIENT_MGMT_THREADS_MAX = 5; // default is 5
    # The port number specified with RPC_SERVICE_OR_PORT will NOT be considered if
    # a port number is specified in SERVER_HOSTNAME_OR_IP_ADDRESSES.
    RPC_SERVICE_OR_PORT = 9703; // default is 9703
    # If port is not specified with a host name or IP in the following option, the port
    # number specified at RPC_SERVICE_OR_PORT will be considered.
    # When port number is specified, it will override the one specified with
    # RPC_SERVICE_OR_PORT.
    SERVER_HOSTNAME_OR_IP_ADDRESSES = "ALLNICS"; # Example: "hostname" or "hostname":port
    # or "IP1","IP2":port or
    # "hostname":port,"IP":port2.
    # Note: When this option is active,
    # CLUSTER_PARTICIPANT should be set to NO.
    ENABLE_DB_HINTS = YES; // default is yes
    PREVENT_DIVIDE_BY_ZERO = YES;
    CLUSTER_PARTICIPANT = NO; # If this is set to "YES", comment out
    # SERVER_HOSTNAME_OR_IP_ADDRESSES. No specific NIC support
    # for the cluster participant yet.
    // Following required if CLUSTER_PARTICIPANT = YES
    #REPOSITORY_PUBLISHING_DIRECTORY = "<dirname>";
    #REQUIRE_PUBLISHING_DIRECTORY = YES; // Don't join cluster if directory not accessible
    DISCONNECTED = NO;
    AUTOMATIC_RESTART = YES;
    # Dynamic Library Section
    # The dynamic libraries specified in this section
    # are categorized by the CLI they support.
    [ DB_DYNAMIC_LIBRARY ]
    ODBC200 = nqsdbgatewayodbc;
    ODBC350 = nqsdbgatewayodbc35;
    OCI7 = nqsdbgatewayoci7;
    OCI8 = nqsdbgatewayoci8;
    OCI8i = nqsdbgatewayoci8i;
    OCI10g = nqsdbgatewayoci10g;
    DB2CLI = nqsdbgatewaydb2cli;
    DB2CLI35 = nqsdbgatewaydb2cli35;
    NQSXML = nqsdbgatewayxml;
    XMLA = nqsdbgatewayxmla;
    ESSBASE = nqsdbgatewayessbasecapi;
    # User Log Section
    # The user log NQQuery.log is kept in the server\log directory. It logs
    # activity about queries when enabled for a user. Entries can be
    # viewed using a text editor or the nQLogViewer executable.
    [ USER_LOG ]
    USER_LOG_FILE_SIZE = 10 MB; // default size
    CODE_PAGE = "UTF8"; // ANSI, UTF8, 1252, etc.
    # Usage Tracking Section
    # Collect usage statistics on each logical query submitted to the
    # server.
    [ USAGE_TRACKING ]
    ENABLE = NO;
    //==============================================================================
    // Parameters used for writing data to a flat file (i.e. DIRECT_INSERT = NO).
    STORAGE_DIRECTORY = "<full directory path>";
    CHECKPOINT_INTERVAL_MINUTES = 5;
    FILE_ROLLOVER_INTERVAL_MINUTES = 30;
    CODE_PAGE = "ANSI"; // ANSI, UTF8, 1252, etc.
    //==============================================================================
    DIRECT_INSERT = YES;
    //==============================================================================
    // Parameters used for inserting data into a table (i.e. DIRECT_INSERT = YES).
    PHYSICAL_TABLE_NAME = "<Database>"."<Catalog>"."<Schema>"."<Table>" ; // Or "<Database>"."<Schema>"."<Table>" ;
    CONNECTION_POOL = "<Database>"."<Connection Pool>" ;
    BUFFER_SIZE = 10 MB ;
    BUFFER_TIME_LIMIT_SECONDS = 5 ;
    NUM_INSERT_THREADS = 5 ;
    MAX_INSERTS_PER_TRANSACTION = 1 ;
    //==============================================================================
    # Query Optimization Flags
    [ OPTIMIZATION_FLAGS ]
    STRONG_DATETIME_TYPE_CHECKING = ON ;
    # CubeViews Section
    [ CUBE_VIEWS ]
    DISTINCT_COUNT_SUPPORTED = NO ;
    STATISTICAL_FUNCTIONS_SUPPORTED = NO ;
    USE_SCHEMA_NAME = YES ;
    USE_SCHEMA_NAME_FROM_RPD = YES ;
    DEFAULT_SCHEMA_NAME = "ORACLE";
    CUBE_VIEWS_SCHEMA_NAME = "ORACLE";
    LOG_FAILURES = YES ;
    LOG_SUCCESS = NO ;
    LOG_FILE_NAME     =     "C:\OracleBI\server\Log\CubeViews.Log";
    # MDX Member Name Cache Section
    # Cache subsystem for mapping between unique name and caption of
    # members for all SAP/BW cubes in the repository.
    [ MDX_MEMBER_CACHE ]
    // The entry to indicate if the feature is enabled or not, by default it is NO since this only applies to SAP/BW cubes
    ENABLE = NO ;
    // The path to the location where cache will be persisted, only applied to a single location,
    // the number at the end indicates the capacity of the storage. When the feature is enabled,
    // administrator needs to replace the "<full directory path>" with a valid path,
    // e.g. DATA_STORAGE_PATH = "C:\OracleBI\server\Data\Temp\Cache" 500 MB ;
    DATA_STORAGE_PATH     =     "C:\OracleBIData\cache" 500 MB;
    // Maximum disk space allowed for each user;
    MAX_SIZE_PER_USER = 100 MB ;
    // Maximum number of members in a level will be able to be persisted to disk
    MAX_MEMBER_PER_LEVEL = 1000 ;
    // Maximum size for each individual cache entry size
    MAX_CACHE_SIZE = 100 MB ;
    # Oracle Dimension Export Section
    [ ORA_DIM_EXPORT ]
    USE_SCHEMA_NAME_FROM_RPD = YES ; # NO
    DEFAULT_SCHEMA_NAME = "ORACLE";
    ORA_DIM_SCHEMA_NAME = "ORACLE";
    LOGGING = ON ; # OFF, DEBUG
    LOG_FILE_NAME     =     "C:\OracleBI\server\Log\OraDimExp.Log";

  • Directly i am dirlling down to detail level

    hi all
    i am working on multilevel hierarchies ,i have created multilevel hierarchies for calendar_date and fiscal_date but the thing is i am using time series functions so for that i have enabled cronalagical key
    in the levels ,in key option i have selected month_nams as the key for drill down bout once i click on the year it drilling down to detail level,not to year level,
    what is the problem ,i don't under stand why it is drilling down from year to detail level
    Thnks

    Hi,
    Can you tell me the diffrent levels in hierarchy.What is thenext level after year.It should drill down to that level.Make sure than you have not given preferred drill path.Also make sure that you are refering the same column.backtrace the year column.
    Regards,
    Sandeep

  • No Fact table exists at this detail level error

    Hi All,
    I am trying to develop an RPD and was trying to use a simple example of joining two fact tables in OBIEE through confirmed dimension.
    This is my example:
    Fact A: Student ID (FK)......Measure1, Measure2...
    Fact B: Student ID (FK)........Measure A, Measure B
    DIM 1: Student ID (PK),.....
    I would like to give the users the option of joining Fact A and Fact B through Dim 1( Which is a conforming Dimension)
    I tried with out level based hierarchy and got NO Fact exists at this level of detail.
    Then I tried creating the level based hierarchy on Dim 1 and selected the detail level for the fact table and I am still getting the error message.
    Am i doing some thing wrong here ?  Or Am i missing any important setting ?
    Is there a way to check whether the dimension is a conforming dimension or not in OBIEE.
    Your help is much appreciated.
    Thanks
    Venu

    Can we use between operator in physical join. We did that, its successfully checking in, but when we re-open the join, its show in RED color.
    So, got doubt, can we use between?When you checkout the rpd object in online mode it would display in red, this is not an error.
    "No fact table exists at the requested level of detail"; what does this error meanThis error usually happens if you have not mapped the content level correctly in the logical table source.
    Rgds,
    Dpka

  • OBIEE 11g level based hierarchy

    Hi everyone,
    here is my problem in brief
    I made a level based hierarchy for Products, and I need to show the product name beside the product code in the last level in the hierarchy, the steps i made to reach this is as follows:
    1- making the name and the code columns keys in the last level (in business model).
    2- making the name and the code as display columns (in presentation).
    what happens when i do this it shows only one of them depends on the order in the "display column" area
    My OBIEE version is 11.1.1.6
    is it a bug or something ?
    thanks a lot in advance.

    guys I found a work around for this problem, I made a logical column and i used the this expression:
    "ALM"."Dim Product"."LEVEL_16_NAME" || ' - ' || "ALM"."Dim Product"."LEVEL_16_CODE" , these two columns contains the desc. and the code for the product
    and then I made this column as a key and in the display columns.
    it works as i want but still considered a work around.
    thanks anyway :)

  • Help needed - OBIEE - Level Based Hierarchy - Expanding Month for one year affects all previous years

    I am creating a level based hierarchy for the Date Dimension
    year --> quarter --> month --> date (one path)
    year .--> month --> date (the second path).
    I create the pivot table using these dim hierarchies. But the problem is,
    when I click on, say "Month" under year 2012, it expands everything above 2012 (such as 2010, 2011 etc).
    I don't want to expand all the years, but only the one I clicked. Anyone knows what is the solution for that.
    I am sorry that I cannot attach any screen shots to explain better.
    I would really appreciate your help on this.
    Thanks
    JD

    I am using OBIEE 11.1.1.7.0.
    ok, I tried one hierarchy per dim table but didn't work too. When I created a logical column as Month + Year (e.g Jan 2014) and added to the hierarchy, its working fine. But that creates other issues on the
    client side.
    I guess, since the month is common to all the years its expanding when clicked. I also added month and year as "chronological key", but that didn't work either.
    Please advice any solution if you know it.

  • Fixing at aggregate level & unfixing at detailed level.

    Hi,
    Our requirement is as given below......
    Our Demand Planning Process is Top-down process. Head Quarter will enter the demand at Territory, Channel and Product Group Level. These values are fixed and gets disaggregated to further planning level based on historical sales. The further planning levels are Sales Officer, Location & Product. Territory Manager can change the demand with in his targets across Sales officers (i.e. he should be able to change the targets of Sales officers without exceeding or reducing the Territory targets).
    Can anyone suggest how to fix the keyfigures at Aggregate Level without fixing it at detailed level. We tried FIX_CALC macro, but could not resolve the issue.
    Thanks in advance.
    SP

    You need to create AGGREGATES in your PLANNING OBJECT STRUCTURE, right click on POS and create  the following aggregates
    (1) ALL TERRITORY characteristics
    Now you will be able to fix at the top level and still be able to change at the detailed level.
    Read the following:* Let me know if you have any questions*
    Aggregate  
    Definition
    The aggregates in APO are not the same as those in the Business Information Warehouse (BW), but they have the same purpose: to speed up data access and therefore increase performance.  SAP recommends that you use aggregates in Demand Planning.
    These aggregates are sometimes referred to as persistent aggregates, in particular when talking about detail and aggregate levels in interactive planning.
    Use
    An APO aggregate contains a subset of the characteristics in the master planning object structure. The creation and use of aggregates is optional. The data is always saved on the lowest level of detail. If aggregates exist, the system saves the planning data on the defined aggregate levels as well as on the lowest level of detail. The data is saved twice, but consistently; that is, the sum of the details equals the aggregate value.
    SAP recommends that the aggregates you build in APO for planning data also exist in BW for actual data.
    If you want to save fixed values at aggregate level ; that is not at detail level of the master planning object structure, in a planning book, you must create aggregates for this level. Otherwise the data is only saved at detail level.
    You cannot form aggregates for navigational attributes
    See also:
    Fixing Key Figure Values
    Aggregates are discussed in detail in OSS note 503363. SAP recommends that you read this note thoroughly before configuring your master planning object structures and aggregate hierarchy.

  • Getting info of detail level  of a dimension

    I have Oracle EE 10g with appr patch for OLAP option and AWM(10.2.0.3A).
    With the help of awxml.jar I am able to get dimensions,levels,hierarchy,attributes and cubes.
    But could you please suggest me what should I do to get the detail level of a dimension.
    Eg: For my time dimension,I have levels like Year,Qtr,month.
    These I am able to get through the java API.
    But I have to get Under Year 1998,1999,…..
    Under Qtr level I have Qtr1,Qtr2,…….
    Under month level I have Jan ,feb,mar…..
    all of these actually we have mapped to the relational tables.
    how do we get these level of info .
    And also if we have to retrieve the data values,i.e the cube info

    Also consider using the BI Beans components that are specifically designed to work with OLAP data sources. These can be built into any Java or thin client environment and provide pre-built data visualisations such as:
    Crosstab
    Graph
    Dimension lists
    Cascading dimension lists
    Measure lists
    Much depends on the type of application and client you are trying to create. You can get more information on this via the BI Beans home page on OTN.
    http://otn.oracle.com/products/bib/index.html
    Keith Laker
    Oracle EMEA Consulting
    BI Blog: http://oraclebi.blogspot.com/
    DM Blog: http://oracledmt.blogspot.com/
    BI on Oracle: http://www.oracle.com/bi/
    BI on OTN: http://www.oracle.com/technology/products/bi/
    BI Samples: http://www.oracle.com/technology/products/bi/samples/

  • Dimension with Level Dased Hierarchy

    Hi everyone
    I have one table in bussines model called items with columns item_code,item_descr,item_brand,item_category.
    I also have a Dimension with Level Dased Hierarchy set as total_level,item_brand,item_category,item_code.
    Data
    ===
    item_brand 1, item_category 21, item_code code1
    item_brand 2, item_category 21, item_code code2
    In Answer when i use the above hierarchy i have the problem that when i expand item_brand 1 and then item_category 21 automatically answer expand also item_brand 2 showing only item_code code2.
    It happens because item_brand 1,2 have the same item_category 21.
    Is there any way to make it work?
    Thanks
    Hermes
    Edited by: hermes on 24 Μαρ 2011 3:05 πμ

    Hi hermes,
    try this:
    create two physical table with the rows ant import in your Physical Layer:
    DIM_TABLE1
    BRAND CATEGORY
    item_brand 1, item_category 21
    item_brand 2, item_category 21
    And DIM_TABLE2
    BRAND CATEGORY ITEM
    item_brand 1, item_category 21, item_code code1
    item_brand 2, item_category 21, item_code code2
    Define the join like this:
    DIM_TABLE1.BRAND = DIM_TABLE2.BRAND and DIM_TABLE1.CATEGORY = DIM_TABLE2.CATEGORY
    In the Business Model create 1 Logical Table Source for your dimension with the source you two physical table, inner join.
    Now map the logical column.
    I hope it helps.
    Regards,
    Gianluca

  • Detail Level in statistics data

    Hi Experts,
    I came cross recently that there has been a huge data transfer to the infoproviders for statistical data. (0TCT_C01, C02 and others)
    I thought that chaging the level of "Statistical Detail Level" from tr. code RSDDSTAT can be a remedy to the problem.
    I attempt to change the level from all (2) to Aggregated data only (0).
    Do you have any idea what will be affected with this parameter change ?
    Thanks..
    Berna

    Hi Berna,
    The query statistics will be collected at aggregated level rather than detailed level and you can expect to have less number of records flowing into technical content targets.
    Just to have a flavour on how the aggregated stats will look like, you can execute a query in RSRT, in Execute and Debug option with the check box 'collect runtime statistics' ticked.
    You will be get query statistics granular and aggregated in two different tabs.
    Thanks,
    Krishnan

  • Problem with setting Source Level in Sun Studio 2

    I've got problem with setting Source Level to 1.5 in Sun Studio 2. When I try to set it to 1.5 in Project properties and click Ok everything seem to go well, but when I open Project Properties again Source Level is set to 1.4. I need this to work cause I started to lear Java recently and I want to use foreach loop.
    Please help

    I'm just citing an example using Date().
    In fact, whether I use DateFormat or Calendar, it shows the same result.
    When I set the date to 1 Jan 1950 0 hours 0 minutes 0 seconds,
    jdk1.4.2 will always return me 1 Jan 1950 0 hours 10 minutes 0 seconds.
    It works correctly under jdk1.3.1

Maybe you are looking for