Use a Code File in Multiple Projects
Although a project typically has multiple breakdown structures associated with it, a specific code file can also be used with more than one project.
This might be the case, for example, if a number of projects were being performed by the same organization and could therefore share the same organizational code file. As a result, Cobra does not force you to define code files that are project-specific. Instead, you can define the code files independent of a particular project and indicate how the structures are to be associated with project data at the time the project is created. Many project managers have found that creating a single work breakdown structure that uses the project ID as the top level of the structure and that includes all their projects has benefits when performing multi-project operations. This strategy allows them to use the work breakdown structure as a basis for drill-down and reporting operations.
In addition to associating code files to control account keys, work package keys, or resource keys, it is possible to assign as many as nine different code files to the project at both the control account and the work package level for a total of 18 files. In this capacity, code files serve the same function as the code files.
Multi Project Considerations for Code Files
Multiple projects can share a single code file. To run reports from a master project, you need to validate the same field with the same code file. In other words, you must setup the information on the Project Properties dialog box for code files using the same fields.