If you selected the Track Owning Organization History check box on the Configure Project Settings screen, the Org History subtask is enabled on the Manage Project User Flow.

Note that you can create a new line on the Org History subtask only when prompted by Costpoint. This occurs when the Manage Project User Flow screen is saved and Costpoint has determined that the Org History subtask must be completed. You cannot create new lines by accessing the Org History subtask from the main screen. This allows Costpoint to check the project tables and determine when the subtask must be completed.

Since the Process Organization Changes utility was designed to facilitate the transferring of revenue, billing, or Cost of Goods Sold (COGS) balances in the G/L, a record for the project must exist in the Manage Revenue Information, Manage Project Billing Information, or Manage Cost of Goods Sold screen before the Org History subtask can be completed.

If the Allow Edit check box is cleared for the Owning Org on the main screen of the Manage Project User Flow, all lower-level projects in the project tree must have the same owning organization. Changing the owning organization at a higher level, when the revenue, billing, or COGS master records exist for a lower level, prompts the completion of the Org History subtask. In this instance, a non-editable row is inserted on the Org History subtask for all lower-level projects, even if they have a master record, because they all contain the same owning organization. Modifications to the Org History subtask can occur only at the higher level. The processed columns on the Org History subtask are changed, accordingly, for all project levels as the organization change process is completed. Note that the Journal Entry Number column is populated only for the projects where the G/L contains records that were transferred.

If the Allow Edit box is cleared, this means that a lower-level project may have a different owning organization, and each project is evaluated separately. In this instance, if a revenue, billing, or COGS record does not exist for the project with an organization change, the Org History subtask need not be completed.

If all the conditions have been met and the owning organization is changed, the following message displays when the screen is saved: "Changing the Owning Org may cause journal entries to be computed. Do you wish to continue?" Clicking No causes the owning organization to revert back to the original organization, after which you can save the screen. Clicking Yes causes the Org History subtask to open and a new line to be created.