PLM146 - Variant Configuration - Scenarios & Enhancements

© SAP AG 2006PLM146 Variant Configuration 3 - Scenarios & Enhancements THE BEST-RUN BUSI NESSES RUN SAP © SAP AG 2006 PLM146 Var i ant Conf i gur at i on – Sc enar i os & Enhanc ement s Þ SAP R/3 Enterprise Þ 2006/Q2 Þ Material number 50078818 © SAP AG 2003 Copyright 2005 SAP AG. All rights reserved. Neither this publication nor any part of it may be copied or reproduced in any form or by any means without the prior written consent of SAP AG. The information contained in this publication is subject to change without prior notice. Copyright Trademarks Þ Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Þ Microsoft, Windows, Outlook and PowerPoint are registered trademarks of Microsoft Corporation. Þ IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corp. in the USA and/or other countries. Þ ORACLE is a registered trademark of ORACLE Corporation. Þ UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Þ Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. Þ HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Þ J AVA is a registered trademark of Sun Microsystems, Inc. Þ J avaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. Þ MaxDB is a trademark of MySQL AB, Sweden. Þ SAP, R/3, mySAP.com, xApps, xApp and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in other countries worldwide. All other product and service names mentioned are the trademarks of their respective owners. Data contained in this document serves informational purposes only. National product specifications may vary. Þ The information contained in this publication is subject to change without prior notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. © SAP AG 2003 Course Prerequisites Required: ¤ PLM140 Variant Configuration 1 - Modeling ¤ Or thorough knowledge of the relevant functions (in R/3 4.5 or higher) ¤ (Overview course PLM100) Recommended: ¤ PLM143 Variant Configuration 2 - Integration ¤ PLM130 Classification ¤ SCM600 Processes in Sales and Distribution ¤ SCM200 Suppl y Chain Planning Overview ¤ SCM300 Suppl y Chain Manufacturing Overview © SAP AG 2006 Target Audience ¤ Course participants Þ Variant modelers for: 4 SAP ERP - Configurator 4 (SAP IPC - Sales Configuration Engine) ¤ Project team 4 DP organizers • Duration: 3 days Notes to the user Þ The training materials are not teach-yourself programs. They complement the course instructor's explanations. On the sheets, there is space for you to write down additional information. ©SAP AG PLM146 1-6 © SAP AG 2002 Contents: Course Overview ¤ Course Goals ¤ Course Objectives ¤ Course Content ¤ Course Overview Diagram ¤ Main Business Scenario ©SAP AG PLM146 1-7 © SAP AG 2002 This course will prepare you to: Model multi-variant products by building on your existing knowledge of variant configuration and examining its functions and handling in detail Course Goals ©SAP AG PLM146 1-8 © SAP AG 2002 At the conclusion of this course, you will be familiar with and be able to use: ¤ Advanced settings of the configuration profile and interface design ¤ Specialized aspects of object dependencies (specificall y constraints) ¤ Special features of the different scenarios ¤ Knowledge-based and result-oriented order BOMs ¤ Multilevel configuration structures ¤ Low-level and high-level configuration ¤ Additional tools (BAPI, ALE, user exits, and the anal ysis tool) ¤ The different ways of storing variant configuration data ¤ Hints on system performance Course Objectives ©SAP AG PLM146 1-9 © SAP AG 2002 Unit 1 Course Overview Unit 2 Variant Configuration: Consolidation Unit 3 Control Options in the Configuration Profile Unit 4 Configuration Scenario Without BOM Explosion Unit 5 More About Constraints Unit 6 More About Object Dependencies Preface Course Content ... ©SAP AG PLM146 1-10 © SAP AG 2002 Unit 7 Configuration Scenarios with BOM Explosion Unit 8 Configuration Scenarios with Order BOMs Unit 9 Other Variant Configuration Tools Unit 10 Conclusion Appendix 4 Data for Exercises 4 Structure of Examples in Exercises 4 Frequentl y Used Menu Paths 4 Ideas for Modeling Course Content ©SAP AG PLM146 1-11 © SAP AG 2002 Course Overview Diagram Control Options in the Configuration Profile 3 3 Configuration Scenarios Without BOM Explosion 4 4 Configuration Scenarios with Order BOMs 8 8 2 2 Configuration Scenarios with BOM Explosion 7 7 Variant Configuration: Consolidation More About Object Dependencies 6 6 Course Overview Course Overview 1 1 More About Constraints 5 5 Other Variant Configuration Tools 9 9 Conclusion 10 10 ©SAP AG PLM146 1-12 © SAP AG 2002 ¤ You are a manufacturer of multi-variant products. To map your multi-variant products, you want to use the variant configuration functions in SAP R/3. ¤ Your design process requires detailed knowledge of the functions and handling of variant configuration that are relevant to modeling. Main Business Scenario ©SAP AG PLM146 2-13 © SAP AG 2002 Contents: Variant Configuration: Consolidation ¤ Procedure for variant configuration modeling ¤ Classification system tools ¤ Material master, bills of material, and task lists ¤ Configuration profile ¤ Dependencies ¤ Pricing ¤ Material variants ¤ Customizing ©SAP AG PLM146 2-14 © SAP AG 2003 Variant Configuration: Consolidation: Unit Objectives With the help of an overview of the basics of variant configuration as covered by course PLM140: ¤ Use all the functions taught in PLM140 ¤ See where the new topics covered by course PLM146 fit into the modeling process as a whole At the conclusion of this unit, you will be able to: ©SAP AG PLM146 2-15 © SAP AG 2002 Control Options in the Configuration Profile 3 3 Configuration Scenarios Without BOM Explosion 4 4 Configuration Scenarios with Order BOMs 8 8 2 2 Configuration Scenarios with BOM Explosion 7 7 Variant Configuration: Variant Configuration: Consolidation Consolidation More About Object Dependencies 6 6 Course Overview 1 1 More About Constraints 5 5 Other Variant Configuration Tools 9 9 Conclusion 10 10 Variant Configuration: Consolidation: Course Overview Diagram ©SAP AG PLM146 2-16 © SAP AG 2002 ¤ You are designing the sol ution to a modeling task. ¤ A major concern is to keep an overview of the integrated objects. Variant Configuration: Consolidation: Business Scenario ©SAP AG PLM146 2-17 © SAP AG 2006 Dependencies Dependencies Preconditions Preconditions Constraints Constraints Procedure (action) Procedure (action) Selection Selection conditions conditions BOM BOM Configuration Configuration profile profile Routing Routing C Characteris haracteristics tics Material master Material master record record Classes Classes Modeling Variant Configuration Material Material variant variant Pricing Pricing Þ There are a number of individual steps to setting up a knowledge base for a configurable material. Þ First, you need the characteristics that describe the material. You assign the characteristics to a variant class. You maintain dependencies for the characteristics and characteristic values, to ensure that only allowed values can be selected. Þ You maintain settings for the configurable material in the material master. You create a configuration profile to define the configuration parameters. The material master record must be assigned to the variant class. Þ You define the components for manufacturing a configurable material in a super BOM and the operations for manufacturing a configurable material in a super task list. You assign object dependencies to the operations and components that are only required for specific variants. Þ Before you can configure a material for production, we advise you to simulate configuration, to check whether all the data is maintained correctly. ©SAP AG PLM146 2-18 © SAP AG 2002 Description, format, and control data Basic Data Basic Data Multilingual headings and descriptions Descriptions Descriptions List of allowed characteristic values Values Values Reference characteristics, document info records, and user interface Addnl Data Addnl Data Restriction to class types Restrictions Restrictions Classification of characteristic Classification Classification Screens for Maintaining Characteristics Þ Naming conventions: º Letters, figures, underscore, and hyphen º Characteristic names must start with a letter º Characteristic names containing a hyphen are allowed in object dependencies, but are not as easy to use. If you use a characteristic whose name contains a hyphen, you must use the expression SKEY to address the characteristic in dependencies. You enter the characteristic name in single quote marks: SKEY 'EXT-COLOR'. (For example, $self.skey‘EXT-COLOR‘ =‘red‘) º You can rename characteristics, because they are stored under an internal number. However, you cannot rename a characteristic that is used in dependencies. ©SAP AG PLM146 2-19 © SAP AG 2006 (When assigning values) Required: yes? no? Numeric val ue Number of characters (decimal pl aces) Unit Exponent di splay Templ ate Negati ve values NUM Character value Number of characters Templ ate Case sensiti ve Time value CHAR DATE TIME Currency value Date value CURR User-defi ned data type ... Entry Entry Format Format Entry + Format + Value Assignment ¤ Single value except class assignment & hierarchy values ¤ Multiple values ¤ Restrictable Indicator cannot be overwritten in class Þ The full functions of formats DATE, TIME, and CURR cannot be used in variant configuration. Þ You cannot use user-defined data types, because dependencies can only read single characteristics. Þ You use the Entry required indicator to define whether it is always obligatory to assign a value to the characteristic. Þ The allowed values and allowed intervals that you define are binding for value assignment, unless you define that additional values are also allowed. Þ You can overwrite characteristic values for a specific class. Þ Indicators for single value, multiple values, and restrictable: Þ The Single value indicator means that only one value can be assigned to an object. If you assign other classes or hierarchy nodes to this class, you can assign more than one value. This serves to restrict the allowed values. The Restrictable indicator denotes a special type of single-value characteristic, which can only be used in constraints. In R/3, you can only use Restrictable together with Single value. ©SAP AG PLM146 2-20 © SAP AG 2006 Variant class Classes of class type 300 (or similar) collect and manage the characteristics to which you assign values in the sales order. Variant Variant class class Classes Classes of of class class type type 300 ( 300 (or or similar similar) ) collect collect and manage and manage the the characteristics characteristics to to which which you you assign assign values values in in the the sales sales order. order. Class node Classes of type 200 (or similar) collect and manage the characteristics for specifying a precise component in the BOM Class Class node node Classes Classes of of type type 200 ( 200 (or or similar similar) ) collect collect and manage and manage the the characteristics characteristics for for specifying specifying a a precise precise component component in in the the BOM BOM Classes in Variant Configuration Þ The control parameters for a class type in Customizing define a class type as a variant class type or a class type for class nodes. Þ In the standard system, you can define an existing class type as a class type for class nodes or a variant class type. You can also define additional variant class types and additional class types for class nodes in Customizing. Þ The class type has central control functions for class maintenance. Þ You cannot change the class type once you have saved a class. Þ You define class statuses, classification statuses, organizational areas, text types, functions, and filters separately for each class type. Þ In the standard system, the class statuses for all class types are: º 0 =In preparation (only class maintenance allowed) º 1 =Released (no restrictions on use) º 2 =Locked (no classification allowed) ©SAP AG PLM146 2-21 © SAP AG 2002 Screens for Maintaining Classes Texts explaining the class Strings for finding the class by matchcode Keywords Keywords Texts Texts Data for standardized classes (DIN standards) Standard Standard Document Document Document info record and document link Characteristics Characteristics Basic Data Basic Data Addnl Data Addnl Data Characteristics of class General information, control data Additional data for class nodes Class Class- -specific specific overwrite overwrite ©SAP AG PLM146 2-22 © SAP AG 2002 Configurable Material ¤ Material number under which all variants of a product are stored in SAP R/3 ¤ Reference for all related objects (bills of material, task lists, configuration profiles, and so on) ¤ Essential control parameters, especiall y those for MRP and sales ¤ ¤ Material number under which all variants of a product Material number under which all variants of a product are stored in SAP R/3 are stored in SAP R/3 ¤ ¤ Reference for all related objects (bills of material, task Reference for all related objects (bills of material, task lists, configuration profiles, and so on) lists, configuration profiles, and so on) ¤ ¤ Essential control parameters, especially those for Essential control parameters, especiall y those for MRP and sales MRP and sales Þ The material master is the reference point for all other objects that are relevant to a product with multiple variants. The bills of material, task lists, and so on, are all created for the configurable material. Þ The material master contains essential control parameters, especially those that are relevant to material requirements planning (MRP) and sales. Þ In the standard system, material type KMAT is defined for configurable materials. However, you can define materials of other material types as configurable materials (by setting an indicator on the Basic data screen of the material master record) or define additional material types for configurable materials. ©SAP AG PLM146 2-23 © SAP AG 2006 Dynamic BOM Dynamic BOM Order BOM Order BOM Material BOM Material BOM Master data > Dependencies > Configured BOM BOM BOM (Super) BOM Þ Definition of a bill of material (BOM): a purpose-built, complete, formally structured list of the objects that make up an object. The list contains the description, object number, quantity, and unit of measure for all objects. Þ The BOM of a configurable material contains all the components that are used in all possible variants of the product. You use dependencies to configure the BOM. In other words, only the components that are required for a specific variant are selected. The BOM is exploded according to the characteristic values you assign. Þ If you define certain settings in the configuration profile, you can make manual changes to the BOM for a sales order. The BOM is then saved as an order BOM for the sales order. Þ You can change the BOM in a production order, as you can for production without variants. Þ Types of BOM items that are especially relevant to variant configuration are classes, non-stock items for materials of the material type KMAT, and variable-size items. ©SAP AG PLM146 2-24 © SAP AG 2002 (Super) Task List Dynamic operation sequence Dynamic operation sequence Copy function Copy function Routing Routing Task list > Dependencies > Configured task list Task list Task list Þ Definition of routing (task list): A routing is a task list that describes the process for producing a material or for performing a service. It contains all the operations, suboperations, and production resources/tools (PRTs) that are required to manufacture the material. Þ The super task list of a configurable material comprises the sequences, operations, suboperations, and PRT assignments that are required to manufacture all possible variants of the material. You use dependencies to select the correct operations for a specific variant. The task list is exploded according to the characteristic values assigned. Þ You can create a routing by copying the configuration simulation. You can also create a routing with reference to a sales order. Þ An alternative sequence lets you select alternative operations for an operation sequence. This can be useful to deal with either different production processes for different lot sizes, or capacity problems. A parallel sequence lets you process operations in parallel with other operations. Suboperations are subordinate to an operation, and can be used to calculate costs and capacity in more detail (control key). You can assign PRTs to any operation. Each production resource/tool must have a master record. ©SAP AG PLM146 2-25 © SAP AG 2006 Variant class ¤ Selecting a class type Þ Provides characteristics Þ Enables link to variant class Configuration Profile for a Material Material master ¤ Defining the configuration scenario ¤ Other control parameters Þ Allowed screens, initial screen Þ Availability check Þ Scenario-based control parameters Þ A configurable material must be linked to classes that have a variant class type, to provide the characteristics for configuration. This is just a general material-to-class assignment, without assigned values. Assigning values would restrict the allowed values. Þ You can assign a material to a class in any of the following situations: º In master data maintenance (material master) º In the classification menu (maintain allocation) º In the configuration profile Þ You can define how a BOM is exploded in configuration: º Value assignment on top level only º Interactive, multi-level configuration in sales order Þ Depending on the type of configuration profile, you can also define whether: º Manual changes to components are allowed º Whether an order BOM is fixed (created automatically) º How the order BOM is saved, and how fixing and instantiation works ©SAP AG PLM146 2-26 © SAP AG 2006 SETS characteristic VALUES or changes object items in the configuration, if the relevant object is included in the configuration MUST an object be included in the configuration? Can a characteristic or characteristic value be included in the configuration? The characteristic or characteristic value CAN be included in the configuration Describes dependencies between SEVERAL objects in the configuration Dependency Types Procedure Procedure (action) (action) Selection Selection condition condition Precondition Precondition Constraint Constraint Þ Dependencies describe the interdependencies between objects in the configuration process. Þ They are used in configuration to ensure that the configuration is complete and consistent. Þ Paradigms of the SAP configurator: º Declarative - The user only declares rules and data - The SAP System determines the processing sequence - The only exception: procedures º Object oriented - Dependencies for objects selected in configuration are read - Inheritance of dependencies ©SAP AG PLM146 2-27 © SAP AG 2003 ¤ Material variants ¤ Order BOMs ¤ Planning ¤ Engin. chg. mgmt ECM ¤ Engin. chg. mgmt OCM ¤ SCE configurator ¤ ... Interdependencies Between Objects in the Model Material master Characteristics & Values Variant class Task List Assign dependencies Material BOM Assign dependencies Pricing (condition records) Configuration profile Assign dependencies Assign dependencies Dependencies •Precondition •Sel. condition •Procedures •Actions •Constraints ©SAP AG PLM146 2-28 © SAP AG 2003 Pricing in SD O Create a multiple-value characteristic (such as SURCHARGE) with reference to field SDCOM-VKOND. O Create condition records of condition type VA00 (absolute amounts) and (or) VA01 (percentage amounts). (The entry in key field " Variant" is entirely your choice.) O Set up a pricing procedure in SD that reads condition types VA00 and (or) VA01. O Assign the condition record to the characteristic value, or create dependencies (procedures or actions) for the pricing characteristic (SURCHARGE) as follows: · $SELF.SURCHARGE = '<key field of condition record>' if characteristic ABC eq value 4711 ... · Assign dependencies to the characteristic values or configuration profile. 2,820 UNI Price Price Surcharge CPU XXL/Minitower 430 UNI Surcharge Modem 250 UNI Surcharge Sound card 340 UNI Total price 2,820 UNI Þ Pricing in R/3 sales is based on conditions. Objects in the configuration are described by characteristics and characteristic values. Pricing for configurable objects must therefore read the characteristics and values for a configurable material and SD conditions. Þ Create a reference characteristic (such as SURCHARGE) with reference to field SDCOM- VKOND. Þ Create condition records with condition type VA00 (absolute amounts) and/or VA01 (percentage amounts). You can use both VA01 and VA00 in pricing. The key for the condition records is your choice. (Caution: these keys are case sensitive.) Þ You create the one-to-one assignments between characteristic values and condition records using the user interface for configuration simulation. Þ You use dependencies (procedures) to assign condition record keys to the reference characteristic, and enter conditions if required. You usually assign the procedure to the configuration profile. Þ The following example illustrates the syntax: SURCHARGE is a reference characteristic for field SDCOM-VKOND. Surcharge_xyz is a variant condition key: º $SELF.<reference characteristic>=‘key of condition record’ IF <condition> - Example: $SELF.SURCHARGE =`Surcharge_xyz´ if EXTRAS eq `MODEM´ and EXTRAS eq `MOUSE´. ©SAP AG PLM146 2-29 © SAP AG 2003 Material Variants Status E Released E Locked E Incomplete CPU FAST Casing TOWER Color Blue Material: Material: Char. value assgmt Char. value assgmt Specific task list Specific BOM Routing Material-routing assignment BOM Configurable material assignment MRP: MRP group: 0065 Configurable product: Sales: Item category group: NORM PC_01 PC_01 PC Þ You create material variants with a material type that is kept in stock. Þ To let you assign characteristic values to a material variant, you link the material to the configurable material whose characteristics you want to use to describe the variant. º You can enter a cross-plant configurable material on the basic data screen. However, a cross-plant configurable material can only be used in purchasing. There, you can print out a document item with its assigned values. If you do not enter a plant-specific configurable material for the material, the characteristic values of the cross-plant configurable material are displayed. º Before you can use variant matching in SD, you must enter a plant-specific configurable material in the MRP data of the material master. Þ To assign values, choose Configure Variant. Þ You also need to define a BOM for material variants. You can either create a new BOM for the material, which is separate from the configurable material, or you can link the material variant to the BOM of the configurable material. The BOM is then interpreted and exploded according to the values you assign in the material master record. Þ You can also create a separate task list (routing) for the material variant, or use the task list of the configurable material. The task list for the configurable material is also interpreted and exploded according to the characteristic values assigned in the material master record. ©SAP AG PLM146 2-30 © SAP AG 2002 MARA Class type? 001 200, 300 Class groups Maintain object types Object table? Class status Organizational areas Text types Classification status Functions and filters Objects Default settings Characteristics groups Characteristic status Templates User profile Customizing for Classification Þ Menu path: In the SAP Reference IMG: Cross-Application Components -->Classification --> Classes/Characteristics Þ In Customizing for classification, under Characteristics, you can: º Define default settings º Define characteristics groups º Check the statuses supplied and change them if required º Define template characters and templates Þ The class statuses, organizational areas, text types for classes, classification statuses, and functions and filters for finding objects are defined separately for each class type. Class statuses and classification statuses are predefined in the standard system. You can check the statuses and change them if required. In the same way as for characteristics, you can define groups for classes. Class groups are not dependent on class type. ©SAP AG PLM146 2-31 © SAP AG 2002 Dependency status Dependency groups (For each object type): Configuration profile status Maintain settings Variant tables Variant functions Maintenance authorizations Customer enhancements Customizing for Variant Configuration Þ Menu path: In the SAP Reference IMG: Logistics General -->Variant Configuration ©SAP AG PLM146 2-32 © SAP AG 2003 Variant Configuration: Consolidation: Unit Summary ¤ These include: · Procedure for variant configuration modeling · Classification tools · Material master, bills of material, and task lists · Configuration profile · Dependencies · Pricing and material variants · Customizing With the help of an overview of the basics of variant configuration as covered by course PLM140: ¤ Use all the functions taught in PLM140 ¤ See where the new topics covered by course PLM146 fit into the modeling process as a whole You are now able to: ©SAP AG PLM146 3-33 © SAP AG 2002 Contents: Control Options in the Configuration Profile ¤ Function of the configuration profile ¤ Basic data and cl ass assi gnment ¤ Configuration initial screen Þ Configuration parameters Þ Settings Þ Sales order and order BOM processes ¤ Details of filter ¤ Details of interface design ©SAP AG PLM146 3-34 © SAP AG 2002 ¤ Define all settings in the configuration profile ¤ Explain the effects of the control options in the profile At the conclusion of this unit, you will be able to Control Options in the Configuration Profile: Unit Objectives ©SAP AG PLM146 3-35 © SAP AG 2002 Control Options in the Control Options in the Configuration Profile Configuration Profile 3 3 Configuration Scenarios Without BOM Explosion 4 4 Configuration Scenarios with Order BOMs 8 8 2 2 Configuration Scenarios with BOM Explosion 7 7 Variant Configuration: Consolidation More About Object Dependencies 6 6 Course Overview 1 1 More About Constraints 5 5 Other Variant Configuration Tools 9 9 Conclusion 10 10 Control Options in the Profile: Course Overview Diagram ©SAP AG PLM146 3-36 © SAP AG 2002 ¤ In the design phase, you need to determine which configuration scenarios to work with. One important factor is the business scenario: ATO = assemble-to-order (according to catalog) MTO = make-to-order (individual products) ETO = engineer-to-order (projects) Control Options in the Profile: Business Scenario ©SAP AG PLM146 3-37 © SAP AG 2002 Configuration Profile for a Material Variant class ¤ Selecting a class type Þ Provides characteristics Þ Enables link to variant class Material master ¤ Defining the configuration scenario ¤ Other control parameters Þ Allowed screens, initial screen Þ Availability check Þ Scenario-based control parameters ©SAP AG PLM146 3-38 © SAP AG 2003 ¤ Basic data ¤ Configuration initial screen see following slides Material Profile name P-501 Profile_1 Pump (Order BOM configuration) Basi c dat a Confign i niti al screen Cl ass Type Status Val i d From Start Logo 300 Variants Rel eased Cl ass Assignment Dependencies Configuration Profile: Basic Data Structure: ©SAP AG PLM146 3-39 © SAP AG 2003 Basi c dat a Confign i niti al screen Confign Parameters UserInterf Order BOM Sales Order BOM appli cati on PP01 Producti on - general Filt er Order Functi ons Component Avail abil ity Level of Detail Only Configurabl e Assembli es Configuration Profile: Configuration Initial Screen BOM Expl osi on None Sing-Level Multilevel Process Sales Order (SET) Order BOM Plnd/Prod. Order Knowl.-Based Result-Ori ented Configuration initial screen structure: ¤ Configuration parameters (7 configuration scenarios) ¤ User interface (all profile-specific settings) see following slides Depending on configuration scenario: ¤ Order BOM see following slides ¤ Sales order (manual changes allowed) ©SAP AG PLM146 3-40 © SAP AG 2003 Configuration Profile: Filters, Priority, and Simulation Filter: Option of restricting the BOM explosion in high-level configuration according to: - Object type (material, class, document, text) - Item category (D, I, K, L, M, N, R, T) - Item status (relevancy indicators) - Sort strings Priorit y of Configuration Profile: In dialog mode: Sequence of configuration profiles shown Without dialog (ALE, IDoc): Profile of highest priority (= lowest number) is selected Simulation of functions in Sales Engineering Planned order Þ The use of filters lets you restrict the explosion of BOMs in high-level configuration. The filters apply to all high-level configuration, so components that are not displayed because of the filter are ignored in both the sales order and in order BOM maintenance. Þ The BOM explosion in high-level configuration can be restricted by the level of detail in the configuration profile and the definition of BOM applications assigned to the configuration profile, as well as by filters. ©SAP AG PLM146 3-41 © SAP AG 2003 Configuration Profile: User Interface Confign initi al screen UserInterf Interface design All owed screens Char. value assgmt Result Master Data Confign structure Start wi th Settings Confign browser Char. val ue assgmt Resul t Master Data Confign structure Interface design is created in an interface-design profile: - Characteristics groups - Sequences - Relevancy to printing 1. " Current settings" 2. " User settings" 3. " Profile settings" - Language - Pricing - Display options - Scope - Default values - Configurator (Can be overwritten for user in configuration simulation) Settings for: (also alternative language) Authorization object C_LOVC_DSG Þ Interface design: Name of interface design: Any character string up to 18 characters (such as material number) Name is unique and linked internally with a number from the number range Checks for same name of interface design: Results in identical interface design Possible for materials with identical class assignment Class assignment can be changed later =>no check =>problem! Þ Configuration browser The configuration browser lets you navigate around the configuration structure, and at the same time displays the value assignment screen for the selected material, so that you can enter values. The configuration browser thereby replaces the configuration structure screen and value assignment screen, so you can only select the configuration browser if you have not selected these screens. Þ Settings º Can be defined in the configuration profile. They are then saved for the specific configuration profile. These settings have the lowest priority. ©SAP AG PLM146 3-42 º Can be defined on the value assignment screen. If you save these settings, they are saved for your user for all configuration profiles. These settings have a higher priority. º Settings that you define on the value assignment screen and do not save are known as the current settings. These settings have the highest priority. º However, you can switch between the 3 different settings at any time (provided that they exist). ©SAP AG PLM146 3-43 © SAP AG 2003 Settings for the order BOM: Maintenance in order allowed Automatic fixing Fix: Selected assys Instantiate: Selected assys Top down Top down Bottom up Bottom up (Only for result-oriented order BOM) Configuration Profile: Order BOM ©SAP AG PLM146 3-44 © SAP AG 2003 Configuration scenarios ¤ Planned/production order & no BOM explosion (= old Planned/production order - single-level) ¤ Planned/production order & single-level BOM explosion ¤ Order BOM & single-level BOM explosion ¤ Sales order and single-level BOM explosion ¤ Planned/production order & multilevel BOM explosion (= old Planned/production order - multilevel) ¤ Order BOM & multilevel BOM explosion (If knowledge-based = old Order BOM) ¤ Sales order & multilevel BOM Explosion (= old Sales order) Configuration Profile: Scenarios Þ Single-level BOM explosion for the header material. In other words, the (single-level) BOM of the material is exploded. The BOM explosion stops after this. Any configurable assemblies in this BOM can be configured, provided that their configuration profiles allow it. Þ Single-level BOM explosion for configurable assemblies according to the functionality above. The prerequisite for this is that the material above the assembly has a multilevel configuration scenario and its BOM has been exploded. ©SAP AG PLM146 3-45 © SAP AG 2002 Overview: Combinations of Scenarios Header Component Plnd/prod. No BOM explosion Single/multilevel Plnd/prod. order Single/multilevel Sales order Single/multilevel Order BOM Possible / allowed Possible / allowed, but onl y with same way of storing order BOM No effect -> This component is treated as though its profile did not exist or were not released. This profile is excluded from the profiles for selection. ( ) (Note 14 87 78) Single-level/ multilevel Order BOM Planned/Prod. No BOM explosion Single-level/ multilevel Sales order Single-level/ multilevel Plnd/prod. ( ) ©SAP AG PLM146 3-46 © SAP AG 2002 You are now able to: ¤ Define all settings in the configuration profile ¤ Explain the effects of the control options in the profile Control Options in the Profile: Unit Summary ©SAP AG PLM146 3-47 ©SAP AG PLM146 3-48 Control Options in the Configuration Pr – Exercises Unit: Control Options in the Configuration Profile Topic: Create Configuration Profile At the conclusion of these exercises, you will be able to: • Create detailed configuration profiles The exercise also covers: • Checking the master data required • Creating the characteristics, variant class, and configuration profile A configurable casing needs to be modeled. Material master records and the super BOM (without dependencies) already exist. Further master data needs to be maintained. Assign the characteristics, classes, and dependencies that you have created to your characteristics/class/dependency group T-##. All the data already exists for group 00. It may help you to use this data as a template to copy from. 1-1 Check the master data that already exists for modeling the configurable casing T-VB1##. 1-1-1 Display material master record T-VB1## with the basic data, sales, and MRP views. Use the following organizational levels: Plant: 1000 Sales organization: 1000 Distribution channel: 10 1-1-2 Display the BOM for your casing with usage 1 in plant 1000. Compare it with the slide "1. Customer Example Part Structure (Casing)" in the appendix. ©SAP AG PLM146 3-49 1-2 Create the characteristics, variant class, and configuration profile required for the example. 1-2-1 Create the following single-value characteristics (you can copy from group 00). The characteristics must be character format characteristics with 2 characters: Pump for T01_## Values: 01 Oil 02 Water 03 Waste water 04 Suspension Pump type T02_## Values: 01 Vacuum 02 Rotary 03 Wing 04 Wet pit 1-2-2 Create variant class T_VB1## for your configurable casing T-VB1## and assign the two characteristics you just created to this class. Assign the class to class group T-##. 1-2-3 Create a configuration profile for your configurable casing T-VB1##. Use a name of your choice for your profile. Assign your configurable casing to variant class T_VB1##. Set the following parameters: Process: Planned/production order BOM Explosion: None (Leave the rest as they default Check all other settings of the configuration profile, to see what the default settings for configuration profiles are. (Settings, …). ©SAP AG PLM146 3-50 Control Options in the Configuration Pr Solutions Unit: Control Options in the Configuration Profile Topic: Create Configuration Profile 1-1 1-1-1 User Menu → Material → Display → Display Current Display material master T-VB1## (current status): Views: Basic data 1 +2 Sales: Sales Org. Data 1 +2 Sales: General / Plant Data MRP 1 -4 Organizational levels: Plant: 1000 Sales organization: 1000 Distribution channel: 10 =>The material master record exists with at least these views for at least these organizational levels. 1-1-2 User Menu → Bill of Material → Material BOM → Display Display BOM with usage 1 in plant 1000. Compare it with the slide "1. Customer Example Part Structure (Casing)" in the appendix. 1-2 1-2-1 User Menu → Classification → Master Data → Characteristics Create single-value characteristics (you can copy from group 00): T01_## Pump for ©SAP AG PLM146 3-51 T-## 1 Released Character format (CHAR) 2 characters ©SAP AG PLM146 3-52 Values: 01 Oil 02 Water 03 Waste water 04 Suspension T02_## Pump type T-## 1 Released Character format (CHAR) 2 characters Values: 01 Vacuum 02 Rotary 03 Wing 04 Wet pit 1-2-2 User Menu → Classification → Master Data → Classes Create a variant class: T_VB1## 300 Variant class Casing T-VB1## 1 (Released) T-## Characteristics: T01_## T02_## 1-2-3 User Menu → Variant Configuration → Configuration Profile → Create Create a configuration profile for configurable material T-VB1##. Profile overview: 0-BOM(or any name) 300 (class type) Class assignment T_VB1## Configuration initial screen: Configuration parameters Process: Planned/production order BOM Explosion: None No further settings UserInterf No settings ©SAP AG PLM146 3-53 (On the Userinterf tab page, choose Settings and make a note of any default settings.) ©SAP AG PLM146 4-54 © SAP AG 2002 Contents: ¤ Overview of scenario ¤ Combinations of configuration profiles ¤ System performance and configuration profiles ¤ Selection conditions Þ Problems with $parent and $root Þ Table access Þ TYPE_OF Configuration Scenario: No BOM Explosion ©SAP AG PLM146 4-55 © SAP AG 2002 ¤ Model configuration tasks using the scenario without BOM explosion, taking account of elementary performance considerations ¤ Use cl ass nodes correctly in this scenario ¤ Formulate complex selection conditions At the conclusion of this unit, you will be able to: Configuration Scenario: No BOM Explosion: Unit Objectives ©SAP AG PLM146 4-56 © SAP AG 2002 Configuration Scenario: No BOM Explosion: Course Overview Diagram Control Options in the Configuration Profile 3 3 Configuration Scenarios Configuration Scenarios Without BOM Explosion Without BOM Explosion 4 4 Configuration Scenarios with Order BOMs 8 8 2 2 Configuration Scenarios with BOM Explosion 7 7 Variant Configuration: Consolidation More About Object Dependencies 6 6 Course Overview 1 1 More About Constraints 5 5 Other Variant Configuration Tools 9 9 Conclusion 10 10 ©SAP AG PLM146 4-57 © SAP AG 2002 ¤ Your configurable product is modeled in its entirety. This means that you do not need order- specific post-processing for the BOM and routing. ¤ The configurable product is configured on one level. The product structure is not relevant to sales. Configuration Scenario: No BOM Explosion: Business Scenario ©SAP AG PLM146 4-58 © SAP AG 2002 Shaft assembl y (No profil e) Rtg Chars: COLOR GLOSS Class: Class: Color Color Characteristics: Pump for: Oil, Water, Waste w. Mode Pump type: Plunger, Rotary ... Connection: RAngle, Rd2, Rd4 ... IDES Example: No BOM Explosion P-500 (Plnd/prod, 0 levels) Rtg Shaft (No profil e) Rtg Slug Linchpin Casing G Casing A Casing C Support Bearing A Bearing B Bearing C ©SAP AG PLM146 4-59 © SAP AG 2002 Sales order 10 P-500 (Pump) Assigned char. values Pump Sales order 10 P-500 (Pump) ¤ Onl y BOM master data ¤ Characteristic value assignment on top level Single-level, interactive value assignment Single-level, interactive value assignment Sales / Customer Super BOM (Master data BOM) P-500 (Pump) Shaft Shaft assy Pump for Mode Pump type Connection Oil Manual Plunger Right-angled flange . . . . . . Configuration Scenario: No BOM Explosion: Overview Values for Pump ... Values for Pump ... Configuration Scenario: No BOM Explosion Þ Value assignment: values are only assigned to the item in the sales order. (You can use constraints here.) Þ Configuration: dependencies for BOM items are not processed until you explode the BOM (in material requirements planning (MRP), for example). Constraints are ignored. º Dependencies for subordinate configuration profiles cannot (!) be processed. Dependencies for BOM items are processed, but only the values assigned to the header material can be used. º BOM explosion: - is simulated in the simulation environment - does not take place in the SD / sales order - takes place in MRP Þ Material requirements: independent requirements are generated for the item entered in the sales order. Þ Type matching only occurs on the top level. Material variants (previously known as stockable types) are only found for the object that is being configured. This function is not available for configurable materials on lower levels. ©SAP AG PLM146 4-60 © SAP AG 2002 ¤ Onl y the $ROOT object can be interactivel y configured in the sales order. ¤ Onl y the material you enter ($ROOT object) becomes a (main) item in the SD sales order. ¤ Components and operations are determined automatically during the MRP run and when creating the production order. There is onl y a dynamic BOM or sequence of operations in the sales order. ¤ You can simulate the explosion of the BOM or task list in the simulation environment. ¤ The ATP availability check can be run from the sales order. Configuration Scenario: No BOM Explosion: Important Points Þ The function for creating order-specific routings is not affected by settings for the configuration scenario, so this function can be used here. Þ Note: The authorization object for an interface design is: C_LOVC_DSG ©SAP AG PLM146 4-61 © SAP AG 2002 No profile No BOM explosion Planned/prod. order Single-level explosion Planned/prod. order Multilevel explosi on Planned/prod. order Multilevel explosi on Sales order Single-level explosion Sales order Multilevel explosi on Order BOM Single-level explosion Order BOM Combinations of Configuration Scenarios Effective Same as No profile *) Same as No profile *) Same as No profile *) Same as No profile *) Same as No profile *) Same as No profile *) Same as No profile *) *) =Can be used in purchase orders in purchasing No BOM explosion No BOM explosion Planned/prod. order Planned/prod. order Þ When you create a sales order for a configurable material with the scenario No BOM explosion, you can only assign characteristic values to the header material, so only the dependencies for the configuration profile of the header material are active. Þ You cannot assign values to a configurable assembly with a profile. However, you can use the profile in purchasing in the following way: º Assign the characteristics of the assembly to the variant class of the header material, as well as to the assembly. In purchasing documents, the values assigned to the header material are copied to the characteristics of the variant class of the assembly. ©SAP AG PLM146 4-62 © SAP AG 2003 General for all scenarios: ¤ Few or no " allowed screens" ¤ Limited BOM explosion: ¤ Number of levels ¤ BOM application ¤ Filter ¤ Indicator " Configurable assemblies only" System Performance and Configuration Profiles ©SAP AG PLM146 4-63 © SAP AG 2002 Configuration Profile on Top Level Onl y Shaft assembl y (No profile) Selection condition: $root.EXTRAS eq 'With... or $parent.EXTRAS eq 'With... not $self.EXTRAS eq 'With... Selection condition: $root.CONNECTION eq 'Rd2' or $parent.CONNECTION eq 'Rd2' not $self.CONNECTION eq 'Rd2' $root = header $parent = next instance Characteristics: Pump for: Oil, Water, Waste w. Mode Pump type: Plunger, Rotary Connection: RAngle, Rd2, Rd4 Extras: With support, ... P-500 (No BOM explosion) Support Bearing A Bearing B Bearing C Þ $self is not possible in selection conditions. Þ In this scenario, you can only query values assigned to the header material, $root. Þ In this scenario, you can also use $parent to query values assigned to the header material. Þ The default is $root. ©SAP AG PLM146 4-64 © SAP AG 2002 Configuration Profile on Several Levels Characteristic Connection - No interactive value assgmt - Dependencies cannot infer value Selection conditions: Characteristic Connection cannot be used $parent $root Characteristics: ... Connection: RAngle Rd2 Rd4 Characteristics: Pump for: Oil, Water, Waste w. Mode Pump type: Plunger, Rotary ... P-500 (No BOM explosion) Shaft assembl y (No BOM explosion) Bearing A Bearing B Bearing C Þ Characteristics CONNECTION, and so on, of assembly SHAFT ASSEMBLY cannot have values assigned to them in the sales order, if you create a sales order for the Pump P-500. Þ No data can be saved for the shaft assembly. Þ In purchasing, a configuration profile for the shaft assembly can be used as a filter. If I create a purchase order for the shaft assembly, and the shaft assembly has no configuration profile, all the values assigned to the header material are copied to the purchase order. If I create a purchase order for the shaft assembly, and the shaft assembly has a configuration profile, the values assigned to the header material are only copied to the purchase order if the characteristics are also assigned to the configuration profile of the shaft assembly. ©SAP AG PLM146 4-65 © SAP AG 2002 Class Nodes in This Scenario Caution ! Caution ! Color is read onl y if no Color is read onl y if no values for class node values for class node Class: Class: Color Color Characteristics: Color: Red, Blue, Green Gloss: yes/no Characteristics: Pump for: Oil, Water, Waste w. Mode ... Color: Red, Blue, Green No manual specialization of class node with this scenario Onl y automatic specialization of class node possible, by: - Value assignment on value assignment interface or - Value assignment for class node by procedure Action $self.GLOSS = 'Yes' if ... P-500 (Plnd/prod, 0 levels) Þ If the value assigned to characteristic COLOR is sufficient to specialize the class node, you can work this way. Þ If 2 different materials have the value 'Blue' and one has GLOSS 'Yes' while the other has GLOSS 'No', and no value is assigned to characteristic GLOSS, you have no influence over which material is selected in material requirements planning (MRP). Þ To optimize system performance, if you use class nodes with automatic specialization, use an additional selection condition for cases where no material is needed or no material can be found. ©SAP AG PLM146 4-66 © SAP AG 2002 Application: ... CPU: ... Hard disk: ... Sales order Selection condition: Selection condition: Selection condition: Selection condition: APPLICATION eq ’PHOTO' and CPU eq ’fast' and Hard disk eq ’ large' OR APPLICATION eq ’PHOTO' and CPU eq ’fast' and Hard disk eq ’ medium' OR...... APPLICATION eq ’PHOTO' and CPU eq ’ fast' and Hard di sk eq ’ large' OR APPLICATION eq ’PHOTO' and CPU eq ’ fast' and Hard di sk eq ’ medium' OR...... APPLICATION eq ’TEXT' and CPU eq ’medi um' and Hard disk eq ’ medi um' OR APPLICATION eq ’SERVER' and CPU eq ’standard' and Hard disk eq ’large' OR...... APPLICATION eq ’TEXT' and CPU eq ’ medium' and Hard disk eq ’medi um' OR APPLICATION eq ’SERVER' and CPU eq ’ standard' and Hard di sk eq ’l arge' OR...... Confble matl Confble matl Selection Conditions (Complex) RAM: giant RAM: large RAM: standard Þ If you want a BOM item or operation to be selected according to complex selection conditions, it is often useful to define tables with the allowed combinations of values and use selection conditions to access the table. ©SAP AG PLM146 4-67 © SAP AG 2003 Table SEL Application Hard disk CPU PHOTO PHOTO SERVER SERVER Large Medium Large Large Fast Fast Medium Medium Slow TEXT Medium Char. 4 A A B C C Each line represents a valid combination of characteristic values Table and (Complex) Selection Conditions Þ If you want to access one table in selection conditions for several BOM items, you must define in the table which table line refers to which BOM item. To do this, you create an additional characteristic (the 4th characteristic, in this example) to identify the BOM item. Þ For each selection condition, you enter the characteristic value that is to trigger the selection condition. Þ The table is only read if all its characteristics have values assigned in the sales order. If no entry in the table matches the values assigned, no component is included in the exploded BOM. Þ Example of a selection condition: º table SEL (APPLICATION =$parent.APPLICATION, HARD_DISK =$parent.HARD_DISK CPU =$parent.CPU, CHAR_4 ='A') ©SAP AG PLM146 4-68 © SAP AG 2002 KMAT KMAT Confi gurable BIKE KMAT KMAT Confi gurable MOPED Selection Condition Without TYPE_OF Pump Selection condition: Selection condition: EXTRAS EXTRAS eq eq 'PUMP' 'PUMP' Extras: Extras: Pump Pump ... ... Sales order Extras: Extras: Pump Pump ... ... Sales order KMAT KMAT Extras KMAT KMAT Extras Þ If a configurable assembly is used multiple times as a component, there are 2 possibilities: Þ 1.) Without TYPE_OF º In the selection condition, only the values assigned to the header material are used. A selection according to the type of the header material is not possible. ©SAP AG PLM146 4-69 © SAP AG 2002 Selection condition: Selection condition: TYPE_OF ($ROOT, (300)MOPED) AND EXTRAS eq 'BELL' TYPE_OF ($ROOT, (300)MOPED) AND EXTRAS eq 'BELL' Selection condition: Selection condition: Selection Condition with TYPE_OF KMAT KMAT Confi gurable BIKE KMAT KMAT Confi gurable MOPED TYPE_OF ($ROOT, (300)BIKE) AND EXTRAS eq 'BELL' TYPE_OF ($ROOT, (300)BIKE) AND EXTRAS eq 'BELL' Extras: Extras: Bell Bell ... ... Sales order Extras: Extras: Bell Bell ... ... Sales order KMAT KMAT Extras KMAT KMAT Extras Bell 2 Bell 1 Þ 2.) With TYPE_OF º In the selection condition, the values assigned to the header material and the type of the header material are both used. Þ Reference to header material using material number: º TYPE_OF ( $ROOT, (MATERIAL) (300) ( NR ='BIKE' ) ) Þ Reference to header material using class number: º TYPE_OF ( $ROOT, (300) BIKE ) ©SAP AG PLM146 4-70 © SAP AG 2003 Configuration Scenario: No BOM Explosion: Unit Summary ¤ Model configuration tasks using the scenario without BOM explosion, taking account of elementary performance considerations ¤ Use class nodes in this scenario ¤ Formulate complex selection conditions, using: Þ $parent and $root Þ Multiple table calls Þ TYPE_OF You are now able to: ©SAP AG PLM146 4-71 ©SAP AG PLM146 4-72 Configuration Scenario: No BOM Exp Exercises Unit: Configuration Scenario: No BOM Explosion Topic: Selection Conditions with Table Calls At the conclusion of these exercises, you will be able to: • Maintain multiple table calls with selection conditions The exercise also covers: • Table maintenance The conditions under which several components are selected are to be stored in a variant table and accessed using selection conditions. Assign the characteristics, classes, and dependencies that you have created to your characteristics/class/dependency group T-##. All the data already exists for group 00. It may help you to use this data as a template to copy from. Read through the entire exercise before you start. 1-1 describes the task as a whole. 1-1 Assign selection conditions to the three casing items in the BOM of your configurable casing T-VB1##(graycast, aluminum, and steel) to ensure that the components are selected according to the following list: Pump for: Pump type: 500-101 (Graycast): Oil Vacuum Waste water Vacuum 500-102 (Aluminum): Oil Wet pit Waste water Rotary Suspension Wet pit 500-103 (Steel) Water Rotary Water Wing Waste water Wing ©SAP AG PLM146 4-73 ©SAP AG PLM146 4-74 1-1-1 Create variant table T_SEL_COND_## that maps the possible combinations shown above. Remember that an additional characteristic is required to represent the casing types. Enter exactly one value for each characteristic in each table line. The additional characteristic must be a character format characteristic with one character. This is important for another exercise later on (link between variant table and database table). 1-1-2 Create selection conditions that refer to this table and assign the selection conditions to the relevant BOM items. Remember that the casing can be an assembly in another structure. ($root or $parent?) 1-1-3 Test the result. ©SAP AG PLM146 4-75 Configuration Scenario. No BOM Explo Solutions Unit: Configuration Scenario: No BOM Explosion Topic: Selection Conditions with Table Calls 1-1 1-1-1 User Menu → Classification → Master Data → Characteristics Create additional characteristic for mapping casing types. Create: T03_## Casing type T-## Character format (CHAR) 1 character Values: 1 Graycast 2 Aluminum 3 Steel User menu→ Variant Configuration → Tools → Table Structure → Create Create variant table: T_SEL_COND_## Table for selection conditions 1 (Released) T-## Characteristics: T01_## T02_## T03_## (No key required) ©SAP AG PLM146 4-76 User menu→ Variant Configuration → Tools → Table Contents → Maintain Fill variant table: T_SEL_COND_## T01_## T02_## T03_## Table maintenance: 01 (Oil) 01 (Vacuum) 1 (GC) 01 (Oil) 04 (Wet pit) 2 (Alu) 02 (Water) 02 (Rotary) 3 (St.) 02 (Water) 03 (Wing) 3 (St.) 03 (Waste water) 01 (Vacuum) 1 (GC) 03 (Waste water) 02 (Rotary) 2 (Alu) 03 (Waste water) 03 (Wing) 3 (St.) 04 ( Suspension) 04 (Wet pit) 2 (Alu) (GC=Graycast, Alu=Aluminum, and St.=Steel.) 1-1-2 (Create global dependencies during assignment) User Menu → Bill of Material → Material BOM → Change T-VB1## Plant: 1000 Usage: 1 ...(Item Overview) → Pushbutton = Ctrl + F1 or Extras → Object dependencies → Assignments Selection condition for component: 500-101 (Graycast): T_SC_T03_##_1 table T_SEL_COND_## (T01_## = $parent.T01_##, T02_## = $parent.T02_##, T03_## = '1' ) similarly (by copying the above selection condition): Selection condition for component: 500-102 (Aluminum): T_SC_T03_##_2 … T03_## = '2' ) Selection condition for component: 500-103 (Steel): ©SAP AG PLM146 4-77 T_SC_T03_##_3 … T03_## = '3' ). ©SAP AG PLM146 4-78 1-1-3 User menu→ Variant Configuration → Environment → Configuration Simulation Configuration simulation: T-VB1## Plant: 1000 (Sales/distribution) (BOM) =>Final state can be checked in result (BOM application PP01) or in planned order ©SAP AG PLM146 5-79 © SAP AG 2002 Contents: More About Constraints ¤ Overview and system performance ¤ Application examples for the INFERENCES section ¤ Value assignment for class nodes ©SAP AG PLM146 5-80 © SAP AG 2002 ¤ Process equations and tables in ways that are not covered by procedures (actions) ¤ Use restrictable characteristics ¤ Name the options for improving system performance with regard to constraints and variant tables More About Constraints: Unit Objectives At the conclusion of this unit, you will be able to: ©SAP AG PLM146 5-81 © SAP AG 2002 More About Constraints: Course Overview Diagram Control Options in the Configuration Profile 3 3 Configuration Scenarios Without BOM Explosion 4 4 Configuration Scenarios with Order BOMs 8 8 2 2 Configuration Scenarios with BOM Explosion 7 7 Variant Configuration: Consolidation More About Object Dependencies 6 6 Course Overview 1 1 More About Constraints More About Constraints 5 5 Other Variant Configuration Tools 9 9 Conclusion 10 10 ©SAP AG PLM146 5-82 © SAP AG 2002 ¤ Modeling in larger configuration structures ¤ Use of functions onl y available in constraints More About Constraints: Business Scenario ©SAP AG PLM146 5-83 © SAP AG 2002 ¤ Infer values and check consistency Between any objects in a configuration task ¤ Active in configuration only No effect on BOM and task-list explosion in low-level configuration (in MRP, for example) Cannot replace selection conditions and procedures ¤ Additional functions Dependency net Constraint 3 Constraint 3 Constraint 2 Constraint 2 Constraint 1 Constraint 1 Constraints Constraints Constraints Þ Constraints are especially necessary for multilevel, interactive configuration. º Constraints read or write characteristic values as well as: - The configurable material and its assigned classes or class structures - Multiple levels of the BOM structure or class hierarchy º The additional functions that constraints provide are also useful in single-level configuration. Constraints can and should be used instead of actions to set up the user interface for value assignment. Þ Constraints are only active during interactive configuration. Constraints are ignored when you explode a BOM or task list dynamically in material requirements planning (MRP) or when you create a production order. Þ Constraints can only be created locally within a constraint net. You assign the constraint net to the configuration profile. ©SAP AG PLM146 5-84 © SAP AG 2002 ¤ INFERENCES Þ Definition of which characteristic values are to be inferred (from equations, tables, or functions) ¤ RESTRICTION(S) Þ Relation between elements in the OBJ ECTS section that must be true º Value inference and consistency check º Direct or using variant functions and variant tables ¤ CONDITION Þ Prerequisite for processing the constraint ¤ OBJECTS Þ Declaration of all classes and objects used Parameters in a Constraint Þ A constraint has up to 4 sections, but has at least the 2 sections OBJ ECTS and RESTRICTIONS. You only use the CONDITION and INFERENCES sections if required. Þ These sections are always in the same order. Þ You can close each section with a period. ©SAP AG PLM146 5-85 © SAP AG 2002 Declaration of other object (such as material) Declaration of an object (class) OBJECTS Section (Declaration) (Material) Object identifier (300) (300) Class Class type type (Nr Partial key name 'PC_01') 'PC_01') Partial key Partial key value value (300) (300) Class Class type type PC PC Class name Class name = Þ To declare an object, you enter the class type and class name. Þ To declare a specific object, such as a material, you enter: º Object identifier defined in Customizing º Class type (optional) º Name of the partial key for the object, as defined in Customizing º Partial key value (the partial key for a material is the material number ) Þ Quote marks and parentheses must be used as shown. If you do not enter the class type, you must enter empty parentheses ( ). Þ Example of document declaration: º (Document) (017) (Type =`DRW´ , Version =`00´ , Part =`000´ , Nr =`P-100´) ©SAP AG PLM146 5-86 © SAP AG 2002 Variables for Objects, Classes, and Characteristics ; , (300) PR ... . (Material) (300) (Nr = (Material) (300) (Nr = ' ' PC_01') PC_01') Object declaration for material Object declaration for material Vari able Variable name name Vari able Variable name name (300) PC (300) PC Object declaration for class Object declaration for class X X Y Y SW SW OS OS Vari able Variable name name Software Software Operating system Operating system Characteristic Characteristic name name (300) PC where is_a is_object = = Þ Constraint variables are subject to the same naming conventions as characteristics and classes. However, you can start the name with a query (?). The variables only apply locally in the constraint. Examples of valid variable names: X or ?X or ?my_variable Þ Convention for object declaration of a class: <variable name>is_a <class> Other object declaration: <variable name>is_object <object> Þ In the above example, X replaces the expression (300) PC. Þ Variables replace complex expressions in the following sections of a constraint: º SW replaces (300) PC.SOFTWARE º OS replaces (300) PC.OPERATING_SYSTEM. Þ Use a comma to separate lists of the following equivalent expressions: º Object or class declarations in the OBJ ECTS section º Objects in the INFERENCES section º Actions in the RESTRICTIONS section Þ Use a semicolon to separate equivalent expressions in a list of characteristic declarations. Þ You can use a period to close each section, such as the OBJ ECTS section. ©SAP AG PLM146 5-87 © SAP AG 2003 ¤ Optional ¤ Syntax: similar to preconditions Þ Logical expression Þ No $self, $parent, $root, or TYPE_OF Þ Additional terms: PART_OF and SUBPART_OF ¤ Function: condition for processing constraint CONDITION Section Þ In the CONDITION section, you specify when the constraint is processed. A constraint is only processed if the condition in this section is true. Þ The syntax of the CONDITION section is similar to the syntax of a precondition or selection condition. However, the following differences apply: º Instead of $self, $parent, or $root, you name either the object or its variable º TYPE_OF is not allowed º You can use variables for objects, classes, and characteristics º You can use logical expressions of any complexity, including nested disjunctions and conjunctions (AND, OR and parentheses) Þ In addition, you can use the expressions PART_OF and SUBPART_OF. You use PART_OF to check whether one material or document is in the BOM of another. SUBPART_OF checks the same thing across multiple levels of the BOM. Þ In the condition section and in IF conditions in the restrictions section, statements such as the following are false if the characteristic has no value assigned: º <characteristic>=<characteristic value> Þ The functioning of such statements is the same as in preconditions and selection conditions. ©SAP AG PLM146 5-88 © SAP AG 2003 ¤ Syntax: similar to actions Þ Object variables instead of $self, $parent, and $root Þ Additional term: " false" ¤ Function: similar to actions Þ Calculates additional values as in INFERENCES section Þ Checks all values for consistency RESTRICTIONS Section Þ Constraints are declarative dependencies. Þ You can use the following elements in the RESTRICTIONS section, as for actions: º Formulas º Tables and functions º Calculation of values on the left-hand side of an equation, if the restriction is an equation Þ SAP R/3 checks whether the restriction is fulfilled. If it is not, the configuration is inconsistent. This also applies if the constraint calculates characteristic values. If a single-value characteristic already has a value of another origin (such as user entry): º If the value is different, an inconsistency is generated º If the value is the same, an additional explanation is saved ©SAP AG PLM146 5-89 © SAP AG 2002 Automatic: Þ By assigning values to relevant characteristics for superior configuration profiles Manual: Þ By finding objects in the class, if scenario allows Procedure for class node: Constraint: Value Assignment for Class Nodes PC ... Class node ($self.COLOR = 'Red', $self.GLOSS = '0' ) if CASING = 'TW' objects: (300) PC where CS = CASING , (200) HUE where COL = COLOR ; GL = GLOSS . restrictions: COL = 'red' if CS eq 'TW', GL = '0' if CS eq 'TW'. Onl y in scenarios " sales order " or " order BOM" Onl y in scenarios Sales order or Order BOM Þ Caution: Constraints can only be used to assign values to class nodes in high-level configuration. For this reason, such constraints only work if the replaced component is saved. This is only possible in the scenarios "sales order" and "order BOM". ©SAP AG PLM146 5-90 © SAP AG 2002 part_of, subpart_of in the CONDITION Section part_of (PC, PC package) is true. part_of (PC, PC package, ‘0015’) is true. part_of (Casing, PC package) is false. subpart_of (PC, PC package) is true. subpart_of (casing, PC package) is also true. part_of refers to a component of a BOM and the material for which the BOM was created. subpart_of also refers to several levels of the BOM. PC package PC Monitor Casing CD drive 15 ©SAP AG PLM146 5-91 © SAP AG 2002 ¤ Each characteristic variable in the RESTRICTIONS section can be inferred ¤ Applies to: Þ Formulas Þ Tables Þ Function calls in the RESTRICTIONS section ¤ Conditions: Þ The variable is in the INFERENCES section. Þ Conversion is mathematically possible or a key is defined. Þ Variable is not in any conditional section. INFERENCES Section Þ The INFERENCES section can only contain characteristic variables - separated by commas. Þ If you call a table or function, the relevant access key must be defined (value assignment alternative of table or function). Þ If you use arithmetical expressions, it must be possible to solve them with the variables in the INFERENCES section. ©SAP AG PLM146 5-92 © SAP AG 2002 objects: (300) PC where OS = OPERATING_SYSTEM, (300) PRINTER where PD = PRINTER_DRIVE. restrictions: PD = OS objects: (300) PC where OS = OPERATING_SYSTEM, (300) PRINTER where PD = PRINTER_DRIVE. restrictions: PD = OS inferences: PD , OS Package PC Printer Examples of Constraints Þ The constraint returns an inconsistency if the RESTRICTIONS section is not true. The RESTRICTIONS section can also infer values. Þ Without an INFERENCES section, you can only infer values in the same way as with procedures (or actions). Further values can only be inferred by using the INFERENCES section. Þ In the above examples, the characteristic values (not the value descriptions) must be the same. ©SAP AG PLM146 5-93 © SAP AG 2002 objects: (300) Special_casing where D = Depth; W= Width; H = Height; V = Volume. restrictions: V = D * W * H. inferences: V , D , W , H. ¤ The RESTRICTIONS section can be processed in any direction. Þ If three variables (=n-1) are known, the fourth (last) can be inferred. Equations Þ R/3 converts the equation to the following additional equations: º D =V / W / H º W =V / D / H º H =V / D / W Þ As soon as three values are known, R/3 finds the appropriate equation and executes it. Þ Variant tables and variant functions with alternative selection function in a similar way. º If you use variant functions, it is the responsibility of the programmer to ensure that the inverse equation exists and is called. Þ To optimize system performance, only trigger the conversions you really need in the INFERENCES section. ©SAP AG PLM146 5-94 © SAP AG 2002 Table CS Printer Monitor CPU Inkjet Laser_1 20" 21" Standard Medium Laser_2 24" Fast Check and inference of correct values Each column is unique Each characteristic can be used as a key Check table for all keys Use INFERENCES section Value assignment alternatives Constraints with Tables and INFERENCES (1) Þ Values are only inferred if the key has complete values. Otherwise, processing is terminated and the table is ignored. Þ If processing of the table produces ambiguity, a runtime error occurs. ==>Check the table! Þ You cannot define dependencies for table entries. ©SAP AG PLM146 5-95 © SAP AG 2002 OBJECTS: PC IS_A (300)PC. RESTRICTIONS: table CS (PRINTER = PC. PRINTER, MONITOR = PC. MONITOR, CPU = PC. CPU ). INFERENCES: PC. PRINTER, PC. MONITOR, PC. CPU Constraints with Tables and INFERENCES (2) Table CS Printer Monitor CPU Inkjet Laser_1 20" 21" Standard Medium Laser_2 24" Fast Þ Table CS is for inferring values for characteristics PRINTER, MONITOR, and CPU. Þ The allowed value combinations are defined in table CS. Þ Value assignment alternatives must be defined to infer values for all three characteristics. Þ For each characteristic (value assignment key), the table allows values to be inferred for the other two characteristics. This means that each characteristic represents its own complete key. ©SAP AG PLM146 5-96 © SAP AG 2003 Allowed combinations Allowed values Char. Language Printer handbook Software handbook D E S D OS handbook F D D E E E F F D;E;S S S S P S S;E S;E R R D;E D;E D;E;F;S;P;R D;E;F;S;R D;E;S D;E;F;S No value assignment alternatives Variant Table for Constraints with Restrictable Characteristics Þ Purpose: º When a value is entered for one or more characteristics in the list above, the missing values (for characteristics language and handbook language for printer, operating system, and other software) are to be inferred. - If this is not possible, the result is a restriction to the values still allowed. Þ In constraints, you can restrict the allowed values for a characteristic, as well as inferring values. The characteristics on the value assignment user interface (assigned to the variant class) must be single-value and restrictable. Þ To manage the allowed values of a characteristic dynamically, you can refer to a table. A key is required to do this. Þ Enter the characteristics whose allowed values you want to restrict in the INFERENCES section. ©SAP AG PLM146 5-97 © SAP AG 2003 OBJECTS: PC IS_A (300)PC. RESTRICTIONS: table LANGUAGE (LANGUAGE =PC.LANGUAGE, PRINTER_HB =PC.PRINTER_HB, OS_HANDBOOK =PC.OS_HANDBOOK, SOFTWARE_HB =PC.SOFTWARE_HB). INFERENCES: PC.LANGUAGE, PC.PRINTER_HB, PC.OS_HANDBOOK, PC.SOFTWARE_HB). Language Printer handbook Software handbook D E S D OS handbook F D D E E E F F D;E;S S S S P S S;E S;E R R D;E D;E D;E;F;S;P;R D;E;F;S;R D;E;S D;E;F;S (HB =Handbook) Constraints with a Variant Table and Restrictable Characteristics ©SAP AG PLM146 5-98 © SAP AG 2002 ¤ Collect constraints in a small number of nets ¤ Use the CONDITION section ¤ Set up the CONDITION section as a " disjunctive standard form" , making purely " or" relations from any purely " and" relations: Exampl e: (a1 and ... and an) or (b1 and ... and bn) ... Exampl e: not a or not b (instead of not (a and b) ) ¤ Use characteristic variables if you use a characteristic more than once in a constraint ¤ Only enter what you really need to enter in the INFERENCES section System Performance and Constraints To improve system performance: To improve system performance: ©SAP AG PLM146 5-99 © SAP AG 2003 ¤ - Variant tables without runtime objects + Vari ant tables with runtime objects ++ Transparent tables ¤ Runtime objects: Þ Created and updated automatically as of R/3 4.5 Þ (up to R/3 4.0): Display/change/create in table structure Extras Runtime object Activate System Performance and Variant Tables To improve system performance: To improve system performance: Þ Variant tables without runtime objects existed only up to R/3 4.0x. ©SAP AG PLM146 5-100 © SAP AG 2003 ¤ Four sections of a constraint: - OBJECTS - CONDITION - RESTRICTIONS - INFERENCES Functions of each section? ¤ INFERENCES section and equations, tables, and functions ¤ Constraints and restrictable characteristics ¤ Class nodes ¤ System performance when using constraints and variant tables ... More About Constraints: Unit Summary ©SAP AG PLM146 5-101 ... More About Constraints Exercises Unit: ... More About Constraints Topic: Restrictable Characteristics and Constraints At the conclusion of these exercises, you will be able to: • Maintain constraints with restrictable characteristics The exercise also covers: • Creating the characteristics and variant tables required Three characteristics need to be included in the user interface for value assignment of your casing, and only certain combinations of values can be assigned to them. Dependencies are to be used to ensure that it is not possible to enter inconsistent values. In other words: If values are assigned to these three characteristics, only allowed values are displayed for the other characteristics. If the allowed values are restricted to exactly one value, this value is set by the system. 1-1 Create the following single-value restrictable characteristics for the user interface for value assignment (you can copy from group 00): Language T05_## Values: en English de German fr French es Spanish pt Portuguese ru Russian Documentation T06_## Values: en English de German es Spanish ru Russian ©SAP AG PLM146 5-102 ©SAP AG PLM146 5-103 Inscription T07_## Values: en English de German ru Russian Assign these characteristics to the class for the casing T_VB1##. 1-2 The values that can be set (either manually or by the system) for characteristics Language, Documentation, and Inscription are as shown in the table below: Language Documentation Inscription de de;en de;en en en en fr en;es en es en;es en pt en;es en ru ru;en ru;en Create variant table T_CONSTRAINT_## that maps the possible combinations shown above. 1-3 Create constraint net T_CN_VB1##for the casing. Assign constraint T_CS_VB1##to this constraint net. This constraint ensures that values can only be assigned manually or by the system according to the above variant table. The constraint net must be assigned to the configuration profile of the configurable casing T-VB1##. 1-4 Check the result in configuration simulation. ©SAP AG PLM146 5-104 ... More About Constraints Solutions Unit: More About Constraints Topic: Restrictable Characteristics and Constraints 1-1 Remember to use your group number! When copying, change the group number from T-00 to your group number. User Menu → Classification → Master Data → Characteristics For all 3 characteristics: T-##(group) 1 Released Character format (CHAR) 2 characters Single-value restrictable Language T05_## Values: en English de German fr French es Spanish pt Portuguese ru Russian Documentation T06_## Values: en English de German es Spanish ru Russian Inscription T07_## Values: en English de German ru Russian User Menu → Classification → Master Data → Classes ©SAP AG PLM146 5-105 Change variant class: T_VB1## 300 Characteristics: T05_## T06_## T07_## User menu→ Variant Configuration → Tools → Table Structure → Create Create variant table structure: T_CONSTRAINT_## Table for constraint 1 (Released) T-## Characteristics: T05_## (Key T06_## column T07_## blank) (Key is not required here.) User menu→ Variant Configuration → Tools → Table Contents → Maintain T_CONSTRAINT_## Table for constraint T05_## T06_## T07_## Language Documentation Inscription de de;en de;en en en en fr en;es en es en;es en pt en;es en ru ru;en ru;en (View: Table Maintenance) Button: Display options → Indicator: All Values To use this variant table in the SAP IPC SCE (although it is not the purpose of this course to cover SCE), the table must be normalized. To do this, choose (from the table maintenance view) Table Untag. 1-3 User menu→ Variant Configuration → Dependency → Dependency Net → Create ©SAP AG PLM146 5-106 Create constraint net T_CN_VB1## with constraint T_CS_VB1##. Create constraint net: T_CN_VB1## 1 (Released) !!! T-## (group) Assign and create constraint at the same time: T_CS_VB1## T-## (group) objects: (300)T_VB1## where LANGUAGE = T05_##; DOCUMENTATION = T06_##; INSCRIPTION = T07_##. restriction: table T_CONSTRAINT_## (T05_## = LANGUAGE, T06_## = DOCUMENTATION, T07_## = INSCRIPTION) inferences: LANGUAGE, DOCUMENTATION, INSCRIPTION – Check and save syntax – Release and save constraint – Release, check, and save constraint net User Menu → Variant Configuration → Configuration Profile → Change Change configuration profile: for material T-VB1## Pushbutton: Assign object dependencies Assign constraint net T_CN_VB1## 1-4 Configuration simulation: T-VB1## 1000 Sales/distribution and BOM =>Check final state ©SAP AG PLM146 5-107 ©SAP AG PLM146 6-108 © SAP AG 2002 Contents: More About Object Dependencies ¤ Variant tables and database tables ¤ Variant functions ¤ Characteristic selection and configuration profile ¤ Information from the sales order and object dependencies ¤ Structure VCSD_UPDATE ¤ Structure SCREEN_DEP ©SAP AG PLM146 6-109 © SAP AG 2003 More About Object Dependencies: Unit Objectives ¤ Maintain table calls and function calls ¤ Link variant tables to database tables and transfer data between them ¤ Use multiple classification and class hierarchies in variant configuration ¤ Select characteristics in configuration profile maintenance by using different class types or organizational areas ¤ Read information from the sales order and use dependencies to write to fields in the sales order ¤ Use structure SCREEN_DEP for interface design At the conclusion of this unit, you will be able to: ©SAP AG PLM146 6-110 © SAP AG 2002 More About Object Dependencies: Course Overview Diagram Control Options in the Configuration Profile 3 3 Configuration Scenarios Without BOM Explosion 4 4 Configuration Scenarios with Order BOMs 8 8 2 2 Configuration Scenarios with BOM Explosion 7 7 Variant Configuration: Consolidation More About More About Object Dependencies Object Dependencies 6 6 Course Overview 1 1 More About Constraints 5 5 Other Variant Configuration Tools 9 9 Conclusion 10 10 ©SAP AG PLM146 6-111 © SAP AG 2002 ¤ For further modeling of your configurable product, you need more detailed information on suitable object dependencies. More About Object Dependencies: Business Scenario ©SAP AG PLM146 6-112 © SAP AG 2003 System Performance and Dependencies ¤ Define global dependenci es if used more than once (if local, dependency must be loaded several times) ¤ Value check using function module, instead of precondition restrictable characteri stics with constraint and variant table ¤ Do not mix procedures, actions, and constraints (value inferences should not influence each other) Þ Training systems contain function module Z_VALUE_CHECK for demo purposes. This is used in course PLM130 as a value check. ©SAP AG PLM146 6-113 © SAP AG 2003 Variant Tables - Summary Preconditions, Value Value sel. conditions, inference restrictions if... (set values) Key no yes no required? (First key onl y n keys) Table contents no yes no unambiguous? (for all keys) ambiguity => runtime error no entry => terminates no error Access All chars Key always when? have values has value (First key, one key) Variant Variant table table inferences inferences: Usage: Þ Describing allowed combinations of values (access only if all characteristics have values assigned) in selection conditions, preconditions, constraints, and in IF conditions of procedures and actions. Þ Inference of characteristic values (access only if all keys have values assigned) in procedures, actions, and constraints. Þ Restricting allowed values (immediate access) in special constraints. Restrictions: Þ Try to use only single-value characteristics in the table structure. Þ In simple dependencies (not constraints) only the first value assignment alternative can be used. Þ All characteristics required to access the table must have values assigned, or the dependencies terminate. Þ If no value is inferred (for example, missing table entry)? Dependencies terminate: value to be inferred is not defined. ©SAP AG PLM146 6-114 © SAP AG 2003 Linking Variant Tables (1) 1) Variant tables without links - See system performance tips " System Performance and Variant Tables" in unit " More About Constraints" 2) Use existing database tables as variant tables ¬Create structure of variant table (basic data, characteristics) ¬ In basic data of variant table: enter database table ¬ Link active Field assignment ©SAP AG PLM146 6-115 © SAP AG 2003 Linking Variant Tables (2) 3) Link existing variant table to new database table ¬Create database table in ABAP Workbench and activate it Here: - Define field names with suitable data elements (format) - For all characteristics used as keys in the variant table, define corresponding fields as keys (unambiguous) ¬Link variant table to database table (as in 2): In basic data of variant table: enter database table ¬ Link active Field assignment ¬Data transfer: variant table to database table In menu for variant configuration Tools Function Table structure Table contents Maintai n Transfer to database tabl e Database operat ions Insert Insert and change Insert, change, and del ete ©SAP AG PLM146 6-116 © SAP AG 2003 Variant Functions - Summary Functions Functions ¤ Additional functions in dependencies by using ABAP programs Usage: Procedure: ¤ Define input and output characteristics ¤ Define an ABAP program ¤ Create a function that calls the ABAP program ¤ Enter the function in a dependency, such as a procedure, and link the dependency to the configuration profile (keyword: FUNCTION) and assign dependencies to (for example) the configuration profile Þ In variant configuration, you can use your own ABAP programs to describe interdependencies that are not covered by the standard dependencies. ©SAP AG PLM146 6-117 © SAP AG 2002 Example of a Variant Function function z_t146 (char1_f = char1_o , char2_f = char2_o , char3_f = $self.char3_o) function z_t146 (char1_f = char1_o , char2_f = char2_o , char3_f = $self.char3_o) Similar to variant tables: Variant configuration Tools Functions Characteristics Keys Similar to variant tables: Variant configuration Tools Functions Characteristics Keys Interface: Table parameters and exceptions Function module Function module Table parameters Ref. structure Exceptions QUERY MATCH CUOV_01 CUOV_01 FAIL Internal_ERROR Interface: Import and export parameters Import parameter Ref. field Global CUOV_00 3. Create a function that calls the ABAP program 2. Define an ABAP program 1. Define input and output characteri stics 4. Enter the function i n a dependency (action, for exampl e) ©SAP AG PLM146 6-118 © SAP AG 2002 Class Hierarchy and Multiple Classification LENGTH: 1 LENGTH: 1 - - 10 10 COLOR: R, B, G COLOR: R, B, G WIDTH: 3 WIDTH: 3 - - 30 30 VERSION: E, S, L VERSION: E, S, L HEIGHT: 2 HEIGHT: 2 - - 20 20 LENGTH: 4 - 7 HEIGHT: 2 - 20 COLOR: R, B, G VERSION: E, S WIDTH: 3 - 30 Values: VERSION: E, S Values: LENGTH: 2 -7 Values: LENGTH: 4 -9 Class hierarchy Multiple classification Configurable product Class 1 Class 1 Class 3 Class 3 Class 2 Class 2 Class 5 Class 5 Class 4 Class 4 Þ In variant configuration you can use classes that are part of a class hierarchy. Þ Characteristics that are assigned to classes in a class hierarchy are always inherited by the subordinate classes. The allowed values of inherited characteristics can be restricted for the subordinate class. Þ The Single value attribute of a characteristic is not active in assignments of classes to other classes, so the allowed values can be restricted to any range of values. ©SAP AG PLM146 6-119 © SAP AG 2002 Selecting a Class by the Class Type Configurable product Configurable product Char: VERSION HEIGHT WIDTH COLOR Char: VERSION HEIGHT WIDTH COLOR Char: WIDTH COLOR Char: WIDTH COLOR Char: VERSION HEIGHT Char: VERSION HEIGHT Class 6 Class 6 Type 300 Type 300 Class 7 Class 7 Type 300 Type 300 Conf. prof. A Type 300 Char: WIDTH COLOR Conf. prof. B Type 300 Char: VERSION HEIGHT Class 6 Class 6 Type 300 Type 300 Class 8 Class 8 Type 301 Type 301 Conf. prof. A Type 301 Conf. prof. B Type 300 Þ You can create additional variant class types. Þ You can select a variant class type for each configuration profile. Þ Several active configuration profiles result in a selection screen in the sales order. Do you want this? Þ 1. Multiple classification with one class type º If all the classes assigned to the configurable material have the same variant class type, you cannot define which characteristics of which class are displayed in any more detail. Þ 2. Multiple class types - one classification per class type º If all the classes assigned to the configurable material have different variant class types, you can select a class in the profile by selecting a variant class type. The characteristics of this class are then displayed. Þ You can combine these forms as required. ©SAP AG PLM146 6-120 © SAP AG 2002 Char: Org.area WIDTH R COLOR T Selecting Characteristics by the Organizational Area Char: Org.area VERSION E LENGTH E,F Class 6 Class 6 Org.area: E,F Org.area: E,F Class 7 Class 7 Org.area: R,T Org.area: R,T Conf. prof. A Org.area: E,R Conf. prof. B Org.area: F,T Char: VERSION LENGTH WIDTH Char: LENGTH COLOR Configurable product Þ Organizational areas are defined per class type in Customizing. º 1. In basic data of class, assign organizational areas to class º 2. Assign organizational areas to characteristics º 3. Assign organizational areas to configuration profiles Þ Organizational areas are only relevant to the user interface: you must still assign a value to required characteristics. Þ The authorization object for organizational areas is C_TCLS_BER. You must still assign a value to required characteristics. If you are not authorized to assign all required values, the configuration can only be saved with status "incomplete". ©SAP AG PLM146 6-121 © SAP AG 2002 Reading Information from the Sales Order Syntax: $SELF.PUMP_FOR = 'Oil' if CUSTOMER eq 'Acme Oil Company'. Solution: Solution: Procedure that refers to a reference Procedure that refers to a reference characteristic for the sales order characteristic for the sales order (such as CUSTOMER) (such as CUSTOMER) Concept: If the customer is called Acme Oil Company, the pump is always for oil Þ In dependencies, you can process any information you want from the current sales order. To do this, you need reference characteristics. Þ For constraints, you must enter the reference characteristics in the variant class (characteristic that is hidden during value assignment). Þ To find the name of the table field, choose the F1 help, then Technical info. ©SAP AG PLM146 6-122 © SAP AG 2002 Writing Information to the Sales Order Syntax: $SELF.WEIGHT = 45 if PUMP_TYPE eq 'Wet pit'. Solution: Solution: Procedure that refers to a reference Procedure that refers to a reference characteristic for the sales order characteristic for the sales order (such as VCSD_UPDATE). (such as VCSD_UPDATE). Concept: Depending on the customer's choice (assigned values), the weight of the pump is calculated. Then it is updated in the sales order item. Þ As of R/3 4.5, you can also use dependencies directly with individual fields in the sales order item. These are: º Gross and net weight +unit º Volume +unit º Cumulative order quantity +sales unit º Counter +factor for converting sales unit to storage unit º Target quantity +target quantity unit º Counter +factor for converting target quantity unit to storage unit º Description Þ For constraints, you must enter the reference characteristics in the variant class (characteristic that is hidden during value assignment). Þ To find the name of the table field, choose the F1 help, then Technical info. ©SAP AG PLM146 6-123 © SAP AG 2002 ¤ Tables whose field values can be changed by dependencies: Þ SDCOM Structure for communication between SD and variant configuration Þ MMCOM Structure for communication between MM and variant configuration Þ VCSD_UPDATE Structure for updating the sales document Þ STPO BOM item fields Þ PLPO Operation fields in routing Þ PLFH Production resource/tool fields Þ PLFL Operation sequence fields Þ SCREEN_DEP Dynamic change to how characteristic is displayed Reference Characteristics - Write Access Þ In table SDCOM, field VKOND, you maintain variant conditions for determining surcharges and discounts during value assignment, by entering reference characteristics that refer to these fields in dependencies, or in characteristics maintenance. Þ In purchasing, field VKOND in table MMCOM is used for maintaining variant conditions. Þ In table PLPO, not all fields can be changed. Structure PLPO_CFMOD defines which fields can be changed. ©SAP AG PLM146 6-124 © SAP AG 2002 Reference Characteristics - Read-Only Access ¤ Sales order tables whose field values can be read by dependencies: Þ VBAK Header data Þ VBAP Item data Þ VBKD Commercial data Þ MAEPV Material master fields Þ MAAPV Material master fields Þ VEDA Contract data Þ VBPA_AG Partner: Sold-to Party Þ VBPA_WE Partner: Ship-to Party Þ VBPA_RE Partner: Bill-to Party Þ VBPA_RG Partner: Payer Þ You can use reference characteristics to refer to these sales order tables. However, dependencies have read-only access to fields in these tables. You cannot use dependencies to change field values. ©SAP AG PLM146 6-125 © SAP AG 2002 Options: Options: ¤ Hide characteristic ¤ Characteristic ready for i nput, manual value assignment possible ¤ Characteristic displayed only, no manual value assignment ¤ Delete dynamically set parameters = Override settings defined in characteristic Structure SCREEN_DEP INVISIBLE INPUT NO_INPUT RESET Dynamic Change to User Interface Status (1) ©SAP AG PLM146 6-126 © SAP AG 2002 Dynamic Change to User Interface Status (2) ¤ Create multiple-value reference characteristics for structure SCREEN_DEP ¤ Create action and assign to profile (for example) Syntax: $self.<reference char.> = '<characteristic to be influenced>' if <condition> Example: reference characteristic DISPLAY with reference to SCREEN_DEP - NO_INPUT $SELF.DISPLAY = 'PUMP_TYPE' if ......... Procedure: Procedure: ©SAP AG PLM146 6-127 © SAP AG 2003 More About Object Dependencies: Unit Summary ¤ Maintain table calls and function calls ¤ Link variant tables to database tables and transfer data between them ¤ Use multiple classification and class hierarchies in variant configuration ¤ Select characteristics in configuration profile maintenance by using different class types or organizational areas ¤ Read information from the sales order and use dependencies to write to fields in the sales order ¤ Use structure SCREEN_DEP for interface design You are now able to: ©SAP AG PLM146 6-128 ... More About Object Dependencies Exercises Unit: More About Object Dependencies Topic: Linking Variant Tables At the conclusion of these exercises, you will be able to: • Link variant tables to database tables • Transfer data from a variant table to a database table To optimize system performance for object dependencies, you want to work with database tables. You do not want to work with variant functions here. Table maintenance will be carried out in the variant table. 1 You want to link your variant table T_SEL_COND_## to an existing database table and transfer the contents. 1-1 Display the existing database table ZTPUMP_## in the Data Dictionary. Transaction SE11 – add this to your favorites. Make a note of the field names, keys, field types or data types, and field lengths: 1. _________________________ 2. _________________________ 3. _________________________ 4. _________________________ 1-2 Check that the table is empty. Transaction SE16 – add this to your favorites. ©SAP AG PLM146 6-129 1-3 Create the link between variant table T_SEL_COND_## and the database table. Assign fields 1 to 3, in that order, to characteristics T01_##to T03_##, in that order. Activate the link. You want to link the variant table for your selection conditions to the database table. Make sure that you do not use the wrong variant table. 1-4 Transfer the table contents of the variant table to the database table. 1-5 Check that the table contents of the database table are correct. (The rest is optional) Insert a new entry in the variant table. Make sure that your new entry is a new combination of pump medium (pump for) and pump type. Change the casing type in one of the existing entries. Transfer the changed data to the database table, by using Insert and change. Check the result in the database table. ©SAP AG PLM146 6-130 ... More About Object Dependencies Exercises Unit: More About Object Dependencies Topic: Object Dependencies with Information from the Sales Order At the conclusion of these exercises, you will be able to: • Use reference characteristics to query information in the sales order You have included three language characteristics in the user interface for value assignment. When assigning values to these characteristics, you want to use information from the sales order or the location of the sold-to party. 2 Use a reference characteristic T09_## to create a link to table field VBPA_AG- LAND1 (country of origin of sold-to party). Assign this reference characteristic to your variant class. The country of origin will be used to set the value of language characteristic T05_## automatically. Check the result by creating a sales order. Exit the sales order without saving. Order type: OR =(Standard order) Sales organization: 1000 Distribution channel: 10 Division: 00 ---------------------------------------------------------- Sold-to party: 1000 Ship-to party: 1000 Purchase order number: (Your choice) ©SAP AG PLM146 6-131 ©SAP AG PLM146 6-132 ... More About Object Dependencies Exercises Unit: More About Object Dependencies Topic: Object Dependencies for Changing Information in the Sales Order, Using Structure VCSD_UPDATE At the conclusion of these exercises, you will be able to: • Perform recursive calculations • Change individual fields in a sales order item by using object dependencies and reference characteristics The weight of your material (the configurable casing) depends on the configuration. This means that you need to make it possible to change the gross and net weight in the sales order item, depending on the characteristic values assigned. 3-1 You want to use dependencies to change the weight specifications in the sales order item. To do this, you need reference characteristics for structure VCSD_UPDATE. Create reference characteristics T19N_## and T19B_##, for transferring the net and gross weight to the sales order item. (Reference to table fields VCSD_UPDATE-NTGEW and VCSD_UPDATE-BRGEW.) These reference characteristics should not be displayed on the value assignment screen. The net weight from the material master record is to be used in the calculation. Create reference characteristic T19_##, referring to table field NTGEW (net weight) in table MAAPV. (Reference to table field MAAPV-NTGEW) Assign the characteristics to your variant class. 3-2 The net weight in the material master applies to vacuum pumps. The net weight for rotary pumps is 1.5 kg more. The net weight for wing pumps is 2 kg more. The net weight for rotary pumps is 3.5 kg more. The gross weight is 10% more than the net weight. ©SAP AG PLM146 6-133 Create a procedure that transfers the net weight and gross weight to the sales order item, depending on the values assigned. 3-3 Check the result by creating a sales order. Exit the sales order without saving. ©SAP AG PLM146 6-134 ©SAP AG PLM146 6-135 ... More About Object Dependencies Exercises Unit: More About Object Dependencies Topic: Object Dependencies with Structure SCREEN_DEP and recursive calculations At the conclusion of these exercises, you will be able to: • Perform recursive calculations • Dynamically change how characteristics are displayed by using structure SCREEN_DEP Our pump program is designed so that the maximum pump capacity derives automatically from the pump type and pump medium (pump for). You want to use procedures to calculate the maximum pump capacity and show the result in the sales order. The pump capacity must always be calculated by the system. To ensure that this happens, this characteristic must only be displayed once a value has been assigned to it. It must not then be possible to enter the value manually. 4-1 Create numeric characteristic T04_## for the pump capacity, with allowed values from 1,000 – 100,000 l/h, and assign this characteristic to your class. 4-2 Create dependencies that calculate the pump capacity according to the following rules: The pump capacity for a plunger or vacuum pump is 5,000 l/h. The pump capacity for a wet pit pump is 4,000 l/h. The pump capacity for a wing pump is 8,000 l/h. The pump capacity for a rotary pump is 6,000 l/h. The pump capacity doubles for waste water, triples for oil, and quadruples for water. (optional: Check the dependencies in configuration simulation.) ©SAP AG PLM146 6-136 4-3 The pump capacity must always be calculated by the system. If the system has not calculated a value, the characteristic for the pump capacity must not be displayed. To do this, create a reference characteristic T10_## with reference to table SCREEN_DEP and field INVISIBLE. Once the system has calculated the pump capacity (according to the value assigned to the pump-type characteristic), the characteristic for pump capacity is displayed, but the value cannot be changed. To do this set the appropriate characteristic indicator. Test the result in the simulation or by creating a sales order (but exit the sales order without saving). ©SAP AG PLM146 6-137 .. More About Object Dependencies Solutions Unit: More About Object Dependencies Topic: Linking Variant Tables 1 1-1 Insert transaction SE11 (ABAP Dictionary) in your favorites: Favorites → Insert transaction (= Ctrl + Shift + F4) or: SAP Menu → Tools → ABAP Workbench → Development → ABAP Dictionary = SE11 → Favorites → Insert (= Ctrl + Shift + F6) Display database table ZTPUMP_##. => Fields 1. MANDT (Key) Clnt 3 characters 2. FIELD1 (Key) Char 2 characters 3. FIELD2 (Key) Char 2 characters 4. FIELD3 Char 1 character (The status is after the table name. This must be "active".) 1-2 Add transaction SE16 (data browser) to your favorites: Favorites → Insert transaction (= Ctrl + Shift + F4) or: SAP Menu → Tools → ABAP Workbench → Development → Data Browser = SE16 → Favorites → Insert (= Ctrl + Shift + F6) Check the table contents: Database table ZTPUMP_## ¬Enter Leave selection screen blank ¬ Execute =F8 =>empty ©SAP AG PLM146 6-138 1-3 User Menu → Variant Configuration → Tools → Table Structure → Change Variant table T_SEL_COND_## Database table ZTPUMP_## ¬ Enter → Pushbutton: Field assignment T01_## Field1 (use F4 help) T02_## Field2 T03_## Field3 → Back Activate link and save 1-4 User menu: → Variant Configuration → Tools → Table Contents → Transfer to Database Table Variant table T_SEL_COND_## "Insert" ¬ Execute = F8 =>8 Inserted data records 1-5 Favorites → Data Browser (SE16) Database table ZTPUMP_##(All 8 entries exist) (optional) New entry in variant table: For example: 01 (Oil) 02 (Rotary) 3 (Steel) Change existing entry: For example line 1: 01 (Oil) 01 (Vacuum) 3 (Steel) User menu: → Variant Configuration → Tools → Table Contents → Transfer to Database Table Variant table T_SEL_COND_## Insert and Change ¬ Execute =>Warning message: Entries already exist in database table. =>1 inserted data record, 1 changed data record Favorites → Data Browser (SE16) Database table ZTPUMP_## (Now 9 entries exist) ©SAP AG PLM146 6-139 ... More About Object Dependencies Solutions Unit: More About Object Dependencies Topic: Object Dependencies with Information from the Sales Order 2 User Menu Classification → Master Data → Characteristics Create characteristic: T09_## ¬ Create Straight to Additional Data Table: VBPA_AG Field: LAND1 Leave all settings as in ABAP Dictionary Characteristics group: T-## User Menu Classification → Master Data → Classes Change variant class: T_VB1## 300 Characteristics: Add T09_##(Ignore warning message) User Menu → Variant Configuration → Configuration Profile → Change Change configuration profile: for material T-VB1## Pushbutton: Assign dependencies =Ctrl +F9 Create procedure during assignment: 40 T_PROC_T09_## (The country of origin will be used to set the value of language characteristic T05_## automatically.) Syntax: $self.T05_## = $self.T09_## ©SAP AG PLM146 6-140 Check the result by creating a sales order. Exit the sales order without saving. SAP Menu → Logistics → Sales and Distribution → Sales → Order → Create = VA01 or Favorites → Create Sales Order = VA01 Order type: OR =(Standard order) Sales organization: 1000 Distribution channel: 10 Division: 00 --------------------------------------------------------- Sold-to party: 1000 Ship-to party: 1000 Purchase order number: (Your choice) T-VB1## 1 piece ¬ Value assignment screen =>Language filled according to country key (Exit order without saving) ©SAP AG PLM146 6-141 ... More About Object Dependencies Solutions Unit: More About Object Dependencies Topic: Object Dependencies for Changing Information in the Sales Order, Using Structure VCSD_UPDATE 3-1 Create reference characteristic for updating the net weight in the sales order: User Menu Classification → Master Data → Characteristics Create characteristic: T19N_## ¬ Create Straight to Additional Data tab page Table: VCSD_UPDATE Field: NTGEW Leave all settings as in ABAP Dictionary Except. Select No Display (!) Characteristics group: T-## Create reference characteristic for updating the gross weight in the sales order: Create characteristic: T19B_## ¬ Create Straight to Additional Data tab page Table: VCSD_UPDATE Field: BRGEW Leave all settings as in ABAP Dictionary Except. Select No Display (!) Characteristics group: T-## Create reference characteristic for reading the net weight from the material master: Create characteristic: T19_## ¬ Create Straight to Additional Data tab page Table: MAAPV Field: NTGEW Leave all settings as in ABAP Dictionary Characteristics group: T-## ©SAP AG PLM146 6-142 User Menu Classification → Master Data → Classes Change variant class: T_VB1## 300 Characteristics: Add T19_##, T19N_##, and T19B_##. 3-2 Change net weight and gross weight according to the pump type: User Menu → Variant Configuration → Configuration Profile → Change Change configuration profile: for material T-VB1## Pushbutton: Assign object dependencies Create procedure in assignment: 10 T_PROC_T19_## Syntax: $self.T19N_## = mdata $self.T19_## if $self.T02 _## = '01' , $self.T19N_## = mdata $self.T19_## + 3.5 if $self.T02 _## = '02' , $self.T19N_## = mdata $self.T19_## + 2 if $self.T02 _## = '03' , $self.T19N_## = mdata $self.T19_## + 1.5 if $self.T02 _## = '04', $self.T19B_## = $self.T19N_## * 1.1 3-3 Check the result by creating a sales order. Exit the sales order without saving. Favorites → Create Sales Order (VA01) Order type: OR =(Standard order) Sales organization: 1000 Distribution channel: 10 Division: 00 ---------------------------------- Sold-to party: 1000 Ship-to party: 1000 Purchase order number: (Your choice) T-VB1## 1 piece On the value assignment screen: Net weight (according to material master record) =2,500 is displayed Net ©SAP AG PLM146 6-143 weight and gross weight of the item are under Hidden characteristics. A value only appears here if the pump type has an assigned value. Weights also in order overview. Here, the weight is always specified. If no pump type was assigned, the weights are taken directly from the material master record. With a pump type, the values calculated by the procedure are shown. (In the order overview table, scroll right to relevant columns.) ©SAP AG PLM146 6-144 ... More About Object Dependencies Solutions Unit: More About Object Dependencies Topic: Object Dependencies with Structure SCREEN_DEP 4-1 User Menu Classification → Master Data → Characteristics Create numeric characteristic T04_##. Pump capacity in l/h T-## 1 (Released) NUM 6 characters Maybe unit of measure l/h Select Single-value Values: 1000 – 100,000 And assign to class: User Menu Classification → Master Data → Classes Change variant class: T_VB1## 300 Characteristics: Add T04_## 4-2 User Menu → Variant Configuration → Configuration Profile → Change Change configuration profile: for material T-VB1## Pushbutton: Assign object dependencies ©SAP AG PLM146 6-145 Create procedure in assignment: 20 T_PROC_T402_## ©SAP AG PLM146 6-146 Syntax: $self.T04_## = 5000 if $self.T02 _## = '01' , $self.T04_## = 4000 if $self.T02 _## = '04' , $self.T04_## = 8000 if $self.T02 _## = '03' , $self.T04_## = 6000 if $self.T02 _## = '02' Create a second procedure or include its contents in the first procedure. Make sure the sequence is correct! Create procedure in assignment: 30 T_PROC_T0401_## Syntax: $self.T04_## = $self.T04 ## * 2 if $self.T01_## = '03', $self.T04_## = $self.T04 ## * 3 if $self.T01_## = '01', $self.T04_## = $self.T04 ## * 4 if $self.T01_## = '02'. Configuration simulation: T-VB1## 1000 PP01 => Final state (Pump capacity only if pump type is assigned.) 4-3 Create reference characteristic for hiding characteristics. User Menu Classification → Master Data → Characteristics Create characteristic: T10_## Straight to Additional Data tab page Table: SCREEN_DEP Field: INVISIBLE Description: SCREEN_DEP invisible Characteristics group: T-## No Display Rest default User Menu Classification → Master Data → Classes Change variant class: T_VB1## 300 Characteristics: Add T10_##. ©SAP AG PLM146 6-147 Hide using dependencies for characteristic "pump capacity" if this characteristic has no assigned value: User Menu → Variant Configuration → Configuration Profile → Change Change configuration profile: Material T-VB1## Pushbutton: Assign object dependencies Create procedure in assignment: 50 T_PROC_T10_## Syntax: $self.T10_## = 'T04_##' if not $self.T04_## specified (Make sure the sequence is correct! Calculate the pump capacity first, before processing this procedure!) Once the system has calculated the pump capacity (if a value is assigned to the pump-type characteristic), the characteristic for pump capacity is displayed, but the value cannot be changed. Change characteristic: T04_## Additional data: Indicator Not ready for input Check the result in the simulation or in the sales order. (See above for solution.) ©SAP AG PLM146 7-148 © SAP AG 2002 Configuration Scenarios with BOM Explosion Contents: Planned/Production Order Scenario with BOM Explosion Scenario Sales Order ¤ Overview of scenario ¤ Combinations of configuration profiles ¤ Item category determination in SD, transfer of requirements, and variant configuration ¤ Simple SET processing with SET in SET ¤ Multilevel configuration and dependencies for updating configuration ¤ Problems with $ROOT in the sales order scenario ¤ $SUM_PARTS and $COUNT_PARTS ©SAP AG PLM146 7-149 © SAP AG 2002 ¤ Maintain multilevel configuration structures with scenarios with BOM explosion ¤ Maintain dependencies in this environment to: Þ Update the values assigned to individual configuration profiles Þ Explode BOMs ¤ Identify more aspects of modeling and configuration that you can use to improve system performance At the conclusion of this unit, you will be able to: Configuration Scenarios with BOM Explosion: Unit Objectives ©SAP AG PLM146 7-150 © SAP AG 2002 Configuration Scenarios with BOM Explosion: Course Overview Diagram Control Options in the Configuration Profile 3 3 Configuration Scenarios Without BOM Explosion 4 4 Configuration Scenarios with Order BOMs 8 8 2 2 Configuration Scenarios Configuration Scenarios with BOM Explosion with BOM Explosion 7 7 Variant Configuration: Consolidation More About Object Dependencies 6 6 Course Overview 1 1 More About Constraints 5 5 Other Variant Configuration Tools 9 9 Conclusion 10 10 ©SAP AG PLM146 7-151 © SAP AG 2002 Configuration Scenarios with BOM Explosion: Business Scenario ¤ Your multivariant product is a collection of configurable products (assemblies) from the customer's point of view. ¤ For this reason, this is the structure you want to show in sales and distribution: It must be possible to assign values to individual configurable components. ©SAP AG PLM146 7-152 © SAP AG 2002 ¤ Maintain multilevel configuration structures with scenarios with BOM explosion and process planned/production order ¤ Maintain dependencies for this environment ¤ Identify more aspects of modeling and configuration that you can use to improve system performance At the conclusion of this topic, you will be able to: Configuration Scenarios with Process Planned/Production Order: Topic Objectives ©SAP AG PLM146 7-153 © SAP AG 2002 Characteristics: Pump for Mode Pump type ... Characteristics: Pump for Pump type Color Characteristics: W. pressure Range Connection Char.: Packaging IDES Example: Planned/Production Order with BOM Explosion P-502 (Plnd/prod. M-L) Shaft assy (Plnd/prod. M-L) Casing (Plnd/prod. M-L) Packaging (Plnd/prod. M-L) Rtg Rtg Purch. part SD relevant Shaft (No profil e) Rtg ©SAP AG PLM146 7-154 © SAP AG 2002 Sales order 10 P-502 (Pump) 20 (10) Packaging Sales order P-502 (Pump) Casing Packaging Shaft assy Multilevel, interactive configuration Also for items not relevant to sales Values for Pump, Casi ng Shaft, and Packagi ng Values for Pump, Casi ng Shaft, and Packagi ng Pump for P P- -502 (Pump) 502 (Pump) Color Red Packaging Wood Oil Packaging Packaging (SD relevant) (SD relevant) Shaft Shaft assy assy . . . . . . Connection Round 2 Casing Casing Super BOM (Master data BOM) ¤ Master data BOM ¤ Value assignment on all levels Sales Configuration Scenario: Planned/Production Order with BOM Explosion: Overview Þ Multilevel configuration in sales order: º Configuration: - Multilevel, interactive configuration of all configurable items (not only sales-relevant items) in sales order º Characteristic values can be saved for each configurable component. º Pricing for the header material º Sales BOM and production BOM - You can use separate BOMs for sales (5) and production (1). - You can also combine the two, by defining sales-relevant items in a universal BOM (3). ©SAP AG PLM146 7-155 © SAP AG 2002 Configuration Scenario: Planned/Production Order with BOM Explosion: Important Points ¤ In the sales order: - The header object is configured interactivel y - All items (not onl y sales-relevant items) are configured interactivel y - Across: Any number of levels (multilevel BOM explosion) Two levels if present (single-level BOM explosion) ¤ The result is one or more lines in the sales order linked to a main item. However, onl y sales-relevant items appear in the sales order. ¤ The values assigned to all items are saved with reference to the main item. ¤ The main item generates independent requirements. Þ If you want to configure across any number of levels, define all configuration profiles with scenario: Planned/production order with multilevel BOM explosion and from the second level Planned/production order scenarios with single-level or multilevel BOM explosion. Þ If you want to restrict the configuration to two levels, use a configuration profile with scenario: Planned/production order with single-level BOM explosion at header level, and from the second level Planned/production order scenarios with single-level or multilevel BOM explosion. ©SAP AG PLM146 7-156 © SAP AG 2003 Combinations of Configuration Scenarios No profile No BOM explosion Plnd/prod. order Single-level explosion Plnd/prod. order Multilevel explosi on Plnd/prod. order Multilevel explosi on Sales order Single-level explosion Sales order Multilevel explosi on Order BOM Single-level explosion Order BOM Single Single- -level or level or multilevel multilevel BOM BOM explosion explosion Planned Planned/ /production production order order Useful Single-level or multilevel BOMexplosion and configuration across two or more levels *) Same as No profile *) Same as No profile *) Same as No profile *) Same as No profile *) Same as No profile *) =Only the profile for the header material determines whether single-level or multilevel BOMexplosion Single-level or multilevel BOMexplosion and configuration across two or more levels *) Þ When a configuration profile for a material is selected, the system first searches for all active profiles. Then it searches for the $parent material. º If there is no $parent material (in other words, the material is the header), all active profiles are displayed on the profile selection screen. º If a $parent material exists, only the profiles that are allowed in combination with the $parent profile are displayed on the profile selection screen. ©SAP AG PLM146 7-157 © SAP AG 2003 Configuration Scenario: Planned/Production Order with BOM Explosion: Transfer of Requirements Master data Super BOM and Material master MRP: BOM Explosion Production BOMs SD: Sales order Sales BOM Pump (Item cat. grp 0002) Casing (Item cat. grp 0002) Shaft (Item cat. grp 0002) $root $parent $root Pump Shaft Casing BOM explosion for: Pump Values for pump Shaft Values for pump and shaft Casing Values for pump and casing Pump Shaft Casing Þ Item category group 0002 for the header material (in the standard system) ensures that the values assigned to the header material can be referred to as $root in both SD and MRP. Þ The BOM explosion in MRP can use: º The values assigned to the pump to explode the BOM of the pump º The values assigned to the pump and the shaft to explode the BOM of the shaft º The values assigned to the pump and the casing to explode the BOM of the casing Þ The sales relevancy and item category group of the items do not affect this in the standard system. Þ A configurable header material with item category group 0004 cannot be used as a header material in the scenario 'Planned/Production Order With BOM explosion' in the standard system. ©SAP AG PLM146 7-158 © SAP AG 2002 H ead er m aterial H ead er m aterial 0002 TAE NORM TAE 0004 TAE 0002 TAC (Standard Settings) Item category group: generates item category: Item category group: generates item category: 1. 1. 2. 2. as for 2. as for 2. H eader m aterial H eader m aterial 0002 TAC NORM TAN 0004 TAM 0004 TAM Item category group: generates item category: Item category group: generates item category: 3. 3. 4. 4. as for 2. as for 4. Item Category Determination and Variant Configuration Þ See Customizing: Sales Search for Assign item categories º In this environment, the item categories and item category groups are defined. Þ See SAP Library: ->LO ->LO General ->Variant Configuration search for ->Item categories ->Graphic 1 (and following) ©SAP AG PLM146 7-159 © SAP AG 2003 Task: If the color of the casing is BLUE, the packaging must be wood. Configuration Profiles on Several Levels: Value Assignment Characteristics: Pump for Mode Pump type ... Characteristics: Pump for Pump type Color: Blue Chars: W. pressure Range Connection Char.: Packaging: Wood P-502 (multil evel BOM) Shaft assy (multil evel BOM) Casing (multil evel BOM) Packaging (multil evel BOM) Þ Configurable materials in the BOM for pump P-502 (participants can fill out the table): Material type Item cat. group Procurement type Sales-relevance (BOM) Pump P-502 Casing 500-100 Shaft (assy) 502-300 Packaging 500-800 ©SAP AG PLM146 7-160 © SAP AG 2003 General hints for all scenarios: ¤ Configurator ++ On request + On enter - - Permanent View Settings ¤ Pricing (including procedures in group SAP_PRICNG) + On request - Permanent View Settings ¤ Navigation in structure ++ Navigation button not - Configuration structure - Result screen System Performance and Configuration ©SAP AG PLM146 7-161 © SAP AG 2002 BOM Explosion (MRP) in this Environment (1) Characteristics: Pump for Mode Pump type ... Chars: W. pressure Range Connection P-502 (Plnd/prod. M-L) Shaft assy (Plnd/prod. M-L) Shaft (No profil e) $self. $parent $root ? ©SAP AG PLM146 7-162 © SAP AG 2002 BOM Explosion (MRP) in this Environment (2) Characteristics: Pump for Mode Pump type ... P-502 (Plnd/prod. M-L) Shaft (Plnd/prod. M-L) Chars: Connection $self. $root $parent Not possible Values for $root or $parent ? Chars: W. pressure Range ... Shaft assy (Plnd/prod. M-L) ©SAP AG PLM146 7-163 © SAP AG 2002 General hints for all scenarios: ¤ Few configuration levels (also reduces time for user navigation) ¤ Keep configuration model small: Several small models are better than one large model ¤ Separate BOMs for configuration in SD and for MRP and production order (Standard: PP01, SD01) ¤ In task list: alternative sequences instead of several operations with the same selection conditions System Performance and Configuration Structure, BOM, and Task List Þ Few configuration levels º Large structures require more time to explode during the configuration process. It also takes the user more time to navigate around them. Þ Separate BOMs º You can use the BOM application and the selection ID for alternative selection, to control how the BOM is found according to the BOM usage in SD, MRP, and production control. º To improve system performance, you need to consider whether to restrict the number of levels in the BOM explosion in SD. You can do this by changing existing BOM applications or creating new ones. (For example, SD01: Priority 1, BOM usage 3 (universal), no other priorities) Þ Task list º If you have several consecutive operations with the same selection conditions: - You can group them together in an alternative sequence - You assign the selection conditions one, to the entire sequence - You may need to add a dummy operation in the standard sequence ©SAP AG PLM146 7-164 © SAP AG 2002 Configuration Scenarios with Sales Order: Topic Objectives ¤ Maintain multilevel configuration structures with sales order scenarios: Þ Only for header material (SET processing) Þ Possibly for additional assemblies (SET in SET) also ¤ Maintain dependencies in this environment ¤ Use the procedural expressions $SUM_PARTS and $COUNT_PARTS At the conclusion of this topic, you will be able to: ©SAP AG PLM146 7-165 © SAP AG 2002 CD drive 2 PC: T-PC ... Characteristics: Casing type No. of CD drives Software ... Characteristics: Dimensions Number Slots Inserts ... Characteristics: (Sales order) (Sales order) SD SD relevant relevant SD SD relevant relevant Itm cat. grp Itm cat. grp 0004 0004 IDES Example: with Sales Order Process Software 1 Software 2 Software 3 CD drive 1 Rtg Rtg Special casing Minitower casing (No BOM explosion) (No BOM explosion) (Order BOM) (Order BOM) ©SAP AG PLM146 7-166 © SAP AG 2002 Configuration Scenarios with Sales Order: Overview Sales order 10 T-PC.. (PC) 20 (10) Casing 30 (10) CD drive 40 (10) Software 50 (10) Material from class Sales order T-PC... Casing CD drive Multi-level, interactive configuration in sales order Only sales- relevant BOM items Manual changes allowed Values for PC, Casing, CD dri ve, … Values for PC, Casing, CD dri ve, … Casing type Height 50 cm MT Property Value1 ¤ Several sales order items ¤ Char. value assgmt ¤ Manual changes Sales Super BOM (Master data BOM) Hard disk 10 GB T T- -PC... PC... (PC) (PC) Software Software SD relevant SD relevant CD drive CD drive SD relevant SD relevant Casing Casing SD relevant SD relevant Color Color SD relevant SD relevant Sales order process ="SET" processing Þ Manual changes to items are saved in the sales order. Changes to master data do not affect order-specific item changes. Þ Pricing and requirements transfer º Item category group 0004 (in the standard system) means that pricing is calculated and requirements are transferred for the individual components of the set (not on the top level). º Material requirements are only transferred to PP if the configuration is consistent and complete. º Requirements are only transferred for the subordinate items that are relevant to sales. (These are also the items that appear in the sales order.) ©SAP AG PLM146 7-167 © SAP AG 2002 Sales Order Process: Change of $root Object Master data Super BOM and Material master MRP: BOM Explosion Production BOMs SD: Sales order Sales BOM $root $root PC Dri ve Casing Dri ve Casing $root $ROOT in MRP $ROOT in MRP generates requirements generates requirements PC (Item cat. grp 0004) Dri ve (Item cat. grp 0002) Casing (Item cat. grp 0002) Sales order process ="SET" processing Þ Transfer of requirements - $root º Item category group 0004 (in the standard system) means that requirements are transferred for the individual components of the set. º The MRP run interprets the materials for which planned independent requirements are transferred as $root. º Selection conditions for BOM items of these assemblies and subordinate assemblies (Drive and Casing in the example) can use $root to refer to characteristics of the material of the assembly that generates planned independent requirements. The values assigned to the PC are not available in MRP. Þ In the sales order, however, $root is always the header material - the material for which you created the sales order. ©SAP AG PLM146 7-168 © SAP AG 2006 Configuration Scenario Sales Order: Important Points ¤ In the sales order, you configure the following interactivel y: Þ Header object Þ All sales-relevant items, across: 4 Two levels 4 Any number of levels ¤ The result is several lines in the sales order, linked to the main item ¤ Pricing can be set at main item level or at subitem level Transfer of requirements can onl y take place at subitem level. Þ If you want to configure across any number of levels, use a configuration profile with scenario: multilevel BOM explosion at header level. Þ If you want to restrict configuration to only two levels, use a configuration profile with scenario: single-level BOM explosion at header level. ©SAP AG PLM146 7-169 © SAP AG 2006 Combinations of Configuration Scenarios No profile No BOM explosion Plnd/prod. order Single-level explosion Plnd/prod. order Multilevel explosi on Plnd/prod. order Multilevel explosi on Sales order Single-level explosion Sales order Multilevel explosi on Order BOM Single-level explosion Order BOM Single Single- -level or level or multilevel BOM multilevel BOM explosion explosion s sales order ales order Cannot be used, since value assignment using header material does not exist in MRP Same as no profile, cannot be used (see above) Can be used: see relevant unit Single-level or multilevel BOM explosion and configuration across two or more levels *) Can be used: see relevant unit Single-level or multilevel BOM explosion and configuration across two or more levels *) Can be used: see relevant unit *) =Only the profile for the header material determines whether single-level or multilevel BOM explosion takes place Same as no profile, cannot be used (see above) Þ When a configuration profile for a material is selected, the system first searches for all active profiles. Then it searches for the $parent material. º If there is no $parent material (in other words, the material is the header), all active profiles are displayed on the profile selection screen. º If a $parent material exists, only the profiles that are allowed in combination with the $parent profile are displayed on the profile selection screen. ©SAP AG PLM146 7-170 © SAP AG 2003 IDES Example: " SET in SET" CD drive 2 Characteristics: Casing type ... Special casing Chars: ... (No BOM explosion) (No BOM explosion) (Order BOM) (Order BOM) Itm cat. grp Itm cat. grp 0004 0004 Casing Minitower Software 1 Software 2 Software 3 CD drive 1 Chars: ... All All SD SD relevant relevant Handbook 1 Packaging Class Printer Class Monitor Handbook 2 Handbook 3 Handbook ... Chars : ... (...) (...) PC: T-PC ... (Sales order) (Sales order) PC package (Sales order) (Sales order) Characteristics: With printer? With monitor? ... Itm cat. grp Itm cat. grp 0004 0004 ©SAP AG PLM146 7-171 © SAP AG 2002 Sales order: Sales order: 10 PC package TAM 20 (10) Monitor TAN 30 (10) PC TAM 40 (30) Casing TAC 50 (30) CD drive TAC 60 (30) Software TAN 80 (30) CPU TAN 40 (10) Printer TAC Item Categories for Scenarios with Sales Order H ead er m aterial H ead er m aterial 0002 TAE NORM TAE 0004 TAE 0002 TAC H eader m aterial H eader m aterial 0002 TAC NORM TAN 0004 TAM 0004 TAM Þ See Customizing: Sales Search for Assign item categories º In this environment, the item categories and item category groups are defined. Þ See SAP Library: ->Logistics ->LO Logistics General ->Variant Configuration ->Configurable Materials in Sales Documents ->Item Categories for Configurable Materials ->Graphic 1 (and following) ©SAP AG PLM146 7-172 © SAP AG 2003 BOM Explosion (MRP) in this Environment CD drive 2 Characteristics: Casing type ... Special casing (No BOM explosion) (No BOM explosion) (Order BOM) (Order BOM) Itm cat. grp Itm cat. grp 0004 0004 Casing Minitower Software 1 Software 2 Software 3 CD drive 1 Handbook 1 Packaging Class Monitor Handbook 2 Handbook 3 Handbook ... ... (...) (...) PC: T-PC ... (Sales order) (Sales order) PC package (Sales order) (Sales order) Characteristics: With printer? With monitor? ... Itm cat. grp Itm cat. grp 0004 0004 $root $self ? Not possible Not possible Class Printer Þ In this example, item category group 0004 for materials PC package and PC generate item category TAM in the sales order. Þ According to the standard settings in Customizing for Sales and Distribution, no requirements are transferred for these "SET materials". Þ In this example, planned independent requirements are transferred for the top level (possibly configurable) components outside the gray (online the red) area. These materials are the $root materials in MRP. ©SAP AG PLM146 7-173 © SAP AG 2006 Solution: Procedure with $sum_parts Example.: $self.TOTAL_WEIGHT = $sum_parts ($self, PART_WEIGHT) See See SAP Library SAP Library Prerequisite: - Multi-level configuration - After BOM is exploded The Function: $sum_parts Concept: A numeric characteristic is to be summed across several configurable materials in a configuration structure. Example: Total weight Total dimensions PC: Number of slots and inserts ©SAP AG PLM146 7-174 © SAP AG 2006 Solution: Procedure with $count_parts Example: $self.NUMBER_PARTS = $count_parts($self Prerequisites: - Multilevel configuration - Same unit for all components - After BOM is exploded - You need the sum of all components - You need the sum on the first level The Function: $count_parts See See SAP Library SAP Library Concept: You want to sum the total number of components in a configuration structure to process this result further. ©SAP AG PLM146 7-175 © SAP AG 2002 ¤ Maintain multilevel configuration structures with scenarios with BOM explosion ¤ Maintain dependencies for this environment to: · Update the values assigned to individual configuration profiles · Explode BOMs ¤ Identify more aspects of modeling and configuration that you can use to improve system performance You are now able to: Configuration Scenarios with BOM Explosion: Unit Summary (1) ©SAP AG PLM146 7-176 © SAP AG 2003 ¤ Model multilevel configuration structures with scenarios that have BOM explosion and either process planned/production order or process sales order (including " SET in SET" ) ¤ Explain and set up item category determination and item category groups ¤ Explain special features for scenario process sales order ¤ Optimize system performance regarding: · Configuration · Configuration structure · BOM · Routing ¤ Use $part_of, $subpart_of, $sum_parts, and $count_parts You are now able to: Configuration Scenarios with BOM Explosion: Unit Summary (2) ©SAP AG PLM146 7-177 Configuration Scenarios with– Exercises Unit: Configuration Scenarios with BOM Explosion Topic: Planned/Production Order Scenario with Multilevel BOM Explosion At the conclusion of these exercises, you will be able to: • Create sales orders for configurable materials in this scenario, and execute processing in MRP and so on The exercise also covers: • Checking the master data required • Creating the characteristics, variant class, and configuration profiles • Creating constraints and other object dependencies The configurable material "casing" is now an assembly in a configurable pump. In sales and distribution, you want to be able to assign values to the assembly. You need to create dependencies to model multilevel configuration. 1-1 Check the master data that already exists for modeling the configurable pump T-VPU##. 1-1-1 Display material master record T-VPU## with the basic data, sales, and MRP views. Use the following organizational levels: Plant: 1000 Sales organization: 1000 Distribution channel: 10 1-1-2 In change mode, display the BOM for your pump with usage 3 in plant 1000. Compare it with the slide "2. Customer Example Part Structure (Pump Without Casing)" in the appendix. Add the configurable assembly (T-VB1##) to the BOM, if it is not already there. ©SAP AG PLM146 7-178 1-2 Create a configuration profile with a variant class for the configurable pump. 1-2-1 Create the characteristics required (copy from group 00): Length of metal sheet (cm) T13_## Values: 10 – 100 Width of metal sheet (cm) T14_## Values: 10 – 100 Area of metal sheet (m 2 ) T15_## Values: 0.01 - 1 1-2-2 Create variant class T_VPU## for your configurable pump and assign the characteristics you just created to this class. 1-2-3 Create a configuration profile for your configurable pump T-VPU##. Use the name N-BOM for your profile. Assign your configurable pump to variant class T_VPU##. Set the following parameters: – Multilevel BOM explosion – PP01 (BOM application) – No availability check – No restrictions for BOM explosion – All screens, including configuration browser – (Rest: default) 1-2 -4 Check the configuration profile in the simulation. Can you assign values to your casing when configuring the pump? __________________________ Why? __________________________ 1-2-5 Create another configuration profile for your configurable casing T- VB1##. (Do not change the existing profile, because it will be needed again.) Use the name 1-BOM for your profile. Do you need to reassign variant class T_VB1##? Set the following parameters: – Single-level BOM explosion – All object dependencies of the first profile – Rest as in 1-2-3 ©SAP AG PLM146 7-179 Use the copy function for assigning object dependencies: Ctrl Y + Ctrl C + Ctrl V ©SAP AG PLM146 7-180 1-3 Optional The BOM of the pump contains a variable-size item for sheet metal ST37 (100-700). 1-3-1 Create and assign dependencies to ensure that the following formula is used to calculate the area (Size 3) from the other 2 sizes – length and width: Area =Length x Width / 10,000 (Division by 10,000 is necessary to convert the length and width in cm to the area in m 2 .) 1-3-2 Assign dependencies to the BOM so that variable-size item data is overwritten according to the values assigned. 1-3-3 Check the result in the simulation. 1-4 Create and save a sales order with the following data: Order (OR) 1000 10 00 Sold-to party: =Ship-to party: 1000 Purchase order no.: Your choice Material No./Qty. T-VPU## 1 piece Assign values to the header material and the configurable assembly. Can you assign values to the assembly? Must this assembly appear as an item in the sales order? Save your sales order and make a note of the number. Do an MRP run for configurable pump T-VPU##. To do this, use single-item planning for sales order with the number of your sales order. Display the stock/requirements list for the following materials: T-VPU## T-VB1## Single-item planning: Transaction MD50 – add this to your favorites. Stock/requirements list: Transaction MD04 – add this to your favorites. ©SAP AG PLM146 7-181 Display the relevant planned orders with their values and account assignment. ©SAP AG PLM146 7-182 Configuration Scenarios with BOM Exercises Unit: Configuration Scenarios with BOM Explosion Topic: Process Sales Order with Multilevel BOM Explosion At the conclusion of these exercises, you will be able to: • Set up and execute SET processing ("sales order" processes) The exercise also covers: • Changing a material master and BOM for SET processing and creating configuration profiles • Creating constraints • Creating sales orders You now want to supply the pump as a set or package. To do this, you change the existing structure. You need to decide which dependencies from the configuration profile – for the Planned/production order scenario with multilevel BOM explosion – you need to re-use. The task also gives you the option of creating further constraints (optional). 2-1 Using the structure from the previous unit, you want to model SET processing. 2-1-1 Change material master record T-VPU## to stop the header material from generating planned independent requirements. Use the following organizational levels: Plant: 1000 Sales organization: 1000 Distribution Channel: 10 2-1-2 Change the BOM for your pump with usage 3 in plant 1000, so that all of its components are relevant to sales. 2-1-3 Create a configuration profile for your configurable pump T-VPU##, using the scenario "sales order with multi-level BOM explosion". Give the profile a higher priority than the profile you created in the previous unit. ©SAP AG PLM146 7-183 Use the name N-SET for your profile. ©SAP AG PLM146 7-184 Set the following parameters: – Sales Order (SET) – Multilevel BOM explosion – PP01 (BOM application) – No availability check – No restrictions for BOM explosion UserInterf – All screens, including configuration browser Sales order – No manual changes allowed – (Rest: default) Do you need to assign a class again? Why? 2-2 Optional Create dependencies that map the following interdependencies in multilevel value assignment: Assign all the characteristics you create here to the variant class for the pump. Some of these characteristics will be used in subsequent exercises, but you can create them later instead. 2-2-1 Create a characteristic for the "range". T18_## Values: 01 Open 02 Closed The range must be closed if the pump is for oil. Which types of dependency can you use to do this? Check the result in the simulation. 2-2-2 Create characteristics for the "maximum working pressure (bars)": T17_## Values: 2 – 10 and the "connection": T11_## Values: 01 Right- angled flange 02 Round flange (2-hole) 04 Round flange (4-hole) XX Other ©SAP AG PLM146 7-185 If the maximum working pressure is over 8 bars, the pump must be a plunger pump with a 4-hole round flange as the connection. Which types of dependency can you use to do this? Check the result in the simulation. ©SAP AG PLM146 7-186 2-2-3 Create a characteristic for the "rotation direction": T16_## Values: 01 Clockwise 02 Counter-clockwise 03 Both If the pressure cover in the BOM for the pump is item ‘0055’, the rotation direction must be "Both". Which types of dependency can you use to do this? Check the result in the simulation. 2-3 Create and save a sales order with the following data: OR 1000 10 00 Sold-to party: =Ship-to party: 1000 Purchase order no.: Your choice Material No. / Qty T-VPU## 1 piece Select the configuration profile for SET processing. In which order are the profiles shown? Why? Assign values to the header material and the configurable assembly. Can you assign values to the assembly? ____ Must this assembly appear as an item in the sales order? ____ Which configuration profile lets you assign values to the assembly? _______ Why this profile and not the others? __________ Which items appear in the sales order? __________ What is the default item category for the individual items? ___________ Why are there problems with components? __________ ©SAP AG PLM146 7-187 In the sales order, check the weights of: The casing (T-VB1##) The bearing case (100-500) Where does this data come from? Save your sales order and make a note of the number. Which configurable materials transfer independent requirements as a result of this sales order? ____________ ©SAP AG PLM146 7-188 Configuration Scenarios with BOM E ©SAP AG PLM146 7-189 xpl Solutions Unit: Configuration Scenarios with BOM Explosion Topic: Planned/Production Order Scenario with Multilevel BOM Explosion 1-1 Check the modeling of the configurable pump T-VPU##: 1-1-1 User menu Material → Display → Display Current Material T-VPU##: Views: Basic data 1 +2 Sales: Sales Org. Data 1 +2 Sales: General / Plant Data MRP 1 -4 Organizational levels: Plant: 1000 Sales organization: 1000 Distribution channel: 10 1-1-2 User menu Bill of Material → Material BOM → Display Change BOM with usage 3 plant 1000. Compare with graphic (see appendix). ¬ Add new material item: L T-VB1## 1 piece ©SAP AG PLM146 7-190 1-2 1-2-1 User menu → Classification → Master Data → Characteristics Create single-value characteristics (copy from group 00 as much as possible): T13_## Description: Length of metal sheet (cm) Numeric Characteristics group: T-## Unit of measure: cm Values: 10 – 100 T14_## Description: Width of metal sheet (cm) Numeric Characteristics group: T-## Unit of measure: cm Values: 10 – 100 T15_## Description: Area of metal sheet (m 2 ) Numeric Characteristics group: T-## Unit of measure: m2 Values: 0.01 – 1 1-2-2 User menu → Classification → Master Data → Classes Create a variant class: T_VPU## 300 Variant class for pump assembly 1 (Released) T-## Characteristics: T13_## T14_## T15_## ©SAP AG PLM146 7-191 1-2-3 User menu → Variant Configuration → Configuration Profile → Create Create a configuration profile for the pump T-VPU##. Prof. Name: N-BOM 300 Class assignment T_VPU## Configuration initial screen: Configuration parameters – Process: Planned/prod. order – Multilevel BOM explosion – PP01 (BOM application) – No availability check – No restrictions for BOM explosion User interface – All screens, including configuration browser In other words, without configuration structure – (Rest: default) 1-2-4 Configuration simulation (see previous exercises) You cannot assign values to the casing, because configuration scenarios planned/production order without BOM explosion are inactive under configuration scenarios planned/production order with BOM explosion. 1-2-5 User menu → Variant Configuration → Configuration Profile → Change Create another configuration profile for casing T-VB1##. (Do not change the existing profile.) ¬ New entries Profile name: 1-BOM 300 Class assignment already exists Copy object dependencies from the first profile for the casing. Session 2: Display configuration profile 0-BOM for your material T- VB1##. Here, select the list of dependencies with Ctrl +Y then ©SAP AG PLM146 7-192 copy with Ctrl +C. Session 1: → Assign dependencies (= Ctrl + F9 ¬ Here: Insert dependencies using Ctrl +V ¬ Resort (Sort sequence from profile 0-BOM) ©SAP AG PLM146 7-193 Configuration initial screen: Configuration parameters – Process: Planned/prod. order – BOM explosion: single level – PP01 (BOM application) – No availability check UserInterf – All views, including configuration browser – (Rest: default) ©SAP AG PLM146 7-194 1-3 Optional 1-3-1 Create a constraint that uses the following formula to calculate the area (Size 3) from the other 2 sizes – length and width: Area =Length x Width / 10,000 Create constraint net T_CN1_VPU## with constraint T_CS1_VPU##: User menu Variant Configuration → Dependency → Dependency Net → Create Create constraint net: T_CN1_VPU## Description is your choice 1 (Released) T-## (group) Assign and create constraint at the same time: T_CS1_VPU## Description: Size calculation T-## (group) objects: (300)T_VPU## where L = T13_##; W = T14_##; A = T15_##. restriction: A = L * W / 10000. inferences: A, L, W Save all and release Assign constraint net to the configuration profile of the pump: User Menu → Variant Configuration → Configuration Profile → Change Change configuration profile: for material T-VPU## Pushbutton: Assign dependencies =Ctrl +F9 Assign constraint net T_CN1_VPU## ©SAP AG PLM146 7-195 1-3-2 Assign dependencies to the BOM so that variable-size item data is overwritten according to the values assigned. Create reference characteristics with reference to fields ROMS1, ROMS2, and ROMEN in table STPO. (Not necessary if dependencies work with reference characteristics of group 00: TROMS1_00, TROMS2_00, and TROMEN_00.) User Menu → Classification → Master Data → Characteristics Create reference characteristic: TROMS1_## Additional data: STPO – ROMS1 Characteristics group: T-## TROMS2_## Additional data: STPO – ROMS2 Characteristics group: T-## TROMEN_## Additional data: STPO – ROMEN Characteristics group: T-## User Menu Bill of Material → Material BOM → Change T-VPU## Plant: 1000 Usage: 3 Item 30 (100-700 =metal sheet ST37 as variable-size item) ...(Item Overview) → Pushbutton or Extras → Object dependencies → Assign Assign and create procedure at the same time 10 T_PROC_ROMS_## $self.TROMS1_## = T13_## , $self.TROMS2_## = T14_## , $self.TROMEN_## = T15_## . (Alternatively you can work with the reference characteristics for group 00.) 1-3-3 Configuration simulation (see previous exercises) ©SAP AG PLM146 7-196 1-4 Create and save sales order SAP Menu → Logistics → Sales and Distribution → Sales → Order → Create = VA01 or Favorites → Create Sales Order = VA01 Order type: OR =(Standard order) Sales organization: 1000 Distribution channel: 10 Division: 00 ---------------------------------- Sold-to party: 1000 Ship-to party: 1000 Purchase order number: (Your choice) T-VPU## 1 piece Assign values to the header material and the configurable assembly. Values are assigned to assembly T-VB1##via configuration profile 1-BOM. (On value assignment screen, see Environment → Configuration Profile.) The assembly need not appear as an item in the sales order. Save your sales order and make a note of the number. (Ignore the pricing error and any other incompleteness messages.) Execute single-item planning for sales order with the number of your sales order. Transaction MD50 (Planning for sales order) and Transaction MD04 (Display stock/requirements list) Add both transactions to your favorites: Favorites → Insert transaction (= Ctrl + Shift + F4) Planning for sales order: Sales order number Item 10 Keep defaults +confirm Stock/requirements lists for materials: T-VPU## T-VB1##(both in plant 1000) (Start with one) ¬ Overview Double-click on planned order ¬ Details of MRP element Pushbutton: Display element ¬ Display planned order (header) Values ©SAP AG PLM146 7-197 Pushbutton: Configuration Account assignment Tab: Assignment ©SAP AG PLM146 7-198 Configuration Scenarios with BOM Explosion Solutions Unit: Configuration Scenarios with BOM Explosion Topic: Process Sales Order with Multilevel BOM Explosion 2-1 Model SET processing: 2-1-1 Change material master record T-VPU## to stop the header material from generating independent requirements. User menu Material → Change → Immediately Use the following organizational levels: Plant: 1000 Sales organization: 1000 Distribution channel: 10 Screen: Sales: Sales Org. Data 2 Item Category Group: 0004 2-1-2 Change BOM for pump to make all components sales relevant. User Menu Bill of Material → Material BOM → Change BOM Material: T-VPU## Usage 3 Plant 1000 Pushbutton: Select all (= Ctrl + F3) Pushbutton: Item (= F7) Tab: Status/long text Set sales-relevant indicator (Continue with Next Item = Shift + F6) 2-1-3 User Menu → Variant Configuration → Configuration Profile → Change Material T-VPU## ¬ New Entries 02 N-BOM 300 (Released) 01 N-SET 300 (Released) ©SAP AG PLM146 7-199 Parameters of profile in detail: – Sales order process – Multilevel BOM explosion – PP01 (BOM application) – No availability check – No restrictions BOM explosion UserInterf – All screens, including configuration browser In other words, without configuration structure Sales order – No manual changes allowed – (Rest: default) Do you need to assign a class again? No Why? The link is at material level, not at profile level 2-2 Optional General: User menu Variant Configuration → Dependency → Dependency Net → Create Create constraint net T_CN2_VPU## 1 (Released) T-## (group) User Menu → Variant Configuration → Configuration Profile → Change Change configuration profile N-SET for material T-VPU## Pushbutton: Assign object dependencies Assign constraint net T_CN2_VPU## ©SAP AG PLM146 7-200 2-2-1 The range must be closed if the pump is for oil. User Menu → Classification → Master Data → Characteristics Create characteristic "Range": T18_## T-##(group) 1 Released Character format (CHAR) 2 characters single value Values: 01 Open 02 Closed User Menu → Classification → Master Data → Classes Change variant class: T_VPU## 300 Char: Add T18_##. User menu Variant Configuration → Dependency → Dependency Net → Change Change constraint net T_CN2_VPU## Assign and create constraint at the same time: T_CS_VPU##_221 T-## objects: (300)T_VPU##, (300)T_VB1## restriction: (300)T_VPU##.T18_## = '02' if (300)T_VB1##.T01_## = '01'. Which types of dependency can you use to do this? Only constraints Check the result in the simulation. (See above for solutions) ©SAP AG PLM146 7-201 2-2-2 If the maximum working pressure is over 8 bars, the pump must be a plunger pump with a 4-hole round flange as the connection. User Menu → Classification → Master Data → Characteristics Create characteristic “Maximum working pressure (bar)”: T17_## T-##(group) 1 Released Numeric (NUM) 2 characters Single-value Values: 2 - 10 Create characteristic "Connection": T11_## T-##(group) 1 Released Character format (CHAR) 2 characters single value Values: 01 Right-angled flange 02 Round flange (2-hole) 04 Round flange (4-hole) XX Other User Menu → Classification → Master Data → Classes Change variant class: T_VPU## 300 Characteristics: Add T17_##and T11_##. User menu Variant Configuration → Dependency → Dependency Net → Change Change constraint net T_CN2_VPU## Assign and create constraint at the same time: T_CS_VPU##_222 T-## objects: (300)T_VPU##, (300)T_VB1## condition: (300)T_VPU##.T17_## > 8 ©SAP AG PLM146 7-202 restriction: (300)T_VPU##.T11_## = 'o4', (300)T_VB1##.T02_## = '01' Which types of dependency can you use to do this? Constraints or procedures (or actions) Check the result in the simulation. (See above for solutions) 2-2-3 If the pressure cover in the BOM for the pump is item ‘0055’, the rotation direction must be "Both". User Menu → Classification → Master Data → Characteristics Create characteristic "Rotation direction": T16_## T-##(group) 1 Released Character format (CHAR) 2 characters single value Values: 01 Clockwise 02 Counter-clockwise 03 Both User Menu → Classification → Master Data → Classes Change variant class: T_VPU## 300 Char: Add T16_##. User menu Variant Configuration → Dependency → Dependency Net → Change Change constraint net T_CN2_VPU## Assign and create constraint at the same time: T_CS_VPU##_223 T-## (group) objects: PU is_a (300)T_VPU## , XX is_object (Material)()(Nr = '100-400') condition: part_of(XX, PU, '0055') ©SAP AG PLM146 7-203 restriction: PU.T16_## = '03' Which types of dependency can you use to do this? Only constraints Check in the simulation before and after changing the BOM (with item number 55 and with another item number). ©SAP AG PLM146 7-204 2-2 Create and save sales order: Favorites → Create Conditions (VA01) Order (OR) 1000 10 00 Sold-to party: 1000 Ship-to party: 1000 Purchase order no.: Your choice T-VPU## 1 piece – Two profiles in quotation for header material – "N-SET" first, because the priority is higher – Values assigned to header material with profile "N-SET" – Values can be assigned to casing, but only with profile "0-BOM" because this profile is allowed below scenario sales order and profile 1-BOM is not allowed here. Must this assembly appear as an item in the sales order? Yes (sales-relevant) Which items appear in the sales order? All BOM items, because they are sales relevant (except materials whose sales views are not maintained – this is a modeling problem) What is the default itemcategory for the individual items? Pump TAM (assembly item) Casing TAC (variant configuration) Others TAN (standard item) Weights in item overview: T-VB1## According to object dependencies 100-500 According to material master Save your sales order and make a note of the number. Favorites → Display stock/requirements list MD04 Stock/requirements lists for materials: T-VPU## T-VB1## (Start with one) ¬ Overview ©SAP AG PLM146 7-205 Sales order exists for configurable casing (not for the pump). ©SAP AG PLM146 8-206 © SAP AG 2002 Contents: Configuration Scenarios with Order BOMs ¤ Overview of scenario ¤ Settings in the configuration profile ¤ Combinations of configuration profiles ¤ Knowledge-based order BOM ¤ Result-oriented order BOM ¤ Class nodes, system performance, and classificati on ¤ Single-level order BOM ¤ Multilevel order BOM (including type matching for assemblies) ¤ Problems with $parent and $root ©SAP AG PLM146 8-207 © SAP AG 2002 ¤ Maintain single-level and multilevel order BOM structures ¤ Create sales orders for the order BOM scenario and make technical changes to the BOM ¤ Create and change both knowledge-based and result-oriented order BOMs in technical postprocessing ¤ Use class nodes in this scenario ¤ Control the BOM explosion At the conclusion of this unit, you will be able to: Configuration Scenarios with Order BOMs: Unit Objectives ©SAP AG PLM146 8-208 © SAP AG 2002 Configuration Scenarios with Order BOMs: Course Overview Diagram Control Options in the Configuration Profile 3 3 Configuration Scenarios Without BOM Explosion 4 4 Configuration Scenarios Configuration Scenarios with Order BOMs wi th Order BOMs 8 8 2 2 Configuration Scenarios with BOM Explosion 7 7 Variant Configuration: Consolidation More About Object Dependencies 6 6 Course Overview 1 1 More About Constraints 5 5 Other Variant Configuration Tools 9 9 Conclusion 10 10 ©SAP AG PLM146 8-209 © SAP AG 2002 ¤ You want to model your configurable product so that it is possible to make manual, order-specific modifications at any time. ¤ The configuration scenario with the order BOM process gives you the option of creating order BOMs and (if required) order-specific routings in technical postprocessing. Configuration Scenarios with Order BOMs: Business Scenario ©SAP AG PLM146 8-210 © SAP AG 2002 IDES Example with BOM Explosion and Order BOM Process Shaft assy (Order BOM) Rtg Characteristics: Pump for: Oil, Water, Waste w. Mode Pump type: Plunger, Rotary ... P-501 (Pump) (Order BOM) Rtg Shaft (No profil e) Rtg Slug Linch pin Casing G Casing A Casing C Support Bearing A Bearing B Bearing C Characteristics: Pump for Pump type Material Diameter Suction chnl (Order BOM) Purch. part ©SAP AG PLM146 8-211 © SAP AG 2002 Two steps Technical order processing Configuration Scenarios with Order BOMs: Overview Sales order 10 P-501 (Pump) Sales Super BOM (Master data BOM) P-501 (Pump) Shaft Shaft assy Single-level (standard), interactive configuration Single-level (standard), interactive configuration 2. 2. 1. 1. BOM maintenance Sales order item 10 P-501 (Pump) Multilevel, interactive configuration Manual changes Type matching on request Multilevel, interactive configuration Manual changes Type matching on request Configuration Scenario with Order BOM: Þ Two-step process: º In Sales and Distribution (SD), configuration is on the top level only as standard. You can use the configuration profile to define that multilevel configuration is possible in the sales order (Indicator "Maintenance allowed in order"). º In BOM maintenance, configuration can be interactive and on multiple levels, and manual changes can be made. - All BOM items can be processed, unless filters restrict processing. - As of R/3 4.0A, type matching is possible for assemblies. ©SAP AG PLM146 8-212 © SAP AG 2002 Order BOM Step 1 Sales order 10 P-501 (Pump) Assigned char. values Pump Sales order 10 P-501 (Pump) As standard, single-level, interactive value assignment As standard, single-level, interactive value assignment Sales Super BOM (Master data BOM) P-501 (Pump) Shaft Shaft assy Pump for Mode Pump type Oil Manual Plunger . . . . . . 1. 1. Values for Pump ... Values for Pump ... Configuration Scenario with Order BOM: in Sales and Distribution Þ Configuration º In Sales and Distribution (SD), configuration is on the top level only as standard. º You can use the configuration profile to define that multilevel configuration is possible in the sales order. º (Indicator "Maintenance allowed in order") Þ BOM explosion º None Þ Material requirements: º Transferred from sales order for header material. Þ Type matching º Only possible for header material in sales. ©SAP AG PLM146 8-213 © SAP AG 2002 Order BOM Step 2 Values for Pump, Shaft assembl y, shaft Values for Pump, Shaft assembl y, shaft Super BOM (Master data BOM) P-501 (Pump) Shaft Shaft assy Technical order processi ng 2. 2. BOM maintenance Sales order item P-501 10 Pump for Oil Multi-level, interactive configuration Manual changes Type matching on request Multi-level, interactive configuration Manual changes Type matching on request Shaft assy Connection ... ... RAngle, Round 2, Round 4 Shaft ... ... Order BOM P-501 (Pump) 10 Fl ywheel 20 Shaft assy 30 ... ¤ Value assignment across number of levels specified in profile ¤ Order-specific BOMs where needed or wanted Configuration Scenario with Order BOM: in technical order processing Þ Multilevel, interactive configuration, number of levels can be defined in configuration profiles. º Assigned values are saved for all configurable items. Þ Manual changes can always be made to components of a configurable material with an active profile. If you are using a result-oriented BOM without restricting the level of detail, you can also maintain other order-specific BOMs. A changed assembly is saved as an order BOM for the sales order. º If no changes are made to a changeable assembly, an order-specific BOM is still saved if the Automatic fix indicator is set (see next slide). As of R/3 4.5, manual fixing is also possible. Þ Requirements º Material requirements for a sales order item are transferred from the sales order. º Order-specific changes to the BOM are read in material requirements planning (MRP), whether the changes are made manually or as a result of the configuration process. ©SAP AG PLM146 8-214 © SAP AG 2002 Automatic Fixing Indicator ¤ VA01 only -> No order BOM ¤ VA01 and CU51 without manual changes Automatic -> No fixing order BOM Automatic -> Order BOM fixing ¤ VA01 + CU51 and -> Order BOM manual changes Þ The Automatic fixing indicator lets you automatically create order BOMs for assemblies in technical order processing, even if no manual changes are made. An order BOM is then created the first time you call technical processing for the sales order. Þ 1. Sales order created in SD, no technical order processing ==> No order BOM created Þ 2. Sales order created in SD, technical postprocessing, but without manual changes, Automatic fix indicator not set ==>No order BOM created Þ 3. Sales order created in SD, technical postprocessing, but without manual changes, Automatic fix indicator set ==>Order BOM created (if it does not already exist) Þ 4. Sales order created in SD, technical order processing, with manual changes ==>Order BOM created ©SAP AG PLM146 8-215 © SAP AG 2002 Configuration Scenarios with Order BOMs: Important Points ¤ Two-step process: 1. Sales 2. Technical order processing ¤ In the sales order, onl y the header material is configured interactivel y as standard. ¤ The configurable components can be interactivel y configured subsequentl y in a separate environment (CU51). ¤ In the order BOM, any components can be changed, deleted, copied, or added. ¤ The result is a line in the sales order and one or more new BOMs with reference to the sales order item. ¤ Changes are relevant to material requirements planning (onl y if indicator KASTL is set to plant-specific in table T399D) ©SAP AG PLM146 8-216 © SAP AG 2003 Combinations of Configuration Scenarios No profile No BOM explosion Plnd/prod. order Single-level explosion Plnd/prod. order Multilevel explosi on Plnd/prod. order Multilevel explosi on Sales order Single-level explosion Sales order Multilevel explosi on Order BOM Single-level explosion Order BOM Single Single- -level or level or multilevel BOM multilevel BOM explosion explosion Order BOM Order BOM Useful Same as No profile Single-level or multilevel BOM explosion and configuration across two or more levels *)**) Same as No profile *) Single-level or multilevel BOM explosion and configuration across two or more levels *)**) Same as No profile *) Same as No profile *) =Only the profile for the header material determines whether single-level or multilevel BOM explosion **) =If header and assembly material are not saved in the same way, same as No profile Same as No profile Þ When a configuration profile for a material is selected, the system first searches for all active profiles. Then it searches for the $parent material. º If there is no $parent material (in other words, the material is the header), all active profiles are displayed on the profile selection screen. º If a $parent material exists, only the profiles that are allowed in combination with the $parent profile are displayed on the profile selection screen. Þ If you create a sales order for a configurable material that has the order BOM scenario, you can only assign values to the header material in sales (in the standard system). Only the dependencies for the configuration profile of the header material are active. º In technical postprocessing, you can assign values to configurable assemblies that have the order BOM scenario. Dependencies for the configuration profiles of configurable assemblies to which you can assign values are active here. You can maintain order BOMs. Þ For more information, see note 148778. ©SAP AG PLM146 8-217 © SAP AG 2003 " Single-Level Order BOM" (1) Shaft assy (No acti ve profile) Characteristics: Pump for: Oil, Water, Waste w. Connection: RAngle, Rd2, Rd4 Extras: With support, ... ... P-501 (Order BOM) Support base Selection condition: $root.EXTRAS eq 'With ... or $parent.EXTRAS eq 'With ... not $self.EXTRAS eq 'With ... Procedure (or action): $self.QUANT eq 4 if ... not $parent.QUANT eq 4 not $root.QUANT eq 4 ... Selection condition: $root.CONNECTION eq 'Rd2' or $parent.CONNECTION eq 'Rd2' not $self.CONNECTION eq 'Rd2' $root = header $parent = next instance Bearing A Bearing B Bearing C Þ The above model has an active profile at header material level only. All configurable components either have no configuration profile or their configuration profiles are not released. Þ Each configuration has only one instance in the above model. This instance can be queried by all items of the multilevel BOM structure with $parent or $root. ©SAP AG PLM146 8-218 © SAP AG 2003 Class Nodes for Order BOMs Class: Class: Color Color Characteristics: Color: Red, Blue, Green Gloss: yes/no Characteristics: Pump for: Oil, Water, Waste w. Connection: RAngle, Rd2, Rd4 Extras: With support, ... ... P-501 (Order BOM) ¤ A manual specialization of a class node is also possible in this scenario. ¬ Finding objects ¤ It is possible to use a constraint to assign a value to the class node. ¤ It is possible to use a procedure to assign a value to the class node. ¤ An automatic specialization is also possible. (Assign values to characteristics COLOR and GLOSS on the value assignment interface.) Þ If the class node is not specialized automatically, you can specialize it manually in technical postprocessing. º The function for finding classified objects is available for this purpose (=functions of transaction CL30N) Þ Automatic specialization uses the values assigned to characteristics of the class node. You can use a procedure or a constraint to do this. º If this does not work, the system automatically searches for characteristics of the class node on the $parent level (immediately above). º If this does not work, the system automatically analyzes each next level up, toward the $root material. Þ If you use classification as a selection condition (BOM ==>Item ==>General data), the values assigned to $root are always queried. ©SAP AG PLM146 8-219 © SAP AG 2002 Single-Level Order BOM (2) Characteristics: Pump for: Oil, Water, Waste w. Connection: RAngle, Rd2, Rd4 Extras: With support, ... ... P-501 (Pump) (Order BOM) Shaft assy (No profil e) Support ... Bearing A Bearing B Bearing C ... Manual changes always allowed! Manual changes onl y allowed for result-oriented BOM with unrestricted level of detail! ©SAP AG PLM146 8-220 © SAP AG 2002 Engineeri ng After creating the sales order and configuring the sales product, technical postprocessing must take place. This means that sales must inform engineering of incoming orders. Implementation options: - Set user status in the sales order item and report on the status - Define a workflow (not in standard) - Send a mail about the sales order item Confirmation to sales after creating the order BOM to trigger: - Recalculation of prices - Transfer of requirements - Change of user status Communication Between Sales and Engineering Sales order 10 PM-1000 10 Pc SD SD PP PP Þ If the customer requires an enhancement to material configuration, sales and engineering must work closely together. Þ Technical postprocessing of order items is not automatic: it requires sales to inform engineering. ©SAP AG PLM146 8-221 © SAP AG 2002 Customer requirement Locking Requirements Transfer from SD to PP Options for temporaril y locking requirements transfer from SD to PP: Þ Set the status of the configuration to incomplete or locked Þ Set a delivery block in the order header and set the Fixed date and quantity indicator Þ Change the schedule line category in the order (CN/CP - with or without transfer of requirements) Þ Set reason for rejection in order item Requirements for the sales order can be transferred onl y after the order BOM and order routing have been created. Planning in MRP follows this. Status in BOM and routing influence relevancy to MRP. Sales order 10 Matl PM-100010 Pc MRP Planned order SD SD PP PP PP PP PP PP Þ You can define customer-specific reasons for rejecting a sales document item in Customizing for SD. Þ Remember that locking of requirements transfer also means that any requirements already planned will not be consumed. Þ For more information on managing configuration statuses, see note 139978 and related notes. ©SAP AG PLM146 8-222 © SAP AG 2003 ¤ Delete items: Þ Non-variable part Þ Variant parts, even if dependencies make them relevant Þ Configurable items and all their components ¤ Change items: Þ Non-variable part Þ Variant parts, even if dependencies make them relevant Þ Configurable items and all their components ¤ Add items: Þ Non-variable part Þ NO class items Þ Configurable items ¤ Copy items: Þ As for adding items Þ If possible, no exploded class items Order BOM: Manual Changes SAP Menu Logistics Production Master Data Bills of Material Bill of Material Order BOM Create Change Display Maintain (Multilevel) Display (Multilevel) Order Browser Þ If you add configurable items: º If the item has a configuration profile with the Order BOM scenario, you can assign values to it, explode its BOM, and make manual changes. Þ If you add or change items: º You cannot add dependencies to be processed subsequently or items with dependencies to be processed subsequently. ©SAP AG PLM146 8-223 © SAP AG 2002 System Performance and Classification ¤ General hints for all scenarios: ¤ Use cl ass hierarchies or prevent them in Customizing ¤ Default values defined in the characteristic are qui cker than default values set by dependencies ¤ Smallest possible number of highly-selective characteristics for class node ¤ Run statistics for the class type for class nodes ¤ Use separate material items instead of class nodes with few materials ¤ Separate class types for class nodes and vari ant classes ¤ Set up database tables for selection in class nodes Þ How do you set up database tables for class nodes? º In Customizing for the class type (200 here), set the "generated tables" flag. (Transaction O1CL.) º This assumes that report RCCLUKA2 has been started for this class type (transaction SA38). º In class maintenance for the class node (transaction CL02), set the characteristics to index relevant. º Set up the database table for selection, by creating it and filling it (transaction CLGT). The names of the tables are stored in system tables GEN_TABLES_MAIN and GEN_TABLES_SUB. ©SAP AG PLM146 8-224 © SAP AG 2002 Multilevel Order BOM (1) Shaft assy (Order BOM) Characteristics: Pump for: Oil, Water, Waste w. Mode: Electric Pump type: Plunger, Rotary ... P-501 (Order BOM) Selection condition: $parent.CONNECTION eq Rd2 not $self.CONNECTION eq Rd2 not $root.CONNECTION eq Rd2 $parent = next instance Bearing A Bearing B Bearing C Standard: Standard: In the sales order, onl y the In the sales order, onl y the header material can have values header material can have values assigned to it (in this example, assigned to it (in this example, onl y the pump). onl y the pump). This means the connection This means the connection cannot have values assigned. cannot have values assigned. This level can This level can onl y onl y have values have values assigned in technical assigned in technical postprocessing. postprocessing. Characteristics: ... Connection: RAngle, Rd2 , Rd4 Standard: (Without "Maintenance Allowed in Sales Order" Flag) Þ Create sales order in SD for pump P-501 Þ Only assign values to header material Þ No value assignment for configurable assemblies (manually or by dependencies) - for example, bearings are not selected (correctly) Þ No order BOMs can be maintained from the sales order Extended Mode: (With "Maintenance Allowed in Sales Order" Flag) Þ Create sales order in SD for pump P-501 Þ At first, you can only assign values to the header material Þ In the sales order, switch to engineering view: here you can also assign values to configurable assemblies (manually and by using dependencies for the header or assembly), and the BOM can be exploded across multiple levels Þ Order BOMs cannot be maintained from the sales order ©SAP AG PLM146 8-225 © SAP AG 2003 " Multilevel Order BOM" (2) Shaft assy (Order BOM) P-501 (Order BOM) X... Y... Z... Bearing A Bearing B Bearing C ... Manual changes to assigned values allowed! Characteristics: Pump for: Oil, Water, Waste w. Mode: Electric Pump type: Vacuum, Rotary ... Characteristics: ... Connection: RAngle, Rd2 , Rd4 Þ Technical postprocessing for sales order for pump P-501 º Values assigned to header material cannot be changed (even with constraints) º Value assignment for configurable assemblies with order BOM scenarios (manually or by dependencies, also depending on values assigned to $root) º Order BOMs for each assembly: - With manual changes - With the "Automatic Fixing" Indicator - Fixed manually ©SAP AG PLM146 8-226 © SAP AG 2002 KMAT 1 KMAT 2 KMAT 2 Saving of result of fixing How Order BOMs are Saved KMAT 2 KMAT 3 Knowledge based = Super = Master data BOM KMAT 1 KMAT 2 KMAT 2 KMAT 2 KMAT 3 = Result = Exploded BOM Changed Deleted Added Result oriented ©SAP AG PLM146 8-227 © SAP AG 2006 Solution: ... Solution: ... Manual saving of order BOMs Manual saving of order BOMs KMAT 1 KMAT 2 KMAT 2 = Result in technical postprocessing CU51 or CU51E Configuration Profile – Fixing KMAT 2 KMAT 3 Selected assembl y Top down Bottom up Fix Fix ©SAP AG PLM146 8-228 © SAP AG 2002 Variant class 300 Variant class 300 KMAT 1 KMAT 2 KMAT 2 Value 1 Value 2 Value 3 Value 1 Value 2 Value 3 1 2 A 1 2 B ? ? Configuration Profile – Instantiation KMAT 2 KMAT 2 Selected assembl y Top down Bottom up Solution: ... Solution: ... Same product " KMAT2" twice Same product " KMAT2" twice Instantiate Instantiate ©SAP AG PLM146 8-229 © SAP AG 2003 Type Matching (Variant Matching) for Assemblies P-501 (Order BOM) Rtg Linch pin Support base Bearing A Bearing B Bearing C Characteristics: Max. pressure: 8 bar Range: closed Connection: Rd4 Max. pressure: 8 bar Max. pressure: 8 bar Range: closed Range: closed Connection: Rd4 Connection: Rd4 Max. pressure: 5 bar Range: open Connection: Rd2 Max. pressure: 8 bar Range: closed Connection: other Shaft Shaft - - 01 01 Shaft Shaft - - 02 02 Characteristics: Pump for: Oil, Water, Waste w. Mode: Electric Pump type: Vacuum, Rotary ... Shaft Shaft - - 03 03 Shaft assy (Order BOM) Rtg Type matching for material variant Þ Type matching (variant matching) is also possible at assembly level. Þ Prerequisite: - Scenario Order BOM for configuration profile of header material and assembly - Values assigned must match material variant exactly Þ Type matching (variant matching): º Only in technical postprocessing º Started manually º Works for all assemblies, not selected assemblies º Saved in order BOM ©SAP AG PLM146 8-230 © SAP AG 2003 Header Order BOM Characteristics: VERSION: S, N, L LENGTH: 1 - 10 COLOR: R, B, G Characteristics: HEIGHT: 2 - 20 COLOR: R, B, G Characteristics: WIDTH: 3 - 30 PROP: 1, 2, 3 Are the examples possible? How?: 1. WIDTH = (HEIGHT + LENGTH) / 2 2. Header COLOR R results in VERSION L 3. Assembl y 1 COLOR R results in VERSION L Can Dependencies Do This? Assembl y 1 Order BOM Assembl y 2 No order BOM Values assigned in sales Values assigned in CU51 Þ Header material: - Value assignment or changing of values only in sales order Þ Assembly 1: - Value assignment or changing of values only in technical postprocessing - Only values assigned to header can be used (in dependencies) Þ Assembly 2: - Configuration profile is handled as inactive Þ Example 1? ……………………………………………………………………………………. Þ Example 2? …………………………………………………………………………………….. Þ Example 3? ……………………………………………………………………………………. ©SAP AG PLM146 8-231 © SAP AG 2002 Pricing and the Order BOM Scenario ¤ Only values assigned in SD (VA01 or VA02), only at header level, are relevant to pricing ¤ Characteristics of subordinate assemblies are not relevant to pricing ¤ No values assigned or manual changes made in technical postprocessing (CU51) are relevant to pricing ©SAP AG PLM146 8-232 © SAP AG 2002 BOM Explosion (1) Header Order BOM Characteristics: VERSION: S, N, L LENGTH: 1 - 10 COLOR: R, B, G Characteristics: HEIGHT: 2 - 20 COLOR: R, B, G Characteristics: WIDTH: 3 - 30 PROP: 1, 2, 3 Assembl y 1 Order BOM Assembl y 2 No order BOM No profile $parent $root $self ©SAP AG PLM146 8-233 © SAP AG 2002 No profile BOM Explosion (2) Header Order BOM Characteristics: VERSION: S, N, L LENGTH: 1 - 10 COLOR: R, B, G Characteristics: HEIGHT: 2 - 20 COLOR: R, B, G Characteristics: WIDTH: 3 - 30 PROP: 1, 2, 3 Assembl y 1 Order BOM Assembl y 2 No order BOM Procedure: $self.STPO_MENGE = ... if ... Procedure: $set_default($self, COLOR, $root.COLOR) Selection condition: $parent.COLOR eq R R $root.COLOR eq R R R R R Red Þ If the same characteristic is assigned to different materials by means of variant classes, you can assign values independently. Þ You can use dependencies to describe interdependencies (for example, for default values). Þ In selection conditions, both values assigned to characteristic COLOR can be accessed independently of each other. For example, you can change the component quantity depending on the values assigned to both levels. ©SAP AG PLM146 8-234 © SAP AG 2002 $self BOM Explosion (3) Header Order BOM Characteristics: VERSION: S, N, L LENGTH: 1 - 10 COLOR: R, B, G Characteristics: HEIGHT: 2 - 20 COLOR: R, B, G Characteristics: WIDTH: 3 - 30 PROP: 1, 2, 3 Assembl y 1 Order BOM Assembl y 2 No order BOM No profile $parent $root $self No! $root No! Þ If a BOM structure has a large number of levels, all characteristic values that are required for processing dependencies must be at one of the following levels: º $root level º $parent level º If values cannot be assigned to any characteristics at $parent level, only $root level is available. Þ $self level -> Changes to BOM item with reference characteristics Þ Configuration profiles with scenarios other than order BOM are ignored. This can lead to the situation shown in the above example, in which the $parent level is more than one level above the current item, even perhaps the header material. ©SAP AG PLM146 8-235 © SAP AG 2002 ¤ Maintain single-level and multilevel order BOM structures ¤ Create sales orders for the order BOM scenario and make technical changes to the BOM ¤ Maintain both knowledge-based and result-oriented order BOMs in technical postprocessing ¤ Use class nodes in this scenario ¤ Control the BOM explosion You are now able to: Configuration Scenarios with Order BOMs: Unit Summary ©SAP AG PLM146 8-236 Configuration Scenarios with Order BOMs Exercises Unit: Configuration Scenarios with Order BOMs Topic: Single-Level Configuration Structure with Scenario Order BOM At the conclusion of these exercises, you will be able to: • Process sales orders in the environment of this scenario, including order BOM maintenance The exercise also covers: • Checking the master data required • Creating the characteristics, variant class, and configuration profile • Creating a sales order (VA01) and maintaining an order BOM (CU51) A configurable shaft assembly needs to be modeled. Material master records and the super BOM already exist, but without dependencies. The configuration cannot and should not be modeled completely. For this reason, you want to use the option of creating an order BOM. This is implemented as the "order BOM" scenario, with the option of subsequent technical postprocessing. 1-1 Check the master data that already exists for modeling the configurable shaft assembly T-VB2##. 1-1-1 Display material master record T-VB2## with the basic data, sales, and MRP views. Use the following organizational levels: Plant: 1000 Sales organization: 1000 Distribution channel: 10 1-1-2 Display the BOM for your shaft assembly with usage 1 in plant 1000. Compare it with the slide "4. Customer Example Part Structure (Shaft)" in the appendix. (Assembly T-VB3## is not yet in the BOM. Do not assign it to the BOM yet.) ©SAP AG PLM146 8-237 1-2 The bearing selected is to depend on the value assigned to characteristic "connection", according to the following list: Bearing A For right-angled flange Bearing B For round flange (2-hole or 4-hole) Bearing C For other connection To do this, create selection conditions that work correctly, even if the shaft is an assembly in another structure. ($parent or $root?) You do not want the number of screws required to be set by object dependencies – you want to be able to change this manually in technical order processing. If you did not create characteristic "connection" in the previous unit, create it now: T11_## Values: 01 Right-angled flange 02 Round flange (2-hole) 04 Round flange (4-hole) XX Other 1-2-1 Create variant class T_VB2## for your configurable shaft, and assign the characteristic you just created to this class. 1-2-2 Create a configuration profile for your configurable shaft T-VB2##. Use the name N-OBOM for your profile. Assign your configurable shaft to variant class T_VB2##. Set the following parameters: – Process "order BOM" Result-Oriented – Multilevel BOM explosion – PP01 (BOM application) – No availability check – BOM explosion only for configurable assemblies UserInterf – All views, including configuration browser Order BOM – (All default) – (Rest: default) ©SAP AG PLM146 8-238 1-2-3 Assign selection conditions to the three bearing items, so that the components are selected according to the values above: Remember that the shaft can be an assembly in another BOM. ($parent or $root?) Check the result in the simulation. ©SAP AG PLM146 8-239 You can simulate both steps in the simulation. In the sales view, you assign values to the header material. Here: pushbutton: Engineering In the engineering view, you can simulate the BOM explosion. 1-3 Add a sales-relevant item for the shaft T-VB2## to the BOM for your pump T-VPU##. Check the BOM structure of the pump T-VPU## in the simulation. Which configuration profiles are shown for the pump? For each profile you select for the pump, which configuration profiles can be used for the two configurable assemblies? Why? If only one profile is possible, this profile is selected automatically without being displayed explicitly first. To see the profile that is active in the simulation (including the sales order), choose → Environment → Configuration Profile. 1-4 Create and save a sales order with the following data: Order (OR) 1000 10 00 Customer: 1000 Purchase order no.: Your choice T-VB2## 1 piece → Assign values and save. 1-5 In technical postprocessing (order BOM maintenance), change the following data: • You require 3 screws M6x60 and no harness (cable structure). • Increase the component number of the slug 100-310 to 2. Can you? Why? ©SAP AG PLM146 8-240 Optional Display the order BOM as saved in database table STPO. ©SAP AG PLM146 8-241 Configuration Scenarios with Order BOMs Exercises Unit: Configuration Scenarios with Order BOMs Topic: Multilevel Configuration Structure with Scenario Order BOM At the conclusion of these exercises, you will be able to: • Process sales orders in the environment of this scenario, including order BOM maintenance The exercise also covers: • Checking the master data required • Creating the characteristics, variant classes, and configuration profiles • Creating sales orders (VA01) and creating and processing order BOMs (CU51) In the BOM structure of the configurable shaft assembly, you want to include a configurable assembly. You want to be able to maintain order BOMs for this assembly, too. Material master records and the super BOM already exist for the configurable assembly, but without dependencies. 2-1 Check the master data that already exists for modeling the configurable shaft assembly T-VB3##. Display the BOM of your assembly T-VB2##(shaft) in change mode, with usage 1 in plant 1000. Compare it with the slide "4. Customer Example Part Structure (Shaft)" in the appendix. Add assembly T-VB3##to the BOM of the configurable shaft. 2-2 The color selected is to depend on the value assigned to characteristic "color", according to the following list: 100-801 (Red) If value 'Red' is assigned to T-VB2##(shaft) 100-803 (Yellow) If value 'Yellow' is assigned to T-VB3##(assembly color) 100-805 (Blue) If value 'Blue' is assigned to T-VB2##(shaft) or T-VB3## (assembly color) ©SAP AG PLM146 8-242 The quantity of material T-OIL required must be maintained manually in technical postprocessing. 2-2-1 Create the following single-value characteristic (you can copy from group 00): Color T12_## Values: 1 Red 3 Yellow 5 Blue 2-2-2 Create variant class T_VB3## for your configurable assembly and assign the characteristic you just created to this class. Assign the color characteristic to variant class T_VB2##. 2-2-3 Create a configuration profile for your configurable assembly T- VB3##. Use the name 1-OBOM for your profile. Assign your configurable shaft to variant class T_VB3##. Set the following parameters: – Process order BOM Result oriented – Single-level BOM explosion – PP01 (BOM application) – No availability check UserInterf – All views, including configuration browser (Rest: default) 2-2-4 Assign selection conditions to the three color items, so that the components are selected according to the list above: Check the result in the simulation. Start configuration with material T- VB2##. 2-3 Create and save a sales order with the following data: ©SAP AG PLM146 8-243 Standard order (OR) 1000 10 00 Customer: 1000 Purchase order no.: Your choice T-VB2## 1 piece Assign values to the configurable shaft. Can you assign values to the "color" assembly? 2-4 In technical postprocessing (order BOM maintenance), assign values to assembly "color", and change data in both BOMs. Why can you now make changes to both BOMs? ©SAP AG PLM146 8-244 Configuration Scenarios with Order BOMs Solutions Unit: Configuration Scenarios with Order BOMs Topic: Single-Level Configuration Structure with Scenario Order BOM 1-1 Check the modeling of the configurable shaft T-VB2##. 1-1-1 User menu Material → Display → Display Current Display material master T-VB2## (current status): Views: Basic data 1 +2 Sales: Sales Org. Data 1 +2 Sales: General / Plant Data MRP 1 -4 Organizational levels: Plant: 1000 Sales organization: 1000 Distribution channel: 10 1-1-2 User Menu Bill of Material → Material BOM → Display Display BOM with usage 1 in plant 1000. Compare with the slide in the appendix. Assembly T-VB3## is not yet in the BOM 1-2 The bearing selected is to depend on the value assigned to characteristic "connection": 1-2-1 (If you did not create characteristic "connection" in the previous unit, create it now T11_## Values: 01 Right-angled flange 02 Round flange (2-hole) 04 Round flange (4-hole) XX Other) User Menu → Classification → Master Data → Classes ©SAP AG PLM146 8-245 Create a variant class: T_VB2## 300 Variant class shaft 1 (Released) T-## Characteristics: T11_## 1-2-2 Create a configuration profile for the shaft T-VB2##. User menu → Variant Configuration → Configuration Profile → Create Profile overview: N-OBOM 300 Class assignment T_VB2## Configuration initial screen: – Process "order BOM" Result-Oriented – BOM explosion multilevel – PP01 (BOM application) – No availability check – BOM explosion only for configurable assemblies !! UserInterf – All views, including configuration browser (Rest: default) 1-2-3 Create the following selection conditions: Bearing A For right-angled flange Bearing B For round flange (2-hole or 4-hole) Bearing C For other connection User Menu Bill of Material → Material BOM → Change ©SAP AG PLM146 8-246 T-VB2## Plant: 1000 Usage: 1 ©SAP AG PLM146 8-247 Assign and create selection condition for component Bearing type A = 500-501 at the same time: T_SC_T11RE_## $parent.T11_## eq '01' Assign and create selection condition for component Bearing type B = 500-502 at the same time: T_SC_T1124_## $parent.T11_## in ('02', '04') Assign and create selection condition for component Bearing type C = 500-503 at the same time: T_SC_T11XX_## $parent.T11_## eq 'XX' Configuration simulation (see previous exercises) Value assignment in sales view BOM explosion in engineering view 1-3 Add shaft to BOM for pump as sales-relevant item: User Menu → Bill of Material → Material BOM → Change BOM for material T-VPU##with usage 3 in plant 1000 ¬ Add new material item: L T-VB2## 1 piece Sales-relevant indicator (In item detail screen, status) Configuration simulation (see previous exercises) Result: Two possible configuration profiles for pump: 1. N-BOM ¬ Only profile 1-BOM possible for casing No profile active for shaft 2. N-SET ¬ Only profile 0-BOM possible for casing Profile N-OBOM possible for shaft ©SAP AG PLM146 8-248 1-4 Create and save sales order Favorites → Create Sales Order (VA01) Standard order (OR) 1000 10 00 Sold-to party: 1000 (if prompeted, ship-to party: 1000) Purchase order no.: Your choice T-VB2## 1 piece Assign values to the header material. 1-5 Order BOM maintenance: User Menu → Bill of Material → Order BOM → Maintain (Multilevel) =>Value assignment screen (display only) Pushbutton: Result You require 3 screws M6x60 and no harness (cable structure). (Select item for screw M6x60, then choose Pushbutton: Item full = Shift + F4 Change quantity Select item for cable structure Pushbutton: Delete = Shift + F2 or → Edit → Delete) Can you change the component quantity of the slug 100-310 to 2? No Why? Even though it is a result-oriented BOM (this allows maintenance of order BOMs even for non-configurable assemblies), the BOM of the shaft 100-300 is not displayed here and therefore cannot be changed. (See flag in configuration profile "Only configurable assemblies".) ©SAP AG PLM146 8-249 optional Favorites → Data Browser (SE16) Database table KDST Select order BOMs using order number in Field: VBELN ¬ Make a note of the internal BOM number STLNR Favorites → Data Browser (SE16) Database table STPO (Select items of order BOMs using BOM category STLTY =K and internal BOM number STLNR) You can also use ANNAM =PLM-##. ©SAP AG PLM146 8-250 Configuration Scenarios with Order BOMs Solutions Unit: Configuration Scenarios with Order BOMs Topic: Multilevel Configuration Structure with Scenario Order BOM 2-1 Check the modeling of the configurable assembly T-VB3## User Menu Bill of Material → Material BOM → Change Display BOM for material T-VB2##with usage 1 plant 1000. Compare with graphic. ¬ Add new material item: L T-VB3## 1 piece 2-2 2-2-1 User Menu → Classification → Master Data → Characteristics Create single-value characteristic, copying from group 00 if possible: T12_## Description: Color Group T-## Values: 1 Red 3 Yellow 5 Blue 2-2-2 User Menu → Classification → Master Data → Classes Create a variant class: T_VB3## 300 Variant class for color 1 (Released) T-## Characteristics: T12_## Change variant class: T_VB2## 300 ©SAP AG PLM146 8-251 Add characteristic T12_##. 2-2-3 User Menu → Variant Configuration → Configuration Profile → Create Create a configuration profile for color T-VB3##. Profile overview: 1-OBOM 300 Class assignment T_VB3## Configuration initial screen: Configuration parameters – Process "order BOM" Result-oriented order BOM – Single-level BOM explosion – PP01 (BOM application) – No availability check UserInterf – All views including configuration browser (Rest: default) 2-2-4 Assign selection conditions to colors according to the following list: 100-801 (Red) If value 'Red' is assigned to T-VB2##(shaft) 100-803 (yellow) If value 'Yellow' is assigned to T-VB3##(color) 100-805 (Blue) If value 'Blue' is assigned to T-VB2##(shaft) or T-VB3##(assembly color) User Menu Bill of Material → Material BOM → Change T-VB3## Plant: 1000 Usage: 1 (Item Overview) → Pushbutton or Extras → Object Dependencies → Assignments = Ctrl + F1 Assign and create dependency (procedure) at the same time Item: 100-801: Selection condition: T_SC_ROOT_1_## ©SAP AG PLM146 8-252 Syntax: $root.T12_## = '1' Item: 100-803: Selection condition: T_SC_PARENT_3_## Syntax: $parent.T12_## = '3' Item: 100-805: Selection condition: T_SC_ROOT_PARENT_5_## Syntax: $root.T12_## = '5' or $parent.T12_## = '5' Configuration simulation with T-VB2## (see previous exercises). Value assignment in sales view BOM explosion in engineering view 2-3 Create and save sales order: Favorites → Create Sales Order (VA01) Standard order (OR) 1000 10 00 Sold-to party: 1000 (if prompted, ship-to party: 1000) Purchase order no.: Your choice T-VB2## 1 piece You can only assign values to the header material. (You cannot assign values to assembly T-VB3##.) 2-4 Create order BOM: User Menu → Bill of Material → Order BOM → Maintain (Multilevel) → Value assignment screen (display only) Assigning values to the assembly is possible here, because configuration profile is also "order BOM". Pushbutton: Result Changes possible in both BOMs. (Reason: active profiles with same type of order BOM (result oriented)) ©SAP AG PLM146 8-253 ©SAP AG PLM146 9-254 © SAP AG 2003 Contents: Other Variant Configuration Tools ¤ Tables for storing variant configuration data ¤ Application Programming Interface (API) ¤ Appli cation Link Enabling (ALE) ¤ User exits ¤ Anal ysi s tool ¤ SAP IPC Sales Configuration Engine ©SAP AG PLM146 9-255 © SAP AG 2006 Other Variant Configuration Tools: Unit Objectives ¤ Describe how variant configuration is saved. ¤ Say which APIs and user exits exist in the variant configuration environment. ¤ Use ALE to distribute variant configuration models. ¤ Use the analysis tools for reporting. ¤ Describe how modeling for the SAP IPC Configuration Engine differs from modeling for the SAP ERP variant configuration. At the conclusion of this unit, you will be able to: ©SAP AG PLM146 9-256 © SAP AG 2002 Other Variant Configuration Tools: Course Overview Diagram Control Options in the Configuration Profile 3 3 Configuration Scenarios Without BOM Explosion 4 4 Configuration Scenarios with Order BOMs 8 8 2 2 Configuration Scenarios with BOM Explosion 7 7 Variant Configuration: Consolidation More About Object Dependencies 6 6 Course Overview 1 1 More About Constraints 5 5 Other Variant Other Variant Configuration Tools Configuration Tools 9 9 Conclusion 10 10 ©SAP AG PLM146 9-257 © SAP AG 2006 ¤ You want to keep variant configuration open, so that you can: Þ Use interfaces Þ Distribute models to other SAP ERP Systems Þ Work with models outside the SAP ERP System (?SCE) ¤ You want to explore further technical possibilities Other Variant Configuration Tools: Business Scenario ©SAP AG PLM146 9-258 © SAP AG 2003 IBase: IBIB IBase administrative data Instances: IBIN Instances IBINT Instance descriptions Assigned characteristic values: IBINVALUES Symbols for instance IBSYMBOL Characteristic value or interval Structure: IBST Parent and root information Owner: IBINOWN Owner of configuration, such as sales order or material Observer: IBINOBS Interested party for instance, such as planned order or production order No conversion required for new table structure How Variant Configuration is Saved (1) Þ IBIN contains one entry for each configuration. Date validity is relevant here, so the primary key is the IN_RECNO field, not the object or the instance. Þ IBINVALUES contains the value assignment key for each value assigned in the configuration (primary key IN_RECNO). The key is given by the SYMBOL_ID field. This means that the assigned values are not explicitly in database table IBINVALUES. Þ IBSYMBOL contains the information on which value was assigned to which characteristics in which class type for each symbol ID. Together with the entries in IBINVALUES, this gives the assigned values in the configuration. ©SAP AG PLM146 9-259 © SAP AG 2002 How Variant Configuration is Saved (2) CUVTAB Table header CUVFUN Function header CUVTAB_ADM Administrative data CUVFUN_ADM Administrative data CUVTAB_TX Texts CUVFUN_TX Texts CUVTAB_FLD Characteristics CUVFUN_PAR Characteristics (old: KSML) (old: KSML) CUVTAB_IND Value assignment CUVFUN_IND Value assignment alternatives (old: KRIF) alternatives (old: KRIF) CUVTLN Line (old: CUVT and KSSK), only here with engineering change management CUVTAB_VALC Character values CUVTAB_VALC Non-character values Conversion to new table structure required: XPRA (=conversion report program) runs automatically on upgrade Þ This new way of saving variant tables and variant functions requires new steps in Customizing for variant configuration: º Maintain statuses for variant tables (previously class statuses for class type 029) º Maintain groups for variant tables (previously class groups) º Maintain statuses for variant functions (previously class statuses for class type 036) º Maintain groups for variant functions (previously class groups) Þ In authorization management, there are new authorization objects for: º Maintaining variant tables (structure and contents) º Linking to database tables º Maintaining variant functions Þ Only the maintenance of table contents is interfaced to engineering change management. ©SAP AG PLM146 9-260 © SAP AG 2006 SAP ERP SCE External systems CAx C, C++ ... SAP ERP SAP ERP SAP User Code API BAPI SAPGUI API CAD Interface Reports User Exits User Exits User Exits RFC Accessed from SAP Accessed externall y SAP Interface Landscape ©SAP AG PLM146 9-261 © SAP AG 2006 Terms in the Interface Landscape ¤ User exits Customer-specific programs are called at a specific point in time, with a predefined interface - Existing INCLUDE commands access INCLUDE files that are initiall y empty ¤ API Interfaces used by application programs to communicate with other systems - Function modules that compl y with predefined rules (for example, RFC compatible) ¤ BAPI Business Application Programming Interface; - Standardized interface (API with additional predefined rules) ¤ RFC Remote Function Call; - Procedure enabling communication between SAP Systems and external systems (including other SAP Systems) ©SAP AG PLM146 9-262 © SAP AG 2006 Test Environment for APIs in Variant Configuration API Li st Log Fil e Fi ni sh Initiali zati on Confi gurator APIs/BAPIs Anal ysi s Sal es order i tem CAVC_ TEST CAVC_#_<exact function> O = Object C = Configuration of all instances I = Configuration of one instance Example: Order BOM - Initialize - Save and close - Exit CU51 CAVC O ORDER BOM INIT CAVC O ORDER BOM SAVE CAVC O ORDER BOM CANCEL ©SAP AG PLM146 9-263 © SAP AG 2002 User Exits in the Variant Configuration Environment (1) O User exits on the value assigment screen: - Use interface design to fulfill prerequisites - Create pushbuttons - Name: CUSTOMER_PUSHBUTTON_### - Any description and pushbutton label - No other details to specify Pushbutton 01 Exit_SAPLCEI0_010 Pushbutton 02 Exit_SAPLCEI0_011 Pushbutton 10 Exit_SAPLCEI0_019 In program LCEI0F01 in FORM routine EXECUTE_PUSHBUTTON_GROUP ©SAP AG PLM146 9-264 © SAP AG 2002 User Exits in the Variant Configuration Environment (2) O Additional user exits for variant configuration ¤ CCUX0000 = Additional check on configuration - Executed at final check on configuration - Contains function module: Exit_SAPLCUKO_001 ¤ CCUX0001 = Load function for configuration - Controls whether source for loading is external: Function module: Exit_SAPLCUD0_001 - Loads from external source: Function module: Exit_SAPLCUXC_001 ¤ CCUX0002 = Specification of a class node - Reacts to inconsistencies in object search Function module: Exit_SAPLCUD0_002 ¤ CCUX0800 = Controls level of detail in multilevel configurations - Sets explosion of all or onl y configurable assemblies Function module: Exit_SAPLCUKO_002 Þ The list above contains a selection of user exits with the function modules they include. Þ For a complete list, go into transaction SMOD. In the F4 help, choose the Hierarchy of SAP applications. To find all the user exits in the variant configuration environment, look under: º SAP º LO º LO-VC º CU In the components of the enhancement, you will find the list of function modules. ©SAP AG PLM146 9-265 © SAP AG 2002 The anal ysis tool can be called from the result screen of configuration. It logs the following for the current configuration: ¤ Summary Configurable item Class node Characteristics (single-level, multilevel, restrictable) Values ¤ Overview of dependencies: which are used, how often, and where? ¤ Explosion of all BOMs of configurable items ¤ Reporting for class nodes ¤ Detailed list of configuration of configurable items: Configuration profile Dependencies Assigned values Extras : : Anal ysi s Anal ysis Tool ©SAP AG PLM146 9-266 © SAP AG 2006 ALE ALE ALE Structure of the complete model of the configurable product Engineering Application Link Enabling (ALE) Advantages ¤ Use of a SAP System with special Customizing as a PDM System ¤ Separate release upgrades ¤ Distribution of system load ¤ Heterogeneous SAP system landscape can be represented Requirements of data distribution The following must be possible: Þ (Selective) transport of product data to different target systems, especially master data for variant configuration Þ Robust, reliable, fast data distribution Þ Change management across different systems Þ Monitoring across different systems Þ Keep the productive system running without interruption during data distribution ¬Which tools are available for data distribution, and when should you use which tool? ©SAP AG PLM146 9-267 © SAP AG 2006 ALE Strategies (Simplified) Set a change pointer ALE Target system Source system Material: A-01 IDoc generation Batch jobs Manual transacti on Directl y SAP PLM Appli cation SAP ERP Appli cation ALE CAD application (and local PDM application) Interface Material: A-01 Material Material Material Material Save change Change Material: Basic Data Change Material: Basic Data Material: A-01 Assembly 01 Material status: 01 02 Basic material: ST37 Material Material TM TM Þ The SAP System has two distribution options. First, there is direct distribution. You use a report program to select the objects you want to distribute. Second, you can use a "change pointer" to control distribution. Each change to an object, such as a status change in a material master, can generate a change pointer. This pointer can generate IDocs (intermediate documents) that control the transport from the source system to the target system. Þ For more detailed information, see the SAP documentation on ALE. ©SAP AG PLM146 9-268 © SAP AG 2003 Sequence for Transporting Objects with ALE O Characteristics and characteristic values O Classes O Table structures O Table contents O Function modules O Functions O Global dependencies O Constraint nets O Characteristics and values for assignment of global dependencies G Material master records ¤ Configuration profiles ¤ Interface design ¤ Bills of material ¤ Material master records of material variants 11 11 12 13 14 Þ Message types (IDocs) supplied Material master record MATMAS Bill of material BOMMAT Characteristics CHRMAS Classes CLSMAS (basic data & dependencies) (basic data & dependencies) Object classification CLFMAS Global dependencies KNOMAS Configuration profile CNPMAS Variant tables VTAMAS Variant table contents VTMMAS Constraint nets DEPNET Variant function VFNMAS Document DOCMAS Cost center COSMAS Cost center group COGRP Cost elements COELEM Cost element group COGRP2 Activity types COASMAS Activity type group COGRP5 Prices COACTV Change numbers ECMMAS Prices and conditions COND_A Þ Interface designs are distributed using a BAdI (object name VariantConfigUI, method Savem). Þ The values assigned to material variants are distributed with the material master records. Settings are required for this in the Global Settings in Customizing for the material master. ©SAP AG PLM146 9-269 © SAP AG 2003 Product Replication with ALE Distribution Units ¤ Product replication with mySAP PLM distributes products from a central PLM system to other productive SAP systems. The product data is collected in consistent data packets and distributed to the target system using ALE. ¤ Distribution of products instead of individual objects ¤ Collected in configuration folders in the replication workbench ¤ Simultaneous distribution to different target systems ¤ Controlled, transparent process ¤ Notification of recipients Þ A product version is created in a central PLM system. This version consists of consistent data and contains the product structure. Þ The distribution of the product version uses Application Link Enabling (ALE) technology for replication of the entire product. Þ Product replication with mySAP PLM makes the distribution of products from a central PLM system to various production systems easier. Þ Product data is collected in the replication workbench For example, you select a material master record, collect all the data related to it by using the "baseline" procedure, and transfer this data to a configuration folder. Þ Then you define the target system and the recipients responsible are notified. Distribution transfers either delta information only or all data (for the initial distribution). ©SAP AG PLM146 9-270 © SAP AG 2006 SAP IPC - Sales Configuration Engine Online Store Mobile Sales Internet Sales Vehicl e Management System CRM Contact Center Speci fic Integrati on Scenari o Non-SAP SCE database Runtime Runtime version 1 version 1 O Modeling in the SAP ERP System O Creating a knowledge-base object O Creating one or more runtime versions PLM O Downloading the runtime version to the SCE database SAP IPC Þ Abbreviations: º CRM Customer Relationship Management º IPC Internet Pricing and Configurator º ITS Internet Transaction Server º KB Knowledge base º PLM Product Lifecycle Management º RFC Remote Function Call º SCE Sales Configuration Engine º SPE Sales Pricing Engine Þ A knowledge-base object defines virtual parentheses around all objects in the knowledge base of a configurable product. Runtime versions can only be generated for released knowledge- base objects. Þ The runtime version of a knowledge-base object defines the criteria (date, plant, and BOM application) for the knowledge base. On generation of the runtime version, the data of all objects in the knowledge base is collected together. The consistency of the data is checked. Each has a unique name. ©SAP AG PLM146 9-271 © SAP AG 2002 Modeling for the SCE: Differences from SAP R/3 (1) ¤ Each runtime version contains: Þ Exactl y one plant Þ Exactl y one BOM explosion Þ Exactl y one development status (ECM) = date (Parameter effectivity is ignored) ¤ No configuration profiles with single-level BOM explosion ¤ No order BOM maintenance in the IPC SCE No type matching at assembly level ¤ Only sales-relevant BOM items can be configured ¤ Only materi al items and class items are copied to the runtime versions ¤ Item key consists of an item number and a material or class number © SAP AG 2002 ©SAP AG PLM146 9-272 © SAP AG 2002 © SAP AG 2002 Modeling for the SCE: Differences from SAP R/3 (2) ¤ The classification of materials cannot be used as a selection condition (see basi c data, item detail screen) ¤ Manual creation and deletion of items is not possible ¤ BOMs for configurable materials onl y ¤ No conversion between units of measure - it uses the base unit of measure ¤ Al l characteristics must be assigned to (variant) classes, including reference characteristics, otherwise they are not downloaded ¤ User-defined data types (UDEF) cannot be used ¤ Value hierarchies cannot be used (only end nodes are transferred) ¤ Intervals cannot be assigned as values ¤ No class-specific overwrite ¤ Organizational areas are ignored ©SAP AG PLM146 9-273 © SAP AG 2003 © SAP AG 2003 Modeling for the SCE: Differences from SAP R/3 (3) ¤ Reference characteristics can onl y be used for: STPO-MENGE, SDCOM (VBAK and VBAP downloaded by sales application, not in SCE knowledge base) ¤ 1:1 assignment of reference characteristic to table field ¤ For both techniques for value-dependent pricing, reference characteristic SDCOM-VKOND is required ¤ Class nodes are only repl aced if exactly one suitable material number is found ¤ Find objects in class node onl y by assigning values at the class node itself ¤ Manual replacement of class node only with swing user interface (UI), not with Web UI. ©SAP AG PLM146 9-274 © SAP AG 2002 © SAP AG 2002 Modeling for the SCE: Differences from SAP R/3 (4) ¤ Syntax elements part_of and subpart_of can be processed only for configuration scenarios Sal es order and Planned/production order multilevel ¤ You cannot use $sum_parts and $count_parts ¤ All procedures must be assigned to the configuration profile or BOM, not to characteristics or characteristic values ¤ Actions cannot be used! ¤ Vari ants functions and user exits must be written in Java (or C) ¤ Names of variant tables and their columns must consist entirely of alphanumeric characters and underscores, and must not start with SCE ¤ Each tabl e field must contain exactl y one entry ©SAP AG PLM146 9-275 © SAP AG 2002 Other Variant Configuration Tools: Unit Summary ¤ Describe how variant configuration is saved (new structure!) ¤ Say which APIs and user exits exist in the variant configuration environment ¤ Use ALE to distribute vari ant configuration models ¤ Use the analysis tools for reporting ¤ Describe how modeling for the SAP IPC SCE differs from modeling for SAP R/3 You are now able to: ©SAP AG PLM146 10-276 © SAP AG 2002 Conclusion: Course Overview Diagram Control Options in the Configuration Profile 3 3 Configuration Scenarios Without BOM Explosion 4 4 Configuration Scenarios with Order BOMs 8 8 2 2 Configuration Scenarios with BOM Explosion 7 7 Variant Configuration: Consolidation More About Object Dependencies 6 6 Course Overview 1 1 More About Constraints 5 5 Other Variant Configuration Tools 9 9 Conclusion Conclusion 10 10 ©SAP AG PLM146 10-277 © SAP AG 2002 Now you are familiar with and are able to use: ¤ Advanced settings of the configuration profile and interface design ¤ Special aspects of object dependencies ¤ Special features of the different scenarios ¤ Knowledge-based and result-oriented order BOMs ¤ Multilevel configuration structures ¤ Low-level and high-level configuration ¤ Additional tools (BAPI, ALE, user exits, and the anal ysis tool) ¤ The different ways of storing variant configuration data ¤ Hints on system performance Course Summary ©SAP AG PLM146 10-278 © SAP AG 2002 Recommended Follow-up Acti vities ¤ Go through the exercises using IDES data or your own data ¤ Read online documentation ¤ Read IMG documentation ¤ Read release notes ©SAP AG PLM146 11-279 © SAP AG 2003 ¤ Structure of customer example: Pump T-VPU## ¤ Data Sheet for Exercises ¤ Frequently-used menu paths ¤ Ideas for Modeling Contents: Appendix ©SAP AG PLM146 11-280 © SAP AG 2003 Customer Example Structure (Pump) Pump T-VPU## configurable Red 100 - 801 Yellow 100-803 Blue 100 - 805 Grayc. 500 - 101 Alu. 500 - 102 Steel 500 - 103 Harness 100 - 432 Casing T-VB1## Met. sh. 100 - 700 Brg case 100 - 500 Electrics 100 - 400 Shaft T-VB2## Bolt 100 - 433 Bearing 100 - 510 Casing 100 - 410 Chip 100 - 420 Color display 100 - 430 Power supply 100 - 431 Harness 100 - 432 Bolt 100 - 433 Bolt M 6x60 100 - 433 Harness 100 - 432 Bearing A 500 -501 Bearing B 500 -502 Bearing C 500 -503 T-OIL configurable configurable Shaft 100 - 300 Slug for shaft 100 -310 Color T-VB3## configurable ©SAP AG PLM146 11-281 © SAP AG 2003 1. Customer Example Substructure (Casing) Casing T-VB1## configurable Plnd/Prod. order without BOM explosion Variant class: T_VB1## Pump for: Oil, Water, Waste water, Suspension Pump type: Vacuum, Wet pit, Rotary, Wing Language: De, En, Fr, Es, Pt, Ru Documentation: De, En, Es, Ru Inscription: De, En, Ru Pump lift: 1000 - 100,000 l/h Weight: +(reference characteristics) Grayc. 500 - 101 Alu. 500 - 102 Steel 500 - 103 Bolt M 6x60 100 - 433 Harness 100 - 432 ©SAP AG PLM146 11-282 © SAP AG 2003 2. Customer Example Structure (Pump Without Shaft) Pump T-VPU## configurable Casing T-VB1## Met. sh. 100 - 700 configurable Variant class: T_VPU## Rotation: CW, Ctr-CW, Any Max. W. pressure: 2 - 10 bars Range: open, closed Length: 10 - 100 cm Width: 10 - 100 cm Area: 0.01 - 1 m² Color: Red, Yellow, Blue R Electrics 100 - 400 Brg case 100 - 500 Plnd/Prod. order with multil evel BOM explosion Plnd/Prod. order without BOM explosion Pl nd/Prod. order with si ngl e-l evel BOM explosion ©SAP AG PLM146 11-283 © SAP AG 2003 Pump T-VPU## configurable Casing T-VB1## Met. sh. 100 - 700 configurable Variant class: T_VPU## Rotation: CW, Ctr-CW, Any Max. W. pressure: 2 - 10 bars Range: open, closed Length: 10 - 100 cm Width: 10 - 100 cm Area: 0.01 - 1 m² Color: Red, Yellow, Blue Electrics 100 - 400 Brg case 100 - 500 3. Customer Example Structure (Pump Without Shaft) R Pl nd/Prod. order with si ngl e-l evel BOM explosion Pl nd/Prod. order without BOM explosion Pl nd/Prod. order wi th mul til evel BOM explosion Sal es order with mul ti level BOM explosion ©SAP AG PLM146 11-284 © SAP AG 2003 4. Customer Example Part Structure (Shaft) Color T-VB3## configurable Red 100 - 801 Yellow 100-803 Blue 100 - 805 Harness 100 - 432 Shaft T-VB2## Bolt M 6x60 100 - 433 Bearing A 500 -501 Bearing B 500 -502 Bearing C 500 -503 T-OIL configurable Variant class: T_VB2## Connection: Right-angled flange Round flange (2-hole) Round flange (4-hole) Other Color: Red, Yellow, Blue Variant class: T_VB3## Color: Red, Yellow, Blue Shaft 100 - 300 Slug for shaft 100 -310 Order BOM Mul ti level Order BOM Single l evel ©SAP AG PLM146 11-285 © SAP AG 2003 5. Customer Example Structure (Pump) Shaft T-VB2## configurable Color T-VB3## configurable Pump T-VPU## configurable Casing T-VB1## Met. sh. 100 - 700 configurable Variant class: T_VPU## Rotation: CW, Ctr-CW, Any Max. W. pressure: 2 - 10 bars Range: open, closed Length: 10 - 100 cm Width: 10 - 100 cm Area: 0.01 - 1 m² Color: Red, Yellow, Blue Electrics 100 - 400 Brg case 100 - 500 R Order BOM Mul ti level Order BOM Sing-Level Pl nd/Prod. order wi th multi l evel BOM explosion Sal es order with mul ti level BOM explosion Pl nd/Prod. order without BOM explosion Pl nd/Prod. order with si ngl e-l evel BOM explosion ©SAP AG PLM146 11-286 © SAP AG 2003 Database Tables for Variant Configuration (1) KSSK OBJ EK =Object key KLART =Class type CLINT =Internal class number KLAH CLINT =Internal class number KNOBJ =Object no. for dep. KSML CLINT =Internal class number IMERK =Internal char. number OMERK =Internal char. number CABN ATINN =Internal char. number ATNAM =Characteristic name KNOBJ =Object no. for dep. CAWN ATINN =Internal char. number ATWRT =Char. value (CHAR) ATFLV =From char. value (NUM) ATFLB =To char. value (NUM) KNOBJ =Object no. for dep. CUCO OBJ EK =Object key KNOBJ =Object no. for dep. CUKB KNNUM =Int. dependency no. KNNAM =Dependency name CUKN KNNUM =Int. dependency no. CUEX KNOBJ =Object no. for dep. KNNUM =Int. dependency no. CUOB KNOBJ =Object no. for dep. KNNUM =Int. dependency no. Þ MARA General material data Þ MARC Plant data for material Þ CUCO Master data table for configuration profiles Þ VBAP Item data for sales document Þ INOB Assignment of an internal number to any object Þ MAST Link between material and bill of material Þ KDST Link between sales order item and bill of material Þ AUSP Values assigned to characteristics Þ KSSK Assignment table: object to class Þ CUOB Assignment of object to dependencies Þ STPO BOM items Þ CABN Master data for characteristics Þ KLAH Master data for class header Þ KSML Assignment of characteristics to classes Þ CAWN Master data for characteristic values Þ CUEX Dependency compilation Þ CUKB Administrative information on dependency maintenance Þ CUKN Dependency source code base for variants / configuration ©SAP AG PLM146 11-287 © SAP AG 2003 Database Tables for Variant Configuration (2) INOB CUOBJ =Internal object number OBTAB =Database table of object OBJ EK =Object key AUSP OBJ EK =Object key ATINN =Internal char. number Database tabl es for routing PLPO PLFH PLFL KNOBJ =Object no. for dep. MARC MATNR =Material number CUOBJ STDPD =Plant-specific material variant VBAP VBELN =Document number POSNR =Item number MATNR =Material number CUOBJ =Configuration object MAST STLNR =BOM number MATNR =Material number WERKS =Plant STPO STLTY =BOM category STLNR =BOM number STPOZ =Internal item number KNOBJ =Object no. for dep. MARA MATNR =Material number CUOBF SATNR =Cross-plant material variant CUCO OBJ EK =Object key KNOBJ =Object no. for dep. IBASE IBSYMBOL-ATINN =Internal char. number IBIN-INSTANCE =Instance of configuration KLAH CLINT =Internal class number CUOB KNOBJ =Object no. for dep. KSSK OBJ EK =Object key CABN ATINN =Internal char. number = Part 1 = Part 3 KDST STLNR =BOM number VBELN =Document number POSNR =Item number MATNR =Material number Þ MARA General material data Þ MARC Plant data for material Þ CUCO Master data table for configuration profiles Þ VBAP Item data for sales document Þ INOB Assignment of an internal number to any object Þ MAST Link between material and bill of material Þ KDST Link between sales order item and bill of material Þ AUSP Values assigned to characteristics Þ KSSK Assignment table: object to class Þ CUOB Assignment of object to dependencies Þ STPO BOM items Þ CABN Master data for characteristics Þ KLAH Master data for class header Þ KSML Assignment of characteristics to classes Þ CAWN Master data for characteristic values Þ CUEX Dependency compilation Þ CUKB Administrative information on dependency maintenance Þ CUKN Dependency source code base for variants / configuration ©SAP AG PLM146 11-288 © SAP AG 2003 Database Tables for Variant Configuration (3) IBIN IBASE =IBase number INSTANCE =Instance number OBJ NR =Object number incl. object type IN_RECNO =Unique record number IBINVALUES IN_RECNO =Unique record number SYMBOL_ID =Symbol identifier IBIB IBASE =IBase number IBINOBS INSTANCE =Instance number INTTYP =Type of observer OBJ KEY =Object key of observer IBSYMBOL SYMBOL_ID =Symbol identifier ATINN =Internal char. number ATWRT =Char. value (CHAR) ATFLV =From char. value (NUM) ATFLB =To char. value (NUM) IBST INSTANCE =Instance number PARENT =Superior component ROOT =Top-level component IBSTREF IN_RECNO =Unique record number OBJ KEY =Object key IBINOWN INSTANCE =Instance number INTTYP =Type of owner OBJ KEY =Object key of owner Data analysis: IBINOWN-INTTYP + IBINOWN-OBJ KEY Root: IBINOWN-INSTANCE IBIN-INSTANCE IBIN-IBASE All: IBIN-INSTANCE IBIN-IN_RECNO IBINVALUES-SYMBOL_ID IBSYMBOL-AT... Þ IBIB IBase administrative data Þ IBIN Data of an instance version Þ IBINT Instance descriptions Þ IBST Root relationship and is_part_of relationship ("Parent" and "Root") Þ IBINVALUES Assignment of a characteristic value to an instance Þ IBINOWN Owner of root instance and therefore of IBASE (for example, sales order item) Þ IBINOBS Instance observer (for example, follow-up documents for sales order, such as production order) Þ IBSTREF BOM reference to an is_part_of relationship / instance Þ IBSYMBOL Characteristic value (single value or interval) ©SAP AG PLM146 11-289 ©SAP AG PLM146 11-290 Data Sheet for Exercises Explanation of Symbols in Exercises and Solutions Exercises Solutions Objectives Business Scenario Hints and Tips Warning or Caution ©SAP AG PLM146 11-291 Data in the Exercises All data exists in IDES. The IDES demo data was used as a copy template. Type of Data Exercise Data in IDES Demo Data in IDES Materials *) =Group ## Pump (configurable) …*) T-VPU## P-500 Casing (configurable) …*) T-VB1## 500-100 Shaft (configurable) … *) T-VB2## 500-300 Color (configurable) …*) T-VB3## Copy of 500-100 Casing (cast iron) 500-101 500-101 Casing (aluminum) 500-102 500-102 Casing steel 500-103 500-103 Cable structure 100-432 100-432 Screw (bolt) M 6x60 100-433 100-433 Sheet metal ST37 100-700 100-700 Bearing case 100-500 100-500 Ball bearing 100-510 100-510 Electronic 100-400 100-400 Casing for electronic drive 100-410 100-410 Circuit board M-1000 100-420 100-420 Color display 100-430 100-430 Mains adapter 100 –240 V 100-431 100-431 Bearing Case A 500-501 500-501 Bearing Case B 500-502 500-502 Bearing Case C 500-503 500-503 Color red without gloss 100-801 100-801 Color yellow without gloss 100-803 100-803 Color blue without gloss 100-805 100-805 ©SAP AG PLM146 11-292 Oil (OH material) T-OIL T-OIL Shaft 100-300 100-300 Slug for shaft 100-310 100-310 All the following data already exists in IDES for group 00. Data for all other groups also exists, unless it is marked with (*). In these cases, the data is created or assigned (bill of material, for example) in the exercises during the course. Bills of Material Header material Component T-VPU##(plant 1000) (usage 3) L T-VB1##(*) L T-VB2##(*) R 100-700 L 100-500 L 100-400 T-VB1##(plant 1000) (usage 1) L 500-101 L 500-102 L 500-103 L 100-432 L 100-433 T-VB2##(plant 1000) (usage 1) L 500-501 L 500-502 L 500-503 L T-VB3## (*) L 100-432 L 100-433 L 100-300 T-VB3##(plant 1000) (usage 1) L 100-801 L 100-803 ©SAP AG PLM146 11-293 L 100-805 L T-OIL Classes (all *) (300)T_VB1## (300)T_VB2## (300)T_VB3## (300)T_VPU## Characteristics (all *) T01_## Pump for T02_## Pump type T03_## Type of casing T04_## Pump capacity T05_## Language T06_## Documentation T07_## Lettering T09_## Country key T10_## SCREEN_DEP invisible T11_## Connection T12_## Color T13_## Length of sheet metal (cm) T14_## Width of sheet metal (cm) T15_## Area of sheet metal (m2) T16_## Rotation direction ©SAP AG PLM146 11-294 T17_## Maximum working pressure (bar) T18_## Range T19_## Net weight (material master) T19N_## Net weight of item T19B_## Gross weight of item TROMS1_## Size 1 TROMS2_## Size 2 TROMEN_## Quantity of variable- size item Object Dependencies (*) T_SC_T03_##_1 T_SC_T03_##_2 T_SC_T03_##_3 T_CN_VB1## T_CS_VB1## T_PROC_T401_## T_PROC_T402_## T_PROC_T09_## T_PROC_T10_## T_PROC_T19_## T_SC_T11RE_## T_SC_T1124_## T_SC_T11XX_## T_SC_ROOT_1_## T_SC_PARENT_3_## T_SC_ROOT_PARENT_5_## ©SAP AG PLM146 11-295 T_PROC_ROMS_## T_CN1_VPU##(N-BOM profile) T_CN2_VPU##(N-SET profile) T_CS1_VPU##(in T_CN1_VPU##) T_CS_VPU##_221 (in T_CN2_VPU##) T_CS_VPU##_222 (in T_CN2_VPU##) T_CS_VPU##_223 (in T_CN2_VPU##) Variant Tables (*) T_SEL_COND_## T_CONSTRAINT_## Configuration Profiles (*) For T-VB1## 0-BOM 1-BOM For T-VB2## N-OBOM For T-VB3## 1-OBOM For T-VPU## N-BOM N-SET ©SAP AG PLM146 11-296 ©SAP AG PLM146 11-297 Frequently-Used Menu Paths Activities Menu Path Master Data Maintenance: Display material master 1. SAP Menu → 2. Logistics → 3. Production → 4. Master Data → 5. Material Master → 6. Material → 7. Display → 8. Display Current Change material master …→ 7. Change → 8. Immediately Create material master …→ 7. Change General → 8. Immediately Display material BOM …→ 5. Bills of Material → 6. Bill of Material → 7. Material BOM → 8. Display Change material BOM … → 8. Change Create material BOM … → 8. Create Display routing … → 5. Routings → 6. Routings → 7. Standard Routings → 8. Display Change routing …→ 8. Change Create routing … → 8. Create Classification Objects: Characteristics maintenance 1. SAP Menu → 2. Cross-Application Components → 3. Classification System → 4. Master Data → 6. Characteristics Class maintenance …→ 5. Classes Variants Menu Objects: Display single dependency 1. SAP Menu → 2. Logistics → 3. Central Functions → 4. Variant Configuration → 5.Dependency → 6. Single Dependency → 7. Display Change single dependency …→ 7. Change Create single dependency … → 7. Create ©SAP AG PLM146 11-298 Activities Menu Path Variants Menu Objects (Continued): Modeling environment Variant configuration -> 1. SAP Menu → 2. Logistics → 3. Central Functions → 4. Variant Configuration → 5. Modeling Environment for Variant Configuration Display constraints and constraint nets 1. SAP Menu → 2. Logistics → 3. Central Functions → 4. Variant Configuration → 5. Dependency → 6. Dependency Net → 7. Display Change constraints and constraint nets …→ 7. Change Create constraints and constraint nets … → 7. Create Display configuration profile 1. SAP Menu → 2. Logistics → 3. Central Functions → 4. Variant Configuration → 5. Configuration Profile → 6. Display Change configuration profile …→ 6. Change Create configuration profile … → 6. Create Display variant table structure 1. SAP Menu → 2. Logistics → 3. Central Functions → 4. Variant Configuration → 5. Tools → 6. Table Structure → 7. Display Change variant table structure …→ 7. Change Create variant table structure … → 7. Create Maintain variant table contents 1. SAP Menu → 2. Logistics → 3. Central Functions → 4. Variant Configuration → 5. Tools → 6. Table Contents → 7. Maintain Transfer variant table contents → database table 1. SAP Menu → 2. Logistics → 3. Central Functions → 4. Variant Configuration → 5. Tools → 6. Table Contents → 7. Transfer to Database Table Create pricing conditions 1. SAP Menu → 2. Logistics → 3. Central Functions → 4. Variant Configuration → 5. Environment → 6. Pricing → 7. Create Condition Change pricing conditions …→ 7. Change Condition Display pricing conditions … → 7. Display Condition ©SAP AG PLM146 11-299 Activities Menu Path Maintain order BOM (variant configuration) 1. SAP Menu → 2. Logistics → 3. Production → 4. Master Data → 5. Bills of Material → 6. Bill of Material → 7. Order BOM → 8. Maintain (Multilevel) Display order BOM … → 8. Display (Multilevel) ABAP Workbench ABAP Dictionary 1. SAP Menu → 2. Tools → 3. ABAP Workbench → 4. Development → 5. ABAP Dictionary Data Browser 1. SAP Menu → 2. Tools → 3. ABAP Workbench → 4. Overview → 5. Data Browser Sales Create sales order 1. SAP Menu → 2. Logistics → 3. Sales and Distribution → 4. Sales → 5. Order → 6. Create Change sales order …→ 6. Change Create sales order …→ 6. Create PP Material Requirements Planning Planning for sales order 1. SAP Menu → 2. Logistics → 3. Production → 4. MRP → 5. Planning → 6. Single-Item Planning, Sales Order Display stock/requirements list 1. SAP Menu → 2. Logistics → 3. Production → 4. MRP → 5. Evaluations → 6. Stock/Reqmts List ©SAP AG PLM146 12-300 © SAP AG 2002 ¤ Introduction to Modeling ¤ The Configurable Product ¤ Dependencies for the Configurable Product Contents: Appendix: Ideas for Modeling ©SAP AG PLM146 12-301 © SAP AG 2002 Appendix: Hints ¤ This material is not part of the standard course. ¤ This section contains additional material to give you ideas for modeling variants. ¤ Each customer i s different, so there are few general rules that will necessarily appl y to everyone. ¤ For this reason, this section contains only suggestions for setting up a variant model. ©SAP AG PLM146 12-302 © SAP AG 2002 Part 1: Introduction to Modeling Introduction to Modeling Introduction to Modeling ©SAP AG PLM146 12-303 © SAP AG 2002 Configurable material, (300) class, Characteristics Dependencies Configurable Configurable material, material, (300) class, (300) class, Characteristics Characteristics Dependencies Dependencies SD Conditions SD SD Conditions Conditions PP BOM Routing PP PP BOM BOM Routing Routing PS Network PS Network Configurable Object Dependencies PM Maint. ord. PM Maint. ord. SM MSS SM MSS Data Structure for Variants ©SAP AG PLM146 12-304 © SAP AG 2002 ¤ Define who is involved Þ Product manager Þ Design engineer Þ Work scheduler, and so on ¤ Execution Þ Knowledge Acquisition Þ Implementation Þ Testing Introduction to Variant Configuration ©SAP AG PLM146 12-305 © SAP AG 2002 Central group: Product manager Design engineer Sales Production Project production The data structure determines the team structure Plant maintenance Service management Who is Involved Configurable material, (300) class, Characteristics Dependencies Configurable Configurable material, material, (300) class, (300) class, Characteristics Characteristics Dependencies Dependencies SD Conditions SD SD Conditions Conditions PP BOM Routing PP PP BOM BOM Routing Routing PS Network PS Network Dependencies PM Maint. ord. PM Maint. ord. SM MSS SM MSS ©SAP AG PLM146 12-306 © SAP AG 2002 ¤ Task of the central group Þ Product identification Þ Characteristics and characteristic values Þ Central dependencies ¤ Preparatory work in departments Þ Collecting and setting up data Þ General, non-product-specific data, for example, that pricing always depends on customer plus material ¤ As soon as the central group has finished, the departments model according to central specifications Procedure ©SAP AG PLM146 12-307 © SAP AG 2002 ¤ Sources Þ Sales catalog, technical documentation Þ Legacy configurator Þ New product structure ¤ Viewpoints Þ New structure or 1:1 copy of existing structures Þ Reengineering ¤ The target structure must be the focus Knowledge Acquisition ©SAP AG PLM146 12-308 © SAP AG 2002 ¤ Highlight objects in red Þ Objects such as products, bills of material, and task lists, depending on what you are currentl y working on ¤ Highlight attributes in yellow Þ Attributes are often described with adjectives in continuous prose, such as large, or colored ¤ Highlight configuration knowledge in green Þ Configuration knowledge is often present in the form of flow diagrams or descriptions, such as " Whenever… then…" Working with Knowledge Sources ©SAP AG PLM146 12-309 © SAP AG 2002 ¤ The data structure determines the order in which you set up a configurable product. ¤ A project group for model ing configurable products comprises a central, interdepartmental group, plus groups in the departments. ¤ The central project group defines important structures for all departments. ¤ Sources for knowledge acquisition must be processed methodically before they are formalized. Part 1: Topic Summary ©SAP AG PLM146 12-310 © SAP AG 2002 Part 2: The Configurable Product The Configurable Product The Configurable Product ©SAP AG PLM146 12-311 © SAP AG 2002 ¤ Identifying Configurable Products Þ Name components from the customer viewpoint, if the product is multilevel ¤ Define variables ¤ Restrict variables Þ " You can onl y select this option if ... " Knowledge on a Configurable Product ©SAP AG PLM146 12-312 © SAP AG 2002 ¤ What is a product and what are its variants? Þ One product with millions of variants? Þ Millions of products without variants? Þ A middle way? ¤ Is a product single-level or multilevel? Þ Several products are logically related ¤ Viewpoint and language of customer are always decisive Identifying Configurable Products ©SAP AG PLM146 12-313 © SAP AG 2002 ¤ The customer sees the product as multilevel Þ Product comprises many logicall y related units Þ Example: standing closet and wall closet with the same finish ¤ The same component is configured in different ways Þ One product on the top level does not accuratel y represent a configuration Þ Example: several standing closets, each with a different number of drawers => can onl y be determined for each closet separatel y, not for the entire kitchen Multilevel Configuration Only If... Þ Check carefully whether multilevel configuration is necessary for your application. º In many cases, it is sufficient to include a configurable material in the BOM without configuring it separately. The BOM and routing of the configurable material are determined from the configuration of the header material. Þ Multilevel configuration can be useful if you require an order BOM for certain components, but you always want to configure others dynamically. ©SAP AG PLM146 12-314 © SAP AG 2002 Modeling Questions for Multilevel Models ¤ How many product levels (= BOM levels)? Þ The fewer the better. Ideall y: onl y use one level. Þ Customer must be able to understand the structure. ¤ Product levels to match BOM levels? Þ Can be mapped separatel y ¤ Which characteristics on which level? Þ As general as possible => Characteristics on top level Þ As specific as necessary => Characteristics at component level ©SAP AG PLM146 12-315 © SAP AG 2002 Separate Structures for Product and Production ¤ Customer viewpoint differs from production viewpoint Þ Kitchen example: production onl y looks at the individual closets. The closets are assembled to make a kitchen at the customer's premises. The " kitchen" level is not relevant to production. ¤ Possible scenarios Þ Individual components different in production => Define BOM items as relevant to sales Þ Sales and production use different structures => Separate BOMs for sales Þ Header material not relevant to production => Transfer requirements at component level ¤ This section looks at the product structure onl y ©SAP AG PLM146 12-316 © SAP AG 2002 Product Modeling Task 1 ¤ Identify your products Þ Use the terms highlighted in red in your knowledge sources ¤ Decide for each product whether it must be multilevel Þ How is the product described in the sales catalog? ¤ If multilevel: list the components Þ Make a graphic of the product hierarchy red ©SAP AG PLM146 12-317 © SAP AG 2002 Use of Groups ¤ If you maintain your data directly in SAP R/3, create groups in Customizing for: Þ Materials (discuss with your project section leader first) Þ Characteristics Þ Classes Þ Dependencies (procedures for pricing in SAP_PRICING) ¤ Create a separate group for each product Þ Use the same group name for different types of master data for the same product ©SAP AG PLM146 12-318 © SAP AG 2002 Define Characteristics ¤ Characteristics are configuration parameters from the customer viewpoint ¤ Characteristics must reflect the customer's terminology Þ Characteristics and their values are printed in the order confirmation Þ Consider using language-independent terminology for your characteristics and values ¤ Characteristics must describe a product in its entirety Þ From the viewpoint of sales, production, purchasing, plant maintenance, and so on ©SAP AG PLM146 12-319 © SAP AG 2002 Working with Organizational Areas ¤ Organizational areas let you show only certain characteristics, depending on the task at hand Þ Not all characteristics are relevant to all steps of order processing Þ Example: You do not need the color in a quotation, but you do in a sales order => Separate organizational areas for quotation and sales order ¤ For each characteri stic, note the steps where it is not relevant ¤ Group together related steps in the process when you define organizational areas ©SAP AG PLM146 12-320 © SAP AG 2002 How Not to Define Characteristics (1) ¤ Two characteristics representing the same attribute Þ Example 1: one characteristic for brake horsepower, one for kilowatt Þ Example 2: one characteristic each for length, width, and area ¤ Characteristics on the wrong level of the hierarchy Þ Example: characteristic FINISH for each component of the kitchen, although all components have the same finish ©SAP AG PLM146 12-321 © SAP AG 2002 How Not to Define Characteristics (2) ¤ No reuse of characteristics Þ The same characteristic is created multiple times for different products Þ Example: the standing closet and the wall closet have the same finish, so there must be one characteristic for both products Þ Different allowed values or meanings collected in one characteristic Þ Example: the length of a ship and the length of a microprocessor must not be represented by the same characteristic ©SAP AG PLM146 12-322 © SAP AG 2002 Product Modeling Task 2 ¤ Identify your characteristics: Þ Use the terms highlighted in yellow in your knowledge sources Þ Enter the allowed values for each characteristic Þ Set up naming conventions for characteristics and their values, especiall y for language-independent keys ¤ Create a new page for each product Þ A new page for each component, too, if the structure is multilevel ¤ Start a new line: Þ For each characteristic. List details of the characteristic header. Þ For each characteristic value. yellow ©SAP AG PLM146 12-323 © SAP AG 2002 You could use a spreadsheet program to create a list. You could then create a batch-input program to transfer the data to SAP R/3. Name sc_width 60cm 80cm sc_opng L R Product: Standing closet Description Width Door opening Left Right Data type num [cm] char Single/multi-val. Single-value Single-value Opt./reqd Required Required Display onl y Example of Characteristics List ©SAP AG PLM146 12-324 © SAP AG 2002 Revision of the Product Structure ¤ After assigning characteristics, examine your product structure criticall y. Þ Which products must be grouped together as variants? Þ Which products must be broken down? ¤ Document your criteria for grouping together and breaking down products. ©SAP AG PLM146 12-325 © SAP AG 2002 Grouping Together and Breaking Down Products ¤ Quantitative criteria Þ Number of common characteristics Þ Number of common characteristic values Þ Common configuration logic (see next section) ¤ Qualitative criteria Þ Are products or characteristics essentiall y different? Þ Example: a mosquito is not an elephant, although both have long legs and a long nose Þ Does the customer understand why products are grouped together or broken down? ©SAP AG PLM146 12-326 © SAP AG 2002 Part 3: Dependencies Dependencies Dependencies ©SAP AG PLM146 12-327 © SAP AG 2002 Dependencies Can Be Assigned... ¤ At characteristic or characteristic value level: Þ Precondition Þ Selection condition Þ Action Þ Procedure ¤ At configuration profile level: Þ Action Þ Procedure Þ Constraint net ©SAP AG PLM146 12-328 © SAP AG 2002 Dependencies at Characteristic (Value) Level (1) ¤ Apply to all products that use the characteristic Þ If one dependency applies to many products, dependency maintenance involves less work Þ Exception: you assign the dependency to a characteristic for one class onl y ¤ The knowledge base is scattered among many characteristics Þ If a product has many complex dependencies, dependency maintenance involves more work Þ However, on the configuration screen, you can display the dependencies assigned to each characteristic and value ©SAP AG PLM146 12-329 © SAP AG 2002 Dependencies at Characteristic (Value) Level (2) ¤ You can maintain dependencies at characteristic (value) level only if you want to: Þ Hide characteristics Þ Hide characteristic values (except for restrictable characteristics) Þ Make optional characteristics into required characteristics ©SAP AG PLM146 12-330 © SAP AG 2002 Dependencies at Configuration Profile Level ¤ Apply to only one configuration profile Þ However, a dependency can be used in many configuration profiles Þ If the same dependencies must be repeatedl y assigned to many configuration profiles, dependency maintenance involves more work Þ Exception for constraints: you can group together many constraints in a constraint net and assign the net to many configuration profiles ¤ All of the dependenci es are assigned to one object Þ If a product has many complex dependencies, dependency maintenance involves less work ©SAP AG PLM146 12-331 © SAP AG 2002 Complex Dependencies ¤ To calculate a third characteristic value from two known characteristic values, it is best to assign the dependency to the configuration profile. Þ Example: Area = Length * Width ©SAP AG PLM146 12-332 © SAP AG 2002 Product Modeling Task 3 ¤ Set up your configuration knowledge: Þ Assign dependencies to products, characteristics, and values Þ Use the terms highlighted in green in your knowledge sources Þ Assign cross-characteristic dependencies to the product ¤ Extend your lists from Part 2 ¤ Create tables for more complex interdependencies green ©SAP AG PLM146 12-333 © SAP AG 2002 You could complete the tables from Part 2 by adding a column for configuration knowledge. Name sc_width 60cm 80cm sc_opng L R Product: Standing closet Description Width Door opening Left Right Data type num [cm] char . . . Condition IF Height > 180 IF Height < 160 Set doorknob installation point = 'Right' Set doorknob installation point = 'Left' Cross-characteristic: Standing closet only for "Blue Moon" range Example of Extended Lists ©SAP AG PLM146 12-334 © SAP AG 2002 Tables ¤ For each table, document: Þ Whether it onl y checks a value combination Þ Whether certain columns are used to calculate the values for others: mark these columns ¤ Assign the tables to the products ©SAP AG PLM146 12-335 © SAP AG 2002 Modeling Knowledge in the Bill of Material ¤ Classification knowledge Þ Class items Þ Individual classified objects ¤ Dependencies Þ Selection conditions Þ Procedures (actions) ¤ Configurable phantom assemblies ©SAP AG PLM146 12-336 © SAP AG 2002 When Do You Use Class Items? ¤ Objects classified in the class are: Þ Interchangeable Þ Large in number ¤ Selection: Þ Always follows the same scheme Þ Is logicall y simple - using AND relationships, for example 4 For more complex logical expressions, it can be useful to define a selection condition for the class item ©SAP AG PLM146 12-337 © SAP AG 2002 Advantages of Class Items ¤ Easier to maintain dependencies Þ Selection conditions for BOM items not needed Þ If there are changes, you need to maintain onl y the class Caution: these changes are at client level, but BOM changes are at plant level ¤ Better overview in the bill of material Þ One generic item instead of many material items Þ No need to search for dependencies in the BOM ©SAP AG PLM146 12-338 © SAP AG 2002 Fine-Tuning of Class Items ¤ Additional data screen of class Þ Check: required, optional, or multiple selection Þ Default values ¤ Dependencies for class item Þ Set characteristic values for finding objects in class Þ If characteristics do not appear directl y on configuration screen ¤ Manual search for objects in class during configuration ©SAP AG PLM146 12-339 © SAP AG 2002 Using Dependencies to Find Objects in Classes ¤ Dependencies set characteristic values for class Þ Used instead of assigning values directl y on the value assignment user interface Þ Dependencies are assigned to class item (not class) Þ You can use the following dependencies: Þ Procedures Þ (Actions) Þ Constraints (onl y if fixing the search result) ¤ Objects are found according to characteristic values Þ Dependencies link characteristics in the configuration to characteristics of classes in the BOM. Þ Multiple assignments are supported Þ Characteristics and values in the configuration can be totally different from those in the class Þ Without dependencies for the class item, the search for objects in the class uses: º Characteristics that occur in the configuration and in the class (same name) º The values assigned during configuration ©SAP AG PLM146 12-340 © SAP AG 2002 Manual Search for Objects in Configuration ¤ On the configuration screen, you can: Þ Choose Configuration structure to see an overview of the configurable objects and class items Þ Select a class item and start finding objects ¤ This is the easy way because: Þ No dependencies are required Þ Characteristics for finding objects need not be in the configuration ¤ You can use dependencies to check consistency Þ You can start finding objects in the class: º On the configuration screen º In the configuration result º In the order BOM Þ This is useful if the components can be selected directly by the user according to the classification. Advantages: º Very flexible º Least work for modeling Þ You can use constraints to check consistency. Example: º Objects: - (300) Computer where application =application, - (200) Processor where power =power º Condition: - application =screen_processing and power =low º Restriction: - false - * A computer for screen processing cannot work with - * a low-power processor. ©SAP AG PLM146 12-341 © SAP AG 2002 Classified Objects as BOM Items: Classification as a Selection Condition ¤ Instead of a class item, you can enter classified objects as BOM items Þ Materials can be assigned to a class or class type that is not defined for use in BOMs Þ Enter the class type on the item detail screen ¤ Entering classified objects as BOM items is useful if: Þ You want to avoid selecting from all objects classified in the class Þ You want to use existing classifications to avoid creating selection conditions => dependency maintenance involves less work ©SAP AG PLM146 12-342 © SAP AG 2002 Task for Class Items ¤ Take a printout of your bil l of material: Þ Highlight in color all the materials that could be defined in a class item Þ Write the number or name of a class for each class item ¤ For each class, create a list of: Þ Characteristics Þ Classified objects Þ Characteristic values for materials ¤ Set up a BOM containing the class items ©SAP AG PLM146 12-343 © SAP AG 2002 Define (if required) whether at least 1 object or at most 1 object must be selected Material No. hs_01 hs_02 hs_03 hs_04 hs_11 hs_12 hs_13 hs_14 Width 60 80 60 80 60 80 60 80 Height 180 180 200 200 180 180 200 200 Finish Oak Oak Oak Oak Beech Beech Beech Beech Class (300) Standing closet Example of Class List ©SAP AG PLM146 12-344 © SAP AG 2002 Dependencies in BOMs ¤ You can assign the following dependencies to a BOM item: Þ Selection conditions Þ Actions Þ Procedures ¤ You cannot assign dependencies to a BOM header Þ Processing of the entire BOM is limited to $SUM_PARTS and $COUNT_PARTS Þ Prerequisite: multilevel, interactive configuration Þ You cannot assign preconditions or constraint nets to a BOM item. º Preconditions do not make sense here, because they explain when the assigned object is not valid, but do not say when it is valid. With a BOM item, you need to be definite about exactly when it is selected. Þ Processing of the entire BOM is limited. It can be useful to calculate information such as the sum of all component weights and the frequency of components. You can use a constraint with $sum_parts or $count_parts for processes of limited scope. However, the user must configure the BOM interactively. ©SAP AG PLM146 12-345 © SAP AG 2002 Variable-Size Items and Actions ¤ Actions do not trigger recalculations in variable-size items Þ If an action overwrites the value or quantity of a size, this does not trigger recalculation in MRP Þ Workaround: use a procedure to calculate the actual quantity directl y ©SAP AG PLM146 12-346 © SAP AG 2002 Complex Dependencies ¤ SAP R/3 calculates a fact for each applicable dependency Þ System performance suffers if dependencies are very complex ¤ For this reason, it can be advisable to: Þ Break down complex expressions into more simple expressions Þ Use the simplified expressions multiple times Þ Avoid using local dependencies ©SAP AG PLM146 12-347 © SAP AG 2002 Differences Between Dependency Types ¤ Preconditions are conjunctive: Þ If logicall y related by AND, split up and assign separately Þ A precondition is a necessary condition (for a characteristic value, for example) ¤ Selection conditions are disjunctive: Þ If logicall y related by OR, split up and assign separatel y Þ A selection condition is a sufficient condition (for a BOM item, for example) ©SAP AG PLM146 12-348 © SAP AG 2002 24 preconditions create 24 facts a b c d a b c d a b c d a b c d 1 1 1 1 2 1 1 1 1 2 2 1 4 2 2 3 ∧ ∨ ∧ ∧ ∨ ∧ ∧ ∨ ∧ ∧ ∨ ∧ ( ) ( ) ( ) ... ( ) a a a a b c b c d d d 1 2 3 4 1 1 2 2 1 2 3 , , , , , , ∧ ∧ You can do the same with 9 preconditions. Simplifying Preconditions: Example ©SAP AG PLM146 12-349 © SAP AG 2002 Why Split Complex Expressions? ¤ System performance improves, because SAP R/3 needs to calculate fewer facts ¤ Dependency maintenance involves less work because: Þ Logical expressions are simpler (overview) Þ There are fewer dependencies ©SAP AG PLM146 12-350 © SAP AG 2002 Only Split Conditions If... ¤ It makes sense semantically Þ For example, due to different functional or logical background ¤ You want to improve: Þ System performance: the system needs to calculate fewer facts Þ Dependency maintenance: it is easier to see what is happening (for example, there are fewer dependencies and they are simpler) ¤ Resist the temptation to overdo it! ©SAP AG PLM146 12-351 © SAP AG 2002 Task for Improving Dependency Maintenance ¤ Create a list of all dependencies - for one product, for example ¤ Duplication: Þ Delete dependencies that have the same source code Þ Check local dependencies very carefull y ¤ Complex logical expressions: Þ Collect similar logical expressions Þ Check whether it makes sense to break them down