Using Special Condition Types

Objective

After completing this lesson, you will be able to use special condition types

Manual Pricing

Once a value is entered for condition type Order Value (HM00), all other found pricing elements in the order are automatically deactivated.

Note

Condition type HM00 is used whenever an entire sales order value has been agreed upon with a customer and you need to enter this order value manually in the sales order.

The concept of using the condition exclusion indicator on condition type PR00 with requirement 2 in the pricing procedure was introduced as a method to achieve net pricing. In addition, you can specify the net price manually at the header level with condition type HM00. The PN00 condition type allows you to specify the net price at the item level.

Header condition type HM00 allows you to enter the order value manually. The system then distributes the new order value proportionally between the items, taking into account the previous net item value. The system determines the taxes again for each item.

Net Price PN00

Once for a sales order item a price is entered for condition type PN00, all other found condition values are automatically deactivated for that sales order item.

Condition type PN00 allows you to specify the net price for an item manually. The system deactivates the original conditions.

Minimum Order Value

Note

See the following video to learn about the special condition types for maintaining a minimum order value:

Minimum Price PMIN

If for a sales order item a minimum price has been set in a condition record for condition type PMIN, and the net sales order item value is below this minimum price, a surcharge is added to the sales order item using condition type PMIN.

You can create a minimum price for a material by using condition type PMIN. If the minimum price is not met during pricing, the system determines the difference by using condition type PMIN.

How to Use Condition Types AMIW and AMIZ

Graduated Pricing

Condition type Graduated-to interval scale price PR02 can be used to charge a customer for the materials bought in each tier of a scale instead of applying a single price to all bought materials.

You can maintain condition records with interval scales if the condition type is set to scale type D in Customizing. You CANNOT use interval scales for group conditions.

Note

Both condition types PR00 and PR02 are assigned condition class B. PR02 is placed after PR00 in the pricing procedure. The price with the highest level is always used because only one price can be effective at any given time.

PR00 becomes inactive automatically. PR02 uses scale type D (graduated to interval scale) to allow the calculation by using multiple levels on the scale in the condition record.

When using scale type D (graduated to interval scale), always make the last point on the scale a larger number than will ever occur in the production environment. This avoids an error in calculation for the last part of the line item quantity.

Use Special Condition Types

ExerciseStart Exercise

Customer Hierarchy Pricing

An example is shown of a customer hierarchy: customer Miller.

Customer hierarchies are available in the SAP standard system to enable you to create flexible hierarchies that reflect the structure of customer organizations. For example, if your customer base includes multilevel buying groups, cooperatives, or chains of retail outlets, you can create hierarchies to reflect the structure of these groups. You use customer hierarchies during sales order processing and billing to determine pricing and statistics. Customer hierarchies are valid only for a certain period of time.

A customer hierarchy consists of nodes.

The steps to create a customer hierarchy are as follows:

Create master records for each node.
Assign the nodes to each other.
Assign the customer master records to the relevant nodes.

You can move the hierarchy nodes. If you move a node, the system automatically reassigns all related nodes and customer master records.

Hierarchy Path

A customer hierarchy is shown, representing the multilevel buying group called Miller. Miller head office is the highest node defined in the hierarchy. The southern, northern, central, and northeastern regional offices are also defined as nodes. A price agreement is decided with the Miller buying group for a particular product line. You offer a discount that is valid for all regions and offices in the buying group. In addition, you offer a promotional discount for the northern zone. You create the appropriate condition records for the Miller head office and northern nodes. An order from customer 2742 is received and granted the cross-regional discount. When you receive orders from customers 2743 and 2744, the system uses the pricing data that is stored for the northern regional office and grants the exclusive promotional discount.

You can assign price or rebate agreements to a high-level node within a customer hierarchy. The agreements are then valid for customers at all the subordinate levels of this node. You can create pricing condition records for each node that is indicated as relevant for pricing. If one or more nodes in the hierarchy path of a sales order contain pricing information, the system takes these nodes into account automatically during pricing according to the defined access sequence.

The customer hierarchy in the figure represents the multi-level buying group, Miller. Miller head office is the highest node defined in the hierarchy. The southern, northern, central, and northeastern regional offices are also defined as nodes.

A price agreement is decided with the Miller buying group for a particular product line. You offer a discount that is valid for all regions and offices in the buying group. In addition, you offer a promotional discount for the northern zone. You create the appropriate condition records for the Miller head office and northern nodes.

An order from customer 2742 is received and granted the cross-regional discount. When you receive orders from customers 2743 and 2744, the system uses the pricing data that is stored for the northern regional office and grants the exclusive promotional discount.

Hierarchy Discount HI01

Condition type Hierarchy Discount HI01 can be used to maintain a pricing condition record for a discount that needs to apply to all lower hierarchy levels in a customer hierarchy.

Customer 2743 belongs to the northern office of the Miller group. As a result, the system assigns a discount of 8%.

In the SAP standard system, the access sequence is set in Customizing so that the discount is initiated at the lowest hierarchy level.

Discounts and Surcharges

Condition type Pallet Discount KP00 can be used to maintain a discount per pallet. You need to maintain in the material master for a material for which you want to use KP00, what the conversion rate is from the base unit of measure to the pallet unit of measure.

Note

Pallet discount KP00:
Partial and whole quantities of materials can be detected by the system and used in various pricing scenarios. You do not have to use only pallet as a unit of measure; you can apply this condition type to any unit of measure.
Other pallet discount types:
Other pallet discount types are variations of condition type KP00.

The used formulas and configuration settings can also be used for other units of measure in addition to pallets.

The pallet discount offers the customer a discount for whole units of measure only, such as a complete pallet. This is controlled by basic formula 22 in the pricing procedure. This formula only takes the number of complete pallets into account.

Incomplete Pallet Surcharge KP01

Condition type Incomplete Pallet Surcharge KP01 can be used to maintain a surcharge per incomplete pallet . The unit of measure for the pallet and the conversion rate for the base unit of measure to this pallet unit of measure also needs to be maintained for the material that uses it.

In incomplete pallet surcharge KP01, the customer pays a surcharge for an incomplete pallet. This is controlled in basic formula 24 in the pricing procedure. This formula tests the quantity for a fractional portion.

Mixed Pallet Discount KP02

Note

See the following video to learn about the various options for maintaining mixed pallet discounts, and surcharges for incomplete mixed pallets:

Condition Type DIFF

Some currencies need to be rounded to a specific number. Any rounding differences are calculated and made visible using condition type DIFF. This condition type is a group condition that is distributed among all the items according to value.

You can maintain a rounding unit in table T001R for each company code and currency in the SAP Customizing - IMG:ABAP Platform → General Settings → Currencies → Define rounding rules for currencies.

If the final amount in the order header differs from the rounding unit, the system rounds the amount up or down as specified.

Condition type DIFF determines the difference amount. This condition type is a group condition that is distributed among all the items according to value.

How to Use Condition Type DIFF

Customer Hierarchy Pricing

ExerciseStart Exercise

Log in to track your progress & complete quizzes