does anybody know a (preferably simple) functional procedure to transfer a WBS from one project definition to another? In our case, a number of WBS elements must be financially 'isolated' from the main project and be managed seperately in a new project definition. The problem is that actuals are already posted to those WBS elements, so the old trick of renaming-recreating-renaming can't be applied.
For the tech heads, there is table PRHI which handles the linkage WBS->project definition. Does it sound like a good idea to directly tackle this table with an ABAP (select single for update) and to re-shuffle the WBS assignments this way? (Hello database inconsistency??)
In your opinion, is the re-assignment of existing WBS elements to another project definition an approach that makes sense, conceptually speaking? How do companies usually adapt their project management when - for reasons of organisational re-structuring - partial projects are split off from an initially common project and the financial responsibilities for these partial projects are transferred to a new branch or new legal entity?
Any input is appreciated
RFB
