Using Condition Types in SAP: Knowing What Condition Your Condition Is In

Below is a snippet from one of hundreds of articles available to ERPtips subscribers.

If you would like a complimentary copy of the full article, please email
Mark.Downs@ERPtips.com
(include the title of the article in your email)

To subscribe to ERPtips, go to
www.ERPtips.com/Subscribe.asp.

ERPtips Journal is published by Klee Associates, Inc.

ERPtips University provides both public and onsite training for SAP clients.
For more about ERPtips University, including the current schedule, click here:
www.ERPtips.com/WorkshopSchedule.asp

Using Condition Types in SAP: Knowing What Condition Your Condition Is In

Want to love SAP Purchasing unconditionally? Jocelyn Hayes demonstrates how to create a new
condition type, add it to a calculation schema, and test. Once you`ve mastered this not-so-easy
technique in purchasing—you can apply this to SD Pricing as well! This is yet another taste from Jocelyn

Click here to read this Snippet

 SAPtips4On Logistics/MM
Page 

February / March 2008 Volume VI Issue 1

Using Condition Types in SAP : ®

Knowing What Condition Your Condition Is In

By Jocelyn Hayes, SAPtips Director of Consulting and Training

Editor’s Note: Want to love SAP Purchasing uncondi-
tionally? Jocelyn Hayes demonstrates how to create a
new condition type, add it to a calculation schema, and
test. Once you’ve mastered this not-so-easy technique in
purchasing—you can apply this to SD Pricing as well!
This is yet another taste from Jocelyn’s upcoming Mate-
rial Masters workshop—found only at SAPtips Univer-
sity in Dallas!
Condition Types: Introduction
Conditions refer to Pricing “rules” in SAP Purchas-
ing. You can maintain conditions related to discounts,
surcharges, taxes, freight, and just about anything
you want to add to the pricing procedure for Purchas-
ing. Conditions can be used in Purchase Orders, Info
Records, Quotations, and Outline Agreements. In addi-
tion to these conditions, you
can also maintain Vendor
conditions on the Vendor
Master record that apply to
all Purchasing documents
created for that Vendor.
of materials offered by the vendor), a material condition
group, material group, material type, incoterms, and
invoicing party.
Vendor Subrange is maintained in the Info Record in
Figure 1.
Time-Independent Conditions
Opposite of time-dependent conditions, no validity
period or scales exist for time-independent conditions.
Purchase Order conditions are time-independent. Time-
dependent conditions will generate subtotals – net price
and effective price.
Note: If you wish to share conditions across Purchasing
Organizations, create a Reference Purchasing Organiza-
tion and maintain them at that level.

In this article, I will discuss

two types of conditions that
exist in SAP: time-depen-
dent and time-independent
conditions. This tip was
developed using ECC 6.0,
SAPtipsJournal

but is relevant to earlier

releases as well.

Time-Dependent
Conditions
Info Records, Contracts,
Quotations, and Schedul-
ing Agreements all contain
time-dependent conditions,
unless otherwise specified in
Customizing. Time-depen-
dent conditions allow you to
assign validity periods and
scales to the pricing. They
can also be entered generi-
cally against a vendor, a
vendor sub-range (a grouping Figure 1: Vendor Subrange Field

SAPtips.com SAPtips © 2008 Klee Associates, Inc.

 SAPtips4On Logistics/MM
Page 

February / March 2008 Volume VI Issue 1

This article will provide step-by-step instructions on

SAP utilizes a pricing procedure
called “Condition
Technique” to arrive at a net cost
for your purchases.
SAP utilizes a pricing procedure called “Condition
Technique” to arrive at a net cost for your purchases.
The same concept is utilized in SAP Sales Pricing. It has
four main components that must be understood:
how to create and add a new condition type to an exist-
ing calculation schema that is used for standard Pur-
chase Orders. The new condition type will be to have a
vendor discount included automatically at the header of
a Purchase Order.
Step 1: Determine Condition Table to Use
in Access Sequence
In the first step of creating a new condition type, you
must determine what fields you want to use in storing
your condition records. In this example, we will provide
the option to store the Vendor Discount condition record
at the Vendor level only or at the Vendor and Purchas-
ing Organization level. This means that we will need
two Condition Tables.

• Condition Type – represents various factors that lead The following provides steps to finding the correspond-
to the net price and can include discounts, surcharges, ing Condition Table that we will assign to our access
freight, base price, and taxes. sequence in the next step:

• Condition Table – includes the fields that will be 1. Navigate to the IMG, and follow the path:
used in your access sequence. Materials Management ‡ Purchasing ‡ Conditions ‡ Define
Price Determination Process ‡ Maintain Condition Table
• Access Sequence – when you create a condition
record, you select an access sequence. The access 2. Click on “Display condition table” (Figure 2) and
sequence determines the level at which you would click on
like to maintain your condition. For example, if you
are maintaining a condition record for a Vendor
Discount, you may wish to maintain it at the Vendor
level, or the combination of Vendor and Purchasing
Organization. To differen-
tiate between the levels at
which you maintain this
data, you assign multiple
Condition Tables to your
access sequence, and you
SAPtipsJournal

define the order in which

the system accesses the
records. The example pro-
vided in this section will
explain this further.

• Calculation Schema
(this is the term in Pur-
chasing, it is the same
as Pricing Procedure
in SD)– the calculation
schema includes all the
condition types you will
use to determine your net
price.
Figure 2: Display Condition Table

SAPtips.com SAPtips © 2008 Klee Associates, Inc.