Populating Variant COnfiguration value in ORDERS05

Hi,
I'm going to create Sales Order using ORDERS05 IDoc Type.Data coming from Non-SAP system consists of Variant Configuration data.I mean those data we have to place at the Item Level variant configuration area.Can anybody please tell me which segment I've to populate for the same? or if there is no segment for that then how we can achieve this........Is there any exit for the same?
Thanks in advance,
Sarbajit

Hi Sarbajit,
There is a segment need to fill the structures XE1CUREF or XE1CUCFG (IDOC).For this pass characteristic name and it is values.In va01 if you seen it will pass description and it is value.I did this before and created order and quotation.
ORDER_CFGS_REG
    POSEX              000010
     CONFIG_ID          000001
    ROOT_ID            000001
ORDER_CFGS_INST
    CONFIG              000001
    INST_ID            000001
    OBJ_TYPE            MARA
    CLASS              300
    OBJ_KEY             CONFIG-MATERIAL
CONFIG_ID          000001
     INST_ID            000001
    CHARC              'TURRET'
    VALUE              1.
pass in this way to three structures.These are mandatory to fill if you have any issues please post.
Regards,
Madhu.

Similar Messages

PO EDI - How do I exclude a specific variant configuration value

Hello,
When sending POs via EDI we include our variant configuration values (segment E1CUCFG/E1CUVAL). There is one specific variant configuration we don't want to include as it's irrelevant to the vendor and keeps confusing them. We do need to send all the other variant configuration values. What would be the best way to do this?
Thank you,
Michael

Never mind, I found it.
MM06E001 / EXIT_SAPLEINM_013 allows me to modify E1CUVAL.

Variant Configurator : Value set by user or dependency ?

Hi,
How can i determine whether a value in a characteristic in the variant configurator is set by a user or by a dependency ?
with regards
Erik

Hi,
When a variant is created , inthat particular screen, theres an option
Whether it is cretd by user or system.
And table name is RSVAR
field is TRANSPORT
Thanks,
Shreya

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

Copying Variant Configuration across sales order items

Hi,
We are working with SAP 4.7.
I have a requirement to default the variant configuration values entered within line 1 of the sales order entry process on to subsequent lines. i.e. defaulting initial values for the configuration.
Our users have to enter many variant line items on a sales order and within an individual order the variant characteristics will be very similar, therefore by defaulting these values to be the same as the previously entered line would be a considerable overhead saving.
However I am having difficulty accessing the variant values which have been entered in the first line item. I have looked at userexit_move_workarea_to_sdwa and userexit_get_field_from_sdcom, however I don't know if I am heading in the right direction. Any advice appreciated.
Thanks for your time.

We are doing this with main-positions and subpositions. The sales clerk enters the main Position with all the characteristics, switches to the tab "Fast data entry" types in the main position, he wants to copy from and the material. There is a dependency which calls a function module which does the real work.
This works with 4.6B in 4.7 there is a psotion type global position which acts similiar.
Ok, now the code:
Dependency
pfunction Z_SD_WERTE_CHARACTERICS
(SD_VBAP_UEPOS         = SD_VBAP_UEPOS,
   STAERKE           = $self.STAERKE,
   BREITE              = $self.BREITE)
/code
CALL FUNCTION 'Z_SD_INHERITANCE'
     EXPORTING
          GLOBALS        = globals
     TABLES
          QUERY          = query
          MATCH          = match
     EXCEPTIONS
          FAIL           = 1
          INTERNAL_ERROR = 2
          OTHERS         = 3
/code
Z_SD_INHERITANCE
DATA: h_uepos LIKE vbap-uepos.
DATA: x_values TYPE ibco2_value_rec OCCURS 0 WITH HEADER LINE.
FIELD-SYMBOLS:
-values.
    ENDLOOP.
ENDIF.
*-- Ausgabeverarbeitung
LOOP AT match WHERE atcio = 'O'.
*-- Konvertierung ATINN auf ATNAM
    SELECT SINGLE * FROM cabn WHERE atnam = match-varnam.
    CHECK sy-subrc EQ '0'.
    READ TABLE x_values WITH KEY atinn = cabn-atinn.
    IF     sy-subrc IS INITIAL AND
       NOT x_values-atwrt IS INITIAL.
      match-atwrt = x_values-atwrt.
    ELSEIF sy-subrc IS INITIAL AND
       NOT x_values-atflv IS INITIAL.
      match-atflv = x_values-atflv.
    ENDIF.
    match-atfor = cabn-atfor.
    MODIFY match.
ENDLOOP.
ENDFUNCTION.
/code
Kind regards
Matthias Kabel

ATP Check for Components for Variant Configuration

Hi Gurus,
Does it exist a way to perform the ATP Check for components (in variant configuration) like in a test?
I mean, I know that when I create a SO (with the correct settings) the system will perform the ATP Check for components (Missing parts list). But is it possible to do this without trying to create the SO? Maybe a tcode as CU50 or PMEVC where I could enter the variant configuration values, then it explodes the BOM and do the ATP Check (as a simulation).
Thanks in advance.
Best regards.

Hi Christopher,
If you enable the "Component Availability" within your configuration profile (under Confign initial screen, Confign Parameters), then you will see an additional option within CU50 while configuring. By pressing this button, you can see an availability check as of the date specified on the CU50 initial screen. You can also modify the quantity on the CU50 initial screen for a more realistic simulation of a sales order (where a customer may order more than one of a product). See screenshots below:
In CU42:
In Value Assignment of CU50:
Hope this helps!

SD Variant Configuration - characteristic value computation

Hi Everyone
Greetings from Vinod
i am creating a variant material which has 3 characteristics. out of the 3 characteristics, 2 are inputed by the user and the third characteristic needs to be populated with the difference of the 2 chatacteristic values that we have entered before. is there a standard setting that we have to maintain, or should we do a custom development on the same. the third characteristic value which is computed based on the difference of the precious two characteristic will then derive pricing of the variant material. please throw some suggestions and inputs in this discussion.

Hi,
calculating values of characteristics is done with so-called dependencies.
In a dependency you can define the rule how a value should be calculated.
You have to create a class of class type 300 and assign your characteristics to this class.
Assign the class to a material of material type "Configurable Materials".
Open the material with transaction PMEVC (Modeling Environment for Variant Configuration).
There you maintain a dependency of type procedure.
The source code may look like this for your example:
$SELF.CHARACTERISTIC_3 = CHARACTERISTICS_1 - CHARACTERISTIC_2
You can find details for variant configuration on help.sap.com:
http://help.sap.com
-> SAP ERP
-> SAP ERP Central Component
-> Logistics
-> Logistics - General
-> Variant Configuration (LO-VC)
Details on transaction PMEVC (Modeling Environment for Variant Configuration):
http://help.sap.com
-> SAP ERP
-> SAP ERP Central Component
-> Logistics
-> Logistics - General
-> Variant Configuration (LO-VC)
-> Modeling Environment for Variant Configuration
Information on dependencies:
http://help.sap.com
-> SAP ERP
-> SAP ERP Central Component
-> Logistics
-> Logistics - General
-> Variant Configuration (LO-VC)
-> Dependencies
and
-> Dependency Syntax: General Rules
Best regards,
Sebastian

VC Variant Configurator SD; changing values by FM    'CUOV* '

Hi everybody,
It appears me some troubles with VC when I try to set value for particular feature again.
I have inconsistency fault when I try to change the value by calling FM 'CUOV_SET_FUNCTION_ARGUMENT' from configuration profile but it was set manually by user first (in standard VC window).
Both values of feature are correct (old and new).
Error looks like :
E: Inconsistent values inferred for characteristic (here is number of characteristic)
and next in details:
The following values are incompatible with each other:
(here is old value)
(here is new value)
Let me also know you, that this inconsistency problem exits in case when I try to overwrite feature value by FM I mentioned, and this value was set manually first only ( VC window)
If I try to owerwrite the feature manually (using the same value) - there is OK.
I suppose, I should in "any way " clear values which was set manually first, or change "something" in SAP Variant Configurator what let me change priority and allows overwrite value by FM which was set first manually ( in VC window) . But I have no idea how to do it...
I will be gratefull for any hints.
Thanks & Regards
Tomas

Standard SAP does not let you overwrite a value that is flagged as "Set by User". We had a similar requirement where we had to force a user-entered value to be deleted and replace it with a calculated value. To get around the issue, we copied the code from FM CUPR_DEL_VAL, which deletes values set by procedure, into our own FM called Z_VC_CUPR_DEL_VAL. In our version of the code we inserted a couple of statemtents that delete both user-entered values and values that were set as a default.
The great part about this mod was that we didn't even have to create our copy of the module inside of the CUPR function group. It worked fine if we just created in one of our custom function groups.
These were the lines we added to the end of the module after we copied:
KNTYPE = 'DI'.
PERFORM DDB_DEL_VALS_BY_KNTYPE(SAPLCUDB) USING INSTANCE ICABN-ATINN
                                                 RFLAG KNTYPE RESULT.
KNTYPE = 'SF'.
PERFORM DDB_DEL_VALS_BY_KNTYPE(SAPLCUDB) USING INSTANCE ICABN-ATINN
                                                 RFLAG KNTYPE RESULT.

Characterstic Value Length - Variant Configuration.

Hello,
I am defining Characterstics to be used in Variant Configuration.
SAP is limiting the maximum length of the characterstic value only to Max of 30 chars.
I have certain scenarios where the Value for a certain characterstic may be
more than 30 characters.
Is there any way to overcome this in SAP. I am sure this kind of issue might have arised in any of your projects.
Can you please share your expertise to overcome this situation.
Thanks in Advance,
Best Regards,
Bharat.

No. Your limited to the 30 characters. You should try to figure a way to either abbreviate the values or split the single charac. into multiple charac. if possible.
Depending on how your planning to use the info there are some things you can do.
You can allow multiple values and additional values. Then you can type as many "lines" of text that you want. Start each new entry with a number. As in
1 This is text to 30 characters
2 This liine is more text to 30
3 This line is a 3rd line
etc..
You need the numbers other wise I believe SAP will sort the values alphabetically and can present them in a different order when shown in display.
I have also created multiple characteristics for this as well
CHAR_TEXT_1
CHAR_TEXT_2
CHAR_TEXT_3
We can then type in short text info as a value in the class and mark it as the default text so it defaults onto each new batch. I've used this to put short segments of text on COA's. The characteristic description is set to what ever we want to display on a the COA. So it might wind up something like:
WARNING: Wear OSHA approved respirator.
WARNING: Wear latex gloves
Craig

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

Auto populate variant characterstics values in sales order

Hi Sapients,
we are trying to configure variant configuration at sales order level. We have created several characterstic and assigned it to class. Now some of the characterstics will be fixed at material level and some of the characterstics are dependent on the values supplied by the user in sales order. we have created characterstics like grade, profile, size, length, tdc number , tdc date, tdc customer, hardness, composition etc and assigned it to class salesspec ( class type 300 ).The characterstics like profile, grade, size, length are entered in the material master itself.
TDC related details like tdc no, tdc date, tdc customer, hardness, composition will be entered through a ZPROGRAM and the details will be stored in ZTABLE (ZTDC) where TDC number wll be the primary key and the respective details will be stored here.Now when we create sales order, after entering the material and clicking on variant configuration, the configuration screen comes up where the user will enter the appropriate TDC number . based on the TDC no entered by the users , the other dependent values like TDC date, tdc customer, hardness, chemical composition needs to be automatically populated in the sales order variant configuration screen .
Please guide me how to resolve this issue. shall i create dependency based on TDC no. In dependecy what is the code i have to write . Please elaborate in detail as i dont have idea on dependency.
Is it possible through user exit.
Thanks

Starting right is the first significant step. Looking at the answers to my questions, I think your industry certainly needs VC as also righty figured out by you. VC is a long way to go, and in my opinion you will need good experts handle this situation. In VC you will discover thatt there are 10 different ways to achieve the same outcome, but what matters is which solution you choose. This will depend upon a oot of factors during producg modelling, cutting the classification system, bulding configuration profiles, etc.
To give you a guideline:
1. You have 2 situtations MTO and MTS. MTO is 100% configurable material and MTS is where your KMAT will be replaced by an SKU (stock-kept-unit). For this you should emply variant type matching functionality. It's explained in SAP LO-VC help. Let me know if you do not have it.
2. For MTO you build classification system thoroughly to classifiy your products accordingly. This also involves creation of cstics. Ensure that you don't want to create cstics you will need to abondon in future.
3. To answer your question in the post: Steps involved in VC are:
a. create cstics, assign them to relevant class (type 300)
b. assign class to material CL20N or in configuration profile.
c. create configuration profile for material CU41 and write your object dependency (OB type = procedure)
d. In your OD (procedure) employ a table, say ZTDC. This is not ABAP table but a variant table created via CU61 and values maintained in CU60
e. your code in OD may look like this:
TABLE ZTDC
(TDC_NO = TDC_NO,
TDC_DAT = $SELF.TDC_DAT,
TDC_CUST = $SELF.TDC_CUST,
TDC_HRD = $SELF.TDC_HRD)
Here, TDC_NO is the key field you should define while table creation and when this is keyed in by users the other elements get determined autmoatically as per the varaint table.
Hope this helps. Let me know if you face any issues. Thank you.
- Nikhil.

BAPI/FM in ECC to create a sales order with variant configurable material

Hi all,
I need to create a function module that creates a sales order in ECC with a variant configurable material.
can some one tell me if there is a in built function module or BAPI that i can make use of to create a sales order with variant configurable material in ECC.
Regards,
Jessica Sam

Thanks MxG,
I dont know how to use this BAPI. .Can you suggest me a sample code.
My reqmnt is, i have
Sold to party, ship to party, bill to party , VC config material and all char values that should be populated while creating a sales order.
please help me with what values should i populate in i/p paramters and and how to use this BAPI with some sample code if posible.
Regards,
Jessica.

How to Create Sales Order using BAPI with Variant configurations

Hi All,
I need to create a sales order using BAPI BAPI_SALESORDER_CREATEFROMDAT2 with Varaint confiugartions. I will get Header ITEM and variant configuration items in the flat file. Kindly help me in this regard.
One more thing, is there any way to findout all the Varaint classifications for a particular Material?
I have done the below coding. Sales order is getting created but variant configurations are not populating.
*...Configuration: Reference Data
DATA: gt_order_cfgs_ref TYPE TABLE OF bapicucfg,
      wa_order_cfgs_ref TYPE bapicucfg.
*...Configuration: Instances
DATA: gt_order_cfgs_inst TYPE TABLE OF bapicuins,
      wa_order_cfgs_inst TYPE bapicuins.
*...Configuration: Part-of Specifications
DATA: gt_order_cfgs_part_of TYPE TABLE OF bapicuprt,
      wa_order_cfgs_part_of TYPE bapicuprt     .
*...Configuration: Characteristic Values
DATA: gt_order_cfgs_value TYPE TABLE OF bapicuval,
      wa_order_cfgs_value TYPE bapicuval.
*...Configuration: BLOB Internal Data (SCE)
DATA: gt_order_cfgs_blob TYPE TABLE OF bapicublb ,
      wa_order_cfgs_blob TYPE bapicublb.
*...Configuration: Variant Condition Key
DATA: gt_order_cfgs_vk TYPE TABLE OF bapicuvk,
      wa_order_cfgs_vk TYPE bapicuvk.
*...Configuration: Reference Item / Instance
DATA: gt_order_cfgs_refinst TYPE TABLE OF bapicuref,
      wa_order_cfgs_refinst TYPE bapicuref.
*...Configuration: Reference Data
wa_order_cfgs_ref-posex = '10'.
wa_order_cfgs_ref-config_id = '1'.
wa_order_cfgs_ref-root_id = '1'.
wa_order_cfgs_ref-SCE = '1'.
wa_order_cfgs_ref-CBASE_ID_TYPE = 'G'.
wa_order_cfgs_ref-CONSISTENT = 'T'.
wa_order_cfgs_ref-COMPLETE = 'T'.
APPEND wa_order_cfgs_ref TO gt_order_cfgs_ref.
*..2nd item
wa_order_cfgs_ref-posex = '20'.
wa_order_cfgs_ref-config_id = '2'.
wa_order_cfgs_ref-root_id = '1'.
wa_order_cfgs_ref-SCE = '1'.
wa_order_cfgs_ref-CBASE_ID_TYPE = 'G'.
wa_order_cfgs_ref-CONSISTENT = 'T'.
wa_order_cfgs_ref-COMPLETE = 'T'.
APPEND wa_order_cfgs_ref TO gt_order_cfgs_ref.
*...Configuration: Instances
wa_order_cfgs_inst-config_id = '1'.
wa_order_cfgs_inst-inst_id = '1'.
wa_order_cfgs_inst-obj_type = 'MARA'.
wa_order_cfgs_inst-class_type = '300'.
wa_order_cfgs_inst-obj_key = '2021B'.
wa_order_cfgs_inst-quantity = 1.
wa_order_cfgs_inst-PERSIST_ID_TYPE = 'G'.
wa_order_cfgs_inst-CONSISTENT = 'T'.
wa_order_cfgs_inst-COMPLETE = 'T'.
APPEND wa_order_cfgs_inst TO gt_order_cfgs_inst.
*..2nd item
wa_order_cfgs_inst-config_id = '2'.
wa_order_cfgs_inst-inst_id = '1'.
wa_order_cfgs_inst-obj_type = 'MARA'.
wa_order_cfgs_inst-class_type = '300'.
wa_order_cfgs_inst-obj_key = '2021B'.
wa_order_cfgs_inst-quantity = 1.
wa_order_cfgs_inst-PERSIST_ID_TYPE = 'G'.
wa_order_cfgs_inst-CONSISTENT = 'T'.
wa_order_cfgs_inst-COMPLETE = 'T'.
APPEND wa_order_cfgs_inst TO gt_order_cfgs_inst.
*...Configuration: Characteristic Values
wa_order_cfgs_value-config_id = '1'.
wa_order_cfgs_value-inst_id = '1'.
wa_order_cfgs_value-charc = 'BASIC_MACHINE'.
wa_order_cfgs_value-value = 'L28'.
wa_order_cfgs_value-VALCODE = '1'.
APPEND wa_order_cfgs_value TO gt_order_cfgs_value.
wa_order_cfgs_value-config_id = '1'.
wa_order_cfgs_value-inst_id = '1'.
wa_order_cfgs_value-charc = 'BUCKET'.
wa_order_cfgs_value-value = 'PL1001'.
wa_order_cfgs_value-VALCODE = '1'.
APPEND wa_order_cfgs_value TO gt_order_cfgs_value.
*..2nd item
wa_order_cfgs_value-config_id = '2'.
wa_order_cfgs_value-inst_id = '1'.
wa_order_cfgs_value-charc = 'BUCKET_FOC'.
wa_order_cfgs_value-value = '023OP0049'.
wa_order_cfgs_value-VALCODE = '1'.
APPEND wa_order_cfgs_value TO gt_order_cfgs_value.
wa_order_cfgs_value-config_id = '2'.
wa_order_cfgs_value-inst_id = '1'.
wa_order_cfgs_value-charc = 'BUCKET_HOE'.
wa_order_cfgs_value-value = '028MS0004'.
wa_order_cfgs_value-VALCODE = '1'.
APPEND wa_order_cfgs_value TO gt_order_cfgs_value.
wa_order_cfgs_value-config_id = '2'.
wa_order_cfgs_value-inst_id = '1'.
wa_order_cfgs_value-charc = 'TYRE_PRESSURE_GAUGE'.
wa_order_cfgs_value-value = '81004402'.
APPEND wa_order_cfgs_value TO gt_order_cfgs_value.
*...Configuration: Reference Item / Instance
wa_order_cfgs_refinst-posex = '10'.
wa_order_cfgs_refinst-config_id = '1'.
wa_order_cfgs_refinst-inst_id = '1'.
APPEND wa_order_cfgs_refinst TO gt_order_cfgs_refinst.
*..2nd item
wa_order_cfgs_refinst-posex = '20'.
wa_order_cfgs_refinst-config_id = '2'.
wa_order_cfgs_refinst-inst_id = '1'.
APPEND wa_order_cfgs_refinst TO gt_order_cfgs_refinst.
Regards,
Rajesh

Hi all,
Please help me in solving the issue.
Rajesh

Material Variant configuration in sales order line item from Ztable

Hello Experts,
we have configurable material and and creating sales order. from sales order line item if we goto configuration we can maintain variant configurations. My requirement is that when i click on configuration after selecting a line item i need to check ztable where i have material no and and relable text. if an entry exists i have to populate this relable text in one of the configuration filed. Can any one help how can i read and update configuration in sales order level and where to do this coding so that when i click on configuration the value from ztable populated in a field.
Many thanks in advance.

Hi Senthil,
It is simple.
When you create a characteristic which should have the value maintained in the Z table, go to the tab values. Here you have a push button called "Other Value check". Here you click this button and select the function module option. Now, in the window, you will have a place where you can mention the name of teh function module.
You create a function module with the help of your developer to find out the text maintained in the Z table using teh rules you have in your mind and update that logic in the characteristic. In the earlier screen, you just have to mention the name of the function module, thats all, your work is done.
Now when you configure, for this characteristic, the value will be automatically determined using teh function module. You have to create such characteristics as "Not ready for input" ones in additional data for which you cannot enter values manually.
Hope this helps.

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.

Populating Variant COnfiguration value in ORDERS05

Similar Messages

Maybe you are looking for