| Solution ID: prim17577 |
| Update Existing does not Update Resource Units & Prices during import of an XER |
| Status: Reviewed |
| Version(s): 3.x, 4.0, 4.1, 5.0, 6.0, 6.1, 6.2 |
From Primavera OCP
| Problem: | Update Existing does not Update Resource Units & Prices during import of an XER
|
| Cause: | This is by design. The system only updates the rates which have an effective date greater than the computer’s system date. If you update prior rates, than the system will need to recalculate resource cost for all resources which may not be accurate. |
| Fix: | Workaround: Change the computer’s system date to be prior to whatever ’effective date’ you want to update. Import the project, than change the system date back to be “today’s” date. For example: In the example below, in one database, the resource has a Max Units/Time of 8h/d and Price/Unit of $30.00/h. If you export that project to a database where the Max Units/Time are 10h/d and the Price/Unit is $33.65, in order for the change to take effect (i.e. go to 8h/d and $30.00/h), the system date of the computer has to be before Jul 4, 2001. Before – Resource’s existing database information:
After import from other database:
NOTE: We have found that it may be necessary to exit & then launch the software to get the budgeted cost to update after performing this workaround. The ability for Update existing to update Units & Prices for past time periods not just future ones is in an existing enhancement request. |
