Import File Validation
Cobra performs validations on the data in the file after you identify the import file to be used for entering actual costs.
The following restrictions must be followed:
- Control account, work package keys, or code values must be valid.
- Any transaction dates must be before the project status date.
- Actual costs must be posted to either open control accounts or to open work packages.
- Resources in the import file must correspond to the resources that were budgeted to the control account or work package. However, there is a project option to allow you to post unbudgeted resources.
Whenever Cobra detects an error during the validation process, a message appears on the screen, and a log of the session is stored in a text file. You can save this file for further review.
After all validations are complete, Cobra takes one of the following actions:
- If Cobra detects any errors when validating cumulative actual costs, Cobra asks you to post the corrected transactions.
- If Cobra detects any errors when validating current period actual costs, Cobra does not post any actual cost data. However, selecting the
Post valid records option on the Included Costs page of the Integration wizard allows these actual costs to be posted.
You can show the result values on the error log when loading actual costs. To show result values in the log, select the Print values of invalid records to the process log option on the Options page of the Integration wizard.
Cobra creates a transaction error file when you load actual costs for invalid transactions that Cobra is unable to load during the integration. The transaction error file, whose filename is the same as the transaction filename but with the .err extension, is generated in the \<User>\Documents\Deltek\Cobra\Logs folder. You can access the file and fix the invalid transactions, and load it directly back to Cobra.