Applying Special Pricing Functions

Objective

After completing this lesson, you will be able to apply special pricing functions

Group Conditions

Note

See the following video to learn about the concept of group conditions:

Group Conditions with Varying Keys

If a condition is a group condition, it must be indicated as such in Customizing. The unit of measure for accumulation must also be given.

The formulas available in the Group Condition Routine field are as follows:

  • Formula 1 (complete document):

    This formula adds the quantities or values of all the line items in the sales document that have the same condition type as the group condition that is currently being processed.

  • Formula 2 (for all condition types):

    This formula adds the quantities or values of all the line items in the sales document, irrespective of which condition types have been applied.

  • Formula 3 (material group):

    This formula adds the quantities or values of all the line items in the sales document that have the same material pricing group (KONDM field) as the current sales document line item.

Exclusion of Conditions

Requirement 2 for a line in a pricing procedure means that the system checks whether a condition exclusion indicator is present in the found condition record. If so, the condition record is not used.

Conditions can be linked to requirements in the pricing procedure.

A requirement can evaluate the condition exclusion indicator and, if this indicator is set, ignore the condition. The condition exclusion indicator can be set in either the condition type or the condition record.

If the exclusion indicator is selected in a condition type or a condition record, all the condition types in the pricing procedure that meet the following criteria are ignored:

  • The condition types that follow the condition type for which the exclusion indicator is set

    The condition types prior to the condition type for which the exclusion indicator is set are not be affected by the exclusion.

  • The condition types to which a requirement routine is assigned to check for the exclusion indicator

It does not matter whether or not the requirement routine number is the same. In the pricing procedure, the PR00 condition type can have requirement 2 assigned to it and the K007 line can have requirement 6 assigned to it. If the exclusion indicator is set on PR00, K007 is excluded.

What is important is that the requirement routine has the logic that checks for the existence of the exclusion indicator and if this indicator is set, the condition is deactivated.

There is a difference between setting the exclusion indicator in the condition type and the condition record. If the indicator is set in the condition type, the exclusion applies to all the condition records of that type. If the indicator is set in the condition record, the exclusion applies only to that record; other condition records of the same type are not affected.

You can use condition exclusion to not allow other conditions if a particular condition is used. For example, if a certain type of discount is used, other discounts are not allowed.

You can create your own exclusion indicators and test for the existence of the indicator in the requirement routines.

Comparison of Condition Types

Note

See the following video to learn about determining the best price by using condition exclusion:

Comparison Methods for Condition Types

There are several comparison methods that can be used for comparing condition types.

Some of the comparison methods are as follows:

  • A:

    All conditions records in the first exclusion group are compared with each other and the condition with the best price is selected. All other conditions are deactivated.

  • B:

    All condition records for one condition type are compared with each other and the condition with the best price is selected. All other conditions are deactivated. This method can be used with condition type PR00.

  • C:

    The overall price of all condition records in the first exclusion group is compared with the overall price of all condition records in the second exclusion group. The group resulting in the best price is selected. The conditions of the other group are deactivated.

  • D:

    If a condition record is determined for the condition types of the first exclusion group, all the condition records for the second exclusion group are deactivated.

  • E:

    Method E is similar to method B, except that the worst (highest charge or lowest discount) price is selected.

  • F:

    Method F is similar to method C, except that the group with the worst overall price is selected. The conditions of the other group are deactivated.

  • L:

    Method L is similar to method A, except that the worst (highest charge or lowest discount) price is selected.

Condition Update

In a condition type you can maintain an X in the field Condition Update. This means that data will from then on be tracked inside of a condition record of this condition type Additional limits can be set for this data in the condition record: maximum condition value, maximum number of orders and maximum condition base value. If a limit is exceeded, the condition record won't be used anymore.

Values can be accumulated in condition records and tested against maximum limits. In this way, you can set a maximum condition value, condition base value, or number of orders for a condition.

You can display these cumulative values in the condition record.

Condition Supplements

Using a condition supplement means you can maintain condition values for condition types inside of the condition record of another condition type: the one to which the supplement condition types are assigned.

Condition supplements do not have their own access sequence. Condition supplements are found and maintained with the underlying condition record of condition type PR00.

You define the set of allowed condition supplements in Customizing for the main condition type. You can do this by assigning a different pricing procedure (PR0000) to the condition type that lists the required condition supplements.

Use Various Condition Type Attributes

ExerciseStart Exercise

Use Condition Exclusion for Groups of Conditions

ExerciseStart Exercise

Track Cumulative Values

ExerciseStart Exercise

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn