Outline Agreement Procedure
Outline Agreement Procedure
<Other Clause>
Copyright @ 2003 Holcim Services (Asia) Ltd.
APBM
Document Control
Document Name Outline Agreement Procedure Training Document
Author Ha Tran
File Name & Path
Created 19-Nov-04
Last Edited
Printed on
Document Approval
Role Name Signature Date
Distribution List
Role Name Signature Date
Table of Contents
OVERVIEW .......................................................................................................................................... 4
USE OF CONTRACTS......................................................................................................................... 4
Overview
An outline purchase agreement is a longer-term arrangement with a vendor 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.
An outline agreement does not contain data on specific delivery dates or quantities to be delivered.
This data is transmitted to the vendor in one of two ways, depending on the type of outline
agreement. A vendor is notified of quantities and delivery dates either in a specialized form of
purchase order called a contract release order, or in a delivery schedule.
An outline agreement can be a contract or a scheduling agreement. There are two key differences
in the use of these two agreement types:
Use of Contracts
Contracts can be created without reference, or with reference to an outline agreement requisition, an
RFQ, or another contract.
Various item categories can be used. The item category influences document field control.
If the contract item is for a stock material, the corresponding views and data of the material master
record must have been created. If the item is for a consumable material, the account assignment
data may already be stored in the contract. Alternatively, account assignment category U can be
used. The use of this account assignment category means that the account assignment data does
not have to be specified until the purchase order is created.
Noted that since R/3 4.6A, the reference to the contract in the purchase order is entered at item
level. This has the advantage that items both with and without contract reference, or referencing
different contracts, can be included in a single purchase order.
The release documentation for the contract item is updated for each PO item created with reference
to a contract. The system provides the following data for each release order:
The release documentation also includes the total quantity or value already released and the target
quantity in comparison with the still open quantity, or the target value in comparison with the still
open value.
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.
• Quantity contract
The contract is fulfilled when a stipulated target quantity per contract item is reached as
a result of the issue of release orders.
• Value contract
The contract is fulfilled when a stipulated overall target value (total value of all items) is
reached as a result of the issue of release orders.
• Distributed contracts
These are centrally agreed contracts that are made available to other R/3 system for the
issue of release orders against the contract. Contracts can be created in one SAP
system and then be made available to other independent SAP systems (that is,
distributed among other systems). The central system in which the contract is created
and the local systems that also procure using this contract are all separate, independent
SAP systems. The data must therefore be kept identical in each individual system. In
order for changes to be continually compared and reconciled, thus ensuring that all the
systems involved always have the correct data, data is exchanged via Application Link
Enabling (ALE).
The contract type quantity contract (MK) is chosen if the total quantity of each item to be ordered
over the duration of the contract is known. After specifying the validity period of the contract in the
header data, it is mandatory to enter the target quantity at item level. Specification of the total value
in the header data is optional.
The contract type value contract (WK) is selected if the total value of all release orders issued
against this contract is not in excess of a certain amount. In addition to the validity period, the target
value must be specified in the header data of the value contract. Specification of the relevant target
quantity at the item level is possible, but not necessary.
Noted that all contracts that are due to expire in the future can be listed. The analysis, which is
based on a suitable selection parameter, is run over the fields Target Value and Total Release Value
for value contracts and Target Quantity and Quantity Released To Date for quantity contracts.
The item categories M and W are intended for the entry of contract items without specification of the
material number.
Item Category M
Recommended for similar materials of the same price. These can be materials with different
material numbers or materials without material master records.
When this contract item of category M is entered, the short description, material group, target
quantity, unit of measure, and price are entered but not the material number. The short description
must then be entered in the contract release order (for example, lined, two-hole pre-punched).
It is also possible to have the option of releasing materials with a material master record against this
contract item in the release order, provided that the material group and purchase order unit of
measure agree.
Item Category W
Recommended for materials belonging to the same material group but with different prices. Item
category W can only be used in value contracts.
When entering the contract item, only the short text and the material group are entered. The target
quantity or price is not required to be entered. However, it is possible to enter additional conditions.
For example, a discount can be entered in the header conditions if the vendor grants a discount on
all POs referencing the contract. The discount is calculated automatically when a contract release
order is created.
The price, the target quantity, and the material number are not specified until a release order is
created. The relevant material master record must be assigned to the same material group as the
contract item referenced. If the contract release order does not contain a material number, it must
have a valid account assignment (such as a cost center).
Noted in the purchase order, the item categories M and W are not allowed. Prior to R/3 4.6A, it is
required to remove the preset item category M and W manually when a release order is created
referencing a certain contract item. Since 4.6A, the item category in a release order to be issued
against a contract item having the item category M or W is blank, so it is not mandatory to remove it
any longer.
No new item categories can be defined in Customizing. Neither can the attributes of existing item
categories be changed. Of course, only the short description of item categories can be changed.
Use
An enterprise that operates with a central purchasing organization covering several plants can
negotiate better conditions at a higher level. It is possible to create contracts that relate not to just
one particular receiving plant, but to the purchasing organization. In this case, a centrally agreed
contract is created without specification of a plant.
The plant is not specified until the contract release order is created. All plants covered by the
purchasing organization can release against a centrally agreed contract. In the case of plant-
specific contracts, a release order can only be created for the relevant receiving plant. In addition, in
centrally agreed contract, different conditions or partners (for example) for individual plants can be
created as well.
Noted if certain plants are not to be allowed to release against the contract, the centrally agreed
contract should be blocked as a source in the source list for these plants.
Features
Plant Conditions
Centrally agreed contracts enables to specify separate conditions for each receiving plant ie. it
allows prices and conditions to be determined individually for each receiving plant. This makes it
possible, for example, to make due allowance for different transportation costs for different routes
and distances. Plant conditions are not an add-on to the central conditions, but a plant-specific
alternative to them. Noted, however, that maintenance of plant conditions in centrally agreed
contracts is only possible via Edit Æ Plant Conditions.
When the contract release orders are created for plants without plant conditions, the conditions of
the contract item are used.
If certain plants are not to issue release orders against the contract, the central contract should be
blocked from use as a source of supply by these plants in the source list.
Partner Roles
Vendors may assume different roles (partner roles) in the procurement process. Partner roles
(sometimes also referred to as “partner functions”) include the roles of “ordering address”, “goods
supplier”, and “invoicing party” or forwarder/carrier.
Various partner roles can be maintained either in the vendor master record (in the Partner Roles
view) or in each individual contract. The partners being defined in the vendor master record are
valid for a certain purchasing organization. In addition to the partners that are valid for a purchasing
organization, different partners can be created for individual plants or vendor sub-ranges in the
vendor master record.
If the partners have already been defined in the vendor master record, they are pulled from there
into the contract as default values. However, partner roles can also be assigned for the first time in
the contract.
Two individual vendors belonging to the vendor corporate group X supply receiving plants in different
region. In the vendor master record, the receiving plants have been assigned as follows: Vendor X2
supplies plant 0001 only, and vendor X3 to plant 0002 only. If a buyer wishes to release material
4711 against the centrally agreed contract with vendor corporate group X, he or she enters the key
for the plant for which the material is to be procured.
If he or she enters plant 0001, the system determines vendor X2 as the ordering address on the
basis of the assignment in the vendor master record. Similarly, if he or she enters plant 0002, the
system determines vendor X3 as the ordering address on the basis of the assignment in the vendor
master record.
It is also possible to assign several partners with the same role to a plant (e.g. two ordering
addresses). When the release order is created, it is required to decide on one of them.
Fig-01
1.2. On “Create Contract : Initial Screen” screen, fill in the data as below:
Fig-02
Purchasing group Key for a buyer or a group R Enter the purchasing group
of buyers, who is/are
responsible for certain
purchasing activities
Item Category Key defining how the O Enter the item category
procurement of a material
or service item is
controlled
Acct assignment Specifies whether O Enter the acct assignment cat.
cat. accounting for an item is to
be effected via an auxiliary
1.3. On “Create Contract : Header Data” screen, fill in the data as below:
Fig-03
1.4. On “Create Contract : Item Overview” screen, fill in the data as below:
Fig-04
Targ. qty. (Target Total quantity that can be O Enter the target quantity
quantity) released or scheduled
against the relevant
agreement
Oun (Order Unit) Specifies the unit of O Enter the order unit
measure in which the
material is ordered
Net price Net price per price unit O Enter the net price
1.5. On “Create Contract : Item XXXXX” screen, fill in the data as below:
Fig-05
1.6. In case, supplementary pricing conditions are required to be maintained for the contract
document. On “Create Contract : Item XXXXX Additional Data” screen, maintain
information as specified in the table below:
Fig-06
1.7. On “Create Gross Price Condition (PB00) : Condition Supplements” screen, maintain
information as specified in the table below:
Fig-07
1.8. On “Create Contract : Item Overview” screen, maintain information as specified in the
table below:
Fig-08
Fig-09
Fig-10
2.2. On “Create Contract : Initial Screen” screen, fill in the data as below:
Fig-11
Purchasing group Key for a buyer or a group R Enter the purchasing group
of buyers, who is/are
responsible for certain
purchasing activities
Item Category Key defining how the O Enter the item category
procurement of a material
or service item is
controlled
Acct assignment Specifies whether O Enter the acct assignment cat.
cat. accounting for an item is to
be effected via an auxiliary
2.3. On “Create Contract : Header Data” screen, fill in the data as below:
Fig-12
2.4. On “Create Contract : Item Overview” screen, fill in the data as below:
Fig-13
Targ. qty. (Target Total quantity that can be O Enter the target quantity
quantity) released or scheduled
against the relevant
agreement
Oun (Order Unit) Specifies the unit of O Enter the order unit
measure in which the
material is ordered
Net price Net price per price unit O Enter the net price
2.5. On “Create Contract : Item XXXXX” screen, fill in the data as below:
Fig-14
Click on icon
2.6. On “Create Contract : Item XXXXX Additional Data” screen, maintain information as
specified in the table below:
Fig-15
2.7. On “Create Contract : Item Overview” screen, maintain information as specified in the
table below:
Fig-16
Fig-17