How do you get around the required (changing)WBS import export requirement/issue? i must be missing something. It is crazy that you cannot import the cost accounts and costs. I am simply importing the costs from an original file to a later file of the same name. Costs import fine. I will only import the cost accounts if you also import the WBS - and being that the WBS uses the project name, even though the same file that rev number is different and over-writes the WBS and blanks out most of it because of the slight name difference - how crazy is this. Let me know if a way around this, I must be missing something. Its crazy, why not just activity ID's like it used to be?
How do you get around the required (changing)WBS import export requirement/issue?
Forum Sponsor
Top Posters
Julian Pegg
1 posts
Peter Nagy
2 posts
Raymund de Laza
17 posts
Syed_Asad
0 posts
Tony Greyvenstein
0 posts
Ahmed Al-Jubouri
13 posts
Umar Alvi
3 posts
Sibusiso Mahlalela
0 posts
Michael Samanyayi
3 posts
Simon Gumede
0 posts
try this
1. copy the project that has all of the cost codes
2. create a dummy activity in the project that has all of the cost codes and assign ALL of the cost codes to that dummy activity
3. delete all other activitiies
4. export that project with the 1 activity to an xer file
5. open the project that you want all of the cost codes in and import the xer file
6. during the import process select add to existing
7. in the next part of the import process select modify and check do not import for all items except the 1st section for activity and import the one activity project inot the other project
8. now delete the dummy activity in the opened project
Thanks - both of you for both answers.
depends on what version you are using. If you have a 32 bit machine with p6 on it you can import the cost codes suing an excel spreadsheet.
or you can use sdk
John,
P6 treats data ina databse not as files, so if you consider that the same Activity ID can exist in multiple projects, then there must be something in the database that create a unique value for each activity. In the case of P6 - projects, project ID's and the corresponding WBS ID are all stored in the same data table and by requiring each activity ID to have a corresponding WBS ID is how that uniqueness is obtained.
The easiest solution to your problem would be to use Excel's Search and Replace field to modify the WBS ID column in your import file such that the PROJECT ID/WBS ID matches the new project you are going to import into.