Adding of new infoobject to a cube?

Expert's,
I have an issue,where in I need to add a new  infobject to a cube.This cube is getting updated by an ODS.The ODS is updating deltas  to cube.Upto ODS it is Full update.The infobject which has to be added to a cube is allready available in ODS and also getting populated.
Now my question is ,
How can I add new infobject to a cube without deleting the contents of the cube.I<b> also need all hystorical data whatever available for that infobject.</b>Hope I am clear.
Points will be definitely awarded for the right answers.

Hi  Vasu,
   if you are using BI 7.0 means.. you can do that through <b>Remodelling</b> .. option... select your cube. and  right clcik  it.. and in the context menu you can find this option...
  with this.. with out deleting old data you can add new fileds and populate the data also...
  But if you are using 3.x means.. with out deleting the existed data.. you can't addthese  new fields.. and  you can't  load the  those particular data ..
      so,  you need to  take the backup of that data.. and  change the structure of cube... and load  all the data from the  start...
regards
@jay

Similar Messages

  • How to add new infoobject to existing cube or dso?

    Hi all,
    Can we add new infoobject to exixting cube in BW 3.5 ver? if yes how can we add? Please provide me steps.
    Thank you.
    Sunil

    Hi Sunil,
    If you want to add new info object to the IC or DSO which is already holding data - then you need to make a copy of that particular DSO/IC and load the data into dummy.
    Now delete the data from the IC/DSO to which you want to add the new info object. once the data is deleted it will allow you to add new info object to you IC/DSO.
    save it and activate the IC/DSO
    load the data from Dummy DSO and from new run on wards the newly updated info object will also get updated(historical data will not be updated if its newly added to DS as well).
    If you want the historical data for the newly added field then you need to drop the compelte data and need to extract from source.
    Note: You can't include the new info objects are change the existing info objects if there is data exist in the IC/DSO
    Regards
    KP
    Edited by: prashanthk on Dec 31, 2010 10:54 AM

  • Adding a New Dimension to a CUBE

    Hello
    Being in new at Oracle OLAP...
    If I need to add a new dimension, SHOULD I RECREATE the cube entirely again??
    Is not there any other way??
    Regards

    Each cell in a cube is referenced by a dimension. Think of it as pointers to cells in a multi-dimensional array.
    So when you add or remove a dimension, what should happen to all those cells.
    In a way you are breaking the cube.
    Since cube data is loaded from a table, you can always re-load your cube after adding or removing a dimension.
    Dimensions are not added/removed frequently, once the design is finalized. You may add a new hierarchy to existing dimensions, which is done more frequently compared to adding a dimension. After adding a new hierarchy, you just have to re-aggregate cube data and not re-load from relational source.
    Cubes are created for reporting, and can be deleted/recreated or truncated - monthly, quarterly or yearly - for various reasons.
    Your source transactional detailed data should be in one (or more) fact tables and should never be deleted.
    Is there any "operational" concern in a Production environment, because of which you are asking this question?
    One trick could be: to create the new cube (with more dimensions or less dimensions than the original cube) and then COPY DATA from original cube into that new cube.
    But it may take the same amount of time as re-loading the new cube from the relational source.

  • Adding new infoobject to cube with data

    Hi experts
    Our cube contains data and is fully compressed (E-table), there is are no requests in F-table.
    We need to add 2 key figures and 2 characteristics.
    The characteristics get a new dimension table.
    We don't use the remodel technique. We add these new infoobjects.
    There is no need for a reload of historical data for these new objects.
    We only need data starting from the first load date after the changes occured.
    Are there any errors in this approach?
    Thanks

    Thomas,
    When you are adding a new dimension to your cube - you are adding a primary key to your E and F Fact tables - therefore when your transport goes it - it will reorganize your cube tables.
    For this - assuming that you are collecting the changes in the normal way and not changing any settings ....
    1. Check the UNDO table space in target system , the UNDO table space should have enought free space available that will be greater than the size of your E and F Fact table sizes - because , the way the transport moves is that a copy of the table is taken in the undo table space in the database and then the tables are adjusted - if your undo table space is insufficient - the transport will fail after some time
    2. If this is a big cube - then the transport will take time to go in - if BASIS imports transport requests in sequence - then this transport will hold the queue and might delay others whi have smaller transports.... make sure that your transport goes in last if there are others waiting for you to complete
    3. Also inform BASIS that the transport is going to take time - sometimes long running transports can get the BASIS team excited :-)
    These are not technical but some bases that can be covered in advance...
    Hope this helps.,...

  • Unable to add new Infoobject from Infoprovider to multiprovider

    Hello Experts,
    I have a multiprovider which joins four different Cubes. Now, I added a new Infoobject to one of those Cubes but I am unable to transfer that InfoObject from the Cube to the multiprovider.  I tried the identify characteristics option in the edit multiprovider mode but I was unable to see that Infoobject in the base cube to which it is added. The only unusual thing about this Infoobject is that it is not linked to any source field and set to initial in the update rules as I am populating it using a ABAP code in the end routine. I am not sure if this has got to do anything with the problem
    Any help in this regards will be appreciated and points will be duly assigned.
    Thanks
    Rishi

    HI,
    Try this,
    Deactivate and activate the MP again.
    Also Try this Program,
    RSDG_MPRO_ACTIVATE
    Hope this helps...

  • Steps for adding a new attribute

    Please let me know if the below steps are correct
    =================================================
    I have an Infoobject called 0XXXX in BW and want to add another attribute called XXX_TYPE.
    This infoobject is used in 2 Info Cubes and a Multiprovider. Also in 3 queries.
    In R/3 the info I need is stored in a Table(XYZ). Please let me know if the below steps are correct and all I need
    1) Create a generic extractor to pull the data from XYZ table (Like an ABAP program) .. This is the part which I am not clear !!!
    2) Modify 0XXXX in BW to add this new navigational attribute
    3) Load Master data using process chain
    4) Re activate all update rules
    5) Change Infoprovider's for the new attribute (How to do that ??)
    6) Change query (What changes will I need to make .. Just select this attribute field into the required query)
    Please help

    Hello,
    As you said, either enhance the extract structure by adding this new InfoObject and then write the code in the user-exit.
    Or if the SAP table has the Key fields of the InfoObject, then create a generic extractor. Create a view by including the key fields of the InfoObject and the new attribute InfoOBject for which data has to be derived from this. Use this view or the table itself for the extractor.
    Create new InfoSOurce for the InfoObject which will only update the new InfoObject. Keep only transfer rules for the Key InfoObjects and the new InfoObject.
    GSM.

  • Problem while adding a new dimension in a existing cube with data in BW3.5

    Hi,
    We are trying to create a new dimension with new characteristics in a existing cube. But while activating we are getting error that "InfoCube contains data; intentional changes not permitted". Can we add a new dimension in a existing cube with data in BW3.5? If it is not possible then we can take the backup and delete the data from cube and then change the cube. But my question is that, when we will transport the cube with changes to quality then will it transport successfully or same procedure needs to be done there as well.
    Regards,
    Saikat

    hi,
    Adding new infoobject /dimension to the cube containing data in 3.5 is not possible.
    easier solution is create a new cube similar to old and add the new dimension and proceed.
    else you have to drop data and transport.
    Ramesh

  • Adding new infoobject

    hai
    i am adding new infoobject to ods and cube,that have data already.how can i do.i want to delete the data both in ods and cube.if so how to delete the data in ods.

    hi..
    Unless you delete data from Cube , Data from ODS can not be deleted and this behavior is to maintain consistency of data and subsequent delta updates from ODS to Cube.
    You cant delete the data from ODS if data is already in Active table of ODS.
    In this scenario you can do only delete the whole data & again upload.
    ODS ---> Rightclick -
    > Delete
    You will have to activate ODS in order to delete data from ODS.
    Ideal sequence could be
    1. Delete data from ODS
    2. Do enhancement in R/3 side
    3. Do enhancement in BW side ( add/ remove info object )
    4. Activate ODS, Update Rule.
    hope it helps..

  • Problems adding new caracteristics ti 0IC_C03 Cube

    Hi people:
    We made a copy of standar cube 0IC_C03. We add some new time characteristics (0halfyear, etc..). De activation of the cubes is OK, but when we try to map the corresponding fields in the tranformation rules, the new fields doesn't exist. Like the group of transformation are standar, we try to add them manually, but the infoobject isn't seen.
    Does this cube has a limitation for adding new infoobjects? Am I misssing some step I don't know?
    Thank you in advanced.

    Hi,
    There is a relation between time characterstics ,
    We have to take care of this relation in the transformation mapping where we are mapping source fields to target fields.
    Please refer below link which will show you the relation between time characterstics.
    http://help.sap.com/saphelp_nw70/helpdata/en/44/be8b631c743959e10000000a1553f6/content.htm
    Hope this will help you...
    Thanks,
    Jitendra

  • Adding new fields to existing cube

    Hi all,
    We have a cube with data, now we added 2 new fields to the datasource. And want to add two more fields in the Cube to correspond to the new fields. What would be the impact on the data that is already there in the cube? Can I go ahead and add the fields in the cube and start extracting data? What I want to know is what would be the implications in such a scenario?
    Any insight or help would be appreciated and fully rewarded.
    Thanks,
    Mav

    Hi,
    At least from the experience I had there were no performance issues. The only issue would be in terms of the time taken to transport. The larger the amount of data ,longer the transport time.
    You can continue extraction of data for those 2 fields from that point on. No need to empty the data from the cube and reload again. Only thing is that the data in the past for these 2 fields may not be mapped to the existing data in the cube. If you want to do that dump the cube and reload. Otherwise the data will be mapped from the time you start extracting the new fields with the data in the cube.
    Cheers,
    Kedar

  • Issues with Writing back data to Planning Cube After adding a new characterstic

    Hello,
    We have two cubes and a MP on top of it. ( Reporting Cube and Planning Cube ). An aggregation layer has also been built and so does a planning BEx query on top of it.
    Before Scenario: things were working fine as we were able to write back data to planning cube using the BEx.
    After Scenario: We created a new Dimension in the planning cube and added a new characteristic ( lets call it ZX_KEY ) . This Characteristic holds the concatenated values of some of the other characteristics in its master data tables . ( For ex: Account_Customer ID_Country-code_Industry-code ).
    This new characteristic is also present in the reporting cube and has been added and transferred to MP.
    This new characterstic was added to the planning BEx query as one of the rows and we executed it the analyzer. After entering the required values for all characterstics ( including the newly added ZX_KEY ) and the key figure values, we tried saving it. Now this is where the Analyzer is throwing up this error..
    ~~Characterstic combination cannot be assigned to part provider ~~
    ~~Characterstic 'ZX_KEY'; Characterstic value 'R123000000_12_US_TX'~~
    ~~ Entered values are incorrect:Correct before navigation ~~
    The value that we are entering ( R123000000_12_US_TX ) is picked up from the master data table of ZX_KEY by double clicking and selecting it from the fetched values. So i am not sure as to why its throwing up the above error. Request your help on this please.
    regards,
    Karthik

    Hi,
    Try to check that all characteristics are correctly assigned at multiprovider level.
    hope it helps

  • InfoSet maintance - added new InfoObject, not available in query

    Hi,
    We appended a new field to the 0VENDOR_ATTR extractor and the data comes accoss fine.  We are using InfoObject 0CREDITOR in an InfoSet.  When I did an 'adjust' step to the InfoSet, the new InfoObject became visable but the check box is grayed out and the new InfoObject is not usable in a query.  Is there any way to change the check box so that the new InfoObject is available in a query?
    Thanks,
    John

    Hi John,
    Change your 0CREDITOR InfoObject and make sure that the 'Attribute Only' box is not checked.  You will be unable to make it usable in an InfoSet query if this box is checked.  Let me know if this solves your issue.
    Josh

  • Adding a new field to a Z table

    We have a Z table on which we have created a datasource. We have created a virtual cube on this datasource and queries are built on this cube. This setup is present on Dev, Quality and Prod environment.
    Now we have added a new field to the Z table in Dev. We will be creating a new Infoobject for this new field and will be adding it in the Virtual Infoprovider and also in the queries.
    1. Do we need to replicate the datasource so that newly added field is visible to the datasource? If no, is there any way?
    2. When I have to transport this to Quality and Prod, do I have to capture all the components and objects (Table,Datasoure,Virtual Cube Queries)? If no, what should I capture in the transport request?

    Hi,
    First, you have to regenerate the datasource in order to add the field:
    1) Log on to source system (where Z table is stored) and go to transaction RSA6.
    2) Select the root node and click Expand (icon with '+' sign).
    3) Search for your datasource (you can use the binoculars icon).
    4) Click on Change.
    5) Verify that the field appears on the list.  Make sure that "Hide field" and "Field only known on client exit" options are not marked for this field.
    6) Click on Save.
    7) Select "Datasource" -> "Generate" (CTRL+S) menu option.
    8) Use RSA3 transaction in order to verify the new field appears on test extractions.
    Then, to replicate the datasource in BI:
    1) Log on to SAP BI and go to RSA1 transaction.
    2) Go to "Modeling" -> "DataSources" section.
    3) Search for your datasource and right click on it.  Select "Replicate metadata" from context menu.
    4) Add the new InfoObject to the VirtualProvider.
    5) Update the transformation which joins the DataSource to the VirtualProvider.
    As far as transport requests are concerned, even though it requires more work, it is a good practice to group objects in different transport requests according to their type:
    In the source System (R3 for instance):
    1) One transport request with the table.
    2) One transport request with the datasource and its structure.
    In BI:
    1) One transport order with the datasource replica.
    2) One transport order with the new InfoObject(s).
    3) One transport order with the modified VirtualProvider.
    4) One transport order with the modified transformations from the datasource towards the VirtualProvider.
    5) One transport order with the Queries and their elements.
    I hope this helps you.
    Regards,
    Maximiliano

  • Append new InfoObject to InfoCube 0PAPA_C02/InfoSource 0HR_PA_PA_1

    Hi,
    I need to append a new InfoObject (which is an attribute of 0EMPLOYEE) to InfoCube 0PAPA_C02 and it's InfoSource 0HR_PA_PA_1.
    However, when I try to add the InfoObject to the extract structure by using transaction SBIW (or RSA6), I'm unable to add it (it doesn't allow to add any other InfoObjects).
    I am doing something wrong or do I have to do this some other way?
    Regards,
    Mark.

    hi mark,
    u say u need to append new object attribute of 0employee,
    so u should heve loaded master data fro 0employee.
    if this is the  case then u can use transfer rule or update rule for loading the new object by read from master data.
    u need not add any object in extract structure.
    u have to added one more field in the cube.
    either u have to remodle or full load it in a new cube with new field added.
    reward points if helpful.

  • Need to add new InfoObject to existing target

    Hi,
    I need to add one extra InfoObject to my existing cube. Data is coming from r/3 can please detailed me the procedure..
    r/3 side enhancements and BW side enhancement in details.
    regards,
    Silpa

    Hi Silpa,
    Before adding the field into existing info cube fiirst u need to check in R/3 the field is properly enhanced  or and data is populated or not
    In R/3 side if u enhance any field that will avialble on field only known exit or inversion check in data source make that field seletion properly.
    After that u need to check in RSA3 check the data.
    After Replicate u r data source.
    Once it is completed in R/3 come to BW
    U need add the compateble field in transferstructure structure and CS also.
    To load the new field data u need to delete the existing data in cube level.
    And go for Re-init.
    Hope this will help.
    Regards,
    HARI GUPTA

Maybe you are looking for