ms excel export import guidance primavera 6

3
RPC UK Limited 1 The Courtyard, Hawksworth Est., Thorpe Lane, Guiseley, Leeds, LS20 8LG t. f. e. w. 01943 222 001 0870 432 8424 [email protected] www.rpc.uk.com Page 1 of 3 Dave’s Tips 5 - Microsoft Excel Export and Import Guidance Primavera P6 Client / Server INTRODUCTION The functionality of importing and exporting to Microsoft Excel is widely used for numerous reasons. This document provides general guidance and guidelines for users who utilise the import functionality to change their data in a schedule using an Excel workbook. RULES There are many positive aspects to using a MS Excel workbook to update the data within a schedule. However, there are some rules if this data is to be imported successfully and some rules which assist the user. RULE 1 - The Row 1 Rule After the export functionality has been completed and the Microsoft Excel workbook is created, the user upon opening the file will notice that each workbook tab (excluding the USERDATA tab) has an additional row (row 1) within the table. The content of this row may not make much sense to some users as the terminology contained is unfamiliar. This row is very important if the user wants to import their data from the Microsoft Excel workbook back into Primavera P6 Client / Server. The reason for this is that row 1 contains the application database column names and in most cases this does correspond to the name displayed in the application itself. Fig 1.0 Fig 1.0 shows us that row 1 which contains information like “task_code”, “status_code” e.t.c does not correspond to the data displayed in row 2. Also from this we can see that the application field “Actual Start” is really “act_start_date” within the database. The key point to remember here is… If the data contained in row 1 is modified in any way, Primavera P6 will not be able to import that specific data column. If you want to import from a Microsoft Excel workbook, do not change the data contained in row 1.

Upload: manan-shah

Post on 14-Apr-2015

1.012 views

Category:

Documents


6 download

DESCRIPTION

MS Excel Export Import Guidance Primavera 6

TRANSCRIPT

Page 1: MS Excel Export Import Guidance Primavera 6

RPC UK Limited

1 The Courtyard,

Hawksworth Est., Thorpe Lane,

Guiseley, Leeds, LS20 8LG

t.

f.

e.

w.

01943 222 001

0870 432 8424

[email protected]

www.rpc.uk.com

P a g e 1 o f 3

Dave’s Tips 5 - Microsoft Excel Export and Import Guidance

Primavera P6 Client / Server

INTRODUCTION

The functionality of importing and exporting to Microsoft Excel is widely used for numerous

reasons. This document provides general guidance and guidelines for users who utilise the import

functionality to change their data in a schedule using an Excel workbook.

RULES

There are many positive aspects to using a MS Excel workbook to update the data within a

schedule. However, there are some rules if this data is to be imported successfully and some

rules which assist the user.

RULE 1 - The Row 1 Rule

After the export functionality has been completed and the Microsoft Excel workbook is created,

the user upon opening the file will notice that each workbook tab (excluding the USERDATA tab)

has an additional row (row 1) within the table. The content of this row may not make much sense

to some users as the terminology contained is unfamiliar. This row is very important if the user

wants to import their data from the Microsoft Excel workbook back into Primavera P6 Client /

Server. The reason for this is that row 1 contains the application database column names and in

most cases this does correspond to the name displayed in the application itself.

Fig 1.0

Fig 1.0 shows us that row 1 which contains information like “task_code”, “status_code” e.t.c does

not correspond to the data displayed in row 2. Also from this we can see that the application field

“Actual Start” is really “act_start_date” within the database.

The key point to remember here is…

If the data contained in row 1 is modified in any way, Primavera P6 will not be able to

import that specific data column.

If you want to import from a Microsoft Excel workbook, do not change the data contained in

row 1.

Page 2: MS Excel Export Import Guidance Primavera 6

RPC UK Limited

1 The Courtyard,

Hawksworth Est., Thorpe Lane,

Guiseley, Leeds, LS20 8LG

t.

f.

e.

w.

01943 222 001

0870 432 8424

[email protected]

www.rpc.uk.com

P a g e 2 o f 3

RULE 2 – The Asterisk Rule

Within an exported Microsoft Excel workbook the user may come across columns of data where

the application title (row2) contains an asterisk before the actual column title.

Fig 1.2

Fig 1.2 contains a screen shot of an exported project with the column “Start” displayed. Before

the Primavera P6 column title we can see that an asterisk e.g. “(*)Start”. The presence of the

asterisk indicates that this field if updated in Microsoft Excel will not be imported during the

import functionality into Primavera P6. This can be quite frustrating if the user wants to limit

data modification in the application. However, if a rule of thumb is applied understanding where

any limitations exist is simple.

Rule of Thumb

If you can change it in Primavera P6 Client / Server you can modify and import it with Excel.

This rule does not apply to all iterations but to the vast majority. Also within Primavera P6 the

column “Start” can be many things e.g. Actual Start Early Start, Remaining Early Start, e.t.c. So

ask yourself “how does the database know which data item to update?” The answer is simple, it

doesn’t. In Fig 1.2 we can see that the column “ACTUAL START” has been displayed and does not

contain the asterisk, therefore it can be updated and imported. This is just one example of this

scenario and many, many more exist.

RULE 3 – The USERDATA tab Rule

This rule is very simple indeed. The USERDATA tab created during the export contains the data

format assigned and utilised in the export.

Fig 1.3

Fig 1.3 shows us that when the project was exported, the format to display duration was set to

Day. Also, the units format was set to Hour. This is identified in Fig 1.4.

Fig 1.4

Page 3: MS Excel Export Import Guidance Primavera 6

RPC UK Limited

1 The Courtyard,

Hawksworth Est., Thorpe Lane,

Guiseley, Leeds, LS20 8LG

t.

f.

e.

w.

01943 222 001

0870 432 8424

[email protected]

www.rpc.uk.com

P a g e 3 o f 3

In some education and training materials it stipulates that the user preferences set during the

export MUST be the same as those in the import file. This is not the case as it depends on the

data to be imported. For example, this rule does apply if you are importing resource units, as one

users preferences may be set to days for the import but the export option is set to hours.

However, for any data type where a rule is not displayed in the USERDATA worksheet the data

imported is not affected (e.g. Cost Accounts, Activity codes, e.t.c.).

RULE 4 – It’s an Excel Workbook

Above all else the user should not lose sight of the fact that the exported file is nothing more

than an Microsoft Excel workbook complete with all of the great functionality of this application.

For example, Macros, formula, control panels and symbols can all be created, assigned, populated

and exist within any Microsoft Excel workbook file and the results of these functions can be

imported into Primavera P6 Client / Server tool. This can be used to create some aesthetically

pleasing interfaces where non Primavera P6 users can access, review and even post schedule,

cost and resource data changes/updates.

RPCuk Knowledge Zone

In keepin g wi th ou r phi losophy of addin g va lu e, we want our c l ients, par tners and

exp lorers o f ou r web si te and n ewsletter sub scr ibers to view th e ir interact ion wi th

RPCuk as a rewardin g exper ience.

We bel ieve th at kn owledge tran sfer i s an in tegral part o f any re lat ion sh ip and, over the

years , we have acqui red a wealth o f exp er iences and learn ed - u sua l ly th e hard way ! -

some u seful t ip s and t r i cks which we are more than happy to sh are.

We wi l l regular ly b e pub l i sh ing b r ief in gs on a var i ety o f p roject management and

p lann ing top ics that may be of interest . In add i t ion, we intend to o f fer useful too ls and

l inks to oth er resources throu gh ou r RPCuk T ip s and Tr icks Sect ion

I f y ou have n ot a lready done so, s ign up to th e RPCuk e lect ronic n ewsletter and keep

check ing th e Knowled ge Zon e for more Oracle Primavera P6 hints, tips and shortcuts.

We hope you find the knowledge zone useful and informative. If you would like to contribute to

the knowledge zone or indeed have any topics / suggestions please feel free to contact us on

01943 222001 or by emailing [email protected] – any feedback would be most

welcome.