Inactive Dimension Tables for Cube

Hi Gurus ,
           I am transporting a cube from one system to another and the transport fails becasue the dimension tables are in active in the target system. Now since this system is read only I cannot manually activate it , last resort I even trioed opening the system and activating it and re transported the transport. I get the same error saying that table /BIC/ZXXXXX is inactive.
Can anyone help....please....

hi Sanjeev,
did you change any dimensions in dev ?
like delete some characteristics from existing dimension,
or add new characteristic or move from one to another
dimension ?
if so, you may need to delete production data first,
to avoid this, please change back characteristics to previous dimension, and create a new dimension and add new characteristic to the new create dimension.
another possibility is database problem, try to search oss note for infocube dimension inactive.
hope this helps.

Similar Messages

  • Tables for Cube

    Hi guys,
    im trying to activate a cube, but the process fails, saying there was no primary key for the table /BIC/L<CubeName> .
    Now i wonder what kind of table that is. Is there any complete List of tables for Cubes? I know about those:
    /BIC/F<CubeName>      Fact table,
    /BIC/E<CubeName>      compressed Fact table
    /BIC/D<CubeName>T     Time dimension table      
    /BIC/D<CubeName>P     Requenst dimension      
    /BIC/D<CubeName>U     Unit dimension      
    /BIC/D<CubeName>1       User dimension 1 and so on
    /BIC/L<CubeName>     ????
    What is the purpose of table L? Are there any other important tables for the cube?
    cheers...

    Hi,
    This is the validity table. which is /BIC/L(cube name). If u have any non cumulative key figures then a validity table will be created for the same. But am not sure about the error.
    Khaja

  • Table for Cube request

    Hi Experts,
    I would like to know the table in which data load request for cube is stored with records added and transferred and other cube related details. Please help.

    Hi,
    for the request part you can look at the table RSBKREQUEST by filling in the source or target object.
    Different tables for cube are :
    RSDCUBE    Directory of InfoCubes
    RSDCUBET   Texts on InfoCubes 
    RSDCUBEIOBJ    Objects per InfoCube (where-used list) 
    RSDDIME    Directory of Dimensions 
    RSDDIMET   Texts on Dimensions 
    RSDDIMEIOBJ    InfoObjects for each Dimension (Where-Used List) 
    RSDCUBEMULTI    InfoCubes involved in a MultiCube 
    RSDICMULTIIOBJ     MultiProvider: Selection/Identification of InfoObjects 
    RSDICHAPRO     Characteristic Properties Specific to an InfoCube 
    RSDIKYFPRO    Flag Properties Specific to an InfoCube 
    RSDICVALIOBJ    InfoObjects of the Stock Validity Table for the InfoCube 
    thanks,
    arminder

  • Status control table - 'Perform update for status control table for cube '

    Hello Experts,
    While loading data to DSO, I am getting this message - 'Perform update for status control table for cube Z3MLQUA'.
    What is status control table ? and can I have some inputs as to how to solve this issue
    Regards,
    arjun

    Hi,
    This message is not a issue in itself. It is just a SAP message which means that the system is checking/updating the system tables to carry out the operation whether it can be done or not.
    If your loads are failing at this step or after this message there can be many reasons, check some of  the possible reasons below
    Performing check and potential update for status control table
    Update from PSA error in Process Chain
    problem in deleting request
    Reporting not available ,even if Data is sucessfully loaded into DT
    Hope this helps,
    Kush kashyap

  • Change dimension tables for an infocube

    hello all,
    we have an existing cube where a few of the dimension tables are quite big compared to size of fact table.  we understand enough about getting the correct dimension table sizes, our question revolves around the existing cube.
    meaning, when we make the dimension table changes in dev and transport to val, will the transport be successful with data in the cube (so it will be stored in a format of old dimension table structure)?  do we have to dump the cube before transport and then reload after transport successful?
    thanks so much!

    Hi,
    Please check the below link
    Re: Cube Transport issue
    For remodelling,
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID0196158950DB01648128345571943727End?blog=/pub/wlg/5772
    Thanks

  • Table for Cube & ODS count

    Hi Gurus,
    Could you please tell me the name of the tables to find the Total count of
    1) Cubes
    2) ODS
    3) Queries (Report)
    4) No of total users,
    in BW system.
    Thanks
    Nisha

    Hi,
                                 Table name
    No of total users      USR02
    Cubes                     RSRREPDIR
    Queries                   RSRREPDIR
    Hope this helps...

  • How to View master data & Trasaction data tables for Puchasing Cube

    Hi BW masters,
    How should I check which tables (Master data tables and Transaction data tables) are involved with Business Content Cube(Purchasing data 0PUR_C01). I would like to know this information in order to go to that table and browse the data in that table. Where should we go and check this out.
    I will reward the points for the good answers.:-)
    Thanks
    Syed.

    hi Syed,
    to view tables' content you can use SE16,
    you can try infocube name, dimension tables of cube are store in *d[infocube name]1 to F, fact tables are f[infocube name] and e[infocube name]-compress,
    infocube data are stored in star schema, you can use LISTCUBE to view the content (to see the structure/tables in cube, use LISTSCHEMA),
    master data (not time-dependent) are stored in text table t[infoobject name], attribute - p[infoobject name] and hierarchy - h[infoobject name],
    take a look bw multidimensional data modeling for detail
    http://help.sap.com/bp_biv235/BI_EN/documentation/Multi-dimensional_modeling_EN.doc
    hope this helps.

  • Why cube cannot exceed 16 dimension tables?

    hi experts,
    why a cube can't exceed or limited with 16 dimension tables,what is the background or technical specification for this limitation
    what is answer if  i questioned, why you cannot create more than 16 dimension tables for a cube.
    pl help me regarding this
    thanks & regards
    venkat

    Hi,
    It is more related to db level restriction.Since we may not have more  than 16 key fields  in a table so we can not  have more than 16 dim table for cube.Please give a close look the doc below that will help you a lot.
    http://help.sap.com/bp_biv235/BI_EN/documentation/Multi-dimensional_modeling_EN.doc
    Regards.

  • The table for storing data for infocube and ODS

    Hi all:
        could you please tell me how to find the table for storing data for infocube and ODS?
    thank you very much!

    Hi Jingying Sony,
    To find tables for any infoprvider go to SE11.
    In database table field enter the following
    Cube -
    Has fact table and dimension table
    For customized cube - ie cube names not starting with ' 0 '
    Uncompressed Fact table - /BIC/F<infocubename>
    Compressed fact table - /BIC/E<infocubename>
    Dimension table - /BIC/D<infocubename>
    For standard cube - ie cube names  starting with ' 0 '
    Uncompressed Fact table - /BI0/F<infocubename>
    Compressed fact table - /BI0/E<infocubename>
    Dimension table - /BI0/D<infocubename>
    Click on display.
    For DSO,
    For standard DSO active table- /BI0/A<DSO name>00.
    You use 40 for new table.
    Click on display.
    For customized DSO use- /BIC/A<DSO name>00.
    An easier way is in the database table field, write the name of the cube/DSO preceeded and followed by ' * ' sign. Then press F4 . It shall give you the names of the available table for that info provider.
    Double click on the name and choose display.
    Hope this helps,
    Best regards,
    Sunmit.

  • Urgent-Issue in the Dimension tables

    Hi Experts,
    Question1:
    I have a flat file load to a cube.this flat file has 1.5 mil records.One of the dimension created has a 2 dates(original date & current date) assigned.
    When i look at dimension table for # entries is 30million.And when i look at the table i see the sids as 0,0 ( for 2 dates) and dim id's being creted.
    When i did a search on the dimension table with current date & original date as not equal to 0.I see only 76,000 records.
    Question 2:
    we have an ODS which loads to the cube.In the process chain we have program that deletes the data in ods which does not match some conditions and then loads it tot he cube.
    My question is,since we are not deleting contents from the cube and reloading it from the ODS(Full update).Will i not be seeing same records coming in with Full update which get agrregated in the cube.
    Ex: i have a record in ODS.
    A   X  Z  100  1000
    After full update to the cube,the cube would have
    A   X  Z  100  1000
    When i run the process chain and data is dleeted from ODS on some condition and i still have hte same record in ODS and when this loads into cube wont this be aggregated with the previous record.
    A  X   Z  200  2000
    Would appreciate,if anyone could explain if i am missing anything.

    Hello,
    If you can't see the SID means you have not loaded the master data, that why there is no reference to the SID table and the values are 0.
    InfoCube by default will have aggregated values, when there are duplicate records on the Keyfigures will be aggregated.
    For example I have a Material Dimension and Customer Dimension
    In the fact table,  it will be like this
    DIM1     DIM2    KF1   KF2
    Mat001  Cust1  100    10
    Mat001  Cust2  200    5
    for this there will be 1 entry in Material DIM table for Mat001 and 2 entries for Customer DIM table for Customer Cust1 and Cust2.
    Material  Dimension
    DIM ID    SID
    1             Mat001  (Here it will be SID from Material Master)
    Customer Dimension
    1             Cust1  (Here it will be SID from Customer Master)
    2             Cust2  (Here it will be SID from Customer Master)
    Note : DIM ID is the combination of one or more SID in the dimension table.
    So the exact fact table will look like
    MATDIM    CUSDIM       AMT      QTY
    1               1                  100        10
    1               2                  200        5
    If you load the data again with same characteristics values then the key figure will be aggregated
    Example if you load
    Mat001 Cust2 25 5
    then the fact table will not have a new entry instead the it will aggregates and looks like (bolded one)
    MATDIM    CUSDIM       AMT      QTY
    1               1                  100        10
    1               2                  220        10
    Hope its clear
    thanks
    Chandran

  • One Dimension Table Deletion issue

    Dear Guru's
    Query run's very long time to execute in prod system
    In our production system, we have a Cube in which one dimension(Eg:- /BIC/PC_17 which show 38% when i run report SAP_INFOCUBE_DESIGNS  ). Due to the performance issue of the Query, i am thinking to delete data from SE11 only for this dim table...What will happen with the Factable?
    Since Dim table has reference to Factable...Is it correct if i delete the entries for this Dimension table for the perfomance issue?
    PLease suggest me i am very much confused, also this is a prod system....so pls give me only good answers..no gess please...
    Also ....suppose if this Dim17  is not used in Query Does it make sense to delete entries from this Dim 17 for Query performance, since this exist's in cube...
    Thanks in adv,
    Dev

    Hi,
    you should not do that. In no case. There are some ways to speed up a query. Use them: e.g. building aggregates, running rsrv to check the cube and possibly have unused entries of dimensions deleted, compress the cube....
    regards
    Siggi

  • Static and small dimension table should I use lookup

    Hi Gurus,
    I am creating interface to load my fact table.
    Generally for different codes to replace with surrogate keys I use dimension table for look-up in interface.
    but I have question if dimension table is very small and has only static values like
    Sur_key, Code, Description.
    1, C, Create
    2 , R, Redeem
    in such case if in interface for fact table, I just write expression "if source_table.column=C then 1 else 2".
    Please advice if this is better way or not.
    Thanks in advance.

    I agree - it is much better practice to use lookups to populate surrogate keys. Using hard-coded values in code requires the developer to always remember that dependency on dimensional data and can cause unexpected results down the line if the keys are updated or are inconsistent across environments.

  • Reg: Fact table and Dimension table in Data Warehousing -

    Hi Experts,
    I'm not exactly getting the difference between the criteria which decide how to create a Fact table and Dimension table.
    This link http://stackoverflow.com/questions/9362854/database-fact-table-and-dimension-table states :
    Fact table contains data that can be aggregate.
    Measures are aggregated data expressions (e. Sum of costs, Count of calls, ...)
    Dimension contains data that is use to generate groups and filters.
    This's fine but how does one decide which columns to consider for Fact table and which columns for Dimension table?
    Any help is much appreciated.
    Pardon me if this's not the correct place for this question. My first question in the new forum.
    Thanks and Regards,
    Ranit Biswas

    ranitB wrote:
    But my main doubt was - what is the criteria to differentiate between columns for Fact tables and Dimension tables? How can one decide upon the design?
    Columns of a fact table will often be 'scalar' attributes of the 'fact' data item. A dimension table will often be 'compound' attributes of a 'fact'.
    Consider employee information. The EMPLOYEE table can be a fact table. It might have scalar attribute columns such as: DATE_HIRED, STATUS, EMPLOYEE_ID, and so on.
    Other related information that can't be specified as a single attribute value would often be stored in a 'dimension' table: ADDRESS, PHONE_NUMBER.
    Each address requires several columns to define it: ADDRESS1, ADDRESS2, CITY, STATE, ZIP, COUNTRY. And an employee might have several addresses: WORK_ADDRESS, HOME_ADDRESS. That address info would be stored in a 'dimension' table and only the primary key value of the address record would be stored in the EMPLOYEE 'fact' table.
    Same with PHONE_NUMBER. Several columns are required to define a phone number and each employee might have several of them. The dimension tables are used to help 'normalize' the data in the employee 'fact' table.
    And that EMPLOYEE table might also be a DIMENSION table for other FACT tables. A DEVELOPER table might have an EMPLOYEE_ID column with a value that points to a 'dimension' row in the EMPLOYEE dimension table.

  • Integration Services - Dimension Table

    I?m trying to build a dimension table for a star schema to be used with Essbase Integration Services. I need to know how to structure the table when the data in the fact table is at a more granular level that that of the Essbase leaf member. The typical structure of my dimension tables is: [Leaf Node Name], [Leaf Node Alias], [Gen01], [Gen02]?, where the leaf node name is also the level of detail in my fact table.

    Well do remember bitmap indexes are best on columns where there not so many unique values. Everyone has differing opinions on what that # ought to be. In other words, the cardinality, or # of unique elements is not extremely high.
    IN general, bitmap indexes will improve performance given that the CBO is using them.
    Look at this post, it is a pretty good discovery on this sort of thing. it tends to be a design process, where you test with your given dataset and optimize it.
    http://www.rittmanmead.com/2007/07/27/playing-around-with-star-transformations-and-bitmap-indexes/
    -Greg

  • How to find out the infoProvider for a given dimension table?

    Experts:
    In RSA1, I want to find out the infoProvider for a given dimension table.
    But I am not sure how to display the tables linked to a given infoProvider.
    Could you provide a way to display all tables linked to a given infoProvider?
    Thanks a lot!

    See, The dimension table starts with Dcubename1 and incremental Dcubename2 .... so on
    Ex.ZSD_C01 is your cube name
    Dim tables starts for this is /BIC/DZSD_C011 /BIC/DZSD_C012 ...
    Goto - LISTSCHEMA  - derive cube name from given dim table and enter cube name  - execute - will show you all the tables

Maybe you are looking for