Restrict Update Rule from Re-install

We've modfied SAP delivered update rules to add our own start routines and mapping. Since update rules are non-mergeable objects in business content installation, they gets overwritten with business content delivered version if someone re-installs the update rules. Is there any way we can restrict from allowing user to re-installing the update rule? Is there any BAPI or user exit available throught which I can restrict installation of specifc update rules? Any inputs are appreciated.
Thanks,
Milind

Since you have your own routines, the best thing is to keep this as the custom update rules and leaving the content one untouched.
Ravi Thothadri

Similar Messages

  • Activate Update Rules from Business Content

    Hello,
    I am trying to install 0QM_C10 from business content. Every thing works fine except there are no update rules (there are 3 info sources for this cube). I am new to this and it doesn't make sense for me to manually create (ofcourse the system does the proposal) update rules. Since that is lot of work. I was expecting some transaction / tool where I can activate the update rules from the Business Content (since I can see the update rules in the business content under "Display Description". Is there any tool like that?
    Or, am I doing some thing wrong so the update rules are not automatically installed from the business content along with Cube and info sources?
    Note: I did separate installation for cubes as well as info sources from business content using Grouping by "Only necessary objects" option.
    Thanks in advance.
    Bala
    Message was edited by: Bala Lingamaneni
    Message was edited by: Bala Lingamaneni

    Bala,
    please don't uncheck the checkbox that you find when you open a new thread (let it as default!)...this is the only way to be able to assign points to your helper !
    Write a request (as a normal post) into SDN Suggestion forum in which you ask to Marc Bernard or Mark Finnern to convert this post as question !
    Bye,
    Roberto

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

  • How to debug start routines of update rules from ODS to InfoCube

    Dear gurus,
      I have an update rule from ODS to InfoCube. I wrote a start routine in the update rule. Now I want to debug it. I went to monitor and simulate update the data package and only got the prompt "No data exists in the corresponding PSA table". So how can I debug this start routine?
      Thanks in advance.
    Jin Ming

    Jin,
    In order to use PSA between ODS and InfoCube, you may have to use an exclusive InfoPackage and load separately. In that InfoPackage, choose the radio button to use a PSA.
    I think you are currently updating the InfoCube directly without using a separate InfoPackage.
    Look for an InfoSource under DataMarts (search for 8<ODS Technical name>) and create your InfoPackage there.
    Good luck.

  • Error while copy of Update Rules from ODS 0SD_O03 to InfoCube 0SD_C13

    Hi all,
    I work on a NW04s SPS9 System I would like to simply copy Update Rules (from an ODS to an InfoCube) from the BCT to the 1:1 Z-Copies of these Objects.
    To do so, I copied the InfoProviders 0SD_O03 and 0SD_C13 to Z-Versions. In SAP BCT the InfoCube is updated from the ODS. The ODS itself is updated from InfoSource.
    After successfully copying the two InfoProviders as next step I tried to copy the Update Rules from the Content version Objects to the Z-Version Objects to link them.
    Similar to copying update rules in 3.5 I tried
    - right click on "ZSD_C13"
    - choose Additional Functions - Create Update Rules"
    - choose DataSource: ODS Object "ZSD_O03"
    - choose Copy from: InfoCube "0SD_C13"
    This result in the error "0SD_C13 is not suitable as a template for copying update rules".
    Some hints that might help:
    1. The very same error occurs if I try to copy the Update Rules from 0SD_O03 to 0SD_C13.
    2. I also tried to copy both Update Rules (to C12 & C13) on a BW 3.5 system where it worked fine: The update rules from both Z-ODSs to both Z-Cubes were copied correctly 1:1 and without any errors.
    3. In the NW04s System I was able to copy the Update Rules from the InfoSource 2LIS_11_VAITM to 0SD_O01 (as well as from 2LIS_11_VAHDR to ODS 0SD_O03). So I only cannot copy Update Rules from ODSs to InfoCubes while it is possible to copy Update Rules from InfoSources to ODSs.
    4. During copy of 0SD_O03 the system warned: "InfoObject 0FISCVARNT needs to be in key for DataStore object ZSD_O03". No matter whether I move this IO to the keys of the Z-ODS, the Update Rules copy does not work.
    - This warning does not show up on BW3.5 when I copy the very same ODS. Can anyone explain this?
    - This warning is not displayed during the copy of ODS 0SD_O01, just for 0SD_O03.
    5. Obviously during a preceding test I actually must have been able to copy the Update Rules for another copy of 0SD_C13 (as I can see the Update Rules in the SAPGUI). I stopped this first test as I was not able to do the Update Rules copy for 0SD_C12.
    Yet as of today I cannot copy Update Rules this for both cubes 0SD_C13 as well as 0SD_C12. So yesterday there was no error on copying the Update Rules to InfoCube ZSD_C13, but today there is. To my knowledge nothing has been changed in the System Setup / Customizing in the mean time.
    6. For both cubes ZSD_C13 as well as ZSD_C12 it is possible to copy Update Rules that map from the BCT ODS to the Z-InfoCbes. So I can copy Update Rules from 0SD_O03 to ZSD_C13 and from 0SD_O01 to ZSD_C12. This would point in the direction that the copied ODSes are the source of this behavior?
    I am not sure whether this is a special NW04s behavior and how to use it correctly so the Update Rules can be copied.
    Please could you help on how to copy these Update Rules in NW04s or share your experience if you had similar?
    Thanks a lot,
    Werner

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

  • Copy Update Rule from Business Content

    Hi All,
    Currently I have activated some standard BI Content E.g. InfoCube 0FIAR_C03, DSO 0FIAR_O03, InfoSource 0FI_AR_4 and all the corresponding update rules.
    Now I have copied both InfoCube and DSO into another customized version E.g. ZAR_C03 and ZAR_O03. I managed to copy the same update rule from InfoSource 0FI_AR_4 to ZAR_O03 using the template but I don't have the option of copying the same update rule from ZAR_O03 to ZAR_C03 using the same update rule of 0FIAR_O03 to 0FIAR_C03.
    I know I have the choice to manually re-create all the details but is there any other workaround?
    Please read through carefully my question. I have seen some forum asking to load data from 0FIAR_O03 to then ZAR_O03 then so forth.
    Purpose of doing the above method is because I want to remain the business content as what it is and just to copy it to Z version for customization.
    Thanks
    David Yee

    Hi All,
    Is there any other second opinion related to this issue before I close the question?
    Thanks
    David Yee

  • "Old" update rule from ODS not working

    Hi Gurus,
    I need to set up the "old" fashioned update rule to load data from an ODS1 to another ODS2.
    The thing is that I need to set up an update rule because I need to implement a Return Table Routine that is not supported (as far as I know) by the new Transformation/DTP.
    When I select option (through the right mouse click over ODS1)  "Other Options" - "Create Update Rule" it takes me out of the RSA1 and leaves me in the main menu making it impossible to create a new update rule.
    The strange thing is that I have this working from and ODS to an InfoCube.....
    Suggestions, a workaround??
    Andrea.

    Hi Jerry,
    Just to confirm that this is not working. The tys_TG_1 structure only shows me the target infoprovider structure. Check that in the how to, to be able to derive employee first you need to assign eache source_filed to the result_field leaving employee blank.
    I need to have in the same place, the source_field structure (source infoprovider field structure) and the result_field structure (target infoprovider structure). That is what the "old" return table gives me as in the same place I can have the communication_structure (source infoprovider field structure) with the return_table structure (target infoprovider structure). 
    Just to understand, in the source infoprovider I have 12 Key Figures (1 for each period) and I have to split each incoming record to 12 records. If I work only with the result_field structure tys_TG_1 and the result_package tyt_TG_1 I'm not able the see those 12 KF.
    So... return table functionality is not fully supported by BW 7 as far as I know.
    Any other ideas why I'm not able to create the old Update Rules from an ODS?
    Regards,
    Andrea.

  • Update rules not getting installed from business content.

    Hello,
    One more major issue I am seeing is that my update rules for some cubes (0PUR_C01)are not getting installed at all from business content and the errors i am getting are like datasource 0vendor_text not maintained and then there is long list of such red lights. when actually I can see most of the datasources active in the datasource tab on BW side.
    So i dont know how to get these update rules working.
    Please advice,
    Thanks

    Hi Mukund,
    please see also the answer that I provided to your thread
    <a href="https://forums.sdn.sap.com/thread.jspa?threadID=121274&tstart=0">Strategy toward new and 3.x datasource / infosource</a>
    In addtion, you might want to check
    <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/84/497e4ec079584ca36b8edba0ea9495/content.htm">help.sap.com DataWarehouse</a>
    and the online documentation for more general information about data modeling / acquisition.
       Cheers
          SAP NetWeaver 2004s Ramp-Up BI Back Office Team

  • Simple creation of Update Rule from BW Data Source

    Hi guys,
       Pertaining standard SAP Business Content extractors
       I am referring to <b>InfoCube : 0PA_C01(Headcount and Personnel Actions)</b>
       I am attempting to<u> create </u>an <b>Update Rule</b> from <b>Info Source : 0HR_PA_PA_1(Headcount)</b>
       This <b>Info Source : 0HR_PA_PA_1(Headcount)</b> is connected to <b>BW Data Source</b>(Not R/3!) 0HR_PA_PA_1
       I have created an Info Package for this Info Source and managed to get 15 records{In Contrast to my 68800 Records from Info Source : 0HR_PA_0(Employee)}
       So, when I create an Update Rule to Connect <b>Info Cube: 0PA_C01(Headcount and Personnel Actions)</b> to <b>Info Source to Info Source : 0HR_PA_PA_1(Headcount)</b>, I get the following error
    ERROR : <b>IC=0PA_C01 IS=0HR_PA_PA_1 error when checking the update rules</b>
      Could you please also advice, why do I only get 15 records for Data Source 0HR_PA_PA_1 ?
      P/S : I am on BW 3.5

    Hey Rohini,
       This <b>Data Source: 0HR_PA_PA_1(Headcount)</b> is tricky to me because it`s a BW Data Source.
       Exact Error Message is as follows :-
      "<b>Error Message : RSAU461
        IC=0PA_C01 IS=0HR_PA_PA_1 error when checking the update rules</b> "
       My Exact Problem is that I don`t see any values for the following fields in my Info Cube : 0PA_C01(Headcount and Personnel Actions)
      Country;
      Country Code;
      Gender;
      Nationality;
      Language;
      Postal Code;
      Region;
      Position;
      Job;
      Payroll Area;
      Payroll Group;
      Pay Scale's;
      Pay Grade's
      This is because, this information is supplied by InfoSource : 0HR_PA_PA_1
      But I don`t have an Update Rule for this InfoSource in my InfoCube : 0PA_C01
      So, that's why I am attempting to create this additional Update Rule
    <i>  And also, could someone enlighten me why would SAP not include such a standard Update Rule when they have already idenfied those needed fields in a Cube ? This is suppose to be a STANDARD workable Business Content right ?</i>
      P/S: I have applied Note : 336229

  • Update rule from attribute

    Hi, my problem may be simple to solve, but I dont know too much ABAP so need some help.
    I want to populate Cost Center in my cube by mapping it to Responsible Cost Center (attribute of Order Number).
    How can I do that?
    Thanks,
    Frank

    Hi Frank,
    Insert Cost Center in Communication Structure and then in Start Routine of Update Rules insert this code (substitute definition with the IO code, cut off '0'):
    data: begin of t_costcent occurs 0,
    costcenter like /BI0/Pcostcenter-costcenter,
    responsible like /BI0/Pcostcenter-responsible,
    end of t_costcent.
    select * into corresponding fields of table t_costcent
    from /BI0/Pcostcenter where  objvers = 'A'.
    loop at DATA_PACKAGE.
    read table t_costcent with key
    responsible = DATA_PACKAGE-responsible
    if sy-subrc = 0.
    DATA_PACKAGE-costcenter = t_costcent-costcenter.
    modify DATA_PACKAGE.
    endif.
    endloop.
    Ciao.
    Riccardo.

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

  • Reg: 0PUR_C01 - Update Rule - Not Getting Installed

    Dear friends
    I am trying to activate MM Cube (0PUR_C01)
    But when collecting dependent objects for 0PUR_C01 with data flow before option, Once collection over, system throws the following message
    1.             Object 0DB87SIC1 (InfoObject,IOBJ) could not be collected for object 0PUR_C01 (InfoCube,CUBE)
    2.     Object 0DBGUDUNS (InfoObject,IOBJ) could not be collected for object 0PUR_C01 (InfoCube,CUBE)
    3.     Object '0DB87SIC1' (IOBJ) of type 'InfoObject' is not available in version 'D'     
    4.     Object '0DBGUDUNS' (IOBJ) of type 'InfoObject' is not available in version 'D'     
    And also, I could able to see the following long text error message.
    1.     You have collected objects in the BI Metadata Repository. Associated objects for object 0PUR_C01 of type InfoCube, CUBE have also been collected. Object 0DB87SIC1 of type InfoObject,IOBJ was among these objects
    2.     However, this object 0DB87SIC1 of type InfoObject,IOBJ is not available in the metadata repository
    3.     If this error occurs while you are installing BI Content, an error may have occurred during the delivery. Inform SAP. In all other cases, check that the object has not been deleted by another user during collection.
    I tried to install those collected objects, the cube alone gets installed and visible in workbench. Update Rules are not getting installed. Even after,I have collected the update rule separately and tried to install lot of times, no luck for me
    eventhough the job has been successful
    If anybody came across this type errors, Please guide me to solve that
    Points will be awarded for the right answers.
    Regards
    Raju Saravanan

    hi raju
    1. Object 0DB87SIC1 (InfoObject,IOBJ) could not be collected for object 0PUR_C01 (InfoCube,CUBE)
    2. Object 0DBGUDUNS (InfoObject,IOBJ) could not be collected for object 0PUR_C01 (InfoCube,CUBE)
    3. Object '0DB87SIC1' (IOBJ) of type 'InfoObject' is not available in version 'D'
    4. Object '0DBGUDUNS' (IOBJ) of type 'InfoObject' is not available in version 'D'
    u just ignore this errors and install. this wont affect.
    u just try again colllecting the cube and collect it "befroe and after"
    u wld get the update rules for the following datasources
    2LIS_02_ITM
    2LIS_02_S012
    2LIS_02_SCL
    Regards
    Dina

  • Cannot Create Update Rule from Infosource to Cube

    Hello;
    I am a beginner to BI and am learning. This may be a very basic question, but I got stuck.
    In the create update rule screen, I get an error message that says
    Data Source (whatever the name is) not maintained. (check your entries)
    Could some one help as to where I went wrong?
    Thx,
    Sushma
    Su

    Goto your InfoSource and open DataSource Structure and transfer structure. Check if the structure is correct, make the necessary changes if required and activate it. Then create update rules providing correct infosource name. Until you create /activate your transfer structure, you won't be able to create update rules.
    Reward point if helps.
    Regards,
    Ashok
    Message was edited by:
            ashok saha

  • 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

  • Map My Update Rule from a Master Data Attribute

    Hello experts,
    I haven't tried this scenario yet, hope you can help me, the Issue is this
    I have 2 InfoObjects ZPSCHRCHY and 0PROFIT_CTR from InfoCube WBS cost and allocations I want both the InfoObjects to be mapped to 0PROFIT_CTR attribute of 0WBS_ELEMT master data object, I have tried the Master Data Attribute but only 0PROFIT_CTR is an attribute of the Master Data.how can I mapped ZPSCHRCHY and 0PROFIT_CTR to 0PROFIT_CTR?, Is creating a start routine for it must be used? Thank you very much
    Regards and Thanks
    Chris

    PROGRAM UPDATE_ROUTINE.
    $$ begin of global - insert your declaration only below this line  -
    TYPES:
    BEGIN OF r_MD_WBS_ELEMENT,
       WBS_ELEMT  like /BI0/PWBS_ELEMT-WBS_ELEMT,
       OBJVERS    like /BI0/PWBS_ELEMT-OBJVERS,
       PROFIT_CTR like /BI0/PWBS_ELEMT-PROFIT_CTR,
    END of r_MD_WBS_ELEMENT.
    DATA: t_MD_WBS_ELEMENT  TYPE STANDARD TABLE OF r_MD_WBS_ELEMENT,
           wa_MD_WBS_ELEMENT TYPE r_MD_WBS_ELEMENT.
    $$ end of global - insert your declaration only before this line   -
    The follow definition is new in the BW3.x
    TYPES:
      BEGIN OF DATA_PACKAGE_STRUCTURE.
         INCLUDE STRUCTURE /BIC/CS8ZPSG030.
    TYPES:
         RECNO   LIKE sy-tabix,
      END OF DATA_PACKAGE_STRUCTURE.
    DATA:
      DATA_PACKAGE TYPE STANDARD TABLE OF DATA_PACKAGE_STRUCTURE
           WITH HEADER LINE
           WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
    FORM startup
      TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
               MONITOR_RECNO STRUCTURE RSMONITORS " monitoring with record n
               DATA_PACKAGE STRUCTURE DATA_PACKAGE
      USING    RECORD_ALL LIKE SY-TABIX
               SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
      CHANGING ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
    $$ begin of routine - insert your code only below this line        -
    fill the internal tables "MONITOR" and/or "MONITOR_RECNO",
    to make monitor entries
      REFRESH: t_MD_WBS_ELEMENT.
          SELECT WBS_ELEMT
                 OBJVERS
                 PROFIT_CTR
          INTO TABLE t_MD_WBS_ELEMENT
          FROM /BI0/PWBS_ELEMT
       FOR ALL ENTRIES IN DATA_PACKAGE
         WHERE WBS_ELEMT   = DATA_PACKAGE-WBS_ELEMT.
        IF sy-subrc EQ 0.
        Do nothing
        ENDIF.
    if abort is not equal zero, the update process will be canceled
      ABORT = 0.
    $$ end of routine - insert your code only before this line         -
    ENDFORM.

Maybe you are looking for