3 Answers
-
Best AnswerPosted on Oct 31, 2007 at 04:40 AM
Hi Tarak
Condition types can be defined as follows:-
Price elements are represented in the SAP system byg condition types. Price elements can be, for example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in condition records.
You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.
You specify an access sequence in every condition type. Thus, you define which fields the SAP system checks when searching for a valid condition record.
<b>Note</b>
--> The pricing procedure groups all condition types together which the SAP system is to automatically take into account during pricing for a business transaction (see the section "Define and assign pricing procedures").
Remember that you can only specify manually in a document those condition types which are contained in the pricing procedure.
--> You can change the outcome of pricing in the sales document manually. You can limit options for changing a condition type in this IMG step.
<b>Recommendation</b>
=> If you define your own condition types, the key should start with the letter Z since SAP reserves these letters for that purpose in the standard system.
=> Do not change the condition types which are contained in the standard SAP R/3 System.
<b>Actions</b>
1. Check to what extent you can use the condition types contained in the standard SAP R/3 System.
2. Create new condition types by copying a similar conditions type and changing it according to your requirements. One reason for creating a new condition type is you may require a calculation rule for a discount which is not avaialable in the standard system.
Specify an alphanumeric key which can have up to 4 digits, and a textual description.
Specify an access sequence for the condition types. You do not need to specify an access sequence for header conditions.
3. Maintain the detail screen of the condition type.
You can also assign a reference condition type if the condition types you are working with are similar. Then you will only have to maintain condition records for the reference condition type.
In addition, you can define the upper and lower limits for the value of a condition at condition type level. This way, you limit the amounts or the scale values in the corresponding condition records.
<b>Checking settings</b>
You can use the SDCHECKT685A report to check the settings for the condition types. This is not a complete check but it does, for example, check the scale type setting for group conditions. For more information, read the report documentation.
<b>Pricing Procedure</b>
You define the pricing procedures in this step. In addition, you assign the pricing procedures to the transactions by defining the following dependencies:
==> Customer
==> Sales document type
==> Sales area
In the pricing procedure, you define which condition types should be taken into account and in which sequence. During pricing, the SAP System automatically determines which pricing procedure is valid for a business transaction and it takes the condition types contained in it into account one after the other.
The determination of the procedure depends on the following factors:
<b>Customer determination procedure</b>
You specify the customer determination procedure in the customer master record for each sales area.
<b>Document pricing procedure</b>
You specify the document pricing procedure for each sales document type and billing type.
To determine the procedure, you allocate the customer determination procedure and the document pricing procedure to a pricing procedure within a sales area.
<b>SAP Recommendation</b>
=> Define your own pricing procedures which contain only those condition types which you use. Otherwise, the system makes unneccessary accesses to conditions.
=> Do not change the pricing procedures contained in the standard SAP R/3 System.
<b>Actions</b>
1. Create new pricing procedures by copying a similar pricing procedure.
--> Specify a key with up to 6 characters and a description.
--> For a procedure, specify the condition types in the sequence of their usage.
Maintain the lines of the pricing procedure
2. Afterwards define the customer determination procedures for determining the procedure.
3. Define the document pricing procedures for determining the procedure.
4. Assign the procedure to the sales document types and billing types.
5. To determine the procedure, define the allowed combinations of:
=> Sales area
=> Customer determination procedure
=> Document pricing procedure
=> Pricing procedure
<b>Check settings</b>
You can check the settings for your pricing procedures. This is not a complete check. It mainly checks the requirements and calculation formulas for standard condition types. Refer to the report documentation for more information
Thanks
G. Lakshmipathi
Add a comment
-
Former MemberPosted on Oct 30, 2007 at 04:45 PMHi Tarak,
<b>Condition Types</b>
A condition type serves to differentiate between prices in the system. Price elements are represented in the SAP system by condition types. You can define a separate condition type for each type of price, surcharge or discount that may arise in your business transactions. The condition type defines, for example, a discount as a fixed amount or as a percentage.
<b>Configuration</b>
SPRO -> Sales & Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Condition Types
A few standard condition types provided by SAP are
BO01
Mat/Group Rebate
BO02
Material Rebate
BO03
Customer Rebate
BO04
Hierarchy Rebate
BO05
Hierarchy rebate/mat
EK01
Actual Costs
EK02
Calculated costs
HA00
Percentage Discount
HB00
Discount (Value)
HD00
Freight
PR00
Price
PR01
Price incl.Sales Tax
VPRS
Cost
<b>Example</b>
A customer comes to a retailer, say for a Television, inquires about the price of a particular model. Now the retailer would have the basic price of the product to which the Freight or Transport charges would be added, the discount would be deducted (if any) and finally add the tax value.
Consider the above example and try to create your pricing procedure. Keep it simple till you understand the concepts.
Hope it had helped you. Do reward if you had felt the same.
Regards
Nadarajah Pratheb
Add a comment
-
Former MemberPosted on Oct 30, 2007 at 04:43 PM
hi
Condition Types
Use
A condition type is a representation in the system of some aspect of your daily pricing activities. For example, you can define a different condition type for each kind of price, discount or surcharge that occurs in your business transactions.
Example of a Condition Type
You define the condition type for a special material discount. You specify that the system calculates the discount as an amount (for example, a discount of USD 1 per sales unit). Alternatively, you can specify that the system calculates the discount as a percentage (for example: a 2% discount for orders over 1,000 units). If you want to use both possibilities, you must define two separate condition types. The following figure illustrates how condition types can be used during pricing in a sales document.
In the example in the preceding figure, two discounts apply to the item in the sales order. The first discount is a percentage discount based on the quantity ordered. The second discount is a fixed discount based on the total weight of the item.
You determine the calculation type for a condition type in Customizing. This determines how the system calculates prices, discounts and surcharges for a condition. When setting up condition records, you can enter a different calculation type than the one in Customizing. At present all available calculation types are permitted. The field ‘Calculation type’ can however not be accessed if this field is left empty. After the data release has been printed, if the field has not been completed manually, the proposal is automatically taken from Customizing. After this it is no longer possible to make manual changes.
If you use different calculation types for what are otherwise the same conditions (for example, percentage, as a fixed amount or quantity-dependent), you do not have to define different condition types in Customizing. You can set a different calculation type when maintaining the individual condition records.
Condition Types in the Standard R/3 System
The standard system includes, among many others, the following predefined condition types:
Condition type
Description
PR00
Price
K004
Material discount
K005
Customer-specific material discount
K007
Customer discount
K020
Price group discount
KF00
Freight surcharge (by item)
UTX1
State tax
UTX2
County tax
UTX3
City tax
Creating and Maintaining Condition Types
You can change and maintain condition types provided in the standard version of the SAP R/3 System or you can create new condition types to suit the needs of your own organization. You create and maintain condition types in Customizing.
To reach the condition type screen from the initial Customizing screen for Sales and Distribution:
Basic Functions ® Pricing ® Pricing Control ® Define condition types.
A dialog-box appears, listing the transaction options. Select the corresponding transaction for defining the condition types.
In the Conditions: Condition Types view, you can change existing condition types or create new ones.
Condition Types:
The condition type determines the category of a condition and how it is used.
The calculation type and the scale base type can be controlled for each condition type.
For Example: Scale for Condition Type PROO1 pieces 800 uni
10 pieces 750 uni
100 pieces 700 uni
Possible scale base types Possible calculation types
Value Percentage from an initial value Fixed amount
Quantity Amount per unit of measure
Weight Amount per unit of weight
Volumes Amount per unit of volume
Time period Quantity per unit of time
Each condition type can be set as an automatic surcharge, discount or either.
Condition types: A calculation or formula used for a component of pricing.
Header Condition:
Conditions can also be entered at the document header level. These are known as header conditions and are valid for all items.
These header conditions are automatically distributed among the items based on net value. The basis for distributing the header conditions can be changed in the pricing procedure by selecting the appropriate routine (e.g. weight, volumes) in the AltCBV (alternative formula for condition base value) field.
Incase of Condition type RB00, the value is copied to all line items. For Example: Condition Type RB00 is maintained with value $ 50 & there are 4 line items, then all 4 line items each will be populated with the value $ 50.
Incase of Condition type HB00, the value is distributed to all line items. For Example: Condition Type HB00 is maintained with value $ 50 & there are 4 line items, then the value $ 50 is divided in all 4 line items propotionately.
Add a comment
Add a comment