Condition Type in SAP: How to Create & Configure

โšก Smart Summary

Condition Types in SAP describe each element of a price, such as gross price, discount, or freight. Customizing controls the condition class, calculation type, access sequence, and the changes a user may make during document entry.

  • ๐Ÿท๏ธ Core Definition: A condition type represents one pricing element, for example PB00 gross price or a percentage discount.
  • ๐Ÿ”Ž Access Sequence: Each condition type points at an access sequence that decides where its value is searched for.
  • โš™๏ธ Control Data 1: Condition class, calculation type, condition category, rounding rule, and plus or minus sign.
  • ๐Ÿ‘ฅ Group Condition: Allows one condition to spread its value across several items in the same document.
  • โœ๏ธ Change Control: Manual entry, header or item level, deletion, and which fields a user may overwrite.
  • ๐Ÿ“ˆ Scales: Quantity or value scales let the rate change automatically as the ordered amount grows.
  • ๐Ÿ“‹ Copy to Create: New condition types are normally created by copying an existing one and adjusting the copy.

Condition type in SAP MM

What is a Condition Type in SAP?

A condition type is the smallest unit of pricing in SAP. Each one describes a single element that contributes to the final price: the gross price itself, a percentage discount, a freight charge, a tax, or a surcharge for a small order.

On a purchase order the buyer sees one net value, but underneath it SAP has evaluated a list of condition types in a defined order. Three pieces of configuration make that possible:

  • The condition type describes what kind of value this is and how it behaves.
  • The access sequence attached to it decides where SAP looks for the value, and in what priority.
  • The calculation schema decides the order in which the condition types are applied and what each is calculated from.

PB00 is the reference example. It is the gross price, it carries an access sequence that searches the info record and contract, and it sits at step 1 of the standard purchasing schema so that every discount below it has a base to work from.

Steps to Define Condition Types

Defining of condition types can be done in few simple steps.

Step 1) Define condition types

In the IMG, click on the define condition types option.

Define Condition Types in SAP

Step 2) Choose Define Condition

In next step, Choose Define Condition Type option.

Define Condition Types in SAP

Step 3) Find all of the existing entries

You can find all of the existing entries for condition types.

  1. Click on the desired condition you would like to change.
  2. Click this icon to choose the selected condition and enter the change mode.
  3. If you want to create a new entry click on New entries. In this case, you don’t have to select any existing entries.
  4. If you want to create a new condition type by copying an existing condition type (it will inherit its settings which you can change โ€“ just like copying a condition table in the previous topic), you can choose this icon โ€“ copy condition type.

You have several more actions at your disposal: deletion, selecting all condition types, deselecting all condition types.

Define Condition Types in SAP

If you select multiple condition types, you can edit them all by navigating through them in the following screen (arrow left and right or F7 and F8).

This screen has a lot of settings for a condition type, let’s review the most important.

Step 4) Section of the screen contains

First section of the screen contains condition type PB00, description, and access sequence used for condition determination.

A) Control data 1 section contains the following:

  1. Condition class (e.g. prices, discounts, taxes)
  2. Calculation type (e.g. quantity, percentage, fixed amount, formula)
  3. Condition category (e.g. basic price, input tax)
  4. Rounding rule (e.g. commercial, round up, round down)
  5. Plus/minus (indicates if a condition can be positive, negative or both)

B) Group condition section:

  1. Group condition (indicates if a condition calculates its value by more than one item in the document)
  2. RoundDiffComp (rounding difference comparison)
  3. Group condition routine (routine that calculates the value)

C) Changes which can be made section:

  1. Manual entries (e.g. no limitations, not possible, manual entry has priority)
  2. Header condition (indicates if a condition can be used at header level)
  3. Item condition (indicates if a condition can be used at item level)
  4. Delete (indicates if a condition can be deleted)
  5. Amount/percent (can amount/percentage be changed)
  6. Value (can value be changed)
  7. Qty. relation (can conversion factor between UoMs be changed during processing)
  8. Calculat. Type (can calculation type be changed during processing)

Define Condition Types in SAP

Step 5) Save your changes

The other section on the lower end of the same screen are:

D) Master data section:

  1. Valid to (default date to use)
  2. Pricing Proc. (pricing procedure to be used for this condition type)
  3. Delete fr. DB (deletion procedure for this condition type)

E) Scales section:

  1. Scale basis (e.g. quantity scale, value scale)
  2. Check value (default blank)
  3. Scale type (controls the validity of the value/quantity)

F) Control data 2 section:

  1. Currency Conv. (indicates if currency conversion is allowed)
  2. Accruals (if you check this box you indicate that it is a statistical condition)
  3. Promotion condition (is this condition relevant only for promotions)
  4. Quantity conversion (controls how quantity conversion will be processed)
  5. Exclusion (condition exclusion indicator โ€“ e.g. gross price, tax code, delivery cost)
  6. Rel.Acc.Assig (determines if the condition type is relevant for account assignment)

Define Condition Types in SAP

When you are done with creating, changing or copying of the condition type, you can save your changes.

โš ๏ธ Warning: Always copy an existing condition type rather than editing a standard one such as PB00. A support pack can overwrite standard entries, and a copied type in the customer name range keeps your settings safe.

Condition Class, Calculation Type and Condition Category

These three fields sit next to each other on Control data 1 and are the most frequently confused settings in pricing configuration. They answer different questions.

Field Question it answers Typical values
Condition class What kind of element is this? B price, A discount or surcharge, D taxes
Calculation type How is the amount worked out? C quantity, A percentage, B fixed amount, formula
Condition category What special role does it play? H basic price, D tax, B delivery costs, blank for none
Plus/minus Which sign is permitted? A positive only, X both, blank negative only
Rounding rule How is the result rounded? Commercial, round up, round down

Condition category is the field that quietly changes behaviour elsewhere. Setting it to B marks the condition as a delivery cost, which makes it appear on the goods receipt for planned delivery costs and posts it to a freight clearing account rather than into the stock value.

Standard Purchasing Condition Types

SAP delivers a working set of condition types for purchasing. Recognising them saves building equivalents from scratch and makes an existing configuration far easier to read.

Condition Type Meaning Class
PB00 Gross price found automatically through an access sequence Price
PBXX Gross price entered manually, no access sequence Price
RA00 Percentage discount from the gross value Discount
RA01 Percentage discount on the gross price Discount
RB00 Absolute discount Discount
ZA00 Absolute surcharge Surcharge
FRA1 Freight as a percentage Delivery cost
FRB1 Freight as an absolute amount Delivery cost
FRC1 Freight per quantity unit Delivery cost
SKTO Cash discount, normally statistical Discount
NAVS Non deductible input tax Tax

PB00 and PBXX illustrate the role of the access sequence perfectly. PB00 carries one and therefore finds a price by itself from the purchase info record or a contract. PBXX carries none, so it exists purely to accept a manually typed price. The full configuration sequence is covered across the SAP MM tutorial series.

FAQs

Either no access sequence is assigned, or the condition records behind it do not exist for the key being used. Check the access sequence first, then the condition records in MEK3.

A header condition applies to the whole document and is distributed across items, typically by value. An item condition applies to one line only. A condition type can permit both.

AI compares a proposed condition type against similar ones already in use and warns when class, calculation type, and category form a combination that has never worked in practice.

Yes. Analysing order quantities and paid prices reveals where volume breaks genuinely occur, so scale levels reflect real buying patterns instead of round numbers chosen by hand.

It lets one condition consider the combined quantity or value of several items when choosing a scale rate, then distributes the resulting amount back across those items proportionally.

Summarize this post with: