Control Account Fields Versus Codes

When actual costs are posted to a project, a unique identifier must be used to process the import file.

You may use either a combination of fields such as the WBS and OBS, a single field such as the work package key field, or a code on the control account or work package. Consider the following:

  • The row is uniquely identified. You cannot choose WBS, for example, and have WBS on multiple control accounts.
  • The level of the class is consistent with the fields. If the class level is work package, then a field on the work package must be in the file.

    The selections you make on the Field Mapper page the Integration wizard are validated. You may select either all control account fields or codes at the appropriate level. While you may use a combination of control account fields to uniquely identify where the actual costs will be posted, you may not use a combination of codes. For example, if you select a code on the control account, the first validation performed is to check for duplicate codes assigned to any of the control accounts. This validation procedure assures Cobra will know where the transaction is to be posted. If you do not have a unique identifier, the process stops and Cobra displays an error message.

    To determine the best business process for your organization, you must determine when charge numbers are assigned to a project and when you plan to build your Cobra project. If your organization only assigns charge numbers after a project is underway and you plan to use Cobra as your estimating tool, you will probably find using a code on the control account a good implementation. That way you can create the control accounts before you have charge numbers, and assign the charge numbers to the control accounts after the contract has been awarded.