Managing No Release Order Contracts

Objective

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

Edit a Contract Request

Edit Access 

When you create a contact, you are automatically given edit access (permission to edit the contract). You can also specify which other users you want to be able to edit the contract.

A screenshot of an Access Control settings. The interface includes a checked box labeled “Restrict Release Access” with options to filter users by Name, Group, Supervisor, and Cost Center. Each option has a dropdown menu next to it with the default setting “(select a value)”. There is also an unchecked box for “Payment Terms” and another unchecked box for “Appendices,” both located on the left side of the interface under the main heading. The overall layout is clean with a minimalist design, using shades of blue and gray

If you need to edit a contract, you must edit from level of contract request.

The screenshot shows a test interface labeled “CR58084 - Test 3.” Below the label, there’s a description: “These are the details of the request you selected. Depending on its status, you can edit, change, copy, cancel, or submit the request for approval.” Buttons for actions like “Copy,” “Change,” “Print,” and “Excel Export” are also visible.

During changing contract request, status of document will be composing. Immediately, the number of contract request change by adding number of version. Number of version depends how many times you going to "change" document.

A contract number CR58084-V2

During editing the contract, you are not able to change:

  • Purchasing unit​
  • Contract type​
  • Hierarchy type​
  • Supplier​
  • Contract type (release/ no-release)​
  • Currency

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.

No Release Order Process Flow

The process flow outlined here focuses on the method of handling contracts in the procurement process, particularly focusing on contracts without a release order. The process is described in a series of interlinked steps as follows:

  1. The process begins with the user creating a contract compliance request (CR). In this phase, the user selects a supplier and designates the items or services needed. They also establish control limits and determine access permissions for the contract.​
  2. The next step is the approval phase. The CR, once approved, transforms into an official Contract (C). This contract isn't immediately active, it only becomes accessible from a specified Effective Date.​
  3. Following approval, the contract is forwarded to the chosen supplier via the SAP Ariba Network. This network is a cloud-based solution that allows organizations to connect and conduct transactions.​
  4. After receiving the contract, the supplier then creates an invoice based on the agreed contract. This invoice is then sent back through the Ariba Network to SAP Ariba, the platform where all these steps are undertaken.​
  5. Lastly, the contract details are updated in SAP Ariba with information on receiving, invoicing, or payment data depending on the predetermined configuration settings of the system. This ensures clear record keeping, marking the resolution of the contract.​
The process begins with the user creating a contract compliance request (CR), The next step is the approval phase, Following approval, the contract is forwarded to the chosen supplier via the SAP Ariba Network, After receiving the contract, the supplier then creates an invoice based on the agreed contract, Lastly, the contract details are updated in SAP Ariba with information on receiving, invoicing, or payment data depending on the predetermined configuration settings of the system

Log in to track your progress & complete quizzes