Problems importing with V.5.

Oliver, Valentin



As far as I remember this issue was solved by SP2 and the procedure described by Nimbu.



Dieter

All,



I get that error even though I am on P5 SP1 on a stand-alone.



I think when UDF’s are used and the programme isn’t scheduled and refreshed before exporting, an orphaned record error can occur.

Hi Chris,



I tried using your spreadsheet and got some 13 orphaned records, which I then manually deleted from the UDF_value and used the build xer function. After importing in Primavera though, I am missing most of the budgeted labor units and Units % complete.



Any idea why?



Regards,



Valentin

Another solution that worked for me is this:



Download the SP2 from Primavera Knowledgebase and update the database (ConfigAsst.exe file in the SP2 database update folder).



Run database queries/scripts on the source database (the database where the XER was exported from). See steps below.





Run the appropriate script below on the database that the XER was exported from

- For Microsoft SQL Server, run the script as PRIVUSER

- For Oracle , run the script as ADMUSER

- For MSDE Primavera 5.0 Standalone installation, save the appropriate script to the root of the C:\ drive and run the following from a DOS command prompt:

(Start > Run > type ’cmd’ and click OK): osql -U sa -P prima -S localhost\primavera -d pmdb$primavera -i c:\delete_orphaned_UDFVALUE_##.sql





Note: RUN THIS SCRIPT ON A BACKUP OF THE DATABASE FIRST!

I too have been plagued by this error. We are running three machines with standalone versions of P5 and have generated this error whilst checking out and checking in between the different PCs.

I have found the easiest work around was to use Primavera’s XER file Parser excel sheet to solve prevent the error.



http://knowledgebase.primavera.com/attachment/PATTLNK_632006_536-xerFil…



You can load the XER file into the spreadsheet and using the diagnostics, identify the orphaned UDF values.

In Diagnostic window, select "Cross check FK"

Then Table "Task" & Field "Task_id"

Then Secondary Table "UDF Value" Field "FK_id"

This will identify all orphaned values

I have written a quick macro then to delete all the orphaned records which I can try to post up if it’s of use to anyone.

You then have to use the build XER function and re-import.



This works well for us, but is still simply a work around for a problem that we still cannot really identify. We cannot have two people working on a schedule at the same time as we are running standalone, which rules out primavera’s documented cause.

Regards

Chris

or may be "...we have noticed your problem. This is a case for enhancement request...please inform us if you prefer to add your problem to enhancement request..." !!

Try Service pack 2!

Ronald,



Do you have any suggestion for my problem posted above on 8Hrs in P3 and 10Hrs in Ver 5.0



Cheers, Amar.

Unfortunately this problem occurs also after SP1 is installed. And the reason is that Custom Fields for deleted activities are stored in the *.xer file.



So I have only one solution:

Generate XLS files with Acivity list and all user fields and link them to MS Access database. After that you will be able to write a query showing all user field records that are useless and should be delited.



Otherwise you will have to delete all UFs if they are not so important for you.



The same solution for WBS user fields.



Regards!

hi Marcio and P5 user.



I have other solution for this problem:



1.- Copy the project to other EPS.

2.- Now export the project copy to file *.xer and ready.







This method was not given by primavera

Thx so much for ur help.i’ll let u know at the first time if i have further information.



Best Regards



Sandwind He

External Early Start and External Late Finish are two data fields that were just added with Version 5.0. In the data base documentation, they call it "Early Start/Late Finish dates for sharing schedules with Primavera Contractor."



More than this, I do not know at present time. Let me know if you come up with further information.

i found that i can not fill the external early start and finish data in Primavera5.0.and i dont know in which case i should use it...why~who can tell me the reason?





Thx & Best Regards



Sandwind He

Dinesh, Thanks for your suggestions. Unfortunately, I think my problem is different. I am the only user in the company. When you get time, can you please revisit my query? THanks, Amar.

Hi there,



"This can happen for a variety of reasons. For example, if multiple users are in a project and user 1 runs a global change or fill down for a user defined field and user 2 is deleting an activity at the same time. The global change will run, however when you export the XER file and try to import it, the program will check and not find the activity the UDF is pointing to".



Do an new export of the same file and import it again and it will work.



Regards



Dinesh

Friends,



By Default, the number of hours per day in Version 5.0 and 3.1 is 8 Hours.



I have 10 Hours per day as per our company norms and the same is set in Version 5.0



I have to import a file from Version 3.1 and provide links to a project in Version 5.0



When links are given from file imported to Version 5.0 (Project 1) and the file created in Ver 5.0 (Project 2) , the links are not seem to be realstic.



For Eg:

Imported File: Project 1



Activity ID 10 : Finish on : Jan 01



Created File: Project 2



Activity ID 101 : FS with Activity ID 10

Duration 1 day



Now after scheduling



Activity ID 101 Starts on Jan 01 and ends on Jan 02.



This is because, for Project 2, still 2 hours left on Jan 01 and the activity completed 2 hours before the closing hours on Jan 02.



Practically, I wish the activity 101 to start on Jan 02.



How to set this? ( Giving lag is one option but laborious)



Cheers, Amar.

YOU HAVE FOUND SOLUTION TO THE PROBLEM "CVRJC-3802-1", OF BEING THEREFORE I REQUEST TO YOU TO MAKE IT TO ME ARRIVE BEEN THANKFUL



Kind regards,



DANIEL S.



[Deleted by Moderator - English only, please.]