3305 Main Street Ste 019 Vancouver, WA 98663

Skipped Projects – The budget code structure for this project does not match the template project

Background

This article addresses the following message that may be listed on the Determine Modifications recap report when running Integrator:

Skipped Projects
    Project "######"
        The budget code structure for this project does not match the template project (######). This project was skipped

Prolog allows for the budget code structure of each project to be defined independently however all projects that are registered to be integrated under the same Integrator connection must have the same budget code structure.  This is because the field mappings are defined within the Integrator connection settings.  Note that if you have projects that must use a different budget code structure, they can be integrated by creating another connection (identifying the same databases) and defining the field mappings accordingly.  The above message is shown when the budget code structure of a project being integrated is different than what is expected by Integrator.

Resolution

The following list summarizes the steps you can take to understand why the project is being skipped and how to resolve it:

  1. Identify your Model Project
  2. Confirm that your Model Project is correct
  3. View and document your Model Project's budget code structure
  4. Compare the budget code structure for the skipped project
  5. Correct the budget code structure
1. Identify your Model Project

The Model Project (also known as the Template Project) is a project in your Prolog database that Integrator will compare all other projects to relative to their budget code structure.  This project is identified in the upper left section of the Integrator report by the label "Template Project" or "Model Project" (depending on version).  You can dictate which project number is used for this purpose in the General Settings window by entering the desired project number in the Model Project box.  This setting should not be changed often and it is the recommendation of Event 1 Software that you create a special project (not to be used as an actual project) for this purpose, identify it in the General Settings window, and then never change it.  If no value was entered in the Model Project field in the General Settings window, Integrator will use the first project found in the Prolog database as the Model Project.

2. Confirm that your Model Project is correct

As noted above, the Model Project generally should not be changed however as noted above, if the Model Project box in the General Settings window has not been filled in, Integrator will use the first project found in the Prolog database.  If this is what is occurring and you have archived and removed projects from your Prolog database, then the first project may have changed.  This would lead to the Model Project changing automatically.  You should confirm that the Model Project identified on the report contains the desired budget code structure and if it does not, enter the project number of the correct Model Project in the General Settings window.

3. View and document your Model Project's budget code structure

To view the budget code structure of the Model Project, open Prolog and then open the Model Project.  Click Admin and then Budget Code Structure Setup.  The window that is displayed will show a grid containing six rows (one for each possible budget code segment).  The columns represent the individual settings for each budget code segment.  The combination of these settings constitutes your budget code structure.  You should make note of these details because when working with these details for the skipped project, you must make them match exactly in order to resolve the problem.

4. Compare the budget code structure for the skipped project

Close the Model Project and open the skipped project.  Click Admin and then Budget Code Structure Setup.  The budget code structure for the skipped project will be displayed.  A comparison of the Model Project's budget code structure to the one shown for the skipped project should reveal differences.  Note that the message on the Integrator report will indicate which row (Budget Group 1 - 6) contains the difference and which Property (column) the differences appear in.  Also be aware that some differences are not visually apparent.  For example, a space in the Separator Character column may exist in one but not the other however the space character is not visible.  To check for this, double-click inside the cell of the Budget Code Structure Setup window to enter edit mode in that cell.  Then right-click and click Select All.  All text (including any spaces) will be selected (highlighted).  If the cell is completely empty, the Select All option will not be enabled.

An example of how Integrator reports the budget code structure differences is shown here:

Budget Group 2

Property This Project Model Project
Show In Code False  True 
Budget Group 5
Property This Project Model Project
Order In Code
Budget Group 6
Property This Project Model Project
Order In Code
5. Correct the budget code structure

If your company uses a Prolog project template to create new projects, it is possible that the skipped project was simply setup incorrectly by not using the project template.  If this was the case and no data (that you wish to keep) has been recorded under the project yet, you can simply delete the project and recreate it using the correct project template.  If you need to keep the existing project, you can make changes to the properties shown in the Budget Code Structure Setup window provided that no Budget records have been created yet.  If Budget records have been create, you may be able to delete them if no data will be lost by doing so, otherwise you may need to utilize the Prolog Budget Group Update Utility feature (found under the Tools / Database Utilities menu) to make certain changes or call upon your Prolog support representative for assistance.  Again, the objective is to change the values shown in the Budget Code Structure Setup window of the skipped project such that they exactly match the values shown for the Model Project.