Open Plan Schedule Integration Error and Warning Messages

Learn about the error and warning messages related to the Open Plan Schedule Integration process, as displayed in the process log, along with their resolutions.

Type	Message	Cause and Resolution
Error	Could not get list of valid schedule fields.	This error occurs when the OP_DoEnumFields() method fails to retrieve the list of valid schedule fields from the Open Plan database. To resolve this error, verify the database connection to Open Plan tables and check user permissions for accessing the field dictionary tables.
Error	The {field_constant} references invalid field ‘{field_name}’.	This error occurs when the field name specified in the configuration does not exist in the Open Plan schedule database. To resolve this error, update the field mapping configuration to reference a valid field name that exists in the Open Plan database.
Error	The {field_constant} references field ‘{field_name}’ which could not be found in the Open Plan tables.	This error occurs when the referenced field name does not exist in any of the expected Open Plan tables. To resolve this error, verify that the field exists in the Open Plan database and is accessible.
Error	Schedule code file {filename} does not exist.	This error occurs when the specified schedule code file name does not exist in the list of valid Open Plan code files. To resolve this error, select a code file that exists in the Open Plan schedule or create the code file in Open Plan before running the integration.
Error	Could not get list of OP projects.	This error occurs when the SQL query fails while Cobra attempts to retrieve the list of Open Plan projects from the WST_DIR table. To resolve this error, verify the Open Plan database connectivity and access permissions to the project directory tables.
Error	‘{project_name}’ is not a valid Open Plan project name.	This error occurs when the specified project name does not exist in the Open Plan database. To resolve this error, verify that the project name is correct and exists in Open Plan and check for case- sensitivity issues.
Error	Error creating temporary table LinkPRG.	This error occurs when the temporary tables for resource and code linking data staging cannot be created. To resolve this error, check disk space, verify temp directory permissions, and ensure table names are not already in use.
Error	SQL error getting baseline UID.	This error occurs when a SQL error occurs while Cobra attempts to retrieve the baseline unique identifier from Open Plan. To resolve this error, verify that the baseline exists and that the database connectivity is working.
Error	SQL error accessing activity records.	This error occurs when a SQL error occurs while Cobra retrieves activity data from Open Plan activity tables. To resolve this error, verify the database connectivity and activity table access and check the SQL query syntax.
Error	There are no activities that meet your link criteria.	This error occurs when no activities match the filter criteria specified for the link (all activities were filtered out). To resolve this error, review the link filter criteria to ensure they are not too restrictive and verify that activities exist in Open Plan.
Warning	Cannot load an Open Plan resource file into a Cobra code file.	This warning occurs when you attempt to load an RDS (resource) file into a code file format, which is incompatible. To resolve this warning, use the correct file format for resource imports (BDN format). This warning does not stop the process.
Warning	Activity {activity_id}: Activity marked as started but no actual start date.	This warning occurs when an activity has its completion status set to In Progress but does not have an actual start date defined. To resolve this warning, select the For schedule activities with percent complete and no actual start date, use the early date as the Cobra actual start date option on the Status page of the Integration Wizard if the schedule activities use the Percent Complete EVT. Otherwise, set the actual start date in Open Plan.
Warning	Activity {activity_id}: Activity marked as complete but no actual finish date.	This warning occurs when an activity has its completion status set to Complete but does not have an actual finish date defined. To resolve this warning, select the For schedule activities with percent complete and no actual start date, use the early date as the Cobra actual start date option on the Status page of the Integration Wizard if the schedule activities use the Percent Complete EVT. Otherwise, set the actual finish date in Open Plan.
Warning	Invalid Budget Class ‘{class}’ for {CA/WP keys}, ID {activity_id}.	This warning occurs when a resource assignment has a class value that is not valid for budget data according to the Cobra class definitions. To resolve this warning, review the class assignments in Open Plan. The resource will be skipped but the process continues.
Warning	Invalid Forecast Class ‘{class}’ for {CA/WP keys}, ID {activity_id}.	This warning occurs when a resource assignment has a class value that is not valid for forecast data according to the Cobra class definitions. To resolve this warning, review the class assignments in Open Plan. The resource will be skipped but the process continues.
Warning	There are no code assignment records found, so code assignments will not be loaded.	This warning occurs when no code assignment values are found in the schedule for the specified code fields. To resolve this warning, no action is required. The code assignments will not be imported but the process continues. Add code assignments in Open Plan if needed.