SO BOM or Variant Configuration or Other for Technical Sale

Dear Community,
I would like to ask you and advice on this.
In a Plastic Packaging Industry with lots of different products but very similar at the same time, production is triggered after the customer order.
To me it sounds very logical to use Variant Configuration scenario to specify product details which define its components and operations. Nevertheless the Sales People are don't have the enough knowledge to define completely the product and need a Technical Area to define key information to complete the product. before sending sales order (or quotation) to customer.
Which scenario would you use ? And most important: how would you use it to integrate the customer requirement information with technical data from experts?
Thank you in advance,
Best Regards,
Sebastián Ligueros

Hi Mario and the rest of community, I wish you a Happy New Year!
Answering the questions: The product is engineered specifically for the customer and is possibly (not always) subject to change in every sales order.
The first requirement from customer goes to sales department. If the product is new there is lot of joint woirk with technical area to develop the particular product and then send the quotation to the customer when most of the processes and components are defined. Product can be further specified in the sales order. If the product has been already sold in the past, sales department send quotation/sales order taking as reference a previous one maybe changing one or two elements like graphic design.
In this interaction between the sales department requirement and technical area for product development at "preparation for quotation level" and then for sales order I would like to know in your opinion which would be the best scenario.
Thank you,
Sebastián Ligueros

Similar Messages

Production Order BOM with Variant Configurable Material

Hi,
I have a requirement to process the document items in the Production Order BOM for a variant configurable martial. I am not sure which Function Module will do this purpose. I checked the FM: CS_BOM_EXPL_MAT_V2 and does not seem to be working.
Can you please help me with a suitable Function Module or program that will process the Production Order BOM? Appreciate Your Help.
Thanks,
Kanan
Edited by: Kannan SA on Jul 6, 2011 8:59 PM

What are you doing with the characteristics right now ?
If you want operations selected based on characteristic values, you need to have dependencies written just like you do (or in your case, will do) in your BOM components.
I understand the business-push to not do things 100% at the start and just "oh we'll add that part later" but I would really push back to get that part included initially.

Super BOM in Variant configuration

Hi SAP gurus,
Can anyone tell me the difference between Variant configuration and Super BOM, if possible with an example.
And also please forward any information on configuring the Super BOM.
Thanks & regards,
Praveen Kumar,
[email protected]

Hi,
For super BOM u need to do do the following configurartion settings.
1. For Min item pricing go to VOV7 and select TAQ , go to structure scope and keep B(Explode Multi BOM)
2. then go to v0v4 do the settings
         OR ERLA TAQ
         OR NORM TAQ TAE
         OR NORM TAE   TAE
3. Maintain the records in CS01.
Regards,
Sree

Variant Configuration - product validation step at sales order

Hi all,
By using Variant Configuration, new products can be created at sales order entry ==> is there any way to put a validation process in place where a number of checks (by different people) should be performed before being able to save the order?
thanks
Bart

Hi Vineet,
Thanks for your answer.
I realize dependencies can help control which characteristics value can be choosen. In the meantime my question became; how I can prevent that my sales order gets visible for the planning department (typically they would look in transaction MD04 I guess)? I will post this question under the appropriate topic.
This is the type of flow I have in mind:
customer service fills in the order, specifies the values for the characteristics, Availability check runs and the order is saved
order is saved but not confirmed so it is not transferred to planning
planning (or other department like production) checks the order and the variant. If it is ok, they will confirm the order so it gets to the planning. If not, they will get in contact with customer service.
I'm not experienced in availability check, planning, etc so I might have written big mistakes here.
Kr,
Bart

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

Multilevel variant configuration without BOM explosion

Hi!
We have the following problem:
We use BOMs with variant configuration in SD and NO BOM explosion. Means, enter the BOM-head material in the SD line, go to the configuration screen and configure the multilevel BOM. There are classes and attributes on every level in the multilevel BOM structure.
After finishing the variant configuration, we save the SD order. If we enter the new SD order again with VA03 and go to the configuration of the SD line, the system forgot every attribute value on levels other than the BOM-head. We see the structure of the selected BOM materials, but no previously entered configuration value on other levels.
Do we make something wrong, or is this a SAP standard "feature" ?
Thanks,
Richard

Hi,
This is a standard feature.The values which you will select for the configurable material,you will not able to see when you got to VA03.
Reward points if helpful.
Regards,
Amrish Purohit

Variant Configuration - Order BOM problems

Good morning,
I am having problems regarding the Order BOM in variant configuration. I have maintained the configuration profile as follows:
CONFIG PARAMETERS
Ordem BOM
Result oriented
Multilevel
BOM application - SD01
ORDER BOM
Maint. in order allowed - checked
Automatic fixing - checked
I have also maintained a BOM, for usage '5 - sales and distriburion', with the selection conditions at the object dependencies.
When I test the results in CU50, assign all characteristics and push the button "Engineering" the icons for manual maintenance appear correctly in the screen...BUT when I raise the actual order, the icons are gone, therefore I cant add or delete items of the selected BOM.
Any ideias of how to fix that?
Thanks in advance.
Adriano Cardoso

Note 303446
Note 901452
composite Note 774346
Please refer to above notes. Hope it helps
Regards
Sai

BOM explosion using variant configuration

Hi
I have a material (LAPTOP) and it has two BOM(RAM and HARD DISK).
LAPTOP is my main material.
Through VA01, when I try creating a Sales Order, I give the Material as LAPTOP and when I click "Configuration" menu, I will be showing the Variant Configuration Characteristic values for this material (LAPTOP) namely RAM and HARD DISK.
When I select them and come back to VA01 scree, I could see both the sub materials (RAM and HARD DISK).
But my question, I want to see only the one which I select. If I select RAM, then only RAM shoudl be displayed in my sales order not HARD DISK.
I have created the Characteristics as "Multiple Value" assignmetn
Please help.
Thanks in Advance,
Priya

Hi Priya,
Use Dependency concept ,to achieve your requirement.
Regards,
Subash.

Copy Order Bom in Two-Step Variant Configuration

Dear Community,
In Multilevel VC Order Bom Scenario. Configuration is made for the first level by sales department, then further levels are configurated by Technical Department.
If the sales document is a quotation and then we want to create de sales order with reference to the quotation, only the configuration for the first level is getting copied. All the characteristics of the lower level configurable materials appear in blank, as well as selected class items in quotation as well as manually added components.
Is there a way to copy the whole order bom of the original document or the characteristics value for every level?
Thank you
Sebastián Ligueros

Hi Rahul,
Basically , an order bom doesnot explode therefore you cannot configure any of the components.Please review note 303446
By changing the default value of the variable GV_FORCE_BOM_EXPLOSION_ASL in Include LCUKOFBE, you can force the explosion of the order BOM in the sales order.As a result, subordinate items of the order BOM are configured provided that these items were not fixed.I
Therefore please set this variable GV_FORCE_BOM_EXPLOSION_ASL to X and retest,
Thanks
Amber

Variant configuration BOM

Hi
Please tell me type of BOM in Variant Configuration? When and where it should use. ?
How to comfigured ?

close

Creation of sales order with Variant configuration info

Hi friends,
   I am creating sales order along with Variant configuration data. We have 3 level BOM structure.
I am using BAPI_SALESORDER_CREATEFROMDAT2 and filling in ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_PART_OF ORDER_CFGS_VALUE, ORDER_CFGS_REFINST
tables exactly the same way BAPISDORDER_GETDETAILEDLIST FM returns.
Sales order is being created with no variant configuration information.(Not in the header level atleast)
Can any one help me on this.
Thanks
Seshagiri

Updating Variant Configuration data for SO item became little tricky for us in an ongoing implementation. After spending some hours investigating the correct combination of data to pass, we were able to post the document correctly. As no detailed documentation is available online for this scenario, I hope this post will help community for similar requirements. J
For updating Variant configuration (VC) data for Sales order item, we need to populate below tables of standard FM or BAPI (e.g. SD_SALESDOCUMENT_CREATE).
Normally the standard FM or BAPI does not return any error messages in case configuration data is not updated successfully.
·         SALES_SCHEDULES_IN: The required date field should be populated with appropriate value (REQ_DATE).
·         SALES_ITEMS_IN: Field PO_ITM_NO should be populated with appropriate value.
·         SALES_CFGS_REF Table:
1.       This table should have 1 record per item.
2.       Combination of CONFIG_ID and ROOT_ID should be unique across line items.
POSEX
000010
CONFIG_ID
000001
ROOT_ID
00000001
SCE
1
COMPLETE
T
CONSISTENT
T
CBASE_ID_TYPE
G
·         SALES_CFGS_INST:
1.       This table should have 1 record per item.
2.       Combination of CONFIG_ID and INST_ID should be unique across line items.
CONFIG_ID
000001
INST_ID
00000001
OBJ_TYPE
MARA
CLASS_TYPE
300
OBJ_KEY
MATNR value
QUANTITY
Quantity value
QUANTITY_UNIT
Quantity Unit
COMPLETE
T
CONSISTENT
T
OBJECT_GUID
MATNR value
PERSIST_ID_TYPE
G
·         SALES_CFGS_VALUE:
1.       Combination of CONFIG_ID and INST_ID should be unique across line items.
2.       We can have multiple characteristics for a material. In that case appropriate records should be inserted in this table. Note that CONFIG_ID and INST_ID should be same for all the rows you insert in this table for multiple characteristics for a material.
3.       The characteristic value should be in SAP internal format.
CONFIG_ID
000001
INST_ID
00000001
CHARC
Material characteristics
VALUE
Material characteristics value
·         SALES_CFGS_VK:
1.       Combination of CONFIG_ID and INST_ID should be unique across line items.
2.       We can have multiple characteristics for a material. In that case appropriate records should be inserted in this table. Note that CONFIG_ID and INST_ID should be same for all the rows you insert in this table for multiple characteristics for a material.
CONFIG_ID
000001
INST_ID
00000001
VKEY
Material characteristics

Class & Characteristics in variant configuration

Hi PP guru's
Pl explain me in detail all the configuration path , spro , tcode for the above said .
thanx in advance
Regards,
Vimalbalaji

Dear Vimalbalaji,
<a href="http://www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm">Steps for SD Variant Configuration</a> :
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.
<a href="http://help.sap.com/saphelp_ides/helpdata/en/0a/857463c87611d1a7760000e8a5f6c8/content.htm">SAP Help Link for Variant Configuration for an Order BOM</a>.
<a href="http://www.sap-basis-abap.com/sd/steps-for-variant-configuration-and-pricing.htm">Steps for Variant Configuration and Pricing</a>
$ROOT is the highest-level configurable material in a configuration.
$PARENT refers to the object immediately above $SELF in a multi-level configuration.
The variable $PARENT has no meaning for the header material, because the header material has no superior materials.
In dependencies that are allocated to BOM items, $PARENT refers to the configurable material for which the BOM was created, whereas $SELF refers to the material of the BOM item.
$SELF is the material to which the dependency is allocated.
Regards,
Naveen.

Variant Configuration $Root $Parent $Self

Hi Gurus
Please help in providing information on Variant Configuration $Root $Parent $Self, and if possible with some test cases..to make it as a base for exploring.
Thanks in advance.
Points will be rewarded.
Regards
Suddu

Dear Suddu,
$ROOT is the highest-level configurable material in a configuration.
$PARENT refers to the object immediately above $SELF in a multi-level configuration.
The variable $PARENT has no meaning for the header material, because the header material has no superior materials.
In dependencies that are allocated to BOM items, $PARENT refers to the configurable material for which the BOM was created, whereas $SELF refers to the material of the BOM item.
$SELF is the material to which the dependency is allocated.
<a href="http://help.sap.com/saphelp_ides/helpdata/en/0a/857463c87611d1a7760000e8a5f6c8/content.htm">SAP Help Link for Variant Configuration for an Order BOM</a>.
<a href="http://www.sap-basis-abap.com/sd/steps-for-variant-configuration-and-pricing.htm">Steps for Variant Configuration and Pricing</a>
<a href="http://www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm">Steps for SD Variant Configuration</a> :
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.
Regards,
Naveen.

Variant configuration with Sales order?

Dear SAPIENTS,
I require variant configuration scenario in case of sales order, batch mangement, MRP, production order.
Regards,
Kaushal Rai
Edited by: Kaushal Rai on Feb 27, 2009 2:06 PM

Dear,
Follow these steps.
1. Create the Characteristics in CT04.
2. Create the Class in CL02. (Class type 300)
3. Assign the characteristics to the above created class.
4. Create the material (Product) in MM01 with material type KMAT.
5. Assign the Class created in Step 2 to Classification view of Material.
6. Create the configuration Profile in CU41. to the necessary setting to in it.
7. Write the dependencies (Precondition, sele, procedure) in CU01.and Create Dependency net in CU21.
8. Assign sele, procedure, Dependency net in Configuration Profile.
9. Assign Preconditons to Chracteristics or Char values in Class.
10. Check the model in CU50. whether your depencies or working file or not.
11. Create the Supr BOM and Super Routing and attach the dependences in the respective and check whether your bom components and required operations are picking or not in CU50.
12. VK11 - Enter VA00 (Condition) For Std RVA001 Pricing Procedure.
Please refer this thread,
variant configuration
http://www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm
Regards,
R.Brahmankar

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

SO BOM or Variant Configuration or Other for Technical Sale

Similar Messages

Maybe you are looking for