Help reqd on WBS hierarchy

Hi All,
We are in the process of creating a custom report for our client.
Problem:  WBS group is not fetching the respective WBS elements
Scenario :
When I need WBS elements under “UTILITY” WBS group , the report should display all the WBS elements under each WBS subgroup .This scenario is failing.
i.e If a WBS group has several WBS subgroups which are linked by WBS elements (data is maintained at two or more levels ) , we fail to capture such data in our report.
e.g. Gas is a subgroup of UTILITY which stores several WBS elements . We need to display all the WBS elements under Gas subgroup (similarly TRANS, CUTOPS, ELECTRIC etc.)  data in our report.
Please help us in resolving this issue .

Hi Hemanth
                   To analyse your issue we would require more detialed steps as in which transaction you are using to genrate the report. Ehther you generate reports on projects or WBS elements. What is the detailed structure of Project or WBS?
These details would help us to reach to a solution.
Thanks and Kind Regards
Mohan

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

  • 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

  • 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 in MIRO Help Reqd

    I have setup new instance. Created p.o & done MIGO things worked fine. In MIRO typically error is seen in tax code. I have assigned Tax procedure TAXGB to country IN. In Fin Acct in tax on sales & purchases defined new taxcode VX with country option IN. Still during MIRO its showing error Tax code VN & Country IN doesnot exist in procedure TAXGB. In error msg its M8 249 & origin is shown as check invoice document.
    Help reqd from SAP Gurus pls.
    Regards

    Check these links
    while doing MIRO, i am getting error:-Tax code V0 country IN does not exist
    Tax code Z4 country IN does not exist in procedure TAXINJ
    Tax code V0 country IN does not exist in procedure TAXINN
    Tax code V0 country IN does not exist in procedure TAXINN

  • Urgent Help Reqd: Delta Problem....!!!

    Hi Experts,
    Urgent help reqd regarding follwoing scenario:
    I am getting delta to ODS 1 (infosource : 2LIS_12_VCHDR) from R/3. Now this ODS1 gives delta to Cube1. I got one error record which fails when going to cube (due to master data check).And this record would be edited later.
    So I thought of re loading cube and using error handling to split request in PSA and load valid records in cube.Later when I have coorect info abt error, I would load erroneous record manually using PSA.
    I did following steps:
    1)Failed request is not in cube...(setting is PSA and then into target)....also it has been deleted from PSA.
    2)Remove data status from source ODS1.
    3)Change error handling in infopackage to valid " Valid records update, reporting possible".
    4)start loading of cube.
    But when I did this I got following message :
    <b> "Last delta update is not yet completed.Therefore, no new delta update is possible.You can start the request again if the last delta request is red or green in the monitor"</b>
    But both my requests in cube and ODS are Green...no request is in yellow...!!
    Now the problem is :
    1) I have lost ODS data mart status
    2)how to load valid records to cube, since errorneous record can be edited only after 3- 4 days.
    3)How not to affect delta load of tomorrow.
    Please guide and help me in this.
    Thanks in advance and rest assured I will award points to say thanks to SDNers..
    Regards,
    Sorabh
    Message was edited by: sorabh arora

    Hi Joseph,
    Thanks for replying....
    I apolgize and I have modified the message above..
    I just checked in cube...there is no failed request for today...and neither in PSA....Person who has handed this to me may have deleted this is PSA..and why req is not in failed state in cube...I am not sure..though setting is "PSA and then into data package".....
    So how to go frm here....
    Thanks
    Sorabh

  • 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

  • Input help of the org. hierarchy

    Hello all,
    I have two similar enviroments, one with ish version 4.6 and another with version 6.00
    The input help of the organizational hierarchy when it is called from nv2000 or report RNLORG01
    in 6.00 is very slower than 4.6. (Both enviroments have the same parameters OE_LEVEL and OE_LOAD) There is something I can do to optimize this input help? Thanks in advance.
    Regards.

    There are two more recent notes related to this input help:
    Note 1272171 - IS-H: OrgUnit input help does not display all OrgUnits
    The input help for organizational units does not display all inter-departmental organizational units
    Note 1292719 - IS-H: Input help for nursing OU displays incorrect info
    If you call the input help in NV2000 in the field "Nursing OU", the system may not display the name of the nursing OU correctly in some cases. The system displays the name of higher-level departmental OU instead.

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

  • HELP  exit CO02 wbs

    Hy yall i had a custom help search for wbs in the prpm collective search, i needed to you give to the werks the default value of the werks in that dynpro.
    I used this rudimental code and it's works but is there any more "elegant"  way or a FM  to retrieve that value and set the parameter id?
    i used this.
    data: str(70) type c.
      data: str2(70) type c.
      field-symbols: <werks> type co_pwerk,
                     <auart> type aufart.
      clear str.
      concatenate '(' 'SAPLCOKO1' ')CAUFVD-WERKS'   into str.
      assign (str) to <werks>.
      clear str2.
      concatenate '(' 'SAPLCOKO1' ')CAUFVD-AUART'   into str2.
      assign (str2) to <auart>.
      set parameter id 'WRK' field <werks>.
      set parameter id 'AAT' field <auart>.

    Hi
    You can try to use some BTE for vendor (tran. FIBF), for examples:
    00001421 after updating
    00001440 before updating
    Max
    Message was edited by: max bianchi

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

Maybe you are looking for