PLM146 - Variant Configuration - Scenarios & Enhancements

PLM146 Variant Configuration 3 - Scenarios & Enhancements

PLM146

Variant Configuration – Scenarios & Enhancements

THE BEST-RUN BUSINESSES RUN SAP SAP AG 2006 © SAP AG©2006

SAP R/3 Enterprise 2006/Q2 Material number 50078818

Copyright

Copyright 2005 SAP AG. All rights reserved. Neither this publication nor any part of it may be copied or reproduced in any form or by any means without the prior written consent of SAP AG. The information contained in this publication is subject to change without prior notice.

© SAP AG 2003

Trademarks Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corp. in the USA and/or other countries. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. 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. MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP.com, xApps, xApp and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in other countries worldwide. All other product and service names mentioned are the trademarks of their respective owners. Data contained in this document serves informational purposes only. National product specifications may vary. The information contained in this publication is subject to change without prior notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Course Prerequisites

Required: PLM140 Variant Configuration 1 - Modeling Or thorough knowledge of the relevant functions (in R/3 4.5 or higher) (Overview course PLM100)

Recommended: PLM143 Variant Configuration 2 - Integration PLM130 Classification SCM600 Processes in Sales and Distribution SCM200 Supply Chain Planning Overview SCM300 Supply Chain Manufacturing Overview © SAP AG 2003

Target Audience

Course participants Variant modelers for: SAP ERP - Configurator (SAP IPC - Sales Configuration Engine) Project team DP organizers • Duration: 3 days

© SAP AG 2006

Notes to the user The training materials are not teach-yourself programs. They complement the course instructor's explanations. On the sheets, there is space for you to write down additional information.

Course Overview

Contents: Course Goals Course Objectives Course Content Course Overview Diagram Main Business Scenario

© SAP AG 2002

© SAP AG

PLM146

1-6

Course Goals

This course will prepare you to: Model multi-variant products by building on your existing knowledge of variant configuration and examining its functions and handling in detail

© SAP AG 2002

© SAP AG

PLM146

1-7

Course Objectives

At the conclusion of this course, you will be familiar with and be able to use: Advanced settings of the configuration profile and interface design Specialized aspects of object dependencies (specifically constraints) Special features of the different scenarios Knowledge-based and result-oriented order BOMs Multilevel configuration structures Low-level and high-level configuration Additional tools (BAPI, ALE, user exits, and the analysis tool) The different ways of storing variant configuration data Hints on system performance © SAP AG 2002

© SAP AG

PLM146

1-8

Course Content

Preface Unit 1

Course Overview

Unit 2

Variant Configuration: Consolidation

Unit 3

Control Options in the Configuration Profile

Unit 4

Configuration Scenario Without BOM Explosion

Unit 5

More About Constraints

Unit 6

More About Object Dependencies

...

© SAP AG 2002

© SAP AG

PLM146

1-9

Course Content

Unit 7

Configuration Scenarios with BOM Explosion

Unit 8

Configuration Scenarios with Order BOMs

Unit 9

Other Variant Configuration Tools

Unit 10

Conclusion Appendix Data for Exercises Structure of Examples in Exercises Frequently Used Menu Paths Ideas for Modeling

© SAP AG 2002

© SAP AG

PLM146

1-10

Course Overview Diagram

Course Overview

1


6


2


7


3


8

Configuration Scenarios Without BOM Explosion

4


9


5

Conclusion

10

© SAP AG 2002

© SAP AG

PLM146

1-11

Main Business Scenario

You are a manufacturer of multi-variant products. To map your multi-variant products, you want to use the variant configuration functions in SAP R/3. Your design process requires detailed knowledge of the functions and handling of variant configuration that are relevant to modeling.

© SAP AG 2002

© SAP AG

PLM146

1-12


Contents: Procedure for variant configuration modeling Classification system tools Material master, bills of material, and task lists Configuration profile Dependencies Pricing Material variants Customizing

© SAP AG 2002

© SAP AG

PLM146

2-13

Variant Configuration: Consolidation: Unit Objectives

At the conclusion of this unit, you will be able to: With the help of an overview of the basics of variant configuration as covered by course PLM140: Use all the functions taught in PLM140 See where the new topics covered by course PLM146 fit into the modeling process as a whole

© SAP AG 2003

© SAP AG

PLM146

2-14

Variant Configuration: Consolidation: Course Overview Diagram

Course Overview

1


6


2


7


3


8


4


9


5

Conclusion

10

© SAP AG 2002

© SAP AG

PLM146

2-15

Variant Configuration: Consolidation: Business Scenario

You are designing the solution to a modeling task. A major concern is to keep an overview of the integrated objects.

© SAP AG 2002

© SAP AG

PLM146

2-16

Modeling Variant Configuration Dependencies Characteristics haracteristics Material variant

Preconditions

Pricing

Classes

Constraints

Procedure (action)

Material master record

Configuration profile

BOM

Routing

Selection conditions

© SAP AG 2006

There are a number of individual steps to setting up a knowledge base for a configurable material. First, you need the characteristics that describe the material. You assign the characteristics to a variant class. You maintain dependencies for the characteristics and characteristic values, to ensure that only allowed values can be selected. You maintain settings for the configurable material in the material master. You create a configuration profile to define the configuration parameters. The material master record must be assigned to the variant class. You define the components for manufacturing a configurable material in a super BOM and the operations for manufacturing a configurable material in a super task list. You assign object dependencies to the operations and components that are only required for specific variants. Before you can configure a material for production, we advise you to simulate configuration, to check whether all the data is maintained correctly.

© SAP AG

PLM146

2-17

Screens for Maintaining Characteristics

Basic Data

Description, format, and control data

Descriptions

Multilingual headings and descriptions

Values

List of allowed characteristic values

Addnl Data

Reference characteristics, document info records, and user interface

Restrictions

Restriction to class types

Classification

Classification of characteristic

© SAP AG 2002

Naming conventions: Letters, figures, underscore, and hyphen Characteristic names must start with a letter Characteristic names containing a hyphen are allowed in object dependencies, but are not as easy to use. If you use a characteristic whose name contains a hyphen, you must use the expression SKEY to address the characteristic in dependencies. You enter the characteristic name in single quote marks: SKEY 'EXT-COLOR'. (For example, $self.skey‘EXT-COLOR‘ = ‘red‘) You can rename characteristics, because they are stored under an internal number. However, you cannot rename a characteristic that is used in dependencies.

© SAP AG

PLM146

2-18

Entry + Format + Value Assignment Format

Single value

NUM

Numeric value Number of characters (decimal places) Unit Exponent display Template Negative values

CHAR

Character value Number of characters Template Case sensitive

DATE

Date value

TIME

Time value

CURR

Currency value

...

Entry

except class assignment & hierarchy values

Multiple values

Restrictable

User-defined data type

(When assigning values) Required: yes? no?

Indicator cannot be overwritten in class

© SAP AG 2006

The full functions of formats DATE, TIME, and CURR cannot be used in variant configuration. You cannot use user-defined data types, because dependencies can only read single characteristics. You use the Entry required indicator to define whether it is always obligatory to assign a value to the characteristic. The allowed values and allowed intervals that you define are binding for value assignment, unless you define that additional values are also allowed. You can overwrite characteristic values for a specific class. Indicators for single value, multiple values, and restrictable: The Single value indicator means that only one value can be assigned to an object. If you assign other classes or hierarchy nodes to this class, you can assign more than one value. This serves to restrict the allowed values. The Restrictable indicator denotes a special type of single-value characteristic, which can only be used in constraints. In R/3, you can only use Restrictable together with Single value.

© SAP AG

PLM146

2-19

Classes in Variant Configuration

Variant class Classes of class type 300 (or (or similar) similar) collect and manage the characteristics to which you assign values in the sales order.

Class node Classes of type 200 (or (or similar) similar) collect and manage the characteristics for specifying a precise component in the BOM

© SAP AG 2006

The control parameters for a class type in Customizing define a class type as a variant class type or a class type for class nodes. In the standard system, you can define an existing class type as a class type for class nodes or a variant class type. You can also define additional variant class types and additional class types for class nodes in Customizing. The class type has central control functions for class maintenance. You cannot change the class type once you have saved a class. You define class statuses, classification statuses, organizational areas, text types, functions, and filters separately for each class type. In the standard system, the class statuses for all class types are: 0 = In preparation (only class maintenance allowed) 1 = Released (no restrictions on use) 2 = Locked (no classification allowed)

© SAP AG

PLM146

2-20

Screens for Maintaining Classes

Basic Data Keywords Characteristics

Texts

Document

Standard

Addnl Data

General information, control data

Strings for finding the class by matchcode

Characteristics of class

ClassClass-specific overwrite

Texts explaining the class

Document info record and document link

Data for standardized classes (DIN standards)

Additional data for class nodes

© SAP AG 2002

© SAP AG

PLM146

2-21

Configurable Material

Material number under which all variants of a product are stored in SAP R/3 Reference for all related objects (bills of material, task lists, configuration profiles, and so on) Essential control parameters, especially those for MRP and sales

© SAP AG 2002

The material master is the reference point for all other objects that are relevant to a product with multiple variants. The bills of material, task lists, and so on, are all created for the configurable material. The material master contains essential control parameters, especially those that are relevant to material requirements planning (MRP) and sales. In the standard system, material type KMAT is defined for configurable materials. However, you can define materials of other material types as configurable materials (by setting an indicator on the Basic data screen of the material master record) or define additional material types for configurable materials.

© SAP AG

PLM146

2-22

(Super) BOM

Master data > Dependencies > Configured BOM

BOM

Material BOM

Dynamic BOM Order BOM

© SAP AG 2006

Definition of a bill of material (BOM): a purpose-built, complete, formally structured list of the objects that make up an object. The list contains the description, object number, quantity, and unit of measure for all objects. The BOM of a configurable material contains all the components that are used in all possible variants of the product. You use dependencies to configure the BOM. In other words, only the components that are required for a specific variant are selected. The BOM is exploded according to the characteristic values you assign. If you define certain settings in the configuration profile, you can make manual changes to the BOM for a sales order. The BOM is then saved as an order BOM for the sales order. You can change the BOM in a production order, as you can for production without variants. Types of BOM items that are especially relevant to variant configuration are classes, non-stock items for materials of the material type KMAT, and variable-size items.

© SAP AG

PLM146

2-23

(Super) Task List

Task list > Dependencies > Configured task list

Task list

Routing

Dynamic operation sequence Copy function

© SAP AG 2002

Definition of routing (task list): A routing is a task list that describes the process for producing a material or for performing a service. It contains all the operations, suboperations, and production resources/tools (PRTs) that are required to manufacture the material. The super task list of a configurable material comprises the sequences, operations, suboperations, and PRT assignments that are required to manufacture all possible variants of the material. You use dependencies to select the correct operations for a specific variant. The task list is exploded according to the characteristic values assigned. You can create a routing by copying the configuration simulation. You can also create a routing with reference to a sales order. An alternative sequence lets you select alternative operations for an operation sequence. This can be useful to deal with either different production processes for different lot sizes, or capacity problems. A parallel sequence lets you process operations in parallel with other operations. Suboperations are subordinate to an operation, and can be used to calculate costs and capacity in more detail (control key). You can assign PRTs to any operation. Each production resource/tool must have a master record.

© SAP AG

PLM146

2-24

Configuration Profile for a Material

Selecting a class type Provides characteristics Enables link to variant class

Variant class Material master

Defining the configuration scenario Other control parameters Allowed screens, initial screen Availability check Scenario-based control parameters

© SAP AG 2006

A configurable material must be linked to classes that have a variant class type, to provide the characteristics for configuration. This is just a general material-to-class assignment, without assigned values. Assigning values would restrict the allowed values. You can assign a material to a class in any of the following situations: In master data maintenance (material master) In the classification menu (maintain allocation) In the configuration profile You can define how a BOM is exploded in configuration: Value assignment on top level only Interactive, multi-level configuration in sales order Depending on the type of configuration profile, you can also define whether: Manual changes to components are allowed Whether an order BOM is fixed (created automatically) How the order BOM is saved, and how fixing and instantiation works

© SAP AG

PLM146

2-25

Dependency Types

Precondition

Can a characteristic or characteristic value be included in the configuration? The characteristic or characteristic value CAN be included in the configuration

Selection condition

MUST an object be included in the configuration?

Procedure (action)

SETS characteristic VALUES or changes object items in the configuration, if the relevant object is included in the configuration

Constraint

Describes dependencies between SEVERAL objects in the configuration

© SAP AG 2006

-

Dependencies describe the interdependencies between objects in the configuration process. They are used in configuration to ensure that the configuration is complete and consistent. Paradigms of the SAP configurator: Declarative The user only declares rules and data The SAP System determines the processing sequence The only exception: procedures Object oriented Dependencies for objects selected in configuration are read Inheritance of dependencies

© SAP AG

PLM146

2-26

Interdependencies Between Objects in the Model Characteristics & Values

Assign dependencies

Material master

Variant class

Dependencies

Configuration profile

• Precondition • Sel. condition • Procedures • Actions • Constraints

Assign dependencies

Pricing (condition records)

Material variants Order BOMs Planning Engin. chg. mgmt ECM Engin. chg. mgmt OCM SCE configurator ...

Material BOM

Task List

Assign dependencies

Assign dependencies

© SAP AG 2003

© SAP AG

PLM146

2-27

Pricing in SD Surcharge CPU XXL/Minitower 430 UNI Price

Surcharge Modem

250 UNI

2,820 UNI

Surcharge Sound card

340 UNI

Total price

2,820 UNI

Create a multiple-value characteristic (such as SURCHARGE) with reference to field SDCOM-VKOND. Create condition records of condition type VA00 (absolute amounts) and (or) VA01 (percentage amounts). (The entry in key field "Variant" is entirely your choice.) Set up a pricing procedure in SD that reads condition types VA00 and (or) VA01. Assign the condition record to the characteristic value, or create dependencies (procedures or actions) for the pricing characteristic (SURCHARGE) as follows: $SELF.SURCHARGE = '' if characteristic ABC eq value 4711 ... Assign dependencies to the characteristic values or configuration profile. © SAP AG 2003

Pricing in R/3 sales is based on conditions. Objects in the configuration are described by characteristics and characteristic values. Pricing for configurable objects must therefore read the characteristics and values for a configurable material and SD conditions. Create a reference characteristic (such as SURCHARGE) with reference to field SDCOMVKOND. Create condition records with condition type VA00 (absolute amounts) and/or VA01 (percentage amounts). You can use both VA01 and VA00 in pricing. The key for the condition records is your choice. (Caution: these keys are case sensitive.) You create the one-to-one assignments between characteristic values and condition records using the user interface for configuration simulation. You use dependencies (procedures) to assign condition record keys to the reference characteristic, and enter conditions if required. You usually assign the procedure to the configuration profile. The following example illustrates the syntax: SURCHARGE is a reference characteristic for field SDCOM-VKOND. Surcharge_xyz is a variant condition key: $SELF. = ‘key of condition record’ IF - Example: $SELF.SURCHARGE = `Surcharge_xyz´ if EXTRAS eq `MODEM´ and EXTRAS eq `MOUSE´.

© SAP AG

PLM146

2-28

Material Variants

Material: PC_01 Sales: Item category group: NORM MRP: MRP group: 0065 Configurable product: PC

Routing Material-routing assignment

Status Released Locked Incomplete

Specific task list

Char. value assgmt CPU Casing Color

FAST TOWER Blue Specific BOM BOM Configurable material assignment

© SAP AG 2003

You create material variants with a material type that is kept in stock. To let you assign characteristic values to a material variant, you link the material to the configurable material whose characteristics you want to use to describe the variant. You can enter a cross-plant configurable material on the basic data screen. However, a cross-plant configurable material can only be used in purchasing. There, you can print out a document item with its assigned values. If you do not enter a plant-specific configurable material for the material, the characteristic values of the cross-plant configurable material are displayed. Before you can use variant matching in SD, you must enter a plant-specific configurable material in the MRP data of the material master. To assign values, choose Configure Variant. You also need to define a BOM for material variants. You can either create a new BOM for the material, which is separate from the configurable material, or you can link the material variant to the BOM of the configurable material. The BOM is then interpreted and exploded according to the values you assign in the material master record. You can also create a separate task list (routing) for the material variant, or use the task list of the configurable material. The task list for the configurable material is also interpreted and exploded according to the characteristic values assigned in the material master record.

© SAP AG

PLM146

2-29

Customizing for Classification

Default settings

Characteristic status

Characteristics groups

Templates

Maintain object types

Objects

Object table? Class status

MARA Class type?

Organizational areas

001 200, 300

Text types Classification status

Class groups

Functions and filters User profile © SAP AG 2002

Menu path: In the SAP Reference IMG: Cross-Application Components --> Classification --> Classes/Characteristics In Customizing for classification, under Characteristics, you can: Define default settings Define characteristics groups Check the statuses supplied and change them if required Define template characters and templates The class statuses, organizational areas, text types for classes, classification statuses, and functions and filters for finding objects are defined separately for each class type. Class statuses and classification statuses are predefined in the standard system. You can check the statuses and change them if required. In the same way as for characteristics, you can define groups for classes. Class groups are not dependent on class type.

© SAP AG

PLM146

2-30

Customizing for Variant Configuration

Maintenance authorizations Dependency status Dependency groups Variant tables Variant functions (For each object type): Configuration profile status Maintain settings Customer enhancements © SAP AG 2002

Menu path: In the SAP Reference IMG: Logistics General --> Variant Configuration

© SAP AG

PLM146

2-31

Variant Configuration: Consolidation: Unit Summary You are now able to: With the help of an overview of the basics of variant configuration as covered by course PLM140: Use all the functions taught in PLM140 See where the new topics covered by course PLM146 fit into the modeling process as a whole These include: Procedure for variant configuration modeling Classification tools Material master, bills of material, and task lists Configuration profile Dependencies

© SAP AG 2003

© SAP AG

Pricing and material variants Customizing

PLM146

2-32


Contents: Function of the configuration profile Basic data and class assignment Configuration initial screen Configuration parameters Settings Sales order and order BOM processes

Details of filter Details of interface design

© SAP AG 2002

© SAP AG

PLM146

3-33

Control Options in the Configuration Profile: Unit Objectives

At the conclusion of this unit, you will be able to Define all settings in the configuration profile Explain the effects of the control options in the profile

© SAP AG 2002

© SAP AG

PLM146

3-34

Control Options in the Profile: Course Overview Diagram

Course Overview

1


6


2


7


3


8


4


9


5

Conclusion

10

© SAP AG 2002

© SAP AG

PLM146

3-35

Control Options in the Profile: Business Scenario

In the design phase, you need to determine which configuration scenarios to work with. One important factor is the business scenario: ATO = assemble-to-order (according to catalog) MTO = make-to-order (individual products) ETO = engineer-to-order (projects)

© SAP AG 2002

© SAP AG

PLM146

3-36

Configuration Profile for a Material

Selecting a class type Provides characteristics Enables link to variant class

Variant class Material master

Defining the configuration scenario Other control parameters Allowed screens, initial screen Availability check Scenario-based control parameters

© SAP AG 2002

© SAP AG

PLM146

3-37

Configuration Profile: Basic Data

Structure:

Basic data Configuration initial screen

P-501

Material Profile name Basic data

see following slides

Pump (Order BOM configuration)

Profile_1

Confign initial screen

Class Type

300

Status

Variants

Class Assignment

Released

Valid From Start Logo

Dependencies

© SAP AG 2003

© SAP AG

PLM146

3-38

Configuration Profile: Configuration Initial Screen

Configuration initial screen structure: Basic data Confign initial screen

Confign Parameters

UserInterf

Process

Order BOM

User interface (all profile-specific settings) see following slides

Sales Order

BOM Explosion

Plnd/Prod. Order

None

Sales Order (SET)

Sing-Level

Order BOM

Multilevel

Configuration parameters (7 configuration scenarios)

Knowl.-Based

Depending on configuration scenario: Order BOM see following slides

Result-Oriented

BOM application PP01

Production - general

Filter

Order Functions Component Availability

Sales order (manual changes allowed)

Level of Detail Only Configurable Assemblies

© SAP AG 2003

© SAP AG

PLM146

3-39

Configuration Profile: Filters, Priority, and Simulation Filter: Option of restricting the BOM explosion in high-level configuration according to: - Object type (material, class, document, text) - Item category (D, I, K, L, M, N, R, T) - Item status (relevancy indicators) - Sort strings

Priority of Configuration Profile: In dialog mode: Sequence of configuration profiles shown

Without dialog (ALE, IDoc): Profile of highest priority (= lowest number) is selected

Simulation of functions in

Sales Engineering Planned order

© SAP AG 2003

The use of filters lets you restrict the explosion of BOMs in high-level configuration. The filters apply to all high-level configuration, so components that are not displayed because of the filter are ignored in both the sales order and in order BOM maintenance. The BOM explosion in high-level configuration can be restricted by the level of detail in the configuration profile and the definition of BOM applications assigned to the configuration profile, as well as by filters.

© SAP AG

PLM146

3-40

Configuration Profile: User Interface Interface design is created in an interface-design profile: - Characteristics groups - Sequences Authorization object - Relevancy to printing C_LOVC_DSG - Language Settings for: (also alternative language) - Display options - Scope - Pricing - Default values - Configurator

Confign initial screen

UserInterf Interface design Settings

(Can be overwritten for user in configuration simulation)

Confign browser Allowed screens

Start with

Char. value assgmt

Char. value assgmt

Result

Result

Master Data

Master Data

Confign structure

Confign structure

1. "Current settings" 2. "User settings" 3. "Profile settings"

© SAP AG 2003

Interface design: Name of interface design: Any character string up to 18 characters (such as material number) Name is unique and linked internally with a number from the number range Checks for same name of interface design: Results in identical interface design Possible for materials with identical class assignment Class assignment can be changed later => no check => problem! Configuration browser The configuration browser lets you navigate around the configuration structure, and at the same time displays the value assignment screen for the selected material, so that you can enter values. The configuration browser thereby replaces the configuration structure screen and value assignment screen, so you can only select the configuration browser if you have not selected these screens. Settings Can be defined in the configuration profile. They are then saved for the specific configuration profile. These settings have the lowest priority.

© SAP AG

PLM146

3-41

Can be defined on the value assignment screen. If you save these settings, they are saved for your user for all configuration profiles. These settings have a higher priority. Settings that you define on the value assignment screen and do not save are known as the current settings. These settings have the highest priority. However, you can switch between the 3 different settings at any time (provided that they exist).

© SAP AG

PLM146

3-42

Configuration Profile: Order BOM

Settings for the order BOM: Maintenance in order allowed Automatic fixing

Fix:

Selected assys

Instantiate:

Selected assys

Top down

Top down

Bottom up

Bottom up (Only for result-oriented order BOM)

© SAP AG 2003

© SAP AG

PLM146

3-43

Configuration Profile: Scenarios Configuration scenarios Planned/production order & no BOM explosion (= old Planned/production order - single-level) Planned/production order & single-level BOM explosion Order BOM & single-level BOM explosion Sales order and single-level BOM explosion Planned/production order & multilevel BOM explosion (= old Planned/production order - multilevel) Order BOM & multilevel BOM explosion (If knowledge-based = old Order BOM) Sales order & multilevel BOM Explosion (= old Sales order)

© SAP AG 2003

Single-level BOM explosion for the header material. In other words, the (single-level) BOM of the material is exploded. The BOM explosion stops after this. Any configurable assemblies in this BOM can be configured, provided that their configuration profiles allow it. Single-level BOM explosion for configurable assemblies according to the functionality above. The prerequisite for this is that the material above the assembly has a multilevel configuration scenario and its BOM has been exploded.

© SAP AG

PLM146

3-44

Overview: Combinations of Scenarios Header Component

Planned/Prod. Single-level/ No BOM multilevel explosion Plnd/prod.

Single-level/ multilevel Sales order

Single-level/ multilevel Order BOM

Plnd/prod. No BOM explosion Single/multilevel Plnd/prod. order Single/multilevel Sales order Single/multilevel Order BOM

( )

Possible / allowed

( ) Possible / allowed, but only with same way of storing order BOM No effect ->

(Note 14 87 78) © SAP AG 2002

© SAP AG

This component is treated as though its profile did not exist or were not released. This profile is excluded from the profiles for selection.

PLM146

3-45

Control Options in the Profile: Unit Summary

You are now able to: Define all settings in the configuration profile Explain the effects of the control options in the profile

© SAP AG 2002

© SAP AG

PLM146

3-46

© SAP AG

PLM146

3-47

Control Options in the Configuration Pr –

Exercises

Unit:


Topic:

Create Configuration Profile

At the conclusion of these exercises, you will be able to: • Create detailed configuration profiles The exercise also covers: • Checking the master data required • Creating the characteristics, variant class, and configuration profile A configurable casing needs to be modeled. Material master records and the super BOM (without dependencies) already exist. Further master data needs to be maintained.

Assign the characteristics, classes, and dependencies that you have created to your characteristics/class/dependency group T-##. All the data already exists for group 00. It may help you to use this data as a template to copy from.

1-1

Check the master data that already exists for modeling the configurable casing T-VB1##. 1-1-1 Display material master record T-VB1## with the basic data, sales, and MRP views. Use the following organizational levels: Plant: 1000 Sales organization: 1000 Distribution channel: 10 1-1-2 Display the BOM for your casing with usage 1 in plant 1000. Compare it with the slide "1. Customer Example Part Structure (Casing)" in the appendix.

© SAP AG

PLM146

3-48

1-2

Create the characteristics, variant class, and configuration profile required for the example. 1-2-1 Create the following single-value characteristics (you can copy from group 00). The characteristics must be character format characteristics with 2 characters: Pump for

Pump type

T01_## Values: 01 02 03 04 T02_## Values: 01 02 03 04

Oil Water Waste water Suspension Vacuum Rotary Wing Wet pit

1-2-2 Create variant class T_VB1## for your configurable casing T-VB1## and assign the two characteristics you just created to this class. Assign the class to class group T-##. 1-2-3 Create a configuration profile for your configurable casing T-VB1##. Use a name of your choice for your profile. Assign your configurable casing to variant class T_VB1##. Set the following parameters: Process: Planned/production order BOM Explosion: None (Leave the rest as they default Check all other settings of the configuration profile, to see what the default settings for configuration profiles are. (Settings, …).

© SAP AG

PLM146

3-49

Control Options in the Configuration Pr

Solutions

Unit:


Topic:

Create Configuration Profile

1-1 1-1-1 User Menu → Material → Display → Display Current

Display material master T-VB1## (current status): Views:

Basic data 1 + 2 Sales: Sales Org. Data 1 + 2 Sales: General / Plant Data MRP 1 -4

Organizational levels:

Plant: Sales organization: 1000 Distribution channel: 10

1000

=> The material master record exists with at least these views for at least these organizational levels. 1-1-2 User Menu → Bill of Material → Material BOM → Display

Display BOM with usage 1 in plant 1000. Compare it with the slide "1. Customer Example Part Structure (Casing)" in the appendix. 1-2 1-2-1 User Menu → Classification → Master Data → Characteristics

Create single-value characteristics (you can copy from group 00): T01_##

© SAP AG

Pump for

PLM146

3-50

T-## 1 Released Character format (CHAR) 2 characters

© SAP AG

PLM146

3-51

Values:

01 02 03 04

Oil Water Waste water Suspension

T02_##

Pump type T-## 1 Released Character format (CHAR) 2 characters

Values:

01 02 03 04

Vacuum Rotary Wing Wet pit

1-2-2 User Menu → Classification → Master Data → Classes

Create a variant class:

T_VB1## 300 Variant class Casing T-VB1## 1 (Released) T-## Characteristics:

T01_##

T02_## 1-2-3 User Menu → Variant Configuration → Configuration Profile → Create

Create a configuration profile for configurable material T-VB1##. Profile overview:

0-BOM(or any name)

Class assignment

T_VB1##

300 (class type)

Configuration initial screen:

© SAP AG

Configuration parameters

Process: Planned/production order BOM Explosion: None No further settings

UserInterf

No settings

PLM146

3-52

(On the Userinterf tab page, choose Settings and make a note of any default settings.)

© SAP AG

PLM146

3-53

Configuration Scenario: No BOM Explosion

Contents: Overview of scenario Combinations of configuration profiles System performance and configuration profiles Selection conditions Problems with $parent and $root Table access TYPE_OF

© SAP AG 2002

© SAP AG

PLM146

4-54

Configuration Scenario: No BOM Explosion: Unit Objectives

At the conclusion of this unit, you will be able to: Model configuration tasks using the scenario without BOM explosion, taking account of elementary performance considerations Use class nodes correctly in this scenario Formulate complex selection conditions

© SAP AG 2002

© SAP AG

PLM146

4-55

Configuration Scenario: No BOM Explosion: Course Overview Diagram

Course Overview

1


6


2


7


3


8


4


9


5

Conclusion

10

© SAP AG 2002

© SAP AG

PLM146

4-56

Configuration Scenario: No BOM Explosion: Business Scenario

Your configurable product is modeled in its entirety. This means that you do not need orderspecific post-processing for the BOM and routing. The configurable product is configured on one level. The product structure is not relevant to sales.

© SAP AG 2002

© SAP AG

PLM146

4-57

IDES Example: No BOM Explosion

P-500 (Plnd/prod, 0 levels)

Rtg

Casing G

Shaft assembly (No profile)

Support Rtg

Casing A

Characteristics: Pump for: Oil, Water, Waste w. Mode Pump type: Plunger, Rotary ... Connection: RAngle, Rd2, Rd4 ...

Class: Color

Chars: COLOR GLOSS

Casing C

Bearing A Bearing B

Linchpin

Bearing C

Rtg

Shaft (No profile)

Slug

© SAP AG 2002

© SAP AG

PLM146

4-58

Configuration Scenario: No BOM Explosion: Overview Sales / Customer Only BOM master data Characteristic value assignment on top level Super BOM (Master data BOM) P-500 (Pump)

Sales order Sales order 10 P-500 (Pump)

Shaft assy Shaft

Assigned char. values Pump Pump for

Oil

Mode

Manual

Pump type

Plunger

Single-level, Single-level, interactive interactive value value assignment assignment

10 P-500 (Pump)

Values for Pump ...

...

Connection Right-angled flange © SAP AG 2002

Configuration Scenario: No BOM Explosion Value assignment: values are only assigned to the item in the sales order. (You can use constraints here.) Configuration: dependencies for BOM items are not processed until you explode the BOM (in material requirements planning (MRP), for example). Constraints are ignored. Dependencies for subordinate configuration profiles cannot (!) be processed. Dependencies for BOM items are processed, but only the values assigned to the header material can be used. BOM explosion: - is simulated in the simulation environment - does not take place in the SD / sales order - takes place in MRP Material requirements: independent requirements are generated for the item entered in the sales order. Type matching only occurs on the top level. Material variants (previously known as stockable types) are only found for the object that is being configured. This function is not available for configurable materials on lower levels.

© SAP AG

PLM146

4-59

Configuration Scenario: No BOM Explosion: Important Points

Only the $ROOT object can be interactively configured in the sales order. Only the material you enter ($ROOT object) becomes a (main) item in the SD sales order. Components and operations are determined automatically during the MRP run and when creating the production order. There is only a dynamic BOM or sequence of operations in the sales order. You can simulate the explosion of the BOM or task list in the simulation environment. The ATP availability check can be run from the sales order.

© SAP AG 2002

The function for creating order-specific routings is not affected by settings for the configuration scenario, so this function can be used here. Note: The authorization object for an interface design is: C_LOVC_DSG

© SAP AG

PLM146

4-60

Combinations of Configuration Scenarios Effective No profile

No BOM explosion Planned/prod. order

No BOM explosion Planned/prod. order

Same as No profile *)

Single-level explosion Planned/prod. order


Multilevel explosion Planned/prod. order


Single-level explosion Order BOM


Multilevel explosion Order BOM


Single-level explosion Sales order


Multilevel explosion Sales order


*) = Can be used in purchase orders in purchasing © SAP AG 2002

When you create a sales order for a configurable material with the scenario No BOM explosion, you can only assign characteristic values to the header material, so only the dependencies for the configuration profile of the header material are active. You cannot assign values to a configurable assembly with a profile. However, you can use the profile in purchasing in the following way: Assign the characteristics of the assembly to the variant class of the header material, as well as to the assembly. In purchasing documents, the values assigned to the header material are copied to the characteristics of the variant class of the assembly.

© SAP AG

PLM146

4-61

System Performance and Configuration Profiles

General for all scenarios: Few or no "allowed screens" Limited BOM explosion: Number of levels BOM application Filter Indicator "Configurable assemblies only"

© SAP AG 2003

© SAP AG

PLM146

4-62

Configuration Profile on Top Level Only

P-500 (No BOM explosion)

Characteristics: Pump for: Oil, Water, Waste w. Mode Pump type: Plunger, Rotary Connection: RAngle, Rd2, Rd4 Extras: With support, ...

Shaft assembly (No profile)

Support

$root = header $parent = next instance

Selection condition: $root.EXTRAS eq 'With... or $parent.EXTRAS eq 'With... not $self.EXTRAS eq 'With...

Bearing A Bearing B

Selection condition: $root.CONNECTION eq 'Rd2' or $parent.CONNECTION eq 'Rd2' not $self.CONNECTION eq 'Rd2'

Bearing C © SAP AG 2002

$self is not possible in selection conditions. In this scenario, you can only query values assigned to the header material, $root. In this scenario, you can also use $parent to query values assigned to the header material. The default is $root.

© SAP AG

PLM146

4-63

Configuration Profile on Several Levels

P-500 (No BOM explosion)

Characteristics: Pump for: Oil, Water, Waste w. Mode Pump type: Plunger, Rotary ...

Shaft assembly (No BOM explosion)

Selection conditions: Characteristic Connection cannot be used $parent $root

Bearing A Bearing B

Characteristics: ... Connection:

RAngle Rd2 Rd4

Characteristic Connection - No interactive value assgmt - Dependencies cannot infer value

Bearing C © SAP AG 2002

Characteristics CONNECTION, and so on, of assembly SHAFT ASSEMBLY cannot have values assigned to them in the sales order, if you create a sales order for the Pump P-500. No data can be saved for the shaft assembly. In purchasing, a configuration profile for the shaft assembly can be used as a filter. If I create a purchase order for the shaft assembly, and the shaft assembly has no configuration profile, all the values assigned to the header material are copied to the purchase order. If I create a purchase order for the shaft assembly, and the shaft assembly has a configuration profile, the values assigned to the header material are only copied to the purchase order if the characteristics are also assigned to the configuration profile of the shaft assembly.

© SAP AG

PLM146

4-64

Class Nodes in This Scenario

P-500 (Plnd/prod, 0 levels)

Class: Color

Characteristics: Pump for: Oil, Water, Waste w. Mode ... Color: Red, Blue, Green

Caution ! Color is read only if no values for class node Characteristics: Color: Red, Blue, Green Gloss: yes/no Action $self.GLOSS = 'Yes' if ...

No manual specialization of class node with this scenario Only automatic specialization of class node possible, by: - Value assignment on value assignment interface or - Value assignment for class node by procedure © SAP AG 2002

If the value assigned to characteristic COLOR is sufficient to specialize the class node, you can work this way. If 2 different materials have the value 'Blue' and one has GLOSS 'Yes' while the other has GLOSS 'No', and no value is assigned to characteristic GLOSS, you have no influence over which material is selected in material requirements planning (MRP). To optimize system performance, if you use class nodes with automatic specialization, use an additional selection condition for cases where no material is needed or no material can be found.

© SAP AG

PLM146

4-65

Selection Conditions (Complex) Sales order Confble matl

RAM: giant

RAM: large

Application: ... CPU: ... Hard disk: ...

RAM: standard

Selection condition:


APPLICATION APPLICATION eq eq ’PHOTO' ’PHOTO' and CPU eq eq ’fast' ’fast' and Hard Hard disk eq ’large' OR OR APPLICATION APPLICATION eq eq ’PHOTO' ’PHOTO' and CPU eq eq ’fast' ’fast' and Hard Hard disk eq ’medium' OR...... OR......

APPLICATION APPLICATION eq eq ’TEXT' ’TEXT' and and CPU eq eq ’medium' ’medium' and and Hard disk disk eq ’medium' ’medium' OR APPLICATION APPLICATION eq eq ’SERVER' ’SERVER' and CPU eq ’standard' ’standard' and Hard Hard disk eq eq ’large' OR...... OR......

© SAP AG 2002

If you want a BOM item or operation to be selected according to complex selection conditions, it is often useful to define tables with the allowed combinations of values and use selection conditions to access the table.

© SAP AG

PLM146

4-66

Table and (Complex) Selection Conditions

Table SEL Application

Hard disk

CPU

Char. 4

PHOTO

Large

Fast

A

PHOTO

Medium

Fast

A

SERVER

Large

SERVER

Large

TEXT

Medium

Medium Slow Medium

B C C

Each line represents a valid combination of characteristic values © SAP AG 2003

If you want to access one table in selection conditions for several BOM items, you must define in the table which table line refers to which BOM item. To do this, you create an additional characteristic (the 4th characteristic, in this example) to identify the BOM item. For each selection condition, you enter the characteristic value that is to trigger the selection condition. The table is only read if all its characteristics have values assigned in the sales order. If no entry in the table matches the values assigned, no component is included in the exploded BOM. Example of a selection condition: table SEL (APPLICATION = $parent.APPLICATION, HARD_DISK = $parent.HARD_DISK CPU = $parent.CPU, CHAR_4 = 'A')

© SAP AG

PLM146

4-67

Selection Condition Without TYPE_OF

Sales order KMAT Configurable BIKE

Sales order

Extras: Pump ...

KMAT Configurable MOPED

KMAT

KMAT

Extras

Pump

Extras: Pump ...

Extras

Selection condition: EXTRAS eq 'PUMP'

© SAP AG 2002

If a configurable assembly is used multiple times as a component, there are 2 possibilities: 1.) Without TYPE_OF In the selection condition, only the values assigned to the header material are used. A selection according to the type of the header material is not possible.

© SAP AG

PLM146

4-68

Selection Condition with TYPE_OF

Sales order KMAT Configurable BIKE

Sales order

Extras: Bell ...

KMAT Configurable MOPED

KMAT

Extras: Bell ...

KMAT

Extras

Extras

Bell 1

Bell 2



TYPE_OF ($ROOT, (300)BIKE) AND EXTRAS eq 'BELL'

TYPE_OF ($ROOT, (300)MOPED) AND EXTRAS eq 'BELL'

© SAP AG 2002

2.) With TYPE_OF In the selection condition, the values assigned to the header material and the type of the header material are both used. Reference to header material using material number: TYPE_OF ( $ROOT, (MATERIAL) (300) ( NR = 'BIKE' ) ) Reference to header material using class number: TYPE_OF ( $ROOT, (300) BIKE )

© SAP AG

PLM146

4-69

Configuration Scenario: No BOM Explosion: Unit Summary You are now able to: Model configuration tasks using the scenario without BOM explosion, taking account of elementary performance considerations Use class nodes in this scenario Formulate complex selection conditions, using: $parent and $root Multiple table calls TYPE_OF

© SAP AG 2003

© SAP AG

PLM146

4-70

© SAP AG

PLM146

4-71

Configuration Scenario: No BOM Exp

Exercises

Unit:


Topic:

Selection Conditions with Table Calls

At the conclusion of these exercises, you will be able to: • Maintain multiple table calls with selection conditions The exercise also covers: • Table maintenance The conditions under which several components are selected are to be stored in a variant table and accessed using selection conditions. Assign the characteristics, classes, and dependencies that you have created to your characteristics/class/dependency group T-##. All the data already exists for group 00. It may help you to use this data as a template to copy from. Read through the entire exercise before you start. 1-1 describes the task as a whole. 1-1

Assign selection conditions to the three casing items in the BOM of your configurable casing T-VB1## (graycast, aluminum, and steel) to ensure that the components are selected according to the following list: Pump for: 500-101 (Graycast): 500-102 (Aluminum):

500-103 (Steel)

© SAP AG

Pump type:

Oil Waste water

Vacuum

Oil Waste water Suspension

Rotary Wet pit

Water Water Waste water

PLM146

Vacuum Wet pit

Rotary Wing Wing

4-72

© SAP AG

PLM146

4-73

1-1-1 Create variant table T_SEL_COND_## that maps the possible combinations shown above. Remember that an additional characteristic is required to represent the casing types. Enter exactly one value for each characteristic in each table line. The additional characteristic must be a character format characteristic with one character. This is important for another exercise later on (link between variant table and database table). 1-1-2 Create selection conditions that refer to this table and assign the selection conditions to the relevant BOM items. Remember that the casing can be an assembly in another structure. ($root or $parent?) 1-1-3 Test the result.

© SAP AG

PLM146

4-74

Configuration Scenario. No BOM Explo Solutions Unit:


Topic:

Selection Conditions with Table Calls

1-1 1-1-1 User Menu → Classification → Master Data → Characteristics

Create additional characteristic for mapping casing types. Create:

T03_## Casing type T-## Character format (CHAR) Values:

1

Graycast 2 3

1 character

Aluminum Steel

User menu→ Variant Configuration → Tools → Table Structure → Create

Create variant table:

T_SEL_COND_## Table for selection conditions 1 (Released) T-##

Characteristics:

© SAP AG

T01_## T02_## T03_## (No key required)

PLM146

4-75

User menu→ Variant Configuration → Tools → Table Contents → Maintain

Fill variant table: T_SEL_COND_## T01_##

T02_##

01 (Oil) 01 (Oil) 02 (Water) 02 (Water)

01 (Vacuum) 1 (GC) 04 (Wet pit) 2 (Alu) 02 (Rotary) 3 (St.) 03 (Wing)

T03_## Table maintenance:

3 (St.) 03 (Waste water) 01 (Vacuum) 1 (GC) 03 (Waste water) 02 (Rotary) 2 (Alu) 03 (Waste water) 03 (Wing) 3 (St.) 04 ( Suspension) 04 (Wet pit)

2 (Alu)

(GC=Graycast, Alu=Aluminum, and St.=Steel.) 1-1-2 (Create global dependencies during assignment) User Menu → Bill of Material → Material BOM → Change

T-VB1## Plant: 1000 Usage: 1 ...(Item Overview) → Pushbutton = Ctrl + F1 or Extras → Object dependencies → Assignments

Selection condition for component: 500-101 (Graycast): T_SC_T03_##_1 table T_SEL_COND_## (T01_## = $parent.T01_##, T02_## = $parent.T02_##, T03_## = '1' ) similarly (by copying the above selection condition): Selection condition for component: 500-102 (Aluminum): T_SC_T03_##_2

… T03_## = '2' )

Selection condition for component: 500-103 (Steel):

© SAP AG

PLM146

4-76

T_SC_T03_##_3

© SAP AG

… T03_## = '3' ).

PLM146

4-77

1-1-3 User menu→ Variant Configuration → Environment → Configuration Simulation

Configuration simulation: T-VB1## Plant: 1000 (Sales/distribution) (BOM) => Final state can be checked in result (BOM application PP01) or in planned order

© SAP AG

PLM146

4-78


Contents: Overview and system performance Application examples for the INFERENCES section Value assignment for class nodes

© SAP AG 2002

© SAP AG

PLM146

5-79

More About Constraints: Unit Objectives

At the conclusion of this unit, you will be able to: Process equations and tables in ways that are not covered by procedures (actions) Use restrictable characteristics Name the options for improving system performance with regard to constraints and variant tables

© SAP AG 2002

© SAP AG

PLM146

5-80

More About Constraints: Course Overview Diagram

Course Overview

1


6


2


7


3


8


4


9


5

Conclusion

10

© SAP AG 2002

© SAP AG

PLM146

5-81

More About Constraints: Business Scenario

Modeling in larger configuration structures Use of functions only available in constraints

© SAP AG 2002

© SAP AG

PLM146

5-82

Constraints

Constraints Constraint 3

Infer values and check consistency

Constraint 2

Between any objects in a configuration task

Constraint 1

Active in configuration only No effect on BOM and task-list explosion in low-level configuration (in MRP, for example)

Dependency net

Cannot replace selection conditions and procedures Additional functions

© SAP AG 2002

Constraints are especially necessary for multilevel, interactive configuration. Constraints read or write characteristic values as well as: - The configurable material and its assigned classes or class structures - Multiple levels of the BOM structure or class hierarchy The additional functions that constraints provide are also useful in single-level configuration. Constraints can and should be used instead of actions to set up the user interface for value assignment. Constraints are only active during interactive configuration. Constraints are ignored when you explode a BOM or task list dynamically in material requirements planning (MRP) or when you create a production order. Constraints can only be created locally within a constraint net. You assign the constraint net to the configuration profile.

© SAP AG

PLM146

5-83

Parameters in a Constraint OBJECTS Declaration of all classes and objects used

CONDITION Prerequisite for processing the constraint

RESTRICTION(S) Relation between elements in the OBJECTS section that must be true Value inference and consistency check Direct or using variant functions and variant tables

INFERENCES Definition of which characteristic values are to be inferred (from equations, tables, or functions) © SAP AG 2002

A constraint has up to 4 sections, but has at least the 2 sections OBJECTS and RESTRICTIONS. You only use the CONDITION and INFERENCES sections if required. These sections are always in the same order. You can close each section with a period.

© SAP AG

PLM146

5-84

OBJECTS Section (Declaration)

(300)

PC

Class type

Class name

Declaration of an object (class)

(Material)

(300)

Object identifier

Class type

= (Nr Partial key name

'PC_01') Partial key value

Declaration of other object (such as material) © SAP AG 2002

To declare an object, you enter the class type and class name. To declare a specific object, such as a material, you enter: Object identifier defined in Customizing Class type (optional) Name of the partial key for the object, as defined in Customizing Partial key value (the partial key for a material is the material number ) Quote marks and parentheses must be used as shown. If you do not enter the class type, you must enter empty parentheses ( ). Example of document declaration: (Document) (017) (Type = `DRW´ , Version = `00´ , Part = `000´ , Nr = `P-100´)

© SAP AG

PLM146

5-85

Variables for Objects, Classes, and Characteristics

X Variable name

is_a

Y Variable name

is_object

(300) PC Object declaration for class (Material) (300) (Nr = 'PC_01') Object declaration for material

(300) PC SW OS Variable name

where = =

; Software Operating system , (300) PR ... . Characteristic name

© SAP AG 2002

Constraint variables are subject to the same naming conventions as characteristics and classes. However, you can start the name with a query (?). The variables only apply locally in the constraint. Examples of valid variable names: X or ?X or ?my_variable Convention for object declaration of a class: is_a Other object declaration: is_object

PLM146 - Variant Configuration - Scenarios & Enhancements

Recommend Documents