PLM140 Variant Configuration Part 1

PLM140 Variant Configuration 1 - Modeling mySAP Product Lifecycle Management

Date Training Center Instructors Education Website

Participant Handbook Course Version: 2003 Q3 Course Duration: 3 Day(s) Material Number: 50066289

An SAP course - use it to learn, reference it for work

Copyright Copyright © 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Trademarks •

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

•

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

•

ORACLE® is a registered trademark of ORACLE Corporation.

•

INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.

•

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

•

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

•

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

•

JAVA® is a registered trademark of Sun Microsystems, Inc.

•

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

•

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

Disclaimer THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal (in this documentation) and external (in other locations, such as SAPNet).

18-02-2004

Example text

Emphasized words or phrases in body text, titles of graphics, and tables

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example text

Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.



Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© 2004 SAP AG. All rights reserved.

iii

About This Handbook

PLM140

Icons in Body Text The following icons are used in this handbook. Icon

Meaning For more information, tips, or background Note or further explanation of previous point Exception or caution Procedures

Indicates that the item is displayed in the instructor’s presentation.

iv

© 2004 SAP AG. All rights reserved.

18-02-2004

Contents Course Overview ......................................................... vii Course Goals ...........................................................vii Course Objectives .....................................................vii

Unit 1: Variant Configuration............................................ 1 Overview of Variant Configuration ....................................2 Terms and Objects in Variant Configuration .........................6

Unit 2: Classification Tools for Variant Configuration........... 23 Characteristics Maintenance ........................................ 24 Class Maintenance ................................................... 39

Unit 3: Material Master, BOMs, and Task Lists .................... 57 Creating a Material Master Record ................................. 58 Maintaining a Super BOM ........................................... 71 Maintaining Task Lists ................................................ 85

Unit 4: Configuration Profiles ........................................ 103 Configuration Scenarios ............................................104

Unit 5: Object Dependencies......................................... 123 Types and Functions of Object Dependencies...................124 Creating Object Dependencies ....................................129 Tools for Working With Dependencies ............................138

Unit 6: Object Dependencies in BOMs and Task Lists ......... 147 Maintenance and Functions of Selection Conditions............148 Procedures for BOMs and Task Lists .............................169

Unit 7: Dependencies for Value Assignment ..................... 185 Preconditions and Selection Conditions ..........................186 Procedures for Value Assignment .................................204

Unit 8: Constraints ..................................................... 231 Creating Constraints.................................................232 Structure of a Constraint ............................................237

18-02-2004

© 2004 SAP AG. All rights reserved.

v

Contents

PLM140

Appendix 1:

........................................................... 267

Appendix 2: Recommended Follow-Up Courses and Activities ............................................................... 283 Appendix 3: Data in the Exercises

............................... 285

Index ....................................................................... 291

vi

© 2004 SAP AG. All rights reserved.

18-02-2004

Course Overview This course explains simple modeling tasks of variant configuration. It also explains the functions and features of variant configuration to evaluate and plan the use of variant configuration.

Target Audience This course is intended for the following audiences: • • •

Variant modelers for SAP R/3 Enterprise- Configurator and SAP IPC Sales Configuration Engine Project team Data processing organizers

Course Prerequisites Required Knowledge • • •

Overview course on product/life-cycle data management and document management (LO090/PLM100) Knowledge of characteristics and class maintenance, as covered by the course LO985/PLM130 Knowledge of master data for discrete manufacturing, at least to the extent covered by the course LO090/PLM100

Recommended Knowledge •

LO205/LO206 (PLM110/PLM111/PLM112), Basic Data Part 1 and Part 2, and Customizing

Course Goals This course will prepare you to: •

Model multi-variant products by building on your knowledge of variant configuration and examining its functions and handling in detail

Course Objectives After completing this course, you will be able to: •

18-02-2004

Perform simple modeling tasks of variant configuration

© 2004 SAP AG. All rights reserved.

vii

Course Overview

•

PLM140

Understand the functions and features of variant configuration to evaluate and plan its use

SAP Software Component Information The information in this course pertains to the following SAP Software Components and releases:

viii

© 2004 SAP AG. All rights reserved.

18-02-2004

Unit 1 Variant Configuration Unit Overview This unit describes the functions of individual variant configuration objects. It also explains how to identify the configurable object types and the basic applications of a complete configuration model.

Unit Objectives After completing this unit, you will be able to: • • •

Identify the functions of individual variant configuration objects Identify the configurable object types currently supported in SAP R/3 Enterprise Name the basic applications of a complete configuration model

Unit Contents Lesson: Overview of Variant Configuration.....................................2 Lesson: Terms and Objects in Variant Configuration..........................6 Exercise 1: Working With a Fully Modeled Configuration Task ....... 13

18-02-2004

© 2004 SAP AG. All rights reserved.

1

Unit 1: Variant Configuration

PLM140

Lesson: Overview of Variant Configuration Lesson Overview This lesson introduces variant configuration and how to identify the different functions of individual variant configuration objects.

Lesson Objectives After completing this lesson, you will be able to: •

Identify the functions of individual variant configuration objects

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company wants to optimize its inventories and the storage costs and maintain every possible end-product variant. The senior management of the company decides to use SAP R/3 Enterprise for this purpose. As the Product Manager of the company, you need to identify the functions and uses of variant configuration.

Variant Configuration - Process Flow

Figure 1: From Customer Inquiry to Order Confirmation

Variant configuration in SAP R/3 Enterprise lets you check the following as soon as you create a sales order:

2

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Overview of Variant Configuration

Whether the required variant can be produced. Only variants that are technically possible can be ordered. What price you can quote for the product. Whether the customer’s specifications can be covered from stock. And so on.

Knowledge Base for Materials

Figure 2: Variant Configuration Knowledge Base for Materials

The following objects make up the knowledge base of a configured material: The material master is where the configurable attribute is defined along with some additional planning and control data. Characteristics and values must be created and collected in variant classes (class type 300) in classification functions. The configuration profile contains control data for the configuration process and result. A super BOM must be created which contains all standard components and all possible variable components and assemblies that are required to configure a variant product. A super task list must be created that includes all operations, suboperations, sequences, and Production Resources and Tools (PRTs) that are required to manufacture all possible variants.

18-02-2004

© 2004 SAP AG. All rights reserved.

3

Unit 1: Variant Configuration

PLM140

Pricing condition records must be created for pricing the configurable material. There are five different types of object dependencies that can be used during the configuration process. Dependencies provide the rules or logic for the configuration process. Certain industry sectors, such as aerospace and defense, automotive, make-to-order, assemble-to-order, and hi-tech, use configurable materials.

4

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Overview of Variant Configuration

Lesson Summary You should now be able to: • Identify the functions of individual variant configuration objects

18-02-2004

© 2004 SAP AG. All rights reserved.

5

Unit 1: Variant Configuration

PLM140

Lesson: Terms and Objects in Variant Configuration Lesson Overview This lesson describes configurable object types, class, characteristics, BOM, super BOM, and routing.

Lesson Objectives After completing this lesson, you will be able to: • •

Identify the configurable object types currently supported in SAP R/3 Enterprise Name the basic applications of a complete configuration model

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company decided to use SAP R/3 Enterprise to optimize its storage inventories and maintain possible end-product variant. As the Product Manager of the company, you need to identify the configurable object types in the storage inventories and the basic applications of a complete configuration model.

Configurable Objects

Figure 3: Configurable PC

6

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Terms and Objects in Variant Configuration

Products with a number of features and options have a large range of possible variants. Without restrictions, the example shown can produce 311040 variants. In practice, there are restrictions in the form of rules that reduce the number of possible options. These rules must be defined and applied during the configuration process. Complex products are reflected in complex configuration tasks for sales and production. However, a company that sells or produces products with variants needs to perform these tasks quickly and accurately. As the development cycles and life cycles of products become short, this becomes difficult. How many sets of data must be created and maintained if SAP R/3 Enterprise variant configuration is not used? In the example above, up to 23, 328 material masters, BOMs, task lists, costing records, and pricing records must be created and maintained if SAP R/3 Enterprise variant configuration is not used. “Configurable product“ is the general term for a product that has a large number of variants. The features used to create complex products are stored in SAP R/3 Enterprise as characteristics and values.

Figure 4: Configurable Product, Class, Class Type

A configurable material needs a material master record to: • •

Store important planning and control data Link the product to other objects in the variant configuration data model by assigning it to a variant class

In variant configuration, a variant class groups together the characteristics that describe a configurable material.

18-02-2004

© 2004 SAP AG. All rights reserved.

7

Unit 1: Variant Configuration

PLM140

You can only use variant classes or class nodes to group together characteristics for this purpose. The class type of a class determines whether or not the class is a variant class or a class node. In the standard system, only classes of class type 300 are variant classes. Classes of class type 200 are class items or class nodes. While Customizing for classification, you can define class types – including class types for variant classes.

Figure 5: Configurable Product, Class, Characteristics

You can define the features of a product in SAP R/3 Enterprise by defining characteristics. You can also define values for each characteristic and use these values to describe the customer’s requirements. You can assign the characteristics of your configurable product to the variant class. The configurable material is assigned to the variant class. When you assign the configurable material to the class, you enable configuration by using the characteristics of the class.

8

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Terms and Objects in Variant Configuration

Figure 6: Super BOM of PC

You can use the BOM to define which parts can be used in a configurable material. You can also create a super BOM for the configurable material, which contains parts that might be used in specific variants or variable parts and parts required in variants or non-variable parts. This BOM can contain items that are configurable materials (multilevel configuration).

Figure 7: Bill of Material for PC

You can use preconditions to check the consistency of the assigned values. This ensures that only valid combinations of values appear and are selected in configuration. You can also use selection conditions to determine that a specific BOM item and operation is selected if a certain value is assigned to it. This determines which casing, CPU, and extras must be selected.

18-02-2004

© 2004 SAP AG. All rights reserved.

9

Unit 1: Variant Configuration

PLM140

Routing of a Configurable Material

Figure 8: Routing for PC

The routing of a configurable material: • • • •

Has one standard sequence Might have one or more parallel and alternative sequences Comprises operations, which can have suboperations Might have Production Resources/Tools (PRTs) assigned to operations or suboperations

You can use object dependencies to determine which sequences, besides the standard sequence, operations, suboperations, and PRTs are required for each variant, and whether or not they are used in this form.

10

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Terms and Objects in Variant Configuration

Interdependencies Between Objects in the Configuration Model

Figure 9: Interdependencies Between Objects in the Model (12)

Other Configurable Objects

Figure 10: Other Configurable Object Types

18-02-2004

© 2004 SAP AG. All rights reserved.

11

Unit 1: Variant Configuration

12

PLM140

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Terms and Objects in Variant Configuration

Exercise 1: Working With a Fully Modeled Configuration Task Exercise Objectives After completing this exercise, you will be able to: • Create a sales order and work in the configuration environment with a modeled configurable material

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company has decided to use SAP R/3 Enterprise to optimize its storage inventories so that it could maintain every possible end-product variant. As the Product Manager of the company, you have modeled the configuration tasks for the PCs. Now, you need to test the result.

Task: Create a sales order for configurable material T-VPC99. Familiarize yourself with the views and functionality of the configuration user interface. 1.

Create a sales order with the following data: Order Type: OR Sales Organization: 1000 Distribution Channel: 10 Division: 00 Sold-to Party: 1000 Purchase order (PO) Number (Your choice) Material: T-VPC99 Order quantity: 1 You see the Characteristic Value Assignment screen.

2.

Assign values to characteristics from the allowed values of each characteristic. Use the F4 help.

3.

What are the allowed values offered for the hard disk if the fast CPU is selected?

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

13

Unit 1: Variant Configuration

PLM140

4.

What are the allowed values offered for the hard disk if the standard CPU is selected?

5.

Can you change the CD ROM value?

6.

Display the assigned values as a print list.

7.

Display the object dependencies.

8.

Run pricing, if a button is available for this purpose. Display the pricing conditions.

9.

Return to the entry screen of the sales order. How many items are there? What is the net value? What are the value-dependent surcharges? What is the gross value? Exit the sales order without saving.

14

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Terms and Objects in Variant Configuration

Solution 1: Working With a Fully Modeled Configuration Task Task: Create a sales order for configurable material T-VPC99. Familiarize yourself with the views and functionality of the configuration user interface. 1.

Create a sales order with the following data: Order Type: OR Sales Organization: 1000 Distribution Channel: 10 Division: 00 Sold-to Party: 1000 Purchase order (PO) Number (Your choice) Material: T-VPC99 Order quantity: 1

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

15

Unit 1: Variant Configuration

PLM140

You see the Characteristic Value Assignment screen. a)

Create a sales order for configurable material T-VPC99: Transaction VA01 Add this to your favorites (cursor on Favorites, right-hand mouse button, then “Insert Transaction“) SAP Menu → Logistics → Sales and Distribution → Sales → Order → Create Sales order with the following parameters: Order Type: OR Sales Organization: 1000 Distribution Channel: 10 Division: 00 (Enter) Sold-to Party: 1000 Ship-to party if prompted: 1000 Purchase order (PO) number (Your choice) Material:T-VPC99 Order quantity: 1 (Enter)

2.

Assign values to characteristics from the allowed values of each characteristic. Use the F4 help. a)

3.

What are the allowed values offered for the hard disk if the fast CPU is selected? a)

4.

All four hard disks

What are the allowed values offered for the hard disk if the standard CPU is selected? a)

5.

Assign values to the characteristics. Use the F4 help = double-click.

Only the standard and medium hard disks

Can you change the CD ROM value? a)

No, this value was set by a procedure and cannot be changed. CD ROM is set when you assign a value to Multimedia. If you try to overwrite this value, you see a Conflict dialog box. Display the explanation of the value on the value assignment screen = blue “I“ button. Continued on next page

16

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Terms and Objects in Variant Configuration

6.

Display the assigned values as a print list. a)

7.

Assigned values as print list. (List button)

Display the object dependencies. a)

Display the object dependencies (green double-arrow button). For example: Software, F4 help for values of hard disk F4 help

8.

Run pricing, if a button is available for this purpose. Display the pricing conditions. a)

Display the pricing conditions. (Pushbutton in net value block. Run pricing first if required = Button.)

9.

Return to the entry screen of the sales order. How many items are there? What is the net value? What are the value-dependent surcharges? What is the gross value? Exit the sales order without saving. a)

Return to the entry screen of the sales order (green arrow button). How many items are there? One What is the net value? (Button: 5 Euro each) Varies, depending on the values selected or assigned by object dependencies. (Example: Basic price 700 Euro + 10 Euro for each GB of hard disk + 80 Euro for minitower + 120 Euro for tower What are the value-dependent surcharges? Varies, depending on the values selected or assigned by object dependencies. What is the gross value? Varies, depending on the values selected or assigned by object dependencies. Exit the sales order without saving.

18-02-2004

© 2004 SAP AG. All rights reserved.

17

Unit 1: Variant Configuration

PLM140

Lesson Summary You should now be able to: • Identify the configurable object types currently supported in SAP R/3 Enterprise • Name the basic applications of a complete configuration model

18

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Unit Summary

Unit Summary You should now be able to: • Identify the functions of individual variant configuration objects • Identify the configurable object types currently supported in SAP R/3 Enterprise • Name the basic applications of a complete configuration model

18-02-2004

© 2004 SAP AG. All rights reserved.

19

Unit Summary

20

PLM140

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Test Your Knowledge

Test Your Knowledge 1.

Which of the following are true for variant configuration? Choose the correct answer(s).

2.

□

A

□

B

□

C

□

D

The material master contains control data for the configuration process and result. Characteristics and values must be created and collected in variant classes (class type 300) in classification functions. In the configuration profile, the configurable attribute is defined along with some additional planning and control data. Pricing condition records must be created for pricing the configurable material.

The features that are used to create complex products are stored in SAP R/3 Enterprise as and . Fill in the blanks to complete the sentence.

3.

Which statements are true for routing of a configurable material? Choose the correct answer(s).

18-02-2004

□

A

□

B

□

C

□

D

Routing of a configurable material has many standard sequences. Routing of a configurable material can have only one alternative sequence. Routing of a configurable material comprises operations that can have suboperations. Routing of a configurable material can have Production Resources/Tools (PRTs) assigned to operations or suboperations.

© 2004 SAP AG. All rights reserved.

21

Test Your Knowledge

PLM140

Answers 1.

Which of the following are true for variant configuration? Answer: B, D In the material master, the configurable attribute is defined along with some additional planning and control data. Also, the configuration profile contains control data for the configuration process and result.

2.

The features that are used to create complex products are stored in SAP R/3 Enterprise as characteristics and values. Answer: characteristics, values

3.

Which statements are true for routing of a configurable material? Answer: C, D Routing of a configurable material has one standard sequence. Also, routing of a configurable material can have one or more parallel and alternative sequences.

22

© 2004 SAP AG. All rights reserved.

18-02-2004

Unit 2 Classification Tools for Variant Configuration Unit Overview This unit explains the various classification tools available for variant configuration. It also explains how to maintain characteristics and classes in variant configuration.

Unit Objectives After completing this unit, you will be able to: • • • • • •

Maintain characteristics Identify the special features of characteristics maintenance for variant configuration Create characteristics with reference to master data fields Create variant classes and class nodes Assign objects to classes and find objects in classes Identify the special features of class maintenance for variant configuration

Unit Contents Lesson: Characteristics Maintenance ......................................... 24 Exercise 2: Characteristics Maintenance ................................ 33 Lesson: Class Maintenance .................................................... 39 Exercise 3: Class Maintenance ........................................... 47

18-02-2004

© 2004 SAP AG. All rights reserved.

23

Unit 2: Classification Tools for Variant Configuration

PLM140

Lesson: Characteristics Maintenance Lesson Overview This lesson explains how to create and maintain characteristics. It also identifies the special features of characteristics maintenance.

Lesson Objectives After completing this lesson, you will be able to: • • •

Maintain characteristics Identify the special features of characteristics maintenance for variant configuration Create characteristics with reference to master data fields

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. To maintain every possible end-product variant, the company has decided to implement SAP R/3 Enterprise variant configuration solution. The basic foundation for this solution rests in SAP R/3 Enterprise classification. As the Product Manager of the company, you need to define characteristics, their values, and assign these characteristics to classes.

24

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Characteristics Maintenance

Introduction to Characteristics

Figure 11: Variant Configuration Knowledge Base for Materials

Characteristics and values and at least one variant class (class type 300) must be created in SAP R/3 Enterprise classification.

Figure 12: Screens: Characteristics

Naming conventions Letters, figures, underscores, and hyphens Characteristic names must start with a letter.

18-02-2004

© 2004 SAP AG. All rights reserved.

25

Unit 2: Classification Tools for Variant Configuration

PLM140

Characteristic names with a hyphen require the use of a keyword when used in dependencies. 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 “EXTERNAL-COLOR“. You can rename characteristics, provided that they are not addressed in dependencies. Technically, they are stored under an internal number.

Figure 13: Characteristic Status

You can define additional statuses in Customizing for classification, if required. You can also change existing statuses. The standard settings are shown.

26

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Characteristics Maintenance

Entry and Format of Characteristics

Figure 14: Entry/Format

Exponent 0: No exponent 1: Standard 1, ... E-xx 2: Predefined exponent 0, ... E- (enter exponent) 3: Scientific ---,-- E-xx Formats DATE, TIME, and CURR cannot be used in variant configuration. You use the Entry Required indicator to define whether it is mandatory to assign a value to a characteristic. If a characteristic is not yet used in a class, you can change the data type and the format data of a characteristic.

18-02-2004

© 2004 SAP AG. All rights reserved.

27

Unit 2: Classification Tools for Variant Configuration

PLM140

Figure 15: Allowed Values – Value Assignment Type for Characteristics

Intervals can be restricted, unrestricted, closed, half open, or open. For example: 100 - 200 , >100 , 100 - Select views: Basic Data 1, 2 Classification Sales Organization Data 1, 2 Sales Plant Data MRP 1, 2, 3, 4 Work Scheduling Costing 1, 2 Indicator “Create views selected“ Save as default values → Enter => Organizational levels: Plant 1200 Sales organization 1000 Distribution channel 10 Save as default values → Enter Enter data as shown in the exercise. Note: Only assign the material to your variant class – do not assign any characteristic values. From the classification view, choose Continue to go to the next step.

2.

Create T-VPZ## with Industry Sector M and material type KMAT.

→ Use your PC, T-VPC## as a template to copy from. Continued on next page

68

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Creating a Material Master Record

Do not maintain any classification view. Plant 1200 Sales Organization 1000 Distribution Channel 10 Maintain the following views for material T-VPZ##: Basic Data 1, 2 Sales Organization Data 1, 2 Sales Plant Data MRP 1, 2, 3, 4 Work Scheduling Costing 1, 2 For material T-VPZ##, use the same data as for T-VPC##, but without a classification view and with a new description: A different Description: Extras for PC (Group ##) a)

Create with template: MMK1 Material: T-VPZ## Industry Sector: M = Mechanical Engineering Copy from ... Material: T-VPC##!!! → Enter => Select views:No classification, but otherwise as above. → Enter => Organizational levels: Fill out Copy from column !!! Plant 1200 Sales organization 1000 Distribution channel 10 Save as default values → Enter Enter data as shown in the exercise: in other words, only change: - Description - No class assignment (if it has been copied, delete it)

18-02-2004

© 2004 SAP AG. All rights reserved.

69

Unit 3: Material Master, BOMs, and Task Lists

PLM140

Lesson Summary You should now be able to: • Create a material master record, including control parameters for sales and Material Requirements Planning (MRP)

70

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintaining a Super BOM

Lesson: Maintaining a Super BOM Lesson Overview This lesson explains how to maintain a super Bill of Material with class items and configurable assemblies.

Lesson Objectives After completing this lesson, you will be able to: •

Maintain a super BOM without dependencies with class items and configurable assemblies

Business Example ABC Motors is an automobile manufacturing company that manufactures various models of cars. The company is implementing variant configuration solution to maintain all the possible end-product variants. You are the Product Manager of the company. To implement variant configuration solution, you have created the material master record. Now, you need to create the bill of material.

Overview of BOM

Figure 32: Super BOM

Definition: Bill of Material A bill of material is a formally structured list for an object, and contains all the related objects, their description, their quantity, and their unit.

18-02-2004

© 2004 SAP AG. All rights reserved.

71

Unit 3: Material Master, BOMs, and Task Lists

PLM140

The BOM of a configurable material contains all the parts that are required for all possible variants of the material. Object dependencies are used to configure the BOM: only the parts that are required for a specific variant are selected. The BOM is exploded according to the characteristic values assigned. You can also make manual changes to the BOM for a sales order, provided that the settings in the configuration profile allow this. You can, for example, delete or insert components. The BOM is then saved as an order BOM for the sales order. You can change the BOM in the production order, as in production without variants.

Items in BOM

Figure 33: Class Item - Item Category K

You can enter a class in which materials or documents are classified as an item in a BOM. The class must have a class type that allows it to be used as a BOM item. In the standard system, you can use classes of class type 200, for materials, and class type 201, for documents, as class items. Only these two object types can be selected via a class item. When you assign characteristic values in configuration functions, the class is replaced by a material or a document.

72

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintaining a Super BOM

Figure 34: Non-Stock Item - Item Category N

You can create non-stock items both with and without a material master record. If you enter a non-stock item without entering a material number, you must enter a descriptive text and procurement data. You enter the purchasing data for non-stock items with or without a material number, except materials with material type KMAT. The system uses the pricing data to determine the release strategy. The material group is required for generating a purchase requisition. The component is procured directly for the production order. Purchase requisitions are created automatically. A non-stock item can also be a configurable material. In this example the EXTRAS is a place holder that contains the three components as pictured. The EXTRAS are selected when the sales order is configured, and must have the appropriate object dependencies.

18-02-2004

© 2004 SAP AG. All rights reserved.

73

Unit 3: Material Master, BOMs, and Task Lists

PLM140

Figure 35: Variable-Size Item - Item Category R

If you want to use one material number to represent different-sized pieces of a material, you assign the item category R. On the Variable-Size Item Data detail screen, the system uses the sizes and formula you enter to immediately calculate the variable-size item quantity required. Material requirements can be determined directly from the BOM explosion, without having to perform additional steps first. You do not need to maintain a separate material master record for each section of the material that is cut to size. Variable-size items are useful in variant configuration because you can use dependencies with reference characteristics to maintain variable-size item data.

74

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintaining a Super BOM

Exercise 5: BOM Maintenance (Without Dependencies) Exercise Objectives After completing this exercise, you will be able to: • Maintain super BOMs for configurable materials

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company has decided to use SAP R/3 Enterprise to optimize its storage inventories and maintain every possible end-product variant. You are the Product Manager of the company. To model the PC and other configurable materials, you must create the super BOM. The BOM for the PC has multiple levels, so you need to create several BOMs in the system.

Task: Create the two BOMs. 1.

Create the two BOMs as shown: in “PC - Customer Example (BOM Structure)“ Create the BOMs in: Plant: 1200 and with: Usage: Production = 1 The materials you require are in the following table. All items are stock items, except for T-VPZ## and the class node for Colors. All items have quantity 1. Which item categories do the two items that are not stock items have? You may want to copy from: T-VPC00 1200 1 and T-VPZ00 1200 1, if you copy ask your instructor for details.

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

75

Unit 3: Material Master, BOMs, and Task Lists

PLM140

Description

Material Number

Configurable Personal Computer

T-VPC## T-PCS

Bolt set T-PC21 Casing Tower T-PC22 Casing Minitower T-PC23 Casing Desktop T-CPU-1 CPU, Standard T-CPU-2 CPU, Medium T-CPU-3 CPU, Fast (200) Class Node for Color T_VPC_COLOR Hard disk, small T-DISK-1 Hard disk, medium T-DISK-2 Hard disk, large T-DISK-3 Hard disk, extra large T-DISK-4 MS Access T-SW-10 MS Word T-SW-40 MS Excel T-SW-20 MS Office Package T-SW-30 CD drive, slow T-CD-1 CD drive, medium T-CD-2 CD drive, fast T-CD-3 Speaker Set (2), 10 Watt T-SPEAKER-10 Speaker Set (2), 15 Watt T-SPEAKER-15 Speaker Set (2), 40 Watt T-SPEAKER-40

76

Extras for PC (Group ##)

© 2004 SAP AG. All rights reserved.

T-VPZ##

18-02-2004

Continued on next page

PLM140

18-02-2004

Lesson: Maintaining a Super BOM

Configurable Extras for PC

T-VPZ##

Standard Keyboard

DPC1009

Mouse - Model: Standard

T-PZ1

Modem 56600 bps

DPC9026

© 2004 SAP AG. All rights reserved.

77

Unit 3: Material Master, BOMs, and Task Lists

PLM140

Solution 5: BOM Maintenance (Without Dependencies) Task: Create the two BOMs. 1.

Create the two BOMs as shown: in “PC - Customer Example (BOM Structure)“ Create the BOMs in: Plant: 1200 and with: Usage: Production = 1 The materials you require are in the following table. All items are stock items, except for T-VPZ## and the class node for Colors. All items have quantity 1. Which item categories do the two items that are not stock items have? You may want to copy from: T-VPC00 1200 1 and T-VPZ00 1200 1, if you copy ask your instructor for details.

Continued on next page

78

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintaining a Super BOM

Description

Material Number

Configurable Personal Computer

T-VPC## T-PCS

Bolt set T-PC21 Casing Tower T-PC22 Casing Minitower T-PC23 Casing Desktop T-CPU-1 CPU, Standard T-CPU-2 CPU, Medium T-CPU-3 CPU, Fast (200) Class Node for Color T_VPC_COLOR Hard disk, small T-DISK-1 Hard disk, medium T-DISK-2 Hard disk, large T-DISK-3 Hard disk, extra large T-DISK-4 MS Access T-SW-10 MS Word T-SW-40 MS Excel T-SW-20 MS Office Package T-SW-30 CD drive, slow T-CD-1 CD drive, medium T-CD-2 CD drive, fast T-CD-3 Speaker Set (2), 10 Watt T-SPEAKER-10 Speaker Set (2), 15 Watt T-SPEAKER-15 Speaker Set (2), 40 Watt T-SPEAKER-40 18-02-2004

Extras for PC (Group ##)

© 2004 SAP AG. All rights reserved. T-VPZ##

79 Continued on next page

Unit 3: Material Master, BOMs, and Task Lists

PLM140

Configurable Extras for PC

T-VPZ##

Standard Keyboard

DPC1009

Mouse - Model: Standard

T-PZ1

Modem 56600 bps

DPC9026

a)

Create a bill of material: Option 1: (without template): CS01= SAP Menu → Logistics → Production → Master Data → Bills of Material → Bill of Material → Material BOM → Create or User Menu → Bill of Material → Material BOM → Create Material: T-VPC## Plant: 1200 BOM Usage: 1 = Production Enter items according to the list. Bill of Material 2: CS01 Material: T-VPZ## Plant: 1200 BOM Usage: 1 = Production Enter items according to the list. Option 2: (with template, without engineering workbench): CS01 Material: T-VPC## Plant: 1200 BOM Usage: 1 = Production Do not choose Enter. Choose Copy from = F7 Continued on next page

80

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintaining a Super BOM

=> Copy from Material: T-VPC00 Plant: 1200 BOM Usage: 1 = Production

→ Enter → Select all = Ctrl + F3 → Copy = F5 Change item 90 to T-VPZ##. 2. Copy bill of material T-VPZ00 to T-VPZ## in the same way. CS01 Material: T-VPZ## Plant: 1200 BOM Usage: 1 = Production Enter items according to the list. 3. Option 2: (With template, with engineering workbench): CEWB = SAP Menu → Logistics → Production → Master Data → Engineering Workbench or User Menu → Engineering Workbench => Select EWB working area: S_ALLES Focus BOM Header - All

→ Enter Pushbutton: Additional Selection Criteria Tab page: BOM Header Material: T-VPC00 and T-VPZ00 Use multiple selection and copy. Plant: 1200

→ Execute: Load BOMs and Task Lists => BOM Headers Overview Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

81

Unit 3: Material Master, BOMs, and Task Lists

PLM140

Use the pushbutton Set/Reset Data in Context to reset the context area. Select the line containing T-VPC00. → Copy = Shift + F11 => Dialog box: EWB: Process Using → Enter => Dialog box: EWB: Copy - Target Data T-VPC##1200 1 Set ’Multilevel Copy’ indicator

→ Copy Range Here, select: - All indicators for routings - Component Assignment - All indicators for bills of material - No object dependencies and no classification Execute = F8 Copy = F8 Select new line only.

→ Bills of Material → Items Overwrite extras with a separate material T-VPZ##. (You may want to check the routing:

→ Task Lists → Headers=> Two headers → Task Lists → Operations=> Operations for first task list with dependencies, for second task list without dependencies.

→ Bills of Material → BOM Headers Use the pushbutton Set/Reset Data in Context to reset the context area. Select the line containing T-VPZ00 only: Copy = Shift + F11 => Dialog box: EWB: Process Using → Enter => Dialog box: EWB: Copy - Target Data T-VPZ## 1200 1 Set indicator “Multilevel copy“ Copy Range Select: -All indicators for BOMs only Continued on next page

82

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintaining a Super BOM

-No object dependencies and no classification -No Component Assignment -No indicators for routings (except those that cannot be deleted) Execute Copy Save Exit transaction

18-02-2004

© 2004 SAP AG. All rights reserved.

83

Unit 3: Material Master, BOMs, and Task Lists

PLM140

Lesson Summary You should now be able to: • Maintain a super BOM without dependencies with class items and configurable assemblies

84

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintaining Task Lists

Lesson: Maintaining Task Lists Lesson Overview This lesson describes how to maintain a task list and routing with additional sequences, suboperations, and Production Resources/Tools (PRTs).

Lesson Objectives After completing this lesson, you will be able to: •

Maintain task lists and routings without dependencies with additional sequences, suboperations, and Production Resources/Tools (PRTs)

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company is implementing variant configuration solution to maintain end-product variants. As the Product Manager of the company, you have created the material master record and the bill of material. Now, you need to create a task list and routing. These are used to represent all variants of the product.

Overview of Task Lists

Figure 36: Super Task List

Definition: Task List

18-02-2004

© 2004 SAP AG. All rights reserved.

85

Unit 3: Material Master, BOMs, and Task Lists

PLM140

A task list is a list that describes the process for producing a material or for performing a service. The task list contains all the operations, suboperations, and Production Resources/Tools (PRTs) that are required to produce the material. The task list or routing for a configurable material contains all the sequences, operations, suboperations, and PRT assignments that are required to produce all possible variants of the material. You then assign dependencies to the operations, sequences, and PRTs in routings for configurable materials. The operations for a specific variant are selected by object dependencies. The routing is exploded according to the characteristic values you assign. You can create a routing by copying the configuration simulation. You can do this for a specific sales order.

Using Task Lists

Figure 37: Task List

An alternative sequence allows you to select alternative operations for a sequence of operations. This can be useful to deal with either different production processes for different lot sizes, or capacity problems. A parallel sequence allows you to process operations simultaneously with operations in the standard sequence of the routing. Suboperations are a more detailed definition of the operational activity. The suboperations comprise a hierarchy below the main operation for which they define additional details in costing and capacity planning. The control key setting also plays an important role here.

86

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintaining Task Lists

Scheduling is always done at operation level. The standard values for suboperations can be summarized per operation, with the same dimension and unit. You can assign PRTs to any operation. The PRT must have a master record.

18-02-2004

© 2004 SAP AG. All rights reserved.

87

Unit 3: Material Master, BOMs, and Task Lists

88

© 2004 SAP AG. All rights reserved.

PLM140

18-02-2004

PLM140

Lesson: Maintaining Task Lists

Exercise 6: Routing Maintenance (Without Dependencies) Exercise Objectives After completing this exercise, you will be able to: • Maintain super task lists for configurable materials

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company is implementing SAP R/3 Enterprise to optimize its storage inventories and maintain every possible end-product variant. You are the Product Manager of the company. In the model for the PC, it becomes necessary to create the routing for a configurable PC. You need to create a routing for the PC. The assembly Extras is defined as a non-stock, configurable assembly, implying that its components are provided directly for the production order for the PC. Hence, Extras needs no routing.

Task: Create a routing in plant 1200 for your PC, T-VPC##. You may find it useful to copy from the routing for PC, T-VPC00 in plant 1200. Ask your instructor for details if you choose the copy from transaction. 1.

The routing is: For usage: Production With status: Released (general)

2.

The routing has one standard sequence only, which contains the following operations: Operation

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

89

Unit 3: Material Master, BOMs, and Task Lists

Operation

PLM140

Work center Control key

Description Standard Values

10

PC-1PP01 Standard Assembly & Paint Setup 10 min Labor 10 min

20

PC-1PP01 Installation CPU standard Setup 5 min Labor 5 min

30

PC-1PP01 Installation CPU medium Setup 6 min Labor 6 min

Continued on next page

90

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintaining Task Lists

40

PC-1PP01 Installation CPU fast Setup 7 min Labor 7 min

50

PC-1PP01 Installation Extras Setup 8 min Labor 8 min

60

PC-3PP01 Final inspection and packaging Setup 0 min Labor 10 min

3.

Maintain all the standard values specified in the table above for the operations.

4.

Assign the Production Resource/Tool (PRT) PP-FHMS (Type: OTHER) to operation 50. If prompted, enter: Control key 1 Quantity 1

18-02-2004

© 2004 SAP AG. All rights reserved.

91

Unit 3: Material Master, BOMs, and Task Lists

PLM140

Solution 6: Routing Maintenance (Without Dependencies) Task: Create a routing in plant 1200 for your PC, T-VPC##. You may find it useful to copy from the routing for PC, T-VPC00 in plant 1200. Ask your instructor for details if you choose the copy from transaction. 1.

The routing is: For usage: Production With status: Released (general) a)

Create a routing: Option 1: (without template): CA01=SAP Menu → Logistics → Production → Master Data → Routings → Routings → Standard Routings → Create or User Menu → Environment → Routings → Standard Routings

→ Create

Material:T-VPC## Plant: 1200 Usage:1 = Production Status:4= Released (general)

→ Operation overview 2.

The routing has one standard sequence only, which contains the following operations: Operation

Continued on next page

92

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintaining Task Lists

Operation

Work center Control key

Description Standard Values

10

PC-1PP01 Standard Assembly & Paint Setup 10 min Labor 10 min

20

PC-1PP01 Installation CPU standard Setup 5 min Labor 5 min

30

PC-1PP01 Installation CPU medium Setup 6 min Labor 6 min

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

93

Unit 3: Material Master, BOMs, and Task Lists

40

PLM140

PC-1PP01 Installation CPU fast Setup 7 min Labor 7 min

50

PC-1PP01 Installation Extras Setup 8 min Labor 8 min

60

PC-3PP01 Final inspection and packaging Setup 0 min Labor 10 min

a) 3.

Maintain all the standard values specified in the table above for the operations. a)

4.

Enter operations according to the list.

For standard values in the operation overview, scroll right.

Assign the Production Resource/Tool (PRT) PP-FHMS (Type: OTHER) to operation 50. If prompted, enter: Control key 1

Continued on next page

94

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintaining Task Lists

Quantity 1 a)

Select operation → PRT overview => Window: New PRT as material master

→ Switch to window: New PRT as other PP-FHMS Enter data, choose Enter, save routing. Option 2: (with template, without engineering workbench): CA01 Material:T-VPC## Plant: 1200 Choose Copy from = F5 Type:Routing Material: T-VPC00 Plant:1200 Status:4= Released (general)

→ Save Option 3: (With template, with engineering workbench): See solution above for bills of material. Unit: Material Masters, BOMs, and Task Lists

18-02-2004

© 2004 SAP AG. All rights reserved.

95

Unit 3: Material Master, BOMs, and Task Lists

PLM140

Lesson Summary You should now be able to: • Maintain task lists and routings without dependencies with additional sequences, suboperations, and Production Resources/Tools (PRTs)

96

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Unit Summary

Unit Summary You should now be able to: • Create a material master record, including control parameters for sales and Material Requirements Planning (MRP) • Maintain a super BOM without dependencies with class items and configurable assemblies • Maintain task lists and routings without dependencies with additional sequences, suboperations, and Production Resources/Tools (PRTs)

18-02-2004

© 2004 SAP AG. All rights reserved.

97

Unit Summary

98

PLM140

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Test Your Knowledge

Test Your Knowledge 1.

To enable availability checks for the material and its components, you must enter a checking rule. The default checking rule for a . configurable material is Fill in the blanks to complete the sentence.

2.

Which views for material master maintenance are correctly matched with respective functions? Choose the correct answer(s).

3.

□ □

A B

□ □

C D

Basic Data View - Defines if the material is configurable Sales View - Used for class and characteristic value assignments Work Scheduling View - Sets the order change profile Classification View - Identifies the item category group and general item category group

If you enter a non-stock item without entering a material number, you must enter a and the . Fill in the blanks to complete the sentence.

4.

Which of the following statements are true for BOM? Choose the correct answer(s).

5.

18-02-2004

□

A

□

B

□ □

C D

The BOM of a configurable material contains all the parts that are required for all possible variants of the material. Class dependencies are used to configure the BOM; only the parts that are required for a specific variant are selected. The BOM is exploded according to the object dependencies. You can change the BOM in the production order.

Explain the usefulness of an alternative sequence of a task list.

© 2004 SAP AG. All rights reserved.

99

Test Your Knowledge

6.

PLM140

Sometimes, scheduling is not done at the operation level. Determine whether this statement is true or false.

□ □

100

True False

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Test Your Knowledge

Answers 1.

To enable availability checks for the material and its components, you must enter a checking rule. The default checking rule for a configurable material is 02. Answer: 02

2.

Which views for material master maintenance are correctly matched with respective functions? Answer: A, C Sales view identifies the item category group and general item category group whereas classification view is used for class and characteristic value assignments.

3.

If you enter a non-stock item without entering a material number, you must enter a descriptive text and the procurement data. Answer: descriptive text, procurement data

4.

Which of the following statements are true for BOM? Answer: A, D Object dependencies are used to configure the BOM; only the parts that are required for a specific variant are selected. In addition, the BOM is exploded according to the characteristic values assigned.

5.

Explain the usefulness of an alternative sequence of a task list. Answer: An alternative sequence allows you to select alternative operations for a sequence of operations. This can be useful to deal with either different production processes for different lot sizes, or capacity problems.

6.

Sometimes, scheduling is not done at the operation level. Answer: False Scheduling is always done at the operation level.

18-02-2004

© 2004 SAP AG. All rights reserved.

101

Unit 3: Material Master, BOMs, and Task Lists

102

© 2004 SAP AG. All rights reserved.

PLM140

18-02-2004

Unit 4 Configuration Profiles Unit Overview This unit explains various configuration profiles using scenarios. It also explains how to create and name configuration profiles.

Unit Objectives After completing this unit, you will be able to: • •

Create configuration profiles and define essential control parameters Name the possible configuration scenarios

Unit Contents Lesson: Configuration Scenarios .............................................104 Exercise 7: Creating and Testing a Configuration Profile ............ 113

18-02-2004

© 2004 SAP AG. All rights reserved.

103

Unit 4: Configuration Profiles

PLM140

Lesson: Configuration Scenarios Lesson Overview This lesson describes how to create configuration profiles and define essential control parameters. It also explains various configuration scenarios.

Lesson Objectives After completing this lesson, you will be able to: • •

Create configuration profiles and define essential control parameters Name the possible configuration scenarios

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company is implementing variant configuration solution of SAP R/3 Enterprise to maintain end-product variants. You are the Product Manager of the company. Your team now wants to gain an overview of the different scenarios for variant configuration that are available in SAP R/3 Enterprise.

Configuration Profile for a Material

Figure 38: Configuration Profile for a Material

104

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Configuration Scenarios

You define essential settings for materials in the configuration profile. The settings you can make for other configurable object types are more restricted. You select a class type. You can define settings that affect configuration. You define these settings for each object, and they apply to the object wherever it is used. However, you can overwrite these settings for your user in the configuration editor. You can specify an interface design for grouping characteristics together on the value assignment screen. You can assign dependencies to a configurable object in the configuration profile. Dependency nets can only be assigned to a configuration profile. If you assign actions and procedures to the configuration profile, you can manage them more easily because they are all in one place. For materials, you must also maintain configuration parameters for BOM explosion. Depending on the configuration parameters you set, other fields in the configuration profile are hidden or shown. The configurable material must be assigned to at least one variant class. This link is usually only a material-to-class assignment, without assigned values. Assigning values would restrict the allowed values. You have the following options for assigning a material to a class: • • •

18-02-2004

Master data maintenance (material master) The classification menu (maintain assignment) The configuration profile (class assignment)

© 2004 SAP AG. All rights reserved.

105

Unit 4: Configuration Profiles

PLM140

Production Order

Figure 39: Scenario: Planned/Production Order Without BOM Explosion

Only the header material is configured interactively in the sales order. The result is one order item in the sales order. The BOM is only simulated in the configuration simulation - it is not exploded in the sales order. All components, variable and non-variable parts, are determined automatically during the MRP run. Process Flow Create a sales order and enter the configurable material as an order item. You see the configuration editor, where you assign values to the characteristics of the material. As you enter characteristic values, dependencies for the characteristics and values are processed. You cannot go to other overviews in the configuration editor if you select None under BOM explosion. In MRP, requirements are determined for the item in the sales order. In the planned order or production order, the components of the BOM and the operations of the routing are determined according to the characteristic values assigned in the sales order. Low-level configuration applies.

106

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Configuration Scenarios

Order BOM

Figure 40: Scenario: Order BOM - Overview

Purpose - You use this processing option if you want to make customer-specific changes to the BOM of a material that you configure in the sales order. In the sales order, you assign values to the characteristics of the material, but the BOM is not exploded. The BOM components that match these values are not determined until you process the order BOM. Subordinate configurable materials can be configured in the order BOM processing function, and you can make order-specific changes to the BOM. If you change the characteristic values assigned to the material in transaction VA01 or CU51, this might affect the order BOM. Prerequisites - The configuration profile of the configurable material specifies the “order BOM“ process with single-level or multilevel BOM explosion.

18-02-2004

© 2004 SAP AG. All rights reserved.

107

Unit 4: Configuration Profiles

PLM140

Figure 41: Scenario: Order BOM - Step 1

Create a sales order and enter the configurable material as an order item. You see the configuration editor, where you assign values to the characteristics of the material. As you enter characteristic values, dependencies for the characteristics and values are processed. The BOM is not exploded in the sales order. You cannot assign values to subordinate configurable materials in the sales order. The header material appears as a sales order item. You can also create an order BOM for a quotation.

108

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Configuration Scenarios

Figure 42: Scenario: Order BOM - Step 2

Procedure - After you have created and saved the sales order, you use a special transaction to process the order BOM. This transaction explodes the entire structure of the order BOM. You can configure subordinate configurable assemblies. The technical review determines which assemblies need to be changed and which new assemblies are required. You can make the following changes to an order BOM: change BOM items, for example, quantity, insert items, delete items, copy items, cut items, and replace class items manually. Result-oriented order BOM If you set this indicator, the configured order BOM is saved with all manual changes. If you do not set this indicator, the super BOM is saved with all manual changes and object dependencies (selection conditions and procedures). When you call the BOM, the selection conditions are processed automatically and only the selected items are displayed. Automatic fixing If this indicator is set, you can use the maintenance function to save an order BOM, even if no changes are made to the BOM. If this indicator is not set, an order BOM is only created if you make manual changes to the BOM.

18-02-2004

© 2004 SAP AG. All rights reserved.

109

Unit 4: Configuration Profiles

PLM140

Sales Order

Figure 43: Scenario: Order BOM + Maintenance Allowed in Sales Order

The Maintenance in order allowed indicator allows you to go to the engineering view without leaving sales order maintenance. In the sales order, you see a button labeled “Engineering“. This means that the assigned values are temporarily fixed. The BOM can be exploded. You can do a multilevel configuration. You cannot maintain an order BOM in the sales order. From here, you can go back to the “Sales“ view at any time to change the values assigned to the header material. In technical postprocessing (CU51), exactly the same function is available. This means that: • • • •

110

The values assigned to the header material cannot be changed. The BOM can be exploded. You can do a multilevel configuration. You can create order BOMs.

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Configuration Scenarios

Figure 44: Scenario: Sales Order (SET Processing) 1

Purpose - You can use this processing type to describe variant products that comprise several salable configurable materials. These products are supplied together, but are not assembled using a production order. For example, a PC is made up of the components monitor, CPU, keyboard, and printer. These components are all salable materials that can be manufactured and sold separately. In the sales order, you want to see order items for the individual components that make up the computer, as well as the whole computer. In sales order processing, these products are grouped together in a SET. For this reason, this type of processing is also referred to as SET processing. Process Flow - Create a sales order and enter the configurable material as an order item. You see the configuration editor, where you assign values to the characteristics of the material. You can then display the result of the BOM explosion by choosing Result. You see all the sales-relevant BOM components that are selected according to the values assigned.

18-02-2004

© 2004 SAP AG. All rights reserved.

111

Unit 4: Configuration Profiles

PLM140

Figure 45: Scenario: Sales Order (SET Processing) 2

This scenario means that in the sales order you can only process sales-relevant BOM items. You can also configure the configurable assemblies that are sales relevant. You can use constraints to infer characteristic values between assemblies. After you have configured all materials, you return to the order item entry screen. All BOM items that were selected and are relevant to sales are displayed as subitems for the main item in the sales order. You can use the item category group to control requirements transfer and pricing at component level.

112

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Configuration Scenarios

Exercise 7: Creating and Testing a Configuration Profile Exercise Objectives After completing this exercise, you will be able to: • Create a configuration profile with all the necessary settings for your PC • Simulate the configuration with the data you have created so far

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company has decided to use SAP R/3 Enterprise to optimize its storage inventories and maintain every possible end-product variant. You are the Product Manager of the company. In the model for the PC configuration task, you need to create the configuration profile. This will make it possible to configure the PC on one level without the option of making manual changes.

Task 1: Create a configuration profile for your PC T-VPC## with the name PROFILE_PF0. 1.

Check whether the assignment to the variant class exists and create if it does not exist.

2.

Maintain the detail settings for your profile. Include the following information: Confign parameters Profile name

PROFILE_PF0

Class Type

300

Class Assignment

T_VPC##

BOM Explosion

None

Process

Planned/production order

Interface design

TVPC##

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

113

Unit 4: Configuration Profiles

PLM140

Task 2: Check the result of what you have done so far in the configuration simulation. 1.

2.

Simulate the configuration of your PC T-VPC## in plant 1200. Configuration: Sales/distribution. First select the BOM as the configuration result. Display the Characteristic Value Assignment screen. Why do the values for characteristic Extras appear on the screen, but not the values for the other characteristics?

3.

Do not assign any characteristic values and choose: Result. What happens? Why?

4.

Assign values to all characteristics and choose: Result or Planned order. If prompted, select BOM application: PP01 What happens now? What do you notice about the result? Why?

5. 6. 7.

Display the BOM master data (super BOM). From the result overview of the BOM, display the exploded task list (routing) of the PC. (Optional) Call configuration simulation again - this time with configuration result task list. Assign values to all characteristics and look at the result. Display the routing master data (super task list).

114

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Configuration Scenarios

Solution 7: Creating and Testing a Configuration Profile Task 1: Create a configuration profile for your PC T-VPC## with the name PROFILE_PF0. 1.

Check whether the assignment to the variant class exists and create if it does not exist. a)

Create a configuration profile for your PC, T-VPC##: CU41 = SAP Menu → Logistics → Central Functions → Variant Configuration → Configuration Profile → Create or User Menu → Variant Configuration → Configuration Profile

→ Create

=> Select configurable object

→ Here: Select Material and choose Enter Material:T-VPC## ( Enter Prof. name:PROFILE_PF0 Class Type:300

→ Profile detail= Shift + F7 Check whether the assignment to the variant class exists and create if it does not exist. → Class Assignment 2.

Maintain the detail settings for your profile. Include the following information: Confign parameters Profile name

PROFILE_PF0

Class Type

300

Class Assignment

T_VPC##

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

115

Unit 4: Configuration Profiles

PLM140

BOM Explosion

None

Process

Planned/production order

Interface design

TVPC##

a)

Basic data: Do not change Confign initial screen: Confign parameters: Process: Plnd/Prod. Order BOM Explosion: None (Do not change anything else) Userinterf: Interface design:TVPC## (Do not change anything else)

Task 2: Check the result of what you have done so far in the configuration simulation. 1.

Simulate the configuration of your PC T-VPC## in plant 1200. Configuration: Sales/distribution. First select the BOM as the configuration result. a)

Check the result of what you have done so far in the configuration simulation. CU50 = SAP Menu → Logistics → Central Functions → Variant Configuration → Environment → Configuration Simulation or User Menu → Variant Configuration → Environment → Configuration Simulation Material:T-VPC## Plant: 1200 Configuration:Sales/distribution Configuration result:BOM

2.

Display the Characteristic Value Assignment screen. Continued on next page

116

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Configuration Scenarios

Why do the values for characteristic Extras appear on the screen, but not the values for the other characteristics? a)

Display the Characteristic Value Assignment screen = F8. The characteristic’s interface control is defined to automatically display the allowed values on the characteristic value assignment screen.

3.

Do not assign any characteristic values and choose: Result. What happens? Why? a)

Do not assign any characteristic values and choose: Result What happens? You see the following error message: No value was assigned to “CPU of PC“. Why? If characteristics are defined as “Required“, values must be assigned.

4.

Assign values to all characteristics and choose: Result or Planned order. If prompted, select BOM application: PP01 What happens now? What do you notice about the result? Why? a)

Then assign values to all characteristics and choose: Result = Ctrl + F9 or Planned order = Ctrl + Shift + F5 (BOM application: PP01) What happens now? What do you notice about the result? No components were restricted. Why? Object dependencies are required to select components.

5.

Display the BOM master data (super BOM). a)

Display the BOM master data (super BOM).

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

117

Unit 4: Configuration Profiles

6.

From the result overview of the BOM, display the exploded task list (routing) of the PC. a)

7.

PLM140

From the result overview of the BOM, display the exploded task list (routing) of the PC.

(Optional) Call configuration simulation again - this time with configuration result task list. Assign values to all characteristics and look at the result. Display the routing master data (super task list). a)

(Optional) Call the configuration simulation again - this time with the configuration result task list. Assign values to all characteristics here, too, and display the result. Display the routing master data (super task list).

118

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Configuration Scenarios

Lesson Summary You should now be able to: • Create configuration profiles and define essential control parameters • Name the possible configuration scenarios

18-02-2004

© 2004 SAP AG. All rights reserved.

119

Unit Summary

PLM140

Unit Summary You should now be able to: • Create configuration profiles and define essential control parameters • Name the possible configuration scenarios

120

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Test Your Knowledge

Test Your Knowledge 1.

All components, variable and non-variable parts, are determined . automatically during the Fill in the blanks to complete the sentence.

2.

The of the configurable material specifies the “order BOM“ process with single-level or multilevel BOM explosion. Fill in the blanks to complete the sentence.

3.

Which of the following statement are true for the indicators in BOM? Choose the correct answer(s).

18-02-2004

□

A

□

B

□

C

□

D

If you set the “Result-oriented order BOM“ indicator, the configured order BOM is saved with all the manual changes rejected. If you do not set the “Result-oriented order BOM“ indicator, the super BOM is saved with all manual changes and object dependencies (selection conditions and procedures). If the “Automatic fixing“ indicator is set, you can use the maintenance function to save an order BOM, even if no changes are made to the BOM. If the “Automatic fixing“ indicator is not set, an order BOM cannot be created at all.

© 2004 SAP AG. All rights reserved.

121

Test Your Knowledge

PLM140

Answers 1.

All components, variable and non-variable parts, are determined automatically during the MRP run. Answer: MRP run

2.

The configuration profile of the configurable material specifies the “order BOM“ process with single-level or multilevel BOM explosion. Answer: configuration profile

3.

Which of the following statement are true for the indicators in BOM? Answer: B, C If you set the “Result-oriented order BOM“ indicator, the configured order BOM is saved with all the manual changes. In addition, if the “Automatic fixing“ indicator is not set, an order BOM can be created by making manual changes to the BOM.

122

© 2004 SAP AG. All rights reserved.

18-02-2004

Unit 5 Object Dependencies Unit Overview This unit explains various types and functions of dependencies and their creation. It also explains the use of various tools to work with dependencies.

Unit Objectives After completing this unit, you will be able to: • • • •

Identify the various types of dependencies Describe the functions of dependencies Create dependencies Use tools for working with dependencies

Unit Contents Lesson: Types and Functions of Object Dependencies ...................124 Lesson: Creating Object Dependencies .....................................129 Lesson: Tools for Working With Dependencies .............................138

18-02-2004

© 2004 SAP AG. All rights reserved.

123

Unit 5: Object Dependencies

PLM140

Lesson: Types and Functions of Object Dependencies Lesson Overview This lesson describes various types of dependencies and their functions.

Lesson Objectives After completing this lesson, you will be able to: • •

Identify the various types of dependencies Describe the functions of dependencies

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company is implementing variant configuration solution of SAP R/3 Enterprise to maintain end-product variants. You are the Product Manager of the company and your team has come a long way toward setting up the variant configuration knowledge base. When you try to configure a product, you need to identify the dependencies in the variant configuration solution.

Knowledge Base for Materials

Figure 46: Variant Configuration Knowledge Base for Materials (2)

124

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Types and Functions of Object Dependencies

Figure 47: Variant Configuration Knowledge Base for Materials (1)

Defining Object Dependencies •

Local dependencies have the following properties: – –

•

Global dependencies have the following properties: – –

–

18-02-2004

They cannot be maintained centrally and cannot be assigned to other objects. They are identified by a number assigned by the system and not by an external name.

They are identified by an assigned external name and are maintained and managed centrally. There are special assignment functions that enable you to assign global dependencies to individual objects. However, you can also create all dependencies except constraint nets in the assignment function. If you change a global dependency, it affects all the objects where dependency is used.

© 2004 SAP AG. All rights reserved.

125

Unit 5: Object Dependencies

PLM140

Types of Object Dependencies

Figure 48: Dependency Types

Assignment of Object Dependencies

Figure 49: Assignment of Object Dependencies

126

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Types and Functions of Object Dependencies

Object Dependencies in Classification and Variant Configuration Classification

Variant Configuration

•

•

•

• •

Can be assigned only to classes, characteristics, and values Active only when classifying an object and not when finding objects Dynamic control of characteristic and values Automatic characteristic value assignment

• •

• • •

18-02-2004

Required to perform configuration Can be assigned to various objects in the knowledge base Active during the configuration process as determined by the predefined execution sequence Dynamic control of characteristic and values Automatic characteristic value assignment Multilevel configuration, including checks for completeness and consistency

© 2004 SAP AG. All rights reserved.

127

Unit 5: Object Dependencies

PLM140

Lesson Summary You should now be able to: • Identify the various types of dependencies • Describe the functions of dependencies

128

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Creating Object Dependencies

Lesson: Creating Object Dependencies Lesson Overview This lesson describes how to create dependencies.

Lesson Objectives After completing this lesson, you will be able to: •

Create dependencies

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company is implementing variant configuration solution of SAP R/3 Enterprise to maintain end-product variants. You are the Product Manager of the company. You have identified the dependencies in the variant configuration solution. To ensure that the system selects relevant objects for configuring a product, there should be a mutual interdependence between objects. Now, you need to create these object dependencies.

Processing Sequence of Object Dependencies

Figure 50: Processing Sequence of Dependencies

18-02-2004

© 2004 SAP AG. All rights reserved.

129

Unit 5: Object Dependencies

PLM140

The following processing sequence applies to the value assignment user interface. Processing is started according to your settings, either on ENTER or on request. It includes dependencies for the configuration profile, the characteristics that have values assigned, and the values used. 0. Default values for characteristic 1. All actions multiple times, until no more values can be inferred 2. All procedures exactly once in the following sequence: - Configuration profile - Characteristics - Characteristic values The processing sequence of procedures for each object is defined in the dependency assignment. 3. As in 1. - all actions that are triggered by changes made by procedures. In parallel with points 0. to 3. all constraints are processed as soon as relevant changes are made. 4. All preconditions and then all selection conditions. When you explode the BOM and task list, the following sequence applies: Selection conditions => actions => procedures => actions

Paradigms of SAP R/3 Enterprise Configurator •

Declarative dependency types

•

– Constraints – Actions Semi-declarative dependency types Behave like declarative dependency types, but are processed procedurally and internally

•

– Preconditions – Selection conditions Procedural dependency types

•

– Procedures All dependency types are object oriented – –

130

Inheritance of dependencies within class hierarchies Object-specific processing of dependencies

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Creating Object Dependencies

In declarative dependencies, the point in time when the dependency is processed and the sequence in which the dependencies are processed are not relevant to the result. The result of a declarative dependency can be explained logically. The dependency describes a rule that must always apply. This contrasts with procedural dependencies, where the result depends on the processing sequence and the point in time when the dependency is processed. Some expressions are in themselves non-declarative. For this reason, these expressions cannot be used in declarative object dependencies: NOT SPECIFIED; NOT TYPE_OF; NE You can use these expressions in preconditions and selection conditions. Since preconditions and selection conditions are not processed until the end of the configuration process, you can assume that values have been assigned to all the characteristics that are intended to have values, and that any missing information is deliberately not given. When the not equals (NE) expression is processed for multiple-value characteristics, there is a difference between constraints and actions. In constraints, “not equals“ can be expressed for multiple-value characteristics, because values are processed individually in constraints. In actions, however, the sum of the selected values is processed. Since it is not clear whether it is deliberate that no value was selected for a multiple-value characteristic or whether a value will be assigned at a later point in time, this expression cannot be processed in actions. Dependencies, classes, and objects support a declarative and object-oriented solution for a knowledge base. The system determines the processing sequence of the object dependencies and ensures that they are only executed when required.

Syntax for Object Dependencies • • • •

18-02-2004

Each of the five dependency types has its own syntax rules. Preconditions, selection conditions, actions, and procedures are simple dependencies. Preconditions and selection conditions are Boolean expressions with a binary result. Constraints are more complex object dependencies with their own syntax. They are structured like a program. They have a much broader functional scope. They are especially useful for defining and evaluating complex, multilevel configurations, but can also be used with single-level configurations.

© 2004 SAP AG. All rights reserved.

131

Unit 5: Object Dependencies

•

The syntax of dependencies is not the same as ABAP syntax. However, ABAP function modules can be called in dependencies as variant functions.

• •

Two strings might be separated by any number of blanks. Keywords and strings are not case sensitive, except for characteristic values that were originally defined as case sensitive in characteristics maintenance. Strings containing hyphens must be enclosed in single quotes and preceded with the keyword SKEY. All strings must be entered in their global language-independent form. An asterisk (*) at the beginning of a line identifies the line as a comment. Elements in lists are separated by commas (,). Characteristic values in CHAR format must be enclosed in single quotes. Syntax

• • • • •

• •

The syntax for object variables is different depending on whether the variable is used in constraints or simple object dependencies. In simple dependencies you can use the three object variables $ROOT, $PARENT, and $SELF. These object variables have a fixed meaning: – – –

• • •

132

PLM140

$ROOT always refers to the header material in a configuration. $SELF refers to the current object. Actions and procedures can only set values on this level. $PARENT refers to the instance immediately above $SELF in a configuration structure. Instances are created only for configurable materials with an active configuration profile.

Constraints use a more flexible method of identifying objects and characteristics. All objects and characteristics of the variant classes can be directly and concurrently addressed during the execution of a constraint. Objects and characteristics can be addressed by their system-wide, language-independent names, or by shorter names that are defined as variables within the constraint to keep the syntax simple.

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Creating Object Dependencies

Figure 51: Operators

Figure 52: Arithmetical Expressions

•

• •

You can use the operator IN to define lists of values that have an OR relationship to each other. Example: COLOR IN (“red“, “yellow“, or “green“) This condition is fulfilled if at least one of the values “red“, “yellow“, or “green“ is assigned to characteristic COLOR. In a precondition, this condition is also fulfilled if no value is assigned to characteristic COLOR. Example: POWER IN (200, 300, 350)

Restrictions:

18-02-2004

© 2004 SAP AG. All rights reserved.

133

Unit 5: Object Dependencies

PLM140

Value nodes in value hierarchies are not supported in dependencies. The expression, COUNTRY IN “Europe“, where Europe is a value node with subordinate values, is not allowed in dependencies. •

•

You can use the expression SPECIFIED in: – Preconditions – Selection conditions – Conditions in procedures, actions, and constraints The precondition is fulfilled if any value is selected for the characteristic. However, it does not matter which value is assigned to the characteristic. SPECIFIED SPECIAL_PAINT SPECIAL_PAINT SPECIFIED

•

The negative form NOT SPECIFIED always goes before the characteristic variable. NOT SPECIFIED SPECIAL_PAINT

Restrictions: You cannot use NOT SPECIFIED in actions and constraints. • •

You use TYPE_OF to define that the condition only applies to one object. You use this condition if the dependency is dependent on its environment, for example, dependent on being used for a specific BOM header material. TYPE_OF($ROOT, (Material)(300)(NR=“U91“))

•

If you use a condition like this, for example, a selection condition for a BOM item, the item is included in the BOM explosion if the $ROOT object (header material) has material number “U91“.

Restrictions: TYPE_OF and NOT TYPE_OF cannot be used in constraints.

134

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Creating Object Dependencies

NOT TYPE_OF cannot be used in actions. •

= || = Concatenate terms and cut off after 30 characters CHAR1= ’Variant’ || ’Configuration’ || ’VariantConfiguration’ ==> Char1 = ’VariantConfigurationVariant’

•

LC = Convert to lowercase CHAR1 LC ’Otto’ ==> CHAR1 = ’otto’ Char1 is case sensitive

•

UC = Convert to uppercase CHAR2 UC CHAR1 Char2 is not case sensitive, unlike Char1

• • • • • •

•

mdata := Addresses the “master data“: the value in the relevant database field set_default := Sets default values del_default := Deletes values set by “set_default“ sum_parts := Calculates the sum for a numeric characteristic across all items in a single-level BOM explosion (multilevel configuration only) count_parts := Calculates the item quantities (similar to “sum_parts“) part_of := (In constraints only) allows queries as to whether an object is a component in the exploded BOM of another object (optionally in a specific position) subpart_of := (In constraints only) same as “part_of“ but any BOM structure

Example for mdata: Item quantity “1“ is entered in the bill of material, and T_POS_MENGE is a reference characteristic with reference to database field STPO-MENGE. The following procedure is processed: $self.t_pos_menge = $self.t_pos_menge + 1, $self.t_pos_menge = $self.t_pos_menge * 2

18-02-2004

© 2004 SAP AG. All rights reserved.

135

Unit 5: Object Dependencies

PLM140

This produces the value 1 for the item quantity, because the procedure terminates. The following procedure is processed: $self.t_pos_menge = mdata $self.t_pos_menge + 1, $self.t_pos_menge = $self.t_pos_menge * 2 This produces the value 4 for the item quantity. The following procedure is processed: $self.t_pos_menge = mdata $self.t_pos_menge + 1, $self.t_pos_menge = mdata $self.t_pos_menge * 2 This produces the value 2 for the item quantity.

Status of Object Dependencies

Figure 53: Dependency Status

136

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Creating Object Dependencies

Lesson Summary You should now be able to: • Create dependencies

18-02-2004

© 2004 SAP AG. All rights reserved.

137

Unit 5: Object Dependencies

PLM140

Lesson: Tools for Working With Dependencies Lesson Overview This lesson describes the tools that are used to work with dependencies.

Lesson Objectives After completing this lesson, you will be able to: •

Use tools for working with dependencies

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company is implementing variant configuration solution of SAP R/3 Enterprise to maintain end-product variants. As the Product Manager of the company, you identified the dependencies in the variant configuration solution. To create these dependencies, you need to work with variant functions, tables, and traces.

Variant Tables •

•

• •

Variant tables are used to store combinations of characteristic values, for example, you can only have a gray car interior if the exterior paint color is blue. Variant tables can simplify dependencies. You can reference the table in the dependency and the system can use the table to check assigned values or infer values. If the interdependencies between characteristic values change, you can change the table contents. However, there is no need to change the individual dependencies. You can link a variant table to a database table. You can use variant tables with all dependency types. –

– –

138

In selection conditions, preconditions, constraints, and the conditional part of actions and procedures, variant tables are used to check the values entered during configuration. In actions, procedures, and constraints, you can use tables to infer values. In constraints, you can use tables to restrict the allowed values for a characteristic (restrictable characteristics).

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Tools for Working With Dependencies

Figure 54: Variant Tables (2)

Variant Functions • •

Variant functions enable you to complement an object dependency with special logic for calculations or consistency checks. In a function, you can refer to an ABAP function module and transfer import and export parameters. In the function module, you can access the data for processing. Declaration of function name: FUNCTION Z_LABEL_ID Declaration of characteristics: (CASING = $ROOT.CASING, CPU = $ROOT.CPU, HARD_DISK = $ROOT.HARD_DISK, LABEL_ID = $SELF.LABEL_ID)

When you call a user-defined function module, SAP R/3 Enterprise variant configuration has no control over any error situations that occur. The person who writes the program can use ABAP language elements but has sole responsibility for the code.

18-02-2004

© 2004 SAP AG. All rights reserved.

139

Unit 5: Object Dependencies

PLM140

Trace Functions • •

The trace function traces the internal processing steps that the system makes while processing dependencies. You can start the trace function for the following objects:

•

– Simple dependencies – Constraints – Tables and functions – Dynamic database Additional filter criteria: – –

•

You can restrict the trace function to specific dependencies. You can restrict the trace function for the dynamic database to a given list of characteristics. – You can restrict the trace function to a given list of tables or functions. You can define the level of detail for your trace: –

140

Less detailed or more detailed

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Tools for Working With Dependencies

Lesson Summary You should now be able to: • Use tools for working with dependencies

18-02-2004

© 2004 SAP AG. All rights reserved.

141

Unit Summary

PLM140

Unit Summary You should now be able to: • Identify the various types of dependencies • Describe the functions of dependencies • Create dependencies • Use tools for working with dependencies

142

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Test Your Knowledge

Test Your Knowledge 1.

Local dependencies are identified by an external name. Determine whether this statement is true or false.

□ □ 2.

True False

Object dependencies in classification are active during the configuration process as determined by the predefined execution sequence. Determine whether this statement is true or false.

□ □ 3.

True False

Which of the following statements are true for the expression “SPECIFIED“? Choose the correct answer(s).

4.

□ □

A B

□

C

□

D

You can use the expression “SPECIFIED“ in preconditions. You can use the expression “SPECIFIED“ in selection conditions. The negative form of the expression “SPECIFIED“, that is, “NOT SPECIFIED“, always goes after the characteristic variable. You can use “NOT SPECIFIED“ in actions and constraints.

Which of the dependency statuses are correctly matched with their explanations? Choose the correct answer(s).

□ □ □ □ 5.

A B C D

Dependency status “1“ - Released Dependency status “1“ - In preparation Dependency status “3“ - Locked Dependency status “2“ - Locked

Identify the correct statements for variant tables. Choose the correct answer(s).

□ □ □ □

18-02-2004

A B C D

Variant tables are used to store combinations of class values. Variant tables can simplify dependencies. You can link a variant table to a database table. You can use variant tables with a few dependency types.

© 2004 SAP AG. All rights reserved.

143

Test Your Knowledge

6.

PLM140

For the following objects can you start the trace function? Choose the correct answer(s).

□ □ □ □

144

A B C D

Simple dependencies Import and export parameters Characteristics values Dynamic database

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Test Your Knowledge

Answers 1.

Local dependencies are identified by an external name. Answer: False Local dependencies are identified by a number assigned by the system and not by an external name.

2.

Object dependencies in classification are active during the configuration process as determined by the predefined execution sequence. Answer: False Object dependencies in variant configuration are active during the configuration process as determined by the predefined execution sequence.

3.

Which of the following statements are true for the expression “SPECIFIED“? Answer: A, B The negative form of the expression “SPECIFIED“ (“NOT SPECIFIED“) always goes before the characteristic variable. In addition, you cannot use “NOT SPECIFIED“ in actions and constraints.

4.

Which of the dependency statuses are correctly matched with their explanations? Answer: A, C Dependency status “1“ means that the dependency is released and can be used. However, the dependency must be complete before it can be used; Dependency status “2“ means that the dependency is in preparation and cannot be used as yet; Dependency status “3“ means that the dependency is locked for new use.

5.

Identify the correct statements for variant tables. Answer: B, C You can use the variant tables to store combinations of characteristic values. You can also use variant tables with all dependency types.

18-02-2004

© 2004 SAP AG. All rights reserved.

145

Test Your Knowledge

6.

PLM140

For the following objects can you start the trace function? Answer: A, D You can start the trace function for simple dependencies, constraints, tables and functions, and dynamic database.

146

© 2004 SAP AG. All rights reserved.

18-02-2004

Unit 6 Object Dependencies in BOMs and Task Lists Unit Overview This unit explains object dependencies in BOMs and task lists. It also explains maintenance and functions of selection conditions. In addition, it explains the procedures for BOMs and task lists.

Unit Objectives After completing this unit, you will be able to: • • • •

Create and maintain basic selection conditions Use class nodes in a bill of material Use classification data as a selection condition for classified objects in a bill of material Use reference characteristics with procedures to change field values in exploded BOMs and task lists (routings)

Unit Contents Lesson: Maintenance and Functions of Selection Conditions ............148 Exercise 8: Selection Conditions in BOMs .............................155 Exercise 9: Selection Conditions in Task Lists .........................163 Lesson: Procedures for BOMs and Task Lists ..............................169 Exercise 10: Characteristic Value Assignment for Class Nodes .....173

18-02-2004

© 2004 SAP AG. All rights reserved.

147

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

Lesson: Maintenance and Functions of Selection Conditions Lesson Overview This lesson explains how to create and maintain basic selection conditions. It also explains the use of class nodes in a BOM and the use of classification data as a selection condition for classified objects in a bill of material.

Lesson Objectives After completing this lesson, you will be able to: • • •

Create and maintain basic selection conditions Use class nodes in a bill of material Use classification data as a selection condition for classified objects in a bill of material

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company is implementing variant configuration solution of SAP R/3 Enterprise to maintain end-product variants. As the Product Manager of the company, you are responsible for this implementation. You have created a material master record, bill of material, and routing. These are used to represent all variants of the product. Now, you need to control the interactive and dynamic selection of BOM components and operations in routings.

Selection Condition for BOMs and Task Lists • •

Selection condition: BOM items, Operation, suboperation, sequence, PRT Procedure (Action): BOM items, task list objects

Object dependencies are assigned according to their task, to the object that they are meant to influence. Before you create a dependency, you must select the appropriate dependency type. The dependency type determines how the editor checks the syntax. Selection conditions are used to select the appropriate BOM item from the super BOM, and the appropriate operation, PRT, and so on from the super task list. Procedures are used to change item data or operation data. Procedures can incorporate recursive calculations. This also allows overwriting.

148

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintenance and Functions of Selection Conditions

Figure 55: Selection Condition for a BOM

Depending on the characteristic values you assign during value assignment, you can define which BOM components are selected. For example, if you assigned the value “fast“ to characteristic CPU, you can use a selection condition to determine that the BOM component for the fast CPU is selected. If a different value is chosen for the characteristic CPU, the BOM component for the fast CPU is not selected. If characteristic CPU has no value, the BOM component for the fast CPU is also not selected. Please note that this is different to the effect of preconditions. When you create a selection condition, you have the following options: • •

Create locally, for the BOM item Create globally, uses a separate menu path and is identified by a name

After a global selection condition has been created, it must be assigned to the appropriate object(s). A selection condition is fulfilled if the value in the condition is set for the characteristic. A selection condition is not fulfilled if: • •

18-02-2004

A different value is set for the characteristic No value is selected for the characteristic

© 2004 SAP AG. All rights reserved.

149

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

Figure 56: Selection Condition for a Task List

You use selection conditions for a task list to define which sequences, operations, suboperations, and Production Resources/Tools (PRTs) are to be selected for a specific variant. In this example, the operation “Install Extras“ is only selected if a value is assigned to characteristic EXTRAS. Note the special keyword in the syntax, “Specified“. By using the keyword “Specified“ in a selection condition, you state that it does not matter which value is assigned to the characteristic. Any value triggers the selection condition.

150

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintenance and Functions of Selection Conditions

Figure 57: Selection Condition – PRTs in Task Lists

The Production Resource/Tool (PRT for modem installation) is assigned to operation 50 (Install Extras). You use a selection condition to define that the PRT is selected only if the value “Modem“ is assigned to characteristic EXTRAS. If a value other than “Modem“ is assigned to characteristic EXTRAS, operation 30 appears without an assigned PRT in the task list explosion. Before operation 30, “Install Extras“, can be selected at all, a value must be assigned to the characteristic EXTRAS. However, it does not matter which value is assigned to the characteristic.

18-02-2004

© 2004 SAP AG. All rights reserved.

151

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

Class Nodes in a BOM

Figure 58: Class Nodes in a BOM

You can enter a class as a BOM item instead of a material. First, you must create the class in the classification menu and use it to classify objects. Only classes for materials and documents can be class items, because only materials and documents can be BOM components. The class must have a class type that allows it to be used in BOMs. You define this setting in Customizing for classification. In the standard system, material class type 200 and document class type 201 can be used in BOMs. To replace the class with a material, you can: • • •

Assign values to the configurable material Assign values to the class node, using procedures for the BOM item Assign values to the class node, using constraints for the configuration profile

Alternatively, you can start the find objects function for the class and select a material. The procedure you use depends on whether manual changes to the BOM are allowed. The class can be replaced by a classified material component by assigning values to the class node. If no values have been assigned to the class node, the values assigned to the header material are used. The system searches the BOM structure from the bottom up, according to the values assigned to the characteristics of the class node.

152

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintenance and Functions of Selection Conditions

Figure 59: Classified Materials as BOM Items 1

You can enter materials that are classified in a class from SAP R/3 Enterprise classification as components of a BOM item. For example, you can include various packaging materials, such as crates, as BOM items. These packaging materials can be classified in any class of any material class type.

Figure 60: Classified Materials as BOM Items 2

18-02-2004

© 2004 SAP AG. All rights reserved.

153

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

You can use classification data as selection conditions in variant configuration. To do this, you must enter the class type on the item detail screen and select the selection condition indicator. This is an alternative method to using a class node in the BOM; you specify the materials in the BOM directly. For the object to be selected for the BOM of the configurable material, the classification of the object must match the characteristic values currently assigned in variant configuration including characteristics without assigned values. The characteristics used in the classification of these items must also be assigned to the variant class.

154

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintenance and Functions of Selection Conditions

Exercise 8: Selection Conditions in BOMs Exercise Objectives After completing this exercise, you will be able to: • Explode a super BOM in a multilevel configuration • Create selection conditions • Assign the selection conditions to BOM items

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company has decided to use SAP R/3 Enterprise to optimize its storage inventories and maintain every possible end-product variant. During the configuration simulation, you saw that the resulting BOM was the same as the super BOM. As the Product Manager of the company, it is necessary for you to record interdependencies or object dependencies. This will select the appropriate objects from the super BOM to make a BOM that can be used to manufacture the configured product.

Task 1: Check the existing bills of material: PC: T-VPC## 1200 1 Extras: T-VPZ## 1200 1. See PC Customer Example (BOM Structure). The BOM has no dependencies or has incorrect dependencies. 1.

Create selection conditions that select the correct BOM components for the Tower, Minitower, and Desktop, depending on the value assigned to the characteristic T_CAS_##. Maintain data according to the following naming convention: Field Name or Data Type Field Name or Data Type

Values

Dependency name

T_SC_CAS_TW_##

Dependency description

Selection Condition Tower

Dependency group

T-##

Dependency type

Selection condition Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

155

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

Continue in the same way with selection conditions for the: - Minitower T_SC_CAS_MT_## and - Desktop T_SC_CAS_DT_## Enter the source code by choosing the dependency editor pushbutton. Check the source code for syntax errors. Save the source code once the syntax is correct. Change the status of the dependency to released. Save the dependency. 2.

Create selection conditions that select the different CPU BOM components, depending on the value assigned to the characteristic T_CPU_##. Maintain data according to the naming convention described above. Recommended names for selection conditions: T_SC_CPU_01_## T_SC_CPU_02_## T_SC_CPU_03_##

3.

Create selection conditions that select the correct BOM components for the mouse, modem, and keyboard, depending on the values assigned to characteristic T_EXT_##. Maintain data according to the naming convention described above. Recommended names for selection conditions: T_SC_EXT_01_## T_SC_EXT_02_## T_SC_EXT_03_##

Task 2: Assign your dependencies to the appropriate BOM components. 1.

Using change mode for BOM maintenance, assign your dependencies to the appropriate BOM components. Note: The selection conditions for the Extras are assigned to the BOM components in the BOM for the material “Extras“, T-VPZ##, and not the BOM for the PC.

Task 3: Test your solution. 1.

156

Test your solution using the configuration simulation.

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintenance and Functions of Selection Conditions

Solution 8: Selection Conditions in BOMs Task 1: Check the existing bills of material: PC: T-VPC## 1200 1 Extras: T-VPZ## 1200 1. See PC Customer Example (BOM Structure). The BOM has no dependencies or has incorrect dependencies. 1.

Create selection conditions that select the correct BOM components for the Tower, Minitower, and Desktop, depending on the value assigned to the characteristic T_CAS_##. Maintain data according to the following naming convention: Field Name or Data Type Field Name or Data Type

Values

Dependency name

T_SC_CAS_TW_##

Dependency description

Selection Condition Tower

Dependency group

T-##

Dependency type

Selection condition

Continue in the same way with selection conditions for the: - Minitower T_SC_CAS_MT_## and - Desktop T_SC_CAS_DT_## Enter the source code by choosing the dependency editor pushbutton. Check the source code for syntax errors. Save the source code once the syntax is correct.

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

157

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

Change the status of the dependency to released. Save the dependency. a)

BOMs for PC: T-VPC## and Extras: check T-VPZ##. You have no object dependencies so far - delete dependency assignments if necessary. CS02 or CS03= User Menu → Bill of Material → Material BOM → Change Delete assigned object dependencies:

→ Select component and choose Allocations = Ctrl + F1 = → Extras → Object Dependencies → Assignments = Pushbutton → Use the Delete entry pushbutton to delete = Shift + F2 Create selection conditions: CU01 = SAP Menu → Logistics → Central Functions → Variant Configuration → Dependency → Single Dependency → Create or User Menu → Variant Configuration → Dependency → Single Dependency → Create 1. Dependency: T_SC_CAS_TW_## → Enter Description: Selection Condition Tower Dependency Group: T-## Dependency Type: Selection condition → Dependency editor = F7 Syntax: $root.T_CAS_## = ’TW’ → Check andSave (syntax)

→ Release = Status 1 and save (dependency) Create further selection conditions in the same way. Use the copy functions. 2. T_SC_CAS_MT_## Selection condition Minitower Syntax:$root.T_CAS_## = ’MT’ 3. T_SC_CAS_DT_##Selection Condition Desktop Syntax:$root.T_CAS_## = ’DT’

Continued on next page

158

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintenance and Functions of Selection Conditions

2.

Create selection conditions that select the different CPU BOM components, depending on the value assigned to the characteristic T_CPU_##. Maintain data according to the naming convention described above. Recommended names for selection conditions: T_SC_CPU_01_## T_SC_CPU_02_## T_SC_CPU_03_## a)

4.T_SC_CPU_01_## Selection condition slow CPU Syntax:$root.T_CPU_## = ’01’ 5.T_SC_CPU_02_## Selection Condition Medium CPU Syntax:$root.T_CPU_## = ’02’ 6.T_SC_CPU_03_## Selection condition fast CPU Syntax:$root.T_CPU_## = ’03’

3.

Create selection conditions that select the correct BOM components for the mouse, modem, and keyboard, depending on the values assigned to characteristic T_EXT_##. Maintain data according to the naming convention described above. Recommended names for selection conditions: T_SC_EXT_01_## T_SC_EXT_02_##

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

159

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

T_SC_EXT_03_## a)

7.T_SC_EXT_01_## Selection condition Mouse Syntax:$root.T_EXT_## = ’01’ * Mouse 8.T_SC_EXT_02_## Selection condition Modem Syntax:$root.T_EXT_## = ’02’ * Modem 9.T_SC_EXT_03_## Selection condition Keyboard Syntax:$root.T_EXT_## = ’03’ * Keyboard

Task 2: Assign your dependencies to the appropriate BOM components. 1.

Using change mode for BOM maintenance, assign your dependencies to the appropriate BOM components. Note: The selection conditions for the Extras are assigned to the BOM components in the BOM for the material “Extras“, T-VPZ##, and not the BOM for the PC. a)

Assign selection conditions to BOM for PC: CS02 =User Menu → Bill of Material → Material BOM → Change T-VPC## 1200 1 Select item for Tower Extras → Object Dependencies → Assignments = Ctrl + F1 = Pushbutton

Continued on next page

160

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintenance and Functions of Selection Conditions

Dependency: (Relationship in some systems) Enter T_SC_CAS_TW_## or select it by choosing the F4 help and using ”Find by Group” with dependency group T-##. Continue in the same way for other items: Minitower T_SC_CAS_MT_## Desktop: T_SC_CAS_DT_## Standard CPUT_SC_CPU_01_## Medium CPUT_SC_CPU_02_## Fast CPUT_SC_CPU_03_## Note: The selection conditions for the Extras are assigned to the BOM components in the BOM for the material “Extras”, T-VPZ##, and not the BOM for the PC. CS02 = User Menu → Bill of Material → Material BOM → Change T-VPZ## (Extras) 1200 1 Select item for Mouse Extras → Object Dependencies → Assignments Dependency: Enter T_SC_EXT_01_## and go back Continue in the same way for other items: Modem: T_SC_EXT_02_## Keyboard:T_SC_EXT_03_##

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

161

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

Task 3: Test your solution. 1.

Test your solution using the configuration simulation. a)

Test your solution using the configuration simulation. CU50 = SAP Menu → Logistics → Central Functions → Variant Configuration → Environment → Configuration Simulation or User Menu → Variant Configuration → Environment → Configuration Simulation Display values for these three characteristics on the value assignment screen and display the resulting BOM (BOM application PP01 if prompted). Object Dependencies in BOMs and Task Lists Exercises

162

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintenance and Functions of Selection Conditions

Exercise 9: Selection Conditions in Task Lists Exercise Objectives After completing this exercise, you will be able to: • Explode a super task list in configuration • Create selection conditions • Assign the selection condition to various objects in the routing

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company has decided to use SAP R/3 Enterprise to optimize its storage inventories and maintain every possible end-product variant. Configuration modeling affects the routing of the PC. To select the required operation(s) and PRTs, selection conditions, similar to those for the BOM, are needed. As the Product Manager of the company, you should either write new dependencies or use existing and valid dependencies to select objects.

Task 1: You maintained the following routing for your PC T-VPC##. Operation

Work center

Description

10

PC-1

Standard Assembly & Paint

20

PC-1

Installation CPU standard

30

PC-1

Installation CPU medium

40

PC-1

Installation CPU fast

50

PC-1

Installation Extras PRT: PP-FHMS

60

PC-3

Final inspection and packaging

1.

Check the extent to which you need to create new selection conditions to ensure the following: Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

163

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

Operations 20, 30, and 40 are selected according to the value assigned to the CPU characteristic, T_CPU_##. The PRT for installing the Modem depends on the value assigned to the Extras characteristic, T_EXT_##. The PRT is to be selected only if the value 02 = modem is selected.

Task 2: Assign your dependencies to the appropriate operations and production resource/tool. 1.

Using change mode for routing maintenance, assign your dependencies to the appropriate operations and production resource/tool.

Task 3: Test your solution. 1.

Test your solution using the configuration simulation.

Task 4: (Optional) Simulate the routing configuration once again but do not select any of the “Extras“. Display the result. What do you notice about Operation 50, Installation Extras?

164

1.

Use existing dependencies to correct the situation - that this operation is only selected when one of the Extras is selected during configuration.

2.

Create a new dependency that will select this operation only when one of the Extras is selected during configuration.

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintenance and Functions of Selection Conditions

Solution 9: Selection Conditions in Task Lists Task 1: You maintained the following routing for your PC T-VPC##. Operation

Work center

Description

10

PC-1

Standard Assembly & Paint

20

PC-1

Installation CPU standard

30

PC-1

Installation CPU medium

40

PC-1

Installation CPU fast

50

PC-1

Installation Extras PRT: PP-FHMS

60

PC-3

Final inspection and packaging

1.

Check the extent to which you need to create new selection conditions to ensure the following: Operations 20, 30, and 40 are selected according to the value assigned to the CPU characteristic, T_CPU_##. The PRT for installing the Modem depends on the value assigned to the Extras characteristic, T_EXT_##. The PRT is to be selected only if the value 02 = modem is selected. a)

Check the extent to which you need to create new selection conditions: Operations 20, 30, and 40 are selected according to the value assigned to the CPU characteristic, T_CPU_##. The PRT for installing the Modem depends on the value assigned to the Extras characteristic, T_EXT_##. The PRT is to be selected only if the modem is selected. No new selection conditions are required - they already exist.

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

165

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

Task 2: Assign your dependencies to the appropriate operations and production resource/tool. 1.

Using change mode for routing maintenance, assign your dependencies to the appropriate operations and production resource/tool. a)

Assign the dependencies to the appropriate operations and PRTs. CA02 = SAP Menu → Logistics → Production → Master Data → Routings → Routings → Standard Routings → Change or User Menu → Environment → Routings → Standard Routings → Change Material: T-VPC## Plant: 1200

→ Enter Select the operation you require. Extras → Object dependencies → Assignments (or double-click on field in “Object dependencies“ column. T_SC_CPU_01_## (Slow CPU) T_SC_CPU_02_## (Medium CPU) T_SC_CPU_03_## (Fast CPU) To assign the PRT dependency to operation 50, select operation 50, then choose: Go To → Prod.resources/tools Select the PRT and choose Extras → Object Dependencies → Assignments T_SC_EXT_02_## (Modem)

→ Save

Continued on next page

166

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Maintenance and Functions of Selection Conditions

Task 3: Test your solution. 1.

Test your solution using the configuration simulation. a)

Transaction CU50.

Task 4: (Optional) Simulate the routing configuration once again but do not select any of the “Extras“. Display the result. What do you notice about Operation 50, Installation Extras? 1.

Use existing dependencies to correct the situation - that this operation is only selected when one of the Extras is selected during configuration. a)

Additional Activity: Answer: Operation 50 is offered, even if no Extras are selected. The 3 existing selection conditions T_SC_EXT_01_##, T_SC_EXT_02_##, and T_SC_EXT_03_## (mouse, modem, and keyboard) can be assigned to operation 50.

2.

Create a new dependency that will select this operation only when one of the Extras is selected during configuration. a)

A new selection condition with this syntax can be created: $ROOT.T_EXT_## SPECIFIED This can then be assigned to operation 50 Installation Extras.

18-02-2004

© 2004 SAP AG. All rights reserved.

167

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

Lesson Summary You should now be able to: • Create and maintain basic selection conditions • Use class nodes in a bill of material • Use classification data as a selection condition for classified objects in a bill of material

168

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for BOMs and Task Lists

Lesson: Procedures for BOMs and Task Lists Lesson Overview This lesson explains the use of reference characteristics with procedures to change field values in exploded BOMs and task lists.

Lesson Objectives After completing this lesson, you will be able to: •

Use reference characteristics with procedures to change field values in exploded BOMs and task lists (routings)

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company is implementing variant configuration solution of SAP R/3 Enterprise to maintain end-product variants. As the Product Manager of the company, you are responsible for this implementation. You have created the basic selection conditions. Now, you need to use reference characteristics with procedures to change field values in exploded BOMs and task lists.

Use of Reference Characteristics

Figure 61: Use of Reference Characteristics

18-02-2004

© 2004 SAP AG. All rights reserved.

169

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

You can use reference characteristics in actions and procedures to change the values in master data fields. To access a master data field define a reference characteristic by using the appropriate table and field name. These are examples of two reference characteristics: BOMQTY, which refers to field MENGE in the BOM table STPO and another reference characteristic, LABORTIME, which is created by referencing table PLPO and field VGW03.

Procedures for Changing Field Values

Figure 62: Procedure for a BOM Item

For this procedure, you need to use the reference characteristic BOMQTY, which refers to field STPO-MENGE. You refer to this reference characteristic in a procedure. You assign the value you want the characteristic to have if value “Tower“ is assigned to characteristic CASING. You assign this procedure to the BOM item whose quantity you want to change. As soon as the BOM item is selected, the procedure is processed, providing that any conditions attached to it are fulfilled. If you want a characteristic in a dependency to have a value inferred, you must precede the characteristic name with $SELF, to make it clear that values are to be assigned on this level. In the example, characteristic BOMQTY must be referred to with object variable $SELF, to make it clear that the characteristic refers to the current object – the BOM item – and not the BOM header material.

170

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for BOMs and Task Lists

You can check the effect of this procedure by simulating the BOM explosion in the configuration simulation function.

Figure 63: Procedure for an Operation in a Task List

You can also use object dependencies to change field values in task list tables for the routing. For example, you can change a standard value for an operation. To do this, you create a reference characteristic that refers to one of the fields for standard values (VGW01–06) in table PLPO. In a previous example, reference characteristic LABOR was defined for this purpose. In this procedure, the value of reference characteristic LABOR is set to 5 minutes more if the customer chooses a gloss finish. You assign this procedure to the operation. As soon as the operation is selected, the procedure is processed, provided that any conditions attached to it are fulfilled. You can check the effect of the procedure by simulating the task list explosion.

18-02-2004

© 2004 SAP AG. All rights reserved.

171

Unit 6: Object Dependencies in BOMs and Task Lists

172

© 2004 SAP AG. All rights reserved.

PLM140

18-02-2004

PLM140

Lesson: Procedures for BOMs and Task Lists

Exercise 10: Characteristic Value Assignment for Class Nodes Exercise Objectives After completing this exercise, you will be able to: • Maintain the data for replacing a class node in the BOM • Replace a class node with a component required by the customer • Create a reference characteristic • Use reference characteristics in object dependencies

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company has decided to use SAP R/3 Enterprise to optimize its storage inventories and maintain every possible end-product variant. As the Product Manager of the company, you need to maintain the class nodes. In addition, during the configuration modeling, you may need to access certain database fields and modify their values based on certain conditions.

Task 1: In the bill of material for your PC, you have Class node (200) T_VPC_COLOR 1.

To ensure that the class node can be replaced by a classified component when you assign characteristic values, include the characteristics of the class node in your variant class for the PC: Variant class (300) T_VPC##: T_COL_00 Color Casing T_GLO_00 Gloss

2.

Test your solution using the configuration simulation. Test the effects of selecting different characteristic values. Display the additional information on the replaced component.

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

173

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

Task 2: Create the necessary reference characteristic and write the dependency ensuring that if the Tower casing is selected, then two bolt sets are specified in the BOM for the PC. 1.

Create reference characteristic T_QUANT_##, referring to table field STPO-MENGE.

2.

Create procedure T_PROC_QUANT2_##. This will set the component quantity to 2 if the Tower casing is selected.

3.

Assign this procedure to the relevant BOM item (bolt set).

4.

Test your solution using the configuration simulation.

Task 3: (Optional) Create a suitable reference characteristic and write a dependency. 1.

174

Create a suitable reference characteristic and write a dependency that will change the standard value for labor of 10 minutes in the last operation to 15 minutes if the customer selects a gloss finish. Proceed as described above. Check your results.

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for BOMs and Task Lists

Solution 10: Characteristic Value Assignment for Class Nodes Task 1: In the bill of material for your PC, you have Class node (200) T_VPC_COLOR 1.

To ensure that the class node can be replaced by a classified component when you assign characteristic values, include the characteristics of the class node in your variant class for the PC: Variant class (300) T_VPC##: T_COL_00 Color Casing T_GLO_00 Gloss a)

In the variant class (300) T_VPC_##add the characteristics of the class node (200) T_VPC_COLOR: CL02 = User Menu → Classification → Master Data → Classes or SAP Menu → Cross-Application Components → Classification System → Master Data → Classes Class:T_VPC_## Class type: 300

→ Change → CharacteristicsInclude characteristics (of group 00) T_COL_00 Color of Casing T_GLO_00 Gloss 2.

Test your solution using the configuration simulation. Test the effects of selecting different characteristic values.

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

175

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

Display the additional information on the replaced component. a)

Test your solution using the configuration simulation. (Transaction CU50) Test the effects of selecting different characteristic values. For example: Both unspecified => No substitution Both specified => Exact match of required color material Only color specified => Replaced with color material, and so on. Display the additional information on the replaced component.

→ Result Cursor on “I“ at the end of the item line and on “I“ above

Continued on next page

176

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for BOMs and Task Lists

Task 2: Create the necessary reference characteristic and write the dependency ensuring that if the Tower casing is selected, then two bolt sets are specified in the BOM for the PC. 1.

Create reference characteristic T_QUANT_##, referring to table field STPO-MENGE. a)

Change item quantity of bolt set for Tower. Create reference characteristic T_QUANT_##, referring to table field STPO-MENGE. CT04 = User Menu → Classification → Master Data → Characteristics or SAP Menu → Cross-Application Components → Classification System → Master Data → Characteristics Characteristic: T_QUANT_##

→ Create → Straight to additional data Field Name or Data Type Field Name or Data Type

Values

Table name

STPO

Field name

MENGE

All other data is copied from the ABAP Dictionary. Add characteristics group T-##. 2.

Create procedure T_PROC_QUANT2_##. This will set the component quantity to 2 if the Tower casing is selected. a)

+

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

177

Unit 6: Object Dependencies in BOMs and Task Lists

3.

PLM140

Assign this procedure to the relevant BOM item (bolt set). a)

Create the procedure and assign it to the BOM item for the bolt set. (Here a 1-step process - create the dependency during assignment.) CS02= SAP Menu → Logistics → Production → Master Data → Bills of Material → Bill of Material → Material BOM → Change or User Menu → Bill of Material → Material BOM → Change Material: T-VPC## Plant: 1200 BOM Usage: 1 = Production Select item 10 (T-PCS) and choose pushbutton Allocations.

→ Enter the name of the dependency → Enter → Enter Field Name or Data Type Field Name or Data Type

Values

Dependency name

T_PROC_QUANT2_##

Dependency description

Set Component Quantity

Dependency group

T-##

Dependency type

Procedure

Syntax:

$self.T_QUANT_## = 2 if $root.T_CAS_## = ’TW’

→ Check and save syntax → Status = 1 = Released → Save dependency → Save BOM

Continued on next page

178

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for BOMs and Task Lists

4.

Test your solution using the configuration simulation. a)

Test your solution using the configuration simulation. (Transaction CU50)

Task 3: (Optional) Create a suitable reference characteristic and write a dependency. 1.

Create a suitable reference characteristic and write a dependency that will change the standard value for labor of 10 minutes in the last operation to 15 minutes if the customer selects a gloss finish. Proceed as described above. Check your results. a)

Increase the standard value for the operation if gloss finish. Create reference characteristic T_VGW03_##, referring to table field PLPO-VGW03. CT04 = User Menu → Classification → Master Data → Characteristics or SAP Menu → Cross-Application Components → Classification System → Master Data → Characteristics Characteristic: T_VGW03_##

→ Create → Straight to additional data Field Name or Data Type Field Name or Data Type

Values

Table name

PLPO

Field name

VGW03

All other data is copied from the ABAP Dictionary. Add characteristics group T-##. Create the procedure and assign it to the operation. (Here a 1-step process - create the dependency during assignment.) CA02 = Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

179

Unit 6: Object Dependencies in BOMs and Task Lists

PLM140

SAP Menu → Logistics → Production → Master Data → Routings → Routings → Standard Routings → Change or User Menu → Environment → Routings → Standard Routings → Change Material: T-VPC## Plant: 1200 Last operation: Double-click on field in Dependencies column.

→ Enter the name of the dependency (see small table) → Enter → Enter Field Name or Data Type Field Name or Data Type

Values

Dependency name

T_PROC_VGW0315_##

Dependency description

Standard value = 15 if gloss

Dependency group

T-##

Dependency typeSyntax:

Procedure

Syntax:

$self.T_VGW03_## = 15 if $root.T_GLO_00 = ’1’

→ Check and save syntax → Status = 1 = Released → Save dependency and routing → Save BOM Test your solution using the configuration simulation. Transaction CU50. Note: Due to a program error, no info symbol appears on the result screen. However, the change can still be displayed by selecting the last operation and choosing the info button.

180

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for BOMs and Task Lists

Lesson Summary You should now be able to: • Use reference characteristics with procedures to change field values in exploded BOMs and task lists (routings)

18-02-2004

© 2004 SAP AG. All rights reserved.

181

Unit Summary

PLM140

Unit Summary You should now be able to: • Create and maintain basic selection conditions • Use class nodes in a bill of material • Use classification data as a selection condition for classified objects in a bill of material • Use reference characteristics with procedures to change field values in exploded BOMs and task lists (routings)

182

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Test Your Knowledge

Test Your Knowledge 1.

Explain the uses of procedures.

2.

To replace the class with a material, you can: Choose the correct answer(s).

3.

□ □

A B

□

C

□

D

Assign values to the configurable material Assign values to the class node, using procedures for the BOM item Assign values to the class node, using constraints for the configuration profile Assign values to the class type

To use classification data as selection conditions in variant configuration, you must enter the on the item detail screen and select the selection condition indicator. Fill in the blanks to complete the sentence.

4.

You can check the effect of a procedure by simulating the . Fill in the blanks to complete the sentence.

18-02-2004

© 2004 SAP AG. All rights reserved.

183

Test Your Knowledge

PLM140

Answers 1.

Explain the uses of procedures. Answer: Procedures are used to change item data or operation data. Procedures can incorporate recursive calculations. This also allows overwriting.

2.

To replace the class with a material, you can: Answer: A, B, C You cannot assign values to the class type to replace the class with a material.

3.

To use classification data as selection conditions in variant configuration, you must enter the class type on the item detail screen and select the selection condition indicator. Answer: class type

4.

You can check the effect of a procedure by simulating the task list explosion. Answer: task list explosion

184

© 2004 SAP AG. All rights reserved.

18-02-2004

Unit 7 Dependencies for Value Assignment Unit Overview This unit explains the use of preconditions, selection conditions, procedures, and variant tables for value assignment.

Unit Objectives After completing this unit, you will be able to: • • • •

Use preconditions to hide characteristics or individual values Use selection conditions on characteristics for value assignment if certain conditions apply Use procedures to set values Use variant tables in simple dependencies to infer values

Unit Contents Lesson: Preconditions and Selection Conditions ...........................186 Exercise 11: Preconditions and Selection Conditions for Characteristics and Characteristic Values .................................................193 Lesson: Procedures for Value Assignment ..................................204 Exercise 12: Procedures with Variant Tables .......................... 211 Exercise 13: Using Procedures to Set Default Values ................223

18-02-2004

© 2004 SAP AG. All rights reserved.

185

Unit 7: Dependencies for Value Assignment

PLM140

Lesson: Preconditions and Selection Conditions Lesson Overview This lesson describes the use of preconditions to hide characteristics or individual values. It also describes the use of selection conditions on characteristics.

Lesson Objectives After completing this lesson, you will be able to: • •

Use preconditions to hide characteristics or individual values Use selection conditions on characteristics for value assignment if certain conditions apply

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company is implementing variant configuration solution of SAP R/3 Enterprise to maintain end-product variants. You are the Product Manager of the company. You have created object dependencies in BOMs and task lists. Now, you must ensure that your configuration is complete and consistent. To do this, you need to use preconditions to hide characteristics or individual values. Then, you need to use selection conditions on characteristics to require value assignment if certain conditions apply.

Use of Dependencies for Value Assignment • • •

Precondition: Characteristic, characteristic value Selection condition: Characteristics, BOM items, operation, suboperation, sequence, PRT Procedure (Action): Characteristic, characteristic value, BOM items, task list objects, configuration profile

Use of Preconditions for Value Assignment •

•

186

Characteristic values: The characteristic value to which the precondition is assigned appears in the value assignment function only if the condition is fulfilled. Characteristics: The characteristic to which the precondition is assigned appears in the value assignment function only if the condition is fulfilled.

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Preconditions and Selection Conditions

Figure 64: Precondition for a Characteristic Value

If a certain value is set for characteristic CPU, some of the values for characteristic HARDDISK are hidden. In a precondition, you define the circumstances under which a characteristic or characteristic value is hidden. If a CPU other than medium or fast is selected, characteristic HARDDISK no longer has all its possible values offered as choices. If characteristic CPU has no value, all values for characteristic HARDDISK are offered, because this precondition is not violated. This is an important difference between preconditions and selection conditions. A precondition is fulfilled if the condition you enter is either true or not violated. A precondition is fulfilled if: The specified value is selected for the specified characteristic No value is selected for the characteristic The precondition is not fulfilled if a different value is selected for the specified characteristic. You can also use restrictable characteristics to restrict the allowed values of characteristics, as in constraints with an INFERENCES section.

18-02-2004

© 2004 SAP AG. All rights reserved.

187

Unit 7: Dependencies for Value Assignment

PLM140

Figure 65: Precondition for a Characteristic

In a precondition, you define the circumstances under which a characteristic or characteristic value is hidden. In this example, characteristic SOFTWARE is dynamically hidden by assigning the precondition that a HARDDISK must be specified before SOFTWARE is shown. Only when HARDDISK is specified does characteristic SOFTWARE appear on the value assignment screen. If HARDDISK is not specified, characteristic SOFTWARE does not appear on the value assignment screen.

Variant Tables in Preconditions

Figure 66: Structure of a Variant Table

188

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Preconditions and Selection Conditions

To maintain a table: 1. Create a table structure Define single-value characteristics as columns For conditions (preconditions in this case), value assignment alternatives are not needed 2. Maintain table contents

Figure 67: Example of a Variant Table

If you use a table for preconditions, you enter the valid combinations of values for preconditions in the individual table lines. A precondition is only fulfilled if the characteristic values assigned match a table line. This allows you to ensure that your configuration is consistent. You can enter the same combination in more than one line. The lines must be complete. Make sure there are no empty spaces.

18-02-2004

© 2004 SAP AG. All rights reserved.

189

Unit 7: Dependencies for Value Assignment

PLM140

Figure 68: Variant Tables in Preconditions

If you want to display allowed values only in value assignment functions, enter the characteristic value to which the precondition refers in the precondition itself. This means that the value is only displayed if it is allowed by the combinations of values in the table. You assign the precondition to the value that it refers to. If you want to use the precondition to check consistency, you need not enter any characteristic value in the precondition itself. This means that the system does not check whether the entire value combination is allowed until after you have set the value. If the value is not allowed, you see an inconsistency message. You assign the precondition to the characteristic whose values you want to check.

Use of Selections Conditions •

190

Dynamic: The characteristic to which the selection condition is assigned becomes the required characteristic during configuration if the condition is fulfilled.

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Preconditions and Selection Conditions

Figure 69: Selection Condition for a Characteristic

You can use selection conditions to determine that it is mandatory to assign a value to a characteristic. In this example, characteristic SOFTWARE becomes a required entry characteristic during value assignment. You can select the required entry option in the characteristic. However, this makes the characteristic a permanently required characteristic, and an inconsistency might occur if the characteristic is hidden by object dependencies. For this reason, it is sometimes better to create a selection condition for the characteristic.

18-02-2004

© 2004 SAP AG. All rights reserved.

191

Unit 7: Dependencies for Value Assignment

192

© 2004 SAP AG. All rights reserved.

PLM140

18-02-2004

PLM140

Lesson: Preconditions and Selection Conditions

Exercise 11: Preconditions and Selection Conditions for Characteristics and Characteristic Values Exercise Objectives After completing this exercise, you will be able to: • Use preconditions to ensure that hard disks are not available for all values assigned to other characteristics, such as the CPU • Use preconditions to ensure that a characteristic, such as Software, can only be selected if the hard disk is already selected • Define a characteristic, such as Software, as a required characteristic under certain circumstances, without defining it as a required characteristic all the time

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company has decided to use SAP R/3 Enterprise to optimize its storage inventories and maintain every possible end-product variant. As the Product Manager of the company, you need to ensure that value assignment is complete and consistent. You need to ensure that it is only possible to select combinations of values that are supported for production. You also need to ensure that the customer enters the relevant information in the sales order.

Task 1: Create characteristics using the copy function whenever appropriate. 1.

Create the following characteristics, using the copy function whenever appropriate: Field Name or Data Type Field Name or Data Type

Values

Characteristic

T_HD_##

Description

Hard Disk in GB

Group

T-##

Format/Number of chars

NUM/2

Characteristic values

10, 20, 40, 60

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

193

Unit 7: Dependencies for Value Assignment

PLM140

If you copy, delete the dependency assignments that are copied. Field Name or Data Type Field Name or Data Type

Values

Characteristic

T_SW_##

Description

Software

Group

T-##

Format/Number of chars

CHAR/1 Multiple Values

Values/Descriptions

A Access E Excel W Word

If you copy, delete the dependency assignments that are copied. Assign the characteristics to your PC class T_VPC_##. Optional: Try to keep to the following sequence of characteristics (see solution): 1. PC Casing 2. CPU of PC 3. Extras for PC 4. Hard disk 5. Software 6. Color (Class Node) 7. Gloss (Class Node)

Task 2: If the customer chooses a medium or fast CPU, the values of 40 or 60 GB of the hard disk characteristic T_HD_## are available for selection. 1.

Create a precondition to accomplish this: Field Name or Data Type

Values

Dependency name

T_PRE_CPU23_##

Dependency description

If CPU is medium or fast

Dependency group

T-##

Assign the precondition to the appropriate objects.

Continued on next page

194

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Preconditions and Selection Conditions

Task 3: If a hard disk is selected, characteristic Software, T_SW_##, is available. 1.

Create a precondition to accomplish this: Field Name or Data Type

Values

Dependency name

T_PRE_HD_##

Dependency description

if hard disk is specified

Dependency group

T-##

Assign the precondition to the appropriate object.

Task 4: The characteristic Software, T_SW_##, must be assigned a value if the hard disk is greater than 20 GB and any value is assigned to the casing. 1.

Create a selection condition to accomplish this: Field Name or Data Type

Values

Dependency name

T_SC_HD20_CAS_##

Dependency description

If > 20 GB and with casing

Dependency group

T-##

Assign the selection condition to the appropriate object.

Task 5: Check the effect of your dependencies using configuration simulation. 1.

Determine which hard disks are available if the following CPUs are selected: - No CPU - Slow CPU - Medium CPU - Fast CPU

18-02-2004

2.

Determine which characteristics are not always displayed. Why?

3.

Which characteristics are required characteristics and when? Why?

4.

Display the object dependencies for characteristics and values in the configuration simulation.

© 2004 SAP AG. All rights reserved.

195

Unit 7: Dependencies for Value Assignment

PLM140

Solution 11: Preconditions and Selection Conditions for Characteristics and Characteristic Values Task 1: Create characteristics using the copy function whenever appropriate. 1.

Create the following characteristics, using the copy function whenever appropriate: Field Name or Data Type Field Name or Data Type

Values

Characteristic

T_HD_##

Description

Hard Disk in GB

Group

T-##

Format/Number of chars

NUM/2

Characteristic values

10, 20, 40, 60

If you copy, delete the dependency assignments that are copied. Field Name or Data Type Field Name or Data Type

Values

Characteristic

T_SW_##

Description

Software

Group

T-##

Format/Number of chars

CHAR/1 Multiple Values

Values/Descriptions

A Access E Excel W Word

If you copy, delete the dependency assignments that are copied. Assign the characteristics to your PC class T_VPC_##. Optional: Try to keep to the following sequence of characteristics (see solution): 1. PC Casing 2. CPU of PC 3. Extras for PC Continued on next page

196

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Preconditions and Selection Conditions

4. Hard disk 5. Software 6. Color (Class Node) 7. Gloss (Class Node) a)

Create the following characteristics, using the copy function whenever appropriate: CT04 = User Menu → Classification → Master Data → Characteristics or SAP Menu → Cross-Application Components → Classification System → Master Data → Characteristics Characteristic: T_HD_## (Hard Disk in GB)

→ Create With Reference Select Template: Characteristic: T_HD_00

→ Enter → Enter Check whether or not the copy matches the data given in the exercise. Change the characteristics group and delete any dependency assignments that have been copied with the cursor on value 40 GB. Choose the Object Dependencies pushbutton for the purpose and click the Delete entry pushbutton. Proceed in the same way for 60 GB. Characteristic: T_SW_## (Software)

→ Create With Reference Select Template: Characteristic: T_SW_00

→ Enter → Enter

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

197

Unit 7: Dependencies for Value Assignment

PLM140

Check whether or not the copy matches the data given in the exercise. Change the characteristics group and delete any dependency assignments that have been copied in the basic data. Choose the Object Dependencies pushbutton for the purpose and then click the Delete entry pushbutton twice. Assign the characteristics to your PC class T_VPC##. Try to keep to the given sequence of characteristics: CL02 = User Menu → Classification → Master Data → Classes or SAP Menu → Cross-Application Components → Classification System → Master Data → Classes Class: T_VPC_## Class type: 300

→ Change → Characteristics Option 1 (insert in correct position immediately): Select T_COL_00 and choose the Insert characteristic pushbutton twice. Insert T_HD_## (hard disk) and T_SW_## (software). Option 2 (moving after insertion): Insert T_HD_## (hard disk) and T_SW_## (software). Now, select T_HD_##, place the cursor on T_COL_00, and choose the Move pushbutton. Now, select T_SW_##, place the cursor on T_COL_00, and choose the Move pushbutton.

Task 2: If the customer chooses a medium or fast CPU, the values of 40 or 60 GB of the hard disk characteristic T_HD_## are available for selection. 1.

Create a precondition to accomplish this: Field Name or Data Type

Values

Dependency name

T_PRE_CPU23_##

Dependency description

If CPU is medium or fast

Dependency group

T-##

Continued on next page

198

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Preconditions and Selection Conditions

Assign the precondition to the appropriate objects. a)

If the customer chooses a medium or fast CPU, the values of 40 or 60 GB of the hard disk characteristic are available for selection. Here a 1-step process - create the dependency during assignment. CT04 = User Menu → Classification → Master Data → Characteristics or SAP Menu → Cross-Application Components → Classification System → Master Data → Characteristics Characteristic: T_HD_## (Hard Disk in GB)

→ Change → Values Select 40 GB and choose the Object Dependencies pushbutton. Field Name or Data Type Field Name or Data Type

Values

Dependency name

T_PRE_CPU23_##

Dependency description

If CPU is medium or fast

Dependency group

T-##

Dependency type

Precondition

Syntax:

$self.T_CPU_## in (’02’, ’03’)

→ Check and save syntax → Release and save dependency Select 60 GB and choose Object Dependencies pushbutton

Task 3: If a hard disk is selected, characteristic Software, T_SW_##, is available. 1.

Create a precondition to accomplish this:

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

199

Unit 7: Dependencies for Value Assignment

PLM140

Field Name or Data Type

Values

Dependency name

T_PRE_HD_##

Dependency description

if hard disk is specified

Dependency group

T-##

Assign the precondition to the appropriate object. a)

If a hard disk has already been selected, characteristic Software, T_SW_##, is available. (Here a 1-step process - create the dependency during assignment.) CT04 = User Menu → Classification → Master Data → Characteristics or SAP Menu → Cross-Application Components → Classification System → Master Data → Characteristics Characteristic: T_SW_## (Software)

→ Change → Basic data Object Dependencies pushbutton Field Name or Data Type Field Name or Data Type

Values

Dependency name

T_PRE_HD_##

Dependency description

only if hard disk is specified

Dependency group

T-##

Dependency type

Precondition

Syntax:

$self.T_HD_## SPECIFIED

→ Check and save syntax → Release and save dependency

Continued on next page

200

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Preconditions and Selection Conditions

Task 4: The characteristic Software, T_SW_##, must be assigned a value if the hard disk is greater than 20 GB and any value is assigned to the casing. 1.

Create a selection condition to accomplish this: Field Name or Data Type

Values

Dependency name

T_SC_HD20_CAS_##

Dependency description

If > 20 GB and with casing

Dependency group

T-##

Assign the selection condition to the appropriate object. a)

The characteristic Software, T_SW_##, must be assigned a value if the hard disk is bigger than 20 GB and any value is assigned to the casing. Create a selection condition to accomplish this: In change mode, in the characteristic for software, go back to the screen:

→ Basic data Object Dependencies pushbutton

→ Enter the name of the dependency → Enter → Enter Field Name or Data Type Field Name or Data Type

Values

Dependency name

T_SC_HD20_CAS_##

Dependency description

If > 20 GB and with casing

Dependency group

T-##

Dependency type

Selection condition

Syntax:

$self.T_HD_## > 20 and $self.T_CAS_## specified

→ Check and save syntax → Release and save dependency Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

201

Unit 7: Dependencies for Value Assignment

PLM140

Task 5: Check the effect of your dependencies using configuration simulation. 1.

Determine which hard disks are available if the following CPUs are selected: - No CPU - Slow CPU - Medium CPU - Fast CPU a)

Check the effect of your dependencies using configuration simulation. Determine which hard disks are available if the following CPUs are selected: - No CPU - All - Slow CPU - All except 40 and 60 GB hard disks - Medium CPU - All - Fast CPU - All

2.

Determine which characteristics are not always displayed. Why? a)

Determine which characteristics are not always displayed. Why? T_SW_## “Software” See “With excluded“ indicator in the settings or the “Hidden Characteristics“ pushbutton.

3.

Which characteristics are required characteristics and when? Why? a)

T_SW_## (Software) if the selection condition is fulfilled. T_CPU_## (CPU of PC) is created as a permanent required entry. You cannot leave the value assignment screen when required characteristics do not have values.

4.

Display the object dependencies for characteristics and values in the configuration simulation. a)

202

Display the object dependencies for characteristics and values in the configuration simulation. (Use F4 help)

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Preconditions and Selection Conditions

Lesson Summary You should now be able to: • Use preconditions to hide characteristics or individual values • Use selection conditions on characteristics for value assignment if certain conditions apply

18-02-2004

© 2004 SAP AG. All rights reserved.

203

Unit 7: Dependencies for Value Assignment

PLM140

Lesson: Procedures for Value Assignment Lesson Overview This lesson explains the use of procedures to set values and the use of variant tables in simple dependencies to infer values.

Lesson Objectives After completing this lesson, you will be able to: • •

Use procedures to set values Use variant tables in simple dependencies to infer values

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company is implementing variant configuration solution of SAP R/3 Enterprise to maintain end-product variants. You are the Product Manager of the company. You are in the process of ensuring that your configuration is complete and consistent. You have used preconditions to hide characteristics or individual values. You have also used selection conditions on characteristics to require value assignment if certain conditions apply. Now, you need to set and infer values using procedures and variant tables.

204

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Use of Procedures

Figure 70: Procedures

You can assign procedures to the following objects: • • •

• •

The characteristic value that triggers the procedure. The characteristic that triggers the procedure. The configuration profile of the configurable object. It is easier to manage procedures assigned to the configuration profile, because they are all in one place. BOM items – for example, to change the quantity. Operations – for example, to change the standard values.

The processing sequence of procedures is defined at dependency assignment level. Procedures can overwrite values set by other procedures. In contrast, if different values are set for a single-value characteristic by actions, constraints, or user entries, an inconsistency occurs. If two procedures set the value of a single-value characteristic, the last in the sequence wins out.

18-02-2004

© 2004 SAP AG. All rights reserved.

205

Unit 7: Dependencies for Value Assignment

PLM140

This means you need to ensure that the sequence of procedures is correct otherwise the wrong value could be set. •

Negation of built-in conditions:

•

– not specified – not type_of – not ... in Recursion

•

– Figure = Figure + 1 Setting of default values

•

– $set_default – $del_default Additional expressions – – –

$sum_parts $count_parts $set_pricing_factor

The syntax of procedures is similar to the syntax of actions, but additional expressions are allowed. Procedures are always used for pricing (here also $SET_PRICING_FACTOR). You can use the following elements in procedures only: NOT SPECIFIED NOT TYPE_OF NE (identical to NOT IN ) $COUNT_PARTS: you can calculate the sum of the quantity of BOM components. $SUM_PARTS: you can calculate the sum of the values assigned to a numeric characteristic for individual objects. As well as using procedures to infer values, you can use procedures to: Access values that were changed by a procedure, to change them again (Figure = Figure +1) Set “soft“ values, which can be overwritten by the user or another procedure, or deleted altogether ($SET_DEFAULT, $DEL_DEFAULT)

206

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Figure 71: Procedure for a Characteristic Value

This procedure can also be assigned to the configuration profile. To get the same effect, the syntax would have to be as follows: ($self.CASING = ‘TOWER’, $self CPU = ‘fast’, $self.EXTRAS = ’MOUSE’, $self. ........................ ) IF $root.PACKAGE eq ’LUXURY’

Figure 72: Procedure for the Configuration Profile

18-02-2004

© 2004 SAP AG. All rights reserved.

207

Unit 7: Dependencies for Value Assignment

PLM140

Variant Tables and Procedures

Figure 73: Variant Tables and Procedures (Actions)

You can assign a variant table to a procedure (action) to calculate missing values in a configuration. If the interdependencies between objects are more complex, you can assign variant tables to a constraint. To use actions and procedures with variant tables to infer values, you define value assignment alternatives. A value assignment alternative describes which table fields are key fields and which are data fields. The key fields determine the values in the data fields. Characteristics that refer to data fields in the table must be preceded with the variable $SELF, to ensure that values can be inferred for these characteristics.

208

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Figure 74: Example of a Variant Table with Key Fields

Values inferred using variant tables must be unambiguous: a table cannot contain more than one line with the same key fields.

Procedure for Setting a Default Value

Figure 75: Procedure for Setting a Default Value

18-02-2004

© 2004 SAP AG. All rights reserved.

209

Unit 7: Dependencies for Value Assignment

PLM140

Figure 76: Procedure: $SET_DEFAULT and $DEL_DEFAULT

Procedures for Recursion and Overwriting

Figure 77: Procedures: Recursion and Overwriting

210

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Exercise 12: Procedures with Variant Tables Exercise Objectives After completing this exercise, you will be able to: • Maintain a variant table that can be accessed by a procedure • Maintain a procedure that accesses a table

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company has decided to use SAP R/3 Enterprise to optimize its storage inventories and maintain every possible end-product variant. It is necessary to automatically assign values to characteristics, which then cannot be changed manually. If there are many interdependencies, you, as the Product Manager of the company, can use variant tables in procedures to make the model easier to understand, and to make the allowed combinations of values easier to maintain.

Task 1: Create characteristics using the copy function. 1.

Create the following characteristics, using the copy function whenever appropriate: Field Name or Data Type

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

211

Unit 7: Dependencies for Value Assignment

PLM140

Field Name or Data Type

Values

Characteristic

T_MED_##

Description

Multimedia package

Group

T-##

Format/Number of chars

CHAR/2

Values/Descriptions

01/Standard Package 02/Luxury Package 03/Audiofile Package

Field Name or Data Type

Values

Characteristic

T_CD_##

Description

CD drive

Group

T-##

Format/Number of chars

CHAR/2

Values/Descriptions

01/Slow 02/Medium 03/Fast

Field Name or Data Type

Continued on next page

212

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Field Name or Data Type

Values

Characteristic

T_SPE_##

Description

Speakers in Watts

Group

T-##

Format/Number of chars/Unit of measure

NUM/2/ W

Values/Descriptions 10 W 15 W 40 W Assign the characteristics to your PC class T_VPC_## at the end of the list. (Optional: Define an interface design TVPC## with the following characteristics: Tab page 1: 1. PC Casing 2. CPU of PC 3. Extras for PC 4. Hard disk 5. Software Tab page 2: 1. PC Casing 6. Color (Class Node) 7. Gloss (Class Node) Tab page 3: 8. Multimedia package 9. CD drive 10. Speakers Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

213

Unit 7: Dependencies for Value Assignment

PLM140

Task 2: Maintain the allowed value combinations for the Multimedia Package, CD Drive, and Speakers in a table. The value assigned to characteristic Multimedia Package infers the values for the other two characteristics, namely CD Drive and Speakers. 1.

Create table structure T_TAB_VPC## using the three characteristics identified above. Maintain a value assignment alternative that infers the values of the other two characteristics from the value assigned to characteristic Multimedia Package (key field).

2.

Assign the following characteristics (columns) and the characteristic values (rows) to table T_TAB_VPC##: T_MED_## T_CD_## T_SPE_## Multimedia package CD drive Speaker in W 01 01 10 02 02 15 03 03 40 Use the F4 help (double click) to maintain the table contents.

3.

Create a procedure with a reference to this variant table and assign the procedure to the configuration profile of your PC. Create the following procedure:

4.

Field Name or Data Type

Values

Dependency name

T_PROC_TABLE_##

Dependency description

Value inference with table

Dependency group

T-##

Test your solution using the configuration simulation. Use the explanation function on the values inferred for characteristics T_CD_## (CD Drive) and T_SPE_## (Speakers).

214

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Solution 12: Procedures with Variant Tables Task 1: Create characteristics using the copy function. 1.

Create the following characteristics, using the copy function whenever appropriate: Field Name or Data Type Field Name or Data Type

Values

Characteristic

T_MED_##

Description

Multimedia package

Group

T-##

Format/Number of chars

CHAR/2

Values/Descriptions

01/Standard Package 02/Luxury Package 03/Audiofile Package

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

215

Unit 7: Dependencies for Value Assignment

PLM140

Field Name or Data Type

Values

Characteristic

T_CD_##

Description

CD drive

Group

T-##

Format/Number of chars

CHAR/2

Values/Descriptions

01/Slow 02/Medium 03/Fast

Field Name or Data Type Field Name or Data Type

Values

Characteristic

T_SPE_##

Description

Speakers in Watts

Group

T-##

Format/Number of chars/Unit of measure

NUM/2/ W

Values/Descriptions 10 W 15 W 40 W Assign the characteristics to your PC class T_VPC_## at the end of the list. (Optional: Define an interface design TVPC## with the following characteristics: Continued on next page

216

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Tab page 1: 1. PC Casing 2. CPU of PC 3. Extras for PC 4. Hard disk 5. Software Tab page 2: 1. PC Casing 6. Color (Class Node) 7. Gloss (Class Node) Tab page 3: 8. Multimedia package 9. CD drive 10. Speakers a)

Create the following characteristics, using the copy function whenever appropriate: CT04 = User Menu → Classification → Master Data → Characteristics or SAP Menu → Cross-Application Components → Classification System → Master Data → Characteristics Characteristic: T_MED_##(Multimedia package) → Create With Reference Select Template: Characteristic:T_MED_00

→ Enter → Enter Check whether or not the copy matches the data given in the exercise. Change the characteristics group. Characteristic:T_CD_##(CD drive)

→ Create With Reference Select Template: Characteristic:T_CD_00

→ Enter Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

217

Unit 7: Dependencies for Value Assignment

PLM140

→ Enter Check whether or not the copy matches the data given in the exercise. Change the characteristics group. Characteristic:T_SPE_## (Speakers) → Create With Reference Select Template: Characteristic:T_SPE_00

→ Enter → Enter Check whether or not the copy matches the data given in the exercise Change the characteristics group. Assign the characteristics to your PC class T_VPC##. CL02 = User Menu → Classification → Master Data → Classes orSAP Menu → Cross-Application Components → Classification System → Master Data → Classes Class:T_VPC_## Class type:300

→ Change → Characteristics (Optional:Maintain interface design)

→ Configuration simulation; On value assignment screen: Characteristics group: PART1 Flag:Tab

→ Enter ⇒ Design: Char.Val.Assgmt

→ Pushbutton: Characteristics = Ctrl + F5 Select: Casing CPU Extras Hard disk Software → Enter

→ Save Same for PART2: Casing Continued on next page

218

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Color Gloss Same for PART3: Multimedia package CD drive Speakers

Task 2: Maintain the allowed value combinations for the Multimedia Package, CD Drive, and Speakers in a table. The value assigned to characteristic Multimedia Package infers the values for the other two characteristics, namely CD Drive and Speakers. 1.

Create table structure T_TAB_VPC## using the three characteristics identified above. Maintain a value assignment alternative that infers the values of the other two characteristics from the value assigned to characteristic Multimedia Package (key field). a)

Create a variant table and use a procedure to infer values with this table. Create table structure T_TAB_VPC##: CU61 = SAP Menu → Logistics → Central Functions → Variant Configuration → Tools → Table Structure → Create or User Menu → Variant Configuration → Tools → Table Structure → Create Table:T_TAB_VPC##

→ Enter Description: Multimedia packages Status:1 = Released Group:T-##

→ Characteristics 2.

Assign the following characteristics (columns) and the characteristic values (rows) to table T_TAB_VPC##: T_MED_## T_CD_## T_SPE_## Multimedia package CD drive Speaker in W 01 01 10 Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

219

Unit 7: Dependencies for Value Assignment

PLM140

02 02 15 03 03 40 Use the F4 help (double click) to maintain the table contents. a)

T_MED_## Only select Key Field once: here for the first characteristic. T_CD_## T_SPE_## Maintain table contents: CU60 = SAP Menu → Logistics → Central Functions → Variant Configuration → Tools → Table Contents → Maintain or User Menu → Variant Configuration → Tools → Table Contents → Maintain Table: T_TAB_VPC##

→ Maintain (Entries according to list using double-click = possible entries and save) If you wish, you can change the display options for values by choosing the relevant pushbutton and selecting Value and description. Create procedure with table query: (Here, a 1-step process create the dependency during assignment.) CU42 = SAP Menu → Logistics → Central Functions → Variant Configuration → Configuration Profile → Change or User Menu → Variant Configuration → Configuration Profile → Change

→ Material: T-VPC## 3.

Create a procedure with a reference to this variant table and assign the procedure to the configuration profile of your PC. Create the following procedure:

Continued on next page

220

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Field Name or Data Type

Values

Dependency name

T_PROC_TABLE_##

Dependency description

Value inference with table

Dependency group

T-##

a)

→ Enter → Double-click on profile → Dependency Assignments Field Name or Data Type

Values

Dependency name

T_PROC_TABLE_##

Dependency description

Value inference with table

Dependency group

T-##

Syntax:

Procedure Table T_TAB_VPC## (T_MED_## = $root.T_MED_##, T_CD_## = $self.T_CD_##, T_SPE_## = $self.T_SPE_##)

→ Check and save syntax → Release and save dependency 4.

Test your solution using the configuration simulation. Use the explanation function on the values inferred for characteristics T_CD_## (CD Drive) and T_SPE_## (Speakers). a)

Test your solution using the configuration simulation. Use the explanation function on the values inferred for characteristics T_CD_## (CD Drive) and T_SPE_## (Speakers). (Info pushbutton)

18-02-2004

© 2004 SAP AG. All rights reserved.

221

Unit 7: Dependencies for Value Assignment

222

© 2004 SAP AG. All rights reserved.

PLM140

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Exercise 13: Using Procedures to Set Default Values Exercise Objectives After completing this exercise, you will be able to: • Define the blue casing as a default if a tower casing is selected

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company has decided to use SAP R/3 Enterprise to optimize its storage inventories and maintain every possible end-product variant. You are the Product Manager of the company. You need to set default values in characteristics maintenance for variant configuration.

Task 1: If the value “Tower” is assigned to characteristic T_CAS_##, you want the default color for the casing to be blue “without gloss”. 1.

Create procedure T_PROC_DEFAULT_## to do this. Dependency group: T-## Dependency Type: Procedure Assign this procedure to the configuration profile of your material T-VPC##.

Task 2: Test your solution using the configuration simulation. 1.

Can you overwrite the default value? What happens if the procedure is processed after you have assigned a value to the color characteristic manually? What would happen if you used an action to set a default value instead of an procedure?

18-02-2004

© 2004 SAP AG. All rights reserved.

223

Unit 7: Dependencies for Value Assignment

PLM140

Solution 13: Using Procedures to Set Default Values Task 1: If the value “Tower” is assigned to characteristic T_CAS_##, you want the default color for the casing to be blue “without gloss”. 1.

Create procedure T_PROC_DEFAULT_## to do this. Dependency group: T-## Dependency Type: Procedure

Continued on next page

224

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Assign this procedure to the configuration profile of your material T-VPC##. a)

(Here a 1-step process - create the dependency during assignment.) CU42 = SAP Menu → Logistics → Central Functions → Variant Configuration → Configuration Profile → Change or User Menu → Variant Configuration → Configuration Profile → Change Material:T-VPC##

→ Enter → Double-click on profile → Dependency Assignments (top of screen, not in basic data) → New entries Field Name or Data Type

Values

Dependency name

T_PROC_DEFAULT_##

Dependency description

Default value color gloss T-##

Dependency group Procedure Dependency type ( Syntax: $SET_DEFAULT ($self, T_COL_00, ’02’), $SET_DEFAULT ($self, T_GLO_00, ’0’) ) IF $root.T_CAS_## = ’TW’

→ Check and save syntax → Release and save dependency

Task 2: Test your solution using the configuration simulation. 1.

Can you overwrite the default value? Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

225

Unit 7: Dependencies for Value Assignment

PLM140

What happens if the procedure is processed after you have assigned a value to the color characteristic manually? What would happen if you used an action to set a default value instead of an procedure? a)

Test your solution using the configuration simulation. Can you overwrite the default value blue for color or without gloss for gloss for the tower? Yes What happens if the procedure is processed after you have assigned a value to the color characteristic manually? The procedure is executed, but it does not overwrite the value entered manually. If blue has already been selected manually, the configurator records the assigned value as assigned by the user and as a system default. What would happen if you used an action to set a default value instead of an procedure? The same syntax would return a syntax error. If you had not used $set_default to set the value, the value would be a hard value. This leads to inconsistencies if an attempt is made to set another value either before or after.

226

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Procedures for Value Assignment

Lesson Summary You should now be able to: • Use procedures to set values • Use variant tables in simple dependencies to infer values

18-02-2004

© 2004 SAP AG. All rights reserved.

227

Unit Summary

PLM140

Unit Summary You should now be able to: • Use preconditions to hide characteristics or individual values • Use selection conditions on characteristics for value assignment if certain conditions apply • Use procedures to set values • Use variant tables in simple dependencies to infer values

228

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Test Your Knowledge

Test Your Knowledge 1.

The characteristic to which the precondition is assigned appears in the value assignment function only if . Fill in the blanks to complete the sentence.

2.

In a , you define the circumstances under which a characteristic or characteristic value is hidden. Fill in the blanks to complete the sentence.

3.

Explain the circumstances when it is better to create a selection condition for the characteristic.

4.

Only procedures can overwrite values set by other procedures. Determine whether this statement is true or false.

□ □ 5.

True False

Which of the following statements are true for procedures? Choose the correct answer(s).

6.

□

A

□

B

□ □

C D

You can assign procedures to the characteristic value that triggers the procedure. If two procedures set the value of a single-value characteristic, the last in the sequence wins out. Procedures cannot overwrite values set by other procedures. Two procedures cannot set the value of a single-value characteristic.

A table can contain more than one line with the same key fields. Determine whether this statement is true or false.

□ □

18-02-2004

True False

© 2004 SAP AG. All rights reserved.

229

Test Your Knowledge

PLM140

Answers 1.

The characteristic to which the precondition is assigned appears in the value assignment function only if the condition is fulfilled. Answer: the condition is fulfilled

2.

In a precondition, you define the circumstances under which a characteristic or characteristic value is hidden. Answer: precondition

3.

Explain the circumstances when it is better to create a selection condition for the characteristic. Answer: You can select the required entry option in the characteristic itself. However, this makes the characteristic a permanently required characteristic, and an inconsistency might occur if the characteristic is hidden by object dependencies. For this reason, it is sometimes better to create a selection condition for the characteristic.

4.

Only procedures can overwrite values set by other procedures. Answer: True Only procedures can overwrite values set by other procedures (except default values).

5.

Which of the following statements are true for procedures? Answer: A, B Two procedures can set the value of a single-value characteristic. Moreover, procedures can overwrite values set by other procedures.

6.

A table can contain more than one line with the same key fields. Answer: False A table cannot contain more than one line with the same key fields.

230

© 2004 SAP AG. All rights reserved.

18-02-2004

Unit 8 Constraints Unit Overview This unit explains constraints, the structure of a constraint, and the creation of simple constraints.

Unit Objectives After completing this unit, you will be able to: • • • •

Explain the use of sections of a constraint Create simple constraints in constraint nets Process equations and tables that cannot be processed by actions Use restrictable characteristics

Unit Contents Lesson: Creating Constraints .................................................232 Lesson: Structure of a Constraint.............................................237 Exercise 14: Constraint in Single-Level Configuration ................245 Exercise 15: Constraint in Multilevel Configuration with Complete Model of a Multilevel Configuration Task ...............................249

18-02-2004

© 2004 SAP AG. All rights reserved.

231

Unit 8: Constraints

PLM140

Lesson: Creating Constraints Lesson Overview This lesson describes the use of sections of a constraint. In addition, it explains how to create simple constraints in constraint nets.

Lesson Objectives After completing this lesson, you will be able to: • •

Explain the use of sections of a constraint Create simple constraints in constraint nets

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company is implementing variant configuration solution of SAP R/3 Enterprise to maintain end-product variants. You are the Product Manager of the company and are responsible for the successful implementation of variant configuration. You realize that the company also has configurable products that consist of multiple configurable assemblies. A more sophisticated approach is needed to perform multilevel configuration. You need to use constraints for this purpose.

Overview of Constraints • • • •

They infer values and check the consistency of values between any objects in a configuration task. They are designed for multilevel configuration. They are also useful for single-level configuration. They are only active during interactive configuration.

This dependency type is mainly for intensively interactive configuration tasks and for configuration tasks in which you need to take into account the dependencies between the characteristics of several objects. The main purpose of constraints is to check the consistency of a configuration.

232

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Creating Constraints

Constraints have the following distinguishing features: • • •

•

•

•

You can use constraints to describe the dependencies between completely different objects and their characteristics. Constraints are used to store information on conditions that must be fulfilled if the configuration is to be consistent. Constraints are not directly assigned to individual objects. They are grouped together to form dependency nets and assigned to a configurable material in the configuration profile. In constraints, you enter objects in their general form of expression, without using $SELF, $ROOT, or $PARENT to identify objects. As a rule, you refer to objects in constraints by entering the class to which the objects are assigned. Constraints are declarative dependencies. The processing sequence of constraints and the point in time when constraints are processed are not relevant. Constraints are not processed in a specific order. You cannot determine when a specific constraint is used.

In any processing situation, a constraint is only processed once. However, if a value that is relevant to the constraint is changed, the constraint is triggered again.

Figure 78: Complex Multilevel Configuration

18-02-2004

© 2004 SAP AG. All rights reserved.

233

Unit 8: Constraints

PLM140

Creating Constraints Within a Dependency Net

Figure 79: Creating a Constraint

Constraints can only be created locally within a dependency net. Dependency nets group constraints together and contain central control parameters. To create a constraint: 1. Create a dependency net. You create dependency nets under a separate menu option in the variant configuration menu. You only create the basic data in the dependency net, and release the net once it is ready. If you want to include further constraints in a dependency net, choose Change dependency net. 2. To create individual constraints, choose Assignments in the dependency net. Like other simple dependencies, a constraint comprises basic data and source code. After you have created a constraint, you can change it by double-clicking it in the dependency net. 3. Assign the dependency net to the configuration profile. You cannot assign a dependency net to other object types. Constraints can only be processed in a configuration if the dependency net and constraints are released.

234

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Creating Constraints

Figure 80: Dependency Net for Header Material

18-02-2004

© 2004 SAP AG. All rights reserved.

235

Unit 8: Constraints

PLM140

Lesson Summary You should now be able to: • Explain the use of sections of a constraint • Create simple constraints in constraint nets

236

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

Lesson: Structure of a Constraint Lesson Overview This lesson describes how to process equations and tables that cannot be processed by actions. In addition, it explains how to use restrictable characteristics.

Lesson Objectives After completing this lesson, you will be able to: • •

Process equations and tables that cannot be processed by actions Use restrictable characteristics

Business Example ABC Motors is an automobile manufacturing company. It manufactures various models of cars. The company is implementing variant configuration solution of SAP R/3 Enterprise to maintain end-product variants. You are the Product Manager of the company and are responsible for the successful implementation of variant configuration. The company has configurable products that consist of multiple configurable assemblies. You have to use constraints to perform this multilevel configuration. Now, you need to create the structure of a constraint using objects, conditions, restrictions, and inferences.

OBJECTS Section • • •

•

OBJECTS: Declaration of all classes and objects used CONDITION: Prerequisite for processing the constraint RESTRICTION(S): Restriction that must apply between the elements in the OBJECTS section: Value inference and consistency check; Direct or with reference to functions/tables INFERENCES: Definition of which characteristic values are to be determined

There are four sections in a constraint. Each section is identified by a keyword. The keyword is followed by a colon. Each section ends with a period. OBJECTS: In this section, you specify the objects that are relevant to the constraint. You must specify all objects that are addressed in the constraint. You can also define variables for objects or characteristics.

18-02-2004

© 2004 SAP AG. All rights reserved.

237

Unit 8: Constraints

PLM140

CONDITION: The condition entered here must be fulfilled to process the constraint. You do not need to enter a condition in a constraint. You can leave out the CONDITION section. However, if you enter the keyword CONDITION, you must enter a condition. RESTRICTIONS: In this section, you enter the interdependencies that must exist between the objects and characteristics for the configuration to be consistent. You must enter a restriction in a constraint. INFERENCES: In this section, you enter the characteristics for which characteristic values are inferred. The INFERENCES section is optional. You need it if constraints are processed in a way that actions cannot be.

Figure 81: OBJECTS Section

Class and Class type - The usual way to declare an object in a constraint is by entering the class and class type. If you want to use a constraint to refer to a PC classified in class PC of class type 300, you enter the PC as follows: (300) PC Object Key - If you want to refer to a specific material, you enter the identifier for the object type, the class type, and the object key. In this example, Mat is the object identifier for materials. You define the object identifier to refer to objects in dependencies by choosing Maintain Object Types in Customizing for Classification.

238

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

The object key for materials is the material number. The object key is also specified in Customizing for Classification. In the step Maintain object keys, you define which fields are used to specify an object. You also enter the field name of the key field. The material number key field is referred to as formal parameter NR. An object key can consist of several partial keys, as is the case for documents: (Document)(017)(TYPE = ’DRW’, VERSION = ’00’, PART = ’000’, NR = ’D4545’) For the class type, enter the class type of the class to which the object is assigned. If the object is not assigned to a class, do not enter a class type. However, you must enter empty parentheses as a place holder. (Material)()(NR = ’MAT-A’)

Figure 82: Variables for Objects, Classes, and Characteristics

Defining Variables If you use a class to refer to an object, you use the expression IS_A to define a variable: X IS_A (300) PC If you refer to an object using the object key, and do not enter a class, you use the expression IS_OBJECT to define a variable: Y IS_OBJECT (Material)(300)(NR=‘T-VPCxx’) If you use the object key to refer to an object, you must define a variable. If you use a class to refer to an object, defining a variable is optional. You can enter a ? to make your variables easier to identify: ?X IS_A (300) PC You must know the variables referred to in a constraint while you are creating a constraint.

18-02-2004

© 2004 SAP AG. All rights reserved.

239

Unit 8: Constraints

PLM140

Figure 83: Constraints With and Without Local Variables

Advantages of variables: • • •

Self-explanatory names Easier to maintain subsequent sections of constraint Less code

It is entirely up to you whether or not you use variables. Variables are an option to support modeling. Characteristic variables can be used in conjunction with object variables and class variables.

RESTRICTIONS Section • •

Sets & checks values Syntax: similar to actions

•

– Object variables instead of $self, $parent, and $root – New: “false“ Task: similar to actions – – –

240

Declarative Calculates additional values as in INFERENCES section Checks all values for consistency, such as preconditions

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

In the RESTRICTIONS section of a constraint, you enter the consistency checks that the constraint is to make. The constraint returns an inconsistency if the RESTRICTIONS section is not true. You cannot enter non-declarative expressions, such as NOT SPECIFIED. You can also use the statement FALSE as a restriction. This means that situations described in the CONDITION section are inconsistent. If this situation occurs, an inconsistency message is returned. In the RESTRICTIONS section of a constraint, you can call tables that have been defined earlier. This makes a constraint a powerful tool, since you can replace a large number of preconditions by using a table call in a constraint. You can use tables in constraints to ensure the consistency of assigned values or to infer values. For restrictable characteristics, you can also use a table to dynamically restrict the allowed values of the characteristic. For example, you can use a table call to define the combinations of values for the casing and hard disk of a PC. If you refer to a table in a constraint, only the combinations of values defined in the table are valid. In some cases, values can be inferred from your entries in the RESTRICTIONS section without using the INFERENCES section. This is the case for equations where the left-hand side contains one variable for a characteristic. The characteristic cannot be restrictable.

Figure 84: Examples of a RESTRICTIONS Section

The constraint returns an inconsistency if the RESTRICTIONS section is not true. In the first example, the RESTRICTIONS section can infer a value for the printer software. In the second example, the RESTRICTIONS section can infer a value for the two characteristics of the class node.

18-02-2004

© 2004 SAP AG. All rights reserved.

241

Unit 8: Constraints

PLM140

Unlike a precondition, a constraint does not hide values of a single-value characteristic or multiple-value characteristic that are not allowed. If a precondition is assigned to a characteristic value, the value is not shown if the precondition is not fulfilled. Constraints can hide values of a restrictable characteristic that are not allowed. To do this, the constraint must contain an INFERENCES section.

CONDITION Section • •

Optional. Syntax: Similar to preconditions

•

– Logical expression – No $self, $parent, $root, or TYPE_OF – New: PART_OF and SUBPART_OF Task: Condition for processing constraint

In the CONDITION section, you specify when the constraint is processed. A constraint is only processed if the CONDITION section is true. The syntax of a condition is similar to the syntax of a precondition or selection condition. However, the following differences apply: TYPE_OF is not allowed in constraints. You can use variables for objects, classes, and characteristics You can use logical expressions of any complexity, including nested disjunctions and conjunctions, such as AND, OR, and parentheses. In addition, you can use the expressions PART_OF and SUBPART_OF. PART_OF checks whether a material or document is in the BOM of another material or document. SUBPART_OF checks the same thing across multiple levels of the BOM. In the CONDITION section and in IF conditions in the RESTRICTIONS section, the following statements are false if the characteristic has no value assigned: = The functioning of such statements is the same as in preconditions and selection conditions.

242

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

Figure 85: Example of a CONDITION Section

INFERENCES Section • •

A value can be inferred for any characteristic variable in the RESTRICTIONS section Applies to:

•

– Formulas in the RESTRICTIONS section – Table calls or function calls Prerequisites: – – –

The variable is entered in the INFERENCES section Conversion is mathematically possible or keys are defined The variable does not occur in the CONDITION section or in a condition in the RESTRICTION section after IF

The INFERENCES section can contain only characteristic variables. If you use a table call or a function call, the relevant access keys must be defined there (value assignment alternative of a table or function). If you use arithmetical expressions, it is possible to interpret a variable.

18-02-2004

© 2004 SAP AG. All rights reserved.

243

Unit 8: Constraints

PLM140

Figure 86: Equations

SAP R/3 Enterprise converts the equation into three additional equations: L = V/H/W W = V/H/L H = V/L/W As soon as the three values are known, the system finds the appropriate equation and executes it. Tables or functions calls work in the same way. In the case of functions, the programmer must ensure that the converted equations are there and are called.

244

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

Exercise 14: Constraint in Single-Level Configuration Exercise Objectives After completing this exercise, you will be able to: • Determine that all extras are ordered if the fast CPU is selected. In other words, all values of the extras characteristic have to be set. Use a constraint to set the values

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company has decided to use SAP R/3 Enterprise to optimize its storage inventories and maintain every possible end-product variant. You, as the Product Manager of the company, need to set the values in a single-level configuration.

Task: If the value fast is assigned to the CPU characteristic, you need to selct the three allowed values of the characteristic for extras to be selected automatically. Use a constraint to do this. 1.

Create dependency net T_CN_VPC##. Description: Any Status: Released (can be released immediately) Dependency Group: T-##

2.

In this dependency net, create constraint T_CS_VPC##. Dependency Group: T-## Dependency Type: Constraint Enter the source code that describes the setting of values described above.

3. 4.

18-02-2004

Assign the dependency net to the configuration profile of your material T-VPC##. Test your solution using the configuration simulation.

© 2004 SAP AG. All rights reserved.

245

Unit 8: Constraints

PLM140

Solution 14: Constraint in Single-Level Configuration Task: If the value fast is assigned to the CPU characteristic, you need to selct the three allowed values of the characteristic for extras to be selected automatically. Use a constraint to do this. 1.

Create dependency net T_CN_VPC##. Description: Any Status: Released (can be released immediately) Dependency Group: T-## a) Note: Dependency nets cannot be maintained during assignment. You must create and maintain dependency nets using the transaction for this purpose. Then, you assign them to the configuration profile. Create dependency net T_CN_VPC##: CU21 = SAP Menu → Logistics → Central Functions → Variant Configuration → Dependency → Dependency Net → Create or User Menu → Variant Configuration → Dependency → Dependency Net → Create Dependency Net: T_CN_VPC##

→ Enter Description: Net for T-VPC## Status: 1 Dependency Group: T-## 2.

In this dependency net, create constraint T_CS_VPC##. Dependency Group: T-## Dependency Type: Constraint Continued on next page

246

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

Enter the source code that describes the setting of values described above. a)

Create constraint T_CS_VPC##: Do not leave the dependency net.

→ Assignments = F5 Dependency (Rltnship): T_CS_VPC## Description: All extras for fast CPU = 03 Dependency Group: T-##

→ Dependency editor Syntax: OBJECTS: (300) T_VPC## WHERE CPU = T_CPU_##; EXT = T_EXT_## CONDITION: CPU = ’03’ RESTRICTIONS: EXT = ’01’, EXT = ’02’, EXT = ’03’,

→ Check Save (syntax) → Release and save (dependency) 3.

Assign the dependency net to the configuration profile of your material T-VPC##. a)

Assign the dependency net to the configuration profile: CU42= SAP Menu → Logistics → Central Functions → Variant Configuration → Configuration Profile → Change or User Menu → Variant Configuration → Configuration Profile → Change Material: T-VPC##

→ Enter → Double-click on profile → Dependency Assignments Dependency (Rltnship): T_CN_VPC##

→ Save Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

247

Unit 8: Constraints

4.

PLM140

Test your solution using the configuration simulation. a)

248

Check the result in the configuration simulation.

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

Exercise 15: Constraint in Multilevel Configuration with Complete Model of a Multilevel Configuration Task Exercise Objectives After completing this exercise, you will be able to: • Set up a multilevel configuration of a PC package. This package includes a configurable printer as well as the PC • Maintain BOMs, characteristics, classes, and configuration profiles • Create a constraint to set values for the PC and printer according to the values assigned to the package

Business Example AA Computers is a PC manufacturing company. It manufactures various models of PCs. The company is implementing SAP R/3 Enterprise to optimize its storage inventories and maintain every possible end-product variant. The configurable PC is to be sold as a package that includes a configurable printer. You, as the Product Manager of the company, want to model this configuration task. This involves maintaining constraints that compare the values assigned across the entire multilevel structure.

Task 1: Note: You can copy the master data from the example in group 00. However, be sure to change the resulting objects, such as variant class, characteristics, object dependencies, and configuration profile, so that they are consistent with your group number. This exercise provides an opportunity to apply the new skills that you have learned. However, to do this exercise, you must complete the preceding exercises. Set up the BOM structure for the PC Package: 1.

Create the material master records that you need for package T-VPP## and printer T-VPR##.

2.

Create the BOMs for package T-VPP## and printer T-VPR##. In the BOM for the package, you need to enter your PC T-VPC##. All components must be relevant to sales.

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

249

Unit 8: Constraints

PLM140

Task 2: Create the variant classes and configuration profiles that you need, if they do not exist. 1.

Check the following characteristics: T_PCP1= Package type T_PR1= Printer type T_PR2= Print drive Note: Display these characteristics, which are used by all groups.

2.

Create the following variant classes (by copying): Class: T_VPP## with characteristic:T_PCP1 Class: T_VPR## with characteristics:T_PR1 and T_PR2

3.

Create the configuration profiles that you need. For package T-VPP##: The BOM explosion is “multilevel“ The process is “Sales order“ The BOM application in the settings is PP01 All screens are allowed Assign variant class T_VPP_## Manual changes to sales order are allowed For the printer T-VPR##: The BOM explosion is “multilevel“ The process is “Order BOM“ The BOM application in the settings is PP01 All screens are allowed. Assign variant class T_VPR_##

Continued on next page

250

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

Task 3: If the package type is the standard package (value “01“), the following characteristic values must be set: CASING = Desktop CPU = Slow EXTRAS = Mouse, Modem, and Keyboard COLOR = Blue without gloss HARD_DISK 10 GB SOFTWARE = MS Word MULTIMEDIA PACKAGE = Standard PRINTER_TYPE = Laser printer Use a constraint to do this. 1.

Create dependency net T_CN_VPP##. Description: (Your choice) Status: Released Dependency Group: T-##

2.

In this dependency net, create constraint T_CS_VPP##. Dependency Group: T-## Dependency Type: Constraint Enter the source code that describes the setting of values described above.

18-02-2004

3.

Assign the dependency net to the configuration profile of your package T-VPP##.

4.

Test your solution using the configuration simulation.

© 2004 SAP AG. All rights reserved.

251

Unit 8: Constraints

PLM140

Solution 15: Constraint in Multilevel Configuration with Complete Model of a Multilevel Configuration Task Task 1: Note: You can copy the master data from the example in group 00. However, be sure to change the resulting objects, such as variant class, characteristics, object dependencies, and configuration profile, so that they are consistent with your group number. This exercise provides an opportunity to apply the new skills that you have learned. However, to do this exercise, you must complete the preceding exercises. Set up the BOM structure for the PC Package: 1.

Create the material master records that you need for package T-VPP## and printer T-VPR##. a)

Set up the BOM structure for the PC Package: Check the following material master records: Package T-VPP## Printer T-VPR##

→ Display MM03 => They exist, but are not classified yet 2.

Create the BOMs for package T-VPP## and printer T-VPR##.

Continued on next page

252

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

In the BOM for the package, you need to enter your PC T-VPC##. All components must be relevant to sales. a)

Change bill of material: Package T-VPP## 1200 3 Change item 10 to T-VPC## Set all items to relevant to sales

→ Select item → Item detail = F7 → Status/long text set sales relevancy flag here Printer T-VPR## 1200 1 No change necessary

Task 2: Create the variant classes and configuration profiles that you need, if they do not exist. 1.

Check the following characteristics: T_PCP1= Package type T_PR1= Printer type T_PR2= Print drive Note: Display these characteristics, which are used by all groups. a)

Create the variant classes and configuration profiles that you need. Check the characteristics: T_PCP1 = Package type T_PR1 = Type of printer T_PR2 = Print drive

2.

18-02-2004

Create the following variant classes (by copying): Continued on next page

© 2004 SAP AG. All rights reserved.

253

Unit 8: Constraints

PLM140

Class: T_VPP## with characteristic:T_PCP1 Class: T_VPR## with characteristics:T_PR1 and T_PR2 a)

Copy variant classes: Class: T_VPP## 300 Copy From Class: T_VPP00 300 with characteristic: T_PCP1 (Possibly others) Change description and class group to match your group number. Class: T_VPR## 300 Copy From Class: T_VPR00 300 with characteristics: T_PR1 and T_PR2

3.

Create the configuration profiles that you need. For package T-VPP##: The BOM explosion is “multilevel“ The process is “Sales order“ The BOM application in the settings is PP01 All screens are allowed Assign variant class T_VPP_## Manual changes to sales order are allowed For the printer T-VPR##: The BOM explosion is “multilevel“ The process is “Order BOM“ The BOM application in the settings is PP01

Continued on next page

254

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

All screens are allowed. Assign variant class T_VPR_## a)

Create the required configuration profiles. For both materials, the following applies: Material: T-VPP## T-VPR##

→ Enter Prof. Name: SET_N OBOM_N Class Type: 300 300

→ Profile detail → Class Assignment T_VPP## T_VPR## Detail settings for the profiles Basic data: Do not change Confign initial screen: Confign Parameters: Process: Sales Order (SET) Order BOM BOM Explosion: Multilevel BOM application: PP01 Do not change anything else Userinterface: Allowed screens: All For package, also Confign browser => no structure Do not change anything else For T_VPP##: Sales Order: Flag Manual changes allowed

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

255

Unit 8: Constraints

PLM140

Task 3: If the package type is the standard package (value “01“), the following characteristic values must be set: CASING = Desktop CPU = Slow EXTRAS = Mouse, Modem, and Keyboard COLOR = Blue without gloss HARD_DISK 10 GB SOFTWARE = MS Word MULTIMEDIA PACKAGE = Standard PRINTER_TYPE = Laser printer Use a constraint to do this. 1.

Create dependency net T_CN_VPP##. Description: (Your choice) Status: Released

Continued on next page

256

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

Dependency Group: T-## a)

Maintain constraint: If the package type is the standard package (value “01“), the following characteristic values must be set: CASING = Desktop CPU = Slow EXTRAS = Mouse, Modem, and Keyboard COLOR = Blue without gloss HARD DISK = 10GB SOFTWARE = MS Word MULTIMEDIA PACKAGE = Standard PRINTER TYPE = Laser printer Create dependency net T_CN_VPP##: CU21 = SAP Menu → Logistics → Central Functions → Variant Configuration → Dependency → Dependency Net → Create or User Menu → Variant Configuration → Dependency → Dependency Net → Create Dependency Net: T_CN_VPP##

→ Enter Description: Net for T-VPP## Status: 1!!! Dependency Group: T-## 2.

In this dependency net, create constraint T_CS_VPP##. Dependency Group: T-## Dependency Type: Constraint

Continued on next page

18-02-2004

© 2004 SAP AG. All rights reserved.

257

Unit 8: Constraints

PLM140

Enter the source code that describes the setting of values described above. a)

Create constraint T_CS_VPP##: (continue immediately:)

→ Assignments Dependency (Rltnship): T_CS_VPP## Description: Values for standard package Dependency Group: T-##

→ Dependency editor Syntax: OBJECTS: (300) T_VPC_## WHERE CASING= T_CAS_##; CPU =T_CPU_##; EXTRAS= T_EXT_##; COLOR =T_COL_00; GLOSS= T_GLO_00; HD = T_HD_##; SW =T_SW_##; MED =T_MED_##, (300) T_VPP_## WHERE PACKAGE = T_PCP1, (300) T_VPR_## WHERE TYPE = T_PR1. CONDITION: PACKAGE = ’01’ RESTRICTIONS: CASING =’DT’, CPU =’01’, EXTRAS = ’01’, EXTRAS = ’02’, EXTRAS = ’03’, COLOR =’02’, GLOSS = ’0’, HD = 10, SW =’W’, MED=’01’, TYPE =’L’

→ Check Save (syntax) → Release and save (dependency)

Continued on next page

258

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Lesson: Structure of a Constraint

3.

Assign the dependency net to the configuration profile of your package T-VPP##. a)

Assign dependency net to the configuration profile: CU42= SAP Menu → Logistics → Central Functions → Variant Configuration → Configuration Profile → Change or User Menu → Variant Configuration → Configuration Profile

→ Change

Material: T-VPP##

→ Enter → Double-click on profile Dependency AssignmentsDependency (Rltnship): T_CN_VPP##

→ Save 4.

Test your solution using the configuration simulation. a)

Check the result in the configuration simulation. Start with package T-VPP## (plant 1200)

→ Package type = 1 → Double-click on T-VPC## in the configuration structure on the left. Package type = 1

→ Double-click on T-VPC## in the configuration structure on the left.

18-02-2004

© 2004 SAP AG. All rights reserved.

259

Unit 8: Constraints

PLM140

Lesson Summary You should now be able to: • Process equations and tables that cannot be processed by actions • Use restrictable characteristics

260

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Unit Summary

Unit Summary You should now be able to: • Explain the use of sections of a constraint • Create simple constraints in constraint nets • Process equations and tables that cannot be processed by actions • Use restrictable characteristics

18-02-2004

© 2004 SAP AG. All rights reserved.

261

Unit Summary

262

PLM140

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Test Your Knowledge

Test Your Knowledge 1.

Identify the distinguishing features of constraints. Choose the correct answer(s).

2.

□

A

□ □

B C

□

D

□

E

The main purpose of constraints is to check the consistency of a configuration. Constraints are directly assigned to individual objects. Constraints are used to store information on conditions that must be fulfilled if the configuration is to be consistent. You can use constraints to describe the dependencies between completely different objects and their characteristics. Constraints are processed in a specific order and you can determine when a specific constraint is used.

Constraints can only be processed in a configuration if the dependency net and constraints are locked. Determine whether this statement is true or false.

□ □ 3.

True False

Which of the following sections are correctly matched for the structure of a constraint? Choose the correct answer(s).

4.

□

A

□ □

B C

□

D

OBJECTS: In this section, you specify the objects that are relevant to the constraint. CONDITION: You must enter a condition in a constraint. RESTRICTIONS: You may not enter a restriction in a constraint. INFERENCES: The INFERENCES section is optional.

If you use a class to refer to an object, it is mandatory to define a variable. Determine whether this statement is true or false.

□ □

18-02-2004

True False

© 2004 SAP AG. All rights reserved.

263

Test Your Knowledge

5.

PLM140

The INFERENCES section can contain only characteristic variables. Determine whether this statement is true or false.

□ □

264

True False

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Test Your Knowledge

Answers 1.

Identify the distinguishing features of constraints. Answer: A, C, D Constraints are not directly assigned to individual objects. Moreover, constraints are not processed in a specific order. You cannot determine when a specific constraint is used.

2.

Constraints can only be processed in a configuration if the dependency net and constraints are locked. Answer: False Constraints can only be processed in a configuration if the dependency net and constraints are released.

3.

Which of the following sections are correctly matched for the structure of a constraint? Answer: B, C CONDITION: You do not need to enter a condition in a constraint. RESTRICTIONS: You must enter a restriction in a constraint.

4.

If you use a class to refer to an object, it is mandatory to define a variable. Answer: False Defining a variable is optional if you use a class to refer to an object.

5.

The INFERENCES section can contain only characteristic variables. Answer: True The INFERENCES section can contain only characteristic variables.

18-02-2004

© 2004 SAP AG. All rights reserved.

265

Course Summary

PLM140

Course Summary You should now be able to: • •

266

Perform simple modeling tasks of variant configuration Understand the functions and features of variant configuration to evaluate and plan its use

© 2004 SAP AG. All rights reserved.

18-02-2004

Appendix 1

Figure 87:

18-02-2004

© 2004 SAP AG. All rights reserved.

267

Appendix 1:

PLM140

Figure 88: PC - Customer Example 1 (Configuration Structure)

Figure 89: PC - Customer Example 2 (BOM Structure)

268

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Appendix 1:

Figure 90: PC Package - Customer Example 3 (BOM Structure)

Figure 91: PC - Instructor Example 1 (Configuration Structure)

18-02-2004

© 2004 SAP AG. All rights reserved.

269

Appendix 1:

PLM140

Figure 92: PC - Instructor Example 2 (BOM Structure)

Figure 93: PC - Instructor Example 3 (BOM Structure)

270

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Appendix 1:

Figure 94: PC - Instructor Example 4 (Task Lists)

Figure 95: Database Tables for Variant Configuration (1)

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

18-02-2004

© 2004 SAP AG. All rights reserved.

271

Appendix 1:

PLM140

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

Figure 96: Database Tables for Variant Configuration (2)

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

272

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Appendix 1:

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

Figure 97: Database Tables for Variant Configuration (3)

IBIB IBase administrative data IBIN Data of an instance version IBINT Instance descriptions IBST Root relationship and is_part_of relationship

18-02-2004

© 2004 SAP AG. All rights reserved.

273

Appendix 1:

PLM140

(“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)

Figure 98: The Configuration Profile as of Release 4.5

Figure 99: Configuration Profile: Basic Data

274

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Appendix 1:

Figure 100: Configuration Profile: Configuration Initial Screen

Figure 101: Configuration Profile

The use of filters restricts the explosion of BOMs in high-level configuration. The filters apply to all high-level configuration. Therefore, components that are not displayed due to the filter are ignored in the sales order and in order BOM maintenance. The BOM explosion in high-level configuration can be restricted by the explosion level in the configuration profile. It can also be restricted by the definition of BOM applications assigned to the configuration profile and by filters.

18-02-2004

© 2004 SAP AG. All rights reserved.

275

Appendix 1:

PLM140

Figure 102: Configuration Profile - User Interface

Configuration browser The configuration browser lets you navigate around the configuration structure and displays the value assignment screen for the selected material so that you can enter values. The configuration browser provides the functions of the configuration structure screen and value assignment screen so that you can select the configuration browser if you have not selected these screens. Settings - Can be defined in the configuration profile. Then, they are saved for the specific configuration profile. These settings have the lowest priority. - 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 three settings at any time (provided that they exist).

276

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Appendix 1:

Figure 103: Configuration Simulation

Figure 104: Configuration Profile: Order BOM

Figure 105: Configuration Profile: Scenarios

18-02-2004

© 2004 SAP AG. All rights reserved.

277

Appendix 1:

PLM140

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 if their configuration profiles allow it. Single-level BOM explosion for configurable assemblies according to the functionality above. The prerequisite is that the material above the assembly has a multilevel configuration scenario and its BOM has been exploded.

Figure 106: Overview: Combinations of Scenarios

Figure 107: Configuration Profile: Details of Interface Design

278

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Appendix 1:

Figure 108: Transfer of Requirements and Pricing at Header Level (1)

If the immediately superior configurable material has item category TAC, a subordinate configurable material with item category group 0002 is assigned item category TAE. This means that the material is not relevant to the pricing and transfer of requirements. Components with item category group NORM also have item category TAE.

Figure 109: Transfer of Requirements and Pricing at Header Level (2)

If the superior configurable material has item category TAC, a subordinate configurable material with item category group 0004 is assigned item category TAE. Components with item category group NORM also have item category TAE. Only the superior material is involved in pricing and transfers requirements.

18-02-2004

© 2004 SAP AG. All rights reserved.

279

Appendix 1:

PLM140

Figure 110: Transfer of Requirements and Pricing at Component Level (1)

Item category group 0004 is maintained for the configurable material. The BOM for the material is made up of finished products or trading goods. These materials have item category group NORM. In the sales order, the configurable material has item category TAM in the sales order and is not relevant to pricing or transfer of requirements. The subordinate order items have item category TAN. Order items with this item category transfer requirements and are relevant to pricing.

Figure 111: Transfer of Requirements and Pricing at Component Level (2)

280

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Appendix 1:

If the superior configurable material has item category TAM, a subordinate configurable material with item category group 0002 is assigned item category TAC. This means that the subordinate material transfers requirements. Components of the header material with item category group NORM have item category TAN and do not transfer requirements. Components of subordinate configurable materials with item category group NORM have item category TAE and do not transfer requirements.

Figure 112: Transfer of Requirements and Pricing at Component Level (3)

If the superior configurable material has item category TAM, a subordinate configurable material with item category group 0004 is also assigned item category TAM. Components with item category group NORM have item category TAN and are relevant to requirements and pricing.

18-02-2004

© 2004 SAP AG. All rights reserved.

281

Appendix 1:

282

PLM140

© 2004 SAP AG. All rights reserved.

18-02-2004

Appendix 2 Recommended Follow-Up Courses and Activities

Courses that follow on directly from this course (and therefore can be attended in any order) are: •

PLM143 Variant Configuration 2 – Integration

•

PLM146 Variant Configuration 3 – Scenarios

•

CR245 SAP IPC Product Configuration Modeling for the SCE (Sales Configuration Engine)

• • • •

18-02-2004

Go through the exercises using IDES data or your own data Read online documentation Read IMG documentation Read release notes

© 2004 SAP AG. All rights reserved.

283

Appendix 2: Recommended Follow-Up Courses and Activities

284

© 2004 SAP AG. All rights reserved.

PLM140

18-02-2004

Appendix 3 Data in the Exercises

All the data is in the IDES system and is therefore available in all training systems, unless specified otherwise. Type of Data

Data of Your Exercise Group

Data of Group 00

PC Package Group ##

T-VPP##

T-VPP00

Configurable PC group ##

T-VPC##

T-VPC00

Configurable Printer T-VPR## Group ##

T-VPR00

Materials

18-02-2004

Various monitors

M-01, M-02, M-03, M-04, M-05, M-06, M-07, M-08, M-12, M-13, M-14, M-25, and M-26

Print drive OS/2

T-PR1

Print drive WINNT

T-PR2

Print drive Win 98

T-PR3

Dot matrix printer kit

T-PR4

Inkjet printer kit

T-PR5

Laser printer kit

T-PR6

Printer stand

T-PR7

Bolt set

T-PCS

Tower Casing

T-PC21

Minitower Casing

T-PC22

© 2004 SAP AG. All rights reserved.

285

Appendix 3: Data in the Exercises

PLM140

Desktop Casing Various color components

T-PC23 T-100-801, T-100-802, T-100-803, T-100-804, T-100-805, and T-100-806

Slow CPU

T-CPU-1

Medium CPU

T-CPU-2

Fast CPU

T-CPU-3

Hard disk 10 GB

T-DISK-1

Hard disk 20 GB

T-DISK-2

Hard disk 40 GB

T-DISK-3

Hard disk 60 GB

T-DISK-4

Software: MS Access

T-SW-10

Software: MS Excel

T-SW-20

Software: MS Office Package

T-SW-30

Software: MS Word

T-SW-40

CD drive, slow

T-CD-1

CD drive, medium

T-CD-2

CD drive, fast

T-CD-3

Speaker Set (2), 10 Watt

T-SPEAKER-10

Speaker Set (2), 15 Watt

T-SPEAKER-15

Speaker Set (2), 40 Watt

T-SPEAKER-40

Extras for PC (Group ##)

T-VPZ##

Standard Keyboard Mouse standard model Modem

T-VPZ00 DPC1009 T-PZ1 DPC9026

All the following data already exists in IDES for group 00. Data for other groups is also available in IDES, unless it is marked with (*). Data marked with (*) is created or assigned during the course.

286

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Appendix 3: Data in the Exercises

Bills of Material Header material

Component

T-VPP## (plant 1200) (usage 3)

T-VPC## (*) T-VPR## (200)CL_MONITOR_PC (class item)

T-VPR## (plant 1200) (usage 1)

T-PR1 T-PR2 T-PR3 T-PR4 T-PR5 T-PR6 T-PR7

T-VPC## (plant 1200) (usage 1) (*) T-PCS T-PC21 T-PC22 T-PC23 (200)T_VPC_COLOR(class item) T-CPU-1 T-CPU-2 T-CPU-3 T-VPZ## (*) T-DISK-1 T-DISK-2 T-DISK-3 T-DISK-4 T-SW-10 T-SW-20 T-SW-30 T-SW-40 T-CD-1 T-CD-2 T-CD-3

18-02-2004

© 2004 SAP AG. All rights reserved.

287

Appendix 3: Data in the Exercises

PLM140

T-SPEAKER-10 T-SPEAKER-15 T-SPEAKER-40 T-VPZ## (plant 1200) (usage 1) (*) DPC1009 T-PZ1 DPC9026 Routing (*)

For material T-VPC## Plant 1000, Usage 1

Classes

(300)T_VPC## (*) (300)T_VPP## (*) (300)T_VPR## (*) (200)T_VPC_COLOR (200)T_MONITOR_PC

Characteristics T_PCP1Package type T_PR1Printer type T_PR2Print drive T_CAS_## (*)Casing type T_CPU_## (*)CPU T_EXT_## (*)Extras T_COL_00Color T_GLO_00Gloss T_QUANT_## (*)Component quantity T_VGW03_## (*)Standard value 03 T_HD_## (*)Hard disk T_SW_## (*)Software T_MED_## (*)Multimedia package T_CD_## (*)CD drive T_SPE_## (*)Hard disk

288

© 2004 SAP AG. All rights reserved.

18-02-2004

PLM140

Appendix 3: Data in the Exercises

Object Dependencies (all *)

T_SC_CAS_TW_## T_SC_CAS_MT_## T_SC_CAS_DT_## T_SC_CPU_01_## T_SC_CPU_02_## T_SC_CPU_03_## T_SC_EXT_01_## T_SC_EXT_02_## T_SC_EXT_03_## T_SC_HD20_CAS_## T_PRE_CPU_23_## T_PRE_HD_## T_PROC_QUANT2_## T_PROC_VGW0315_## T_PROC_TABLE_## T_PROC_DEFAULT_## T_CN_VPC## T_CS_VPC## T_CN_VPP## T_CS_VPP##

Variant Tables (*)

T_TABLE_VPC##

Configuration Profiles (*)

For T-VPP## SET-N For T-VPR## N-OBOM For T-VPC## PF0

18-02-2004

© 2004 SAP AG. All rights reserved.

289

Appendix 3: Data in the Exercises

290

© 2004 SAP AG. All rights reserved.

PLM140

18-02-2004

Index A

L

allowed intervals, 28 allowed values, 28 alternative sequence, 86 Automatic fixing, 109

Local dependencies, 125

B bill of material, 71 BOM, 9 Boolean expressions, 131

C Characteristics, 3, 25 Characteristics list, 29 class type, 39, 41 CONDITION section, 242 configurable material, 59, 73 configuration profile, 3, 105 Constraints, 233

D

Maintenance in order allowed, 110 material master, 3 material master record, 7, 59 materials and part masters, 60 MRP, 61

N Naming conventions, 25

O Object dependencies, 148 object key, 238

P

G

parallel sequence, 86 precondition, 187, 189 Pricing condition, 4 Procedural dependency types, 130 procedure, 208 Procedure, 109 procedures, 205 processing option, 107

Global dependencies, 125

R

declarative dependencies, 131 Declarative dependency types, 130 dependencies, 4 dependency net, 234

I inconsistency, 241 Indicators, 28 INFERENCES section, 241 interdependencies, 208

K Keywords, 132

18-02-2004

M

reference characteristic, 171 reference characteristics, 170 Reference characteristics, 30 RESTRICTIONS section, 241 Result-oriented order BOM, 109

© 2004 SAP AG. All rights reserved.

291

Index

PLM140

routing, 10, 86

S sections, 237 selection condition, 151 selection conditions, 191 Semi-declarative dependency types, 130 strings, 132 Suboperations, 86 super BOM, 3 super task list, 3 Syntax, 131

technical review, 109 Trace Functions, 140

V value assignment functions, 190 variant class, 7 variant classes, 3 variant configuration, 2 variant configuration model, 58 Variant functions, 139 Variant tables, 138 variants, 7

T task list, 86

292

© 2004 SAP AG. All rights reserved.

18-02-2004

Feedback SAP AG has made every effort in the preparation of this course to ensure the accuracy and completeness of the materials. If you have any corrections or suggestions for improvement, please record them in the appropriate place in the course evaluation.

18-02-2004

© 2004 SAP AG. All rights reserved.

293