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.

Similar Messages

Variant config pricing

HI,
for variant configuration pricing if we use VA00 ctype ,
when we create sales order whether both proo & vaoo will get detrmined or only vaoo will be there
pl let me kno how exactly varinat configuration pricing works

hi
vaoo will be assigned to characteristics
but in sales order -proo will also be there rite along with va00

Variant Configuration and pricing in a Sales Order

Hi,
I have been successful in updating variant configuration for a sales order using the function modules 'BAPI_SALESORDER_CREATEFROMDAT2' to create the sales order and 'BAPI_SALESORDER_CHANGE' to add the variant configuration characteristics on a configurable material.
The issue I am having is that if I don't add the configuration values for pricing the pricing will not automatically update.
I have tried using function module 'CE_C_PROCESSING' to update the pricing after calling BAPI_SALESORDER_CHANGE without success.
Is there anyway to get the pricing to automatically update without adding the variant configuration values related to pricing?
Any help would be appreciated.
Derick

Hi Derick,
We are trying to create a sales order with a configurable item using 'BAPI_SALESORDER_CREATEFROMDAT2' and the issue that we are facing is we are getting the sales order but the configuration values are not getting populated.
Could you please guide us on how to pass the configuration data to the BAPI to create a sales order with configuration values?
Any help would be highly appreciated.
Thanks...
Abeehs

Variant Configuration Issue

Hi
I want to pass one characteristic value description into other characteristic text value, which i am controlling with procedure dependency.
Currentely i can able to pass Chars value into other text chars with same value.
For examples
Char X    01 - Description A
             02 - Description B
             03 - Description C
Char Y : ( text free form field )
If i select Char A 01 in configuration then through dependency syntax I can able to pass '01' into char Y, but i want to pass A Description in place of char' value.
Please let me know how it is possible.
Vicky

Hi
I am facing issue in Variant Configuration functionality.
I am having 1 characteristic XYZ with values
1 - data
2- cable
3 - wire
Another characteristic is ABC with no value, it is text field.
Now in configuration of material if i select XYZ = 1 (data) then through procedure depedency i am passing a value 1 (same like XYZ). But i want to pass decription of characteristics value in char's ABC
means if i select XYZ = 1 then in char's ABC = Data should come instead of '1'.
Regards
Vicky

Issue in Variant Configuration

Hi all,
I am working on Variant Configuration and i have a Configurable Material with Super BOM Structure.
Separate Configuration Profiles are maintained for both Main Material and BOM Component.
Configuration Process is Sales Order (SET), BOM Explosion is at Multilevel and Application is SD01.
When i create a Sales Order, only BOM's of Main Material are getting Exploded, where as BOM of Components
are not been Exploded. When i am trying to create a Sales Order directly for Configurable Component,
then BOM gets Exploded.But this does not happen when i try for Main Material.
Can any one help me in this regard?
I want to know the reason for this and any further Customization settings, to make Components of Main Material
as well as BOM Material get Exploded in Sales Order.
Thanks in Advance.
Regards,
Ravi

Hi ,
The issue could be due to the following.
When to enter the Main material in the sales order. The Main Material Item Category will be "TAC" for which "Structure of scope" in IMG would have maintained hence it will explode BOM components. Now eventhougth BOM components have " Configuration profile" The item category is "TAE" which will not " Scope of Structure".
Now goto IMG item category configuration and maintain " Bill of Material/ cobnfiguration" settings for TAE. it will explode multi level BOM.
But when u enter the configurable BOM separately in sales order it will explode, because now BOM componet Item cat will be TAC
Hope this will help u
regards
Arun Prasad
Edited by: arun prasad on Jul 30, 2009 6:27 AM

Variant Configuration Cost in Sales Order

Can you let me know what is the standard way to cost Variant configured items in the sales order? for standard item costs, we use VPRS, but for Variant items, the costs vary depending on the variant characteristics selected. Sales Price is controlled by Variant Pricing...but i wanted to know how Cost for these Items should be set up as a best practice. Some place explode the BOMs into the Sales Order - but some characteristics are not Materials per say. Thanks.

Hi Nhu,
Welcome to SCN.See suppose you created sales BOM. In general the sales bom will explode and appear in sales order.Here we consider only main material only.
Sales BOM Configuration;Sales Bom|Sales BOM Configuration;
[Sales Bom Explanation|http://www.sap-img.com/sap-sd/sales-bom-implementation.htm]
[Cost Calculation|http://help.sap.com/saphelp_470/helpdata/en/90/ba6da4446711d189420000e829fbbd/content.htm]
Check these links if there is any issue please post.
Regards,
Madhu.

Variant Configuration Error in sales order

Hi,
Done the customization for variant. Raised sales order & selected the characteristics like colour--Red & engine--200cc for material & checked in item level condition its showing the 2 characteristic 100cc & 200cc engines but not the characteristics colours. Maintained condition record & condition type in pricing procedure.
I have 2 issues
1) In Sales Order I selected only characteristic engine 200cc & why it is showing another characteristic 150cc also in Item level conditions.
2) Why it is not showing the Colour characteristic Red in conditions.
Looking for the experts answer
Regards
Pradeep

Hi,
Variant configuration is as per my knowledge its a case sensitive. Please maintain all the variants and character in CAPP letter and do the same during formula writing also.
During creation of Condition record maintain with CAPPs letter only.
Thanks,
Neo.
*Reword points if its helps.

Variant configuration-- syntax error in creation of object dependencies

In variant configuration when i try to create object dependency (tcode=cu01), after entering the dependency and also description when i enter the syntax in the source code it is giving error: error in syntax check for simple condition
I have entered syntax as : engine_cap in ('1000','1400','2000'), pls guide me with the solution to create object dependency

Dear, Shakeer
Please follow along with my very own config guide of variant config.
1)     Create a configurable Material Using KMAT u2013Material Type. Item Category 0002 and Item Category Group 0002. Go to classification tab-here you maintain the class type 300 and assign the class, we will create this shortly. (So after creating class come back into MM02 and input the class that you create in step 2.)
2)     Create a class in T-Code CL01. Use class type 300 for Variants. In this we assign the characteristics we will create shortly.
3)     Create characteristics in T-Code CT04. Create your characteristic like for example, Z_Type, Z_Model, and Z_Color.
4)     We must create a characteristic for the pricing. Example, Z_CarPrice inside this characteristic we must maintain. Table Name SDCOM, Field Name VKOND in the additional data tab. Also, go to restrictions tab and enter the class type 300 Variants. Now in order to make this pricing work for you, you must maintain (enter) all the values from the characteristics. For example, Red, Blue, Black, Honda, Toyota, GLI, XLI, and 2.0D.
5)     Now going back to the characteristics in CT04 change mode. Make sure Basic Data has *Multiple Selections circled. * Character Format has 26 and a check in case sensitive. Make sure in restrictions tab class type 300 Variants is present. Go back to Values and highlight the first one. Example, Red then go to Extras->Object Dependencies->Assignments You must maintain this code $self.Z_CarPrice=u2019Redu2019 in basic data make sure itu2019s released & procedure is filled in. Go back to dependency editor and paste the same code there after 000010 $self.Z_CarPrice=u2019Redu2019 and do this for each and every value. Very Important * Maintain configuration profile in T-Code CU41 for the material -> Priority 01, Variant Configuration, Class 300, status, Released 1, then click save. Note: If 2 conditions are inactive use class group A instead of B in SPRO for Condition type VA00.
6)     Go to T-Code VK11 and enter VA00 condition type. Enter all the values maintained in the characteristics for example, Red, Blue, Black, Toyota, Etc and enter the price then click on save. Now it should work fine in VA01. Make sure you have assigned the VA00 condition type in the pricing procedure.
Good Luck,
Muhammad Ali Lozada

How to hide variant configuration screen in sales order

Hi Friends,
Could you please help : how to hide variant configuration screen in sales order for a configured material
Ranjan

Hi
The very purpose of VARIANT CONFIGURATION is to for this material these are the characteristics available
In this you choose one characteristic then these are the values available
If you make a choice then this is the price
Means Maruthi car is the product
Say 800
Alto
Zen
These are characteristics
In this you choose say black, cherry red, white these are the values
When you put a sales order for Maruthi car then if it is 800 black colour then price is X
if it is 800 white colour then price is y
So that according to the choice of the customer the pricing and other details are fetched
Why do you want to defeat the very purpose of VARIANT CONFIGURATION
Rather than listing out of the whole product list the system simplifies the thing
Without that popup variant configuration is meaningless
Regards
Raja
Edited by: ramanathan raja on Dec 11, 2008 3:48 PM

BOM explosion in sales order in variant configuration?

Hi All,
After searching all threads iam posting this .
My requirement is
In sales order the material(ZDESKTOP) which has been created in KMAT with item caragery gruop 0002(Configuration) has compenents like PROCESSESOR,DRIVE,KEYBOARD,STORAGE,MEMORY,etc where again each components have 3 varieties(values).while creating sales order the components and picking of values is running well.THE GREEN LIGHT IS ON IN VARIANT CONDITIONS.pricing is picking for variant conditins(values)
These values are stockable items which i created as semifinished.
item catagery TAC is determined.
Now my problem is the values(sub-items) which are attracted pricing should reflect as sub items of ZDESKTOP.
I have created a BOM also for ZDESKTOP.
I HAVE GET ONLY THE PRICED VALUES AS SUB-ITEMS.
HOW TO DO THIS SCENARIO?
Need Help.
Regards,
Reddyy
Edited by: REDDYY SD on Feb 4, 2009 12:51 PM

Hi
check your Item category group in material master , sales org view, if it is 0002 Configuration this material use for varient configuration, but your case it may be LUMF (Structure/mat. below) it used for sub item price.
It is , one of the reason.
Regards
Paulraj.S

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

Sales Order text for Variant Configuration

Hello
I have researched my issue and also have asked other peers for guidance. I feel that I am really close to getting my issue to work but I am not sure what I am missing, so I am hoping that someone can give me some advice as to what to check please. See below for the description.
My issue is in reference to SD Variant Configuration and is outlined below.
Overview
Main Unit is a radio test set
Test set can have an upgraded software
Example
Model 6015 u2013 standard test set
Model 6015T u2013 Upgraded software test set
Model 6015V u2013 Upgraded Software + test Set
Requirement
Use same Material Number using Variant Configuration for the upgrades
Price is to default to the Upgraded price
NOTE:
Our materials are already established and are set up as material type Finished Goods; ERLA item category; sales order item category is a copy of TAC. I am using a Configurable Material type KMAT, item category 0002 and linking to the FG material item category ERLA in the material master.
I have created the Material Variant (KMAT) in MM01
Created the characteristic in CT04
Created Classification in MM02 for material FG
Created Super BOM for Configurable Material in CS01 and added the upgrades as Alt Bom 2 for upgrade and 3 for Upgrade+. Also added the Alt BOM text
Created Profile of configurable material in CU41
For the Material I added the configurable material to MRP 3 screen in MM02
Created the BOM link in CS40
I simulate the material in CU50. I enter my material; select the icon for configuration, I can see the characteristic Value Assignment nad see my characteristics Description. I go to the value and use the drop down I then see the pop up of all the different values.
I have created Characteristic Reference VCSD_UPDATE_ARKTX with table VCSD_UPDATE and field ARKTX - no values
I have created a characteristic Test_Choice with the 2 values one is Test Upgrade 1 and the other is Test Upgrade 2. Both of these have the description as well.
For Material Text:
I have set up a reference characteristic using 30 character format (named VCSD_UPDATE_ARKTX),
with table name VCSD_UPDATE and field name ARKTX.
Then in the Configuration Profile(CU42) for configurable material, added a procedure(named PR_PRODUCT_DESCRIPTION) to the dependencies which contains code that sets the description
$self.VCSD_UPDATE_ARKTX = ''Test Upgrade 1u201D
If $self.TEST_CHOICE = Test_Upgrade_1,
$self.VCSD_UPDATE_ARKTX = ''Test Upgrade 2u201D
If $self.TEST_CHOICE = Test_Upgrade_2,
When Entering the sales order for Material Number XXXXXX, I receive a pop up that I can select which Alternate BOM (from CS02) I would like. I select my line item and then select the configuration icon at the bottom of the sales order. I see again my characterestics values (the same as CU50) but am unable to select the radio button. Not sure if this part is standard. Still no change in the sales order line item. I have validated that I am using a copy of the standard TAC item category. How does the text change to the correct value? Am I missing a seeting somewhere. Please provide any guidance with this as I have been trying to get this to work for over a month.
Thank you for your time. It is greatly appreciated.

I have figured out that this will work if I go to the standard material (it is not KMAT but it is a FERT material type) and set the flag in the Material Master Basic Data 2 tab that this is a configurable material and not use KMAT material type for a super BOM. The text changes for this scenario so it give me hope.
This is not ideal, as I want to use the Super BOM because there are different variations (non stock items) that I need to pull through on the picking list in order to tell the end user which option needs to be loaded in the standard material. At least I know the text can change on the sales order; but I am still struggling with the use of the super BOM and changing the sales text when there is use of a super bom as you tie that to the MRP 3 screen of the FERT material type. I can set everything up, but the text will not change if I set up the material master this way. Guidance is appreciated.
Example
Material 72433 (FERT)
on sales order I enter 72433, my alternate BOM comes up with different Options. Alternate BOM 1 is standard configuration; My Alternate BOM 2 has Option 3 and 4 while alternate BOM 3 has option 5 and 6. Alternate BOM 2 is a 6015T and Alternate BOM 3 is a 6015V.
I want my sales order to pull through the text of 6015T or 6015V, whichever is chosen. I want my picklist to print out the option that was selected.

Consuming Material Having Variant Configuration

HI
We are using Variant Configuration for our semi finished product and its
batch managed.There are two plants in one plant say A and B. In A plant
we are using Variant configuration.The same material is stock transferred
to plant B and is further processed.
We are creating CIR in plant B. After taking MRP run we are converting
planned order to purchase requisition and subsequently Stock transfer
purchase order on Plant A. When the material is produced in plant A,it is
transferred to plant B on stock transfer order mentioned above. But the
material is against CIR in plant B. We remove the material from CIR
through 411E movement and system keep it as free stock in unrestricted.
Now when i am consuming this material for further processing in
production order of Material getting manufactured system is asking me for
Variant Characteristics.
System should not ask me variant characteristics once it has been removed
from CIR i.e. special stock.
Any Work around avilable.
Regards,
Anand.

Hi Anand,
Finally, I could understand your issue from your CSS message.
In your description, AA is configurable material in both plant A and plant B, BB is not a configurable material in plant B, AA is a component of material BB, so when you produce BB, there will be dependent requirement generated for AA from BB, now you want to use the stock of AA to fullfill the dependent requirement, however, the system will require you to enter the characteristic at that time.
Then where is the stock of AA comes from? I have mentioned this in my previous reply. But as I have mentioned it is not correct to have unristricted stock for the configurable material, therefore, your process to have free stock of AA is not correct.
Another point is that, your process to have configurable material as a component of a non-configurable material is also not proper.
For example, material BB is a Car, material AA is the Door of the Car, your Car is not configurable, but the Door is configurable, you may have green door and red door according to the configuration, but as your car is a firmed material then what's the meaning to have different door, if you want to have different door, then that means you also need to have different color of the car, like green door for green car, red door for red car, then that means your car should be also a configurable material to make you can select the color of the car too.
Or if your Car is a firmed material as green car, then do you think there is any meaning to configure the door of the car? Unless you do want a red door for a green car, but this can also be realized with a configurable car.
So normally, like your situation, you should use multi-level configuration structure to do the production in make to order scenario.
Therefore, still the problem has been described in my previous reply, no matter how you get the stock of AA, the AA is produced with the configured configuration module, so the stock of AA is also with the configuration data, then no matter how you want to consume the stock of AA, system will always ask for the characteristic of the requirement to compare it with the stock configuration to see if they are same.
For example, you are producing your Car, but as far as I can see you should have no place to configure the door in production order, therefore when you try to consume the door, the system will of course need to know which color you want, because if you want red door but there is only stock of green door, then how the system should do in your opinion?
Then finially, the best way of solving your issue is to have material variant for the configurable material, like the door, you may have material variant as green door and red door, if your firmed Car is green car, then you can use green door as the firmed component, if your firmed Car is red car, then you can use red door as the firmed component, also when you do the production, you could simply produce the green door directly without configure the door, because the material variant is a stockable item but the configurable material is not, then your scenario would be very simple and there will no such problem any more.
If you do still want to keep your scenario, but don't want the system requires you enter the charateristics, then you may have to do the modification of the goods movement transaction to disable that, but it may lead to the inconsistency situation, like actually you want red door, but what you have in stock is green door, without that, you may consume the green door stock for the red door requirement, then it will mess up all the following process.
Also as you are doing the goods movement in MM transaction, so if there is user-exit could be used to change this behavior is decided by MM function, however, base on my checking there will be no such user-exit to control this behavior at MM side, because the consequnce is really dangerous for the system operation.
Therefore, I think the best way for you is still adjust your production scenario to make your production standard, then SAP system will accept that standard production scenario under your requirement.
Thanks and regards,
Rachel
Edited by: Rachel Tang on Apr 2, 2010 10:25 AM
Edited by: Rachel Tang on Apr 2, 2010 10:32 AM

Copy control settings for Multilevel variant configuration

Dear All,
I have the following scenario for variant configuration A quotation is created for configurable material with multilevel configurable material
with reference to this quoatation a sales order is created.
My requirement is that the quoatation must get copied to sales order as it is along with the values for subitems also.
In copy control settings there is a field at item level called
configuration :
In this if I maintain value
A: The variant is getting copied but the values for subitems is not getting copied the values for main material is in changable mode.
B: The variant is getting copied but the values for subitems is not getting copied the values for main material are not in changable mode.
C:The variant is getting copied   the values for subitems is getting copied the values for main material are in changable mode but the values for subitems are not in changable mode.
My requiremnt is that
The variant must get copied
the values for subitems must get copied
the main material vlaues must be in changable mode
the subitems vlaues must be in changable mode
How can I fullfill this requiremnt, has any one of you come across this scenario, Pleae provide with solution it is urgent
Informative answers will be provided maximum points.
Deepak

Hai Deepak Mehmi,
please check in T CODE VTAA
In the position check
SalesDocType : Sales order type
SalesDocType : Inquiry type
Double clcik and check
DataT 051 General header data       Copying requirements 002 Header-diff.customer
DataT 101 Header business data
DataT 001 Partner header
And Tick mark for Copy Item Number
For further check:
In Item
                                  Copying requirements 301
DataT 151 General item data                                          Pos./neg. quantity   +
                                                           Copy quantity
DataT 102 Bus.data/item compl.                                     Pricing type         G
DataT 002 Partner item                       2 Update document flow   Cont. item copy mode
                                                    Copy product select.
FPLA 251 Conditions                Configuration
                                                           Campaign Deter.
Regards,
Mani

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

Variant Configuration - Pricing issue

Similar Messages

Maybe you are looking for