New forums launched for PM, variant configuration, classification,....

Hi,
now the new forums have been launched and most of the former messages were moved from the PLM forum to this new special forums. To avoid long response times for your future threads please keep in mind to post them in the newly created forums for
SAP Document Management
SAP ERP PLM - Classification and Variant Configuration
SAP Portfolio and Project Management (SAP RPM, cProjects) and cFolders
[Quality Management (QM)|SAP ERP Operations - Quality Management (SAP QM);
[Environment Health & Safety (EHS)|SAP Environment, Health, and Safety Management (SAP EHS Management);
Best regards,
Christoph
Edited by: Christoph Hopf on Aug 3, 2011 9:01 AM

Hi all,
today the new forums for Classification and Variant Configuration are released. So you find these new forums under
ERP PLM Variant Configuration: SAP ERP PLM - Classification and Variant Configuration
ERP PLM Classification : SAP ERP PLM - Classification and Variant Configuration
From now on please post your questions regarding these topics in the new forums.
Best regards,
Christoph

Similar Messages

  • Variant configuration/classification

    hi,
    we have materials manufactured by our client as follows.
    it is an FMCG company and the company makes noodels, ketchup etc............
    now there are various varities of noodels (flavour, rice, flour noodels ).
    my question is should we use variant config or shud we use classification system to map various kind of noodels (variants ).
    basically,  i need to know the  difference between variant config and  classification system  and  relation between these two if any ?
    regds
    Pamela

    hi,
    VC comes with CLASSIFICATION TAB PAGE - this is also called as CLASSIFICATION.
    according to SAP one is dependent on other.
    this is for your understanding:
    Variant configuration offers a unique feature by which requirement of creating separate material for each variant of
    product is eliminated by using u201Cconfigurable materialu201D, that contains all the components and operations for
    production planning requirements.
    Characteristics: Characteristics are used to define the features of configurable material. These characteristics are
    assigned to CLASS TYPE 300. Customers can choose different options fro each characteristic, which are termed as
    a u201CVALUESu201D.
    Each configurable material is assigned to a u201CCLASSu201D via u201CCONFIGURATION PROFILEu201D which controls
    the configuration in the sales order.
    Variant dependent PRICE can be calculated and maintained in VARIANT CONDITIONS.
    COURTESY : SAP LIABRARY
    HOPE THIS CLEARS YOUR ISSUE.
    balajia

  • 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

  • Problem while creating PO from SO for a Variant configurable material

    Hi
    i am facing a problem when i am creating a Purchse order from a Sales order.
    the material is a variant configurable material and we are creating a Sales order in Future date say in june.
    For one of the materials in the SO the configuration is different today and the configuration is different in June.
    Today the BOM contains different materials and in june there is a different bom for the material.
    and according to my understanding the BOM gets exploded on the basis on the delivery date in SO.
    here on the basis of the config which is valid in june materials are getting picked and that is correct.
    when i try to creat a PO out of that SO i could see that the BOM gets exploded and   correct materials are picked but i get the error message that inforecord for one of the componentes is not there.
    but that component is not getting selected in the config..and it is not there in BOM in june.
    It is there in the BOM today but not in JUNE.
    I dont understand why the system is refering to that componeent and throwing this error
    please help
    Thanks & Regards
    sarika

    You may try creating two BOMs  -- one speicfic to the date of order.
    Sanjeev

  • Add new select option for VT04 variants

    Hi Experts,
    Want to know the process of how we add a new select option (say sold-to/KUNAG) to the existing set of selection criteria in the variants in VT04 apart from implicit enhancements.
    Even if we create a new implicit enhancement in LV56LSCR, the new field (sold-to/KUNAG) has to be further added to the select statements also. The select statement in the subroutine INDEX_SELEKTIEREN in LV56LF01 has to be enhanced for the same.
    Also should this new field has to be added to the EXPORT TO and IMPORT FROM MEMORY ID MEMORY_LFSL statements in the other includes of SAPLV56L ?
    Is there a better/recommended way to do this? Any pointers are much appreciated. Thank You.
    Regards,
    Narendra.

    Hi Ravi,
    This is infact the program for the txn VT04, would you be able to shed any other info? Thanks.
    Regards,
    Narendra.
    Edited by: Narendra Daka on Dec 7, 2011 9:00 AM

  • Change MD04 Exception for incomplete Variant Configuration

    Hi PP Gurus.
    I have a problem!
    This is my scenario: when I create a sales order with a configurable  material with a incomplete configuration I need, if possible, to block the generation of the requirement list in MD04. If possible, can I change, with a user exit or BadI or... the Exception Code in MD04?
    Thanks
    Manuel Chiarelli

    Hi.
    I'm sorry...
    The scenario is:
    I've a Sales document with a configurable material. Thi material have some configurable components with different production time.
    If I change the schedule type and I don't set the "MRP relevant", when I launch the MRP on this material, the system doesn't explode the requirement for the components.
    I need, if possible, to force the exception when I execute the planning so I can produce the components.
    Can I do this?
    Thanks
    Manuel

  • New forum area for Adobe Interactive forms

    Would it be possible to create a separate thread for the adobe interactive forms?  Most of the conversations are under the webdynpro forum, but because people refer to this area by so many different names (adobe, ADS, interactive forms) it is really difficult to do a search for anything specific.  (also, you cannot distingquish a post between ABAP interactive forms and Webdynpro interactive forms until you are deep into the message).
    I think enough folks are starting to use interactive forms that we can get some good topics going!
    Also note:  the adobe homepage on SDN needs more visibility.  It is buried under too many links.  I had to email Matthias Zeller to get the url.  I lost patience after about 20 minutes of searching.
    thanks!
    brenda

    A last thought/comment:
    I just went to the WAS homepage.  The link is under FEATURED CONTENT under the black/bold heading Interactive Forms. 
    I would not equate the adobe home page as "featured content".  Now that I have been told, I can find it, but I spent 20 minutes using the forum search to find it and the results were mostly to the help.sap.com links.  Maybe a title change under quick links might make it more intuitive.
    thanks for the opportunity to rant a bit.
    brenda

  • Steps for Variant Configuration

    Hi Gurus,
    Can any body tell me step by step procedure for variant configuration.
    My e-mail id. <REMOVED>
    Regds.......
    Sumit

    Hi Sumit,
    Variant configuration is for manufacturing complex products. The manufacturer always has to offer new variants of its products. Often, new variants are created by modifying existing product designs as you process the order. The important thing is to react quickly to customers' requirements.
    The customer determines the features of the product. A customer buying a car, for example, can choose the features of the car and combine these features as required.
    The product configurator improves information exchange between sales, engineering, and production. Variant configuration helps the customer or salesperson to put together specifications for the product and ensure that the product can be produced from these specifications. It also ensures that production costs do not overstep the mark.
    Procedure -
    Create a Material - KMAT type with Item category (002)
    Create Characteristics 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 i.e. 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.
    Variant configuration is for manufacturing complex products. The manufacturer is
    always having to offer new variants of its products. Often, new variants are created
    by modifying existing product designs as you process the order. The important thing
    is to react quickly to customers' requirements.
    The customer determines the features of the product. A customer buying a car, for
    example, can choose the features of the car and combine these features as required.
    The product configurator improves information exchange between sales, engineering,
    and production. Variant configuration helps the customer or salesperson to put
    together specifications for the product and ensure that the product can be produced
    from these specifications. It also ensures that production costs do not overstep the
    mark.
    Integration
    Variant configuration is integrated in the following applications:
    a.. CA Classification
    b.. LO Material Master
    c.. PP Bill of Material
    d.. PP Routings
    e.. PP-PI Master Recipes
    f.. SD Sales
    g.. SD Conditions
    h.. MM Purchasing
    i.. CO Costing
    j.. PP Material Requirements Planning (MRP)
    k.. PP Production Orders
    You can configure the following objects:
    a.. Materials
    b.. Standard networks in the Project System.
    c.. PM General maintenance task lists
    d.. Model service specifications
    Features
    You do not need to create a separate material for each variant of a product in your
    company. You can use one configurable material to cover all variants. You create a
    super BOM and a super routing for this material, containing all the components and
    operations for producing all variants of the product.
    To define the features of a configurable material, you use characteristics. To
    enable you to use characteristics to configure a material, you assign the material
    to a class of class type 300. Possible characteristics of a car, for example, are
    model, country, color, and engine. The customer can choose from among different
    options for each characteristic (values).
    The only limitations are combinations of features that are not possible for either
    technical or marketing reasons. You cannot combine all types of car engine with all
    types of transmission, for example, or certain types of upholstery are only
    available for more expensive models. In Variant Configuration, you use dependencies
    to control this. This prevents combinations of options that are not allowed.
    Dependencies also select exactly the right BOM components and operations to produce
    a variant.
    Each configurable object must have a configuration profile. The configuration
    profile for a material controls the configuration process in the sales order.
    You can make the price of a variant dependent on the characteristic values assigned
    (Pricing). You can use variant conditions to define surcharges and discounts for a
    variant.
    For variants that are required frequently, you can create material variants, which
    can be produced without a sales order and kept in stock. When you receive a sales
    order, you can check whether the variant required is in stock, so that you can
    deliver immediately.
    Pl go thr below links:
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    http://sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Configuration management (LO-CM) used with Variant configuration (LO-VC)

    Hi
    I am new to SAP, working with Variant configuration (LO-VC).
    I wish to enforce configuration management during development of a new Variant configurator.
    Would Configuration management (LO-CM) work together with Variant configuration (LO-VC)?
    My expectation is that SAP Configuration management (LO-CM) will work similar to solutions like e.g. MsVisualSourceSafe, SubVersion, CVS, IBM/Rational ClearCase etc. in the software development domain.
    best regards Henrik

    Hi Amber
    Thanks a lot for answer, and please apologize my late response.
    I am not confused by the term 'configuration', being used in two different meanings.
    (1) Variant configuration (VC) is the dicipline of creating product variants by making a set of choises from the characteristics describing the product. A complete and consistent set of choises is a 'configuration'.
    (2) Configuration Management in the 'traditional' software development meaning: Software Configuration Management (SCM). E.g. Microsoft VisualSourceSafe, IMB/Rational ClearCase, Subversion etc. are examples of tools used for the kind of SCM I wish to apply to VC models.
    My confusion is whether the SAP CM that I can read about in the SAP online help, is similar to traditional SCM, and whether it can be applied to VC models.
    I wish to apply SCM to a VC model. All the objects that together make up the VC model may then each exist in various versions (version control). A complete set of the objects (in a given version) make up a configuration of the VC model.
    What is achieved is : you can control the development of VC model in just the same way that all serious software is under the control of SCM. This will allow an evolution of the VC model, like e.g. version 1.0 is released in January, then version 1.1 is released in June. A major upgrade of the model may become version 2.0 in December etc. The 'source code' (the objects) of each of the versions can be retrieved at any time from the SCM system. Also with SCM several developers may work on the same VC model at the same time, and merge their individual work into the same model.
    This is very different from todays VC model development. In todays VC model development, only one version exists, that is 'todays version'. Any change to the model is released immediately, and you can undo model changes only if you remember what it was like a little while ago.
    We do develop and test VC models in one SAP system, and then move them to the production system. This is however still very far from the benefits of SCM.
    best regards
    Henrik Saugbjerg

  • 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

  • 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.

  • 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

  • Testing Variant Configuration

    Hi,
    Can anybody provide me the information on how testing of Variant Configuration can be done?

    Hi Ashutosh,
      Check the links below.
      http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
      http://sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm
       Reward points if it helps.
    Regards
    Karan
    Message was edited by:
            Karan Bhatia

  • 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 <b>Charateristics</b> in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc
    Create another <b>characteristics</b> 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 <b>characteristics to a Class</b> 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 <b>class assignment</b> 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.

Maybe you are looking for