condition types in pricing

Former Member · ‎09-03-2007

Hiii everyone..... does anyone have a document explaining all the condition types in pricing ....if yes plss forward them to jimmy_ahuja@hotmail.com

Regards

maddy

Message was edited by:

Maddy

Former Member · ‎10-25-2007

Hi Maddy

COLUMNS IN PRICING PROCEDURE

16 columns - Define Pricing Procedure

• Select the pricing procedure which is the standard and copy it and create our own pricing procedure.

• Highlight it and double click the Control icon in the LHS screen.

• We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.

• The detail description of each column is given below.

Step:•

Number that determines the sequence of theconditionswithin a procedure.

• It indicates the position of the condition type in pricing procedure.

• Ex.: 10, 15 etc.

Counter:•

System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.

• Access number of the conditionswithin a step in the pricing procedure.

• During automatic pricing, the system takes into account the sequence specified by the counter.

Condition Type:

• It represents pricing element in pricing procedure as a base price, discount, freight and tax.

• The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.

• Ex.: PR00 - Price

K004 - Material Discount

K005 - Customer/Material Discount

K007 - Customer Discount.

Description:

• System copies description of condition type from its description (V/06).

From and To:

1. From:This can be used as a base to the condition type for calculating further value.

1. {}From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.

Manual:

• This indicator specifies whether the specific condition type can be determined manually during sales order processing.

• If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.

• For Base Price and Taxes, the entry should be automatic.

• For Discounts and Freights, The entry should be manual.

• If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.

• If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.

Mandatory:

• This indicator specifies that particular condition type is mandatory in the pricing procedure.

• If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.

• If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.

• Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.

• If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.

Statistical:•

This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.

• It is used only for information purposes only.

• This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).

• This is commonly used for condition types

o SKTO - Cash Discount

o VPRS - Cost (Moving average price/Standard Price).

Print:•

The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.

Subtotal:•

The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.

• Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.

• If the same fields are used to store different condition amounts, the system totals the individual amounts.

• These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.

Requirement:

• It is a routine that is written by an ABAP consultant according to the business requirement.

• By defining Requirement in condition technique we can restrict the access of condition type.

• To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).

• For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".

• This Requirement will ensure that these condition types will appear only during the billing document processing.

• If new Requirements are to be defined we follow the procedure given below.

o Go to T.Code: VOFM. - Maintain Requirements & Formulas

o Click on the "Requirements" in the top menu and then click on "pricing".

o We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.

o And we assign the application type like V - Sales/Distribution etc.

AltCty - Condition formula for alternative calculation type:•

It is again a Routine that is written by ABAP Consultant.

• It is an alternative formula for the condition type that can be used instead of standard formulas.

• For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.

• Ex.: 950 0 Profit Margin 11.

• So we assign 11 - Profit Margin.

• If new routines are to be defined we follow the procedure given below.

o Go to T.Code: VOFM. - Maintain Requirements & Formulas

•

o Click on the "Formulas" and then on the "Condition Values".

o We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.

o And we assign the application type.

AltCBV - Alternative formula for condition base value:

• Formula for determining the condition basis as an alternative to the standard.

• It is again a Routine that is written by ABAP Consultant.

• It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.

• Ex.: Freight - KF00.

• Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.

• In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.

• During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.

• Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.

AcyKy - Account Key/ Accrls - Accruals:•

The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.

• In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.

o ERB Rebate sales deduct.

o ERF Freight revenue

o ERL Revenue

o ERS Sales deductions

o ERU Rebate accruals

• For Ex.,

o For all Price condition types like PR00 etc. we assign ERL - Revenue.

o For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.

o For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.

o For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.

• This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.

• This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.

1. STEP

2 CTRSTEP

3. CTYP

4. DISCRIPTION

5. FROM

6. TO

7. MAN

8. Mand

9. STAT

10. PRINT

11. REQUIREMENT

12. ALCTYP

13. ALBCTYP

14. ACKEYS

15. ACCRUALS

A. STEP

This indicates the number of step-in the procedure.

B. COUNTER

This is used to show a second ministep

C. CONDITION TYPE

This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.

D. DESCRIPTION

This forms the description of the condition type.

E. FROM

This is used to define the progression of the calculation and range of subtotals

F. TO

This is used to define the progression of the calculation and range of subtotals

G. MANUAL

This function enables to allow the condition type to be entered manually also apart from automatic pickup.

H. MANDATORY

This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.

I. STATISTICS

This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price

J. PRINT

The activation of this function will enable the printing of the values and conditions to the document.

K. SUBTOTAL

A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also

L. REQUIRMENT KEY

This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.

M. ALTERNATE CALCULATION TYPE

This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.

N. ALTERNATE CONDITION BASE VALUE.

The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.

O. ACCOUNTS KEY

The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.

PR00- ERL

K007/KA00- ERS.

KF00- ERF………….& so On.

P. ACCRUAL KEY.

The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.

Reward if useful to u

Message was edited by:

narendran vajravelu

Former Member · ‎09-17-2007

Hi,

I don't think you need to know all condition types. Instead you should know about the various fields which are there in a particualr condition type. In V/06 when you define a new condition type:

1. Access sequence - Used for condition types which are kept mandatory in the pricing procedure. The access sequence searches for the condition record as per the key combination maintained in the condition table assigned to the access sequence.

2. Condition class - Preliminary structuring of condition types e.g. in surchages and discounts or prices.

A grouping that lets you control each condition type differently.

For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.

3. Calculation type - Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.

The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record.

4. Condition category - A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).

5. Rounding rule - The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.

6. Structured condition - controls whether the condition type should be a duplicated condition or a cumulated condition.

This control is only helpful when you use bill of materials or configurable materials.

Aduplicated condition is duplicated into all assigned items.

A cumulated condition contains the net value of all assigned items.

7. Group condition - Indicates whether the system calculates the basis for the scale value from more than one item in the document.

Use

For a group condition to be effective, the items must belong to a group. You can freely define the group to meet the needs of your own organization. The items can, for example, all belong to the same material group.

8. Routine number for creating group key - Identifies a routine that calculates the basis for the scale value when a group condition occurs in pricing.

Example

You can specify a routine, for example, that totals the value of all items in a document in order to determine the basis for a discount.

9. Rounding difference comparison - Indicator that controls whether rounding difference is settled for group conditions with a group key routine.

If the indicator is set, the system compares the condition value at header level with the total of the condition values at item level. The difference is then added to the largest item.

10. manual entries - Indicator which controls the priority within a condition type between a condition entered manually and a condition automatically determined by the system. Here you can specify whether the condition type can be processed only manually or not

11. Header Condition - If this condition is marked as a header condition, it is possible to enter the condition type in the header condition screen. Checks for changing the condition manually are unaffected by this.

12. Item condition - Mark this field if the conditions of this type are allowed to be entered in the document items. The condition is then only valid for the particular item in which it is entered.

13. Delete - Indicator that controls whether the condition type may be deleted from the document.

14. Amount/percent - Specifies whether the amout or percentage for the condition type can be changed during document processing.

15. Value - Specifies whether the value of the condition type can be changed during document processing.

16. Quantity relation - Specifies whether the conversion factors for the units of measure in conditions of this type can be changed during document processing.

17. Calculation type - Specifies whether the calculation type for the condition type can be changed during document processing.

18. Valid from - Proposed value from when the record of the condition type is valid.

19. Valid to - Proposed value for how long a condition should remain valid.

20. Reference condition type - A condition type which can be used as a reference so that you only have to create condition records once for condition types that are very similar.

21. Reference application - Application, that can be used to refer to condition records from other applications.

Use

You only have to create condition records once for condition types that are very similar. You can also refer to condition records from other applications.

You will find further information on the ReferencCondType field in the documentation.

22. Pricing procedure - Determines which condition types can be used in a document and in which sequence they appear.

Use

The system uses the pricing procedure that you enter here to control the use of condition supplements in records of this condition type. You can apply the discounts that are defined in the pricing procedure as condition supplements during pricing.

23. Delete from database - You can use this indicator to control how the system operates when deleting condition records.

24. Condition index - Specifies whether the system updates one or more condition indices when maintaining condition records.

Use

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

25. Condition update - 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.

26. Scale basis - Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume.

27. Scale formula - Formula for determining the scale base value.

28. Check value - Indicates whether the scale rates must be entered in ascending or descending order.

29. Unit of measurement - Unit of measure that the system uses to determine scales when you use group conditions

30. Scale type - Indicator that controls the validity of the scale value or percentage:

From a certain quantity or value (base scale)

Up to a certain quantity or value (to-scale)

Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.

31. Currency conversion - Controls the currency conversion where the currency in the condition record varies with the document currency.

32. Accruals - Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.

33. Invoice list conditions - Marks the condition type as relevant for internal costing.

34. Inter company billing condition - Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).

35. Service charge settlement(trading contract) - Indicates that the trading contract conditions should be calculated using the vendor billing document.

36. Quantity conversion - This field controls the quantity conversion during determination of the condition basis.

The field is only relevant for calculation rule 'C' (quantity- dependent.

37. Condition exclusion - Indicates whether the system automatically excludes the discounts that are proposed during pricing.

38. Pricing date - Enter the identification code for the date to which a condition of this type is to be calculated in the sales document. If you do not enter an identification code, the pricing date or the date of services rendered is used.

39. Relevance for account assignment - Controls how account assignment is performed for conditions of this type.

40. Text determination procedure - Identifies a group of text types that you can use in, for example, a sales document header. The text procedure also determines the sequence in which the text types appear in the document.

41. Text ID - Specifies which text ID appears in Text Edit Control.

The text ID defines the different types of texts that belong to a text object.

If you understand the control of each field then you will automatically understand the different condition types and how they behave in the sales documents

Reward points if solution helps.

Regards,

Allabaqsh G. Patil

Former Member · ‎09-17-2007

Hi Sheahgiri,

Can you pl mail me the document to srikkanth0701@rediffmail.com.

Thanks

Former Member · ‎09-03-2007

Hi

Sent mail reward If helps

Former Member · ‎09-03-2007

Hi,

I will send to your mail id but no one have all condition types documents.By referring one condition type we have to understand remaining condition types.

condition types in pricing

Accepted Solutions (0)

Answers (5)

Answers (5)

Rounding component values in a production order

A report object, section or area with this name al...

Re: License Type Configuration Vs. Item Category

Re: Issue saving approved document drafts as docum...

Re: Clearing stock from 921 TRANSFER