Projects Tab
Use this tab to establish general settings for your Costpoint projects.
Contents
Field | Description |
---|---|
Require Incurred Cost Submission Code for all Projects | This checkbox is cleared by default, which assumes that you have no government contracts, and that an Incurred Cost Submission Report is not required. In this case, the ICS codes on the Manage Government Contract Information screen are not required for any project. If you select this checkbox, an ICS code is
required for every project, regardless of type. These codes represent the categories specified on the Incurred Cost Submission Reports. Some examples of incurred cost submission codes are:
This checkbox is for use by companies that contract with the federal government. |
Track Owning Organization History | Select this checkbox to track modifications to the owning organization by project. You must select this checkbox to enable the Org History subtask of the Manage Project User Flow screen. This checkbox is selected by default. |
Validate Project Charging by Organizations | Select this checkbox to control which validation method is available on the Basic Info tab of the Manage Project User Flow screen. This checkbox is selected by default. If you leave this checkbox selected, the
Limit Which Orgs Can Charge Specific Accts checkbox is available on the Basic Info tab of the Manage Project User Flow screen. If you do not select this checkbox, only the
Limit Accounts to P/O/A checkbox is available. These options represent two ways of using the PROJ_ORG_ACCT table for transaction validation. Selecting this checkbox does not automatically activate a validation method, but allows you to make the selection on the Basic Info tab.
The Limit Which Orgs Can Charge Specific Accts option is considered the detail method of transaction validation in the PROJ_ORG_ACCT table. When you use this method, the project, account, and org must be in the PROJ_ORG_ACCT table for the transaction to pass validation. This is the most restrictive method of project transaction validation. This setting applies to all transaction entry screens. The Limit Accounts to P/O/A option is considered the summary method of transaction validation in the PROJ_ORG_ACCT table. When you use this method, the account and project must be in the PROJ_ORG_ACCT table, but you can use any org. This less restrictive method allows easier initialization and maintenance. This option applies to all transaction screens. Several other options for transaction validation are available on the Basic Info tab of the Manage Project User Flow screen. The following is a brief summary of those options. For more information on these options, see the screen documentation for the Basic Info tab.
|
Use Goal Multipliers for Billable Value Calculations | Select this checkbox to calculate and report the billable value of your projects. If you select this checkbox, the
Labor and
Non-Labor fields in the
Goal Multiplier group box on the Manage Revenue Information screen are required for all projects. (These goal multipliers are used by the Compute Billing Value of Cost Incurred process.) Billable value reporting is available for any project type and any revenue formula. This checkbox is cleared by default, which assumes that billable value is not calculated.
|
Show Period of Performance Warning Message | Select this checkbox to enable period of performance validation. Enter period of performance data on the Manage Modifications screen. The period of performance validation produces a soft warning every time a transaction is entered that falls outside of the project's period of performance. Because this warning is invoked at the line level, it can greatly reduce the speed of data entry. If you are not concerned with period of performance validation, leave this checkbox cleared. |
Modifications Effective Date | Use this drop-down list to select whether to have the system date default into the project modification effective dates or leave the effective date blank to require users to enter it. Valid options are:
The selection you make in this drop-down list determines the setting of the Effective Date field on the following screens:
Note: If
Default System Date is selected on the Configure Project Settings screen, check that the date that defaults is applicable to new project modifications to avoid revenue ceilings being released incorrectly.
If User Must Enter Date is selected, the Effective Date field on these screens becomes required. Make sure to enter a value in Effective Date before saving the record to avoid an error. The Import Project Master Data application also considers the option you select in this drop-down list, and follows this logic:
|
Validate Modification Descriptions | Select this checkbox to enforce validation of project modification descriptions.
Project modification descriptions are set up on the Manage Modification Descriptions screen. You can define modification descriptions on this screen whether or not the Validate Modification Descriptions checkbox is selected. Once you select this checkbox, however, you must set up modification descriptions on the Manage Modification Descriptions screen, and only those descriptions can be used for new modifications or as replacement descriptions for existing modifications. You will also not be able to delete descriptions that have already been used on a modification if this checkbox is selected. |
Period of Performance Start and End Dates
Use this group box to select the method for updating the period of performance (POP) start and end dates.
Field | Description |
---|---|
Update POP Start Date based on earliest Start Date From | Select the POP update method for the start date. Valid options are:
The default is All Modifications. |
Update POP End Date based on latest End Date From | Select the POP update method for the end date. Valid options are:
The default is Only mods with latest effective dates. |
Quick Project Defaults
Use this optional group box to create defaults for the Manage Project Master Data from Templates process.
Field | Description |
---|---|
Owning Organization | Enter, or click to select, a default owning organization for use during the Manage Project Master Data from Templates process. This default is used only for templates. |
Account Group | Enter, or click to select, a default account group for use during the Manage Project Master Data from Templates process. This default is used only for templates. |
Use Quick Project Templates | If you select this checkbox, you must enter a template ID when initiating a project in the Manage Project Master Data from Templates process. Project templates determine which fields are required, whether a default value or method is being used, and which role is responsible for completing a particular field. |