Managing Release Order Contracts

Objective

After completing this lesson, you will be able to apply techniques to effectively manage the lifecycle of a contract.

Changing a Contract Request

Changing a Contract 

  • Once a contract has been created, there may be several reasons why it may need it be changed. The requester of the contract and any users with Edit Access to the contract can see and use the Edit button at the top of the contract to request changes.
  • When the edit button is selected, the system opens a new version of the Contract Request that was used to create the contract, where changes can be made. The new version of the contract request must be submitted for approvals, and once it's been approved, a new version of the contract with the changes will be generated to replace the existing contract.
The interface displays details found at the top of a contract request, including buttons for ‘Copy’, ‘Change’, ‘Print’, and ‘Excel Export’ are visible.

Close a Contract

Prerequisites

To close a contract, it must be in one of the following statuses:

  • Draft​
  • Published​
  • Expired

Procedure

Open the contract you want to close.​

Go to the OverviewClose Contract.

Screenshot of a test interface labeled ‘C50804-V3 - Test 3’. The interface displays details of a selected request, including buttons for ‘Change’, ‘Close Contract’, ‘Print’, and ‘Excel Export’ are also visible.

The contract moves to a Closed status when one of the following events occurs:

  • The contract’s expiration date has been reached.​
  • You close the contract manually with the Close command.

For contracts without release orders that can be invoiced or received against, the contract is closed, and contract subscriptions are deactivated when it is fully invoiced or fully received. If a contract expired or is closed manually, contract subscriptions will not be deactivated until the contract is fully received or fully invoiced.

When a contract that has pending requisitions associated with it is manually closed, the submitted requisitions are automatically removed from the submitted status.​

Requisitions that are automatically withdrawn need to be manually edited and then manually resubmitted. The contract attached to these requisitions is not automatically detached. This allows the user who selected the contract to review the impact and choose another contract or make other adjustments to the purchase.​

​Automatic withdrawal does not happen in the following cases:

  • The available amount of the contract reaches zero because release orders have been applied against the available amount balance.​
  • You modify the original CR (Contract Request) and the available amount reaches zero because the contract's maximum commitment is set lower than the amount used. In this situation, the contract is automatically closed.
  • The contract was automatically selected for the requisition. In this case, the requisition remains in the submitted status, but the contract is automatically detached from it. The price is recalculated to the original customer catalog price, and the approval process is reevaluated. Similarly, if a requisition is in the composing status, the contract is automatically detached from it.
  • If a contract is reopened, the withdrawn requisitions are not automatically resubmitted.​

Open a Closed Contract​

The contract status moves to Open when one of the following events occurs:

  • The current date is between the contract’s effective and expiration dates, and the contract has a valid available amount.​
  • The contract’s effective date has been reached.
  • You open the contract manually with the Open command.

Log in to track your progress & complete quizzes