Pricing routines.

[Former Member]

Hi Gurus,

Can any one give me brief idea on Pricing Routines & their details.

I have a requiremnet in which I want certain price condition to be applied to only confimed line item.

I wish to use a pricing routine . Please let me know the brief logic and User exit.

Regards

Ajoy Baneerjee

[Former Member · Accepted solution]

Hi there,

When you mean a certain price cindition, do you mean a particular condition type to apply only when item is confirmed?

If that is the case, tehn put a logic in the requirement routine in that condition type. Put a logic that If the schedule lines of that item are confirmed, only then the condition type should apply.

Go to VOFM --> Reuirements --> pricing. Select the required routine & put the logic there.

But if your requirement is to carry pricing for that item only for confirmed line items, tehn you need to put a cde in MV45AFZZ in the include that calls for pricing.

In that include put a code that for your sales org / sales order scenario, pricing is to be carried only when item is confirmed. If item confirmed only then system will call pricing include. Else it will skip.

But in this case 1ce the item is confirmed, you have to carry re-pricing for that material. This will involve a huge customized logic.

Regards,

Sivanand

[Former Member]

Hi,

Go through the following document,

CONDITION VALUE FORMULA 1: PROFIT MARGIN WITH REBATE

Formula '1' sets the value equal to the pricing subtotal '3' minus the cost of the line item.

Example:

A company offers rebate agreements to their customers that are paid out at the end of the year based on

cumulative sales. On a sales order, rebate agreement accruals show up as a statistical amount and do not affect

the net value of the line item. The company, however, would like to see the profit margin in the line item

reflect the expected rebate payments. In order to accomplish this, the user assigns the subtotal field '3' to the

relevant condition types in the pricing procedure so it's value equals the net value as well as the value of any

rebate accruals. The condition value formula '1' is then assigned to the u2018Profit Margin' line in the pricing

procedure. Note that subtotal '3' is just an example supplied by the system. Another subtotal could be used and

the user would then copy this formula and create a new one that uses the other subtotal value. If rebate

accruals should not be included in the profit margin calculation, the user would select condition value formula

'11'.

CONDITION VALUE FORMULA 2: NET VALUE

Formula '2' sets the value equal to net value that has been calculated so far for the item in the pricing

procedure. It contains the amount excluding taxes.

Example:

A company would like to show subtotals in their pricing screen that would represent the gross value, net

value, and net value 2. These are all value lines in the pricing procedure that do not correspond to a specific

condition type. To determine the value for these value lines, the user assigns the condition value formula '2'.

The system then shows in these subtotal lines the net value of the line item up until that point in the pricing

procedure.

CONDITION VALUE FORMULA 3: CASH DISCOUNT MINUS TAX

Formula '3' sets the value equal to the amount eligible for cash discount minus tax.

CONDITION VALUE FORMULA 4: NET VALUE PLUS TAX

Formula '4' sets the value equal to the net value plus tax. This can be assigned, for example, to a value line at

the end of the pricing procedure that should show the final value of the line item.

CONDITION VALUE FORMULA 5: PROFIT MARGIN DIALOGUE

Formula '5' provides an example of how a message can be displayed if the profit margin for a particular item

is below a predefined percentage. To use this feature, the user would copy formula '5' into a new formula and

assign the relevant percentage to the field MINDEST_PROZ.

CONDITION VALUE FORMULA 6: INITIAL PRICE

Formula '6' was delivered to support net price processing. For additional information on the use of this

formula along with examples, please refer to Note 80183.

CONDITION VALUE FORMULA 8: EXPECTED VALUE

Formula '8' provides an example of how the system can compare the customer expected value of a line item

with the net value computed by the system. If the system net value is not within a value range of 1 of the

customer expected value, than the item is blocked. Formula '8' was delivered along with the condition type

EDI2 for customer expected value. Users can copy this formula and specify their own value range tolerance in

the field MAXIMUM.

CONDITION VALUE FORMULA 9: EXPECTED PRICE

Formula '9' provides an example of how the system can compare the customer expected price of a line item

with the net price computed by the system. If the system net price is not within a value range of 0.05 of the

customer expected price, than the item is blocked. Formula '9' was delivered along with the condition type

EDI1 for customer expected price. Users can copy this formula and specify their own value range tolerance in

the field MAXIMUM.

CONDITION VALUE FORMULA 11: PROFIT MARGIN

Formula '11' computes the profit margin for a line item. This is done by subtracting the cost of the item from

the net value. This formula can be assigned to a value line at the end of a pricing procedure to show the profit

margin for the item.

CONDITION VALUE FORMULA 13: MINIMUM VALUE SURCHARGE

Formula '13' computes the applicable surcharge when the order value (before taxes) falls below the predefined

minimum order value. This formula was delivered with condition types AMIW (used to define the minimum

order value) and AMIZ (used to compute the surcharge if the minimum is not met). Within the pricing

procedure, formula '13' should be assigned to condition type AMIZ. In addition, the subtotal 'D' must be

assigned to condition type AMIW in the pricing procedure.

Example:

A company would like to define minimum order values for their customers. As an example, a minimum order

value of 200 USD is defined for Customer A. If Customer A places an order for anything less than 200 USD

(before taxes), the system should automatically compute a surcharge equal to the difference and apply it to the

order. To accomplish this, the user would configure pre-delivered condition types AMIW and AMIZ in their

pricing procedure as defined above and maintain a condition record for AMIW and Customer A equal to 200

USD.

CONDITION VALUE FORMULA 14: BEST PRICE

Formula '14' can be used to select the best price in a pricing procedure when more than one condition type to

determine the price has been configured.

Example:

A company quotes prices based on weight as well as number of cases. In the pricing procedure, they have

maintained two condition types for the price. Condition type ZWGT is listed first and computes the price

based on the weight. Condition type ZCSE is listed second and computes the price based on the number of

cases. When pricing is done, the system should automatically select the best price for the customer. To

accomplish this, the user assigns condition value formula '14' to condition type ZCSE in the pricing

procedure. Using this formula, the system compares the two. If the case price is more expensive, then the

ZCSE condition line is set to inactive. If the case price is less expensive, then the ZCSE condition line

remains active causing the ZWGT condition line to become inactive (active subsequent price in the pricing

procedure).

CONDITION VALUE FORMULA 15: MINIMUM PRICE

Formula '15' was delivered along with condition type PMIN to define minimum prices.

Example:

A company has defined minimum prices for materials. When a material is sold, it should not be sold for a

price below the predefined minimum price. When pricing is done for a sales document line item, if the net

price of the item falls below the minimum, the system should automatically compute a surcharge to bring the

price up to the minimum price. To accomplish this, the user would define the minimum prices using the

condition type PMIN. PMIN would be defined in the pricing procedure and condition value formula '15'

would be assigned. Using the formula, the system compares the minimum price with the net price calculated

to that point in the pricing procedure. If the minimum price is not met, the system computes the necessary

surcharge and assigns it to the PMIN condition line.

CONDITION VALUE FORMULA 16: ROUNDING THE TOTAL

Formula '16' was delivered along with condition type DIFF to support the rounding unit rules that can be

defined in T001R for company code / currency combinations. Condition type DIFF was delivered to perform

the rounding at the end of the pricing procedure with the total value. Using formula '16', the system computes

the rounded value and assigns the difference to the condition type DIFF.

CONDITION VALUE FORMULA 17: ROUNDING AS PER T001R

Formula '17' was delivered so that a condition value could be rounded off according to the rounding unit rules

that can be defined in T001R for company code / currency combinations. When formula '17' is assigned to a

condition type, the condition value will always be rounded using T001R.

CONDITION VALUE FORMULA 18: PERCENT CONTRIBUTION MARGIN

Formula '18' computes the percent contribution margin for the line item comparing the cost and net value of

the item. This formula can be assigned to a value line at the end of a pricing procedure to show the percent

contribution margin for the item.

CONDITION VALUE FORMULA 19: P-VARIANT RITTER

Formula u201819u2019 is used to support the calculation of the net price. For additional information on the use of this

formula along with examples, please refer to Note 80183.

CONDITION VALUE FORMULA 20: P VARIANTS DISCOUNT

Formula u201820u2019 is used to support the calculation of the net price. For additional information on the use of this

formula along with examples, please refer to Note 80183.

CONDITION VALUE FORMULA 25: KZWI1 MINUS TAX

Formula '25' computes the value of the condition line to be equal to the value in subtotal '1' minus tax.

Formula '25' was delivered along with condition type NETW to compute the value of the goods when tax is

part of the price. Reference standard delivered pricing procedure RVAB01 'Tax included in price'.

CONDITION VALUE FORMULA 36: CUMULATION CONDITION

Formula '36' enables the user to display the total of the net values of an item and all the sub-items belonging to

that item. This formula was delivered along with condition type KUMU. This condition type can be assigned

to the pricing procedure along with formula '36' to display cumulative values when main and sub-items are

used.

CONDITION VALUE FORMULA 37: TAX EXEMPTION LICENSE

Formula '37' was delivered to support tax exemption licenses in Italy. This formula should be assigned to the

condition type for tax exemption licenses in Italy (R/3 delivered condition type LCIT) in the pricing

procedure. For additional information on tax exemption licenses, please refer to Note 72040.

CONDITION VALUE FORMULA 38: EXCLUSION WITH VALUE ZERO

Formula '38' sets the value of the field AUSSCHLUSSWERTNULL to 'X'. This formula was delivered in

order to support condition exclusion where conditions with a value of zero should be considered in the

exclusion. For additional information, refer to Note 39641.

Example:

A company has two condition types in their pricing procedure that represent surcharges. A condition

exclusion group has been defined with these two condition types indicating that the lowest of the two should

be applied. In some cases, one of the surcharges may be zero. This could be due to a condition record that is

found or a manual entry. In order to have the system consider zero as the lowest surcharge for the customer,

condition value formula '38' must be assigned to one of the condition types in the pricing procedure.

CONDITION VALUE FORMULA 47: VAT FRANCE

Formula u201847u2019 was delivered to support tax exemption licenses in France. This formula should be assigned to

the condition type for tax exemption licenses in France (R/3 delivered condition type LCFR) in the pricing

procedure to support this functionality. For additional information on tax exemption licenses, please refer to

Note 72040.

CONDITION VALUE FORMULA 48: CHECK DOWN PAYMENTS

Formula '48' was delivered to ensure that the down payment amount the user offsets in a billing document

does not exceed the actual down payment value. Condition value formula '48' is assigned to the condition type

in the pricing procedure representing down payments (R/3 delivered condition type AZWR). Down payment

functionality was delivered with R/3 Release 4.0.

CONDITION VALUE FORMULA 61: PREFERENCE MAX VALUE

Condition value formula '61' was delivered to solve a field overflow problem that can occur when working

with preference determination. This can occur due to the quantity dependency. Formula '61' is assigned to the

preference condition type in the pricing procedure (R/3 delivered condition type PREF). Also reference

condition base value formula '61'

For additional information, please reference Note 92321.

6. Structure of Group Key

A structure of group key formula can be used to influence the basis the system uses when reading the scale of

a group condition. Group conditions are used to cumulate quantities from more than one sales document line

item to read pricing scales. For example, when pricing a particular sales document line item, the user would

like the system to not just consider the quantity of the current line item, but the sum of the quantities of all line

items that share the same material pricing group as the current line item. The formula is assigned to a group

condition type in customizing. When looking at the code for the standard delivered structure of group key

formulas or when writing your own, XVAKEY is the field name that the structure of the group key should be

assigned to. Following is a description of the structure of group key formulas delivered in the standard system.

Regards,

Swamy H P