How To Import WBS From Excel To Primavera P6 Using The SDK
How To Import WBS From Excel To Primavera P6 Using The SDK
In this tutorial we explain how to use the Oracle Primavera P6 SDK to import a
WBS from Excel to Primavera P6. We are using the WBS.xls P6 SDK
spreadsheet made available by Oracle Support. The SDK is a very handy tool,
but the data must exactly respect the required format, we used a sample
WBSand a step-by-step guide to prepare the data to be imported. We assume
you already have the Primavera SDK installed.
Tutorial Assets
The following assets were used during the production of this tutorial.
WBS-Import-P6-Tutorial.xls
WBS.xls
When the wizard screen comes up, select Delimited, and click Next.
Make sure to format the columns as Text (if your code is 01, Excel will keep it
01 as text, otherwise it will change to 1.
The Level column on Worksheet 3 is not needed for this tutorial. I have just
added it to show that we can determine the level of each WBS by counting
how many times the separator (or the delimiter) is repeated.
The green L-columns contain some text formulas that will recombine part of
the WBS Path to build parent and children fields that well need for the import.
The next steps might seem unintuitive, but they are important to follow
correctly. Well then clean things up afterwards.
Copy the data as follows:
Copy the green-L2 data again and this time paste it to the bottom of the
data in the Parent column on Worksheet 4
Copy the green-L3 data and paste it to the bottom of the Child
column on Worksheet 4
Copy the green-L3 data again and this paste it to the bottom of
the Parent column
Copy the green-L4 data and paste it to the bottom of the Child column
Copy the green-L4 data again and this paste it to the bottom of
the Parent column
Copy the green-L5 data and paste it to the bottom of the Child column
Child col
L2 data
L3 data
L4 data
L5 data
Actually thats the most important step in this tutorial, in order for the
SDK (a relational database) to understand the structure of the WBS; this
one must be presented as Parent and children table.
Next, select ok
In the column check the same relation, I put a formula to check if there is the
same item in parent and child. Click the column Filter and select only No.
This will filter out any other entries we dont need for the import.
The WBS Code column is automatically generated by removing from the WBS
ID CHILD code the equivalent Parent WBS ID.
Now our WBS is ready to be imported to Primavera P6.
In Admin -> Admin Preferences, check the maximum WBS Code length that
Primavera P6 can accept. The default of 20 will work for this tutorial, however,
you may want to increase this value to 30 or 40 characters for future imports.
Youll want to have an empty project already setup in P6 that we will import to.
If you dont have one, login to Primavera and create an empty project now,
then come back to this step.
By default, the first level of the WBS is the name of the project.
In this case change the name of the project to SAMPLE, once you finish
importing you can modify the name.
As expected, only the WBS root node is imported into the spreadsheet.
Copy and paste from the Excel file the columns Parent WBS ID, WBS Code
and the WBS Name
Dont overwrite the root node that is already there.
It will take some time to process the data (the SDK is famous for very being
slow).
Step 9 Enjoy
Wrap Up
We explained how to import a WBS dictionary to Primavera P6 using Excel
and the P6 SDK. Here are some examples as to why it is very useful for
planners:
2. If your schedule is using activities codes, you can easily generate WBS
in Excel and imported back to P6.
3. You can design a first cut of your WBS outside Primavera, using many
freely available WBS utilities. Once it is approved, it can easily be
imported to Primavera. We suggest you try WBStool, a mind mapping
WBS tool. All WBS or mind mapping tool can export the WBS path to
Excel, which means this file can be used as an integration tool to
Primavera.
If you want to understand the logic behind all this data processing,
google hierarchical database model.
Using CTE recursive query in any Database you can generate the WBS
Parent and WBS child in one operation. But if you are just a planner, SQL
might be black magic for you (as it is for me). The approach discussed in
this Tutorial will do the trick, and will you save a lot of time doing what all
planners hate the most manual typing.