What is the difference between Closed and Expired Contract Workspace statuses?

A Contract Workspace can be in a Closed status due to either of following

• manually closed by a user
• closed by Buyer side scheduled task

A sourcing side scheduled task picks up Contract Workspaces past their expiration date and sets them to Expired status.

When a contract workspace is Closed:

• Users cannot modify or add project attributes, documents, or tasks.
• Users do not receive notification emails for overdue tasks or for tasks that are approaching their due date.
• Users do not receive expiration or contract notice email notifications.
• Users receive emails from notification tasks only if the Inteligent Configuration Manager (ICM) parameter Enable email notifications for closed Contract Workspace (Application.ACM.EnableNotificationForClosedContractWorkspace) is enabled.

When a contract workspace is Expired:

• Recurring phases stop.
• All tasks other than notification tasks stop.
• Ariba Spend Management stops sending email messages for the project other than messages for notification tasks.
• You cannot modify the contract project or files in the project unless you amend the workspace.

If you close a contract workspace, but want to work on it later, you can amend the project.

For contract workspaces that are configured for auto renewal and have one or more renewals remaining, the expiration date is the date when the contract will be automatically renewed. The expiration date will be updated for each renewal.

Notifications are not sent when the contract status is Closed or at the time of expiration (Expired).

Notifications are sent if a notification task is still active. Notifications can be issued after a contract workspace is Published, Closed, or Expired. However, if a contract workspace is Published, users can complete and create notification tasks without amending the contract workspace.

Strategic Contracts