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

Similar Messages

  • Ratio between Fact table and Dimention table for a Infocube

    Hi All,
    How can we reduce the Ratio between Fact table and Dimention table for a Infocube below 20%.??
    please give suggestions

    Hi
    Reduce Ratio??
    The Ratios are dependent on the Fact Table, and the Dimension table that is modeled for your Cube.
    You cannot change ratio individually, but can set the Line Item Dimension , provided you have only one char object is taking much space and bulky with much percentage, based on your requirement. You can always use fine tuning objects.
    Please be more specific while posting, to get right help from sdn.
    Hope it helps

  • Record column level changes of table for audit.

    Hi Experts,
    I need  suggestion on recording column level changes in table for internal aduit purposes, our company policy does not allow us to enable CDC and CT on database levels so I am looking for whar are other the best ways for doing the same ?
    I know we can use triggers and OUTpUT clause to record the changes on tables but Is there any other light weight solution for recording changes on transactions tables which very gaint tables. 
    Seeking your guidnace on solution side ?
    Shivraj Patil.

    OUTPUT should be the best choice for your case as this would be much lighter than Trigger.

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

  • Change log table for Vendor Bidder information?

    Hi,
    In BBPMAININT transaction we have BIDDER DATA tab.
    If we change any Classification data in BIDDER DATA  tab for the Vendor in which table it updates the change log information?
    I checked in  BBP_SUPP_MONI table this table updates only when we change any Company data information for the vendor not Bidder tab.
    can any one help me?
    Thanks.

    Hi
    There is no standard report.
    But you can check in CDHDR & CDPOS tables for change log.
    Object Class= BUPA_BBP0020
    Tabname=BBPM_BUT_FRG0021
    Best regards
    Ramki

  • Changing color table for intensity graphs

    Hi, I've been working on superimposing intensity graphs and I'm almost getting it, I'm just having trouble with color table, it is suppose to be composed of a 1-D array of 256 colors
    I have 2 intensity graphs each with a different color table (256 color - 256 locations in the color table array). I need to "squeeze" both color table into a third color table for the superimposing of the 2 intensity graphs. therefore I figure I would take every other color value from each of the first 2 color tables (so each color table shrinks to 128 color) and add the values to form a 3rd color table so that the bottom will correspond to the first color table and the top will correspond to the 2nd color table.
    I can do this manually, but it takes WAY too long, so I've been trying to use some kinda of algorism, but I cannot succeed. Anyone have any suggestions? it seems that color table is an unusual kinda of array
    My attempted program is attached.
    thanks very much!!
    Attachments:
    superimposing3.vi ‏111 KB

    Brian,
    I think this is what you're after (attached). The easiest thing to do is to decimate, then concatenate your original color tables to form your new "squeezed" color table. However, keep in mind that you also have to squeeze, or remap, your underlying data values to correspond with either one half of the color table or the other.
    See if what I did makes sense.
    Regards,
    John
    Attachments:
    superimposing3_MOD.vi ‏90 KB

  • Table for Infoobject-Infocube Relation

    Dear All,
           I want to know whether there is a table that maintains information on infoobjects i.e. for a particular infoobject the table maintains all the infocubes where that particular infoobject is used. Is there such a table.If yes please tell me the table.
    Yours truly,
    Ratish

    Sir,
                  Perfect Thankyou Sir!
    Yours truly,
    Ratish

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

  • SQL Server Agent Jobs error for Slowly changing dimension

    Hi,
    I have implemented Slowly changing dimension in 5 of my packages for lookup insert/update.
    All the packages are running good in SSDT. And when i deployed the project to SSISDB and run the packages all are running successfully. But when i created a job out of that and run the packages, then 3 packages ran successfully and 2 packages failed. 
    When i opened All Execution Report. I found the following error:
    Message
    Message Source Name
    Subcomponent Name
    Process Provider:Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description:
    "Login timeout expired". An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description: "A network-related or instance-specific error has occurred while establishing
    a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". An OLE DB record is available. 
    Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ".
    Process Provider
    Slowly Changing Dimension [212]
    Then i opened Provider package in SSDT and changed the source reading record limit from 4,00,000 to 15,000 in source query and deployed again and run, then the job succeeded. more than 15,000 failed.
    And in the 2nd experiment, I removed slowly changing dimension task and implemented normal lookup for insert/update, and set the source reading limit again to 4,00,000 and deployed again and run, then the job succeeded.
    Now i am not able to figure out, what exactly is the problem with Slowly changing dimension task for more than 15,00 records in SQL Server  Agent Job run?
    Can anybody pls help me out.
    Thanks
    Bikram

    Hi Vikash,
    As i have mentioned in the above post, below 2 scenarios: 
    "Then i opened Provider package in SSDT and changed the source reading record limit from 4,00,000 to 15,000 in source
    query and deployed again and run, then the job succeeded. more than 15,000 failed.
    And in the 2nd experiment, I removed slowly changing dimension task and implemented normal lookup for insert/update, and set the source reading limit again to 4,00,000 and deployed again and run, then the job succeeded."
    That means i am able to connect to sql server.
    But if i change the 1st scenario and read 4,00,000 records, the job fails and shows the above mentioned error.
    Similarly in the 2nd scenario, if i implement SCD look up,  the job fails and shows the above mentioned error.
    And i am consistently reproducing this.
    Thanks
    Bikram

  • 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

  • Number of Entries in Dimension Tables and Fact Tables

    Hi all,
    is there an easy way to check
    - the number of entries in the dimension tables
    - the number of entries in the fact table?
    Thanks  a lot
    Alex

    Hi Alex,
    If u want to see the content of Dimension table and Fact table for a infocube then just right click on a particular info cube then select manage . Select coneten tab there , form there u can either select Fact table to see the fact table conten or Infocube content to see the Dimensiontable content.
    Regards..

  • Regularly for an infocube ZPRG_C02 where indexes are corrupting !

    Hi All,
    We are facing this problem Regular for infocube ZPRG_C02 where indexes are corrupting, these can be manually resolved on running SAP_INFOCUBE_INDEXES_REPAIR report but Which isn't ideal and preferred , This cube is updated daily, and the process includes steps to delete and recreate indexes.
    ORACLE: The status of index /BIC/FZPRG_C02~010 is INVALID
    Is their any process , where we can avoid , corrupting these indexes
    How to go about this, any suggestion
    Whether BW Intervention is required in this ?  or Is it a BW issue ?
    How to perform cude index degradation, Please suggest.
    BI System is on SAP EHP 1 for SAP NetWeaver 7.0
    B I Support pack level information :
    SAP_BW     701     0006     SAPKW70106     SAP Business Warehouse

    Perform RSRV test -
    Fact- and Dimension- Table of an InfoCube
    Database Indices of an InfoCube and Its Aggregates
    Check Database Parameter(s)
    Otherwise Re-activate the Cube

  • 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

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

Maybe you are looking for