Cobra Help System

Validity Check Error Codes and Messages

Learn about the error messages related to the Validity Check process, as displayed in the process log, along with their resolutions.

Error Message Cause and Resolution
Baseline dates for <Control Account or Work Package>: <date> do not align with the <Control Account or Work Package> baseline dates. This error occurs when the baseline dates of the control account do not cover the duration of the baseline dates of the work packages.
To resolve this error:
  • Run the Validity Check Wizard and select Adjust Control Account dates to exactly span Work Package dates on the Business Validations page.
Baseline start and finish dates do not span baseline resource assignments for <Work Package> <Work Package ID> This error occurs when the baseline dates of the work package do not cover the time-phased dates of the resource assignments.
To resolve this error:
  • Run the Validity Check Wizard and select Adjust Work Package dates to span resource assignment dates on the Business Validations page.
Could not check for undefined results for resource <resource>. It may reference result fields which do not exist in the TPHASE table This error occurs when executing a query that involves TPHASE and CAWP. Data integrity issues may arise if non-default results were not added through the Cobra Data Tool.
To resolve this error:
  1. Check the TPHASE table and identify the missing results.
  2. Launch the Cobra Data Tool and select the data source to edit.
  3. On the Options page, select Define results and click Next.
  4. On the Define Results page, add the missing results.
Could not fix undefined Results for resource <Resource name>. This error occurs because there was an issue when updating the TPHASE table that could not be resolved.
To resolve this error:
  1. Check the TPHASE table and identify the missing results.
  2. Launch the Cobra Data Tool and select the data source to edit.
  3. On the Options page, select Define results and click Next.
  4. On the Define Results page, add the missing results.
Could not get list of results totals. This error occurs when retrieving a list of result totals.
To resolve this error:
  1. Check the TPHASE table and identify the missing results.
  2. Launch the Cobra Data Tool and select the data source to edit.
  3. On the Options page, select Define results and click Next.
  4. On the Define Results page, add the missing results.
Couldn't insert the account default values. This error occurs when the Validate cost sets option is selected on the Project and Apportionment Validations page of the Validity Check Wizard and you are inserting records to the ACCOUNTS table.
Couldn't insert the classes link default values. This error occurs when the Validate cost sets option is selected on the Project and Apportionment Validations page of the Validity Check Wizard and you are inserting records to the CLASSESLINK table.
Couldn't insert the cost rep default values. This error occurs when the Validate cost sets option is selected on the Project and Apportionment Validations page of the Validity Check Wizard and you are inserting missing record to the COSTREP table.
Error selecting data to check for <Work Package> dates spanning resource assignment dates. This error occurs when the Work Package dates correctly span resource assignment dates option is selected on the Business Validations page of the Validity Check Wizard and you are executing a SELECT statement for the CAWP, CLASSES, and TPHASE tables.
Error updating <Control Account> forecast dates to exactly span <Work Package> dates This error occurs when the Adjust Control Account dates to exactly span Work Package dates option is selected on the Business Validations page of the Validity Check Wizard and you are executing an UPDATE statement to update the CAWP table.
Forecast dates for <Control Account or Work Package>: <date> do not align with the <Control Account or Work Package> forecast dates. This error occurs when the forecast dates of the control account do not cover the duration of the forecast dates of the work packages.
To resolve this error:
  • Run the Validity Check Wizard and select Adjust Control Account dates to exactly span Work Package dates on the Business Validations page.
Forecast dates for <Control Account> : <CA1\CA2\CA3> do not align with the <Work Package> forecast dates This error occurs when the Adjust Control Account dates to exactly span Work Package dates option is selected on the Business Validations page of the Validity Check Wizard and the forecast dates for the work package do not align with the forecast dates for the control account. When the Adjust Control Account dates to exactly span Work Package dates option is selected, the Validity Check Wizard will adjust the control account baseline and forecast dates to align with the work package dates.
Forecast <empty or Early or Late><empty or start or finish> date is empty for <Work Package or Control Account> <Work Package ID or Control Account ID>. This error occurs when the forecast, early, or late start or finish date of a control account or work package is blank or empty.

Example:

  • Forecast <empty><empty>date is empty for <Control Account> <CA1\CA2\CA3>
  • Forecast <empty or Early or Late> <start or finish> date is empty for <Work Package> <WP>
Forecast <Early or Late> <start or finish> date does not match Forecast <start or finish> date for <Work Package> <Work Package ID>. This error occurs in any of the following scenarios:
  • The Work Package dates correctly span resource assignment dates option is selected on the Business Validations page of the Validity Check Wizard and there are packages that have early and late start dates that differ from the actual start dates for In-Progress or Completed work packages. The early and late start dates should always match the actual start date for work packages with a status of In-Progress or Completed.
    Example:
    • Forecast <Early/Late><start> date does not match Forecast <start> date for <Work Package> <WP>
  • There are work packages that have early and late finish dates that differ from the actual finish dates for Completed work packages. The early and late finish dates should always match the actual finish date for work packages with a status of Completed.
    Example:
    • Forecast <Early/Late><finish> date does not match Forecast <finish> date for <Work Package> <WP>
Forecast <empty or Early or Late> T-phase exists prior to the status date for <Work Package> <Work Package ID>. Forecast <empty or Early or Late> start date will not be moved. This error occurs when the Work Package dates correctly span resource assignment dates option is selected on the Business Validations page of the Validity Check Wizard. This warning message informs you that forecast time-phase records exist before the work package status date.
Pending start and finish dates do not span baseline resource assignments for <Work Package> <Work Package ID>. This error occurs when the baseline dates of the work package do not cover the time-phased dates of the resource assignments.
To resolve this error:
  • Run the Validity Check Wizard and select Adjust Work Package dates to span resource assignment dates on the Business Validations page.
<Resource Assignment/Tphase> <CA1> / <CA2> / <CA3> / <WP> / <Code> has an invalid <classtype> <class>. This error occurs when there is an entry in the TPHASE table with an invalid class. For instance, Budget1 does not exist for the project, but it is used in the TPHASE table for the resource assignment listed.
To resolve this error:
  1. Verify that the class mentioned in the error exists within the classes for the project.
  2. Take one of the following actions:
    • Add the missing class to the project.
    • Remove records from the COSTELEM and/or TPHASE tables associated with the invalid class.
    • Rename the invalid class to a valid one in the COSTELEM and/or TPHASE tables.
Result <Result ID>, Resource file <Resource ID> has been defined with a different currency code setting. This error occurs when there are multiple RESULT entries with different currency code settings that exist in the resource calculation file (CALCDETL). The currency code for a RESULT should always be the same within the resource file.
For example, the following scenarios will cause an error during the validity check:
  • Resource Code: SENG, Result: HOURS has the currency code selected.
  • Resource Code: TECH, Result: HOURS has the currency code not selected.
To resolve this error:
  1. Display the Resource File Properties dialog box for the affected resource file.
  2. Click the Results tab.
  3. Locate the result entry mentioned in the error.
  4. Select or clear the Currency checkbox and click Apply.
  5. Select or clear the Currency checkbox according to the correct setting and click Apply.
The included <cost> class <class name> for the <cost> class is at the <actual or work package> level. The <cost> class only supports <actual or work package> level <cost> classes. This error occurs when there is a class in a cost set with an incorrect level at which the costs are captured.
To resolve this error:
  1. Display the Project Properties dialog box.
  2. Click the Classes tab.
  3. Click the Included <Cost> Classes tab and confirm that each of the included classes follows the level at which the costs are captured.
The project log differs from the budget detail. Run Reconcile in Project Audit to align the log with the budget detail. This error occurs when the Project Audit Log matches Project Value option is selected on the Business Validations page of the Validity Check Wizard and the distributed budget calculated from TPHASE differs from the distributed budget calculated from the detail (BASELOG).
The project log disagrees with the project header. Open Project Audit to align the header values. This error occurs when project header values do not match the total audited values.
To resolve this error:
  • Run the Project Audit Wizard to determine which specific values are affected. The wizard will update the project header values to match those in the logs.
TODATE <date value1> does not match the status date <date value2> of the project. This error occurs when the TODATE label in the calendar set18 does not match the status date of the project header.
To resolve this error:
  1. Display the Project Properties dialog box.
  2. On the General tab, click Synchronize.
Undefined Results <result names> for <CAWPID / Resource / Class>. This error occurs when the resource code listed in the error does not exist in CALCDETL.
To resolve this error:
  • Take one of the following actions:
    • Run the Validity Check Wizard and select Fix undefined results on the Resource and Code Assignment Validations page.
    • Open the resource file and click the resource associated with the project. On the Calculations tab, right-click the missing result and select Add Results. For instance, if the resource code ASTRO has a missing result of GANDA, add GANDA.