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

Similar Messages

  • Variant config pricing

    HI,
    for variant configuration pricing if we use VA00 ctype ,
    when we create sales order whether both proo & vaoo will get detrmined or only vaoo will be there
    pl let me kno how exactly varinat configuration pricing works

    hi
    vaoo will be assigned to characteristics
    but in sales order -proo will also be there rite along with va00

  • Variant config pricing condition description not correct

    Hi Gurus!
    I created Sales Order with a variant configuration material, pricing with package items. System pick up the correct
    pricing but pricing Condition Name for all the items are the same, system is taking variant description VK30 instead
    of condition type description in VK11.
    I have a package e.g.
    Material:  Phone Package A
    Condition type:
    - ZZ01 Phone 
    - ZZ02 Charger
    - ZZ03 Battery
    Data entry: Material A001 Nokia phone package
    charcteristics: Phone       PA
                           Charger    A1
                           Battery     T1
    System compute all the description of condition type is the same
    Material:  Phone Package A
    Condition type:
    key: PA-A1-T1
    - ZZ01 Package A for Nokia AAA   10.00
    - ZZ02 Package A for Nokia AAA   30.00
    - ZZ03 Package A for Nokia AAA   50.00
    I want the description of Condition Type not the variant description. Any clue on how to get the correct description of the
    Condition Type?

    Hi Sunny,
    1) With respect to your original question (e.g. "how to have the VTEXT field on the Conditions tab display the Condition Type Description set via the IMG rather than the Variant Description set via txn VK30"). Please know that once you check the "Variant Condition" flag for a condition type, the system has no choice but to present the Variant Description because this behavior is hard-coded.
    Easiest solution would be to activate screen overlay functionality (such as GUIXT) which can present the desired text to the user without affecting underlying code. Another alternative is to ask a developer to make an implicit enhancement that overrides the description just before presentation to the user.
    If neither solution works out and the users insist that you show the condition type description, then variant pricing simply doesn't fit. Hopefully you don't get to this point, but if it happens, then you would have to revert to standard (non-variant) pricing. To start you would need new display-only VBAP fields for each price-relevant characteristic (e.g. ztraining, zcourse_type, zstudent, and maybe zresource). and then custom code to copy values selected in the VC back to the corresponding new line item fields which can be done via a user-exit. Then you would follow the normal process for introducing new price-relevant fields, and redesign your condition types and condition tables to remove all reference to pricing variants. A hassle, but side benefit would be more straight-forward master-data maintenance since the user can directly see and maintain all pricing key fields in VK11/12/13 (rather than having to check variant table(s) to discover how the pricing key fields translate to variant keys) and of course they would always see the condition type description as desired.
    2) Moving on to address your 3rd-August follow-on comment from the other thread (e.g. "However, when I change the input Resource from 01 (Classroom) to 02 (Whiteboard) ... ZA01 is gone"). Is this what you wanted? If yes, then a user who needs a Classroom and Whiteboard and a Projector, would have to create a sales order with three configurable line items - is this the desired outcome?
    Edited by: Laura J. Williams on Sep 23, 2010 1:22 AM

  • Variant condition pricing ( variant product * qty selected)

    Hi All,
    I have created two characteristics for a variant
    characacter-1 is for the type of SHEET ( PVC SHEET, SYNTHETIC SHEET ) and maintained price as PVC SHEET = 100 and SYNTHETIC SHEET = 200
    character-2 is for the length ( where in the user will select any lenght between 0-200 meters)
    now at the time of order creation first the user will select the type of sheet ( PVC SHEET or SYNTHETIC SHEET) and the quantity as 50.
    if PVC SHEET is selected system should give 100 * 50 = 5000 as value for character-2.
    Hope my question is clear, can any body help how to do this.
    Thanks & Regards
    Siva

    Hi,
    http://www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm
    http://help.sap.com/saphelp_di46c2/helpdata/en/d8/fa9bd49ede11d1903b0000e8a49aad/frameset.htm
    http://www.sap-basis-abap.com/sd/steps-for-variant-configuration-and-pricing.htm
    Kapil

  • Variant Configuration - Pricing issue

    Hi,
    Can anybody please help me out with the pricing issue which I am facing?
    How can I increase the price by a certain percentage based on the value of  another pricing condition VA00 and show it as a different pricing condition?
    For example: VA00 for my product price shows 1000. Now on 1000, I want to calculate 30%  and show it with a different pricing condition description such as "Surcharge". I cannot used a fixed price for lets say "Surcharge" because 1000 as product price is not fixed/static and will depend upon variant configuration and the "Surcharge" will also vary with it.
    How can I please implement such a solution?
    With best regards,
    Sunil

    Use the VA01 condition type for this. This is the standard condition type provided by SAP to address this issue. In your pricing procedure against VA01 give the From To as VA00.
    Hope this helps.
    Regards,
    GSL.

  • 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

  • Reg : Variant saving for Module Pool Programming

    Hey Friends,
       Plz help me in how to create variant for Module Pool Programming as in normal reports.Thanx in advance.

    Hi,
    You can create variants for Module pool program using the transaction SHD0. You can create Screen variants for your screens using this Tcode.
    Go to SHD0 -> Give the Transaction code(ZTRAN) for which you want to create a variant -> name of some variant (ZVAR) -> create -> takes you to your transaction -> Give the values that you want to be displayed as variants -> Click on Save -> Opens a pop up to confirm the screen entries -> Check the check boxes of those fields that you have entered the data with (the column with check boxes that says W.Content) -> Exit and Save -> Save the variant -> You can see a screen variant created (ZVAR_0100)
    Now Goto -> Create variant transaction -> Give your transaction variant name (ZVAR) -> Select Transaction with variant -> Takes you to SE93 transaction -> Give the transaction variant name  -> save. Run with the created transaction.
    Edited by: Nitwick on Jul 27, 2009 4:49 PM

  • Reg: Variants Deletion

    Hi Every one,
    Iam using one function module to delete the variatns 'RS_VARIANT_DELETE', with this function module
    i can delete only specified variant only, But i want to delete all the variants at a time with out specifying.
    any function module is there ?.
    Best Regards,
    Narasimha Rao.

    Hello Rao ,
    I didn't find ny FM , but I hope it may help you
    mostly all the variants are stored in table "varid" & "varit" ,
    try to write a report , so as to delete all the variants belonged to Z* or Y* programs.
    Delete from "varid" & "varit"  directly.
    Regards
    Aby.
    Edited by: abhi on Nov 11, 2008 7:04 AM

  • Reg variants

    hi all,
               i have a doubt regading variants.please tell me what is the difference between variants,screen variants and transaction variants.and i want to know how they are utilised in sap.please let me know step by step process to customise them
    regards
    ravi

    hi ravi,
    Welcome to SDN forum.
    Check these threads on discussion about variants.
    <b>variants</b>
    Re: variants
    <b>Deleting Variants</b>
    Re: how to delete variants
    <b>Transaction variants</b>
    Transaction variants (SHD0)
    <b>program variants</b> 
    Re: program variants
    <b>screen variant</b>
    screen variant
    Reward with points for Helpful answers
    Cheers
    Alfred

  • 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

  • Steps to  create variant configuation dependencies code

    Hello Guru's,
    steps to create variant configuration dependency using code?.  will anyone guide me.

    Check the below links.
    Variant Configuration (LO-VC)
    [http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf|http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf]
    Variant Configuration for an Order BOM
    [http://help.sap.com/saphelp_ides/helpdata/en/0a/857463c87611d1a7760000e8a5f6c8/content.htm|http://help.sap.com/saphelp_ides/helpdata/en/0a/857463c87611d1a7760000e8a5f6c8/content.htm]
    [www.sapmmforum.blogspot.com/2007/10/variant-configuration-for-order-bom.html |www.sapmmforum.blogspot.com/2007/10/variant-configuration-for-order-bom.html ]
    Steps for SD Variant Configuration
    [www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm|www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm]
    Steps for Variant Configuration & Pricing
    [www.sap-basis-abap.com/sd/steps-for-variant-configuration-and-pricing.htm|www.sap-basis-abap.com/sd/steps-for-variant-configuration-and-pricing.htm]
    [www.sapsdforum.blogspot.com/2007/10/steps-for-variant-configuration-and.html |www.sapsdforum.blogspot.com/2007/10/steps-for-variant-configuration-and.html ]
    Hope this helps. Reward points if helpful.
    Thanks,
    Balaji

  • Multiple Variant pricing conditions in a Pricing Procedure

    Hi,
    I have a scenario regarding variant configuration pricing in a sale order. I need to attach multiple pricing condition like VA00 in my pricing procedure .
    A material M1 has many characteristics under the category Basic and Special for example.
    Under Basic I have the following characteritics and its respective values maintained in VK11
    B001- Basic Spec 1  USD 100
    B002- Basic Spec 2  USD 200
    B003- Basic Spec 3  USD 300
    Likewise under special category ,
    S001- Special Spec 1- USD 500
    S002- Special Spec 2- USD 1000
    In the pricing procedure the varaint condition VA00 will carry the price of the characteristics. My requirement is as follows
    1. The prices of the Basic spec should be added first and later the special spec
    VA00- Basic Spec 1      100
    VA00- Basic Spec 2      200
    VA00- Basic Spec 3      300
    Sub total Basic spec Value  600
    VA00 Special Spec 1    500
    total basic and special spec - 1100
    The problem I faced in the above format was that the pricing procedure will allow only one entry of VA00. To over come that I copied the condition VA00 and named a new one, for e.g, ZVSP.
    Now when I use the condition ZVSP, it does not fetch the values like VA00.
    Could any one suggest a method in which I can introduce varaint conditions in multiple levels in a pricing procedure.
    Thanks and regards
    Rasheed

    Hi,
    When you copied the VA00 condition type, did you also copy the associated access sequences? Your new condition type should have an access sequence with an access that transfers the value of the doc. field KOMP-VARCOND into the condition VARCOND; use transaction V/07 to check this.
    Regards, Jesper

  • Material Variant pricing

    Hello All,
        I have created a material variant from a configurable material. I would like to know if in the sales order I can pull up the variant pricing condition attached to the configurable material, or do I have to maintain separate conditions in PR00. thanks
    Atul

    Dear Atul,
    As per your Q i understand that you want a pricing to be pulled in sales order.
    The Pricing for the material will same as we do. i.e we need to maintain the record in PR00.
    But for Variant the pricing needs to be Maintaind in condition type VA00.
    All the variant needs to be maintained in VA00 only as this condition type get activated only when you are working with Variant configuration.
    Suhas

  • How to create Material variant

    Dear all,
    I created configurable material and assigned class and BOM and object dependencies as well as configurable profile its working fine.
    I need to create material variant so i assigned configurable material to material variant in MRP 3 view then selected the characterstics as per requirement. BOM also i assigned the configurable material. But at the time planning its not planning as per requirement also i need to consume the stock as per configuration at the time of sales order delivery.
    What are all steps to be followed, where i did mistake pls correct me.
    Regards,
    S.Suresh.

    Dear Mohan,
    Thanks for your response.
    I am very clear  in configurable material  we can use only sales order. I did in my projects no issues.
    But material variant i have doubt, I tried once am not able get what i suppose to get.
    I read the sap help.From that what i understood  we can create PIR for material variant and can make stock thorugh the  order it will consume only whatever we selected from MRP 3 configurable material.
    If i make sales order for configurable material if the material variant and configurable material properties are same it will pick the stock. (For that in sales order item category (mat variant action) to be set).
    1.  Configure the configurable material in the sales order.
           2.      On the value assignment screen, you can already check whether material variants match the material configuration (see Variant Matching on the Value Assignment Screen).
    For a material to be replaced by the material variant in the sales order, the configuration of both materials must match exactly.
           3.      When you have configured the material, exit the configuration editor.
           4.      Depending on the settings in Customizing, the material is either replaced directly by the material variant, or a message is displayed indicating that a suitable material variant has been found.
           5.      If the material is replaced, the material variant is entered in the order item.
    Individual or collective requirements can be created for the material variant. Pricing is also carried out for the material variant, provided that you have not defined the configurable material as a pricing reference material for the material variant.
    So i have doubt on material variant only if  wrong pls correct.
    Regards,
    S.Suresh.

  • Variant .. Please Help

    Hi guru's
    I created varaints for selection screen (FBL5N) customer line items. My problem is tht i want these selection varaint to be come default depanding on specific user...Please tell me is it possible ??
    Please help and if possible please let me know !!
    Many thanks in advance..sure points
    Regards
    Inder

    dear friend
    please try out with the following
    VARIANT CONFIGURATIONS:
    Slide 1: VARIANT CONFIGURATION OVERVIEW Prepared by Arun prasad C R *Please place your comments
    Slide 2: Variant Configuration Introduction: • Variant Configuration is useful if you have a large number of combination of parts that go into a product. It means different permutations and combinations of the parts for same material. • If you maintain a unique material code for each possible combination of parts, you require a large number of material numbers. • Usually involves Make to Order Production Process Variant Configuration Examples: • A customer ordering a computer can choose different combinations of monitor, CPU, keyboard. • A customer ordering a car can choose different combinations of accessories and color. • In a business involving steel manufacturing, the customer may order steel involving different physical properties like tensile strength, diameter. Source: SAP
    Slide 3: Industries for Configurable Products Variant Configuration Source: SAP
    Slide 4: Cross Module Integration Variant configuration is integrated with the following applications: CA Classification LO Material Master PP Bill of Material PP Routings PP Material Requirements Planning (MRP) PP Production Orders PP–PI Master Recipes Variant Configuration CO Costing SD Sales SD Conditions MM Purchasing Source: SAP
    Slide 5: Overview of Terms Variant Configuration Source: SAP
    Slide 6: Overview of Terms • A configurable material has a special bill of material called the Super BOM in which all possible combinations are stored. • The product is configured in the sales order by choosing the required Characteristic Values. • The requirements are passed on Production Planning. On Explosion of the Bill of Material, the system selects the components assigned to the characteristics values in the order. Variant Configuration • After production, the material is assigned as sales order stock for delivery to customer. Source: SAP
    Slide 7: • Sales Order Processing
    Slide 8: IDES Demo Process Steps to be used in the demo: • Creating a Sales Order • Checking Requirements Using MRP • Requirements Planning • Converting the Planned Order into a Production Order • Confirming the Production Order • Checking the Production Order Settlement Variant Configuration • Creating a Delivery • Creating a Billing Document Source: SAP
    Slide 9: Enterprise Structure used for demo Company Code 1000 Sales Org 100 Distribution Channel 12 Variant Configuration Division 00 Plant 1000 Storage Location 0001 Shipping Point 1000 Source: SAP
    Slide 10: MTO Process Overview Make-To-Order Production With a Configurable Product: In this process, you create a sales order in SD and transfer the requirements to PP. The requirements are checked using MRP, before a production order is generated. This production order is created in PP. Shipping and billing both occur in SD. Finally, you check the costs and revenues in CO. Variant Configuration Source: SDN
    Slide 11: Creating a Sales Order (T Code :VA01) • After entering the sales data, a configuration screen pops up. • Configure the material by selecting the characteristics. • Note that the value of Variant Conditions changes as per selection. Variant Configuration Source: SAP
    Slide 12: Creating a Sales Order (VA01) • The system allows analysis of Object Dependencies and Variant Conditions. • Item Category determined in Sales Order is TAC. • Note the Material Availability Date and save the sales order (for test11048 and 11059). Variant Configuration Source: SAP
    Slide 13: • Configuration for VC
    Slide 14: Configuration Details: Material Type OMS2: In definition of KMAT Material Type, indicator ‘Material is Configurable’ is set Other material types like FERT (Finished Product) can also be used if the indicator is set in material master Variant Configuration Source: SAP
    Slide 15: Configuration Details: Item Category in sales order VOV4: Item Category determination is set to determine item category TAC Variant Configuration VOV8: Item Category TAC Source: SAP
    Slide 16: Configuration Details: Condition type for Pricing Condition types VA00 and VA01 (%) are available in Standard SAP for Variant Pricing Variant Configuration Source: SAP
    Slide 17: Configuration Details: Requirement type KEK The requirement class controls the MRP and the requirements consumption strategy as well as the relevancy for planning, settlement profile for costing. Requirements type KEK is determined for strategy group 25 and also for item category TAC. Variant Configuration Source: SAP
    Slide 18: Classification System: Characteristics Mayback 57 S Engine Color Rear wheel Seat Exhaust Antitheft device Variant Configuration Other Options Source: SAP
    Slide 19: Classification System: Characteristics Variant Configuration Source: SAP
    Slide 20: Classification System: Characteristics Variant Configuration Source: SAP
    Slide 21: Classification System: Characteristics CT04: Create characteristics • Data type can be CHAR, NUM, DATE, TIME, CURR Variant Configuration List of values and default value for characteristics can be stored in Value tab. Source: SAP
    Slide 22: Reference Characteristics Reference characteristics are characteristics that refer to table fields. Variant Configuration Tables / Structures whose filed values can be changed by dependencies: SDCOM - Communication between SD and Variant Configuration VCSD_UPDATE - Table for Updating Sales Documents from the Configuration MMCOM, STPO, PLPO, PLFH, PLFL Tables / Structures whose filed values can be read by dependencies: VBAK, VBAP, VBKD, VBPA_AG, VBPA_WE, VBPA_RE, VBPA_RG VEDA, MAEPV, MAAPV Source: SAP
    Slide 23: Classification System: Characteristics CT04: Create characteristics • Object dependencies like pre conditions, selection condition, action, procedures can be created for characteristics • Object dependencies like pre conditions, action, procedure can be created for characteristic values Variant Configuration Source: SAP
    Slide 24: Classification System: Class CL01 /CL02: Create class under class type 300 for Variants Variant Configuration Assign the characteristics to the class. During Material Master creation for Super BoM, this class will be used in the Classification view. Source: SAP
    Slide 25: Material Master of Super BoM (MM02) • Basic Data 2 Screen: Set ‘Material is Configurable’ Indicator • To determine item category TAC in sales order, maintain a suitable item category group such as 0002 • MRP 2 View: Procurement type ‘E: In house Production’ • MRP 3 View: Strategy Grp. ’25: Make-to-order for configurable’ used for demo • MRP3 View: Availability Check ’02: Individual Requirement’ • Classification view: Attach the variant class Variant Configuration Source: SAP
    Slide 26: Bill of Materials (CS01 / CS02 / CS03) Variant Configuration Source: SAP
    Slide 27: Object Dependency in BoM (CS02) Components in Production Order can be selected using Object Dependency type Selection Condition Variant Configuration Source: SAP
    Slide 28: Routings (CA02) Operations in Production Order can be selected using Object Dependency type Selection Condition Variant Configuration Source: SAP
    Slide 29: Configuration Profile: Process Planned/production Order; explosion indicator None (others Single level or Multiple level) The material has a BOM that is not relevant to the sales order. Only the characteristics that describe the variant are required. The components are determined later during material requirements planning or production, so there is no need to explode the BOM in the sales order. Sales order (SET): See next slide also In the sales order, sales-relevant components are shown as sub-items of the header material. Requirements are transferred and pricing is calculated at component level, not at header material level. Order BOM You create a sales order. In order BoM, you can insert extra items or delete items manually. The Variant Configuration changed BOM is stored as a separate BOM for the sales order. Source: SAP CU42
    Slide 30: Configuration Profile: SET This processing form means that in the sales order you can only process sales-relevant BOM items. You can use the item category group like 0004 at configurable material level to define that requirements transfer and pricing are at component level. For example, a PC is made up of the components monitor, CPU, keyboard, and printer. These components are all salable materials that are manufactured separately. In the sales order, you want to see the individual components that make up the computer as order items, as well as the whole computer. In the sales order, these products are grouped together in a SET. For this reason, this type of processing is also referred to as set processing. Variant Configuration Source: SAP
    Slide 31: Configuration Profile: Dependencies Dependencies like Actions and Procedure can be assigned to Configuration Profile. Variant Configuration Source: SAP
    Slide 32: Configuration Profile: Variant Table • Tables are used to store combinations of values for different characteristics • A table HD_1300_COLOR_PR is created in CU62 transaction. It has 2 fields: HD_COLOR (key field) and SURCHARGE. The selected characteristic will be transferred to HD_COLOR and surcharge to SURCHARGE2. • The table contents are given below (see transaction CU60) Variant Configuration VK30: Has description entries for the surcharge column listed above VK12: Will pick up pricing value based on condition type VA00 Source: SAP
    Slide 33: Pricing Check definition of characteristic SURCHARGE2 – Additional data tab -> reference table and field Variant Configuration Simple method to achieve Variant Pricing is given below: • Create multiple value characteristic SURCHARGE2 referring to SDCOM-VKOND. • Put this characteristic in the class HD-000 which was used for the configurable material • Now go to CT04 and change the Characteristic HD_COLOR Go to values tab and select Red. Go to Extras-> Object Dependencies->Editor and then select Procedure. In front of 000010 Enter $self.surcharge2='HD-003_03'. Similarly Select Black to enter $self.surcharge2='HD-003_02‘. Same way 'HD-003_01’ for Silver • VK30: Has description entries for the surcharge column listed above • VK12: Will pick up pricing value based on condition type VA00 Source: SAP
    Slide 34: Pricing VK30: Maintain descriptions for variant price conditions (optional step; done while creating dependencies for surcharges; maintains consistencies of configuration) Variant Configuration VK11 / VK12: Maintain actual condition record for variant price surcharges Source: SAP
    Slide 35: Pricing Factors Pricing factors can only be maintained on characteristic level. The syntax of pricing factors is as follows: $SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>) This expression contains the following information: • The characteristic that refers to structure SDCOM, in which variant conditions are defined. • The variant key used to infer the condition for a characteristic value. Variant Configuration • The factor by which the surcharge increases. Source: SAP
    Slide 36: Material Variant • For variants that are required frequently, create material variants, which can be produced without a sales order and kept in stock. • When a sales order is received, check whether the variant is in stock and deliver immediately. • The material master record of a material variant is linked to the configurable material and configured using the characteristics of the configurable material. Variant Configuration Source: SAP
    Slide 37: Material Variant in Sales Order On the value assignment screen, you can check whether the values assigned match the configuration of a material variant. Variant Configuration Source: SAP
    Slide 38: Material Variant Replacement of configurable material by a material variant Variant Configuration Source: SAP
    Slide 39: Material Variant Item category gets changed to TAN; Pricing will also change as per new MTS product. Variant Configuration Source: SAP
    Slide 40: Summary of day 1 By now, you should be comfortable with the following topics: • Explain what Variant Configuration is and its use in make to order scenario • Using Variant Configuration during sales order processing • Configuration details like item category and condition types • Classification System - Characteristics and Classes • Super BoM, Configuration Profile, Object Dependencies • Pricing Surcharges in sales order processing Variant Configuration • Using Material Variants for make to stock scenario Source: SAP
    Slide 41: • Day 2: Understanding Object Dependencies in detail
    Slide 42: Dependency Types Variant Configuration Source: SAP
    Slide 43: Pre Condition Variant Configuration Only if the model specified is racing, the bicycle can have 21 gears. 1. Create a precondition with the following source code: MODEL eq 'Racing' and Specified MODEL 2. Allocate the precondition to value 21 of characteristic GEARS Source: SAP
    Slide 44: Selection Condition A selection condition is allocated to each component and each operation. This selection condition determines which components and operations are selected for a variant. Variant Configuration Source: SAP
    Slide 45: Changing Master Data with Dependencies In variant configuration, you can use reference characteristics with dependencies to change field values of tables for bills of material (BOMs), task lists, and master recipes. Table names and fields are given below for reference. Table STPO field MENGE can be used to change component quantities of BoM. Table PLPOD field VGW01 can be used to change setup time of Operation. Variant Configuration Source: SAP
    Slide 46: Procedures Procedures can set default values for a characteristic (can be overwritten by the user) Variant Configuration Source: SAP
    Slide 47: Procedures • Set default values: $SET_DEFAULT ($SELF, <characteristic>, <term>) For example: ( $SET_DEFAULT ($SELF, COLOR_CHAR, 'BLUE'), $SET_DEFAULT ($SELF, GLOSS_CHAR, 'NONE') ) IF $root.PC_CASING_CHAR = 'TOWER' • Delete default values: $DEL_DEFAULT ($SELF, <characteristic>, <term>) Variant Configuration Produce a sum of the values for a characteristic in a multi-level configuration: $SUM_PARTS ($SELF, <characteristic>) It can be used to calculate the weight of components and transfer the same to structure VCSD_UPDATE, gross weight field BRGEW • Add the components of a BOM together: $COUNT_PARTS (<$SELF>) • Surcharge for variant conditions in Pricing: $SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>) Source: SAP
    Slide 48: Constraints and Dependency Net The main purpose of a constraint is to monitor the consistency of a configuration. There are four sections in a constraint. 1. OBJECTS: Declaration of all classes and objects used. 2. CONDITION: Pre requisite for processing the constraint. 3. RESTRICTIONS: For interdependencies and consistency check; check and set values. 4. INFERENCES: Enter the characteristics for which characteristic values are to be inferred. Variant Configuration Constraints are grouped together in dependency nets. The dependency net can be allocated to a configuration profile. Example: The hard disk can only have the value ‘1620’ for a tower, or ‘850’ for a mini tower. OBJECTS: PC IS_A (300) PC RESTRICTIONS: PC.HARD_DISK = ‘1620’ if PC.CASING = ‘Tower’, PC.HARD_DISK = ‘850’ if PC.CASING = ‘Mini tower’. Source: SAP
    Slide 49: Actions Actions can be used to infer values for characteristics. Actions can also be used to change field values in BOM items or operations in routings. Procedures can set default values for a characteristic, which can be overwritten by the user. The user cannot overwrite values that are set by an action. For new developments, use Procedures rather than Actions (to become obsolete) Variant Configuration Source: SAP
    Slide 50: Object Variables used in Multi level configurations Variant Configuration Source: SAP
    Slide 51: Allowed Dependency Types • Preconditions are allowed for characteristics and characteristic values. • Selection conditions are allowed for characteristics, BOM items, operations, and production resources/tools. • Procedures & Actions are allowed for characteristics, characteristic values, BOM items, operations, and configuration profiles. • Constraints can only be linked to a configuration profile via dependency nets. Variant Configuration Source: SAP
    Slide 52: Processing Sequence for Dependencies • Each time you enter a value for a characteristic on the value assignment screen and confirm the value, the system processes all the dependencies. • The dependencies are processed in the following sequence: 1. All actions several times, until no more values can be inferred. 2. All procedures exactly once in the following sequence: a) Procedures for the configuration profile in the order you defined b) Procedures for characteristics Variant Configuration c) Procedures for characteristic values The procedures for each characteristic or value are processed in the order you defined. 3. Actions Values set by procedures can also trigger actions. For this reason, all actions are processed again. 4. Preconditions 5. Selection conditions for characteristics Constraints are processed in parallel with points 1–3, if all the objects in the OBJECTS section are present, and if all the conditions in the CONDITIONS section are fulfilled Source: SAP
    Slide 53: • Transfer to Production Planning (Demo)
    Slide 54: 2. Checking Requirements Using MRP (T Code :MD04) Step1 to create sales order has already been discussed earlier. 2. Stock Requirements List: • The sales order is displayed as a separate planning segment (sales order stock required on material availability date and sales order). Variant Configuration Source: SAP
    Slide 55: 3. Requirements Planning (T Code :MD50) The sales order will now be converted into a planned order. Planned Orders represent the first step toward an actual production schedule for the Shop Floor. Variant Configuration Source: SAP
    Slide 56: 4. Convert the Planned Order into a Production Order (MD04) • Planned Orders are a result of MRP run and serve to provide an initial Production Schedule. • Production Orders contain comprehensive information to support a shop floor schedule and provide a method to confirm operations performed. • Production orders can be created with reference to a Planned Order. Variant Configuration Source: SAP
    Slide 57: 4. Convert the Planned Order into a Production Order (MD04) Object Dependency: BoM Selection Condition ensures only necessary material components are taken. Variant Configuration Source: SAP
    Slide 58: 4. Convert the Planned Order into a Production Order (MD04) Object Dependency: Routing Selection Condition ensures only necessary operations are taken. Variant Configuration Source: SAP
    Slide 59: 4. Convert the Planned Order into a Production Order (MD04) Prior to release of order, it is not possible for anyone to enter confirmations for the operations in the order. Release the Order and Save it.  Gantt chart.&#61614; Graphic &#61614;Display the operation scheduling overview, choose Goto  Variant Configuration Source: SAP
    Slide 60: 4. Convert the Planned Order into a Production  Analysis Variant&#61614; Costs &#61614;Order (MD04) Display the planned costs, choose Goto  Configuration Source: SAP
    Slide 61: 5. Confirming Production Order (CO11N) Production  Time Ticket Variant&#61614; For Operation &#61614; Enter &#61614; Confirmation &#61614;Control  Configuration Source: SAP
    Slide 62: 5. Confirming Production Order (CO11N) • Back flushing (posting of an issue of components or material withdrawals) • Storage of the finished product in the warehouse to sales order stock • Goods Movements are posted (errors if any can be corrected in COGI) • Actual costs are calculated • Just in case, to close the order without yielding a product, perform Restrict Processing -> Technical Completion for Production Order in CO02. Variant Configuration Source: SAP
    Slide 63: 5. Confirming Production Order (CO11N) • Sample Material Document and FI document entries are shown below Variant Configuration Source: SAP
    Slide 64: 6. Checking the Settlement of the Production Order &#61614; Settlement &#61614;From the Production Control node, choose Period-End Closing  Individual Processing (KO88) Perform order settlement to transfer the costs of the production order to sales order. Analyze the current cost situation for the Production Order Variant Configuration Source: SAP
    Slide 65: 7. Creating a Delivery (VL10G for delivery due list, VL01N for single delivery) Assign a serial number to the material. Pick and post the goods issue. Movement type will be 601 E indicating delivery from sales order stock. Accounting document will be generated to capture the change in inventory. Variant Configuration Source: SAP
    Slide 66: 8. Creating Billing Document (VF04/VF06 for due list, VF01 for single invoice) VF01: Create the invoice – sample accounting entries (without tax) are shown below F-28: Receive the payment from the customer Variant Configuration Source: SAP
    Slide 67: Other Information • CRM: It is possible to have configurable products among your Online Store offerings using the IPC (Internet Pricing and Configurator). It allows customers to interactively choose product options via an easy-to-use interface. Customers can mix- and-match these options to build the exact product they wish to purchase. • ECC 5.0: Single transaction PMEVC – Modeling Environment for VC Variant Configuration Source: SAP
    Slide 68: Summary By now, you should be comfortable with the object dependencies and the following topics: • Pre conditions • Selection conditions • Procedures • Actions • Constraints and Dependency Net Variant Configuration • Transfer of sales order requirements to PP • Delivery from sales order stock • Invoicing the customer Source: SAP
    Slide 69: Variant Configuration
    regards,
    amlan

Maybe you are looking for

  • Exception in finding the Home object Please Help

    Hi All, I am learning EJB. I wrote a bean called Hello Bean(from examples) which just prints out Hello. I tried calling it from the client program and I get this exception javax.naming.NameNotFoundException: Unable to resolve HelloLocalHome. Resolved

  • White background of extracted image prints in pdf

    Hi'ya Using the "Extract" filter to crop a photo in Photoshop 7.0 allowed me to extract a person from a photo and it was saved as a .psd file. In my InDesign 2.0.1 layout, the psd file looks great and as it was an extracted image, I can put things in

  • Without absolute path, SAXParser1.4   does not find schemLocation!!!!!

    Hello I am validating soap messages according to xsd files with the SAXParser, Java 1.4. My xsds include references to other xsd files as following sample shows: <xs:include schemaLocation="C:/temp/shiphome.xsd"/>       The problem is, how to say the

  • IPhone with my car ipod connection

    I have a 2007 with the built in ipod connection...will my iphone work in my car? im scared to plug my iPhone in. Please Help, thanx.

  • Latest Arch Linux & Huawei E398 GSM Modem

    Hello, I have a Huawei E398 GSM Modem running on the latest Arch linux. Kernel 3.8.10, modemmanager 0.7.990-4, usb_modeswitch  1.2.5-1, usbutils 006-1. The device was working properly until couple of days ago when I last used it. Now it doesn't show