While doing update transfer in the same programme with different update, after impoting into the programme, the WBS not found in the programme. but the Import was successful.
Member for
19 years
Member for19 years
Submitted by Rodel Marasigan on Fri, 2010-03-26 19:57
I also experience the same before and when I done my investigation why it was happening I found out that if you used import to update the existing projects it will not touch or delete Activity ID but can add if not exist, update WBS if the activity is already assigned to existing WBS and many others. The reason why is because these are the basic unique identifier of an existing project on Primavera database. During my analysis, I tried a force update using direct modification on Primavera database table and lost other connections to related tables like PROJWBS, TASKRSRC, ROLES, RSRC, ACCOUNTS..etc. It will import everything if you select create a new project instead of update existing.
Note: XER will not modified existing records on TASK table for Activity ID, Resource assignment, Resource, WBS and will add instead if these are change from the original Projects. Sometimes it may not also update relationship, cost account and roles to existing activities. You can check all fields that not updatable using the excel export. Any fields with * is not updatable.
Member for
16 years 3 monthstry insert new for the wbs
try insert new for the wbs
Member for
10 years 3 monthsWhile doing update transfer
While doing update transfer in the same programme with different update, after impoting into the programme, the WBS not found in the programme. but the Import was successful.
Member for
19 yearsRE: WBS Names not updating during import to P6
Ian,
I also experience the same before and when I done my investigation why it was happening I found out that if you used import to update the existing projects it will not touch or delete Activity ID but can add if not exist, update WBS if the activity is already assigned to existing WBS and many others. The reason why is because these are the basic unique identifier of an existing project on Primavera database. During my analysis, I tried a force update using direct modification on Primavera database table and lost other connections to related tables like PROJWBS, TASKRSRC, ROLES, RSRC, ACCOUNTS..etc. It will import everything if you select create a new project instead of update existing.
Note: XER will not modified existing records on TASK table for Activity ID, Resource assignment, Resource, WBS and will add instead if these are change from the original Projects. Sometimes it may not also update relationship, cost account and roles to existing activities. You can check all fields that not updatable using the excel export. Any fields with * is not updatable.