WBS Hierarchy settings

Hi Experts,
From file  WBS elements is Created  using BAPI  'BAPI_BUS2054_CREATE_MULTI'    , Wbs is created successfully  . But problem is , when I check that WBS elements  in CJ20N , the WBS element are not in correct Hierarchy  as i created from file ,  they are in descenting order but  requirement is ascending order.
Please suggest me what to do on this  , Is there any setting required in CJ20N  or any change require in program.
Thanks
Susant

Hi Ashwini,
You probably solved this issue by now already. But here's the solution:
Line 5 and 6 are inconsistent. Since the WBS_ELEMENTS .LMA$D and LSA$D have different UPs, you cannot referr them with LEF/RIGHT. LEFT and RIGHT should be empty for lines 5 and 6.
Kind regards,
Pascal

Similar Messages

  • Solution for inheritage of user statuses in a WBS hierarchy

    In a SAP 4.6C system I have set-up a specific user status profile for the WBS-hierarchy of a project. The intention is that at the highest WBS-level the user-status is changed manually and that the statuses of the lower WBS-elements will be changed automatically (just like the system statuses). As far as I know
    this is not standard SAP and has to be developed
    Is there anyone who has dealt with the same problem? How do you have handled this: user-exits, substitution etc.?
    I hope somebody can help me.
    Regards,
    Paul

    Dear Hensgens
    You might know that as of release 4.70 the functions 'set & pass user status'
    and 'revoke & pass user status' are part of the standard.
    Please refer to note 486765.
    There is the possibility to do a downgrade of this functionality, we are aware that other customers have done so.
    Regards
    Martina

  • Impossible to search in WBS Hierarchy

    Hello,
    We are using the standard WBS Hierarchy [WBSH] on master data 0WBS_ELEMT.  In Query Designer, when we want to perform a restriction of values on a particular WBS Hierarchy node, using Search fonctionnality in restrict menu, it is impossible to find any values. Can someone help on this issue? This kind of selection is perfectly working on Cost Centre or Cost Element hierarchies
    We are in BI 7.0
    Regards

    Hi,
    Just check if the object is having that hierrachy loaded/maintained and activated. Load/Maintain and activate the same. Check this at object level first in RSA1/RSH1/RSD1. If everything is fine at object level then check in query designer.
    All activated and loaded/maintained hierarchies can be viewed for that object in query designer. (When you are serching use the exact name which is being loaded/maintained at object level
    I hope it will help.
    Thanks,
    S

  • Settlement Rules in WBS Hierarchy

    Hello,
    I have a scenario, where there is a WBS hierarchy. Now the situation is such that client wants each WBS to be settled to different Account assignment categories such as G/L, Cost Centre, PSG, and a combination of 3 (35%,35%,30%). In this case what will happen to the cost that is at top WBS/Project defn?
    Also can I have one settlement profile which will have all the above as valid receivers or do I need to have seperate settlement profiles?
    Secondly if I maintain a statistical account assignment ( for example a cost centre) in the detailed screen, with main receiver as G/L, will the statistical cost be seen against that CC?
    Thanks
    Shiv

    you usually post at the lower level WBS elements so do not worry about the highest level - even if you did make a posting the settlement would take care if it
    you can have one settlement profile with different receivers - just make sure that your settlement configuration is correct
    you will need to check this yourself - I think that applies to profit centre but not cost centre

  • To suppress "WBS HIERARCHY" for every WBS Element Node

    Hi All,
    Below are WBS nodes in the report. For every node, "WBS HIERARCHY" is repeating.
    WBS HIERARCHY
    C-11-5210
    WBS HIERARCHY
    C-11-5214
    WBS HIERARCHY
    C-11-5216
    WBS HIERARCHY
    C-11-8521
    WBS HIERARCHY
    C-15-1000
    Is there any way to suppress this, so that I can get output as follows?
    WBS HIERARCHY
    C-11-5210
    C-11-5214
    C-11-5216
    C-11-8521
    C-15-1000
    Thanks in advance!
    Ketan Zare

    Hi Amer,
    This is required in Analyser. But where do I find this setting in query designer?
    Thank you,
    Ketan Zare

  • WBS Hierarchy Logic build up with dynamic values

    Hello ABAP Crew.
    I currently using BAPI_PROJECT_MAINTAIN, and I have to pass I_WBS_HIERARCHIE_TABLE with the hierarchy table made by me.  Does anyone have a logic on how to do this from values within a table?
    Here are the values coming from a proxy:
    111520
    111520-111234
    111520-111234-19
    111520-111234-19-1
    111520-111234-19-2
    111520-111234-20-1
    111520-111234-20-4
    The purpose is to place this into the table of I_WBS_HIERARCHIE_TABLE in the UP DOWN LEFT RIGHT  format. 
    Now the problem is, the list of values received will always be different.
    Thanks.

    Hi Jotorres,
    Did you get a response for this question about WBS hierarchy logic build up with dynamic values? I have been trying to build it up myself, but its getting increasingly difficult. I wanted to know how you resolved this issue?
    Thanks a dozen !
    Regards
    Aradhana

  • WBS hierarchy not working in BAPI_PROJECT_MAINTAIN

    I have created the following code. Before I added the section for the hierarchy table the structure was created ok, but with all WBS elements at level 1.
    Now I have added the entries into the hierarchy table I am getting an error when I run BAPI_PROJECT_MAINTAIN.
    The error message is CN 189 E - A reference object cannot be entered for the method 'Update'
    I'd appreciate it if someone can see what I have done wrong.
    Many thanks
    Karen
    Code **
    wa_method_project-REFNUMBER = '00001'.
    wa_method_project-OBJECTTYPE = 'WBS-Element'.
    wa_method_project-METHOD     = 'Create'.
    wa_method_project-OBJECTKEY = wbs1.
    append wa_method_project to i_method_project.
    wa_method_project-REFNUMBER = '00002'.
    wa_method_project-OBJECTTYPE = 'WBS-Element'.
    wa_method_project-METHOD     = 'Create'.
    wa_method_project-OBJECTKEY = wbs2.
    append wa_method_project to i_method_project.
    wa_method_project-REFNUMBER = '00003'.
    wa_method_project-OBJECTTYPE = 'WBS-Element'.
    wa_method_project-METHOD     = 'Create'.
    wa_method_project-OBJECTKEY = wbs3.
    append wa_method_project to i_method_project.
    move-corresponding t_bid_definition to wa_WBS_ELEMENT_TABLE.
    wa_WBS_ELEMENT_TABLE-PROJ_TYPE = 'BD'.
    wa_WBS_ELEMENT_TABLE-WBS_ACCOUNT_ASSIGNMENT_ELEMENT = 'X'.
    wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs1.
    wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                      t_bid_definition-PROJECT_DEFINITION.
    wa_WBS_ELEMENT_TABLE-DESCRIPTION = t_bid_definition-DESCRIPTION.
    append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
    wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs2.
    wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                      t_bid_definition-PROJECT_DEFINITION.
    wa_WBS_ELEMENT_TABLE-DESCRIPTION = 'WBS description 1'.
    append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
    wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs3.
    wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                      t_bid_definition-PROJECT_DEFINITION.
    wa_WBS_ELEMENT_TABLE-DESCRIPTION = 'WBS Description 2'.
    append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
    clear wa_WBS_ELEMENT_TABLE.
    wa_project_definition_upd-project_definition =
                                        t_bid_definition-PROJECT_DEFINITION.
    append wa_project_definition_upd to i_project_definition_upd.
    wa_method_project-METHOD     = 'Save'.
    append wa_method_project to i_method_project.
    clear: wa_method_project.
    This is the section I added that stopped the thing working *****************
    Create correct WBS Hierarchy
    wa_method_project-OBJECTTYPE = 'WBS-Hierarchy'.
    wa_method_project-METHOD     = 'Create'.
    append wa_method_project to i_method_project.
    clear: wa_method_project.
    wa_wbs_hierarchie_table-WBS_ELEMENT = wbs1.
    wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                      t_bid_definition-PROJECT_DEFINITION.
    wa_wbs_hierarchie_table-DOWN = wbs2.
    append wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
    clear wa_wbs_hierarchie_table.
    wa_wbs_hierarchie_table-WBS_ELEMENT = wbs2.
    wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                      t_bid_definition-PROJECT_DEFINITION.
    wa_wbs_hierarchie_table-UP = wbs1.
    wa_wbs_hierarchie_table-RIGHT = wbs3.
    append wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
    clear wa_wbs_hierarchie_table.
    wa_wbs_hierarchie_table-WBS_ELEMENT = wbs3.
    wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                      t_bid_definition-PROJECT_DEFINITION.
    wa_wbs_hierarchie_table-LEFT = wbs2.
    append wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
    clear wa_wbs_hierarchie_table.
    CALL FUNCTION 'BAPI_PROJECT_MAINTAIN'
      EXPORTING
        i_project_definition               = t_bid_definition
      tables
        i_method_project                   = i_method_project
        I_WBS_ELEMENT_TABLE                = I_WBS_ELEMENT_TABLE
        I_WBS_HIERARCHIE_TABLE             = i_wbs_hierarchie_table
        E_MESSAGE_TABLE                    = i_bapi_message.

    Here is the final code.
    The Project Definition is created before you do this bit using BAPI_PROJECTDEF_CREATE which is where the entries for t_bid_definition come from.
    I hope this helps
    Karen
    data: wbs1 type ps_posid,
          wbs2 type ps_posid,
          wbs3 type ps_posid.
    clear: wbs1, wbs2, wbs3.
    wbs1 = 'WBS1'.
    wbs2 = 'WBS2'.
    wbs3 = 'WBS3'.
    wa_method_project-REFNUMBER = '00001'.
    wa_method_project-OBJECTTYPE = 'WBS-Element'.
    wa_method_project-METHOD     = 'Create'.
    wa_method_project-OBJECTKEY = wbs1.
    append wa_method_project to i_method_project.
    clear: wa_method_project.
    wa_method_project-REFNUMBER = '00002'.
    wa_method_project-OBJECTTYPE = 'WBS-Element'.
    wa_method_project-METHOD     = 'Create'.
    wa_method_project-OBJECTKEY = wbs2.
    append wa_method_project to i_method_project.
    clear: wa_method_project.
    wa_method_project-REFNUMBER = '00003'.
    wa_method_project-OBJECTTYPE = 'WBS-Element'.
    wa_method_project-METHOD     = 'Create'.
    wa_method_project-OBJECTKEY = wbs3.
    append wa_method_project to i_method_project.
    clear: wa_method_project.
    move-corresponding t_bid_definition to wa_WBS_ELEMENT_TABLE.
    wa_WBS_ELEMENT_TABLE-PROJ_TYPE = 'XX'.
    wa_WBS_ELEMENT_TABLE-WBS_ACCOUNT_ASSIGNMENT_ELEMENT = 'X'.
    wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs1.
    wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                        t_bid_definition-PROJECT_DEFINITION.
    wa_WBS_ELEMENT_TABLE-DESCRIPTION = 'WBS 1 description'.
    append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
    wa_WBS_ELEMENT_TABLE-WBS_PLANNING_ELEMENT = ''.
    wa_WBS_ELEMENT_TABLE-WBS_ACCOUNT_ASSIGNMENT_ELEMENT = 'X'.
    wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs2.
    wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                      t_bid_definition-PROJECT_DEFINITION.
    wa_WBS_ELEMENT_TABLE-DESCRIPTION = ''WBS 2 description'.
    append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
    wa_WBS_ELEMENT_TABLE-WBS_ELEMENT = wbs3.
    wa_WBS_ELEMENT_TABLE-PROJECT_DEFINITION =
                                      t_bid_definition-PROJECT_DEFINITION.
    wa_WBS_ELEMENT_TABLE-DESCRIPTION = ''WBS 3 description'.
    append wa_WBS_ELEMENT_TABLE to i_WBS_ELEMENT_TABLE.
    clear wa_WBS_ELEMENT_TABLE.
    wa_project_definition_upd-project_definition =
                                        t_bid_definition-PROJECT_DEFINITION.
    append wa_project_definition_upd to i_project_definition_upd.
    Create correct WBS Hierarchy
    wa_method_project-OBJECTTYPE = 'WBS-Hierarchy'.
    wa_method_project-METHOD     = 'Create'.
    append wa_method_project to i_method_project.
    clear: wa_method_project.
    wa_method_project-METHOD     = 'Save'.
    append wa_method_project to i_method_project.
    clear: wa_method_project.
    wa_wbs_hierarchie_table-WBS_ELEMENT = wbs1.
    wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                      t_bid_definition-PROJECT_DEFINITION.
    wa_wbs_hierarchie_table-DOWN = wbs2.
    ppend wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
    clear wa_wbs_hierarchie_table.
    wa_wbs_hierarchie_table-WBS_ELEMENT = wbs2.
    wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                      t_bid_definition-PROJECT_DEFINITION.
    wa_wbs_hierarchie_table-UP = wbs1.
    wa_wbs_hierarchie_table-RIGHT = wbs3.
    append wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
    clear wa_wbs_hierarchie_table.
    wa_wbs_hierarchie_table-WBS_ELEMENT = wbs3.
    wa_wbs_hierarchie_table-PROJECT_DEFINITION =
                                      t_bid_definition-PROJECT_DEFINITION.
    wa_wbs_hierarchie_table-UP = wbs1.
    wa_wbs_hierarchie_table-LEFT = wbs2.
    append wa_wbs_hierarchie_table to i_wbs_hierarchie_table.
    clear wa_wbs_hierarchie_table.
    CALL FUNCTION 'ZBAPI_PROJECT_MAINTAIN'
      EXPORTING
        i_project_definition                =  t_bid_definition
      tables
        i_method_project                   = i_method_project
        I_WBS_ELEMENT_TABLE     = I_WBS_ELEMENT_TABLE
        I_WBS_HIERARCHIE_TABLE = i_wbs_hierarchie_table
        E_MESSAGE_TABLE            = i_bapi_message.
    Message was edited by:
            Karen Dean

  • Creating a WBS hierarchy using BAPI_PROJECT_MAINTAIN

    Hi,
    I am trying to create WBS hierarchy, but i am facing some problem in creating it. The code that i have written is :
    DATA : I_PROJECT_DEFINITION LIKE BAPI_PROJECT_DEFINITION OCCURS 0 WITH HEADER LINE,
           I_PROJECT_DEFINITION_UPD LIKE  BAPI_PROJECT_DEFINITION_UP OCCURS 0 WITH HEADER LINE,
           RETURN LIKE  BAPIRETURN1 OCCURS 0 WITH HEADER LINE,
           I_METHOD_PROJECT LIKE BAPI_METHOD_PROJECT OCCURS 0 WITH HEADER LINE,
           I_WBS_ELEMENT_TABLE LIKE BAPI_WBS_ELEMENT OCCURS 0 WITH HEADER LINE,
           I_WBS_HIERARCHIE_TABLE LIKE BAPI_WBS_HIERARCHIE OCCURS 0 WITH HEADER LINE.
    CLEAR I_PROJECT_DEFINITION.
    I_PROJECT_DEFINITION-PROJECT_DEFINITION = 'TEST_2'.
    APPEND I_PROJECT_DEFINITION.
    CLEAR I_METHOD_PROJECT.
    MOVE 'WBS-Element' TO I_METHOD_PROJECT-OBJECTTYPE.
    MOVE  'Create' TO I_METHOD_PROJECT-METHOD.
    MOVE 'T1' TO I_METHOD_PROJECT-OBJECTKEY.
    MOVE '000001' TO I_METHOD_PROJECT-REFNUMBER.
    APPEND I_METHOD_PROJECT.
    CLEAR I_METHOD_PROJECT.
    MOVE 'WBS-Element' TO I_METHOD_PROJECT-OBJECTTYPE.
    MOVE  'Create' TO I_METHOD_PROJECT-METHOD.
    MOVE 'T2' TO I_METHOD_PROJECT-OBJECTKEY.
    MOVE '000002' TO I_METHOD_PROJECT-REFNUMBER.
    APPEND I_METHOD_PROJECT.
    CLEAR I_METHOD_PROJECT.
    MOVE 'WBS-Element' TO I_METHOD_PROJECT-OBJECTTYPE.
    MOVE  'Create' TO I_METHOD_PROJECT-METHOD.
    MOVE 'T3' TO I_METHOD_PROJECT-OBJECTKEY.
    MOVE '000003' TO I_METHOD_PROJECT-REFNUMBER.
    APPEND I_METHOD_PROJECT.
    CLEAR I_METHOD_PROJECT.
    MOVE  'Save' TO I_METHOD_PROJECT-METHOD.
    APPEND I_METHOD_PROJECT.
    CLEAR I_WBS_ELEMENT_TABLE.
    I_WBS_ELEMENT_TABLE-WBS_ELEMENT = 'T1'.
    I_WBS_ELEMENT_TABLE-PROJECT_DEFINITION = I_PROJECT_DEFINITION-PROJECT_DEFINITION.
    I_WBS_ELEMENT_TABLE-DESCRIPTION = 'T1'.
    APPEND I_WBS_ELEMENT_TABLE.
    CLEAR I_WBS_ELEMENT_TABLE.
    I_WBS_ELEMENT_TABLE-WBS_ELEMENT = 'T2'.
    I_WBS_ELEMENT_TABLE-PROJECT_DEFINITION = I_PROJECT_DEFINITION-PROJECT_DEFINITION.
    I_WBS_ELEMENT_TABLE-DESCRIPTION = 'T2'.
    APPEND I_WBS_ELEMENT_TABLE.
    CLEAR I_WBS_ELEMENT_TABLE.
    I_WBS_ELEMENT_TABLE-WBS_ELEMENT = 'T3'.
    I_WBS_ELEMENT_TABLE-PROJECT_DEFINITION = I_PROJECT_DEFINITION-PROJECT_DEFINITION.
    I_WBS_ELEMENT_TABLE-DESCRIPTION = 'T3'.
    APPEND I_WBS_ELEMENT_TABLE.
    CLEAR I_METHOD_PROJECT.
    MOVE 'WBS-Hierarchy' TO I_METHOD_PROJECT-OBJECTTYPE.
    MOVE  'Create' TO I_METHOD_PROJECT-METHOD.
    APPEND I_METHOD_PROJECT.
    CLEAR I_METHOD_PROJECT.
    MOVE  'Save' TO I_METHOD_PROJECT-METHOD.
    APPEND I_METHOD_PROJECT.
    CLEAR I_WBS_HIERARCHIE_TABLE.
    MOVE 'T1' TO I_WBS_HIERARCHIE_TABLE-WBS_ELEMENT.
    MOVE I_PROJECT_DEFINITION-PROJECT_DEFINITION TO I_WBS_HIERARCHIE_TABLE-PROJECT_DEFINITION.
    MOVE 'T2' TO I_WBS_HIERARCHIE_TABLE-DOWN.
    APPEND I_WBS_HIERARCHIE_TABLE.
    CLEAR I_WBS_HIERARCHIE_TABLE.
    MOVE 'T2' TO I_WBS_HIERARCHIE_TABLE-WBS_ELEMENT.
    MOVE I_PROJECT_DEFINITION-PROJECT_DEFINITION TO I_WBS_HIERARCHIE_TABLE-PROJECT_DEFINITION.
    MOVE 'T1' TO I_WBS_HIERARCHIE_TABLE-UP.
    MOVE 'T3' TO I_WBS_HIERARCHIE_TABLE-RIGHT.
    APPEND I_WBS_HIERARCHIE_TABLE.
    CLEAR I_WBS_HIERARCHIE_TABLE.
    MOVE 'T3' TO I_WBS_HIERARCHIE_TABLE-WBS_ELEMENT.
    MOVE I_PROJECT_DEFINITION-PROJECT_DEFINITION TO I_WBS_HIERARCHIE_TABLE-PROJECT_DEFINITION.
    MOVE 'T1' TO I_WBS_HIERARCHIE_TABLE-UP.
    MOVE 'T2' TO I_WBS_HIERARCHIE_TABLE-LEFT.
    APPEND I_WBS_HIERARCHIE_TABLE.
    CALL FUNCTION 'BAPI_PROJECT_MAINTAIN'
      EXPORTING
        i_project_definition               = I_PROJECT_DEFINITION
        i_project_definition_upd           = I_PROJECT_DEFINITION_UPD
      IMPORTING
        RETURN                             = RETURN
      tables
        i_method_project                   = I_METHOD_PROJECT
      I_WBS_ELEMENT_TABLE_UPDATE         =
        I_WBS_ELEMENT_TABLE                = I_WBS_ELEMENT_TABLE
      I_WBS_MILESTONE_TABLE              =
      I_WBS_MILESTONE_TABLE_UPDATE       =
        I_WBS_HIERARCHIE_TABLE             = I_WBS_HIERARCHIE_TABLE
      I_NETWORK                          =
      I_NETWORK_UPDATE                   =
      I_ACTIVITY                         =
      I_ACTIVITY_UPDATE                  =
      I_RELATION                         =
      I_RELATION_UPDATE                  =
      E_MESSAGE_TABLE                    =
      I_ACTIVITY_ELEMENT                 =
      I_ACTIVITY_ELEMENT_UPDATE          =
      I_ACTIVITY_MILESTONE               =
      I_ACTIVITY_MILESTONE_UPDATE        =
    Please can anyone check and tell me what exactly is the problem?
    Thank you.

    Hi Poorvika,
    I am facing same problem. If you find solution, can you please post it here?
    Thanks
    ABAPer

  • Error when trying to extract WBS Hierarchy

    Any help appreciated.
    Using BI7, when trying to extract the WBS Hierarchy from an R3 source system using DataSource 0WBS_ELEMT_WBSH_HIER during the extraction process the load fails with error "The level of the node ID 00041234 does not suit the lev of higher lev node"
    The long text talks about Parent and Child nodes. I believe the numbers being stated, 00041234 etc refer to the Technical IDs shown within the Hierarchy Display within BI. I've checked table PRPS in Project Systems and I assumed the numbers represented WBS Elements - but they do not match when checking the descriptions. (BI to R3)
    Checked on OSS and note 339453 may apply but Im not sure what to check / how to replicate. Based on the errors being reported in BI how can I identify the error in the R3 source system?
    Many Thanks
    Lee

    Closed as no responses.

  • Error Loading WBS Hierarchy

    All:
    While trying to load WBS hierarchy, I am getting following error message.
    "Node ID 00000432 starts an endless loop"
    "Node ID 00000448 does not exists"
    I am not able to find where do these hierarchies are maintained in SAP R/3 so that I can correct hese errors in source system. Any Idea?

    Have you tried transaction code CJ20N?
    Torbjorn

  • Clarification of "Automatic Client Upgrade" in Hierarchy Settings

    Hello all, I am looking for clarification of "Automatic Client Upgrade" in Hierarchy Settings.  I am SCCM 2012 R2 CU1.  It says the latest version is "5.00.7958.1000"  My CU1 version is actually "5.00.7958.1203". 
    From reading various other users forum questions regarding this issue I have learned that this upgrade will only work for "Major versions".  That should be why I don't see the same versions.  My question relates possibly more generally. 
    I am in the process of building and configuring the SCCM 2012 R2 CU1 (site code: IT1) environment.  I have a running production SCCM 2007 R3 (site code:  IT0) environment, with a different side code.  I am not ready for these older SCCM 2007
    R3 clients to be upgraded to SCCM 2012 R2 CU1 as I am still testing and finalizing things. 
    If I enable the "Automatic Client Upgrade" in Hierarchy Settings for 2012 R2 CU1, could someone better explain which clients this affects?
    Will it upgrade my old SCCM 2007 R3 clients to SCCM 2012 R2? 
    Will it upgrade anything outside of the SCCM 2012 site IT1 (if I had two SCCM 2012 sites with different names)?
    Will it upgrade an SCCM 2012 client to SCCM 2012 R2?
    Will it upgrade an SCCM 2012 SP1 CUx client to SCCM 2012 R2?
    Will it upgrade an SCCM 2012 R2 client to SCCM 2012 R2 CU1?  (from what I have read, NO)
    Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

    Will it upgrade my old SCCM 2007 R3 clients to SCCM 2012 R2?   
    No
    Will it upgrade anything outside of the SCCM 2012 site IT1 (if I had two SCCM 2012 sites with different names)?
    Since we cannot have two sites with the same name in a hierarchy I assume these are two different hierarchies. The setting is for a hierarchy wide and works by creating a scheduled task for client to get the package via policies. Though I have not tried
    this but logically it should not.
    Will it upgrade an SCCM 2012 client to SCCM 2012 R2?
    On the same hierarchy,Yes!
    Will it upgrade an SCCM 2012 SP1 CUx client to SCCM 2012 R2?
    On the same hierarchy,Yes.
    Will it upgrade an SCCM 2012 R2 client to SCCM 2012 R2 CU1?  (from what I have read, NO)
    You are correct. CUs are not a major release and a separate client package is created and you need to manually target them to the clients to get it upgraded.
    Umair Khan | http://blogs.technet.com/umairkhan

  • Skip a level in wbs hierarchy

    Hi,
    how to skip a level while creating wbs elements hierarchy?
    Thanks!

    Hi,
    you mean for example you want to create a level 3 WBS under a level 1 WBS?
    is that what you mean by skip a level?
    that is not possible, i cant even think of a scenerio why you might want to do that. (but i'm curious why you asked)
    it isnt even logically feasible. you can create WBS levels only one at a time.
    Good day.

  • WBS HIERARCHY building logic

    HI ,
         I am facing a problem  in building HIERARCHY table , I want to populate the HIERARCHY table in a up down left right manner and after populating it I want to pass it in BAPI_PROJECT_MAINTAIN   table  parameter i.e  I_WBS_HIERARCHIE_TABLE     .
    all the WBS elements are coming from the file . so pls help me with the sample code of HIERARCHY  population .

    Hi Pravik,
    Please refer below link:-
    [http://wiki.sdn.sap.com/wiki/display/Snippets/ABAP%2bProgram%2bto%2bUpload%2bWBS%2bELEMENTS%2bIN%2bHierarchy]
    Kindly set to resolved if it helps you.
    Regards
    Abhii...

  • Can't see newly created WBS Hierarchy

    When using info object 0WBS_ELEMT_WBSH_HIER we are not able to see a new wbs group/hierarchy created in our r/3 system. But for cost center hierarchy we see everything the users create. Is there a setting on 0WBS_ELEMT_WBSH_HIER that we missed to allow multiples?
    on the cost center hierarchy object it allows "intervals". Thats the only difference I see.
    Thanks
    Richard

    Yes, It works perfect if you just write a quick abap program.
    Here are the statements we used.
    declare the hierarchy catalog table
    tables roohiecat .
    write / '*******************' .
    Write / 'Before Table Update' .
    write / '*******************' .
      clear roohiecat .
      Select single * from roohiecat
       where oltpsource = '4R_PS_POSID_0000_HIER' and
              objvers = 'A'.
      Write: / roohiecat-OLTPSOURCE ,roohiecat-OBJVERS ,
              roohiecat-TYPEHC .
    this table holds the Hierarchy class code.
    after creating the generic hierarchy with class code 0000
    the update statement below will run and change the class code
    to 0110 which represents WBS group.
    You must then replicate the datasource to use it in BW.
    Clear sy-subrc.
    Update roohiecat
       set typehc = '0110'
        where oltpsource = '4R_PS_POSID_0000_HIER' and
              objvers = 'A'.
    if sy-subrc = 0 .
      write / '*******************' .
      Write / 'After Table Update' .
      write / '*******************' .
      clear roohiecat .
      Select single * from roohiecat
       where oltpsource = '4R_PS_POSID_0000_HIER' and
              objvers = 'A'.
    Write: / roohiecat-OLTPSOURCE ,roohiecat-OBJVERS ,
              roohiecat-TYPEHC .
    endif .

  • Hierarchy Settings at query level

    Hi,
    I my system Profit Center is compounded on Controlling Area.
    In Cube These are 2 different fields.
    I had a Profit Center Hierarchy that is being extracted from ECC...in the hierarchy The Profit center Key is a combination of Controlling Area + profit center Key.
    The query is restricted on Hierarchy....currently when i execute query its not displaying any data as key is not matching (Profit center key with that of Profit center key in Hierarchy)
    How can i resolve this
    Thanks

    Venkat,
    To troubleshoot your query, remove your filter values and run the query.
    Drill into your data by the characteristics you have set with filter value and see what actual values are in your system for these characteristics.
    Chances are you are filtering by something that has no data hence the No data Available result.
    Regards
    Gill

Maybe you are looking for

  • Bluetooth icon not showing up in menu bar

    Usually, the Bluetooth icon always shows up in my menu bar upon start-up. Lately it has not been appearing. In my system preferences, the show blue-tooth icon in menu bar is checked. If I uncheck it and then check it again it shows up where it is sup

  • My macbook pro 13 inches starts extremely slowly.

    I did not use it almost 6 months and kept it in a neoprene sleeve and store in book rack. RAM 8GB DDR3 installed by store when purchased. recently worked well. Remaining HDD available space greater than 500GB. Hardware test even could not finish a wh

  • HT1212 How do you unlock iPhone when its disabled and will not connect o iTunes

    My iphone is locked.  Says iPhone is disabled, connect to iTunes.  But when i connect ot iTunes it does not connect.  Tells me to put in my password inwhich I cant because it is disabled.  This is an iPhone 4 that is not used as a phone but an iTouch

  • Open certain applications on second monitor

    Hi, The display of my labtop is too small to work on large graphic files, so I would like to open Photoshop, Illustrator and InDesign etc. by default on the external monitor I have connected. Other programs I like to open on the labtop screen. Is thi

  • When i try to open iTunes,

    my computer won't let me - it says i have a run time error R6025 pure virtual function call--- i have tried reinstalling, anti virus, clean registry -- nothing Help!!!