Working with Contracts

Objectives

After completing this lesson, you will be able to:
  • Manage contracts
  • Get to know analytics for contracts

Overview of Outline Agreements

The figure provides an overview of Outline Agreements. An outline purchase agreement is a long-term agreement with a supplier covering the supply of materials or the provision of services, subject to predetermined conditions.

An outline purchase agreement is a long-term agreement with a supplier covering the supply of materials or the provision of services, subject to predetermined conditions. These apply for a predefined period and a predefined total purchase quantity or certain total purchase value.

For long-term outline agreements, you can also store several condition records for each item if, for example, the outline agreement is to last five years and prices within this validity period are to decrease annually by 3%.

Hint

SAP uses the terms Target Quantity and Target Value. The legally binding nature of these specifications must be agreed separately with the supplier.

An outline agreement does not contain data on specific delivery dates or quantities to be delivered.

Depending on the type of outline agreement, this data is transmitted to the supplier in one of the following ways:

  • Contract: contract release order

  • Scheduling agreement: delivery schedule

The following are the key differences in the use of a contract and a scheduling agreement:

  • The volume of documents:

    In the case of a contract, as a rule, you create a new purchase order in the system each time you release goods or services against the contract. With a scheduling agreement, however, there is only one more document in addition to the contract document. This document is the scheduling agreement delivery schedule line, which is extended continuously.

  • Use in automatic materials planning:

    Requirements planning can be set up in a way that the contract item is automatically assigned to a requisition item as the source of supply. However, this requisition must subsequently be converted into a purchase order (= contract release order). In the case of a scheduling agreement, you can directly generate scheduling agreement delivery schedules from the planning run, so that no further processing in purchasing is required.

Creating and Maintaining Contracts and Scheduling Agreements

In the SAP Fiori launchpad, you can use the following apps to maintain purchase outline agreements:

  • App to create, manage, view or renew purchase contracts: Manage Purchase Contracts
  • App to create, manage, or view scheduling agreement: Manage Purchase Scheduling Agreements
  • Apps for purchase contracts that correspond to GUI transactions: Create Purchase Contract, Change Purchase Contract, Display Purchase Contract
  • Apps for purchase contracts that correspond to GUI transactions: Create Scheduling Agreement, Change Scheduling Agreement, Display Scheduling Agreement

In the SAP GUI on the SAP Easy Access screen, you choose the following menu paths to maintain contracts or scheduling agreements:

  • LogisticsMaterials ManagementPurchasingOutline AgreementContractCreate(ME31K).

  • LogisticsMaterials ManagementPurchasingOutline AgreementContractChange(ME32K).

  • LogisticsMaterials ManagementPurchasingOutline AgreementContractDisplay(ME33K).

  • LogisticsMaterials ManagementPurchasingOutline AgreementScheduling AgreementCreate(ME31L).

  • LogisticsMaterials ManagementPurchasingOutline AgreementScheduling AgreementChange(ME32L).

  • LogisticsMaterials ManagementPurchasingOutline AgreementScheduling AgreementDisplay(ME33L).

Introduction to Contracts

Contracts can be created with or without reference to the following:

  • A purchase requisition

  • An outline agreement requisition

  • A request for quotation (RFQ)

  • Another contract

The figure provides you with an overview of working with contracts

Various item categories can be used. The item category influences the document field control.

Depending on the type of item, data must be created as follows:

  • If the contract item is a stock material, purchasing and accounting data must have been created in the relevant material master record.

  • If the contract item is a consumable material, the account assignment data may already be stored in the contract. Alternatively, you can use the account assignment category U (Unknown), which indicates that the account assignment data must not be specified before creating the contract release order.

Contract Release Documentation

The release documentation also includes the following:

  • Quantity or value already released

  • Target quantity in comparison with the still open quantity or the target value in comparison with the still open value

Caution

Over-deliveries and under-deliveries for contract release orders are only included in the release documentation if you set the update to by the delivered quantity using the Customizing transaction OMXX.

Whether the release documentation is updated with reference to the target value of the contract or the target quantity of each individual contract item depends on the agreement type used. For value contracts, the target value is updated at the header level. For quantity contracts, the target quantity is updated at the line item level.

Contract Types

Centrally Agreed Contracts

In plant-specific contracts, a release order can only be created for the relevant plant. In a centrally agreed contract, however, you can store different conditions or partners for individual plants.

Hint

If you do not want certain plants to release against the centrally agreed contract, block the centrally agreed contract as a source in the source list for the materials of these plants.

The plant relevance of a contract item cannot be changed subsequently.

A centrally agreed contract can also be created from a central purchasing organization. When creating a contract item, the system does not check whether the purchasing organization that creates the contract is responsible for a particular plant. This check only occurs in the contract release order. If the release order is performed from another purchasing organization, the central purchasing organization of the releasing purchasing organization must be assigned as the reference purchasing organization.

Plant Conditions in Centrally Agreed Contracts

Caution

In the transaction Create Purchase Contract and the corresponding app, the maintenance of plant conditions in centrally agreed contracts is only possible using (Menu)EditPlant Conditions.

If you have maintained different purchasing data or partner roles on plant or supplier subrange levels, that data is also adopted in the contract. You can change this data on a contract-specific basis.

Central Contracts Using Procurement Hub

Central Procurement

Central Procurement enables integration of the SAP S/4HANA hub system with multiple SAP ERP and SAP S/4HANA back-end systems. Contract management, purchasing, and requisitioning processes can be centralized with the hub system.

Optionally, you can leverage SAP Ariba solutions like Guided Buying.

To use Central Procurement, you have to activate the Procurement Hub and the desired scenarios in the back-end system.

Choose IMGMaterials ManagementPurchasingCentral Procurement - Settings in Hub SystemActivate SAP S/4HANA Procurement Hub and Scenarios.

Central Purchase contracts enable you to create, change, and display contracts created centrally in the hub system. A central purchase contract is a global long-term agreement between an organization and a supplier regarding the supply of materials or the performance of services within a certain period as per predefined terms and conditions. This enables purchasers from various parts of a company at different locations to take advantage of the negotiated terms and conditions. The central purchase contracts are created in SAP S/4HANA (which acts as a hub system) and distributed to the connected systems. SAP ERP, SAP S/4HANA Cloud, or SAP S/4HANA can act as connected systems.

Note

Further procurement scenarios, which are available in the hub scenarios, are as follows:

  • Central Requisitioning
  • Central Purchasing
  • Central Sourcing

Central Procurement is the successor of central functions in SAP SRM.

Create a Centrally Agreed Contract and Issue Release Orders

Contract Monitoring

The figure shows you an example of Selection Parameters in the system

Accumulated values are updated at the item level for quantity contracts, and at the header level for value contracts. You can list all contracts that are going to expire in the near future. The analysis, which is based on a suitable selection parameter, is run on the Target Value and Total Release Value fields for value contracts and the Target Quantity and Quantity Released to Date fields for quantity contracts.

In Customizing for Materials Management under PurchasingReportingMaintain Purchasing ListsSelection ParametersDefine Selection Parameters, you can define a percentage of the target value or target quantity above which a contract is to be regarded as expiring.

Beyond the value and quantity, you can also check contracts with regard to their validity period.

Hint

Target quantity, target value, and validity period are checked in the contract release order. If the quantity or value is exceeded, or in the case of release orders outside the validity period, warning messages are issued. You can set these as error messages to prevent release. You can double-click the warning message to view the message number.

You can define system messages in Customizing for Materials Management under PurchasingEnvironment DataDefine Attributes of System Messages. You can also use the system messages to ensure that a purchase order for a material that has an outline agreement is only possible with a contract reference.

The figure shows SAP Fiori apps for Contract Monitoring in the system

On the SAP Fiori launchpad, following SAP Fiori apps are available for contract monitoring:

  1. Off-Contract Spend: You can use the Off-Contract Spend app to analyze the total spend amount in relation to purchase orders that do not have a contract reference, over the previous year to date. For some items, no negotiated pricing or blanket purchase agreement is in place when they are purchased. These items are defined as non-contract purchases. You can use this app to measure the percentage of purchases made without any contract.

  2. Unused Contracts: You can identify contracts for which a release has not taken place within a specific time frame. With Unused Contracts, you can find the released amount of the unused contracts in the display currency and the IDs of all unused contracts.

  3. Contract Expiry: You can use this app to identify purchase contracts that expire within a specific time frame (default: 90 days). You can also use the app to find the number of expiring contracts, target amount, and the released amount of the expiring contracts.

  4. Contract Leakage: With the Contract Leakage app, you can identity the spend of purchase orders that do not have a contract reference, although an existing contract could have been used. As a purchaser, you want to find the related net value. You can use the Contract Leakage app to determine the amount of purchases made without considering existing contracts.

  5. Value Contract Consumption: You use this app to identify the consumption percentage of value-type contracts from the previous year to date. You can also find the target and released amount of the contracts.

  6. Quantity Contract Consumption: You use this app to identify the consumption percentage (value-based, not quantity-based) of quantity type contracts from the previous year to date. You can also find the target and released quantity of the contracts.

To get an overview of your contracts, you can use the app Manage Purchase Contracts. This app gives you a graphical overview of your contracts including the consumption and expiring data. If a contract is about to expire or has already expired, you can edit the contracts.

Another app for monitoring contracts is Monitor Purchase Contract Items. With this app, you can display aggregated values of purchase contract items for material groups and filter them according to your requirements.

Reporting for Contracts

The following table lists useful evaluations available for contracts in the back-end system:

Evaluations Available for Contracts

EvaluationsTransaction Codes
General evaluationsME80RN
Outline agreements per vendorME3L
Outline agreements by materialME3M
Outline agreements by material groupME3C
Conditions by contractMEKB

In addition, the following apps are also available on the SAP Fiori launchpad:

  • Manage Purchase Contracts
  • Manage Purchase Contract Items