Fields added to dso not to the cube- Init question

Hello,
I would like to know if i make changes to a dso and cube in production.And i need to make changes just to the dso, added 2 fields, these fields are not added to the cube and the cube has not been changed or modified.Now if i want to init and get historical data as well on the newly added fields in the dso, I will delete the data in DSo, but i would liek to know what about the cube.Can i leave the cubes data in it and just init into the dso and resume deltas from dso to the cube once init is done.
Please comment.
Thanks.

No need to delete data in the DSO or the infocube.
Assuming you are loading the DSO from R/3.
Do not delete any initializations from R/3 to DSO .. or from DSO to Infocube.
Leave it as is.
After you move the transport which has the additional attributes added to the DSO object and all the transformations to the cube are also Active.
Now do a full repair load from R/3 to BW for that DSO. You can select the Full repair from the infopackage under the Scheduler Menu option.
Load the data and activate it.
There wouldn't be any duplicates in the DSO unless the two characteristics that you added form a key in the DSO structure.
After loading the data . do a  delta to the infocube. It should load only the delta records from the last run date.

Similar Messages

  • Field"Code group" is not in the result for report CRM_SRV_REPORT

    Hi Guys,
    For the tx CRM_SRV_REPORT - Service Process Monitor, the field "Code group" is not in the standar result, but, is in the initial screen for filter selection.
    This field is not available in the layout modification.
    How can I add this field to the layout of the result list?
    Regards,
    Lyda

    Hi Lyda,
    Additional field cannot be added in the layout of the result list.
    If you will observe the code of the report CRM_TSRV_REPORT, in the field catalog, there is not Code, code group etc., hence it is not seen in the layout.
    Since it is a std report it cannot be modified, either u can create a Z report by copying this or u can raise an OSS message for this.
    Regards,
    Shalini Chauhan

  • Client would like the monetary fields to reflect . and not , in the fields.

    Client would like the monetary fields to reflect . and not , in the fields. There are commas and he wants decimals.
    can any one help me out, this is a tkt  can any one suggest me how do we take it further.

    Hi Jai Ram,
    Ask the user to go to SU3 tcode. Then go to defaults tab. There is a field called Decimal Notation. There are three formats as below
    1.234.456,789
    1,234,456.789
    1 234 456,789
    Select accordingly. Then quit SAP and relogin. The changes will be applied.
    Kind Regards
    sandeep

  • Request had transfer data but there are not in the Cube

    Good morning experts;
    I’m using the BI 7009 version (Business Content 7003).
    I just activate the BC from the 0CO_OM_OPA_1 datasource to the 0OPA_C11 infocube. I also had created a infopackage to upload data from R/3.
    The problem is that, in the InfoCube request, the data where transfer but not inserted. Checking the PSA all the status are green.
    What seems to be the problem?
    Regards;
    Ricardo

    Hi Ricardo,
    If you are using the BI version, you have to load the data into the PSA using an infopackage and then from there on you have to create a transformation from the datasource to the info cube and then using DTP(Data transfer protocol) you can load data into the cube.
    With BI the loading is 2 step process unlike that of the older versions where you can load data directly into the cube using an IP.
    Hope this helps you upto some extent.
    Regards

  • Interval of values not in the cube

    Hello,
    I'm using BW 3.5.
    I need to make a selection in a query on reason code values 7001-7099. Unfortunately when making such restrictions you are only allowed to choose values in masterdata and/or in the cube. There is no masterdata for reason code and there is no data in the cube yet. If you want a particular value, you may enter it in the field below the list and then press the right arrow button, but this doesn't work for intervals. It appears to be a bug. Anyone who has a workaround?

    Hi,
    In case if something is missing ,
    Go thorugh following step
    1. Right click on the characteristics - Restrict
    2. On the left top drop down put "Selection = Value Range"
    3. Just next to that other drop down "Select = Between"
    4. Now type down 7000 in bottom left box
    5. Click on right arrow , this will be selected as lower limit.
    6. Now type down 7999 in bottom left box
    7. Click on right arrow , this will be selected as upper limit.
    I am at Query designer version is 3500.3.555, which is older one .
    And in my system it works perfectly .
    Regards
    Kapadia

  • Added new field to ALV but not  displaying the ouput

    Hi guys,
    I'm adding one more column to be displayed on an old existing program that uses REUSE_ALV_FIELDCATALOG_MERGE to generate the ALV fieldcat.
    DATA : BEGIN OF itab OCCURS 0,
      matnr LIKE eina-matnr,
      extwg LIKE mara-extw,
      matkl LIKE mara-matkl,
      mtart LIKE mara-mtart,
      maktx LIKE makt-maktx,
      lifnr LIKE eina-lifnr,
      wglif LIKE eina-wglif,
    <span style="color:red">idnlf like eina-idnlf,          " <----
    new field</span>
      name1 LIKE lfa1-name1,
      profl LIKE mara-profl,
    END OF itab.
      CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
        EXPORTING
          i_program_name         = sy-cprog
          i_internal_tabname     = 'ITAB'
          i_client_never_display = ''
          i_inclname             = sy-cprog
         i_bypassing_buffer     = 'X'
        CHANGING
          ct_fieldcat            = t_cat
        EXCEPTIONS
          inconsistent_interface = 1
          program_error          = 2
          OTHERS                 = 3.
    I've added in a new field inside the ITAB internal table, but it wouldn't appear in the t_cat, only all the old fields will appear. What have i done wrong?

    Hi
      Facing similar kind of issue.. added one field to the existing internal table. This is not getting populted by the field catalog merge FM. Tried with the suggested solution also of running programs BALVBUFDEL,
    BCALV_BUFFER_DEL_SHARED then logging off  and logging in..
    But the newly added field is not getting populated. Any suggestions would be of great help.
    Regards,
    sridevi S

  • Field over flow can not display the total and subtotal in ALV

    hi
    i am running a z report with huge data in quality system.
    in 2 columns and not able to show the total and subtotal in 2 columns
    it says field overflow and cannot be dispayed.
    value is around 20character integer.

    You can create a domains with 20 positions and 2 decimal, for example.
    Than, associate this domain a data element.
    To finish assign that data element to the column you wanna sum.
    I hope help.

  • HT1349 trying to import a cd and i am receving incorrect song info, that is, songs are listed that are not on the cd in question what to do?

    trying to import a cd and songs are being downloaded from an older cd with a similar name

    If more than one entry is found for the CD (which can occur if more than one person submitted information for the same CD to the Gracenote service), select one of the entries. If it isn’t correct, choose Advanced > Get CD Track Names again and choose the other entry. If it’s still not correct, you can edit the information yourself.

  • Fields not populated in cube

    hi experts,
                       i have one problem i have sales item,and header dso's which i have loaded the data using flat files.when am trying to load to cube some of the fields of header is not  getting populated.when i am loading only header data that time it is showing the data in cube.when i am loading item data also that time some of the fields of header are not populating in cube.i have tried by taking two seperate cubes for header and item and tried to  loading data to multiprovider. but same issue came.for ur reference i am providing screen shots of that. this is multi provider screen shot in this u can observe that division ,region and some fields are not populating data. in local sand box i have done this please help me to resolve this issue.
    header  cube screen shot before loading to multiprovider.
    item cube screen shot before loading to multiprovider.
    regards
    jaswanthi

    How are you "loading" to a MultiProvider? A MultiProvider is merely a "view" on 1 or more InfoProviders, nothing gets loaded in it.
    The screen shot of your MultiProvider shows data of your items InfoCube only... have you filtered on the InfoProvider field? If not, try and filter on your header InfoCube and see whether it shows any data. If not, then there's something wrong with your mappings in the MultiProvider definition.
    It's perfectly normal to have empty fields if you're combining 2 InfoProviders into 1 MultiProvider. If that's not what you want, you should consider an InfoSet (which "joins" data) or model it so that when you're sending item data to a new InfoCube, you "look up" the missing header data in your header data DSO and add it.

  • Data not matching in cube which gets from two DSOs

    Hi All,
    I have a requirement.
    Cube gets from data from 2 DSOs.
    In 1 DSO -
    There are three fields which are mapped to one field in Cube
    2 DSO--There are also similar type.
    Like 4 fields in dso2 mapping to 1 field in cube
    When the data is loaded into Cube,
    the data is shown as split data like DSO 1 data and DSO2 data.
    I want them combined.
    Can anyone let me know what can I do to show as combined data.
    Thanks In advance!

    Thanks to both of you.
    I am different characterstics in DSO1 and DSO2 to cube.
    Ofcourse 1or 2 characterstics are common in both DSOs.
    Employee LNum deptid frname  compcode
    12                               VBNM  W123
    13                                KNML   W145
    15             345    K45
    16             864    L89
    So I am able to see as Split data.12,13 employee IDs are from DSO1 and 15,16 r from DSO2.
    even if I give sam eemploee numbers also, same type of split data appears.
    Please suggest tocombine both DSOs data in the cube.
    Thanks In advance!

  • Query is not picking up right data from the cube

    Hi Bi expert,
    I added one infoobject (0cust_group) on the cube and when I display data through ‘manage’ option on RSA1 transaction, I can see that the infoobject nicely populated. But when running query, it’s coming under ‘Not assigned customer group (s)’. Could you please help me on this matter? I have activated cube and update rule and even generated the query using transaction ‘RSRT’.
    Thanks for your help.

    How do you fill the customer group char in your rules?
    1 - using master data of customer or 2 -datasource sending it from R3?
    case 1:
    check that  0customer attributes are filled and active ( objvers = A)
    case 2: check it in r3 using RSA3 transaction, to see if it is extracting it?
    derya

  • Field Explorer in Crystal Reports does not show the same names as Bex Query

    Hi
    I have crystal reports, I can retrieve data from BW Bex Query. But in the field explorer it does not show the names as in the Bex query designer.
    In the Bex query designer a field will have the following technical name 0Debitor and the description is Customer.
    It shows in crystal reports in the field explorer twice as D[0DEBITOR]D and D[0DEBITOR]D. It also does not seperate key figures and characteristics.
    I would like it to display the field explorer as shown in this blog.
    /people/ingo.hilgefort/blog/2008/02/19/businessobjects-and-sap-part-2
    Thanks in advance

    Hi,
    take a look here:
    /people/ingo.hilgefort/blog/2008/02/19/businessobjects-and-sap-part-2
    make sure you are using the MDX Driver and what happens is that you will see several fields per characteristic. example: one for the key, one for the description, several if modelled for the display attributes
    Ingo

  • Data in the cube is showing multiple entries when compared with ODS

    Hello BW Gurus,
    We have a waste report in production planning on Cube and ODS separately. The same info package loads both targets (which means same infosource) but when we run a report on Cube, the records are showing multiple entries (i.e. Key Figures are not matching when compared to ODS) where as the ODS records are showing correctly as it was in R/3. There are totally 6 key figures out of which 4 pulled from R/3 and 2 are populated in BW.
    An Example:
    Waste report in PP run for plant 1000 for 12/2005 and process order 123456. The operational scrap should be 2.46% and the component scrap should be 3.00% for material 10000000. The report is showing 7.87% for planned operational waste % and 9.6% for planned component waste %. These values are not correct. The ODS values for order 123456 matched the data in R/3 for component and operational scrap.
    There is a Start routine to the ODS and also to the cube. I am not good at ABAP so requesting your Help.
    Here is the ODS Code:
    tables: /BI0/PPRODORDER.
    loop at data_package.
    select single COORD_TYPE
    PRODVERS
    into (/BI0/PPRODORDER-COORD_TYPE,
    /BI0/PPRODORDER-PRODVERS)
    from /BI0/PPRODORDER
    where PRODORDER = data_package-PRODORDER
    and OBJVERS = 'A'.
    if sy-subrc = 0.
    if /BI0/PPRODORDER-COORD_TYPE = 'XXXX'
    or /BI0/PPRODORDER-COORD_TYPE = 'YYYY'.
    data_package-PRODVERS = space.
    else.
    data_package-PRODVERS = /BI0/PPRODORDER-PRODVERS.
    endif.
    endif.
    if data_package-calday = space
    or data_package-calday = '00000000'.
    if data_package-TGTCONSQTY NE 0.
    data_package-calday = data_package-ACTRELDATE.
    endif.
    endif.
    modify data_package.
    endloop.
    Here is Cube Code:
    tables: /BI0/PPRODORDER,
    /BIC/ODS.
    TYPES:
    BEGIN OF ys_mat_unit,
    material TYPE /bi0/oimaterial,
    mat_unit TYPE /bi0/oimat_unit,
    numerator TYPE /bi0/oinumerator,
    denomintr TYPE /bi0/oidenomintr,
    END OF ys_mat_unit.
    DATA:
    l_s_mat_unit TYPE ys_mat_unit,
    e_factor type p decimals 5.
    loop at data_package.
    select single COORD_TYPE
    PRODVERS
    into (/BI0/PPRODORDER-COORD_TYPE,
    /BI0/PPRODORDER-PRODVERS)
    from /BI0/PPRODORDER
    where PRODORDER = data_package-PRODORDER
    and OBJVERS = 'A'.
    if sy-subrc = 0.
    if /BI0/PPRODORDER-COORD_TYPE = 'XXX'
    or /BI0/PPRODORDER-COORD_TYPE = 'YYY'.
    data_package-PRODVERS = space.
    else.
    data_package-PRODVERS = /BI0/PPRODORDER-PRODVERS.
    endif.
    endif.
    if data_package-calday = space
    or data_package-calday = '00000000'.
    if data_package-TGTCONSQTY NE 0.
    data_package-calday = data_package-ACTRELDATE.
    endif.
    endif.
    data_package-agsu = 'GSU'.
    data_package-agsu_qty = 0.
    select single gr_qty
    base_uom
    into (/BIC/ODS-gr_qty,
    /BIC/ODS-base_uom)
    from /BIC/ODS
    where prodorder = data_package-prodorder
    and material = data_package-material.
    if sy-subrc = 0.
    if /BIC/ODS-base_uom = 'GSU'.
    data_package-agsu_qty = /BIC/ODS-gr_qty.
    else.
    SELECT SINGLE * FROM /bi0/pmat_unit
    INTO CORRESPONDING FIELDS OF l_s_mat_unit
    WHERE material = data_package-material
    AND mat_unit = 'GSU'
    AND objvers = 'A'.
    IF sy-subrc = 0.
    IF l_s_mat_unit-denomintr <> 0.
    e_factor = l_s_mat_unit-denomintr /
    l_s_mat_unit-numerator.
    multiply /BIC/ODS-gr_qty by e_factor.
    data_package-agsu_qty = /BIC/ODS-gr_qty.
    ENDIF.
    else.
    CALL FUNCTION 'UNIT_CONVERSION_SIMPLE'
    EXPORTING
    INPUT = /BIC/ODS-gr_qty
    NO_TYPE_CHECK = 'X'
    ROUND_SIGN = ' '
    UNIT_IN = /BIC/ODS-base_uom
    UNIT_OUT = 'GSU'
    IMPORTING
    OUTPUT = DATA_PACKAGE-gsu_qty
    EXCEPTIONS
    CONVERSION_NOT_FOUND = 1
    DIVISION_BY_ZERO = 2
    INPUT_INVALID = 3
    OUTPUT_INVALID = 4
    OVERFLOW = 5
    TYPE_INVALID = 6
    UNITS_MISSING = 7
    UNIT_IN_NOT_FOUND = 8
    UNIT_OUT_NOT_FOUND = 9
    OTHERS = 10.
    endif.
    endif.
    endif.
    modify data_package.
    endloop.
    some how the AGSU qyt is not populating in the cube and when I dbug the code, I could see a clean record in the internal table but not in the cube.
    your suggestion and solutions would be highly appreciated.
    thanks,
    Swathi.

    Hi Swathi
    In ODs we have option of overwriting and addition however in Cube we have only adition.Thats why you are getting multiple enteries.
    If you are running daily full load on the cube then please delete the earlier requests.
    So at one point of time there should be only one full load request in cube. Hope this will solve your problem.
    Regards,
    Monika

  • Data in the cube is showing wrong when compared with ODS

    Hello BW Gurus,
    We have a waste report in production planning on Cube and ODS separately. The same info package loads both targets (which means same infosource) but when we run a report on Cube, the records are showing multiple entries (i.e. Key Figures are not matching when compared to ODS) where as the ODS records are showing correctly as it was in R/3. There are totally 6 key figures out of which 4 pulled from R/3 and 2 are populated in BW. 
    An Example:
    Waste report in PP run for plant 1000 for 12/2005 and process order 123456.  The operational scrap should be 2.46% and the component scrap should be 3.00% for material 10000000.  The report is showing 7.87% for planned operational waste % and 9.6% for planned component waste %.  These values are not correct.  The ODS values for order 123456 matched the data in R/3 for component and operational scrap.
    There is a Start routine to the ODS and also to the cube. I am not good at ABAP so requesting your Help.
    <b>Here is the ODS Code:</b>
    tables:  /BI0/PPRODORDER.
      loop at data_package.
        select single COORD_TYPE
                      PRODVERS
          into (/BI0/PPRODORDER-COORD_TYPE,
                /BI0/PPRODORDER-PRODVERS)
          from /BI0/PPRODORDER
         where PRODORDER = data_package-PRODORDER
           and OBJVERS   = 'A'.
        if sy-subrc = 0.
          if /BI0/PPRODORDER-COORD_TYPE = 'XXXX'
          or /BI0/PPRODORDER-COORD_TYPE = 'YYYY'.
            data_package-PRODVERS = space.
          else.
            data_package-PRODVERS = /BI0/PPRODORDER-PRODVERS.
          endif.
        endif.
        if data_package-calday = space
        or data_package-calday = '00000000'.
          if data_package-TGTCONSQTY NE 0.
            data_package-calday = data_package-ACTRELDATE.
          endif.
        endif.
        modify data_package.
      endloop.
    <b>Here is Cube Code:</b>
    tables:  /BI0/PPRODORDER,
               /BIC/ODS.
      TYPES:
      BEGIN OF ys_mat_unit,
        material                 TYPE /bi0/oimaterial,
        mat_unit                 TYPE /bi0/oimat_unit,
        numerator                TYPE /bi0/oinumerator,
        denomintr                TYPE /bi0/oidenomintr,
      END OF ys_mat_unit.
      DATA:
        l_s_mat_unit             TYPE ys_mat_unit,
        e_factor                 type p decimals 5.
      loop at data_package.
        select single COORD_TYPE
                      PRODVERS
          into (/BI0/PPRODORDER-COORD_TYPE,
                /BI0/PPRODORDER-PRODVERS)
          from /BI0/PPRODORDER
         where PRODORDER = data_package-PRODORDER
           and OBJVERS   = 'A'.
        if sy-subrc = 0.
          if /BI0/PPRODORDER-COORD_TYPE = 'XXX'
          or /BI0/PPRODORDER-COORD_TYPE = 'YYY'.
            data_package-PRODVERS = space.
          else.
            data_package-PRODVERS = /BI0/PPRODORDER-PRODVERS.
          endif.
        endif.
        if data_package-calday = space
        or data_package-calday = '00000000'.
          if data_package-TGTCONSQTY NE 0.
            data_package-calday = data_package-ACTRELDATE.
          endif.
        endif.
        data_package-agsu     = 'GSU'.
        data_package-agsu_qty = 0.
        select single gr_qty
                      base_uom
          into (/BIC/ODS-gr_qty,
                /BIC/ODS-base_uom)
          from /BIC/ODS
         where prodorder = data_package-prodorder
           and material  = data_package-material.
        if sy-subrc = 0.
          if /BIC/ODS-base_uom = 'GSU'.
            data_package-agsu_qty = /BIC/ODS-gr_qty.
          else.
            SELECT SINGLE * FROM /bi0/pmat_unit
              INTO CORRESPONDING FIELDS OF l_s_mat_unit
              WHERE material   = data_package-material
                AND mat_unit   = 'GSU'
                AND objvers    = 'A'.
            IF sy-subrc = 0.
              IF l_s_mat_unit-denomintr <> 0.
                e_factor = l_s_mat_unit-denomintr /  
                              l_s_mat_unit-numerator.
                multiply /BIC/ODS-gr_qty by e_factor.
                data_package-agsu_qty = /BIC/ODS-gr_qty.
              ENDIF.
            else.
              CALL FUNCTION 'UNIT_CONVERSION_SIMPLE'
                EXPORTING
                  INPUT                = /BIC/ODS-gr_qty
                  NO_TYPE_CHECK        = 'X'
                  ROUND_SIGN           = ' '
                  UNIT_IN              = /BIC/ODS-base_uom
                  UNIT_OUT             = 'GSU'
                IMPORTING
                  OUTPUT               = DATA_PACKAGE-gsu_qty
                EXCEPTIONS
                  CONVERSION_NOT_FOUND = 1
                  DIVISION_BY_ZERO     = 2
                  INPUT_INVALID        = 3
                  OUTPUT_INVALID       = 4
                  OVERFLOW             = 5
                  TYPE_INVALID         = 6
                  UNITS_MISSING        = 7
                  UNIT_IN_NOT_FOUND    = 8
                  UNIT_OUT_NOT_FOUND   = 9
                  OTHERS               = 10.
            endif.
          endif.
        endif.
        modify data_package.
      endloop.
    some how the AGSU qyt is not populating in the cube and when I dbug the code, I could see a clean record in the internal table but not in the cube.
    your suggestion and solutions would be highly appreciated.
    thanks,
    Swathi.

    Hi Swathi,
    May be you might want to look into the way the % is being calculated in the cube. If the formula involves counting the no. of records, then you will also be counting the -ve records that are posted in the cube unless you have had a compression on the cube. that might give you wrong numbers.
    Doniv

  • How can changes happened during the cube activation  be nullified.

    Hi all,
    I was trying to activate some business content infocube in the dev.server. I selectecd data flow before. In the process I collected all infoobjects associated with the cube and all the info-objects which are associated with that info-objects. When I installed the cube some of the customised business content info-objects associated with the cube got over written by the delivered version. We dont have the documentation which provides the information on which are all the infoobjects that were modified and which were not.
    Can any one give some idea how the changes happened during the cube activation can be nullified.Or how can I find out which were the info objects which were customised before business content was again activated and which are those changes.
    Regards,
    Anand

    Hi Anand,
    As long as you did not activate the Cube (= not activate BC, but cube itself)
    you can compare the changed cube with the active cube (Change cube screen, use button Version Comparison)
    Udo

Maybe you are looking for