SAP_Variant_Configuration_Overview.ppt

1、A,1,Variant Configuration Overview,All Trade Marks and logos used in the presentation are the copyright of the respective owner organizations.,Target Audience: SAP Functional Consultants Document Classification: For Internal Use Only,A,2,Overview,A,3,Variant Configuration,Variant Configuration,Sourc

2、e: SAP,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

3、a large number of material numbers. Usually involves Make to Order Production Process 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 st

4、eel manufacturing, the customer may order steel involving different physical properties like tensile strength, diameter.,A,4,Industries for Configurable Products,Variant Configuration,Source: SAP,A,5,Cross Module Integration,Variant Configuration,Source: SAP,Variant configuration is integrated with

5、the following applications: CA Classification LO Material Master PP Bill of Material PP Routings PP Material Requirements Planning (MRP) PP Production Orders PPPI Master Recipes CO Costing SD Sales SD Conditions MM Purchasing,A,6,Overview of Terms,Variant Configuration,Source: SAP,A,7,Overview of Te

6、rms,Variant Configuration,Source: SAP,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 Plan

7、ning. On Explosion of the Bill of Material, the system selects the components assigned to the characteristics values in the order. After production, the material is assigned as sales order stock for delivery to customer.,A,8,Sales Order Processing,A,9,IDES Demo,Variant Configuration,Source: SAP,Proc

8、ess 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 Creating a Delivery Creating a Billing Document,A,10,Enterprise

9、 Structure used for demo,Variant Configuration,Source: SAP,Company Code 1000,Sales Org 100,Distribution Channel 12,Division 00,Plant 1000,Storage Location 0001,Shipping Point 1000,A,11,MTO Process Overview,Variant Configuration,Source: SDN,Make-To-Order Production With a Configurable Product: In thi

10、s 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.,A,12,Creating

11、 a Sales Order (T Code :VA01),Variant Configuration,Source: SAP,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.,A,13,Creating a Sales Order (VA01),Variant Confi

12、guration,Source: SAP,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).,A,14,Configuration for VC,A,15,Configuration Details: Material Type,V

13、ariant Configuration,Source: SAP,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,A,16,Configuration Details: Item Category in sales order,Variant Configu

14、ration,Source: SAP,VOV4: Item Category determination is set to determine item category TAC,VOV8: Item Category TAC,A,17,Configuration Details: Condition type for Pricing,Variant Configuration,Source: SAP,Condition types VA00 and VA01 (%) are available in Standard SAP for Variant Pricing,A,18,Configu

15、ration Details: Requirement type KEK,Variant Configuration,Source: SAP,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 c

16、ategory TAC.,A,19,Classification System: Characteristics,Variant Configuration,Source: SAP,Mayback 57 S Engine Color Rear wheel Seat Exhaust Antitheft device Other Options,A,20,Classification System: Characteristics,Variant Configuration,Source: SAP,A,21,Classification System: Characteristics,Varian

17、t Configuration,Source: SAP,A,22,Classification System: Characteristics,Variant Configuration,Source: SAP,CT04: Create characteristics Data type can be CHAR, NUM, DATE, TIME, CURR,List of values and default value for characteristics can be stored in Value tab.,A,23,Reference Characteristics,Variant

18、Configuration,Source: SAP,Reference characteristics are characteristics that refer to table fields.,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 Configuratio

19、n 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,A,24,Classification System: Characteristics,Variant Configuration,Source: SAP,CT04: Create characteristics Object dependencies l

20、ike pre conditions, selection condition, action, procedures can be created for characteristics Object dependencies like pre conditions, action, procedure can be created for characteristic values,A,25,Classification System: Class,Variant Configuration,Source: SAP,CL01 /CL02: Create class under class

21、type 300 for Variants,Assign the characteristics to the class. During Material Master creation for Super BoM, this class will be used in the Classification view.,A,26,Material Master of Super BoM (MM02),Variant Configuration,Source: SAP,Basic Data 2 Screen: Set Material is Configurable Indicator To

22、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

23、: Attach the variant class,A,27,Bill of Materials (CS01 / CS02 / CS03),Variant Configuration,Source: SAP,A,28,Object Dependency in BoM (CS02),Variant Configuration,Source: SAP,Components in Production Order can be selected using Object Dependency type Selection Condition,A,29,Routings (CA02),Variant

24、 Configuration,Source: SAP,Operations in Production Order can be selected using Object Dependency type Selection Condition,A,30,Configuration Profile: Process,Variant Configuration,Source: SAP,Planned/production Order; explosion indicator None (others Single level or Multiple level) The material has

25、 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

26、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.

27、 The changed BOM is stored as a separate BOM for the sales order.,A,31,Configuration Profile: SET,Variant Configuration,Source: SAP,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

28、 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 componen

29、ts 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.,A,32,Configuration Profile: Dependencies,Variant Configuration,Source: SAP,Dep

30、endencies like Actions and Procedure can be assigned to Configuration Profile.,A,33,Configuration Profile: Variant Table,Variant Configuration,Source: SAP,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 f

31、ields: 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),VK30: Has description entries for the surcharge column listed above VK12: Will pick up pricing value based on

32、condition type VA00,A,34,Pricing,Variant Configuration,Source: SAP,Check definition of characteristic SURCHARGE2 Additional data tab - reference table and field,Simple method to achieve Variant Pricing is given below: Create multiple value characteristic SURCHARGE2 referring to SDCOM-VKOND. Put this

33、 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 S

34、elect 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,A,35,Pricing,Variant Configuration,Source: SAP,VK30: Maintain descriptions for variant pric

35、e conditions (optional step; done while creating dependencies for surcharges; maintains consistencies of configuration),VK11 / VK12: Maintain actual condition record for variant price surcharges,A,36,Pricing Factors,Variant Configuration,Source: SAP,Pricing factors can only be maintained on characte

36、ristic level. The syntax of pricing factors is as follows: $SET_PRICING_FACTOR ($SELF, , , ) 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 characteristi

37、c value. The factor by which the surcharge increases.,A,37,Material Variant,Variant Configuration,Source: SAP,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

38、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.,A,38,Material Variant in Sales Order,Variant Configuration,Source: SAP,On the value assignment screen, y

39、ou can check whether the values assigned match the configuration of a material variant.,A,39,Material Variant,Variant Configuration,Source: SAP,Replacement of configurable material by a material variant,A,40,Material Variant,Variant Configuration,Source: SAP,Item category gets changed to TAN; Pricin

40、g will also change as per new MTS product.,A,41,Summary of day 1,Variant Configuration,Source: SAP,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 Config

41、uration details like item category and condition types Classification System - Characteristics and Classes Super BoM, Configuration Profile, Object Dependencies Pricing Surcharges in sales order processing Using Material Variants for make to stock scenario,A,42,Day 2: Understanding Object Dependenci

42、es in detail,A,43,Dependency Types,Variant Configuration,Source: SAP,A,44,Pre Condition,Variant Configuration,Source: SAP,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

43、 precondition to value 21 of characteristic GEARS,A,45,Selection Condition,Variant Configuration,Source: SAP,A selection condition is allocated to each component and each operation. This selection condition determines which components and operations are selected for a variant.,A,46,Changing Master D

44、ata with Dependencies,Variant Configuration,Source: SAP,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 fi

45、eld MENGE can be used to change component quantities of BoM. Table PLPOD field VGW01 can be used to change setup time of Operation.,A,47,Procedures,Variant Configuration,Source: SAP,Procedures can set default values for a characteristic (can be overwritten by the user),A,48,Procedures,Variant Config

46、uration,Source: SAP,Set default values: $SET_DEFAULT ($SELF, , ) 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, , ) Produce a sum of the values for a characteristic in a multi

47、-level configuration: $SUM_PARTS ($SELF, ) 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 () Surcharge for variant conditions in Pricing: $SET_PRICING_FACTOR ($SELF, , ,

48、),A,49,Constraints and Dependency Net,Variant Configuration,Source: SAP,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

49、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. Constraints are grouped together in dependency nets. The dependency net can be allocated to a configuration pro

50、file. 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.,A,50,Actions,Variant Configuration,Source: SAP,Actions can be used to infer

51、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 Proc

52、edures rather than Actions (to become obsolete),A,51,Object Variables used in Multi level configurations,Variant Configuration,Source: SAP,A,52,Allowed Dependency Types,Variant Configuration,Source: SAP,Preconditions are allowed for characteristics and characteristic values. Selection conditions are

53、 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.,A,53,Pro

54、cessing Sequence for Dependencies,Variant Configuration,Source: SAP,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

55、, 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 c) Procedures for characteristic values The procedures for each characteristic or value are process

56、ed 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 13, if all the objects in the OBJECTS section ar

57、e present, and if all the conditions in the CONDITIONS section are fulfilled,A,54,Transfer to Production Planning (Demo),A,55,2. Checking Requirements Using MRP (T Code :MD04),Variant Configuration,Source: SAP,Step1 to create sales order has already been discussed earlier. 2. Stock Requirements List

58、: The sales order is displayed as a separate planning segment (sales order stock required on material availability date and sales order).,A,56,3. Requirements Planning (T Code :MD50),Variant Configuration,Source: SAP,The sales order will now be converted into a planned order. Planned Orders represen

59、t the first step toward an actual production schedule for the Shop Floor.,A,57,4. Convert the Planned Order into a Production Order (MD04),Variant Configuration,Source: SAP,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.,A,58,4. Convert the Planned Order into a Production Order (MD04),Variant Configuration,