How Project Status Components Work Together

Use project statuses to track the project as it flows through the project lifecycle. The project application administrator can define additional statuses to meet business needs using the Manage Project Statuses task.

Define additional features for a project status like workflow approvals, next allowable statuses, status controls, and progress statuses through the Manage Project Statuses task. The following project statuses are available for the execution and financial management of the project:

• Draft

• Submitted

• Active

• Rejected

• Pending Close

• Closed

The default project statuses while creating the project are:

• For financial projects, the status entered in the project template if using template for project creation.

• For nonfinancial projects, the status entered in the setup implementation options.

Note: When you enable a nonfinancial project for financial management, the application doesn't change the status of the project.

The progress status type specifies overall progress of a project, task, or resource. Progress statuses are used for reporting and don't control what you can do with a project. The following are the predefined progress statuses.

• On track

• At risk

• In trouble

Status Attributes

Each status is associated with a status type and a system status. Optionally you can specify status attributes for initial project status and workflow.

• Status Type: Types are Project or Progress.

• System Status: Predefined system statuses that the application uses for internal processing. Every status must map to a predefined system status

• Initial Project Status: Controls whether you can select the status as an initial status on a project template. Initial project status doesn't apply to progress statuses.

• Workflow Attributes: An approval workflow enables you to separate project creation from project approval. Workflow attributes don't apply to progress statuses.

  Project status approval workflow includes these attributes:

  • Status After Change Accepted: The status assigned after approving a project status change.

  • Status After Change Rejected: The status assigned after rejecting a project status change.

    The project status after rejecting the workflow can be the same as the current status.

Status Controls

Status Controls determine the actions allowed for a project in a given project status. By default, a project in an Active application status allows all actions. Status controls don't apply to progress statuses.

Status Controls control the following actions:

• Adjust transactions

• Capitalize assets

• Capitalized interest

• Create burden transactions

• Create new transactions

• Summarize project data

• Updating task progress by Project Team Members

Next Allowable Statuses

Next allowable statuses specify which statuses you can use as the new status when you manually change a system status. All is the default next allowable status, which you can change. Next allowable statuses don't apply to progress statuses.

Defining the next allowable statuses determines the project process flow. For example, you can specify that a project with a Requested status can have the status changed to either Active or Rejected. This example shows two possible process flows for the project: Requested to Active status, or Requested to Rejected status.

The following four options are available when you specify the next allowable statuses:

• All: The current status can change to any status. All is the default value.

• None: The current status can't change.

• System Status: System statuses control the next allowable statuses. Specify which system statuses are next allowable statuses.

• Status Name: Project statuses control the next allowable statuses. Specify which project statuses are next allowable statuses.