Variant Condition "VA00" in Variant Confugration of a KAMT

Hello,
We are using Variant Configuration Process.
KMAT material is added to Sales Order and configured as per the customer's requirements.
Based on the selections (i.e. configuration), dependencies are in place to identify the Variants (Cond Type VA00) to pick the Varinat Price in Sales Order.
E.g. If customer selects Red Colour handle, variant price for Red Habdle is selected.
If during configuration, Red colour handle is selected, variant price of same is picked up.
During configuration, if customer changes the selection from Red for Green Handle, then
it is expected that Price for Red handle is removed and Variant price for Green Handle gets picked up.
Issue: In above example, system does not removed the variant price for Red Handle. This gives incorrect pricing.
Please help
Thanks

Hi
If during configuration, Red colour handle is selected, variant price of same is picked up.
During configuration, if customer changes the selection from Red for Green Handle, then
it is expected that Price for Red handle is removed and Variant price for Green Handle gets picked up.
Issue: In above example, system does not removed the variant price for Red Handle.
This gives incorrect pricing.
1) Have you maintained dependency for "Green Handle", same as Red handle?
2) Are you able to see "Green handle" as pricing variant in your variant configuration screen? If no, still red handle is appearing, means problem is with dependency.
3) If green handle is appearing in variant configuration screen, have you maintained condition records VK11 for green handle as for red?
Please confirm all above settings and reply.
try and revert
Edited by: Yadav on Oct 12, 2009 7:11 AM

Similar Messages

"Mandatory condition VA00 is missing" in standard order.

Hi
Apologies but I could not find the right answer in foroum so I am posting this ..
I have a problem while creating va01 the error in condition tab in items says "Mandatory condition VA00 is missing" and upon analysis it says:VA00 111 Condition ignored (requirement 002 not fulfilled).
I have maintained condition va00 in v/08 , vk11 all records of chracters and its values.
This perticular error comes with standard order, Could some help me in this regard please.
Thanks in advance.
Venksys

hi
VA00 111 Condition ignored (requirement 002 not fulfilled).
In Pricing procedure, you have assgined 002 requirment to Condition type VA00
requirement 002 says,
check: komp-prsfd ca 'BX'.
check: komp-kznep = space.
So check your item category configuration, PRICING is blank and thats why getting this error
Maintain the PRICING as X in item category and try

Question about variant in va00 condition

Hi there:
I know it is necessary to maintain va00 conditin for configurable material, but I am wondering how variant comes in va00 condition, do I need to create them before maintaining condition for va00? Otherwise how do they come?

Hi there:
Thanks for your answer but I want to be more specific.
The variant condition VA00 works on basis of particular characteristics that you would maintain in sales order.
Lets say that characteristic is ZCHAR and class is 300. when maintaining the charactistic values for this particular characteristic, you need to also maintain data in "Addl Data" tab. following needs to be maintained there :
Table Name - SDCOM , Field Name - VKOND.
I think the point is to write dependency here,let's say if ZCHAR has three values:red,blue,yellow, and the condition should be this way, red 1 USD,blue 2 USD, yellow 3 USD,so here dependencies should be$self.ZCHAR='red',$self.ZCHAR='blue',$self.ZCHAR='yellow'? Then once go to vk11 to create condition, then we need to created three variants and they are red, blue , yellow? Respective price will be 1,2,3?
Next you would need to write a dependency that would be linking this characteristic ZCHAR and variant condition VA00.

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

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

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

Variant Configuration - Pricing issue

Hi,
Can anybody please help me out with the pricing issue which I am facing?
How can I increase the price by a certain percentage based on the value of another pricing condition VA00 and show it as a different pricing condition?
For example: VA00 for my product price shows 1000. Now on 1000, I want to calculate 30% and show it with a different pricing condition description such as "Surcharge". I cannot used a fixed price for lets say "Surcharge" because 1000 as product price is not fixed/static and will depend upon variant configuration and the "Surcharge" will also vary with it.
How can I please implement such a solution?
With best regards,
Sunil

Use the VA01 condition type for this. This is the standard condition type provided by SAP to address this issue. In your pricing procedure against VA01 give the From To as VA00.
Hope this helps.
Regards,
GSL.

Condition Types in Price Determination Process

Hi
Can any one explain me about in Detail about the VARIOUS TABS that work in the CONDITION TYPE of PRICE DETERMINATION PROCESS
Thanks & Regards,
Senmani.

hi
hi
control data 1 :
Condition Class is 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.
Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
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
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:
10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
In rounding rule 'B', values are always rounded down:
1045.9 -> 1045 LIT
1045.1 -> 1045 LIT
In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
Structure 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.
control data 2 :
promotions
Specifies that the condition type in question is only valid for Promotions.
Use
Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
Use
If you mark this indicator, the condition appears in the document as a statistical condition.
Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition type:
'Variant condition' (KVARC)
'Internal costing condition' (KFKIV)
The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
inv.list condi
Condition for invoice list
Marks the condition type as relevant for internal costing.
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.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
Scale :
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
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.
Formula for scale base value
Formula for determining the scale base value.
Use
You can use this formula to specify calculation methods that are not provided in the standard system.
reward points if helpful
thanks and regards
ravikant dewangan

How to control the pricing condition in billing document?

Hello Experts,
Greetings!
We are using two pricing condition.One is PR00 another one is VA00.PR00 is a mandetory condition & prices comes from condition record only.Users are not allowed to enter pr00 manually.
Now we have created one more condition VA00 by which user can increase the price for some particular customers.
Now if the user do enter the condition VA00 in sales order & if it beyound credit limit than system gives informative message & blocks for the delivery.
Now the issue is if they do enter the condition in billing documents instead of sales order system does not check the credit limit at billing level.It allows invoice to be generated even beyond the credit limit.
How can we control this? Is it possible that the condition VA00 can only be used for sales order only.It will not allow to enter at billing time?
Plz suggest how can we resolve this issue in order to control the credit limit.
Any help would be highly appriciated.
Best Rgds
Nitin

Hi,
you can use a surcharge condition type which calculates a percentage over the basic price price that is PR00 in your case.
insert it in the pricing procedure just below the PR00
and remember to maintain FROM & TO step no. of PR00, this condition should be manual entry alllowed
and insert one more condtion type in pricing procedure that will add the values of above 2 condtions .
make above condition type w/o account keys and assign account ker erl to this new condtion type,
STEP NO.     COUNTER     C TYPE     DESCRIPTION     FROM      TO     R     ACCOUNT KEY
8     0     PR00     BASIC PRICE                                           YES
11     0     ZSUR     SURCHARGE     8     8     YES
13     0     ZPR0     Price (Gross)     8     11     YES     ERL
in condition type of ZSUR(surcharge)maintain "c"
REVERT IF HELPFUL
Mohit Singh

CRM 7.0: set up IPC product configuration

Dear experts,
we set up a CRM 7.0 with ERP 6.0 backend integration. In the ERP we apply ERP variant configuration (Materials). Quite simple: some configurable materials (material type KMAT) with a few characteristics and product variants of them (material type FERT) which are maintained in order processing. Variant conditions are maintained and automatically determined for product items. Now we need this in CRM for opportunity processing.
Therefore we have created Knowledge Base and Runtime Version for the configurable products in ERP and downloaded test materials (one KMAT and one FERT (product variant) into CRM (download objects MATERIAL and SCE). In CRM product master data maintenance for the KMATconfigurable tab with the configuration profile is displayed. Afterwards we downloaded condition master data into CRM, among others variant condition VA00 with condition table A057. Everything looks fine.
In CRM we want to set up opportunity management. In the opprotunity transaction processing pricing is working already besides the determination of variant pricing. As we intend to maintain only FERT materials (product variants)we do not need interactive product configuration in CRM sales order or product simulation in CRM product master data. We only want the variant prices to be determined automatically for the product variants (FERT) in opportunity processing. That is why we are not sure if it necessary to set IPC configuration settings (XCM etc.). This is my first question. Nevertheless we started to maintain settings for product configuration in order to find out if this is solves our problem:
1.) XCM configuration (IPC): we set up a customer application for "crmproductsimulation" and defined customer components jco (RFC test worked) and productvariants and restarted J2EE Instance in TX: SMICM
2.) We set up product configuration customizing:
table: COMM_IPC_PROP: caller; crmproductsimulation; scenario.xcm; ZCRMproductssimulation
table: COMM_IPC_URL: UI_CFG; http://<host>:<port>100/ipc/ipc/command.do
When starting simulation of product model for configurable product in TX: COMMPR01 I get following error message: "HTTP500: ISA Framework: The [XCM application configuration]='ZCRMproductssimulation' does not exist. Check XCM configuration.
Details:   No details available". This application is maintained in XCM so I assume something else is missing.
To sum up my questions:
1.) Is it necessary to set up IPC product configuration as described above when we only want to maintain FERT products which are product variants and determine corresponding variant prices (VA00). No interactive product configuration is necessary.
2.) If it is necessary to set up IPC product configuration to active product configuration (to see product variants in product master data maintenance and opportunity processing and corresponding variant condition data), what did I do wrong?
Thank you very much for your help.
KInd regards,
Mark

Hi Arup,
thank you very much for your reply.
Concerning XCM / CRM customizing I have done the steps you recommended:
1. XCM: I created customer applications for crmordermaintain and crmproductsimulation and maintained customer component JCO for both of them (Assigned JCO User has SAPALL / SAPNEW, test run was successful) Active and default are ticked. Are there any further steps missing.May be in General Application Settings > Customer > ipcwebappconfig - I changed nothing there (SSLenabled: true)
2. In CRM customizing I maintained tables as follows:
COMM_IPC_PROP:
caller   crmordermaintain scenario.xcm   Zcrmordermaintain (name of customer xcm app -case sensitive)
caller   crmproductsimulation scenario.xcm Zcrmproductsimulation (name of customer xcm app -case sensitive)
COMM_IPC_URL:
Destination: UI_CFG ;Appl. <blank>; URL: http://<host>:<J2EEport/ipc/ipc/command.do
Calling the IPC product configuration e.g. from the CRM product master (simulate model), I get the already mentioned HTTP error:"ISA Framework: The [XCM application configuration]='Zcrmproductsimulation' does not exist. Check XCM configuration.".
That's why I am thinking that something is missing concerning the communication between CRM application and IPC,because XCM applications do definitely exist.
Is the URL correct .../ipc/ipc/commando.do which I maintained in table COMM_IPC_URL?
Is it possible to check if communication between CRM Online and Java does work respectively what do you exactly mean by "IPC URL must be available for UI_CFG"? UI_CFG ist a RFC-connection which has to be maintained additionaly and if so what has to be maintained exactly?
You mentioned a RFC_USER (This is the JCO-User I suppose?)and J2ee user. Is the J2ee user just the admin user of the J2EE engine or do you mean something different?
Thanks in advance for your further help.
Best regards,
Mark
Edited by: Mark Willhoeft on Jun 4, 2010 8:36 PM
Just one further thing: After changing XCM config I restarted J2EE by TX SMICM (Administration - J2EE Instance local - Send soft shutdown - with restart). Is this enough to restart J2EE and activate changed XCM settings or has the restart to be handled different?

Same material with Different qualities

Dear Experts,
Please give me the solution for mentioned issue ....
I have to maintain the same material which has different qualities (grades) and according to these qualities, the material rate is different. i have near about 50 different qualities for the same material and 50 different rates.
My every vendor is supplying this material for 50 different qualities and rates. So in this case to maintain the individual material prices is big challenge.
If i will maintain Info records, i have to maintain 200000 info record. and also there is possibility of price change for every three months.
So please give me any other alternative solution for the problem.

Hi Vijay,
Variant Configuration may work in your case. I collected some links, please go thru the links:
http://help.sap.com/saphelp_47x200/helpdata/en/92/58d455417011d189ec0000e81ddfac/plain.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
http://sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm
http://www.slideshare.net/arun_bala1/variant-configuration-overview
http://www.sap-topjobs.com/VARCONFG%5B1%5D.pdf
Purchasing:-
1. MATERIAL MASTER
Create Material with material type as HALB Transaction code MM01
Enter Material code as ZMAL.
Select the following views Basic data1, Basic data2, Purchasing, MRP1, Storage1, Storage2, Accounting1, Accounting2, Costing1, Costing2.
Basic Data1 Select General Item Category Group as 0002
Basic Data2 Activate the field Material Configurable
Remaining fields data is as applicable.
2. VENDOR MASTER
Create Vendor Master Transaction code XK01
Enter Vendor code as ZVEN
3. Classification Characteristics
Create Characteristics Transaction code CT04
Characteristics created as
i) ZMALCOLOURRED after entering the description click on the tab Addnl data & then fill up the data in Table name = MMCOM & Field name = VKOND then save the characteristic.
ii) ZMALCOLOURBLUE enter the description & save the data, do not enter any data on Addnl data tab strip.
Save the data
4. Classification
Create Class as ZMALCLASS Transaction code CL01
Class as ZMALCLASS, Class Type as 300
Assign the above two characteristics ZMALCOLOURRED & ZMALCOLOURBLUE to class ZMALCLASS.
Save the data
5. Configuration Profile
Create Configuration Profile Transaction code CU41
Enter the material code as ZMAL,
on the next screen enter Priority 10, Profile Name ZMALPROFILE, Class 300. Select the line & click on the push button Class Assignment, assign the class ZMALCLASS come back to main screen
Select the profile line item & click on the Profile Detail
then click on the push button dependency assignment
on the screen input dependency as ZMALDEPENDANCY &
then click on the push button Dependency editor
input the syntax as
$self.ZMALCOLOURRED = 'RED' IF ZMALCOLOURBLUE = 'BLUE'
save data
6. Pricing Procedure ( SPRO )
Pricing condition types like VA00 - Variants/Quantity & VA01 Variants % is included in the pricing procedure with following settings
Sr. No. DATA VA00 CONDITION VA01 CONDITION
Control Data 1
Condition Class A A
Calculate Type C A
Condition Category O O
Changes can be made
Manual Entries C C
Item Condition Active Active
Delete Active Active
Amount / Percent Active Active
Scales
Scale Basis C C
Control Data 2
Variant Condition Active Active
Access Sequence Variants Variants
These conditions will appear in the pricing when variant configuration is made active in vendor Info Record.
7. Vendor Info Record
Create Vendor Info record Transaction code XK01.
Input Fields like Vendor, Material, Purchasing Organisation and Plant.
Click on the push button Variant Configuration In the pop-up window input the variant condition.
Select the line & click on push button choose the pop-up window will display the two condition VA00 & VA01, select the relevant condition, click on choose then save the data.
Input all other relevant data for creation of vendor info record
8. Purchase Order
Create Purchase Order Transaction Code ME21N.
Input all relevant like Vendor, Material, PO quantity, price etc.
Select the Material Data tab strip in Item & click on the push button configuration the characteristic of variant configuration will appear input the required value,
Go to the condition tab you will find variant configuration condition has appeared in pricing condition.
Save the purchase order.
Reg,
Ashok

Special pricing requirement in BOM

Dear Gurus,
Our Client is assembling Machines with sub assemblies and so on. Now when ever a customer comes he asks for a different combination, so we have designed the MMR as ERLA and has a price at header level and once assembled will be PGIed at header level. OK till here.
Now the issue is, client wants to have a facility in the system where, when ever a client comes for an order, marketing ppl should put all the different sub items in the quotation and the system should pull out the prices of those and others that are specified and marketing ppl should be able to give a Quotation. We need the pricing to be done at Sub Item level and delivery will be done at header level.
Main Item = ERLA = "THUNDER D82" = 5000.00
Sub Item 01 = TAE = Motor 10 HP = 2000.00
Sub Item 02 = TAE = Gear Box 4 Teeth = 1750.00
Sub Item 01 = TAE = Compressor 5 TON = 1250.00
Now when a new customer comes in, we need a facility where in VA21, THUNDER D82 is entered and at sub item level the requirement is:
Sub Item 01 = TAE = Motor 12 HP = 2750.00
Sub Item 02 = TAE = Gear Box 5 Teeth = 2100.00
Sub Item 01 = TAE = Compressor 7.5 TON = 1750.00
Main Item = THUNDER D82 = 6600.00
We cannot maintain a new MMR since every customer can demand a new combination. Kindly remember, once assembled this machine is to be priced at header level and delivered / PGIed at header level. And since the machine will have a lot of other parts, we cannot use LUMF at MMR level.
So how to achieve this? Help me out here Gurus. . . . . .
Best Regards
Venkat - Hyd

Hello Venkat
You need to use a combination of Variant Config (VC) and BOM to make this work.
1) Set up Main Item (THUNDER D82) as configurable material . Set up characteristics (CT04) for the options (example Gear Box would be one characteristic with its values as 4 teeth, 5 teeth etc. These are the values user would choose in the sales order in the configuration tab. Set up a class of variant class Type (300, include all these chars in that and finally link this to the material via config profile.
2) Set up a master BOM with all the components possible and use selection conditions to choose them based on configuration in the order.
3) Introduce Variant Pricing conditions (VA00) to add price for the component selected in the main item's pricing. This also involves using Variant table and/or Dependencies.
This is too brief and very broad based. It involves many steps but will work if you go at it methodically.
Let me know if you get any specific doubts as you go through the steps. Take care.

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?

Variant configuration it price va00 is not coming

hi gurus,
i did variant configuration in this manner but the thing is everything is working fine va00 variant condition it is not coming automatically in the sales order eventhough i maintain conditon records in vk11 for the variants. which i created in vk30. still am not getting price. When i saw in sales order analysis tab which is showing this type of messeges. access not made.
variant(!) this type of symbol am getting . When am giving price as manually in the sales order for va00 it is taking. Please help me in this regard. How system will pick price automatically for the conditon type va00.
For ur reference i did characterstics, dependecies, class,
charcterstic zprice in ct04 i maintained additional data tab as table name sdcom field name as vkond
Thanks & Regards
Points will b e rewarded.

Hello,
please have a look at the following menu path:
http://help.sap.com/saphelp_47x200/helpdata/en/92/58c724417011d189ec0000e81ddfac/frameset.htm
Here is describe how a variant condtion is maintained in SD.
Regards
Claudia

Define variant conditions in TVARC

Hi,
We want to define variants for the SAP using the TVARC option. We want to define report varinat for the Date option for one of the reports using the 3 fields of the Table T009B.
How to define a variant condition in Table TVARC. Can someone give an example.
Thanks,
Tanuj

hi,
just check if the characteristics are all assinged properly.
anyways.. pl go thru these steps again to chek and confirm.
The procedure is as follows:
Create a Material - KMAT type with Item category (002)
Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)
Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.
Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.
Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save
Now go back go to extras - Other Dependencies - assignments and assign
relationship ( by default it will come just save)
Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save
Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)
Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.
Hope it helps. Pl reward if useful.
Thanks,
Sadhu Kishore

Variant Condition "VA00" in Variant Confugration of a KAMT

Similar Messages

Maybe you are looking for