pricing question

[Former Member]

Hi gurus,

Pls answer few of my pricing questions:

1.what is the difference between EK01 and EK02 condition type.

2.what is the difference between SKTO and SKTV

3.what is condition index and condition update

4.what is the use of exclusive field indicator in access sequence,condition type,and condition record

thanks in advance

with regards

Asif

[Former Member]

Hi,

1.Tecnicaly it is same but having different useges

2. Same as above

3. Condition index is list of condition and condition update is you can make the use of a particular condition record in the document dependent on a specified total value.

4. Exclusive is system will seek the condition record from specific to general if exclusive it will take only on periority

Points if helpfull

[Former Member]

Hi,

<b>1. Answer:</b>

<b>EK01:</b> The result of unit costing is issued to the first position on the conditions screen for the item & the value can be used as a basis for price determination.

<b>EK02:</b> The result of unit costing is simply a statistical value which can be compared with the price.

<b><b>2. Answer:</b>

SKTO:</b> Cash discount condition which is not used as group condition

<b>SKTV:</b> Cash discount condition which is used as group condition for various items in sales order.

<b>3. Answer:</b>

<b>Condition index:</b>

Specifies whether the system updates one or more condition indices when maintaining condition records.

<b>Use</b>

This makes it possible to list or maintain condition records indepently of condition type and condition table, for example.

<b>Condition update:</b>

Controls whether limit values are relevant for pricing.

E.g.: you can make the use of a particular condition record in the document dependent on a specified total value. This total value can be specified in the condition record which is maintained in VK11 additional data.

<b>4. Answer:</b>

<b>For access sequence -</b> Suppose you have 2 tables assigned to the access sequence. Record has been maintained as per both the key combination of the condition tables. When you click on the exclusive indicator then the system will stop searching for condition record when it finds the first record. That means if it finds record for first key combination then it will not search for condition record of 2nd key combination.

<b>For condition type:

<b>Condition exclusion indicator</b>

Indicates whether the system automatically excludes the discounts that are proposed during pricing.

<b>Use</b>

You can set this indicator in two ways:

1.For a particular condition record (the field appears on the Details screen)

2.For all records of a particular condition type (the field appears on the screen where you define the condition type)

<b>Note</b>

If you set the indicator to exclude conditions, there are several things to consider:

1.The system will still take into account any condition supplements that are part of the condition record for the price (condition type PR00, for example)

2.You can allow for exceptions where you want to include discounts in spite of the condition exclusion indicator (for a particular discount condition you can specify a requirement that applies the discount ONLY when the indicator is set)

<b>Condition record:</b>

Same is the case with the condition record like the condition type explained above.

Reward points if solution helps.

Regards,

Allabaqsh G. Patil

[Former Member]

EK01 :

If you use this condition type, the result of unit costing is issued to the first position on the conditions screen for the item. The value can be used as a basis for price determination.

EK02:

If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price.

Please note the following points :

1) The condition type must have condition category 'Q' (costing).

2) The condition type must agree with the condition type defined for unit costing in the pricing procedure.

2.Skto is before tax sktv is after tax calculation

4.Exclusive indicator if once find the suitable recored it will stop further surching of condition record

[Former Member]

4) if you check the exculsive feild in access sqence, it dont allow to go down the records, it stops where the condition record found.

3) Condition update is controlled by the condition type in setting Customizing for Sales-Pricing Condition Types (Tcode V/06). If you set the condition update for a particular condition type, the system subsequently updates the corresponding condition records whenever you process relevant sales and billing documents.

Condition update provides the basis for the following pricing functions:

Maximum Value

Maximum quantity

Maximum Number of Sales Orders

Ramki

[Former Member]

hi,

EK01

1)EK01 can be used as a basis for determining a price for the make-to-order item.

2) EK02 is a statistical condition which can used instead of VPRS to calculate the profit margin for the assembly item.

3)Condition type EK01 is mainly used for cost-plus contracts in which the sales price depends on the expected costs.

4)Condition type EK01 is selected for sales document type TA (standard order). This means that the value from the cost estimate goes directly into pricing. A surcharge is calculated from this value and the net value for the sales order item is calculated.

EK01 :

If you use this condition type, the result of unit costing is issued to the first position on the conditions screen for the item. The value can be used as a basis for price determination.

EK02:

If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price.

Please note the following points :

1) The condition type must have condition category 'Q' (costing).

2) The condition type must agree with the condition type defined for unit costing in the pricing procedure.

EK02 is used for calculating the magin in line item of order while in case price is based on cost + markup for example then EK01 is used

You can copy the results of sales order costing to the SD conditions. Copying can be carried out:

as a basis for pricing :

If you want to use sales order costing as a basis for pricing in SD, you can use the standard SAP condition type EK01.

Condition Index:

Condition Indices are used to display, change and create condition records with reference. This transaction can include condition records with several condition types and tables. For example, you can use a condition index if you want to see all condition records that apply to a particular product regardless of whether the records are prices or discounts. In this case, you can use one of the standard condition indexes. Or you may want to see a list of condition records that contain a particular sales deal and a material from a user-specified list of products. To display this information, you can create your own condition index.

Creating a condition index is similar to creating a condition table. In Customizing for Sales, you select the combination of fields that you want in the index key. The system automatically proposes a list of permitted fields to choose from. The fields you specify for the key can have a maximum combined length of 100 characters.

Condition Update:

Condition Update is used to track the cumulative values. Special offers and discounts to customers are frequently offered as part of a sales promotion based on accumulated sales order data. For example, when your customers place orders for a new product, you may offer them an introductory allowance up to a specified total value (for example, up to Rs. 5,000). As a customer places orders for the new product, the system must be able to keep track of the cumulative discount total.

rewards if helpful

regards,

Arun prasad