File Selection Page of the Integration Wizard

Use this page to select your project and define the file or database connection that contains the actual cost records for importing data.

Note: When you ceate the actual cost import file for the Actual Cost Integration process in Cobra, it must be in a CSV (comma-separated values) file format.

Contents

Field	Description
Project	Use this field to define the project where the actual costs will be imported. Click to select a project or master project. Note: Only projects where you have right access are displayed.
Actual cost file	Select this option if you are importing actual cost records from a file. Click to locate the file.
Connection name	Select this option if you are importing actual cost records from a database. Click New to create a new connection using the New Connection dialog box, or click Edit to modify an existing connection using the Edit Connection dialog box. Note: Selecting this option displays the Database Table Selection page after you click Next. If you want to load actual cost records from a database table, you must first create a connection to a database that contains the actual cost records. For steps to create a database connection to load actual costs using a MS SQL database, see Create an MS SQL Database Connection to Load Actual Costs.
Actual cost file contains records at the following level	Use this field to define the level of costs contained in the actual cost file. Select one of the following options: Control Account Prompt Work Package Prompt Note: This field is enabled only when the project has actual costs defined at both levels; otherwise, the project level is selected, and the field is disabled.
Auto-create missing Control Account or Work Package	Select this option to automatically create non-existing control accounts and work packages during the Actual Cost Integration process. Attention: For more information on this option, see Actual Costs Preferences. For more information on the automatic creation of non-existing control accounts and work packages, see Automatic Creation of Control Accounts and Work Packages.
Add missing key field code data	Select this option to automatically populate missing key field code values into the appropriate code files during the Actual Cost Integration process, enabling the successful creation of control accounts and work packages. If the actual cost file contains all required key fields as defined in the project, the integration process will proceed normally. If the actual cost file is missing one or more required key fields, or if the added key fields do not conform to the code file structure, the integration process will fail. If the actual cost file includes key field values not found in the code file lookup, Cobra will: Automatically add the missing codes to the relevant code files with the description "Created during Actual Cost import." Respect any defined hierarchy. If the code file has a hierarchy, Cobra ensures the parent and all necessary levels are added. If the code file is a flat list, the missing code is added at the top level. Note: Cobra will validate the codes before adding them to the code files associated with the project's key fields. If an invalid code is found, Cobra will log an error and skip that code. Cobra will still add the valid codes and their associated parent codes to the code files. If the Check Control Account field [n] structure for parent/child uniqueness or Check Work Package structure for parent/child uniqueness option is selected for one or more key fields, Cobra will validate any new control accounts or work packages. If the validation fails, the new codes will remain in the code file, but the control account or work package will not be created. Before Cobra adds a new code to a fixed-form significant code structure, Cobra will check whether the code matches the required length. If the code does not meet the specified length, Cobra will log an error and exclude the code from the code file. For example, if the maximum length is set to 8, each code must be padded to 8 characters. Attempting to load a code such as “ABC” into a fixed-form significant structure results in the following error in the process log: [Error] Fixed Form Significant code 'ABC' is 3 characters and it needs to be 8 characters. An entry is added to the process log for each record where Cobra successfully created a missing code. Note: This option is enabled only if you select the Auto-create missing Control Account or Work Package option.
Use Cost date to define Control Account or Work Package dates	Select this option to utilize the Cost date specified in the actual cost file to define the start dates of automatically created control accounts and work packages during the Actual Cost Integration process. When this option is selected, you must define the Cost date field on the Field Mapper page. Note: This option is enabled only if you select the Auto-create missing Control Account or Work Package option.