| Solution ID: prim23602 |
| Price/Unit is not converted correctly on resource assignment level when importing a P3 project. |
| Status: Reviewed |
| Version(s): 4.1, 5.0, 6.0 |
From Primavera OCP
| Problem: | Price/Unit is not converted correctly at the resource assignment level when importing a P3 project. However, the Resource dictionary is updated correctly, which calculates the Budgeted Cost correctly. |
| Problem: | Duplicate Resource Assignments are created when importing a P3 project in Project Management to update an existing project. |
| Cause: | The data in fields listed below is different from the data that is in the XER file. If this data has changed, Project Management will add the Resource Assignment as a new resource. Price / Unit Activity ID Note: This is by design |
| Fix: | If there is no price per unit defined for the resource in Project Management, the project default price/unit is used on the resource assignment. If this project is export to P3, the price per unit is assigned on the resource as the default price/unit. Then when importing the P3 project a duplicate resource assignment is because a different price per unit is defined.
|
| Fix: | This known problem in Project Management is currently under review and may be corrected in a future release. Workarounds: #1: After import, run Tools, Recalculate Resource Costs. #2: If import through update (i.e. choosing update existing), during the import, modify the Import Configuration to delete unreferenced for Activity Resource Assignments. Note: Don’t use this option if you have Timesheets with the project.
|
