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
[email protected] (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
February / March 2008 Volume VI Issue 1
SAPtipsJournal
Page
SAPtips4On Logistics/MM 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 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’s upcoming Material Masters workshop—found only at SAPtips University in Dallas!
Condition Types: Introduction
Conditions refer to Pricing “rules” in SAP Purchasing. You can maintain conditions related to discounts, surcharges, taxes, freight, and just about anything you want to add to the pricing procedure for Purchasing. Conditions can be used in Purchase Orders, Info Records, Quotations, and Outline Agreements. In addition 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. Timedependent conditions will generate subtotals – net price and effective price. Note: If you wish to share conditions across Purchasing Organizations, create a Reference Purchasing Organization and maintain them at that level.
In this article, I will discuss two types of conditions that exist in SAP: time-dependent and time-independent conditions. This tip was developed using ECC 6.0, but is relevant to earlier releases as well.
Time-Dependent Conditions
Info Records, Contracts, Quotations, and Scheduling Agreements all contain time-dependent conditions, unless otherwise specified in Customizing. Time-dependent conditions allow you to assign validity periods and scales to the pricing. They can also be entered generically against a vendor, a vendor sub-range (a grouping
Figure 1: Vendor Subrange Field
SAPtips.com
SAPtips © 2008 Klee Associates, Inc.
February / March 2008 Volume VI Issue 1
SAPtipsJournal
Page
SAPtips4On Logistics/MM SAP utilizes a pricing procedure called “Condition Technique” to arrive at a net cost for your purchases.
This article will provide step-by-step instructions on how to create and add a new condition type to an existing calculation schema that is used for standard Purchase 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
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:
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 Purchasing Organization level. This means that we will need two Condition Tables.
• Condition Type – represents various factors that lead to the net price and can include discounts, surcharges, freight, base price, and taxes.
The following provides steps to finding the corresponding Condition Table that we will assign to our access sequence in the next step:
• Condition Table – includes the fields that will be used in your access sequence.
1. Navigate to the IMG, and follow the path: 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 sequence determines the level at which you would 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 differentiate between the levels at which you maintain this data, you assign multiple Condition Tables to your access sequence, and you define the order in which the system accesses the records. The example provided in this section will explain this further.
2. Click on “Display condition table” (Figure 2) and click on
• Calculation Schema (this is the term in Purchasing, 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.
