What Is The Condition Technique In SD Pricing?

For the pricing to be automatically determines in the sales document, we have to make all the following customizing settings.

The pricing is based on “condition technique”. Condition technique comprises of 

1.  Condition Tables 
2.  Access Sequence 
3.  Condition Type 
4.  Pricing Procedure.

Condition Tables

Condition table contains the key fields for maintaining the condition records i.e. condition records of a condition type will be stored in condition tables.  Depending on the sales requirement of the client we can have any field as a key field in the condition table.  

One condition type can have multiple condition tables and if required one condition table can be used for multiple condition types.

Defining condition tables

Tcode: SPRO 
- Sales and distribution 
- Basic functions 
- Pricing 
- Pricing control 
- Define condition tables 
- Create condition tables

Specify a condition table number which must be between 501 and 999

From the field catalogue which contains all the available fields select the required key fields.

While maintaining condition records in order to set the validity period we have to get the fields “valid on” and “valid to”. For this here we need to check the field “with validity period”

Select the button “Technical view”. Here fields which are marked as key appears at key level and the fields marked as footer field appears at footer level while maintaining the condition record.

Select the icon “Generate”.

Select the button “Local object” for saving the Table.

Use of Exclusion Group Customizing to Exclude Conditions

How to configure pricing procedure to choose only one among the different condition type?

ECC 6 - Exclusion group Customizing is in the following IMG path (transaction SPRO):

Sales and Distribution > Basic Functions > Pricing > Condition Exclusion > Condition Exclusion for Groups of Conditions Carry out the following steps:

a) Define condition exclusion groups: 
First create one or more exclusion groups, for example:

• G001 Discount group 1
• G002 Discount group 2

This data is stored in the T684 database table.

b) Assign condition types to the exclusion groups:

Then the required condition types are assigned to the exclusion groups, for example:

• G001 Discount Group 1 ZD01 Discount 1
• G001 Discount Group 1 ZD02 Discount 2
• G002 Discount Group 2 ZD03 Discount 3
• G002 Discount Group 2 ZD04 Discount 4

This data is stored in the T684G database table.

c) Maintain condition exclusion for pricing procedures:

Finally, define the required exclusion rules for each pricing procedure. In this case, you can create exclusions in accordance with the following predefined rules (KAUVF field):

- 'A' - Selection of the most favorable condition type within a condition exclusion group 
- 'B' - Selection of the most favorable condition record of a condition type if several condition records exist (for example, selection under various condition records of the condition type PR00) 
- 'C' - Selection of the most favorable of the two condition exclusion groups (in this case, all of the condition types of the two groups are cumulated and the totals are compared with each other). 
- 'D' - "Exclusive" procedure: If any of the condition types of the first group exists on the item, all of the condition types of the second exclusion group are excluded. 
- 'E' - Similar to 'B', but with the most unfavorable condition record. 
- 'F' - Similar to 'C', but with the more unfavorable condition exclusion group.

The actual exclusion rules for a pricing procedure are maintained with a sequence number and completed by specifying the exclusion rule and the affected exclusion group(s):

- 10 D Exclusive G002 Discount Group 2 G001 Discount Group 1 
- 20 A More favorable ... G002 Discount Group 2

This data is stored in the T684S database table.

All exclusion rules except for rule 'D' are based on the knowledge of the condition values of the condition types involved. In accordance with exclusion group Customizing, the condition exclusion is therefore also created in pricing in the FORM XKOMV_AUSSCHLUSS (include LV61AA56)

- after an 'initial' (preliminary) valuation (FORM XKOMV_BEWERTEN, Include LV61AA55) of the pricing result  
- and after the condition exclusion based on the KMANU field

(FORM XKOMV_AUSSCHLUSS, Include LV61AA56)

The exclusion is created with inactivity indicator 'A'.

The information in section 3 also applies here: If conditions were excluded from FORM XKOMV_AUSSCHLUSS, a 'second' (final) valuation of the pricing result takes place once again (FORM XKOMV_BEWERTEN), in order to update the pricing result based on the exclusions made. In this case, conditions with inactivity indicator 'A' are no longer valuated.

Note:

a) Since the exclusion of a condition may influence the condition basis and therefore also the condition value of follow-up conditions, a condition or exclusion group that was more favorable (more unfavorable) than another condition or exclusion group after the preliminary valuation may have been more unfavorable (more favorable) after the final valuation. See also the following example.

In such a case, another exclusion or valuation based on the last valuation is NOT triggered. This procedure could result in a continuous loop (the "flip flop effect"). For more information, see Note 217009.

b) In the R/3 standard system, conditions with a zero condition value do not participate in exclusions according to exclusion groups.  However, you can change the system response in such a way that conditions with a zero condition value also participate in exclusions.

To do this, add the value formula 038 (Include FV64A038), or a corresponding user-defined value formula that contains the source code from value formula 038, to the pricing procedure used for a condition that will definitely be part of the pricing result.

c) Conditions that the condition exclusion indicator (see section 2) already fully excluded from the pricing result of an item no longer participate in exclusions according to exclusion groups. As a result, you can no longer use rule 'D' to exclude the conditions of another group.

d) Exclusion group Customizing should not be maintained randomly, but rather with care. If exclusion group Customizing is so extensive that you can no longer comprehend the formation of the 'final result', it is time to reconsider the relevant business process.

Example:

The aforementioned exclusion group Customizing is valid.  Before an exclusion is created, a document item contains the following preliminary pricing result, which of course is not displayed in this form. In this case, the percentage discount ZD02 refers to the price ZPR0 and the percentage discount ZD04 refers to subtotal 1.

Condtns Amt Condtns Val Inactive

• ZPR0 Price EUR 100.00 1 PC EUR 100.00
• ZD01 Discount 1 EUR 4.00 1 PC EUR - 4.00
• ZD02 Discount 2 5.000% EUR - 5.00

Subtotal 1 EUR 91.00

• ZD03 Discount 3 EUR 9.50 1 PC EUR - 9.50
• ZD04 Discount 4 10.000% EUR - 9.10

Subtotal 2 EUR 72.40

In accordance with exclusion rule 10, the discounts ZD01 and ZD02 are excluded from the G001 exclusion group since conditions were determined from the G002 exclusion group with the discounts ZD03 and ZD04.

In accordance with exclusion rule 20, discount ZD03 (condition value EUR -9.50) excludes discount ZD04 (condition value EUR -9.10) since ZD03 is the more favorable discount in the G002 exclusion group.

After you create the exclusion and the conditions have been valuated again, you finally receive the following final pricing result:

Condtns Amt Condtns Val Inactive

• ZPR0 Price EUR 100.00 1 PC EUR 100.00
• ZD01 Discount 1 EUR 4.00 1 PC EUR - 4.00 A
• ZD02 Discount 2 5.000% EUR - 5.00 A

Subtotal 1 EUR 100.00

• ZD03 Discount 3 EUR 9.50 1 PC EUR - 9.50
• ZD04 Discount 4 10.000% EUR - 9.10 A

Subtotal 2 EUR 90.50

Note that, if subsequently considered, discount 4 would now be more favorable than discount 3, since the exclusion of discounts 1 and 2 influenced the condition basis of the percentage discount 4, but it did not influence the absolute discount 3.

Reasons For Making Any Pricing Procedure in SAP

1. Why we are maintaining separate pricing procedure for inter company sales and business processs. 
  
2.  What is the different between standard and inter company pricing procedure and what type condition type we are using in this intercompany.

There are two simple reasons for making any Pricing Procedure in SAP  SD Modules.

1) Business Reason. What are the pricing aspects or strategies you want to apply for the client requirement in order to sell their 
goods or render services, is all about the reason for various pricing procedures.

Eg: Domestic sales pricing procedure, 
- Export Pricing Procedure, 
- A rebate pricing procedure or 
- A High Discount oriented pricing Procedures. 
- A repair pricing procedures.

You have your own conditions intended to few transactions only. Put all this conditions as a set defining your own Procedures. It may even include special requirements and formulas applied for such Pricing Procedures.

2) A special pricing procedures, in order to facilitate added functionalities of SAP pricing architecture, we must define new 
pricing procedure. SAP Standard programmes checks these special Indicators in-order to do some required functions.

As a example 1, you need to have a Pricing procedure for condition supplement inorder to use the condition supplements. The condition supplement pricing procedure must be given in the condition type definitions (v/06) of the Pricing Condition where you need to supplement, without which SAP SD Condtion Supplements functionality doesnt work.

As a example 2, you need to have a Pricing procedure for Inter Company Billing Conditions(IV01 & IV02) inorder to be active for Inter Company Billing specific transactions. Thus make sure that, the procedure wouldnot apply for non-Inter company transactions.

Eg: KA0000 for Condition Supplement for KA00 
- PR0000 for Condition Supplement for PR00 
- ICAA01 for Inter-Company Billing

Here I would like to remind about a important field in pricing.

In V/08 of defining a new Pricing Procedure, in main screen, you have a field called TSPP (Transaction Specific Pricing Procedure). This has to be ticked on for Intercompany Billings.

The SAP help reads for this field as Under:

Transaction-specific pricing procedure

Pricing procedure transaction-specific indicator

Before Release 4.0A, no special pricing procedures were used for intercompany billing and rebate credit memos, programs were just set accordingly to deal with these situations. As of Release 4.0A you are offered greater flexibility in the form of the option to define special pricing procedures for intercompany billing and rebate credit memos. For reasons of future compatability, you will still be able to use the old program specifications. For this reason, you must set this indicator if you want to create a special pricing procedure. This is to prevent the program settings being used.

This indicator is also used as of Release 4.0A to redetermine the condition class and the statistical condition indicator when copying from a reference document.

Example: 
You copy prices from a shipment document to the billing document. The prices should lead to a surcharge in the billing document. This is guaranteed by the redetermination of the condition class in the pricing procedure.

Same case with Standard Pricing procedure or Inter Company Pricing Procedure.

Can Sales Order and Billing Have Different Pricing

During the interview, the interviewer raised one question,  whether the SALES ORDER & BILLING can have different pricing Procedure?

Yes, can have 2 different pricing procedures

1. One for Sales Order 
2. Another at the Billing

Let us take an example :

Generally in the Pharma industry this procedure is adopted becuase all the goods are batch price based.

 1. In the Pharma Industry whenever the goods are manufactured it will done in a batch to keep track and price is fixed, I mean there will be a Batch Master which has a certain price fixed for it. This Batch Master will have certain number of batches . These batches will have the number series generated wither by internal or external generation depending upon the client requirement

 2. So till all the batches are produced as per that particular Batch Master will have the same price. Like that there will n number of batches will different different prices

 3. So when you are preapring  Sales Order you be only putting the tenative price for the goods that are sold

 4. Then at the time of delivery we will be picking up the goods from different batches basing on the required delivery quantity and finally we do the PGI.

 5. This is called Delivery Based Pricing becuase your price for the goods will be determined at the time of the delivery as the goods picked up from the different batches which have different prices. ( Mind it there will very less difference in the prices).

 6. So at the time of Billing the Pricing Procedure behaves differently depending upon the differnent batches that are picked basing on the batch determination.

 7. So the prices which are detemined from different batches will be the actual prices at which the goods are billed to the customer along with other condition that are applied as required.

How To Add New Fields To Field Catalog

I have to add new field "Profit Center(Design ID)" to the field catalog first and then create new condition table for pricing using this field.

1. How to add new field to field catalog? 
2. How to create condition table using that new field?

For adding field into Field catalogue:

I shall give an example. But you should first identify the field for Profit Center (Design ID) and then do as follows:

For example if you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.

When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.

Prerequisites:

For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').

To solve the problem, proceed as follows:

1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.

2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:

Component   Component type 
ZZPSTYV     ZZPSTYV

Save, check and activate the change you made.

3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.

4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'. Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.

5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.

6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:

              MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.

In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.

Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.For header fields, use structure 
KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.

For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition 
Technique) -> New Fields for Pricing' and Note 21040.

For creating a condition Table:

1) There are almost all the regularly used Conditon Table predefined in the system from 001 to 500.

See what best you can use the Standard Tables to avoid further errors.

2) In case you should define the new condtion Table,

a) Goto TCode: V/03

b) Give a Table any number from 501-999

Press execute and reach to next screen.

c) Check up whether  the field you are looking is already added in Field catalogue.

d) Double click on the fields you want to make a Table..one by one. Note that the sequence here is important in higher hierarchical to lower..

Eample : Sales Org, DC, Division, Customer and then Material etc..,

e) After selecting, click on the Techincal View buttin (redone) and reach to next screen.

7) Check which key  should be in header and which key should be footer. Use check and uncheck functionalities there..

8) Once you are through with all the above steps ..click on generate button.

Check the Table is generated or not.

You can check it at V/04 or V/05 or in SE11.

Meaning of Column in Pricing Procedure

What is the meaning of this column in the pricing procedure ,i.e 
  
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.

Steps for Variant Configuration and Pricing

I want to configer motercycle having differnt types of colour, each colour have varity of standered feature as wall as differnt CC. while want to create slaes order I want motercyle with speciefic colour, Cc feature. which is not possible while creating BOM it will only be configer by materiel Varient Configration.

------------------------------------- 
Here are the Steps for Variant Configuration

1.Create a Material of your Motor Cycle using Material type KMAT(MM01).

2.Then create a characteristic called ZColour(SAP has a standard Characteristic for this but it has multiple values-i.e you can select more than one colour for your Bike.If you do not want that create your own)with character format  and assign single value radio button on the initial screen.Go to values Tab and give the colours you need.save the characteristic.Similarly repeat for CC(I figure this CC as 100cc & 200cc kind of thing.If you want these as materials then it is a different story-I am taking this as feature as well)

3.Create a class called Zbike with the above 2 characteristics.save the class

4.Create a configuration profile Zbikeprof using Cu41 and assign the Kmat material to Class Zbike,

5.Then create the order and Enter the Kmat material you want in the Order.

------------------------------------- 

In variant configuration I have configured my material properly during sales order creation it is selecting proper characterstics. but my question is pricing should calculate at characterstics level not at header level.

------------------------------------- 

Pricing in variant Configuration is done at the Header level only.The logic is that you create pricing variant keys for each characteristic Value.This will be done at the Header level using cond type VA00.based on the characteristic chosen the appropriate price according to the pricing variant key will be picked up.

John Devraj.

------------------------------------- 
Here my question is with out creating the materials is it possible to get price based on the characterstics.

I am working on variant configuration here my product is 9-100. i have created characterstics for describing colours. this characterstics assigned to class, this class is assigned to 9-100(KMAT type). here i have not created  amterial to describe each colour.

Now how I need to setup my system to calculate the price based on colour.

------------------------------------- 

A cool Question. It will really get us into the thick of things in Variant Configuration.

Here are the steps.

1.Create a Characteristic called ZColour(Standard SAP has a characteristic called colour.I did not use it.) 
         Give your values. 
         Say, Red  & Blue

2.Now create another characteristic called ZCol_surcharge 
Give the description and go directly to Addnl Data Tab.Here in the table name Enter "SDCOM" and in the Field Name Enter "VKOND".The system will pick up the format from the Dictionary.

3.Now go to CT04 and change the Characteristic Zcolour. 
Go to values tab and select RED.Goto Extras-> Object Dependencies->Editor and then select Procedure.

In front of 000010 Enter  $self.ZCol_surcharge='RED'. 
Similarly Select Blue  and enter $self.ZCol_surcharge='BLUE'

3.Link both these characteristics to the Class(The class which you have attached the KMAT Material).

4.Go to VK11 and the Enter VA00.Then give the values RED and BLUE and enter the values.

5.Go to your order and Enter your material.

------------------------------------- 

Here are some clarifications required from you.

what is the significance of item category group 0002 and 0004. Apart from these are they any other item category groups are available  for configurable materials ? 
In BOM header material having components. is it possible to make the component as configurable material.

------------------------------------- 

The difference b/w 0002 and 0004 is basically that of LUMF & ERLA. 
In 0002 the pricing happens at the Header Item Level. 
In 0004 the pricing happens at the Sub Item Level. 
Check out the Item category Assignments and things will be Clear.

I think these two are the only ones used for Configuration.

Please let me know in which Scenario you would like to have the configurable material Inside a BOM(as it would help me in visualising thh Item Category Assignment).

------------------------------------- 

As you said I setup my system to calculate price based on colour. 
ZCOLOUR contains all colours in values tab page. 
ZPRICE contains table name and filed name in additional data tab page.

I went to ZCOLOUR characterstics I maintained (extras-object dependicies-editor-action) there I have given   $self.ZPRICE = 'RED' for all the values.

when am creating the sales order price is coming only for RED colour not other colours. even price is maintained for all the colours.

------------------------------------- 

Seems like there is a mistake in the line $self.ZPRICE = 'RED' (You have said you have given this for all the values- If I have not mistaken). This refers only to red colour.

In front of 000010 Enter  $self.ZCol_surcharge='RED'. 
Similarly Select Blue in the Values Tab  and enter $self.ZCol_surcharge='BLUE'

All this is Case Sensitive. So please be careful.

------------------------------------- 

Now its coming any way thank you very much.

------------------------------------- 

I have been reading your's and ugamesh's mails regarding the same but no where the sales doucments have been discussed as well as material master record and configuration in SPRO.

If you can kindly explain me the same as I was trying to do the same.

------------------------------------- 

There is no need SPRO involvement in Variant Configuration.Everything happens in Easy Access. 
As far as Material Master record is concerned you only need to use a KMAT Material type.

There is no need to assign any sales document to this material.

Follow the steps and you will get the result.

------------------------------------- 

I have gone thru the steps and created a sales order, but the pricing procedure is not coming proper. Also do we have to maintain the values for the ZCol_surcharge. 
As I have already maintain the rates of the color in VK11 - VA00.

------------------------------------- 

Have you maintained the Object Dependencies for the values in the characteristics class.

------------------------------------- 

Yes !

What I have done is created a customer with KMAT ( Car), without characteristics tab pg. After this I created 3 charateristics viz., zcolor, zengine & zcol_surcharge and assigned them to Class 300 ( Variant). 
But I have maintained the dependencies only for Zcol_surcharge : $self.Zcol.surcharge='RED' 
Then I assigned all these to a config profile and aslo added the condition VA00 in the pricing procedure, then maintained the same in VK11. 
Now my problem is it is not coming in the SO

------------------------------------- 

I think the problem is with the characteristics. 
For the characteristics Zcolor and Zengine you must maintain some values in the Values Tab. 
Ex: 
Zcolor-  Red 
            Blue 
Zengine- V6(Right now you can use only one Characteristic for learning) 
             V8

The characteristic Zcol_surcharge(By name this suggests that it is applicable only to colour-Whereas you can use it for other characteristics as well) does not have any values.

For the values maintained in the Characteristics Zcolor and Zengine you have to go to each value(Go to values tab and select Red) and maintain the object dependency "Action"  $self.Zcol_surcharge='RED'. Similarly maintain for Blue,V6,V8 for Example.

Then maintain the condition records for Va00(without any Case mismatch).

Use standard pricing procedure RVAA01.(or a copy- as it has provision for VA00).

This should solve your problem.