Brief overview of Outline agreements

Outline agreements in SAP

Presentation – Contracts and Scheduling agreement

What is Outline Agreements? Where it fits in purchasing process?

The outline purchase agreement is often referred to as a blanket or umbrella purchase order. It is basically a long-term agreement between the purchasing department and vendor for material or services for a defined period of time. The purchasing department negotiates with the vendor a set of terms and conditions that are fixed for the period of agreement.

 

wh.JPG

 

Which business requirements lead to use of outline agreement?

 

  1. When purchasing department want to setup long term relationship with vendor for specific group of materials or services
  2. To negotiate binding conditions for purchasing (i.e. price, quantity, discounts etc.) without actually releasing purchase order
  3. Using pre-negotiated offer during day-to-day purchasing
  4. Increase speed of actual purchasing to satisfy actual requirements
  5. Provides better monitoring and control of actual release of purchase order against offer

 

Structure of an Outline Purchase Agreement

 

An outline purchase agreement consists of the following elements:

  • Document header: contains information relating to the entire agreement. For example, the vendor information and header conditions are in the document header.
  • Items: containing the information specific to the relevant material or service. For example:
  • Statistics on ordering activities for the item
    • Quantity or price of the item
    • Conditions, such as quantity discounts and surcharges

 

 

Contracts v/s Scheduling agreement

 

 

In SAP MM Purchasing, such agreements are subdivided into “contracts” and ” Scheduling agreements.”

 

Contracts:

  • Longer- term contract with subsequent issue of release orders
  • Different POs can be released for same contract
  • Mainly used for frequent non-predictable requirements e.g. Purchasing office supplies

 

Scheduling agreement

  • Longer-term scheduling agreements and delivery schedules
  • Same scheduling agreement number is used with different release calls
  • Mainly used for repetitive/predictable requirements e.g. purchasing spare parts of a large fleet
  • Can be tightly integrated with MRP

 

Contract

 

A contract is a longer-term agreement with a vendor (one of the two forms of “outline agreement” in the SAP system) to supply a material or provide a service for a certain period of time. A number of different terms may be used for this concept in purchasing literature, including “blanket order”, “blanket contract”, “systems contract” and “period contract”.

 

The contract does not contain specific delivery dates or the individual delivery quantities. These are specified subsequently in release orders issued against the contract when customer requires them.

 

Contract types

 

When creating a contract, you can choose between the following contract types:

  1. Value contract (MK) : The contract is regarded as fulfilled when release orders totalling a given value have been issued. Use this contract type when the total value of all release orders should not exceed a certain amount.
  2. Quantity contract (WK) : The contract is regarded as fulfilled when release orders totalling a given quantity have been issued. Use this contract type when the total quantity to order over the duration of the contract is known.

qq.JPG

 

Ways of Creating Contracts

Contract can be created in one of the following ways:

  1. Manually: Enter all the contract data manually.
  2. Using the referencing technique: Create a contract by referencing

a.          Purchase requisitions

b.          RFQs/quotations

c.          Other contracts

 

Characteristics of contract:

 

  • Contracts are outline agreements. They do not contain details of the delivery dates for each of the items.
  • To inform vendors of which quantity you need for which date, you enter contract release orders for a contract. A release order is a purchase order that references a contract.
  • If a purchasing information record with conditions exists for the material and the vendor, the system automatically suggests the net price according to these conditions when you create the contract item.
  • Contract validity period is defined in the contract header as the validity period
  • For each item in a quantity contract, you define the target quantity and purchase order conditions.

 

Item categories in contracts

 

Item Category

M – The material is unknown

W – Value and quantity are unknown

D – Procuring an external service

K – Consignment material is involved

L – Subcontracting material is involved

 

  • Item category M is recommended for similar materials with same price but different material numbers. For example, contract for copier paper.
  • Item category W is recommended for material belonging to the same material group but with different prices. For example, contract for office supplies.
  • Item category W can be used only in value contracts.
  • Item category M and W are not allowed in contract release orders.
  • Item category D is used for services contracts.

 

ic.JPG

  • Account assignment category, ‘U’ unknown can be used in contracts. In this case, cost center will be determined at time of creating release order.
  • The account assignment category, ‘U’ is denied in contract release orders. You have to replace the account assignment category with a valid account assignment category.

 

Processing contracts

 

  • Contract release orders are purchase orders that are created with reference to contract.
  • The release order documentation (i.e. the quantity released until now, and the open quantity) is automatically updated when you create a contract release order. This can be used for monitoring the contract.
  • The release order document is contained in the statistics for contract item.
  • You can enter source of supply in the purchase requisition. This ensures that the outline agreement is referenced when the purchase requisition is converted into a purchase order.
  • Contract release order can be created with or without reference to a purchase requisition.
  • The release order documentation comprises details of ordering activity relating to a contract. The system supplies the following data on each release order:

a.          Number of contract release order

b.          Order date

c.          Order quantity

d.          Order value

e.          Quantity released to date

f.          Target quantity

g.          Open target quantity

  • You can list all contracts that are due to expire in the immediate future. The analysis is carried out using the Target value and Total value released fields in the contract header, based on suitable selection parameters

 

Centrally Agreed contract

 

The centrally agreed contract allows a central purchasing organization to create a contract with a vendor that is not specific for just one plant. In this way, the purchasing organization can negotiate with a vendor by leveraging the whole company’s requirements for certain materials or services.

  • Contract items can relate all plants covered by a purchasing organization
  • All plants of a purchasing organization can order against a centrally agreed contract
  • Using the plant conditions function, the centrally agreed contract allows you to stipulate separate prices and conditions for each receiving plant. For example, different transport costs.

 

ca.JPG

 

SAP Transactions

 

  • Create value contract for material group (WK) – ME31K
  • Change contract – ME32K
  • List display contract – ME3L
  • Monitor contracts – ME80RN

 

References:

 

1.          help.sap.com

2.          SAP MM:Functionality and Technical Configuration, SAP Press

Steps for opening and closing period – MM FI CO

Steps for opening and closing Period – MM FI CO

As many of us struggle with changing periods in our DEV and QA environments, here is quick reference for opening and closing period. In doubt, please consult with your FI/CO expert.

There can be upto four transaction involved depending on your situation.

•          MMRV – Allow posting to previous period

•          MMPV – Close Periods

•          OB52 – Change view “Posting Periods: Specify Time Intervals”: Overview

•          OKP1 – Maintain Period Lock

1. MMRV – View current period / Allow posting to previous period

This transaction allows you to view current period and change setting for posting to previous period.

Capture1.JPG

Capture2.JPG

2. MMPV – Close Periods

In MMPV you can execute period closing up to the end of the current fiscal year. The period closing program updates the administration record, thus ensuring that the stock data of the material master are updated.

If, for example, you want to close your periods up to 03/2013, you are not allowed to post values in 01/2013. Therefore, if you still want to make postings in period t, you should execute period closing only for a maximum of t+1 periods.

Capture3MMPV.JPG

3. OB52 – Change view “Posting Periods: Specify Time Intervals”: Overview

In this activity, you close the posting periods for FI-AA and open the new periods for FI-AA.

No more FI-AA postings can be made to the previous period. Postings for the future periods are allowed.

Capture3OB52.JPG

4. OKP1 – Maintain Period Lock

If needed, unlock period for CO transaction.

Capture3OKP1.JPG

If I have missed anything here or misinterpreted, let me know and I will correct it or add additional clarification/tips.

Source: help.sap.com

Posted on: https://blogs.sap.com/2013/04/27/steps-for-closing-period-mm-fi-co/

PDF: Closing_Periods in SAP MM FI CO