Two Update Rules populating One Infocube

Hi all
Im a little confused:
1) I have to add a characteristic to an Infocube.Which I did and also assigned it to an appropriate dimension.
2)There are two update rules populating the Infocube.
3)The new charcteristic that ive added to the cube has to be populated using a routine.
My confusion is that to which update rule should i add the routine to?whats the deciding factor? how do i decide?
I would like to have more details and preferably any document which clarifies such scenarios.
Thanks

You can do it using both update rules or...
Find out which are the related characteritics and write the routine in that update rule:
Ex
Cube has
Project | Activity | Manager | Team Member | .....
Update rule 1 :
Project | Manager |...
Update rule 2:
Project | Activity | Team Member | ....
and the added characteristic is Project Status and it makes more sense to add it to update rule 1 rather than update rule 2...
my 0.02
Arun

Similar Messages

  • Transport of update rules from one BW system to another

    Hello all,
    SAP BW 7.0. Two systems: acceptance, development.
    We adjusted 4 old update rules between DSOs and InfoCubes in development system. Trying to transport it to acceptance system (transactions se01, STMS).
    Two update rules were transferred succesfully as executable. Other two were transferred as inactive. Overall transfer error code 8.
    Strange that when I select some of these update rule and push "check" button it says no errors. But in transport log errors exactly in checking and activating of these rules. Please if someone faced with such strange things suggest a solution.
    Want to add that rules are consistent, they are transported fully to acceptance. Proble just two are inective. In development they are active, of course.
    Activate after transport not an option. They must be transported as active, all 4.
    Appreciate any thoughts, thanks in advance,
    Pavel

    Hi ,
    My friend , kindly follow the steps
    Step1
    Analyze the transfer rules in development , check for any start routines if any , and also field routines , and also some Tables which are associated with the start routines.
    Step2
    In case if you find those , first transport those and collect it in a separate request and transport it
    Step3
    later collect a transfer rule request and go with Over write option ( please tell your BASIS guys )
    Hopefully your issue will be solved
    santosh

  • Rule incorrect error in the update rule of standard infocube

    hi,
    In the standard Appraisal infocube(BW 3.X)
    i have added a new keyfigure field  and written a rule in the update rule to populate datas. whn i checked for sytax errors, saved and return to the update rule screen it displays a red status for tht keyfigure. when i place the cursor on tht traffic light it show the tip as  'Rule Incorrect'
    wht may be the reason.
    do any one have ideas abt this.

    hi sathish,
    i couldnt get u.; i am not familiar with  BW since iam working in BI. could u pls tell the steps involved in adding a  new keyfigure field to a standard cube.
    Actually iam not mapping this field to any of the field from datasource. i am populating data thru rule based upon the characteristic fields of the datasource.
    r u suggesting to add the field in transfer structure level and write a transfer rule. how to add a new field in the transfer structure.

  • Error while copying Update rules from One Cube to other

    I am getting the following error message while I was trying to copy an existing update rule from an existing InfoCube to a New InfoCube. Has anyone experienced this before? Please let me know how to resolve this.
    Formula 3ZKQ....... (Object version M) could not be read.
    The new and original cubes are custom cubes.
    Thanks!

    Hi Vinod,
    Check the update rules for the original cube. Are they active? It appears that they contain a formula...check this too.
    Hope this helps...

  • Update rule from one Cube to another

    Hello Gurus!
    Here is the situation :-
    We have a IC ZCube1. This cube contains order data at schedule line level. It contians an IO  for each Hold Status (in all 10 ) . IO has value 'X' if it is active else blank. 1 order line item can have multiple holds.
    We need a aging report that should show how long particular line is on a Hold .
    Date of change of hold status is not in the cube ZCube1, it is in another ODS. We have created new cube(ZCube2) that will have Orderitem, Line#, DOC#...etc(as key field) and an IO for Hold status (here we have only one IO to hold all status code) and data of change of hold status (we will populate it from ODS ) .
    We have create start routine in ZCube2 that filter out order lines with no active Hold status. Also in this start routine we have logic to create 1 row for each hold status and store it in internal table(ITAB1). 
    Problem :
    Not able to understand how to proceed in update rule to insert multiple rows from  ITAB1 into ZCube2.
    We can  copy ITAB1  to ITAB2 and read it with Key fields. After this we have ITAB2 with multiple Hold status codes with same order item.
    Problem here is how do I assing multiple rows from ITAB2 in update rule to get multiple line item in ZCube2.
    Any thought or input to above said will be very helpful.
    Thanks,
    Murtuza.

    Hi Srinivas,
    I did some change , till earlier post I was trying to figure out how to Move source DP values to internal table.
    Eventually what I need is to Break each order line from source pacakge which contians multiple holds on same line into 1 orderline with only 1 hold status .
    e.g for a orderline if there are 3 hold Source DP will return 1 row . After I execute below code is start routine Source DP will have 3 order line everything same but hold status . I have done changes to the code in previous post and I am able to achieve what I need , but not sure this is efficient way to do ...
    Please advice .
    LOOP AT SOURCE_PACKAGE  ASSIGNING <SOURCE_FIELDS>.
    MOVE-CORRESPONDING <SOURCE_FIELDS> TO wa_ITAB_DP.
          IF <SOURCE_FIELDS>-/BIC/ZCSTATDM EQ 'X'.
            wa_ITAB_DP-/BIC/ZCSTATDM = 'X'.
            wa_ITAB_DP-/BIC/ZCSTATFH = ''.
            wa_ITAB_DP-/BIC/ZCSTATCC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSP = ''.
            wa_ITAB_DP-/BIC/ZCSTATFA = ''.
            wa_ITAB_DP-/BIC/ZCSTATFV = ''.
            wa_ITAB_DP-/BIC/ZCSTATNF = ''.
            wa_ITAB_DP-/BIC/ZCSTATPV = ''.
            wa_ITAB_DP-/BIC/ZCSTATIP = ''.
            APPEND wa_ITAB_DP to ITAB_DP.
          ENDIF.
          IF <SOURCE_FIELDS>-/BIC/ZCSTATFH EQ 'X'.
            wa_ITAB_DP-/BIC/ZCSTATDM = ''.
            wa_ITAB_DP-/BIC/ZCSTATFH = 'X'.
            wa_ITAB_DP-/BIC/ZCSTATCC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSP = ''.
            wa_ITAB_DP-/BIC/ZCSTATFA = ''.
            wa_ITAB_DP-/BIC/ZCSTATFV = ''.
            wa_ITAB_DP-/BIC/ZCSTATNF = ''.
            wa_ITAB_DP-/BIC/ZCSTATPV = ''.
            wa_ITAB_DP-/BIC/ZCSTATIP = ''.
            APPEND wa_ITAB_DP to ITAB_DP.
          ENDIF.
          IF <SOURCE_FIELDS>-/BIC/ZCSTATCC EQ 'X'.
            wa_ITAB_DP-/BIC/ZCSTATDM = ''.
            wa_ITAB_DP-/BIC/ZCSTATFH = ''.
            wa_ITAB_DP-/BIC/ZCSTATCC = 'X'.
            wa_ITAB_DP-/BIC/ZCSTATSC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSP = ''.
            wa_ITAB_DP-/BIC/ZCSTATFA = ''.
            wa_ITAB_DP-/BIC/ZCSTATFV = ''.
            wa_ITAB_DP-/BIC/ZCSTATNF = ''.
            wa_ITAB_DP-/BIC/ZCSTATPV = ''.
            wa_ITAB_DP-/BIC/ZCSTATIP = ''.
            APPEND wa_ITAB_DP to ITAB_DP.
          ENDIF.
          IF <SOURCE_FIELDS>-/BIC/ZCSTATSC EQ 'X'.
            wa_ITAB_DP-/BIC/ZCSTATDM = ''.
            wa_ITAB_DP-/BIC/ZCSTATFH = ''.
            wa_ITAB_DP-/BIC/ZCSTATCC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSC = 'X'.
            wa_ITAB_DP-/BIC/ZCSTATSP = ''.
            wa_ITAB_DP-/BIC/ZCSTATFA = ''.
            wa_ITAB_DP-/BIC/ZCSTATFV = ''.
            wa_ITAB_DP-/BIC/ZCSTATNF = ''.
            wa_ITAB_DP-/BIC/ZCSTATPV = ''.
            wa_ITAB_DP-/BIC/ZCSTATIP = ''.
            APPEND wa_ITAB_DP to ITAB_DP.
          ENDIF.
          IF <SOURCE_FIELDS>-/BIC/ZCSTATSP EQ 'X'.
            wa_ITAB_DP-/BIC/ZCSTATDM = ''.
            wa_ITAB_DP-/BIC/ZCSTATFH = ''.
            wa_ITAB_DP-/BIC/ZCSTATCC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSP = 'X'.
            wa_ITAB_DP-/BIC/ZCSTATFA = ''.
            wa_ITAB_DP-/BIC/ZCSTATFV = ''.
            wa_ITAB_DP-/BIC/ZCSTATNF = ''.
            wa_ITAB_DP-/BIC/ZCSTATPV = ''.
            wa_ITAB_DP-/BIC/ZCSTATIP = ''.
            APPEND wa_ITAB_DP to ITAB_DP.
          ENDIF.
          IF <SOURCE_FIELDS>-/BIC/ZCSTATFA EQ 'X'.
            wa_ITAB_DP-/BIC/ZCSTATDM = ''.
            wa_ITAB_DP-/BIC/ZCSTATFH = ''.
            wa_ITAB_DP-/BIC/ZCSTATCC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSP = ''.
            wa_ITAB_DP-/BIC/ZCSTATFA = 'X'.
            wa_ITAB_DP-/BIC/ZCSTATFV = ''.
            wa_ITAB_DP-/BIC/ZCSTATNF = ''.
            wa_ITAB_DP-/BIC/ZCSTATPV = ''.
            wa_ITAB_DP-/BIC/ZCSTATIP = ''.
            APPEND wa_ITAB_DP to ITAB_DP.
          ENDIF.
          IF <SOURCE_FIELDS>-/BIC/ZCSTATFV EQ 'X'.
            wa_ITAB_DP-/BIC/ZCSTATDM = ''.
            wa_ITAB_DP-/BIC/ZCSTATFH = ''.
            wa_ITAB_DP-/BIC/ZCSTATCC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSP = ''.
            wa_ITAB_DP-/BIC/ZCSTATFA = ''.
            wa_ITAB_DP-/BIC/ZCSTATFV = 'X'.
            wa_ITAB_DP-/BIC/ZCSTATNF = ''.
            wa_ITAB_DP-/BIC/ZCSTATPV = ''.
            wa_ITAB_DP-/BIC/ZCSTATIP = ''.
            APPEND wa_ITAB_DP to ITAB_DP.
          ENDIF.
          IF <SOURCE_FIELDS>-/BIC/ZCSTATNF EQ 'X'.
            wa_ITAB_DP-/BIC/ZCSTATDM = ''.
            wa_ITAB_DP-/BIC/ZCSTATFH = ''.
            wa_ITAB_DP-/BIC/ZCSTATCC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSP = ''.
            wa_ITAB_DP-/BIC/ZCSTATFA = ''.
            wa_ITAB_DP-/BIC/ZCSTATFV = ''.
            wa_ITAB_DP-/BIC/ZCSTATNF = 'X'.
            wa_ITAB_DP-/BIC/ZCSTATPV = ''.
            wa_ITAB_DP-/BIC/ZCSTATIP = ''.
            APPEND wa_ITAB_DP to ITAB_DP.
         ENDIF.
         IF <SOURCE_FIELDS>-/BIC/ZCSTATPV EQ 'X'.
            wa_ITAB_DP-/BIC/ZCSTATDM = ''.
            wa_ITAB_DP-/BIC/ZCSTATFH = ''.
            wa_ITAB_DP-/BIC/ZCSTATCC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSP = ''.
            wa_ITAB_DP-/BIC/ZCSTATFA = ''.
            wa_ITAB_DP-/BIC/ZCSTATFV = ''.
            wa_ITAB_DP-/BIC/ZCSTATNF = ''.
            wa_ITAB_DP-/BIC/ZCSTATPV = 'X'.
            wa_ITAB_DP-/BIC/ZCSTATIP = ''.
            APPEND wa_ITAB_DP to ITAB_DP.
          ENDIF.
        IF <SOURCE_FIELDS>-/BIC/ZCSTATIP EQ 'X'.
            wa_ITAB_DP-/BIC/ZCSTATDM = ''.
            wa_ITAB_DP-/BIC/ZCSTATFH = ''.
            wa_ITAB_DP-/BIC/ZCSTATCC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSC = ''.
            wa_ITAB_DP-/BIC/ZCSTATSP = ''.
            wa_ITAB_DP-/BIC/ZCSTATFA = ''.
            wa_ITAB_DP-/BIC/ZCSTATFV = ''.
            wa_ITAB_DP-/BIC/ZCSTATNF = ''.
            wa_ITAB_DP-/BIC/ZCSTATPV = ''.
            wa_ITAB_DP-/BIC/ZCSTATIP = 'X'.
            APPEND wa_ITAB_DP to ITAB_DP.
          ENDIF.
         CLEAR  wa_ITAB_DP.
    ENDLOOP.
    SOURCE_PACKAGE[] = ITAB_DP[] .

  • Counter in a cube with two update rules

    Dear experts,
    We are implementing a counter to count the occurrences of a characteristic. We are following the steps of the how-to document. But in our case, our cube where we have added the KF for the counter, has 2 update rules. Our question is which update rule shoud have the KF = 1. The characteristic we are going to count is mapped in both update rules.
    Thanks in advance,
    Inma

    Thanks for your answer but, if the same value of the characteristic I want to count comes from both update rules, will the counter value be 2? in my case, value of 2 would be wrong.
    Thanks,
    Inma

  • Add update rule for new key figure in one info struc

    Hi, everyone
    I would like to know how to add update rule for new key figure in one info struc.
    Thanks ahead.
    Eric

    1)I have created the update rule for one info structure
    2)add one key figure in the info structure due to business requirement
    3)then I use MC25 to add update rule for the new key figure, but I find that there no relevant menu to do such operation.
    Can anybody tell me how to do with it?
    Any answer will be appriciated.

  • Copying of Update Rules

    Hi,
    I need to copy the update rules. Let me explain the requirement:
    The standard business content in SD provides the update rules from InfoSource 2LIS_12_VCHDR to InfoCube 0SD_C03.
    We have created an ODS (ZSD_O01) on the InfoSource 2LIS_12_VCHDR, with the one-to-one field mapping in the update rules.
    As a result, the update rules from ODS ZSD_O01 to InfoCube 0SD_C03 are exactly identical to the Business Content Update rules between the InfoSource 2LIS_12_VCHDR and InfoCube 0SD_C03.
    Can I copy (All) the update rules "between the InfoSource 2LIS_12_VCHDR and InfoCube 0SD_C03" and paste them for the update rules "from ODS ZSD_O01 to InfoCube 0SD_C03" ??.
    If you right-click on any individual update rule line (Go to Change Update rules), you see two options: 1. Copy Rule (F6), 2. Copy Update Rules (Ctrl + F12). What is the purpose of these two?
    Regards,
    Milind

    Hi,
    I hope update rules can be copied only if they are based on same Datasource.
    For example if you want to copy update rules for Cube1 to cube2 it can be done only if these two cubes are based on same ODS or Infosouce.
    Also check some of the similar thread..
    Copy update rules from one InfoSource to another one
    Copy Update Rules
    Regards,
    Prema

  • Unable to map Update Rule with u201CMaster data attribu201D option

    Hi,
    Does anybody know the reason why sometimes, in update rules to an ODS, I cannot map an InfoObject with the option u201CMaster data attribu201D?
    I have the characteristic in the ODS, and for another update rule, to the same ODS, I am able to map this field correctly, but for a specific rule, the u201CMaster data attribu201D field appears in blank when I press F4.
    Strange this behaviouru2026
    Can anybody help me with this issue?
    Thanks,
    Best Regards,
    Joana

    Hi  Shanthi,
    I didn't insert the InfoObject as an InfoProvider.
    The problem is that I have two update rules for the same ODS object. For one I can map the characteristic correctly, and for the other, when I press F4 in the "Master Data Attrib", no characteristics appear.
    Thanks,
    Joana

  • Navigation attributes in Updates Rules.

    Hi,
    I´d like to know if it is possible to use a navigation attribute of one InfoCube in the update rule of other InfoCube. For example, i am trying to consolidate some date using the 0Customer attibute 0City, but when i create a new update rule to my InfoCube the only object avaible is 0Customer, its navigation attribute (0City) is unavaible in the Update rule.
    Thanks.

    Hi Luiz,
    check the "Master Data Attribute of" update method in the help link below and see if it does what you need:
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a64e0e07211d2acb80000e829fbfe/frameset.htm

  • Self Update Rule

    Hi all:
           I have a problem in self update rule loading.Actually i have ODS ZOMS001 and for this i have
    two update rules.One update rule is 2LIS_02_SCN and other update rule is 8ZOMS001(Self update rule).During initialise for SCN it takes 3 min and for self update rule 8ZOMS001 it takes 3 mins.During Delta loading for self update rule 8ZOMS001 ,even if i have 1 records(in delta) it takes whole records in ODS and timing goes for 20 mins.But it update only one record in ODS.
          Anyone suggest how can i go for delta records only for self update rule.How can i will minimize the time sequence for self update rule delta loading?.
    This issue stops my proj.Pls give me input.
    Thanks in advance.
    Rgds
    MSK.

    Hello,
    You should also take note that your delta will be a continous loop of changes...since you are updating itself, the loop to itself will produce changes and will continually create change records....so you will always get the same changes..
    For instance,
    Init.
    First delta from 2LIS_02_SCN. (Change log updated)
    That delta goes to itself. (Change log updated)
    Second delta from 2LIS_02_SCN. (Change log updated)
    That delta goes to itself, with changes from first delta to itself and second delta...)
    This continually gets bigger and bigger....
    It is  a continous loop that you will never get out of...
    Be careful in this situation.

  • Update rule key figure problem

    Hello All,
    I am busy creating update rules for an InfoCube. I have defined the update type for the key figure as "addition", I have also selected the source key figure (Budget Volume APO PC) but get the message "Target unit and source unit for the key figure Budget Volume APO PC must be the same" and it gives a red status to the key figure. Please explain what I should do to rectify the problem?
    Thank you and kind regards,
    Keith

    Hello KeItH,
    how r u ?
    first analyze the InfoObject and then if it is not going to be added up for the result value then u can try selecting OVERWRITE option, but this will overwrite your old values and hold the latest one.
    Best Regards....
    Sankar Kumar

  • What is update rules

    Hi All,
            can anyone tell me what is update rules with one practicle example . i have gone through materials but i am not getting it  what happens when we do cleansing between transfer structure to the target.
    Edited by: Mohit Shrivastava on Jan 2, 2009 2:09 PM

    Hi Mohit,
    Actually update rules comes in BIW 3.5 now this concept has been removed from BI7
    DEFN:Update rules specify how the data (key figures, time characteristics, characteristics) is updated to data targets from the communication structure of an InfoSource. You are therefore connecting an InfoSource with a data target
    the data From infosource(Infosource means collection of information that logically belongs together gathered in to single unit)  to target is sent through this update rules
    An update rule must be specified for each key figure and the corresponding characteristics of the InfoCube. For an ODS Object, it must be specified for the data and key fields, and for an InfoObject it must be specified for the attribute and key fields
    the real senarrio example means ,
    suppose ur getting data  of quantity(XYZ,ABC) sold for this year ,from flatfile and from SAP source system .. in the final report u want to see the overall sales of that quantity the data of both source system can be combined infosource , in the report if u want to see only XYZ data then the target has to have data of XYZ only but in the infosource both XYZ and ABC data both are avaliable ..
    u can avoid the data of ABC in update rules (by writing program) this is one senario the use of pdate rules
    Hopes this information help  u ..if yes assigin points to this thread
    Regards,
    Gurudatt

  • Key Figure missing in update rules

    Hi All,
    A Key figure is missing in Update rule of ODS & Infocube.
    But it is listed in infosource ( comm. & transfer structure) of ODS.
    Why it is so . Any suggestions.
    infosource->ODS_>infocube.
    Please help me.
    Edited by: anand k on Mar 24, 2008 12:16 PM

    Hi,
    I will give the process that I followed (as you specified) now:
    1. I deleted the Source System Assignment for the Infosource.
    2. Next went to Source Systems. Right click on source system and replicate it.
    3. Select the InfoSoucre and assign the Data Source.
    4. Here I automatically got the Field(ZZMBGBTR).
    5. I added the field in the Communication Structure. and then assigned the Transfer Rules.  Next activated the InfoSource.NExt checked the InfoCube for the KeyFigure. That InfoObject ZQTY is available.
    6. I activated the InfoCube. Right Click and select Create Update Rules. Still I didnt got that InfoObject.
    Regards
    Jay

  • "update rules inactive " error when importing transport request

    Hi experts,
    I am stuck while importing transport request of update rules. I am moving transport request of update rules from 1 system to another and stuck while importing it in 2nd system. Only two update rules are stuck among all giving an error of "inactive update rules".
    I have again tranported it twice after activating theose two update rules.
    Please help!!!!!

    Hi Heena,
    Can you provide more details of the issue like is it a DSO to DSO transformation, error message etc.

Maybe you are looking for