The following table provides a list of the predefined requirement statuses and the suggested next allowable requirement statuses:

Three status controls are predefined for requirement statuses:

• Include Requirement in Project Forecasts

• Visible in Requirement Searches

• Assign Resources to the Requirement

Use these status controls to restrict allowable actions or requirements based on status.

For information about defining statuses, see Defining Statuses and Status Profile Options.

Predefined Assignment Statuses and Status Controls

The following table provides a list of the predefined assignment statuses and the suggested next allowable assignment statuses:

Two status controls are predefined for requirement statuses:

• Include Assignment in Project Forecasts

• Allow Actual Transactions

Use these controls to restrict allowable actions on assignments based on status.

For information about defining statuses, see Defining Statuses and Status Profile Options.

Predefined Candidate Statuses and Status Controls

The following table provides a list of the predefined candidate statuses and the suggested next allowable candidate statuses:

One status control is predefined for requirement statuses:

• Requires Change Reason

Use this control to require the user to enter a reason for changing the status of a candidate.

For information about defining statuses, see Defining Statuses and Status Profile Options.

Predefined Assignment Approval Statuses

Assignment approval statuses are used by workflow processes. You cannot add, modify, or delete these statuses. In addition, users cannot manually change these statuses. The status is applied to an assignment based on the action being taken.

The following table provides a list of the predefined assignment approval statuses with their associated next allowable status:

For information about defining statuses, see Defining Statuses and Status Profile Options.

Assignment Schedule Statuses

Requirement and assignment statuses are also referred to as schedule statuses because they reflect the status of the schedule for particular days. The following table shows the default settings for assignment schedule statuses:

With the default settings, when a provisional assignment is approved, the status on the assignment is changed to Confirmed. If the provisional assignment is rejected, then the status of the assignment is changed to Rejected.

Assignment schedule statuses do not launch the approval workflow and you cannot enable workflow processes on these statuses. However, you can change the default workflow success and failure statuses for each provisional assignment schedule status.

The schedules and timelines reflect all Confirmed and Provisional assignments. The provisional assignment schedule status must be set to a confirmed status upon the completion of an approval process whether manual or automated through Oracle Workflow. Because all assignment schedule statuses are user-defined, you must specify the success and failure statuses for each user-defined status.

Status Profile Options

You must define the following profile options to set the status defaults for the respective objects. Each profile option is set at the site level only:

• PA: Starting Requirement Status. This profile option defines the default status of newly created requirements.

• PA: Starting Assignment Status. This profile option defines the default status of newly created assignments.

• PA: Default Filled Requirement Status. This profile option defines the status of all filled requirements.

• PA: Default Starting Candidate Status. This profile option defines the status of all newly nominated candidates.

• PA: Default Canceled Requirement Status. This profile option defines the status of canceled requirements.

• PA: Default Canceled Assignment Status. This profile option defines the status of canceled assignments.

Defining Project Statuses

Each project status must be associated with a system status. The predefined system statuses for project statuses are:

• Unapproved

• Submitted

• Approved

• Pending Close

• Closed

• Pending Purge

• Partially Purged

• Purged

You use the Status Controls region of the Statuses window to define actions that are allowed or restricted for each project status.

• Create New Transactions. New transactions include transfers, but not splits.

• Change Workflow Statuses

• Allow Workflow

• Allow Workflow Item Type and Process

• Project Status Report Notifications

• Adjust Transactions

• Generate Revenue

• Generate Invoice

• Capitalize Assets

• Include in Status Reports. Include in Project Status Inquiry and management reports that show summary project information.

• Change Project Probability. Used by Project Resource Management.

• Allow Confirmed Assignments. Used by Project Resource Management.

• Allow Provisional Assignments. Used by Project Resource Management.

• Include Project in Organization Forecasts

• Capitalized Interest. Permits calculation of capitalized interest.

• Create Burden Transactions This action is enabled for all project statuses except Purged, Partially Purged, and Pending Purge. For all other status controls, you can optionally enable or disable the Allow check box for this action.

For more information on defining statuses, setting next allowable statuses, and setting up workflow based on statuses and status changes, please see: Defining Statuses and Status Profile Options.

Defining Status Lists

Status lists capture the business process that governs a project entity's transitions from one status to another. This process is often highly organization dependent and subject to changes due business needs. Having status lists as a bridge between project entities like a control item type and user-defined statuses allows for highly customized processes.

Project users will be exposed to only the relevant user-defined statuses and status transitions. In addition, user-defined status lists are also reusable across many instances of the project entities. This eliminates redundant setup steps for the implementation team if a business process is applicable to many project entities.

For example, a simple approval process may be used in several types of change order and change request. In this case, a single status list that captures this process is sufficient.

Status list is defined for a particular status type, since user statuses are defined per status type. For each status list, a default starting status should be selected. This status should be defined as a starting status during creation.

As part of the standard user status functionality, the implementation team can select to define next allowable statuses for a given user status.

A historic log includes the details of the statuses, the person who makes the change, the timestamp, as well as an optional comment for the change.

A status can be associated with an approval workflow. In this case, the next allowable statuses for this status are restricted and defaulted to the success and failure statuses defined in the status. The workflow will be launched when the control item status is changed to this status. The workflow item key will be the same as the unique key for the status change history. When the workflow is running, user cannot set the control item to a different status. First, the workflow has to be stopped using the Abort Workflow button in the UI. When this happens, the control item status is reverted to the status immediately prior to the submission, according to the status change history. Workflow abortion is included in the status change history.

To define status lists:

1. Navigate to the Status Lists page, and click Create.

2. On the Create Status List page, enter a name, and optionally a description.

3. Select an effective from date, and optionally an effective to date.

4. In the Status table, for each system status:

   • Click on the Update icon

   • Select User Statuses. Check all applicable user statuses.

5. To save your work, click Apply. Repeat the above steps for other statuses.

   Additional Information: You do not need to select user statuses. Oracle has already established a default flow using these seven system statuses.

6. Click Apply to save your status list.