Variant Configuration for coils sheets industry

Dears,
In a variant configuration for coils sheets industry with MTO, there are six production lines:
1. Pickling
2. Cold Rolling
3. Annealing
4. Skin pass
5. Galvanized
6. Coloring
Every product line manufacturing product with different characteristics:
1. Thickness
2. Surface
3. Galvanization types and concentration
4. Color concentration
How to build BOMs and Routing if every production line delivers a product to the next production line and we can sell the output of every production line.
I'm confused to use variant configuration scenario or material variant scenario.
Regards,
Ahmed Rouby

Hi Ahmed,
Variant configuration is the best option to go for,
You have six production lines means you need to create six work centers in super routing.
First create detailed product structure at each level . To build an BOM STRUCTURE follow below procedure.
In your case every production line delivers a product to the next prod line here create super BOM
FOR all 6 production lines comprising possible components for that Product. If pickling is an product then it will have cold rolling and annealing as component and as per business scenario write dependencies under which condition before pickling, coiling or annealing will be selected.
Assuming fulfilling dependencies, coiling is selected for BOM explosion.
Accordingly in coiling super BOM include annealing or skin pass or coloring as component to be selected based on dependency written likewise till raw material BOM can be build.
From FG characteristics should be flown from one
BOM component to other for that write procedures to copy thickness character value from one level to other. Prerequisite could be all characteristics should be in all six product lines class. LIKEWISE MANY BUSINESS SCENARIOS CAN BE BUILD USING PROCEDURES AND CONSTRIANTS AT DIFFERENT PRODUCTLINES.
Above details answers you’re below query:
Type: GV1, Concentration: G60, Thickness: 0.8 mm, Weight:
5 TO, Width: 1250 mm.
DC01_GV1 need a semi-finished as a variant
DC01_SK1 with characteristics:
Thickness: 0.8 mm, Weight: 5 TO, Width:
1250 mm.
DC01_SK1 need a semi-finished as a variant
DC01_NA1 with characteristics:
Thickness: 0.8 mm, Weight: 5 TO, Width:
1250 mm, Surface: Super Bright.
How I build BOMs structures as we have
configurable materials with super BOM and its variants.
Super routing can be built on each product line
with possible all operations required to manufacture it and write dependencies in this operation to be selected at a time under given character value fulfillers.
PLS REPLY HOPE SO YOUR QUERY SPECIFIC ANSWER IS GIVEN.
REGARDS AND THANKS
SANKET

Similar Messages

Variant configuration for material in sap B1

Hi,
Please explain how item variants can be configured in SAP B1 against materials like SAP R3.
Noramlly all the attributes of amaterial cannot be incorporated in material code which are to be filled at the time of transaction in sale order. Every material is associated with a class which constitutes some characteristics . Those characteristics contain some pre defined value in variant.
Please explain if there is any scope of it in SAP B1.
Regards
Indranil

Hi
There is huge gap is there between R3 and SBO. u cant expect same thing in SBO which in R3.
Basic things SBO is gud for lite manfg company, traders. if u r looking for heavy manfg company then u have to look for addons r SDk with SBO.
Basically in SBo u can segrregrate the items by one item group only, & using some properties & udfs u can make subgroups.
Pls check this thread Slightly same kind of req.:
Variant configuration for FG and SFG
Giri

Cats Configuration for time sheet upload

Dear All,
I have time sheet file now i have to upload .Kindly guide me how i can do this thing with help of CATS.I am not aware of the cats how i have to maintain the profile and field selection CAC1,CAC2.
I want to know the steps for doing the same kindly tell me it's urg.
thanks
sandeep

Hi
Create a profile in CAC1 and setup the profile settings in CAC2.
What you select in CAC2 appears in CAT2 sheet.
The CATS config is self explanatory.
R K

Variant configuration for Material for Sales Order

Hello,
I have craeted a configurable material in MM01, then created class for using CL01 , its characteristics using CT04, CU41, CT04, VK11, and lastly VA01.
But still while creating sales order it throws error :
Configuration not possible for material PEN_4 :Reason 2 --> Help
What must be the problem? Also is there any BAPI who can create configurable material?
Can anybody help on this issue.
Useful answer will be rewarded.
Thanks,
Madhura Nadgauda.
Edited by: Madhura Nadgauda on Jan 16, 2008 7:45 AM

try this may be it will help to you,.
REPORT ZVRDOC0 no standard page heading
line-size 300
line-count 50(5).
TABLES : vbak, "Sales Document Header Level
vbap, "Sales Document Header Level
kna1. "General Data in customer Master
*INTERNAL TABLE T_VBAP
DATA : Begin of t_vbap occurs 0,
       vbeln like vbap-vbeln,
       matnr like vbap-matnr,
       posnr like vbap-posnr,
       arktx like vbap-arktx,
       kwmeng like vbap-kwmeng,
       cmkua like vbap-cmkua,
       end of t_vbap.
*INTERNAL TABLE T_TAB.
DATA : Begin of t_tab occurs 0,
        vbeln like vbak-vbeln,
        kunnr like vbak-kunnr,
        audat like vbak-audat,
        netwr like vbak-netwr,
        vkorg like vbak-vkorg,
        name1 like kna1-name1,
        land1 like kna1-land1,
        end of t_tab.
*INTERNAL TABLE T_FINAL.
DATA : Begin of t_final occurs 0,
        vbeln like vbap-vbeln,
        kunnr like vbak-kunnr,
        matnr like vbap-matnr,
        posnr like vbap-posnr,
        arktx like vbap-arktx,
        kwmeng like vbap-kwmeng,
        cmkua like vbap-cmkua,
        audat like vbak-audat,
        netwr like vbak-netwr,
        vkorg like vbak-vkorg,
        name1 like kna1-name1,
        land1 like kna1-land1,
        end of t_final.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE text-bO3.
parameters : P_kunnr like vbak-kunnr.
select-options : S_vbeln for vbak-vbeln,
                 S_audat for vbak-audat.
SELECTION-SCREEN END OF BLOCK B1.
start-of-selection.
select vbeln matnr posnr arktx kwmeng cmkua from vbap
into corresponding fields of table t_vbap where vbeln in S_vbeln .
IF sy-subrc EQ 0.
select vbakkunnr vbakvbeln vbakaudat vbaknetwr vbak~vkorg
        kna1name1 kna1land1 into table   t_Tab   from
        vbak   join kna1   on kna1kunnr = vbakkunnr
        FOR ALL ENTRIES IN t_vbap
        where vbak~vbeln = t_vbap-Vbeln and
        vbak~kunnr = p_kunnr and
        vbak~audat in S_audat .
ENDIF.
*end-of-selection.
loop at t_vbap.
read table t_tab with key vbeln = t_vbap-vbeln.
move :
t_vbap-vbeln to t_final-vbeln,
t_vbap-matnr to t_final-matnr,
t_vbap-posnr to t_final-posnr,
t_vbap-arktx to t_final-arktx,
t_vbap-kwmeng to t_final-kwmeng,
t_vbap-cmkua to t_final-cmkua,
t_tab-kunnr to t_final-kunnr,
t_tab-audat to t_final-audat,
t_tab-netwr to t_final-netwr,
t_tab-vkorg to t_final-vkorg,
t_tab-name1 to t_final-name1,
t_tab-land1 to t_final-land1.
append t_final.
clear t_Final.
endloop.
sort t_Final by vbeln   Kunnr    matnr posnr .
loop at t_final.
at new vbeln.
write : /1 SY-VLINE, 2 t_final-vbeln color 5 inverse.
ULINE /1(250).
endat.
write : /1 SY-VLINE, 2 t_final-vbeln color 5 inverse,
20 SY-VLINE, 21 t_final-posnr color 5 inverse,
40 SY-VLINE, 41 t_final-matnr color 5 inverse,
60 SY-VLINE, 61 t_final-arktx color 4 inverse,
80 SY-VLINE, 81 t_final-kwmeng color 4 inverse,
100 SY-VLINE, 101 t_final-cmkua color 4 inverse,
120 SY-VLINE, 121 t_final-kunnr color 3 inverse,
140 SY-VLINE, 141 t_final-audat color 3 inverse,
160 SY-VLINE, 161 t_final-netwr color 2 inverse,
180 SY-VLINE, 181 t_final-vkorg color 2 inverse,
210 SY-VLINE, 211 t_final-name1 color 1 inverse,
230 SY-VLINE, 231 t_final-land1 color 1 inverse,
250 SY-VLINE.
at end of vbeln.
sum.
ULINE /1(250).
write: /60 SY-VLINE, 'Total' ,
81 t_final-kwmeng color 4 inverse ,100 SY-VLINE,
101 t_final-cmkua color 4 inverse,120 SY-VLINE.
ULINE /1(250).
endat.
at last.
SKIP 2.
sum.
ULINE /1(250).
write: /1 SY-VLINE, 60 SY-VLINE, 'Grand Total' ,
81 t_final-kwmeng color 4 inverse , 100 SY-VLINE ,
101 t_final-cmkua color 4 inverse,120 SY-VLINE.
ULINE /1(250).
endat.
endloop.
TOP-OF-PAGE.
ULINE /50(24).
WRITE : /50 SY-VLINE , 52 'SALES ORDER DETAILS' COLOR 5,
73 SY-VLINE.
ULINE /50(24).
ULINE .
WRITE: /10 'CURRENT DATE :', 25 SY-DATUM COLOR 1 INVERSE,
100 'CURRENT TIME :', 115 SY-UZEIT color 5 INVERSE.
WRITE: /10 'USERNAME :', 25 SY-UNAME COLOR 1 INVERSE,
100 'PAGE NO :', 113 SY-PAGNO COLOR 5 INVERSE.
WRITE: /10 'LOGON CLIENT :', 25 SY-MANDT COLOR 1 INVERSE,
100 'COLON N0 :', 114 SY-COLNO COLOR 5 INVERSE.
WRITE: /10 'CURRENT REPROT:', 25 SY-REPID COLOR 1 INVERSE,
100 'LANGUAGE :', 116 SY-LANGU COLOR 5 INVERSE.
ULINE.
ULINE /1(250).
write : /1 SY-VLINE, 2 'SALES DOC NO' color 6 inverse,
20 SY-VLINE, 21 'SALES DOC ITEM' color 6 inverse,
40 SY-VLINE,41 'MATERIAL NO' color 6 inverse,
60 SY-VLINE, 61 'SHORT SALES TEXT' color 6 inverse,
80 SY-VLINE, 81 'CUMM ORDER SALES' color 6 inverse,
100 SY-VLINE, 101 'CREDIT DATA' color 6 inverse,
120 SY-VLINE, 121 'CUSTOMER NO' color 6 inverse,
140 SY-VLINE, 141 'DOC DATE' color 6 inverse,
160 SY-VLINE, 161 'NET VALUE SALES' color 6 inverse,
180 SY-VLINE, 181 'SALES ORG' color 6 inverse,
210 SY-VLINE, 211 'CUSTOMER NAME' color 6 inverse,
230 SY-VLINE, 231 'CUSTOMER CONTY' color 6 inverse,
250 SY-VLINE.
ULINE /1(250).
END-OF-PAGE.
ULINE.
WRITE: /45 ' THIS IS END OF PAGE FOR SALES DOCUMENT DETAILS'
COLOR 6 .

Tolerance Limits for Class Character in Variant Configuration

HI all,
We are Using Variant Configuration, for this we have linked MIC's to Class character, When The Inspection Lot is created the Lower & Upper Limit in the specification comes as the character Value.it does not takes in to consedration the tolerance key assigned to it. For E.g. Charater Dia has value 20, & in the Tolerance key for 20 +/- 0.10 is maintained, when the Inspection lot is created the Upper & lower Limit comes as 20-20 instead 19.9 - 20.1
I have gone through SAP Note 210658, the sample code provided in note is for "Material Specification" I have tried the same with minor code correction the specifications in the lot comes as desired i.e. specifications in the lot consider the tolerance key.
Our Requirment is of task list, in the same not EXIT for task list is also mentioned but no souce code is provided, when we are using the above program (Used for Material Specification) after doing the desired changes, & when we run in de-bugging mode it shows all the calculations are being done, but finally in the lot specification appear as the charater value ( 20-20) & in the inspection lot One first MIC comes it delete's all other MIC's assigned in the Plan.
Has any body worked on this requirment, please let me know how to do the same, & if any body has used EXIT_SAPLQPAP_001 (Enhancement QPAP0001.)Plese provide me with the soution if any one has worked on it.
Thanks & Regards
Gaurav Behl

Hi ravi,
I did't work on class hierarachies but i do have a document regarding classification.
Regards,
Kanth

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.

BAPI or Function maodule for Variant configuration

Hi,
Is there any BAPI or Function module which can give Variant configuration for a sales order?
Thanks,
Madhu

hi
plz refer to the following code
Check the following Code & also Check the following Standard Programs
L2032U12
LCRMAU01
LCRMAU11
LZOC1U01
MWWMJF32
RBUS2032
Structures for order header
DATA: l_order_header_in LIKE bapisdhd1,
l_order_header_inx LIKE bapisdhd1x,
Tables for order items
li_order_items_in TYPE STANDARD TABLE OF bapisditm,
li_order_items_inx TYPE STANDARD TABLE OF bapisditmx,
Order partners
li_order_partners TYPE STANDARD TABLE OF bapiparnr,
*Schedule lines
li_ORDER_SCHEDULES_IN TYPE STANDARD TABLE OF BAPISCHDL,
li_ORDER_SCHEDULES_INX TYPE STANDARD TABLE OF BAPISCHDLX,
*-condition type
li_ORDER_CONDITIONS_IN TYPE STANDARD TABLE OF BAPICOND,
li_ORDER_CONDITIONS_INX TYPE STANDARD TABLE OF BAPICONDX,
Return table from bapi call
li_return TYPE STANDARD TABLE OF bapiret2,
Sales document number
l_vbeln LIKE bapivbeln-vbeln,
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
order_header_in = l_order_header_in
order_header_inx = l_order_header_inx
testrun = 'X'
IMPORTING
salesdocument = l_vbeln
TABLES
return = li_return
order_items_in = li_order_items_in
order_items_inx = li_order_items_inx
order_partners = li_order_partners
ORDER_SCHEDULES_IN = li_ORDER_SCHEDULES_IN
ORDER_SCHEDULES_INX = li_ORDER_SCHEDULES_INX
ORDER_CONDITIONS_IN = li_ORDER_CONDITIONS_IN
ORDER_CONDITIONS_INX = li_ORDER_CONDITIONS_INX.
Thanks & Regards
ravish
* plz rewrd points if helpful

Why don't we do the confirmation in variant configuration?

Hello guys,
As far as i know that in variant configuration we don't do the confirmation, we directly do the goods receipt.Is it right?If yes than why?
Following are the steps we do while doing the variant configuration scenario:
1)First we create the characteristics and give the values inside it.
2)Then we create the class of class type 200 and give characteristics defined in it.
3)Then we create the variant of class type 300 and give all the characteristics inside it.
4)Now we create the configurable material with Basic data 1,2, MRP 1,2,3,4 , Classification view ,workscheduling view.
In classification view, we give the variant of class type 300.So it shows all the characteristics and its value over there.There we select all the values.
5)Now we create the super bom of configurable material and in class tab we give all the classes of class type 200.Here even we can maintain the dependencies if we define all the characteristics value in item tab.
6)Then we create the super routing and inside it we give all the possible operations inside it.Right now my routing contains operations which are necessary all the times.
7)Then we create the configurable profile for configurable material of class type 300.
8)Now we give the requirement in md81 for configurable material and there we select the characteristics values which we want.
9)After that we run the mrp for configurable material and it generates procurement proposals(planned order) for it.
10) Afer this we convert this planned order into production order and release it and save it.
11) After this we do the goods receipt for the production order in mb31.Because of this it shows the stock of sales order as production order qty.
This procedure my tutor has taught me.Have i missed any steps or am i wrong somewhere?If that the case than plz guide me.

if you can generate a production order then you can always confirm it according to SAP PP logic.
we use variant configuration for the manufacturing of complex products. once the component quantities and
operation are selected for a particular variant and copied to Production order, the rest of the process is same
as normal Production Control. Revert back with any queries you have.
Regards,

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

Using ALE to synchronize Variant Configuration data from Production to Dev

SAP Gurus,
We are trying to move away from opening our production environment every time with need to add new Variant configuration for products.
In order to do so, we need to ensure that our development and staging systems are in line with production LO-VC data. We have been looking at a possible ALE solution but I would like to get other suggestions.
Any thoughts you may have with regards to either pros and cons of ALE, or another solution we may have overlooked. If your clients are transporting Variant Configuration to production, what method are they currently using to ensure data consistency between environments.
Our landscape currently has two production environments for two separate business lines but both use LO-VC therefore we would like to standardize the process.
Thanks and Regards,
Kevin Webb
SAP SD Senior Consultant

Hi Webb,
General its a complex process to transport VC but for system consistency you can:
1. do the changes Manually in each system
2. Use ALE idoc process to transport.
But ALE transport generally used for fresh VC transport, if the VC already present in transporting system, it may cause inconsistency. Hence if you want to transport some changes then I can suggest you to do MANUALLY.
But if you are transporting VC freshly in each system, go for ALE.
try and revert

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 Configurator - Configurable Material in SAP.

Hi,
Is there a BAPI/Function Module / API available to validate a configurable material with all the possible characteristics / classes.
Thanks,
Tanuj

Hi
There is huge gap is there between R3 and SBO. u cant expect same thing in SBO which in R3.
Basic things SBO is gud for lite manfg company, traders. if u r looking for heavy manfg company then u have to look for addons r SDk with SBO.
Basically in SBo u can segrregrate the items by one item group only, & using some properties & udfs u can make subgroups.
Pls check this thread Slightly same kind of req.:
Variant configuration for FG and SFG
Giri

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 configurator BAPI

I need to find a BAPI for the variant configurator for a sales order. To further explain, if you go to VA03 and view a sales order. Then highlight a line item and click on the "Item Details: Configuration" icon (last one on the right under the line items). I need to, somehow, relate a the line item to these characteristics (variant configurator).
Regards,
Davis

VC_I_GET_CONFIGURATION

Variant Configuration for coils sheets industry

Similar Messages

Maybe you are looking for