Reg:Variant configuration

Hi,
I have created a sales order, ran mrp converted planned order to production order
1) at the time of creating Production order  if i press Material lists button it says no material exists ,but already i have cretaed pr/Purchase order,done gr for the raw material
2) At the time of confirming the production order in co11n after entering the confimation qty, if i press goods movement
iam not able to see the raw material
Kindly help me in solving this issu
Also tell me the configuration settings i need to maitain in Shopfloor control
Regards,
Raj

Raj,
Not much info to go on.
Do you have a valid BOM for the Finished goods part that points to the Raw Materials Part? CS03 > enter FGs material; plant in your sales order; Bom usage 1; validity date earlier than the start date of your production order.  Does it exist?  Are the expected RM components there?
If yes, look at your config for production order.OPL8.  Under BOM Application, what is there?  is the Bom Application relevant for explosion? You can see the relevancy in OPJM
General PP settings (including SFC)
http://help.sap.com/bp_bl604/BBLibrary/Documentation/142_BB_ConfigGuide_EN_IN.doc
General Variant settings
http://help.sap.com/bp_bl604/BBLibrary/Documentation/147_BB_ConfigGuide_EN_IN.doc
Best Regards,
DB49

Similar Messages

  • HI Gurus Reg - Variant Configuration

    HI gurus
    Can any body explain the
    $parent, $root, $ self
    and how to use that
    documents i have checked and of  not that much help ful
    thanks in advance
    Rajesh

    Hi Rajesh,
    These all are Object Variables:
    Object Variables
    You use object variables in a multi-level configuration, to describe configurable materials in a configuration structure.
    You can use the following object variables:
    u2022 $ROOT is the highest-level configurable material in a configuration
    u2022 $SELF is the material to which the dependency is allocated
    The material to which an action or procedure is allocated is the same material for which values are inferred by the action or procedure. To make it clear that actions and procedures only infer values for materials to which they are allocated, the characteristics are preceded by the variable $SELF.
    In dependencies that are allocated directly to the header material, $SELF and $ROOT both mean the header material.
    u2022 $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.
    However, in a multi-level, interactive configuration $ROOT may refer to two different objects:
    u2022 If the BOM is exploded in production, $ROOT always refers to the material that transfers requirements.
    u2022 If the BOM is relevant to sales and distribution, $ROOT always refers to the header material.
    Hope it helps!
    Preethi

  • BAPI for Creating Sales Order For Variant Configuration Materials

    Dear Gurus,
    Before posting this thread, we have referred many SDN threads, OSS notes and other sites for any sort of help..but no success..All threads and other referrals are not much of help as they are kind of incomplete( Perhaps, we are unable to understand them..no offense).
    Few checked threads on this subjects are:
    http://scn.sap.com/thread/34590
    http://scn.sap.com/thread/851070
    http://scn.sap.com/community/abap/blog/2014/04/23/update-vc-variant-configuration-data-using-standard-bapi-in-sales-order
    http://scn.sap.com/community/abap/blog/2014/07/15/creating-orders-with-variant-configured-items-using-bapisalesordercreatefromdat2
    http://scn.sap.com/community/abap/blog/2014/04/23/update-vc-variant-configuration-data-using-standard-bapi-in-sales-order
    http://scn.sap.com/thread/120144
    OSS: 549563
    Well, we're using the BAPI (BAPI_SALESORDER_CREATEFROMDAT2) which creates the sales order successfully but without the characteristic values in line items.
    We're passing data to the following parameters - ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_VALUE to create the variant config but not able to see it getting created.
    Pls find attached BAPI coding document for your reference.
    If you could throw any light on this issue will be of great help for us.
    Thank You in Advance!!!
    Reg,
    Jagan-SD.

    Jagan nath
    Try below.
    you would need miimum of 3 segments to pass variant config data using this bapi
    ORDER_CFGS_REF for each configurable item
    POSEX = ITEM #
    CONFIG_id , root_id - Start with 1 and increment it for each configurable line item
    ORDER_CFGS_INST
    CONFIG_ID - from above
    INST_ID - Start with 1 and increment it for each configurable line item
    OBJ_TYPE = "MARA'
    CLASS_TYPE = '300'
    OBJ_KEY = material #
    ORDER_CFGS_VALUE
    CONFIG_ID for the item, INST_ID for the item
    charc for characteristic value
    VALUE for characteristic value
    Reference thread
    How to Fill Configuration Data in BAPI BAPI_SALESORDER_CREATEFROMDAT2
    Hope it will solve your issue.
    Thanks
    Ritesh

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

  • Stock Report for Variant configuration

    Hi Experts,
    Request your help to get the following information.
    We have a material which are packed in to multiple packing modes. Inorder to ease the selection of packing mode in sales order, we are thinking of introducing variant configuration. I.e all the packed materials will be created as variants in SAP and the sales order will be created for the configurable material. When the proper characteristic is selected the material will be automatically replaced by the variant.
    But the requirement is to see the stocks of all the varaints along with the configurable materials as the header. For eg. Material A is having variants A1, A2 & A3. The sales quantites are 25, 30 and 35 respectively.
    In any of the standard report, can I see the sales of these along with the total sales of config mtl A as 90
    Please guide.
    Thanks & Regards
    Prathib

    Hi Prathib,
    On my last project, we define material code with the same code at the beginning like you do A1 A2 A3 (for variants) and AC for example for configurable material. Then for stock report you can use MB52, in material field just write A* it will show you stock from material start with code A. But make sure you define material type and material group for selection wisely. It works for me. Now depends on how well you define your structure.
    Regards,
    Arman

  • Error message while creating configurable material for variant configuration.

    Dear All,
    I want to create configurable material for the purpose of variant configuration. When trying to create configurable material using mm 01 or mm k1, it is displaying an error message that internal number assignment is not possible for the material type configurable materials as well in using external number also. Can anyone specify the steps to be done in creating the configurable material. Thank you all.
    Regards
    Akula Sivaji Kumar Madhu Kiran

    If you want to set these material type to another group (Which has a internal number and external number range), then you can do it.
    In MMNR, Click on the Edit Group.
    Then select the material type and click select element.
    Then mark a tick option in another group and then press Element/Group.
    Then you can see the material type will come under this group.
    Now save your entry, and create a material with this material type.

  • Variant configuration

    I have done all the settings for variant configuration. But still I am getting a error while raising sales order (VA01) (ERROR -configuration not possible for material)
    now what should i do.

    Dear pavan kumar,
    Check Delivering plant is maintained or not in sales order.
    Regards,
    Srikanthraj

  • 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

  • Regd : Error during saving the  sales order for Variant configuration

    Hi -
    When the item( config material) is saved in the sales order , system scheduled the production order and getting an error as " Posting Rule for Assembly order for item 000010 could not be generated".
    Any solutions regarding the error.

    Hi,
    This is the process of Assembly to order with variant configuration. In material master, you can maintain gen item category 0002 (configurable material) in basic data view, sales 2 view item category grp 0002 and strategy group 82 in MRP 3 view. After creating of material master, BOM & Routing, You can create sales order in VA01 transaction.
    In this VA01, When you create sales order, system will check material availability, capacity checking and system will show variants for each items. And also when you will save the sales order, system will create production order no immdiately.
    So you can maintain the above settings compulsory.
    please let me know any clarification.
    Regards,
    Mohan

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

  • 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

  • Error in Variant Configuration CO684

    Hello, friends !
    Back in the forum, now with a problem in Variant Configuration.
    I was able to carry out the whole process up to the creation of the production order. There I have the error message CO 684 "You cannot make an assignment to make to order stock" .
    All the configuration stuff seems to be OK.
    I created a sales order configuring the product.
    The MRP creates a planned order in the Customer Segment of the MD04.
    The components have the special stock E.
    I have tried with stock available in warehouse and also tranferring to E using MB1B movement type 412 E.
    But the error still remains !!
    Any tip or clue ??
    Thanks in advance.
    Dario

    Rajesha,
    for the KMAT we have:
    strategy group: 25
    Individual: 1
    In the sales Order:
    Item Category: TAC
    Requirement Type: KEK (in the procurement Tab); class should be 046.
    However, in the controlling for sales order there is no entry for:
    TAC "   "  046 , only for Class 041, in the Assignment of Requirements Type to transaction.
    In the planned order: Account Assigmnment: M (it takes from strategy 25)
    Settlement Profile (In the order Type) SD1.
    Result Analysis Key: ?? (where can I find it??)
    Regards

  • Variant configuration-- syntax error in creation of object dependencies

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

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

  • How to hide variant configuration screen in sales order

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

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

  • Reg:Variant Dependencies & Pricing

    Hi Gurus,
    I have configured up to the below mentioned steps.
    1.Creation of Material Master Record with required settings
    2.Creation of Characteristic and it's values
    3.Craetion of class
    4.Assign characteristics to Class
    5.Create configuration profile and assign it to MMR
    I have strucked at pricing and dependencies maintenance.I need some info.related to pricing maintenance and dependencies creation.Kindly help me on this regard.
    Thnaks & Regards,
    Sash.

    Hi,
    The following needs to be set up for the variant pricing of configurable product .
    Create pricing condition VA00 for the variants
    Create characteristics
    Create variant table
    Create dependencies
    Allocate the dependencies to the configuration profile
    Procedure:
    1)Create Pricing Condition-VK11 Transaction code.
    Condition Type:VA00
    Maintain the required pricing here.
    Note:The condition type VA00 is defined as a fixed rate surcharge, which is applied to the base price of the product ordered. This variant condition is created as part of the pricing master data for each of the configurable options for which a surcharge should apply
    The condition type VA01 could alternatively be used in variant pricing to increase the price of the higher level material by a fixed percentage rate.
    Maintain the prices for all the variants (Characteristics) you have create.
    Note:The entry of the Variants is case sensitive.
    2)Create Characteristics:Surcharge
    Transaction code:CT04
    Create a Characteristics name to identify your Pricing Characteristic.
    In the addition data tab maintain the following:
    Table Name:VKOND and Field name :SDCOM.
    Note:
    The characteristic u201CSURCHARGEu201D references to the field u201CVKONDu201D of the u201CSDCOMu201D table. It provides the link between the materialu2019s variant configuration and the variant conditions that were entered.
    3)Create Variant Table::
    Transaction code:CU61
    Maintain the characteristics in the Variant table.(Char.Name,Char.Value,Var.Cond )
    Save it..
    4) Maintain the Variant table :
    Transaction code:Cu60
    Maintain values for Example
    Characteristic Name   Characteristic Value  Variant condition
    Size                                     10                             Size_10
    Colour                                  Red                         Colour_Red
    Colour                                  Blue                          Colour_blue
    Save the table.
    5)Create Dependencies:
    Transaction code:CU01
    Maintain the required description and in dependency editor
    You see the screen u201CEdit Dependencyu201D. Select Insert line icon five times to insert lines. Enter the following on the inserted lines.
    TABLE TBL_PRICING                
         (CHAR_NAME  = 'Size',           
          CHAR_VALUE = $self.Size,       
          VAR_COND   = $self.SURCHARGE).
    Note: This procedure references the Table TBL__PRICING.  The dependency checks to see which value was chosen for the 'Size' Option and specifies the appropriate Variant Condition to this choice. 
    Check whether your dependency has errors or not.
    After that Save it and make sure that it has been released(Which you can find in the initial screen)
    6)_Allocate Dependency to the Characteristics profile of the material:
    Transaction code:CU42
    In the screen u201CChange Configuration profile for Material: Profile Overview u201D. On this screen, maintain your profile and select Profile Detail icon.
    You see u201CChange Configuration profile for Material: Detail Screenu201D. Under the Section Header Basic Data, select Object dependencies button.
    You see the screen u201CMaintain Dependency: Allocation to Objectsu201D screen.
    Maintain your dependency here in this configuration profile for the material.
    Once it is done cross check in transaction code 'PMEVC' Transaction code for ECC 6.0.
    Simulate your Variant configured material and cross check.
    Hope it helps.
    The steps may look little bit exhaustive but the process of maintaining it shall be fruitful.
    Have a Nice Day.
    REgards,
    Ravi

Maybe you are looking for

  • Client Security solution not working with fingerprint, Fingerprint Tab is unavailable

    Just recieved my Thinkpad T430 today and have done all updates on the system. I am trying to use Client Security Solution with my fingerprint however it will not allow me to do so. Whenever I go into password manager I get the message, "The requested

  • ORDER SIBLINGS not working in Forms

    This code run fine in Toad BUT giving me error in forms. SELECT        LEVEL                           LOC_NAME,        LOCATION_NAME                   LOC_ID,        LOCATION_ID                     HLOC_ID,        HEAD_LOC_ID MUDRA   FROM AS_LOCATIO

  • Error referencing locally installed JSTL

    Using the JWSDP, I downloaded JSTL 1.0 from Jakarta. I am able to use my own custom tag libs, and indeed the JSTL when the directive is thus: <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %> However, when I try to use JSTL installed l

  • SQL LOGIC

    I have a question regarding a SQL statement that I wrote. The following SQL statement brings back no records: SELECT PROP_BOOK_SI.EMP_ID, AMPEMP.CLOCK_NUMBER, AMPEMP.LAST_NAME, AMPEMP.FIRST_NAME FROM PROP_BOOK_SI LEFT JOIN AMPEMP ON AMPEMP.EMP_ID = P

  • How Ajax works with Struts framework

    How Ajax works with Struts framework . Thanks Ramki