Validity Check

The Validity Check feature allows you to validate a wide range of project information.

Information that can be validated includes data anomalies, invalid reference data, code assignments and files, resource assignments and files, cost set and class definitions, apportionment mappings, project audit errors, business checks, ancillary file checks, and project and master project checks.

A validity check is not required before running processes but is recommended for you to perform before running such processes in order to correct any data errors/anomalies. A validity check is also recommended after importing data into Cobra as there are no validations that are run during the import process.

Business validations check for such things as vertical traceability (dates) and control accounts/work packages that do not have resource assignments and/or costs.

The ancillary file validations check for duplicates within the ancillary files, invalid referenced data within the code/resource files, and the calculations and results within the resource file. Invalid reference data occurs when someone inadvertently deletes the code file that has been assigned to the project. Cobra does not automatically start deleting all the code assignments in the project because the code may have been deleted in error. The validity check helps identify invalid referenced data so that you can add the code assignment back to the code or remove the code assignment from the project.

Data anomalies do not occur under normal circumstances. However, orphan records or duplicate records can exist for reasons such as network errors. These checks locate orphan and duplicate records.

Attention: It is a good practice to validate your data each month before you advance the calendar.

You can also run the Validity Check process through the API.