Primavera Sdk Excel File
Step 2 – Split the WBS Path into Distinct Levels Copy the column WBS Code from “Worksheet 1” to “Worksheet 2” in Excel. We will use the Text to Columns function on the Excel Data tab (Excel 2010), it a very easy tool to split one column by delimiters into multiple columns. Highlight the WBS Code column, and click on Text to Columns. When the wizard screen comes up, select Delimited, and click Next.
Free download primavera sdk excel Files at Software Informer. The Microsoft® Silverlight™ SDK contains documentation, online samples, quickstarts and tools for.
Set the delimiter to a dot “.”. 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. Here’s the result. Zte join air connection manager.
Step 3 – Organize The WBS by Level. Copy the new split columns to “Worksheet 3” and paste each under the appropriate L1, L2, L3, L4 or L5 heading (use the yellow L columns, not the green ones). If you have more levels, just adjust the spreadsheet to add them in. 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 we’ll need for the import.
Step 4 – Organize the WBS by Parent & Child We’re going to combine all of the green L-columns now on Worksheet 4. Start by copying the data under green-L1 and pasting it to the Parent column on Worksheet 4.
Copy the green-L2 data and paste it to the Child column on Worksheet 4. The next steps might seem unintuitive, but they are important to follow correctly.
We’ll 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 Essentially the column data should be combined like this. Step 7 – Open 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. You’ll want to have an empty project already setup in P6 that we will import to. If you don’t 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. Step 8 – Open The P6 SDK WBS.xls As usual input the password, and click on Update Project List. Select the empty project you created.Make sure you select the right project.
Click on “Get WBS”. 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 Don’t overwrite the root node that is already there. Click “Set WBS”.
It will take some time to process the data (the SDK is famous for very being slow). 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:. It is very easy to import a standard WBS into your schedule (perhaps your company Cost breakdown Structure). If your schedule is using activities codes, you can easily generate WBS in Excel and imported back to P6. 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, 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. Things for you to try:. 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. Master Mimo, Here in Brazil, we have a forum to discuss planning techniques and other subjects with almost 6.500 users. Today I posted a question about this problem, but so far I received no reply.
Man, this problem is really sucks. Follow my post: Did someone managed to log on the worksheets that make up the SDK, accessing the BD P6 8.2 in Windows 7? I could see that: when Windows version is XP, the ODBC driver who is responsible for connecting P6 is usually installed and is available in ADMINISTRATIVE TOOLS / ODBC DATA SOURCES / SYSTEM DATA SOURCES.
Thus, it allows any adjustments (if needed) in the alias of the database refers to “public username” and “public password”. However, when Windows version is 7, despite having installed the SDK BD (PMSDK), the ODBC driver is not available in the path mentioned above. Thus there is no way to establish the connection between Excel spreadsheets and Primavera´s BD. Someone has a solution to help? ——– So in a configuration with windows xp + office 2010 (32 bits edition) + Primavera 8.2 = connection works fine! I already tested this configuration and works fine with no errors regarding connection problems.
Mimo, I think the problem is not with any version of Primavera. I´m really convinced that the problem is with version of Windows. But I has a friend with the follow configuration: windows 7 (32 bits edition) + Office 2007 + Primavera version 7. This configuration works very well. According him, he tested the same configuration changing only the Primavera´s version to 8.1. Works fine too!
Well My configuration: Windows 7 (64 bits edition) + Office 2010 (32 bits edition) + Primavera 8.2 = nothing working. No SDK spreadsheets accessing the Primavera´s BD. Hi Bruno, I did a quick search on Oracle Support and found this info. It seems the Win7 security is a bit different.
Hope it helps. Additional security in Windows 7 conceals the 'Primavera P6 SDK' data source from users until the 'ODBC Data Source Administrator' is launched directly from the C:WindowsSyswow64 folder using the 'Run as Administrator' option. Solution There are 2 methods of verifying that the Primavera Software Development Kit (SDK) has been installed: 1) Launch Windows Explorer, navigate to C:WindowsSysWOW64 and locate odbcad32.exe Right-click odbcad32.exe and select 'Run as Administrator'. This will open up the ODBC Data Source Administrator. Select the System DSN tab. The Primavera P6 SDK data source will be listed.
2) Go to Start, Run and execute Regedit. Navigate to HKeyLocalMachineSoftwareWow6432NodePrimaveraUniversalFrameworkDrivers There should be a key folder called 'PrimaveraSoftwareDevelopmentKit'. After a bit more digging, it seems there is a bug NOTE: If using the SDK in a 64-bit environment the utilities will not function if Microsoft Office is installed to the default location of “C:Program Files (x86)” This causes an existing networking bug to occur where the networking layer is unable to parse program locations that contain parenthesis in the path to the executable which is attempting to connect to Oracle. Solution To resolve this problem try either of the following solutions: SOLUTION 1: Use a version of the Oracle software that contains the fix for Bug 3807408. NOTE: Currently the following patches have been released on Windows: Windows 32-bit 9.2.0.7.0 Patch 6: Apply Patch 4928723 or later 10.2.0.1.0 Patch 4: Apply Patch 4923768 or later 10.2.0.2.0 Patch 5: Apply Patch 5383042 or later 10.2.0.3.0 or later contains the fix Windows 64-bit AMD64 and INTEL EM64T 10.2.0.1.0 Patch 4: Apply Patch 4923787 or later 10.2.0.2.0 Patch 5: Apply Patch 5388871 or later 10.2.0.3.0 or later contains the fix For previous versions on Windows please use SOLUTION 2 for now.
SOLUTION 2: Find the location of the application that is generating the error. Check the path to this location and see if it contains any parenthesis. If so, you must relocate the application to a directory without any parenthesis in the path.
Hello All; I have installed Pruimavera P6 Version 8.2 Standalone on my laptop & Configured the database. Then I Run the setup again and chose 'change' After this i selectd The 'Software development kit installation' Then I Configured the database again named 'PMSDK' I selected the user name as 'pubprm$pm' & Entered the same password that i entered during primavera installation (Prima123Vera). Now 'PmSDK' is also configured successfully.
Now I am Getting 2 data base 'PMDB & PMSDK' when I run P6. I followed these all steps through a tutorial 7 Did not do by own. Now the issue is that what to do next to connect Primavera to excel. (I have the utility files for SDK but in those files I am not able to work) Can anyone clear me the concept for using SDK. I am new to the whole P6 experience, just installed v8.2 myself. I used to use RA with P3 extensively, and therefor starting with P6 my first interest was on how to access the data 'throught the kitchen door' I dont quite understand the intended concept behind what the call the SDK (Software Development kit).
I did some setups on different machines with different settings, some with and some without the SDK. It seems to me that installing the SDK does nothing more but create a database alias to connect to an existing database - so where does Sortware Development come in? I achieved exactly the same by NOT installing the SDK, but create Data Connections through the Control Panel (in Windows 7: Control panel Administrative Tools Data Sources (ODBC)). I managed to then access the data from Excel by using ADODB.Connection & ADODB.Recordset objects in VBA. I am using 3 Databases at the moment - 1 on my local machine, 1 on the server at my work site and 1 on our head office servers. I can read (and write) data to any of the 3 by changing the database name (or alias), with or without intalling the SDK.
To answe you question on the use of the SDK: the way I use it is by writing my own code in VBA. To do this you need some knowledge of Visual Basic Programming as well as a basic knowledge of using SQL. Not knowing what your intentions are with this and how you want to use it, just keep in mind when writing your own code: Reading (SQL Select) is easy and safe, changing/updating (SQL Update) gets a bit more tricky and dangerous. Adding data (SQL Insert) is VERY dangerous.
Excel Example
Regards Andre.