Conditions in Which You Cannot Convert a Vision Plan

Certain conditions in a Vision plan prevent the conversion to an iAccess plan.

You cannot change a Vision plan to an iAccess plan if the Vision plan has any of the conditions listed in the following table. If iAccess displays a message about one of these conditions, you must address the problem in Vision before you can convert the Vision plan to an iAccess plan.

Vision Plan Condition	Solution
The Vision plan is mapped to more than one project.	On the Labor tab in Vision Project Planning, adjust the projects that are mapped to the plan.
The plan's Accordion Calendar is set with multiple calendar scales.	Change the plan's Accordion Calendar format to have one bottom scale and one top scale for the entire date range. Avoid setting the bottom scale to Daily, Accounting Period, or Yearly because these are not valid iAccess scales.
The Accordion Calendar's bottom calendar scale is not valid in iAccess.	Change the bottom calendar scale in the plan's Accordion Calendar format from Daily, Accounting Period, or Yearly.
The Accordion Calendar's date range causes values to be in the Overflow column.	On the Accordion Calendar dialog box, extend the date range so that no values display in the Overflow column.
The Vision plan contains extra plan levels between WBS1 and WBS2, or between WBS 2 and WBS3, or the plan has Labor Code plan level rows.	On the Labor tab in Vision Project Planning, remove the plan level rows between WBS1 and WBS2 or between WBS 2 and WBS3, and/or remove the labor code plan level rows. When you delete a plan level row that has a subordinate plan level or assignment rows, those rows are also deleted.
An employee or generic resource, an expense, or a consultant is assigned more than once under the same WBS plan level row.	On the applicable tab in Vision Project Planning, consolidate the assignments so that the employee/resource, expense, or consultant has only one assignment row under the lowest WBS plan level rows.
The Vision plan has expenses at multiple levels. For example, expenses for phase 1 are planned at the phase level and expenses for phase 2 are planned at the task level.	Because it is not clear which level iAccess should select as the expenses planning level during the conversion, you must manually move expenses so that they are at the same level.
The Vision plan has consultants at multiple levels. For example, consultants for phase 1 are planned at the phase level and consultants for phase 2 are planned at the task level.	Because it is not clear which level iAccess should select as the consultants planning level during the conversion, you must manually move consultants so that they are at the same WBS level.
There are plan level rows for units or accounts on the Units tab.	Remove the plan level rows and any planned amounts from the Units tab.
The Use Billing Currency not Project Currency option is selected on the Accounting System Settings form (Configuration > Accounting > System Settings), and the Vision plan's billing currency or cost currency does not match the corresponding project currency. Or The Use Billing Currency not Project Currency option is not selected, and the Vision plan's cost currency does not match the project cost currency.	Change the plan or project currencies so that both the plan and project use the same currencies.
The Vision plan contains WBS rows that are not mapped to WBS records for the project.	Map all WBS rows in the Vision plan to valid WBS records for the project.