HEIRARCHY IN BAPI_PROJECT_MAINTAIN

HELLO experts,
i am using this BAPI BAPI_PROJECT_MAINTAIN for maintaining the herirachy for the WBS but whenver i am creating the wbse its not maintained in the proper level as i am using I_WBS_HIERARCHIE_TABLE for maintaining the heirarchy but its not working properly, kindly hepl me out in solving this problem ASAP
thanks

Take a look at Threa WBS hierarchy not working in BAPI_PROJECT_MAINTAIN
Regards

Similar Messages

Manager Heirarchy is not getting displayed in P&L Dashboard

Hi All,
I have implemented the P&L Dashboard for Financials. Suddenly, It is not displaying the Manager Heirarchy in the Manager Parameter in the P&L Dashboard.
Did anyone faced the same kind of problem, please throw some light.
Regards,
Chandana

Hi,
Thank you All.
Regards,
Shruti B.

How to Display Heirarchy and Character at a time in the report...

Hi
I have a req ...where I need to design a query to display a character and its heirarchy colum by colum...I mean, I have document type master data info object it has texts and Heirarchy data source...and we loaded this data...Also we have document type directly coming from ECC Transactional DS...Now When I take this document type and do not select heirarchy its displaying the document types (KN,KA ,KR etc...)..If I select the heirachy in my query..its displaying in heirarchy structure and the document types (KN,KA,KR ) are displaying as the last nodes. But I want to display the heirarchy and also the document type in 2 diff colums... how it would be possible..is there any thing needs to be done at query level / do i need to take a RKF / CKF and write any code to bring heir and info object value?
Iam bit confused here..pelase advice ASAP.
regards

you cannot have the same character in the query twice. You can either have it in the hier format or just the char.
I am wondering why you need to display the same characters twice in each column.
The best way is to have them in the hier. format and in the char. properties expand the node level as you want so you will see them in the detail level.
assign points if helpful

When create heirarchy, can not find the entry which is in master data

Hi, SDNs
When create a heirarchy for a char , click this char button to add a fields to a node, i can't search the value which is actually in the master data.
Thansk for your time

If you go to create hierararchy or change mode of hierarchy
3 types of nodes you can create
1)Text node
2)Charecteristic node
3)Infoobject values node
text node - is simple any text node you can create
infoobject values node - if the master data is loaded you can create it
if master data is loaded make sure its activated and no master data is under "M" version.
charecteristic node - only if particular infoobject node is included in the tab "external chars in hierarchies" in RSD1 of that particular infoobject
Hope it Helps
Chetan
@CP..

Performance issues with BAPI_PROJECT_MAINTAIN

Hi,
We are facing Performance issues with BAPI_PROJECT_MAINTAIN.Would like to know any suggestions for improving performance.
I would also like to know statistics regarding how much time is required to create a project with 3000 activities, 100 WBS etc.
Regards

Yes, I have. But didnt find any one relevant. If you can share time reqd for particular number of objects or suggest any solutions.
Regards

Product heirarchy vs material groups for sales

Hi,
Can I make use of the material groups(5 in toatl in sales view1) to generate report for seeing the value/sale of any material instead of using product heirarchy ?
If I have created a 3 level heirarchy then how best I can use it to see in a report for any level.
Is there any standard report availble to track my sales/inventory needs based on product heirarchy ??
How can I track my purchases/open orders based on the employee resonsible for that material.i.e without having any HR module how can use the or create the staff of my company engaged in purchasing or for that matter selling also.
May be I can use Purchasing group for each employee.But then I need to use the same employee as Sales person.
How can this be achieved or any better option ??
Thanks in advance.
Regards,
Manoj

Redundant.Has been reposted in MM forum.Do not reply here

Product heirarchy vs material groups in sales view

Hi,
Can I make use of the material groups(5 in toatl in sales view1) to generate report for seeing the value/sale of any material instead of using product heirarchy ?
If I have created a 3 level heirarchy then how best I can use it to see in a report for any level.
Is there any standard report availble to track my sales/inventory needs based on product heirarchy ??
How can I track my purchases/open orders based on the employee resonsible for that material.i.e without having any HR module how can use the or create the staff of my company engaged in purchasing or for that matter selling also.
May be I can use Purchasing group for each employee.But then I need to use the same employee as Sales person.
How can this be achieved or any better option ??
Thanks in advance.
Regards,
Manoj

Hi,
Have you considered using the partner functions to do this.
Most organisations create a new partner type for saleperson (i.e. someone who earns the commision from the sale). This can automatically default if you have the correct master data settings, or can be keyed manually on the partner screen of the sales order. (ask about how to do this on the SD forum, I am sure that an SD expert can tell you the details on how to do this.
I definitely would NOT recommend considering using the Purchasing group, this is not a field to use for this purpose in any way.
The material group and material hierarchy are fine to use for reports on WHAT was sold, but not who by etc.
Steve B

MS Word property descriptions or heirarchy?

I am formatting test reports that I am creating via LabVIEW in MS Word 2000 on NT. The new LabVIEW 6.0.2 Report Generation Toolkit with Word vi's are great but incomplete. My huge hurdle for formatting directly with properties and methods is that there are no descriptions or a heirarchy showing the relationships between all of them. Does anyone know where I can find this documentation? NI does not offer this support, yet.

As i had and will have to deal with those property and invoke nodes, i'd be interested in knowing that, but for now the only way i have found is using VBA (Visual Basic for Applications), most of the properties are detailed there. It also helped me to build my program, when i have a problem doing something programatically, i record a macro and analyze the results, applying them to LabVIEW.
Hope this helps

BAPI_PROJECT_MAINTAIN

I am getting an error in BAPI_PROJECT_MAINTAIN while trying to add an Activity to an existing Network. The Activity number does not exist for the network so I am assuming that CREATE is the best Method to use. Initially, this error was caused by a missing field UVORN, SubOperation, that is required to create an activity. I do not see the connection of UVORN, a work order related field, to creating an Activity.
Now, I am getting an Object Key error from my input data using UPDATE with the same data. I am new to the world of PS and could use some help in getting the input data coded correctly to add and Activity. Any help I can get on this would be gratefully appreciated.
Thank you in advance for your assistance.

Hi Robert,
It is rather the reverse way. BAPI_PROJECT_MAINTAIN has the functions of BAPI_NETWORK_MAINTAIN. Following is an extract from the documentation of the former BAPI:
"With the Maintain BAPI of the WorkBreakdownStruct business object you can edit the objects of a project definition. You can also use all the functions of the Maintain BAPI of the Network business object.
For more information, see Network.Maintain. With WorkBreakdownStruct.Maintain it is possible to edit the project definition, its WBS elements and their hierarchical relationships. The BAPI encapsulates a complete transaction in itself. As a result, several operations on project elements can be processed by only one call. The Project System determines in which order the operations are to be executed on the objects. The caller can choose the operations in any order."
RGds
Deepak

BAPI_PROJECT_MAINTAIN problem while creating milestone

Hi all,
We created the milestone by using the function module.
BAPI_PROJECT_MAINTAIN
We get a success message such as milesone 00000020 created but the same is not getting displayed either in CJ20N
or MLST table.
Guess there is some problem with the commit.
Kindly help me to point to solve the above issue.
Regards,
Ganesh J

Just a short checklist:
How did you use the BAPI (in test environment?? etc.)
check application configuration (can you create milestone manually?)
did the bapi update other fields?
check the BAPI Documentation about usage?
check OOS for known bugs in your release?
Kind regards.
Axel

Not able to update the project using 'BAPI_PROJECT_MAINTAIN'.

I want to create a project , with reference to an already existing project.
I am using 'BAPI_PROJECT_GETINFO' to get the data of the existing project.
The bapi gives the following:
1)     e_project_definition.
2)     e_wbs_element_table.
3)     e_wbs_hierarchie_table
I am passing the u2018e_project_definitionu2019 to 'BAPI_PROJECTDEF_CREATE' to create project.The project is created successfully.
But I am not able to update the project with u2018e_wbs_element_tableu2019
and u2018e_wbs_hierarchie_tableu2019. I am using 'BAPI_PROJECT_MAINTAIN' to update the project.
The program is not giving an error, but it is also not updating the E_WBS_ELEMENT_TABLE and E_WBS_HIERARCHIE_TABLE.
I am attaching the code below.
*& Report ZTEST_PC.
DATA: project_definition   TYPE bapipr-project_definition,
      with_activities      TYPE bapipr-with_activities,
      with_milestones      TYPE bapipr-with_milestones,
      with_subtree         TYPE bapipr-with_subtree,
      e_project_definition TYPE bapi_project_definition_ex,
      return               TYPE bapireturn1.
DATA: i_wbs_element_table         TYPE TABLE OF     bapi_wbs_elements,
      e_wbs_element_table         TYPE TABLE OF     bapi_wbs_element_exp,
      e_wbs_milestone_table   TYPE TABLE OF bapi_wbs_milestone_exp,
      e_wbs_hierarchie_table TYPE TABLE OF bapi_wbs_hierarchie,
      e_activity_table        TYPE TABLE OF bapi_network_activity_exp,
      e_message_table         TYPE TABLE OF bapi_meth_message.
DATA: wa_wbs_element_table    TYPE      bapi_wbs_element_exp,
      wa_wbs_hierarchie_table TYPE bapi_wbs_hierarchie.
DATA: l_new_proj_no TYPE prpss-posid.
DATA: l_project_definition        TYPE bapi_project_definition.
DATA: l_project_definition_upd    TYPE bapi_project_definition_up.
DATA: l_project_definition_stru   TYPE bapi_project_definition.
DATA :l_pspnr      TYPE ps_intnr,
      l_pspid      TYPE ps_pspid,
      l_pro_def(9) TYPE c.
DATA :l_proj TYPE proj.
DATA :l_len TYPE i VALUE '0'.
DATA: lt_dd03l TYPE TABLE OF dd03l,
      ls_dd03l TYPE dd03l.
DATA: fieldname(50), fieldname1(50) TYPE c.
DATA: p_ddic_name(40), struc(40), fun_struc(50) TYPE c.
FIELD-SYMBOLS: <struc>, <c>, <sc>, <def_field> TYPE any.
DATA : i_method_project    TYPE TABLE OF bapi_method_project,
       wa_method_project   TYPE bapi_method_project.
DATA : l_index TYPE bapi_method_project-refnumber.
DATA : it_wbs_element_table         TYPE TABLE OF bapi_wbs_element,
       it_wbs_hierarchie_table      TYPE TABLE OF bapi_wbs_hierarchie.
DATA : wl_wbs_element_table         TYPE bapi_wbs_element,
       wl_wbs_hierarchie_table      TYPE bapi_wbs_hierarchie.
DATA : l_wbs_element_table_update   TYPE bapi_wbs_element_update.
DATA : i_wbs_element_table_update   TYPE TABLE OF bapi_wbs_element_update.
Get the project info of the Project 'C01.10995'
CALL FUNCTION 'CONVERSION_EXIT_ABPSN_INPUT'
EXPORTING
    input = 'C01.10995'
IMPORTING
    output = project_definition.
CALL FUNCTION 'BAPI_PROJECT_GETINFO'
EXPORTING
    project_definition     = project_definition
IMPORTING
    e_project_definition   = e_project_definition
    return                 = return
TABLES
    i_wbs_element_table    = i_wbs_element_table
    e_wbs_element_table    = e_wbs_element_table
    e_wbs_milestone_table = e_wbs_milestone_table
    e_wbs_hierarchie_table = e_wbs_hierarchie_table
    e_activity_table       = e_activity_table
    e_message_table        = e_message_table.
Automate the process the process to get the next number for the func module 'CN_SUCHE_FREIE_NUMMER'.
CLEAR : l_pspnr, l_pspnr, l_pspid, l_pro_def.
SELECT MAX( pspnr ) FROM proj INTO l_pspnr.
SELECT SINGLE * FROM proj INTO l_proj WHERE pspnr EQ l_pspnr.
l_pspid = l_proj-pspid.
CALL FUNCTION 'CONVERSION_EXIT_ABPSN_OUTPUT'
EXPORTING
    input = l_pspid
IMPORTING
    output = l_pspid.
l_pro_def = l_pspid+4(5) + 1.
CONDENSE l_pro_def.
CONCATENATE 'C01.' l_pro_def INTO l_pspid .
function module to generate the nect free number between the given range.
CALL FUNCTION 'CN_SUCHE_FREIE_NUMMER'
EXPORTING
    search_imp = '2'
    prps_s_imp = l_pspid
    prps_e_imp = 'C01.29999'
    no_dialog = 'X'
IMPORTING
    prps_exp   = l_new_proj_no.
IF sy-subrc <> 0.
EXIT.
ENDIF.
Update the fields of 'l_project_definition_upd' as 'X' for the fields which has values in 'E_PROJECT_DEFINITION'.
Get the New Project Number.
MOVE-CORRESPONDING e_project_definition TO l_project_definition.
l_project_definition-project_definition = l_project_definition-project_definition+0(3).
l_new_proj_no = l_new_proj_no+4(5).
CONCATENATE l_project_definition-project_definition '.' l_new_proj_no INTO l_project_definition-project_definition.
TRANSLATE l_project_definition-project_definition TO UPPER CASE.
MOVE-CORRESPONDING l_project_definition TO l_project_definition_stru.
Create the New project with the New project Number.
CALL FUNCTION 'BAPI_PROJECTDEF_CREATE'
EXPORTING
    project_definition_stru = l_project_definition_stru.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
    wait = ' '.
Populate internal table i_method_project for the bapi_project_maintain func module.
CLEAR : wa_wbs_element_table,wl_wbs_element_table,wa_wbs_hierarchie_table,
        wl_wbs_hierarchie_table, it_wbs_element_table, it_wbs_hierarchie_table.
CLEAR : wa_method_project, i_method_project, l_index .
l_index = 0.
LOOP AT e_wbs_element_table INTO wa_wbs_element_table.
MOVE-CORRESPONDING wa_wbs_element_table TO wl_wbs_element_table .
APPEND wl_wbs_element_table TO it_wbs_element_table .
wa_method_project-objecttype = 'WBS_ELEMENT'.
wa_method_project-method     = 'CREATE'.
wa_method_project-objectkey = wa_wbs_element_table-wbs_element.
l_len = strlen( wa_wbs_element_table-wbs_element ).
Setting Levels as reference number.
CASE l_len.
    WHEN '9'.
      l_index = 1.
    WHEN '12'.
      l_index = 2.
    WHEN '15'.
      l_index = 3.
    WHEN '18'.
      l_index = 4.
ENDCASE.
wa_method_project-refnumber = l_index .
TRANSLATE wa_method_project-objectkey TO UPPER CASE.
APPEND wa_method_project TO i_method_project.
CLEAR :wa_method_project, l_index.
ENDLOOP.
l_index = l_index + 1.
wa_method_project-refnumber = ' '. "l_index .
wa_method_project-objecttype = ' '. "'WBS_ELEMENT'.
wa_method_project-method     = 'SAVE'.
wa_method_project-objectkey = ' '.
APPEND wa_method_project TO i_method_project.
CLEAR wa_method_project.
LOOP AT e_wbs_hierarchie_table INTO wa_wbs_hierarchie_table.
MOVE-CORRESPONDING wa_wbs_hierarchie_table TO wl_wbs_hierarchie_table.
APPEND wl_wbs_hierarchie_table TO it_wbs_hierarchie_table.
ENDLOOP.
Update the fields of 'l_project_definition_upd' as 'X' for the fields which has values in 'E_PROJECT_DEFINITION' respectively.
CLEAR : l_project_definition_upd.
p_ddic_name = 'BAPI_PROJECT_DEFINITION_UP'.
struc       = 'l_project_definition_upd'.
fun_struc   = 'E_PROJECT_DEFINITION'.
TRANSLATE: p_ddic_name TO UPPER CASE,
           struc       TO UPPER CASE.
SELECT * FROM dd03l INTO TABLE lt_dd03l WHERE tabname = p_ddic_name.
LOOP AT lt_dd03l INTO ls_dd03l.
ASSIGN ls_dd03l-fieldname TO <c>.
fieldname = ls_dd03l-fieldname .
CONCATENATE fun_struc '-' fieldname INTO fieldname.
ASSIGN (struc) TO <struc>.
ASSIGN COMPONENT <c> OF STRUCTURE <struc> TO <sc>.
ASSIGN (fieldname) TO <def_field>.
IF NOT <def_field> IS INITIAL .
    <sc> = 'X'.
ENDIF.
ENDLOOP.
Update the fields of 'l_wbs_element_table_update' as 'X' for the fields which has values in 'e_wbs_element_table' respectively.
READ TABLE e_wbs_element_table INTO wa_wbs_element_table INDEX '1'.
CLEAR : l_wbs_element_table_update, fieldname1, p_ddic_name, struc, fun_struc .
p_ddic_name = 'BAPI_WBS_ELEMENT_UPDATE'.
struc       = 'l_wbs_element_table_update'.
fun_struc   = 'WA_WBS_ELEMENT_TABLE'.
TRANSLATE: p_ddic_name TO UPPER CASE,
           struc       TO UPPER CASE.
SELECT * FROM dd03l INTO TABLE lt_dd03l WHERE tabname = p_ddic_name.
LOOP AT lt_dd03l INTO ls_dd03l.
ASSIGN ls_dd03l-fieldname TO <c>.
fieldname = ls_dd03l-fieldname .
CONCATENATE fun_struc '-' fieldname INTO fieldname.
ASSIGN (struc) TO <struc>.
ASSIGN COMPONENT <c> OF STRUCTURE <struc> TO <sc>.
ASSIGN (fieldname) TO <def_field>.
IF NOT <def_field> IS INITIAL .
    <sc> = 'X'.
ENDIF.
ENDLOOP.
Append the value of l_wbs_element_table_update TO the table i_wbs_element_table_update for Bapi_project_maintain.
CLEAR i_wbs_element_table_update.
APPEND l_wbs_element_table_update TO i_wbs_element_table_update.
CALL FUNCTION 'BAPI_PROJECT_MAINTAIN'
EXPORTING
    i_project_definition       = l_project_definition
    i_project_definition_upd   = l_project_definition_upd
TABLES
    i_method_project           = i_method_project
    i_wbs_element_table_update = i_wbs_element_table_update
    i_wbs_element_table        = it_wbs_element_table.
   i_wbs_hierarchie_table     = it_wbs_hierarchie_table.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
    wait = ' '.
Please help me to solve the issue.

I am not sure why it is not working?? Try for any other alternate function modules.
But i see one issue with your coding, always check the return table message type and use commit work, instead of sy-subrc check. This fails for BAPI's

How can an ADF Tree be configured to work with varying levels of heirarchy?

We have a need for a Locations tree that represents the Locations heirarchy for any one of our clients. Depending on the client the number of levels in a location heirarchy could range from 1 to 9.
I have created 9 different tree bindings and I can change the tree binding in the jsp page - the example below is for a client with 4 location levels.
<af:tree value="#{bindings.ScdLocs4View1.treeModel}" var="node"
binding="#{backing_locations.tree2}" id="tree2">
For a client with 5 location levels, I'd like to programatically change the value to
#{bindings.ScdLocs5View1.treeModel. How can I do this?
I was thinking I could use the setValue method on the tree control in my page's backing bean. But I have been unable to get a reference to the tree binding.
I don't see an appropriate method for finding a Tree Binding. There are methods for finding an Iterator Binding, an Executable Binding, or a Region Binding (whatever that is). But how do I "find" a reference to a Tree Binding?
I have also given consideration to using a single Tree Binding with 9 levels (or rules in the Tree Binding Editor) and finding a way to programatically "start" the rendering at a particular level (or rule) - in effect telling the ADF Tree control to ignore some number of rules and begin with the specified rule. But I haven't been able to figure out how to do this either.
Help would be greatly appreciated.

Bill,
A tree binding is a particular kind of control binding, so you can find it as a control binding and then cast it to the more specific interface to work with it.

Short Dump while Activating a Heirarchy

Hi Experts,
I have a hierarchy which is in M version, I am trying to copy hierarchy from Quality to Dev system.
The hierarchy in DEV system is in M version. When I try to activate the Hierarchy I am getting a short dump which I am not able to understand.
I have tried also with the ABAP programe to activate it but still I am getting this.
Sorry to paste all the dump but can any one advise what could be reasons behind heirarchy not getting activated.
Thanks,
Tati.
Please find the Dump message.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_RSSH_MESSAGE_HANDLER=======CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    Only message types A, E, I, W, S, and X are allowed.
Information on where terminated
    Termination occurred in the ABAP program "CL_RSSH_MESSAGE_HANDLER=======CP" -
     in "CALL_MESSAGE".
    The main program was "RSSH_HIERM_START_NEU ".
    In the source code you have the termination point in line 11
    of the (Include) program "CL_RSSH_MESSAGE_HANDLER=======CM003".
Source Code Extract
Line SourceCde
    1 METHOD call_message .
    2
    3   FIELD-SYMBOLS: <l_s_msg> TYPE gt_s_msg.
    4
    5   READ TABLE p_t_msg INDEX 1 ASSIGNING <l_s_msg>.
    6   IF sy-subrc <> 0.
    7     MESSAGE x000.
    8   ENDIF.
    9
   10   <l_s_msg>-handled = rs_c_true.
>>>>>   MESSAGE ID <l_s_msg>-msgid TYPE <l_s_msg>-msgty NUMBER <l_s_msg>-msgno
   12     WITH <l_s_msg>-msgv1 <l_s_msg>-msgv2 <l_s_msg>-msgv3 <l_s_msg>-msgv4.
   13
   14
   15 ENDMETHOD.                    "CALL_MESSAGE

Hi Prasad,
Have you changed the 'Object Status' from INA to ACT when using the program RSDG_TRFN_ACTIVATE?
You can also refer to the note SAP Note 1030987 - Activation of transformations dumps
regards,
Ashvin

Error in Creating Level2 WBS using BAPI_PROJECT_MAINTAIN

Hi All,
I am trying to Create a WBS-element at Level 2 of an already existing WBS-element using BAPI_PROJECT_MAINTAIN.
I suppose the 'hierarchy table' has to be populated for positioning a WBS in the structure. But I am getting the error 'The transfered hierarchy is inconsistent. Too many errors.'.
I desire to have the following WBS structure in place :
Project Definition :   PROJ_DEF
WBS for level 1   :   WBS1
WBS for level 2   :   WBS2 (This has to be at a sub-node of WBS1,and NOT at the same level as WBS1)
Can some one give me solution to this error, and suggest a way to create the WBS in this pattern.
Regards,
Somil
I have written the following code to populate the hierarchy table :
l_hierarchy-wbs_element         = 'WBS1'.
l_hierarchy-project_definition   = 'PROJ_DEF'.
l_hierarchy-up                        = ' '.
l_hierarchy-down                    = 'WBS2'.
l_hierarchy-right                     = ' '.
l_hierarchy-left                       = ' '.
APPEND l_hierarchy TO t_hierarchy_table.
l_hierarchy-wbs_element         = 'WBS2'.
l_hierarchy-project_definition    = 'PROJ_DEF'.
l_hierarchy-up                         = 'WBS1'.
l_hierarchy-right                      = ' '.
l_hierarchy-left                        = ' '.
l_hierarchy-down                    = ''.
APPEND l_hierarchy TO t_hierarchy_table.

For create the network and the activity I use this:
*** NETWORK ACTIVITY
   wa_network-network = '000000000001'.
* wa_network-network_type = 'PS02'.
   wa_network-short_text = 'Network'.
   wa_network-wbs_element = ld_wbs.
   wa_network-project_definition = ld_projdef.
   APPEND wa_network TO it_network.
   wa_projmethod-objecttype = 'Network'.
   wa_projmethod-method = 'Create'.
   wa_projmethod-objectkey = ld_wbs.
   wa_projmethod-refnumber = '000001'.
   APPEND wa_projmethod TO it_projmethod.
   CLEAR wa_projmethod.
   d_refnumber = '000001'.
   wa_activity-network = wa_network-network.
   wa_activity-project_definition = ld_projdef.
   wa_activity-wbs_element = ld_wbs.
   wa_activity-activity = '0010'.
   wa_activity-control_key = 'PS02'.
   wa_activity-description = 'Activity 1'.
   wa_activity-plant = '1000'.
   wa_activity-cost_elem = '0000705003'.
   wa_activity-purch_org = '1000'.
   wa_activity-pur_group = '100'.
   wa_activity-matl_group = '90'.
   wa_activity-constraint_type_start = '5'.
   wa_activity-constraint_type_finish = '5'.
   APPEND wa_activity TO it_activity.
   CLEAR wa_activity.
   wa_projmethod-objecttype = 'NetworkActivity'.
   wa_projmethod-method = 'Create'.
   wa_projmethod-objectkey = ld_wbs.
   wa_projmethod-refnumber = d_refnumber.
   APPEND wa_projmethod TO it_projmethod.
   d_refnumber = d_refnumber + 1.
   CLEAR wa_projmethod.

Scheduling not carried out in BAPI_PROJECT_MAINTAIN

Hi All,
I am facing a problem that while updating the basic start date and basic end date for WBS elements using BAPI_PROJECT_MAINTAIN, the scheduling is not being carried out. Basic dates of WBS Elements are saved properly. But the project start date and end date are not updated accordingly.
I am passing the following inputs:
I_PROJECT_DEFINITION = <Project Number>
I_PROJECT_DEFINITION_UPD-PROJECT_DEFINITION = 'X'.
I_PROJECT_DEFINITION_UPD-START = 'X'
I_PROJECT_DEFINITION_UPD-FINISH = 'X'
I_WBS_ELEMENT_TABLE-WBS_ELEMENT = <WBS element Number>
I_WBS_ELEMENT_TABLE-PROJECT_DEFINITION = <Proj Defination>
I_WBS_ELEMENT_TABLE-WBS_BASIC_START_DATE = <Basic Start Date>
I_WBS_ELEMENT_TABLE-WBS_BASIC_FINISH_DATE = <Basic End Date>
I_WBS_ELEMENT_TABLE_UPDATE-WBS_ELEMENT = 'X'
I_WBS_ELEMENT_TABLE_UPDATE-PROJECT_DEFINITION ='X'
I_WBS_ELEMENT_TABLE_UPDATE-WBS_BASIC_START_DATE = 'X'
I_WBS_ELEMENT_TABLE_UPDATE-WBS_BASIC_FINISH_DATE = 'X'
I_METHOD_PROJECT-REFNUMBER = '00000'.
I_METHOD_PROJECT-METHOD = 'SAVE'.
I_METHOD_PROJECT-REFNUMBER = '00001'.
I_METHOD_PROJECT-OBJECTTYPE= 'WBS ELEMENT'
I_METHOD_PROJECT-METHOD = 'UPDATE'
I_METHOD_PROJECT-OBJECTKEY = <WBS element number>
Please let me know the resolution to this problem.

Hi All,
I am facing a problem that while updating the basic start date and basic end date for WBS elements using BAPI_PROJECT_MAINTAIN, the scheduling is not being carried out. Basic dates of WBS Elements are saved properly. But the project start date and end date are not updated accordingly.
I am passing the following inputs:
I_PROJECT_DEFINITION = <Project Number>
I_PROJECT_DEFINITION_UPD-PROJECT_DEFINITION = 'X'.
I_PROJECT_DEFINITION_UPD-START = 'X'
I_PROJECT_DEFINITION_UPD-FINISH = 'X'
I_WBS_ELEMENT_TABLE-WBS_ELEMENT = <WBS element Number>
I_WBS_ELEMENT_TABLE-PROJECT_DEFINITION = <Proj Defination>
I_WBS_ELEMENT_TABLE-WBS_BASIC_START_DATE = <Basic Start Date>
I_WBS_ELEMENT_TABLE-WBS_BASIC_FINISH_DATE = <Basic End Date>
I_WBS_ELEMENT_TABLE_UPDATE-WBS_ELEMENT = 'X'
I_WBS_ELEMENT_TABLE_UPDATE-PROJECT_DEFINITION ='X'
I_WBS_ELEMENT_TABLE_UPDATE-WBS_BASIC_START_DATE = 'X'
I_WBS_ELEMENT_TABLE_UPDATE-WBS_BASIC_FINISH_DATE = 'X'
I_METHOD_PROJECT-REFNUMBER = '00000'.
I_METHOD_PROJECT-METHOD = 'SAVE'.
I_METHOD_PROJECT-REFNUMBER = '00001'.
I_METHOD_PROJECT-OBJECTTYPE= 'WBS ELEMENT'
I_METHOD_PROJECT-METHOD = 'UPDATE'
I_METHOD_PROJECT-OBJECTKEY = <WBS element number>
Please let me know the resolution to this problem.

HEIRARCHY IN BAPI_PROJECT_MAINTAIN

Similar Messages

Maybe you are looking for