Using Schedule Dependencies and Constraints

This chapter provides overviews of schedule dependencies, activity constraints, integration of dependencies and constraints with Microsoft Project, and project schedule indicators, and discusses how to:

• Specify schedule dependencies.

• Specify activity constraints.

Understanding Schedule Dependencies

This section provides overviews of:

• Dependency types and relationships.

• Activities with multiple dependencies.

• Dependencies across projects.

• Copying projects with dependent activities.

Dependency Types and Relationships

A dependency is a logical relationship between two project activities in which the start or end date of one activity depends on the start or end date of another activity. The activity that depends on the other activity is the successor, and the activity that it depends on is the predecessor. The system calculates the successor activity's start date, end date, or duration based on the dependency relationship, dependency type, and calculation method that you establish.

You can define multiple activity successors and activity predecessors for each project activity. The system sets the start and end dates of new activities that are equal to the project start date. You can manually update the dates and duration, or use dependencies and constraints to determine the activity start and end dates.

The best practice for project activity scheduling is to set dependencies and constraints on all activities to drive the project schedule rather than manually updating every activity date. When you specify a dependency on an activity, the predecessor activity schedule might affect the successor activity schedule. If that successor activity has additional related dependencies, there can be a cascading effect on many activity dates. You can select the activity date cascade calculations option on the Project General - Program Management page to specify when to calculate activity dates and roll them up to summary activities. Delaying the summary date rollup can help you manage system performance.

This table identifies the system calculation processing based on the activity date cascade calculations options.

Define dependencies on the Activity Predecessors page where you specify predecessor projects, predecessor activities, dependency types, and lead or lag time. Dependency types that you can establish include:

• End-to-Start: The start date of the successor activity is based on the end date of the predecessor activity.

• End-to-End: The end date of the successor activity is based on the end date of the predecessor activity.

• Start-to-Start: The start date of the successor activity is based on the start date of the predecessor activity.

• Start-to-End: The end date of the successor activity is based on the start date of the predecessor activity.

Additionally, you can define a lag time or lead time for dependency relationships. Lag time is the delay between activities that have a dependency. Lead time is the overlap between activities that have a dependency.

Activity Date Calculation Methods

The system calculates activity start date, end date, and duration based on the calculation method that you specify at the activity level and the lag or lead time that you specify when you create the dependency.

You specify the calculation method in the Calculate field on the Project Activities page or the Activity Definitions - General Information page. The available options are:

• Duration: The system calculates the duration, in whole work days, of the activity based on the start date and end date using this formula: (End Date) – (Start Date) = (Duration).

• End Date: The system calculates the end date of the activity based on the start date and duration using this formula: (Start Date) + (Duration) = (End Date).

• Start Date: The system calculates the start date of the activity based on the duration and end date using this formula: (End Date) – (Duration) = (Start Date).

Specify lead or lag time, in whole work days, in the Lag field on the Activity Predecessors page.

Lag time is the delay between activities that have a dependency. For example, if you need a two-day delay between the end of one activity and the start of another, you can establish an end-to-start dependency and specify a lag time of two days. Lag time is expressed with a positive whole number in the Lag column of the Activity Predecessors page.

Lead time is the overlap between activities that have a dependency. For example, if an activity can start when its predecessor is two weeks from its end date, you can establish and end-to-start dependency with a lead time of ten days for the successor activity. Lead time is expressed with a negative whole number in the Lag column of the Activity Predecessors page.

End-to-Start Dependencies

For an end-to-start dependency, the system sets the start date of the successor activity to the next working day after the predecessor's end date plus or minus any lag or lead time. When the calculation method is:

• End Date: The system sets the successor's end date to its new start date plus the duration, plus or minus any lag or lead time.

• Duration: The end date remains as it was and the system sets the duration to the number of working days from the new start date to the existing end date, plus or minus and lag or lead time.

Note. You cannot set an end-to-start dependency on an activity that has the start date calculation method.

This table shows activities, durations, start dates, and end dates before you establish the end-to-start dependency:

This table shows the effect on the successor activity start and end dates based on the end-to-start dependency with an end date calculation method:

Note. For the examples in this chapter, the duration, start date, and end date are based on the work days in a business calendar with Monday-Friday work weeks.

End-to-End Dependencies

For an end-to-end dependency, the system sets the successor activity's end date to the predecessor activity's end date plus or minus any lag or lead time. When the calculation method is:

• Start Date: The system sets the successor's start date to its end date minus the duration, plus or minus any lag or lead time.

• Duration: The start date remains as it was and the system sets the duration to the number of working days from the new end date to the existing start date, plus or minus and lag or lead time.

Note. You cannot set an end-to-end dependency on an activity that has the end date calculation method.

This table shows activities, durations, start dates, and end dates before you establish the end-to-end dependency:

This table shows the effect on the successor activity start and end dates based on the end-to-end dependency and start date calculation method:

Start-to-Start Dependencies

For a start-to-start dependency, the system sets the successor activity's start date to the predecessor activity's start date plus or minus any lag or lead time. When the calculation method is:

• End Date: The system sets the successor's end date to its start date plus the duration, plus or minus any lag or lead time.

• Duration: The end date remains as it was and the system sets the duration to the number of working days from the new start date to the existing end date, plus or minus and lag or lead time.

Note. You cannot set a start-to-start dependency on an activity that has the start date calculation method.

This table shows activities, durations, start dates, and end dates before you establish the start-to-start dependency:

This table shows the effect on the successor activity start and end dates based on the start-to-start dependency and an end date calculation method:

Start-to-End Dependencies

For a start-to-end dependency, the system sets the successor activity's end date to the predecessor activity's start date plus or minus any lag or lead time. When the calculation method is:

• Start Date: The system sets the successor's start date to its end date minus the duration, plus or minus any lag or lead time.

• Duration: The start date remains as it was and the system sets the duration to the number of working days from the new end date to the existing start date, plus or minus and lag or lead time.

Note. You cannot set a start-to-end dependency on an activity that has the end date calculation method.

This table shows activities, durations, start dates, and end dates before you establish the start-to-end dependency:

This table shows the effect on the successor activity start and end dates based on the start-to-end dependency and Start Date calculation method:

Activities with Multiple Dependencies

You can set one or more dependencies on a successor activity. Each of these dependencies can consist of different types, such as an end-to-end dependency with a predecessor activity along with an end-to-start dependency with another predecessor activity. Each dependency can yield different effects on the successor's start and end dates. The system sets the successor dates and duration based on the predecessor activity that drives the successor dates to the latest date.

Example One of a Successor Activity with Multiple Dependencies

This table shows activities, durations, start dates, and end dates before you establish dependencies:

This table shows the effect on the successor activity start and end dates based on the dependency relationships and types and an end date calculation method:

The Functional Design and Usability Design activities are both predecessors to the Develop activity, However, the system uses the Functional Design activity end date to determine the Develop activity start and end dates. The next working day after the Functional Design activity end date drives the Develop activity dates to be later than if it was driven by the Usability Design activity start date.

Example Two of a Successor Activity with Multiple Dependencies

This table shows activities, durations, start dates, and end dates before you establish dependencies:

This table shows the effect on the successor activity start and end dates based on the dependency types and relationships and an end date calculation method:

The system uses the Develop activity to determine the Unit Test activity's dates. The end date for the Develop activity drives the Unit Test activity dates to be later than the Functional Design activity end date and the Usability Design activity start date.

Dependencies Across Projects

Use the Activity Predecessors page to define a dependency between a successor activity on one project and a predecessor activity on a different project. You can define dependencies across projects as long as the projects are within the same business unit.

The system uses the scheduling calculation method that is specified at the project level of the successor activity if the successor’s dates must change to align with the new dependency relationship. The system allows multiple levels of cross-project dependencies.

The system automatically triggers Change Request workflow for cross-project dependencies. If you change the dates for a predecessor activity that affect the dates for the successor activity, the system automatically sends a change request to the project manager of the project with the successor activity. If the project manager approves the change request, the system uses date processing rules for dependencies to update the successor activity dates or remove the dependency if there is a conflict. If the project manager rejects the change request, the system leaves the successor activity dates as they were and removes the dependency between the two projects’ activities.

See Also

Change Requests for Cross-Project Dependencies

Copying Projects with Dependent Activities

On project templates, you can set up dependencies within a single project. The system calculates the correct activity start dates and end dates for the new project based on the dependency. If you create projects from copies of existing projects, the system copies dependencies within that project to the target project.

Understanding Activity Constraints

This section provides overviews of activity constraints and copying activities with constraints.

Activity Constraints

A constraint is a restriction that you place on an activity to control the activity's start date or end date. You can define flexible, moderately flexible, or inflexible constraints.

• Flexible constraints work with dependencies to make an activity occur as soon or as late as the dependency will allow.

  For example, the system schedules an activity with an As Soon As Possible constraint and an end-to-start dependency as soon as the predecessor activity ends.

  Flexible constraints are:

  • As Soon As Possible

  • As Late As Possible

• Moderately flexible constraints work with dependencies to force activities to occur before or after dates that you specify.

  For example, you can establish an end-to-start dependency that assigns the start date of September 13 on an activity with a Start No Later Than constraint for September 14.

  Moderately flexible constraints are:

  • End No Earlier Than

  • Start No Earlier Than

  • Start No Later Than

  • End No Later Than

• Inflexible constraints force the activity dates to follow the constraint.

  For example, an activity with a Must End On constraint for July 10 and an end-to-start dependency on another activity will always have an end date of July 10 no matter when the predecessor activity's date ends.

  Inflexible constraints are:

  • Must Start On

  • Must End On

Each activity can have only one constraint type, which determines when the activity can start or end. For summary activities, you can select only As Soon As Possible, End No Later Than, or Start No Earlier Than constraint types.

If users try to change detail activities to summary activities, and the detail activities have constraints that are not valid for summary activities, the user must either remove the constraint or leave the activity as a detail activity.

If no constraint type is specified for an activity, users can enter any start and end dates, as long as the dates do no violate any existing dependencies for the activity, and the activity is a detail activity.

On the Project General - Program Management page, you can select a project-level option that requires that activities always honor the constraint. If you select this option:

• Users cannot manually schedule a start date or end date that falls outside of an activity’s constraint.

• If a schedule change to a predecessor activity causes a successor activity's dates to violate its constraint, the user must either resolve the scheduling conflict or remove the dependency.

• If a new predecessor activity causes the successor activity to violate its constraint, the start and end dates for the successor activity will still honor the constraint date.

If you do not require activities to honor the constraint, users can change activity start and end dates manually or through dependency relationships. The constraint remains on the activity but the system allows the activity dates to change even if they violate the constraint.

As Soon As Possible Constraint

Use the As Soon As Possible constraint for the system to schedule the activity as early as it can, based on these rules:

• The system assigns the start date of the activity to the start date of the project.

• If the activity is a summary activity, the start date is based on the earliest start date of its children.

• If you establish dependencies on the activity, the system assigns the activity start and end dates based on the dependency.

• If you remove dependencies from the activity, the system assigns the activity date as the start date of the project.

• If you delete this constraint, the system does not change the activity start and end dates.

  You can manually modify the activity dates.

• If you manually modify the activity start date or end date, the system removes this constraint.

• If you change the activity duration, the system recalculates the end date but does not change the constraint.

Note. You cannot enter an As Soon As Possible constraint if the calculation method is Start Date.

As Late As Possible Constraint

Use the As Late As Possible constraint for the system to schedule the activity as late as it can, based on these rules:

• The system assigns the end date of the activity to the end date of the project.

• If you establish dependencies on the activity and you enable the option for activities to always honor constraint dates, the system assigns the activity end date as the end date of the project.

  However, if you disable the option for activities to always honor constraint dates, the system assigns the end date based on the dependencies.

• If you remove dependencies from the activity, the system assigns the activity end date as the end date of the project.

• If you delete this constraint, the system assigns the activity start date based on the project start date.

• If you manually modify the activity end date, the system removes this constraint.

• If you change the activity duration, the system recalculates the start date but does not change the constraint.

Note. You cannot enter an As Late As Possible constraint if the calculation method is End Date.

End No Earlier Than

Use the End No Earlier Than constraint to establish the earliest possible date that an activity could end. The activity cannot finish any time before the date you specify. The system determines the schedule based on these rules:

• If you assign a constraint date that is the same as or occurs before the activity end date, the system does not change the activity end date.

• If you modify an activity so that the end date falls after the constraint date, the system does not change the constraint date.

• When you enable the option for activities to always honor constraint dates:

  • If you set a constraint date to fall after the activity end date, the system updates the activity end date to the constraint date.

  • If you modify an activity end date to a date that is earlier than the constraint date, you violate the constraint and receive an error message that allows you to remove the constraint or preserve the constraint and not change the activity end date.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity end date to occur before the constraint date, the system ignores the dependency and does not change the successor or predecessor dates.

• When you disable the option for activities to always honor constraint dates:

  • If you assign a constraint date to fall after the activity end date, the system updates the activity end date to the constraint date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the end date, the system uses the dependency to drive the activity schedule and assigns the end date based on the dependency.

  • If you modify an activity end date to a date earlier than the constraint date, you violate the constraint and receive an error message that allows you to remove the constraint or preserve the constraint and not change the activity end date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the end date, the system uses the dependency to drive the activity schedule and assigns the end date based on the dependency.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity end date to occur before the constraint date, the system uses the dependency to drive the activity schedule and assigns the end date based on the dependency.

• If you remove all dependencies from an activity, the system tries to enforce the constraint and assigns the activity end date as the constraint date. However, if the existing dates on the activity conflict with the constraint, which could happen if the option for activities to always honor constraint dates is disabled, the system gives you the option to remove the dependency or remove the constraint.

• If you delete this constraint and have no dependencies on the activity, the system assigns the activity start date based on the project start date.

Start No Earlier Than

Use the Start No Earlier Than constraint to establish the earliest possible date that an activity can begin. The activity cannot start any time before the date you specify. The system determines the schedule based on these rules:

• If you assign the constraint date that is the same as or occurs before the activity start date, the system does not change the activity start date.

• If you modify an activity so that the start date falls after the constraint date, the system does not change the constraint date.

• When you enable the option for activities to always honor constraint dates:

  • If you set a constraint date to fall after the activity start date, the system updates the activity start date to the constraint date.

  • If you modify an activity start date to a date that is earlier than the constraint date, you violate the constraint and receive an error giving you the option to remove the constraint or preserve the constraint and not change the activity start date.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity start date to occur before the constraint date, the system ignores the dependency and does not change the successor or predecessor dates.

• When you disable the option for activities to always honor constraint dates:

  • If you assign a constraint date to fall after the activity start date, the system updates the activity start date to the constraint date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the start date, the system uses the dependency to drive the activity schedule and assigns the start date based on the dependency.

  • If you modify an activity start date to a date earlier than the constraint date, you violate the constraint and receive an error message that allows you to remove the constraint or preserve the constraint and not change the activity end date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the start date, the system uses the dependency to drive the activity schedule and assigns the start date based on the dependency.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity start date to occur before the constraint date, the system uses the dependency to drive the activity schedule and assigns the start date based on the dependency.

• If you remove all dependencies from an activity, the system tries to enforce the constraint and assigns the activity start date as the constraint date. However, if the existing dates on the activity conflict with the constraint, which could happen if the option for activities to always honor constraint dates is disabled, the system gives you the option to remove the dependency or remove the constraint.

• If you delete this constraint and have no dependencies on the activity, the system assigns the activity start date based on the project start date.

Start No Later Than

Use the Start No Later Than constraint to establish the latest possible date that an activity could start. The activity can start anytime on or before the date that you specify. The system determines the schedule based on these rules:

• If you assign a constraint date that is the same as or falls after the activity start date, the system does not change the activity start date.

• If you modify an activity so that the start date occurs before the constraint date, the system does not change the constraint date.

• When you enable the option for activities to always honor constraint dates:

  • If you set a constraint date to occur before the activity start date, the system updates the activity start date to the constraint date.

  • If you modify an activity start date to a date that is later than the constraint date, you violate the constraint and receive an error message that allows you to remove the constraint or preserve the constraint and not change the activity start date.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity start date to occur after the constraint date, the system ignores the dependency and does not change the successor or predecessor dates.

• When you disable the option for activities to always honor constraint dates:

  • If you assign a constraint date to occur before the activity start date, the system updates the activity start date to the constraint date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the start date, the system uses the dependency to drive the activity schedule and assigns the start date based on the dependency.

  • If you modify an activity start date to a occur later than the constraint date, you violate the constraint and receive an error message that allows you to remove the constraint or preserve the constraint and not change the activity end date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the start date, the system uses the dependency to drive the activity schedule and assigns the start date based on the dependency.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity start date to occur after the constraint date, the system uses the dependency to drive the activity schedule and assigns the start date based on the dependency.

• If you remove all dependencies from an activity, the system tries to enforce the constraint and assigns the activity start date as the constraint date. However, if the existing dates on the activity conflict with the constraint, which could happen if the option for activities to always honor constraint dates is disabled, the system gives you the option to remove the dependency or remove the constraint.

• If you delete this constraint and have no dependencies on the activity, the system assigns the activity start date based on the project start date.

End No Later Than

Use the End No Later Than constraint to establish the earliest possible date that an activity could end. The activity can end on or before the date you specify. The system determines the schedule based on these rules:

• If you assign the constraint date that is the same as or occurs after the activity end date, the system does not change the activity end date.

• If you modify an activity so that the end date occurs before the constraint date, the system does not change the constraint date.

• When you enable the option for activities to always honor constraint dates:

  • If you set a constraint date to occur before the activity end date, the system updates the activity end date to the constraint date.

  • If you modify an activity end date to later date than the constraint date, you violate the constraint and receive an error giving you the option to remove the constraint or preserve the constraint and not change the activity end date.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity end date to occur after the constraint date, the system ignores the dependency and does not change the successor or predecessor dates.

• When you disable the option for activities to always honor constraint dates:

  • If you assign a constraint date to occur before the activity end date, the system updates the activity end date to the constraint date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the end date, the system uses the dependency to drive the activity schedule and assigns the end date based on the dependency.

  • If you modify an activity end date to a later date than the constraint date, you violate the constraint and receive an error message that allows you to remove the constraint or preserve the constraint and not change the activity end date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the end date, the system uses the dependency to drive the activity schedule and assigns the end date based on the dependency.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity end date to occur after the constraint date, the system uses the dependency to drive the activity schedule and assigns the end date based on the dependency.

• If you remove all dependencies from an activity, the system tries to enforce the constraint and assigns the activity end date as the constraint date. However, if the existing dates on the activity conflict with the constraint, which could happen if the option for activities to always honor constraint dates is disabled, the system gives you the option to remove the dependency or remove the constraint.

• If you delete this constraint and have no dependencies on the activity, the system assigns the activity start date based on the project start date.

Must Start On

Use the Must Start On constraint to specify the exact date when an activity must start. The system determines the schedule based on these rules:

• The system assigns the start date of the activity to equal the constraint date.

• When you enable the option for activities to always honor constraint dates:

  • If you modify the constraint date, the system updates the activity start date to the constraint date.

  • If you modify an activity start date to a different date than the constraint date, you violate the constraint and receive an error giving you the option to remove the constraint or preserve the constraint and not change the activity start date.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity start date and the constraint date to differ, the system does not change the activity start date. The system allows you to set the dependency, but it does not enforce the dependency.

• When you disable the option for activities to always honor constraint dates:

  • If you modify the constraint date, the system updates the activity start date to match the constraint date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the start date, the system uses the dependency to drive the activity schedule and assigns the start date based on the dependency.

  • If you modify an activity start date to a different date than the constraint date, you violate the constraint and receive an error message that allows you to remove the constraint or preserve the constraint and not change the activity end date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the start date, the system uses the dependency to drive the activity schedule and assigns the end start based on the dependency.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity start date to differ from the constraint date, the system uses the dependency to drive the activity schedule and updates the successor activity's start date based on the dependency.

• If you remove all dependencies from an activity, the system tries to enforce the constraint and assigns the activity start date as the constraint date. However, if the existing dates on the activity conflict with the constraint, which could happen if the option for activities to always honor constraint dates is disabled, the system gives you the option to remove the dependency or remove the constraint.

   

• If you delete this constraint and have no dependencies on the activity, the system assigns the activity start date based on the project start date.

Must End On

Use the Must End On constraint to specify the exact date for which the activity must be completed. The system determines the schedule based on these rules:

• The system assigns the end date of the activity equal to the constraint date.

• When you enable the option for activities to always honor constraint dates:

  • If you modify the constraint date, the system updates the activity end date to the constraint date.

  • If you modify an activity end date to a different date than the constraint date, you violate the constraint and receive an error message that allows you to remove the constraint or preserve the constraint and not change the activity end date.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity end date to differ from the constraint date, the system does not change the activity end date. The system allows you to define the dependency, but if does not enforce the dependency.

• When you disable the option for activities to always honor constraint dates:

  • If you modify the constraint date, the system updates the activity end date to the constraint date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the end date, the system uses the dependency to drive the activity schedule and assigns the end date based on the dependency.

  • If you modify an activity end date to a date different than the constraint date, you violate the constraint and receive an error message that allows you to remove the constraint or preserve the constraint and not change the activity end date, unless the activity has dependencies that affect the activity schedule.

    If the activity has dependencies that affect the end date, the system uses the dependency to drive the activity schedule and assigns the end date based on the dependency.

  • If you establish a dependency on an activity and the dependency relationship is such that it would cause the successor activity end date to differ from the constraint date, the system uses the dependency to drive the activity schedule and updates the successor activity's end date based on the dependency.

• If you remove all dependencies from an activity, the system tries to enforce the constraint and assigns the activity end date as the constraint date. However, if the existing dates on the activity conflict with the constraint, which could happen if the option for activities to always honor constraint dates is disabled, the system gives you the option to remove the dependency or remove the constraint.

• If you delete this constraint and have no dependencies on the activity, the system assigns the activity start date based on the project start date.

Copying Activities with Constraints

If you create a project activity from a copy of an existing activity, the system copies the constraint on that activity to the target activity. However, if you create a project activity from a template, the constraint on that activity does not copy to the target activity.

See Also

Creating and Maintaining Projects

Understanding Integration of Dependencies and Constraints with Microsoft Project

Microsoft Project 2002 has dependencies and constraints that are similar to PeopleSoft Program Management's dependencies and constraints. All dependencies and constraints that you establish in Microsoft Project will transfer to PeopleSoft, and vice versa. It is possible for an activity schedule that you imported from Microsoft Project to differ in PeopleSoft and vice versa, because of differences in activity schedule calculations between PeopleSoft and Microsoft Project. You should maintain your smaller projects (less than one hundred activities) in PeopleSoft. However, for larger projects, you should use Microsoft Project as the master for the activity schedule. The system handles the integration process differently based on the source and target applications.

PeopleSoft to Microsoft Project Integration

The system uses these rules to assign constraints during the integration from PeopleSoft to Microsoft Project, because Microsoft Project requires a constraint on every activity, but PeopleSoft does not:

• If an activity does not have a constraint that is set in PeopleSoft and that activity has dependencies on other activities, the integration process sets an As Soon As Possible constraint on that activity in Microsoft Project and allows Microsoft Project to determine the activity’s schedule based on the dependencies.

• If an activity does not have a constraint set and there are no dependencies, the system compares the activity start date with the project start date.

  • If the activity and project dates are the same, the integration process assigns an As Soon As Possible constraint on the activity.

  • If the activity date is later than the project start date, the integration processes assigns a Start No Earlier Than constraint and a constraint date that is equal to the activity start date.

This diagram shows the logic that the system uses to export dependency and constraint information from PeopleSoft to Microsoft:

Exporting PeopleSoft activity dependency and constraint data to Microsoft

The integration process uses PeopleSoft's project-level date calculation method to determine the calculation method in Microsoft Project. This table displays the mapping between the PeopleSoft and Microsoft Project calculation method mapping to the Microsoft Project calculation method:

Microsoft Project to PeopleSoft Integration

When you import projects from Microsoft Project to PeopleSoft, the integration process sets the activity date cascade calculation option to Manual . The system imports the activity schedule into PeopleSoft exactly as it was in Microsoft Project. The system does not recalculate the schedule in PeopleSoft. You can change the Activity Date Cascade Calculation option on the Project General - Program Management page after you import the project. However, if you change the activity date cascade calculation option, it is possible for an activity schedule that you imported from Microsoft Project to differ in PeopleSoft, because of differences in activity schedule calculations between PeopleSoft and Microsoft Project.

Additionally, the systems assigns the value in the Calculate field based on the project's default value in PeopleSoft for all activities without dependencies. The system assigns the duration calculation method for all activities with dependencies.

Since summary activities in PeopleSoft cannot have dependencies on other activities, if there are any summary activities with dependencies in Microsoft Project, the import process does not bring the dependencies into PeopleSoft. The system issues a warning to indicate that the dependencies on summary activities will not be imported into PeopleSoft. The schedule dates that Microsoft Project assigned as a result of dependencies that were set on summary tasks will not change during the import. You can view the details of this process on the Integration Session Log that you can view on the Create Project from Microsoft page.

See Also

Integrating with Microsoft Project 2002

Understanding Project Schedule Indicators

During project planning and execution, project managers need to be alerted to various conditions that are associated with each activity. A column on the Project Activities page shows warning and informational visual indicators to alert project managers to attributes about each activity.

The Project Activities page displays a warning visual indicator if:

• An activity is scheduled for completion later than its deadline date.

• An activity has not been scheduled within its constraints.

The Project Activities page displays an informational visual indicator if:

• An activity has an inflexible constraint, such as Must End On, Must Start On, End No Later Than, or Start No Later Than.

• An activity has a flexible constraint, such as End No Earlier Than, Start No Earlier Than, As Soon As Possible, or As Late As Possible.

You can move the mouse across the indicator to view alternate text about the nature of these conditions. If more than one condition exists, click the indicator to access the Activity Alerts page to view the alert messages.

See Also

Creating and Maintaining Activities

Specifying Schedule Dependencies

This section discusses how to specify activity predecessors.

Page Used to Specify Schedule Dependencies

Specify Activity Predecessors

Access the Activity Predecessors page.

The project, activity, and descriptions come from the successor activity for which you are defining this dependency.

Specifying Activity Constraints

This section discusses how to specify activity constraints.

Page Used to Specify Activity Constraints

Specifying Activity Constraints

Access the Activity Definitions - General Information page.

The Activity Definitions - General Information page is documented in the PeopleSoft Project Costing PeopleBook. The fields documented here are specific to constraints.

See Also

Entering Activity General Information