The Move Work Package import spreadsheet must contain a list of work packages and the new control account ID as well as any code assignments on the work package:
CA1
CA2
CA3
WP
NEW CA1
NEW CA2
NEW CA3
Work package codes C1 through C9
The first row of the spreadsheet is a header row and is ignored in the import.
The C1 through C9 fields always reference work package code fields in Cobra.
These following validations are performed on the spreadsheet before the process begins:
The target control account must already exist in Cobra before the move.
The work package cannot be complete.
The target control account cannot be complete.
A work package of the same name cannot already exist in the target control account.
The NewCA1, NewCA2, NewCA3 values from the target control account are used to update the linking fields in Open Plan, any related activity will be linked to the target control account.
The following validations are performed on the work package code assignments (C1 through C9):
If the work package code assignments have a validating code file, the code from the spreadsheet must already exist in the code file.
The code assignments in the file are checked to see if the codes exist in the Open Plan code file. The Open Plan prompt for the work package code is used to determine what code in Open Plan will link to the work package code.
If Open Plan is not setup to have a prompt for the code assignments in Cobra, the import proceeds with no error validation.
If Open Plan is setup to have a prompt for the code assignments in Cobra and the spreadsheet has blank code assignments, then when the Move Work Package workflow is complete, Open Plan will remain as it was before the import. That is, it will remain blank if it was blank, and retain its value if it had a value before the Import Move Work Package process.
For example, you have a C4 work package code field in Cobra with a value of XX and the C4 prompt in Open Plan is blank. If C4 is blank in the spreadsheet, then after the completion of the Move Work Package workflow, C4 in Cobra will still has a value of XX and the C4 prompt in Open Plan will remain blank.
If the control account linked fields are a code field in Open Plan, the code must exist in the Open Plan code file.
When importing a code assignment, the Open Plan code assignment with a matching prompt is only updated if that code is unrotated. Similarly, if the code is a user character field, the field must be unrotated.
In the example below, CA1 = 11011 and NEW CA1 = 12011 should both exist in the WBS code in Open Plan, otherwise an error will occur.
CA1 |
CA2 |
CA3 |
WP |
NEW CA1 |
NEW CA2 |
NEW CA3 |
C1 |
C2 |
C3 |
C4 |
C5 |
C6 |
C7 |
C8 |
C9 |
11011 |
|
|
PM1000 |
12011 |
|
|
1.1 |
1200 |
|||||||
11011 |
|
|
TM500 |
12011 |
|
|
1.1 |
1200 |
|||||||
13011 |
|
|
TXT300 |
12011 |
|
|
1.1 |
1200 |
Create a Move Work Package workflow type
Move a work package to a new control account
Schedule a Move Work Package spreadsheet import