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.

Similar Messages

OBIEE 11g: Skip a level in a parent-child hierarchy

Hi everyone,
I've got a parent child hierarchy setup. It's basically Total Company -> Continent -> Country. It's working fine.
For one particular report, the end user would like to bypass continent for just Asia. The rest of the countries should go through their continent first.
For example,
Total Company -> Europe -> Germany
Total Company -> North America -> Canada
Total Company -> Japan
Total Company -> Korea
We do not want to change the hierarchy as it is a corporate standard and eventually we want the grouping there. Just for a single report, we want to bypass.
Is there anyway to do this?
I tried to remove the "Asia" node while building the report, but it also removes the children. So then I tried adding back in the children and they weren't part of the hierarchy. They were off in their own duplicate hierarchy.
Hopefully this is possible.

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.

PS: How to get the hierarchy of a level 1 WBS only?

Hi,
This corresponds to Projects System module.
If we have 5 level 1 WBS elements.Out of them if I want to get only the WBS hierarchy corresponding to a level 1 WBS element (say 2nd level 1 WBS element).
I know that we can get all the WBS elements' hierarchy from BAPI_PROJECT_GETINFO. But I want the hierarchy for only one level 1 WBS element not for all. How?

you could read them from SETNODE table with SETCLASS = '0110'

Issue in creation of level 2 WBS for level 1 WBS which is released

Hello All,
I am trying to create a level 2 WBS for a alrealy created level 1 WBS using BAPI_BUS2054_CHANGE_MULTI .If the level 1 WBS is not released then level 2 WBS gets created .However if the level 1 is released then level 2 WBS doesnt gets created and i get error ' User status INIT is active (WBS #1) '
Using T-code CJ20n i am able to create level 2 WBS for released level 1 WBS .

Hi;
Do you fill WBS_LEFT, WBS_UP fields for IT_WBS_ELEMENT / IT_UPDATE_WBS_ELEMENT tables.
Hierarchy is very important for between WBS.
May help below similar link:
Re: Create Whole Project with BAPI_PROJECT_MAINTAIN
Best regards.

Why I can not find field:Level in Project Hierarchy in BAPI_BUS2054_NEW?

Dear experts,
Why I can not find the field of "Level in Project Hierarchy" in structure BAPI_BUS2054_NEW?
I only define the data to upload wbs:
PROJECT DEFINITION
PROJECT DESCRIPTION
PROJECT PROFILE
WBS Element
WBS description
Can you tell me which fields must to upload?
Looking forward to your reply.
Many thanks.
Merryzhang

Anyone can help me ?I need the field "Level" in BAPI_BUS2054_NEW,But I can not find it.

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

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

MDX missing out 'All' level results for attribute joined to leaf level of a hierarchy

I have an MDX query with a cross-join of a hierarchy and a simple attribute on rows. The leaf level of the hierarchy maps one-to-one with the simple hierarchy, while the other levels map onto multiple values of the simple attribute. In the results,
an 'All' level row of the simple hierarchy is produced for all values of the hierarchy. However:
1. if the rows are numbered using Rank, the row number that the 'All' rows of the root level values of the hierarchy should have is skipped, and the rows that should have it have a repeat of the single child's row number.
2. in SSRS no 'All' level of the simple attribute is found for the root level of the hierarchy.
My reading of this is that the All level is not being produced for the one-to-one root level relationship, and the query is reading the first non-empty value.
Any thoughts on (1) how to force the production of the missing 'All' level values; and (2) how to use Scope or some other means to place values in the positions where they are missing.
Ken

It would be helpful to see your MDX query and a screenshot illustrating the results!
Thanks! Josh

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.

How to do budgeting at activity level and WBS element level in project syst

Dear GURU's,
Can any one please suggest me how to do budgeting at activity level and WBS element level in project systems, friends please I required set by step process.
I need how to do this configuration to map this scenario.
Regards,
Bhanu

Hi Bhanu,
Use this link :
http://help.sap.com/saphelp_45b/helpdata/en/86/98853478616434e10000009b38f83b/frameset.htm
after page opens , click on BUDGET MANAGEMENT , There you will find each and every step you want .
Thanks ,
Dhruv Kumar Malhotra

How to Restrict the node level in account hierarchy

Hi experts,
I want to restrict the node level in account hierarchy. I attached one example. in that if i click 6000 node again it want to show error message. for one parent node i want to create only two child node. Further if i create means it want to show error msgs and not allow to create the node..
Regards,
gopi

Hi ,
The component is bp_hier, and method is onnew_node.
IF lv_tree->is_locked( ) = abap_false.
     lv_tree->lock( ).
   ENDIF.
   CHECK lv_tree->is_locked( ) = abap_true.
   lv_index = typed_context->accounthierarchy->selected_index.
   lv_tree_node = typed_context->accounthierarchy->get_node_by_index( lv_index ).
*key = lv_tree_node->node_key.
CALL METHOD lv_api->get_node_parent
     EXPORTING
       iv_node_key        = key
     IMPORTING
       ev_parent_node_key = lv_paent_key
*      ev_tree_guid       =
*   lv_parent = lv_tree_node->parent_entity.
*    typed_context->accounthierarchy->parent_entity.
CALL METHOD lv_tree_node->get_children
   receiving
     rt_children = rt_child.
   CHECK lv_tree_node IS BOUND.
   lv_tree_node->is_leaf = abap_false.
   TRY.
       lv_proxy_node ?= lv_tree_node.
       TRY.
           lv_object ?= lv_proxy_node->bo.
         CATCH cx_sy_move_cast_error.
           lv_mixed_node ?= lv_proxy_node->bo.
           lv_object ?= lv_mixed_node->if_bsp_wd_ext_property_access~get_model_node( ).
       ENDTRY.
       lv_object_name = lv_object->get_name( ).
       IF lv_object_name = 'BuilHierarchyNode'.
         lv_relation_name = 'BuilHNodeRel'.
       ELSEIF lv_object_name = 'BuilHierarchyHeader'.
         lv_relation_name = 'BuilHeaderNodeRel'.
       ELSE.
         RETURN.
       ENDIF.
       lv_tree_node->get_children( ).
       lv_object = lv_object->create_related_entity( lv_relation_name ).
       lv_child_node = lv_proxy_node->node_factory->get_proxy(
           iv_bo = lv_object
           iv_proxy_type = 'CL_BP_HIER_HIERARCHYTREEV_CN05'
           iv_parent_proxy = lv_tree_node ).
       lv_tree_node->expand_node( ).
       typed_context->accounthierarchy->refresh( ).
       typed_context->accounthierarchy->deselect_all( ).
       lv_child_node->selected = abap_true.
       lv_child_node->is_leaf = abap_true.
*accounthierarchy
*      selectedhierarchynode
       lv_col_wrap = typed_context->selectedhierarchynode->get_collection_wrapper( ).
       lv_col_wrap->clear( ).
This is the code.
i wrote . but its not getting.

Drilling via Hierarchy - how to display upper levels of the hierarchy??

Hi all.
I'm using Discoverer 10.1.2
I have a worksheet which contains only one Pie graph.
Users can drill down and up by clicking on the slices of the graph, because I definied Hierarchy in the Administrator.
Everything's fine, but when drilling down you can't see through which values of upper levels of the hierarchy you go..
For example assume the pie graph displaying three slices for warehouses 1,2 and 3.
User clicks on slice 2. Discovere re-run query with new condition warehouse=2 and displays new pie graph which shows four slices for Items a,b,c and d.
That's fine user can see there are four items on the selected warehouse and there is some amount of each of these items.
But he can't see which warehouse was selected!!!
Discoverer only adds new condition to the source sql query but I have no chance to display these conditions on worksheet.
Discoverer Plus enables to add "Axis Items", "Data points",etc in the graph title.
In the Legend of the Graph there is a Column name of the upper level of the hierarchy but not its value (in my example there would be Legend displaying slice colors for items a,b,c,d and link to "warehouse") I would Like to see current warehouse number (e.g. 2 in above example) too!!
Any workaround???
Thanks a lot.
Jakub

Hi Jakub
In releases prior to 10.1.2 users really had no choice but to drill to detail. However, with the release of hyper drills in 10.1.2 the situation has changed. Most of my customers now use hyper drills and wondered how they ever got by without them. Using hyper linked workbooks allows you to create a library of workbooks that all interlink to each other, up and down the chain.
Thus a user can jump into the chain anywhere they like and the system should let them link up or link down. When done properly you end up with a library. Now take this one step further and make the library owner a generic user called something like ACCOUNTS PAYABLE. You can now have a library of accounts payable workbooks, workbooks that have been shared with either the ACCOUNTS_PAYABLE role or responsibility.
Does this help see the direction I take?
Regards
Michael

Check on level of WBS element for capital purchase PO

Hi Experts,
We are facing a problem. While creating Capital purchase PO, all WBS elements are allowed. Although, system is configured in such a way that GRN can not be done for Level 1 WBS( Parent project). We want to introduce a check at PO creation level only, so that it should not take Level 1 WBS element. How can it be done( validation check can do here or not) .

How did you set up the derivation rule???
I think that is where you specify a level of expenditue or procurement.
Thanks

Skip a level in wbs hierarchy

Similar Messages

Maybe you are looking for