5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding
Key Takeaways
HM00 lets you enter the whole order value manually; the system distributes it to the items in proportion to their previous net values and redetermines taxes.
PN00 lets you enter an item's net price manually, and the system deactivates the original conditions of the item.
PMIN determines the difference when a material's minimum price is not reached; AMIW and AMIZ handle a minimum order value and the surcharge for falling below it.
Customer hierarchy pricing grants agreements made at a node to all customers below it; the standard access sequence starts at the lowest hierarchy level (condition type HI01).
KP00 grants a discount for complete pallets only (formula 22), KP01 charges a surcharge for incomplete pallets (formula 24), and DIFF rounds the document total using the rounding units in table T001R.
Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding
The standard pricing procedure contains more than a price, a few discounts, and tax. The S46200 unit Identifying Condition Types (195 minutes) introduces condition types that solve specific business requirements with standard functions. Knowing them avoids unnecessary custom condition types and is useful when an assessment task describes a requirement such as "the customer has agreed a total order value" or "orders below a minimum value carry a surcharge".
Manual Pricing: HM00 and PN00
Sometimes a customer negotiates a total price for the whole order or a net price for an item, regardless of the normal price and discounts.
HM00 - Order value (header condition)
- Used when an entire sales order value has been agreed with the customer and must be entered manually.
- The system distributes the new order value proportionally between the items, based on each item's previous net value.
- The system redetermines the taxes for each item.
PN00 - Net price (item condition)
- Lets you specify the net price of an item manually.
- The system deactivates the original conditions of the item, so the entered value is the net price.
The course also mentions the older method of achieving net pricing: set the condition exclusion indicator on condition type PR00 and use requirement 2 in the pricing procedure, so that the discounts behind it are excluded.
Minimum Prices and Minimum Order Values
PMIN - Minimum price: you can create a minimum price for a material with condition type PMIN. If the minimum price is not reached during pricing (for example, because large discounts were applied), the system determines the difference with PMIN and adds it, so the item never falls below the minimum.
AMIW and AMIZ - Minimum order value: a company can define a minimum value for an entire order.
AMIW(minimum order value) holds the agreed minimum value for the order and serves as a reference value in the pricing procedure.AMIZ(minimum value surcharge) calculates the surcharge: the difference between the minimum order value and the actual net value of the order, if the order is below the minimum.
Example: the minimum order value is 200 EUR and an order has a net value of 170 EUR. AMIZ adds a surcharge of 30 EUR, so the customer pays at least the minimum. An order with a net value of 250 EUR gets no surcharge.
Graduated (Interval) Prices: PR02
Condition records with interval scales are possible if the condition type is set to scale type D in Customizing. In the standard system, PR02 uses this scale type, while PR00 uses a normal scale. Both have condition class B (prices) and PR02 comes after PR00 in the pricing procedure. Because only one price can be effective at a time, the price at the highest level (later in the procedure) is used: PR00 becomes inactive automatically when a PR02 record exists. Two rules from the course:
- Interval scales cannot be used for group conditions.
- Make the last scale level a number larger than will ever occur, so the last part of an item quantity is always covered.
Customer Hierarchy Pricing
Customer hierarchies reflect the structure of customer organizations, such as multilevel buying groups, cooperatives, or retail chains. They are used in order processing and billing for pricing and statistics, and they are valid for a period of time. A hierarchy consists of nodes. To create one:
- Create master records for each node.
- Assign the nodes to each other.
- Assign the customer master records to the relevant nodes.
If you move a node, the system automatically reassigns all subordinate nodes and customer records.
You can assign price or rebate agreements to a high-level node; they are then valid for all customers below it. Pricing condition records can be created for each node that is marked as relevant for pricing. If nodes in the hierarchy path of a sales order carry pricing information, the system considers them automatically according to the access sequence. In the standard system, the access sequence is set so that the discount is determined at the lowest hierarchy level first.
Example: The Miller Buying Group
The course example is the multilevel buying group Miller. The head office is the top node, with southern, northern, central, and northeastern regional offices below it.
- A discount valid for all regions is created for the head office node.
- An exclusive promotional discount is created for the northern node.
- An order from customer 2742 (not in the northern region) receives the cross-regional head-office discount.
- Orders from customers 2743 and 2744, which belong to the northern office, receive the northern promotional discount, because the access sequence finds the lowest node first. With the hierarchy discount condition type
HI01, customer 2743 gets 8%.
Pallet Discounts and Surcharges
Pallet conditions use formulas in the pricing procedure to evaluate whole and partial units of measure. Although they are named after pallets, they work with any unit of measure.
| Condition Type | Purpose | Formula in the Pricing Procedure |
|---|---|---|
KP00 | Pallet discount for complete pallets only | Base formula 22 counts only complete pallets |
KP01 | Surcharge for an incomplete pallet | Base formula 24 tests the quantity for a fractional portion |
KP02 | Mixed pallet discount across several items that together fill pallets | Group condition across items |
A surcharge for incomplete mixed pallets complements KP02.
Example with a pallet of 50 cartons and an order of 120 cartons: KP00 grants the discount for 2 complete pallets (100 cartons), and KP01 charges the surcharge because 20 cartons form an incomplete pallet.
Rounding: Condition Type DIFF
Some companies round the final amount of an order, for example to 0.05 or to whole currency units. You maintain a rounding unit for each company code and currency in table T001R (Customizing: 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 it up or down. Condition type DIFF determines the difference amount; it is a group condition distributed among all items according to their value.
Example: with a rounding unit of 0.05 and a document total of 1,234.63, DIFF determines a rounding difference of +0.02 (to 1,234.65) or -0.03 (to 1,234.60), depending on the rounding rule maintained for the currency.
Summary Table
| Requirement | Standard Solution |
|---|---|
| Customer agreed a total order value | HM00 (header, distributed by net value, taxes redetermined) |
| Customer agreed an item net price | PN00 (original conditions deactivated) |
| Price must never fall below a minimum | PMIN |
| Orders below a minimum value carry a surcharge | AMIW + AMIZ |
| Price falls in steps by quantity interval | PR02 with scale type D |
| Buying group discounts by organization level | Customer hierarchy with HI01 |
| Discount for full pallets, surcharge for partial pallets | KP00, KP01, KP02 |
| Round the document total | DIFF with rounding units in T001R |
A customer has agreed a total value for an entire sales order. Which condition type is used, and how does the system process it?
PMIN; the system raises every item to the minimum price.
HM00; the value is split by the items' previous net values, and taxes are redetermined.
AMIZ; the system calculates a minimum value surcharge for the whole order.
PN00; the item net price is entered and all items receive the same net price.
A pallet holds 50 cartons and a customer orders 120 cartons. Pallet discount KP00 and incomplete pallet surcharge KP01 are in the pricing procedure. What is the result?
KP00 grants the discount for 2.4 pallets proportionally, and KP01 is not used.
KP00 grants the discount for 3 pallets because the quantity is rounded up.
Only KP01 applies, because the quantity is not a multiple of 50.
KP00 for 2 full pallets, plus a KP01 surcharge for the partial third pallet.
Where are the rounding units used by condition type DIFF maintained?
In the pricing procedure determination (OVKK)
In the condition record of DIFF for each customer
In table T001R for each company code and currency
In the sales document type
In a customer hierarchy, a discount exists at the head office node and a different discount at the regional node of the ordering customer. Which discount does the standard access sequence find first?
The regional node discount, because the search starts at the lowest level
The head office discount, because higher hierarchy nodes always have priority
Both discounts, which are added together
No discount, because hierarchy nodes cannot be relevant for pricing
Sections you finish are checked off in the contents.