Columns for import to P6

Hello everyone,

I have a question; Is it possible to import columns with (*) to P6? I mean columns such as "Physical % Complete" or "Budgeted labor unit".

Thanks in advance

Z
Zoltan Palffy 👤 Member for 16 years 10 months

if you read post #8 on Tue, 2019-05-07 07:31

I mentioned that they were importable 

Z
Zhang Haixiang 👤 Member for 21 years 1 month

It's not that easy.

the budgeted labor unit with * is the data exported in TASK sheet of the exported XLS file, which is a summary of all resources assigned to an activity.

if you use UDF, what number you will put in it, sum of all resources for an act or bugdet of a certain resource of the act?  anyway when you use global change, you need to select which resource will be changed, or P6 will change all resources with that UDF number. 

Actually the bugdeted Unit in TASKRSRC sheet is importable,you can import budget unit for each resource to get the correct sum.

Z
Zoltan Palffy 👤 Member for 16 years 10 months

Zhang 

you can reate a work around as I have posted below or you can use sdk 

Z
Zhang Haixiang 👤 Member for 21 years 1 month

I think it is impossible. * means the data can not be imported.

e.g."Budgeted labor unit" is summary data calculated from all labor resource.

you need to import the budgeted unit for each resource, and then P6 will calculate the  "Budgeted labor unit" for you.

S
Santosh Bhat 👤 Member for 21 years 1 month

Parisa,

You can copy and paste into PRA much easier than into P6. Try it, copy a set of columns out of PRA and paste into excel, modify one of the cells and then copy and paste back. Then you can do such for all the data you want to change.

 

Probably the only useful feature of PRA to make it worth keep using.

P
Parisa Mohsenizadeh 👤 Member for 7 years 1 month

Hello Steven,

Excuse me because of not making my question as clear as possible. Actually, I need columns such as budgeted labor unit in Primavera Risk Analysis but the problem is that I have the related information in an Excel file so first I should export from P6 into excel and match the info and then import it in P6 in order to have the columns such as budgeted labor unit in my P6 file. Then it will be ready to import the Xer file into Primavera Risk Analysis, but the problem is that columns such as budgeted labor unit have (*) in exported excel file so it is impossible to put info in them and then import it again in P6. I also have tried a user defiened field (UDF) for making a global change in P6 for budgeted labor unit column but that didn't work too. Is there any work around?

Thanks in advance

S
Steven Auld 👤 Member for 8 years 8 months

If you are importing into Primavera Risk, why are you using the excel import instead of just importing the xer file?

You may have to open the xer file in notepad first to change the P6 version if you are using a version that is not compatible with Primavera Risk.

Steven

P
Parisa Mohsenizadeh 👤 Member for 7 years 1 month

Hi,

Actually I want to use the Xer File of P6 in order to import it in Primavera Risk Analysis, so I need this information to be in the related columns but due to they have (*) when exporting to excel I can't put the needed information in these columns. Also I couldn't use global change in order to match these columns with the user defined field. Do you have any idea regard this problem?

Thanks in advance 

P
Parisa Mohsenizadeh 👤 Member for 7 years 1 month

Hello,

Actually I have problem for using global change for columns such as "Budgeted Labor Unit", "Actual Labor Unit" and "Remaining Labor Unit". Is it possible for you to help me in this regard?

Thank you

Z
Zoltan Palffy 👤 Member for 16 years 10 months

yes Budgeted unist is importable any coulmns are what you do is create a work around

create a udf (uder defined field) and make the field TYPE the same TYPE as the column that you cannot import

Then import that UDF

Now run a gloabl change where  the Column that is not importable equals the udf

I do this if I need to import expected fnish dates which are not importabale 

There is alwasy a work around 

S
Santosh Bhat 👤 Member for 21 years 1 month

No, fields with an asterix are calculated fields within P6 and cannot be imported.

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