Hi,
You should know about the various fields which are there in a particular condition type. In V/06 when you define a new condition type:
<b>1. Access sequence</b> - 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.
<b>2. Condition class</b> - Preliminary structuring of condition types e.g. in surchages and discounts or prices.
A grouping that lets you control each condition type differently.
<b>For example</b>, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
<b>3. Calculation type</b> - 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.
<b>4. Condition category</b> - A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
<b>
5. Rounding rule</b> - The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
<b>6. Structured condition</b> - 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.
<b>7. Group condition</b> - Indicates whether the system calculates the basis for the scale value from more than one item in the document.
<b>Use</b>
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.
<b>8. Routine number for creating group key</b> - Identifies a routine that calculates the basis for the scale value when a group condition occurs in pricing.
<b>Example</b>
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.
<b>9. Rounding difference comparison</b> - 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.
<b>10. manual entries</b> - 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
<b>11. Header Condition</b> - 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.
<b>12. Item condition</b> - 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.
<b>13. Delete</b> - Indicator that controls whether the condition type may be deleted from the document.
<b>14. Amount/percent</b> - Specifies whether the amout or percentage for the condition type can be changed during document processing.
<b>15. Value</b> - Specifies whether the value of the condition type can be changed during document processing.
<b>16. Quantity relation</b> - Specifies whether the conversion factors for the units of measure in conditions of this type can be changed during document processing.
<b>17. Calculation type</b> - Specifies whether the calculation type for the condition type can be changed during document processing.
<b>18. Valid from</b> - Proposed value from when the record of the condition type is valid.
<b>19. Valid to</b> - Proposed value for how long a condition should remain valid.
<b>20. Reference condition type</b> - 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.
<b>21. Reference application</b> - Application, that can be used to refer to condition records from other applications.
<b>Use</b>
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.
<b>22. Pricing procedure</b> - Determines which condition types can be used in a document and in which sequence they appear.
<b>Use</b>
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.
<b>23. Delete from database</b> - You can use this indicator to control how the system operates when deleting condition records.
<b>24. 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>25. Condition update</b> - Controls whether limit values are relevant for pricing.
<b>E.g.:</b> 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.
<b>26. Scale basis</b> - Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume.
<b>
27. Scale formula</b> - Formula for determining the scale base value.
<b>28. Check value</b> - Indicates whether the scale rates must be entered in ascending or descending order.
<b>29. Unit of measurement</b> - Unit of measure that the system uses to determine scales when you use group conditions
<b>30. Scale type</b> - 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.
<b>31. Currency conversion</b> - Controls the currency conversion where the currency in the condition record varies with the document currency.
<b>32. Accruals</b> - Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
<b>
33. Invoice list conditions</b> - Marks the condition type as relevant for internal costing.
<b>34. Inter company billing condition</b> - Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
<b>35. Service charge settlement(trading contract)</b> - Indicates that the trading contract conditions should be calculated using the vendor billing document.
<b>36. Quantity conversion</b> - This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
<b>37. Condition exclusion</b> - Indicates whether the system automatically excludes the discounts that are proposed during pricing.
<b>
38. Pricing date</b> - 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.
<b>39. Relevance for account assignment</b> - Controls how account assignment is performed for conditions of this type.
<b>40. Text determination procedure</b> - 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.
<b>41. Text ID</b> - Specifies which text ID appears in Text Edit Control.
The text ID defines the different types of texts that belong to a text object.
For the respective fields press <b>"F4"</b> and you will see the various options. Select those and try it out yourself by creating the sales order and see the effects. It will help you a lot. 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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.