Variant pricing?

Variant condition is not finding in the sales order for a configurable material, guyz could you please help me with this issue, variant price condition exist but it is not showing up in sales order when I enter the characterstic value. appreciate your help soon.
thanks.

Dear Mike,
Is Condition record (VK11/ VK12) exists as on Validity Date as Today's Date for Condition Type: VA00
In Depth Details, could be re-checked with following document. You must go-through it, for once.
[Variant Configuration|http://sapdocs.info/2008/09/09/variant-configuration/]
In the end of the Document, Condition record for Variant Price and Surchage/ Discount is explained, in detail.
If, still problem persists, Please update.
Best Regards,
Amit

Similar Messages

Variant pricing in Sales order and Purchase Order for same Config material.

Hi,
I am stuck to a point wherein the varaint pricing is working either in Saler Order or in Purchase Order.
The issue is that the Variant Condition Characteristics 'VARCONDMM' has MMCOM and VKOND in additional tab and in the multiple selection active (arrow) I have maintained SDCOM and VKOND.
SO the variant pricing is active at the time of PO creation when 'VARCONDMM' is used and not at the time of SO creation.
So I created Variant Condition Characteristics 'VARCONDSD' has SDCOM and VKOND in additional tab and in the multiple selection active (arrow) I have maintained MMCOM and VKOND. and changed the dependencies accordingly for other characteristics.
Then the variant pricing is active at the time of SO creation when 'VARCONDSD' is used and not at the time of PO creation.
Any positive/quick inputs are highly appreciated.
Regards,
Abhilash

Hi,
did you check the code in dependency editor of the dependencies..? do they match between your previous system and new one?
Regards,
Raghu.

Variant Pricing Steps

Hello,
Variant pricing configuring steps
Can anyone explain the steps in details for configuring this with explanation of class type.
Full points will be awarded for good answers.
Thanks,
Anil Rajpal

Hi
STEP 1: CREATE CHARACTERISTICS: - T.CODE: CT04
Logistics , central functions , classification , characteristics , create,
Go for value tab page
save it .
Go for the change mode and change the status to RELEASED
Create another characteristic Namely called CAR_COLOUR with char value as white and black and follow the same above procedure.
Step 2: Create Pricing Characteristic CT04
SAVE IT
Go for change mode and change the status to RELEASED AND SAVE IT
STEP 3: CREATE CLASS CL02
GO TO CHAR TAB PAGE
Save it
Again go for change mode and change the status to RELEASED
Step 4: Create configurable material with material type kmat: mm01
Go for mrp3 view
Give strategy group =25 ( make to order ) and rest as usual.
Step 5:
Create sub material masters for finished products
Like : white, black, normal, and disc.
Step 6: create BILL OF MATERIAL (BOM)
PRESS ENTER
SELECT THE LINE ITEM AND GO OF EXTRAS, OBJECT DEPENDENCIES , EDITOR,
SELECT SELECTION CONDITION
PUT THE SYNTAX AS CHARACTERISTIC = u2018CHAR VALUEu2019
CHECK THE SYSTAX ERROR (CRTL + F2)
IF NO ERROR THEN SAVE.
STEP 7: CREATE CONFIGURATION PROFILE: CU41
SELECT MATERIAL AND PRESS ENTER,
SELECT THE LINE ITEM AND GOTO PROFILE DETAILS
Select the user interface tab page and click the setting button
Select the appropriate option as u like
No we have to link the characteristics and values
For the above , for the screen cu41, go for extras , object dependencies, editor
SYNTAX : $ SELF.PRICING CHARACTERISTIC = u2018CHAR.VALUEu2019 IF $SELF.CHARACTERISTIC = u2018CHAR.VALUEu2019
Save it
Come back and again save it
Step 8:
Place the variant condition in the pricing procedure
Procedure zvaa01
Create condition record vk11
Save it
Now entire configuration was done for variant configuration
N0w create a sales order
Va01
Item category: TAC
Billing relevance : (A) : delivery related billing.
thanks
Kuntla

Variant Pricing - Passing a Z* condition to a quote

Wondering if anyone knows how to pass a z condition to a quote from the configuration. We have variant pricing working for the VA00 pricing conditions, but would like to pass across a Z condition. Any ideas?

So instead of VA00, we have Z-PG. In a normal pricing procedure, I set the characteristic that is set to SDCOM-VKOND (VAR_PRICE) to the name of the VA00 condition and then do a $SET_PRICING_FACTOR. How does it know to look at Z-PG instead of VA00?
Example of code of how we do the variant pricing for VA00:
$SELF.VAR_PRICE = 'FCM_CHARGE'
$SET_PRICING_FACTOR ($SELF, VAR_PRICE, 'FCM_CHARGE',CABLE_FIBERS)
FCM_CHARGE is set up under VA00.
How would the code look to find the condition under Z-PG?

Material Variant pricing

Hello All,
I have created a material variant from a configurable material. I would like to know if in the sales order I can pull up the variant pricing condition attached to the configurable material, or do I have to maintain separate conditions in PR00. thanks
Atul

Dear Atul,
As per your Q i understand that you want a pricing to be pulled in sales order.
The Pricing for the material will same as we do. i.e we need to maintain the record in PR00.
But for Variant the pricing needs to be Maintaind in condition type VA00.
All the variant needs to be maintained in VA00 only as this condition type get activated only when you are working with Variant configuration.
Suhas

Variant Pricing _ each item price based upon main item.

Hello,
I request your help for inputs on Variant Pricing functionality for given scenario.
Each material will have different price based upon different brand / main item.
For example u2013 Inbuilt-Sat Nav will be priced different in Toyota Prius & Toyota Avensis.
Let say, we have 2 products (Toyota Prius & Toyota Avensis.) each having 10 different options/ items which are charged separately.
Hence would like to know how we can set up the price in variant based upon Main item & sub item.
Toyota Prius / Customer / InBuilt Sat Nav = £1200
Toyota Avensis / Customer / InBuilt Sat Nav = £1500
Your inputs are appreciated.
Thanks & best regards

If you want to maintain seprate prices for each variants go to VK11 use the following condition types -
VA00: this condition type expresses an absolute amount.
u2013 VA01: this condition type expresses the surcharge/discount as a percentage
above are based on sales org, material and variants combination, so as you said you requirement is based on customer will charge different prices, so create new condition table with customer combination and add in to same access sequesnce and condtion type.
For more details check the below link:
http://www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm
regards
Satish

Variant pricing - steps requested

Hi,
I created configurable material Envelope, assigned variant class 300 to material.
then created characteristics, ZSIZE and gave values like DIN C4, DIN C5.
then created class ZENVELOPE and assigned characteristics to it.
I want to do variant pricing?.
How to proceed?
Thanks

Here are the detailed steps
- create another characterstics 'ZPRICE' and go directly to Addnl data tab. enter table name as SDCOM and in field name enter VKOND. The system would copy required information from the data dictionary.
- go back to characterstic ZSIZE. Go to value tab and select DIN C4.
from menu bar select GoTo - Extras - Object Dependencies - Editor - select procedures.
In front of 000010 enter $self.ZPRICE='DIN C4'.
similarly repeat step for DIN C5.
- go back to class ZENVELOPE and assign your newly created characterstic ZPRICE
- go to VK11 and enter condition record as VA00 and give values for DIN C4 and DIN C5.
- create your order and a pop box would come up giving option to choose DIN C4 or DIN C5. Basing on option you choose system would automatically determine price for this variant.
- Remember to declare material price for your main item Envelope.
- If you have any problems post your message again.

Variant pricing not working

Hi,
I created a variant material computer - KMAT type.
created characteristics ZCOMPUTER with values monitor, keyboard, mouse, price.
created class - ZTOWER and assigned above characteristic values to this class.
created condition records for computer & variants.
created order and i don't see any price determination.
please help where i am wrong.
thanks

You could base my reply below and use it you create your own variants as per your requirments.
You should create separate characteristics for monitor, keyboard, mouse for example Zmonitor, Zkeyboard, Zmouse and assign values for them.
You should create a separate characteristic for price for example ZPRICE.
Delete characteristic Zcomputer.
Material: computer of KMAT material type.
Charactersics
Zmonitor - values samsung, hp
Zmouse - values wireless, optical
zkeyboard - values microsoft, toshiba
ZPRICE: just enter in Addl tab Table name as SDCOM & Field name as VKOND. System would copy info from data structure maintained in table SDCOM.
Class
ZTOWER and assign the above characteristics to this class.
Now go back to characteristics Zmonitor
select value 'samsung' from TAB values From Menu bar select Extras -> Object dependencies ->.Editor
in line 000010 enter $self.ZPRICE='samsung'
select value 'hp'
in line 000010 enter $self.ZPRICE='hp'
similarly do this for values in characteristic zmouse & zkeyboard.
Now create a pricing condition record PR00 for material computer.
create variant condition record VA00 in condition record VK11 for characteristic values samsung, hp, wireless, optical, microsoft, toshiba.
create sales order and you would get a box to choose variants.
please let me know if it works.

Multiple Variant pricing conditions in a Pricing Procedure

Hi,
I have a scenario regarding variant configuration pricing in a sale order. I need to attach multiple pricing condition like VA00 in my pricing procedure .
A material M1 has many characteristics under the category Basic and Special for example.
Under Basic I have the following characteritics and its respective values maintained in VK11
B001- Basic Spec 1 USD 100
B002- Basic Spec 2 USD 200
B003- Basic Spec 3 USD 300
Likewise under special category ,
S001- Special Spec 1- USD 500
S002- Special Spec 2- USD 1000
In the pricing procedure the varaint condition VA00 will carry the price of the characteristics. My requirement is as follows
1. The prices of the Basic spec should be added first and later the special spec
VA00- Basic Spec 1      100
VA00- Basic Spec 2      200
VA00- Basic Spec 3      300
Sub total Basic spec Value 600
VA00 Special Spec 1    500
total basic and special spec - 1100
The problem I faced in the above format was that the pricing procedure will allow only one entry of VA00. To over come that I copied the condition VA00 and named a new one, for e.g, ZVSP.
Now when I use the condition ZVSP, it does not fetch the values like VA00.
Could any one suggest a method in which I can introduce varaint conditions in multiple levels in a pricing procedure.
Thanks and regards
Rasheed

Hi,
When you copied the VA00 condition type, did you also copy the associated access sequences? Your new condition type should have an access sequence with an access that transfers the value of the doc. field KOMP-VARCOND into the condition VARCOND; use transaction V/07 to check this.
Regards, Jesper

Pricing Error: Variant Pricing

Hi Experts,
I have created KMAT material BOX. I have set all the pricing procedures and condition records correctly and when testing the material the pricing does come through correctly.
E.g.
Small = £50
Medium=£150
Large= £250
When putting in material Box and selecting small the price will come through correctly as £50 however I still get a
Price error u201CMandatory condition PR00 is missingu201D.
I donu2019t understand why, as the material BOX doesnu2019t not have a standard price and there can only be three options. So I tried creating a condition for PR00 that was 0.00 but that doesnu2019t work either
Please could you help?
M.Patel

Mr. Patel,
There will be a Standard Basic price for all the materials that are created. In your example you can maintain the standard price in PR00 as $50, and maintain the other prices as Variant Price in VA00.
Now the system will take the base price and depending on the other parameters (Size in you case), it can pick the Variant price(you need to maintain variant price as Mediun Size as $100 and Large as $200).
Regards
Vamsi Javaji.

In variant pricing condion va00is not picking the variants from dropdown

hello all,
wen i m preparing condition record in VK11 and using condition va00
i m not getting variants for my materila
as my PP guy has already made the variants but then also
its telling a message no valu fount in variant colomn
after that wen i m puting the same variant manualy not picking from drop down menu
then also in sales order the vaoo is not coming with any price its comming as no price in it
how to maintain ....................
please help
regards
subrat
[email protected]

hi subrat,
I think you have not maintained CA01 for vaiant char
If not maintained the configuration in ca01 for each variant char
I am sending you the PPT with snap shot, please go through.
The configuration of ca01 is in slide 29
regards,
Arun Prasad C R

Reg:Variant Dependencies & Pricing

Hi Gurus,
I have configured up to the below mentioned steps.
1.Creation of Material Master Record with required settings
2.Creation of Characteristic and it's values
3.Craetion of class
4.Assign characteristics to Class
5.Create configuration profile and assign it to MMR
I have strucked at pricing and dependencies maintenance.I need some info.related to pricing maintenance and dependencies creation.Kindly help me on this regard.
Thnaks & Regards,
Sash.

Hi,
The following needs to be set up for the variant pricing of configurable product .
Create pricing condition VA00 for the variants
Create characteristics
Create variant table
Create dependencies
Allocate the dependencies to the configuration profile
Procedure:
1)Create Pricing Condition-VK11 Transaction code.
Condition Type:VA00
Maintain the required pricing here.
Note:The condition type VA00 is defined as a fixed rate surcharge, which is applied to the base price of the product ordered. This variant condition is created as part of the pricing master data for each of the configurable options for which a surcharge should apply
The condition type VA01 could alternatively be used in variant pricing to increase the price of the higher level material by a fixed percentage rate.
Maintain the prices for all the variants (Characteristics) you have create.
Note:The entry of the Variants is case sensitive.
2)Create Characteristics:Surcharge
Transaction code:CT04
Create a Characteristics name to identify your Pricing Characteristic.
In the addition data tab maintain the following:
Table Name:VKOND and Field name :SDCOM.
Note:
The characteristic u201CSURCHARGEu201D references to the field u201CVKONDu201D of the u201CSDCOMu201D table. It provides the link between the materialu2019s variant configuration and the variant conditions that were entered.
3)Create Variant Table::
Transaction code:CU61
Maintain the characteristics in the Variant table.(Char.Name,Char.Value,Var.Cond )
Save it..
4) Maintain the Variant table :
Transaction code:Cu60
Maintain values for Example
Characteristic Name   Characteristic Value Variant condition
Size                                     10                             Size_10
Colour                                  Red                         Colour_Red
Colour                                  Blue                          Colour_blue
Save the table.
5)Create Dependencies:
Transaction code:CU01
Maintain the required description and in dependency editor
You see the screen u201CEdit Dependencyu201D. Select Insert line icon five times to insert lines. Enter the following on the inserted lines.
TABLE TBL_PRICING
     (CHAR_NAME = 'Size',
      CHAR_VALUE = $self.Size,
      VAR_COND   = $self.SURCHARGE).
Note: This procedure references the Table TBL__PRICING. The dependency checks to see which value was chosen for the 'Size' Option and specifies the appropriate Variant Condition to this choice.
Check whether your dependency has errors or not.
After that Save it and make sure that it has been released(Which you can find in the initial screen)
6)_Allocate Dependency to the Characteristics profile of the material:
Transaction code:CU42
In the screen u201CChange Configuration profile for Material: Profile Overview u201D. On this screen, maintain your profile and select Profile Detail icon.
You see u201CChange Configuration profile for Material: Detail Screenu201D. Under the Section Header Basic Data, select Object dependencies button.
You see the screen u201CMaintain Dependency: Allocation to Objectsu201D screen.
Maintain your dependency here in this configuration profile for the material.
Once it is done cross check in transaction code 'PMEVC' Transaction code for ECC 6.0.
Simulate your Variant configured material and cross check.
Hope it helps.
The steps may look little bit exhaustive but the process of maintaining it shall be fruitful.
Have a Nice Day.
REgards,
Ravi

Pricing Condition is Duplicating on Changing the Variants in Quotation !

Hi,
I have a requirement, where the Pricing Condition (Custom Pricing Condition Specific to the Variant Pricing) is duplicating on changing the Variants in Quotation to be stopped or deleted. I suppose, the variant pricing condition should not be newly added to the pricing table each time, there is a change in the material variants as chosen by the business/user with the Quotation. Instead, I assume, the existing cost for the variant pricing condition should update each time, when the variant material is changed by the user. I am not sure, whether this issue can be controlled in the configuration? or Can I control the occurrence of the duplicate pricing condition inside any user exit by deleting the duplicate condition, but retaining the newly added ( Recently added pricing table entry for that condition)? I am not sure, what are the possibilities to fix this issue? Appreciate if you could provide me with a suitable solution.
Thanks for your time.
Thanks,
Kannan

Hello Kannan.
I have the Same Problem. do you have a solution for the same?
i have written a pricing condition at the characteristic level using pricing Factors. however when i change the characteristic. it is duplicating the condition instead of refreshing it.

Variant config pricing condition description not correct

Hi Gurus!
I created Sales Order with a variant configuration material, pricing with package items. System pick up the correct
pricing but pricing Condition Name for all the items are the same, system is taking variant description VK30 instead
of condition type description in VK11.
I have a package e.g.
Material: Phone Package A
Condition type:
- ZZ01 Phone
- ZZ02 Charger
- ZZ03 Battery
Data entry: Material A001 Nokia phone package
charcteristics: Phone       PA
                       Charger    A1
                       Battery     T1
System compute all the description of condition type is the same
Material: Phone Package A
Condition type:
key: PA-A1-T1
- ZZ01 Package A for Nokia AAA   10.00
- ZZ02 Package A for Nokia AAA   30.00
- ZZ03 Package A for Nokia AAA   50.00
I want the description of Condition Type not the variant description. Any clue on how to get the correct description of the
Condition Type?

Hi Sunny,
1) With respect to your original question (e.g. "how to have the VTEXT field on the Conditions tab display the Condition Type Description set via the IMG rather than the Variant Description set via txn VK30"). Please know that once you check the "Variant Condition" flag for a condition type, the system has no choice but to present the Variant Description because this behavior is hard-coded.
Easiest solution would be to activate screen overlay functionality (such as GUIXT) which can present the desired text to the user without affecting underlying code. Another alternative is to ask a developer to make an implicit enhancement that overrides the description just before presentation to the user.
If neither solution works out and the users insist that you show the condition type description, then variant pricing simply doesn't fit. Hopefully you don't get to this point, but if it happens, then you would have to revert to standard (non-variant) pricing. To start you would need new display-only VBAP fields for each price-relevant characteristic (e.g. ztraining, zcourse_type, zstudent, and maybe zresource). and then custom code to copy values selected in the VC back to the corresponding new line item fields which can be done via a user-exit. Then you would follow the normal process for introducing new price-relevant fields, and redesign your condition types and condition tables to remove all reference to pricing variants. A hassle, but side benefit would be more straight-forward master-data maintenance since the user can directly see and maintain all pricing key fields in VK11/12/13 (rather than having to check variant table(s) to discover how the pricing key fields translate to variant keys) and of course they would always see the condition type description as desired.
2) Moving on to address your 3rd-August follow-on comment from the other thread (e.g. "However, when I change the input Resource from 01 (Classroom) to 02 (Whiteboard) ... ZA01 is gone"). Is this what you wanted? If yes, then a user who needs a Classroom and Whiteboard and a Projector, would have to create a sales order with three configurable line items - is this the desired outcome?
Edited by: Laura J. Williams on Sep 23, 2010 1:22 AM

Dummy characteristics for pricing variant characteristics of BOM- SDCOM-VKO

Hi,
I was trying to create a dummy characteristic OPTICAL_LENS_VP for the characteristic OPTICAL_LENS. While doing that I wanted to enter the Table and Field info SDCOM and VKOND respectively in the tab Addnl Data. However, on doing F4, I do not see the table SDCOM. I tried searching by clicking on the button "SAP Applications" without any luck. Could some one help me please. BTW, the TC for creating a characteristic is CT04.
Thanks,
-Prashanth

Once you save the characteristic, the reference to table name & field name are disabled.
If you want, this characteristic could be deleted or create a new one.
For example lets say create a characteristic ZPRICE.
Go directly to Addl data tab and in Table name field enter SDCOM and Field name enter VKOND. [Don't use search button].
Click enter.
You would get a message 'Formatting data taken from data dictionary' and once you click continue, system populates the required fields.
The reason why we use this is because:
In SD, you can use variant conditions to define surcharges and discounts for configurable materials, depending on the characteristic values you assign. For example If a customer wants a car with a sunroof, the net price is increased by a surcharge of $2000.
You create variant conditions with reference to a material, a distribution channel, and a sales organization.
To create a variant condition, there is a pre-requisite which is that you should have created a characteristic that refers to table SDCOM, field VKOND.
This characteristic (in our case ZPRICE) is assigned to the variant class for the configurable material.
An object characteristic with a reference to the table SDCOM field VKOND is multivalue because several variant conditions can be entered.
In simple terms variant pricing is taking place because of reference to SDCOM table & VKOND field.
SDCOM is a structure in development class 'CU' and Appl component LO-VC

Variant pricing?

Similar Messages

Maybe you are looking for