Products which have similar estrcutures and need a logic to assemble , sap use variant configuration to describe in a inteligent code the possibility to change COMPONENTS of the product, without creating another bill of material
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
Variant configuration in SAP allows companies to simplify manufacturing of products with many variations by defining configurable attributes, characteristics, and rules to dynamically generate bills of materials and routings based on customer specifications. Master data like characteristics, classes, configurable materials, super bills of materials, and super routings provide the configuration knowledge base. Sales orders then prompt for characteristic values, applying the configuration rules to select the appropriate components and operations for manufacturing the variant.
This document provides an agenda for training on variant configuration in SAP. It will cover an overview of variant configuration, how it integrates across modules, the process steps, required master data including characteristics, classes, and configuration profiles, configuration simulation, object dependencies, and include time for Q&A. The target audience is primarily SAP SD and PP consultants, solution architects, and other SAP consultants and delivery teams. The training will demonstrate how variant configuration is used to efficiently configure products with multiple part combinations like computers and cars.
This document provides an overview of variant configuration in SAP. Variant configuration allows checking technical feasibility and pricing of product variants when creating a sales order. It is integrated with various SAP applications including classification, materials management, production planning, and sales. Key concepts discussed include classes, characteristics, super BOMs, routings, object dependencies, and material variants. The document walks through the process of configure-to-order production using variant configuration from sales order through production order settlement.
Variant configuration allows for simplifying production of products with variations by using a configurable BOM and routing that can select the required components and operations based on characteristic values chosen. It helps ensure the right product is produced and makes the sales process more efficient. Key aspects include super BOMs/routings that include all variants, characteristics to define variations, object dependencies to select components, and configuration in sales orders to trigger selection of needed components.
Variant configuration is a tool in SAP that helps simplify the production of products with variations. It uses characteristics and characteristic values to configure products in sales orders. This selects the appropriate components from a super bill of materials. Configurable materials can have pricing dependent on characteristic values. Standard variants can also be predefined and planned for high demand configurations.
SAP Variant Configuration Training helps for sizable amount of combination of components to enter the product. We provide SAP VC Training at corporate level
The document provides steps for setting up variant configuration in SAP. It describes configuring a Dell computer with options for RAM, hard disk, processor, and color. Key steps include: 1) Creating a class and defining characteristics; 2) Creating material masters for components; 3) Building a super BOM with optional components; 4) Creating a configuration profile; and 5) Generating a sales order to run MRP for the configured material. The document also outlines master data settings needed to enable variant configuration in SAP.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
Variant configuration in SAP allows companies to simplify manufacturing of products with many variations by defining configurable attributes, characteristics, and rules to dynamically generate bills of materials and routings based on customer specifications. Master data like characteristics, classes, configurable materials, super bills of materials, and super routings provide the configuration knowledge base. Sales orders then prompt for characteristic values, applying the configuration rules to select the appropriate components and operations for manufacturing the variant.
This document provides an agenda for training on variant configuration in SAP. It will cover an overview of variant configuration, how it integrates across modules, the process steps, required master data including characteristics, classes, and configuration profiles, configuration simulation, object dependencies, and include time for Q&A. The target audience is primarily SAP SD and PP consultants, solution architects, and other SAP consultants and delivery teams. The training will demonstrate how variant configuration is used to efficiently configure products with multiple part combinations like computers and cars.
This document provides an overview of variant configuration in SAP. Variant configuration allows checking technical feasibility and pricing of product variants when creating a sales order. It is integrated with various SAP applications including classification, materials management, production planning, and sales. Key concepts discussed include classes, characteristics, super BOMs, routings, object dependencies, and material variants. The document walks through the process of configure-to-order production using variant configuration from sales order through production order settlement.
Variant configuration allows for simplifying production of products with variations by using a configurable BOM and routing that can select the required components and operations based on characteristic values chosen. It helps ensure the right product is produced and makes the sales process more efficient. Key aspects include super BOMs/routings that include all variants, characteristics to define variations, object dependencies to select components, and configuration in sales orders to trigger selection of needed components.
Variant configuration is a tool in SAP that helps simplify the production of products with variations. It uses characteristics and characteristic values to configure products in sales orders. This selects the appropriate components from a super bill of materials. Configurable materials can have pricing dependent on characteristic values. Standard variants can also be predefined and planned for high demand configurations.
SAP Variant Configuration Training helps for sizable amount of combination of components to enter the product. We provide SAP VC Training at corporate level
The document provides steps for setting up variant configuration in SAP. It describes configuring a Dell computer with options for RAM, hard disk, processor, and color. Key steps include: 1) Creating a class and defining characteristics; 2) Creating material masters for components; 3) Building a super BOM with optional components; 4) Creating a configuration profile; and 5) Generating a sales order to run MRP for the configured material. The document also outlines master data settings needed to enable variant configuration in SAP.
The document discusses availability check configuration in SAP. Key points:
- Availability check verifies stock availability when creating sales orders.
- It can be configured using availability check groups, checking rules, and scope of check parameters.
- Configuration includes options like considering safety stock, stock in transit, blocked stock, and open purchase orders and sales requirements.
- Backorder processing allows assigning quantities from cancelled low priority orders to new high priority orders if stock is unavailable. It requires individual requirements to be set for the material.
This document outlines the configuration steps for automatically determining batches in delivery documents. Key steps include:
1. Configuring batch management strategies, access sequences, and search procedures.
2. Allocating the SD batch search procedure.
3. Activating automatic batch determination in sales orders and deliveries.
4. Creating a class for batch shelf life dates and maintaining it in material masters.
5. Creating batches for materials and maintaining shelf life expiration dates.
6. Maintaining condition records for batch search strategies to trigger automatic batch determination during delivery processing based on available stock batches.
In this presentation , I have covered WM-PP interface. The presentation gives an overview of the concept as well as the process flow with and without the interface.It also talks about the master data and the various parameters that play a key role in the WM-PP processes
Variant Configuration in SAP PP: Beginner's Guidesapdocs. info
1. The document provides guidelines for configuring and applying variant configuration in production planning. It demonstrates an MTO configuration scenario with characteristic parameter entry in the sales order, transfer of requirements from the sales order to MRP, conversion of planned orders to production orders, and selection of appropriate materials and operations from super BOMs and super routings to create deliveries of the finished product.
2. Key steps include creating characteristics, classes, a configurable material, super BOM, configuration profile, object dependencies, precondition/selection condition dependencies, super routing, testing the configuration, running MRP, creating production and purchase orders, confirming orders, and delivering the finished product.
3. The configuration allows parameters like car
SAP Data Migration With LSMW - Introduction and Key Conceptsanjalirao366
This document discusses SAP Data Migration With LSMW (Legacy System Migration Workbench). LSMW is a free SAP tool used to migrate non-SAP data into SAP. It can import large volumes of data from legacy systems into SAP efficiently with transformations. LSMW works with business objects rather than tables and requires little to no ABAP coding. The major tasks performed by LSMW are importing data from legacy systems, converting the data, and importing it into the SAP system. It can migrate different types of data like master data, transaction data, and configuration data.
This document provides instructions for configuring stock transport orders in SAP, which allow for the physical transfer of goods between two plants or company codes. It outlines the key configuration steps, which include defining a stock transport order document type, assigning shipping data and checking rules to plants, and associating delivery types and one-step procedures with document types and plant combinations. The configurations allow goods to be transferred between plants within a company code or across company codes with delivery and optional billing.
Condition technique is a configuration technique in SAP used to configure complex business rules, such as pricing. It consists of several key components, including a field catalog, condition tables, an access sequence, condition types, pricing procedures, and pricing procedure determination. Condition tables contain business rules and are accessed in the order specified by the access sequence. Condition types represent logical components like taxes or discounts. Pricing procedures combine condition types and are assigned to documents like sales orders. Overall, condition technique provides a rules engine for flexibly configuring diverse and changing business rules through its various components.
This document discusses how to configure a bill of materials (BOM) item as a variant material in SAP. It describes setting up a material called CYCLE as a configurable BOM item with characteristics like CYCLETYRES and CYCLEMODEL. It also covers creating a variant class, defining characteristic values and dependencies, building a configuration profile, and establishing variant conditions to control which sub-items are included based on the characteristic combinations selected. Finally, it shows how to create a sales order for the configured CYCLE material and have its BOM explode with the correct sub-items based on the variant condition rules.
The document discusses pricing concepts in SAP such as condition tables, condition types, access sequences, condition records, and pricing procedures. It provides definitions of these key terms and describes how to set them up in transactions like creating a condition table, defining condition types, and maintaining pricing procedures. Steps are outlined to go through the document and SAP documentation to understand these pricing concepts.
This document provides a summary of important tables and transaction codes for SAP SD (Sales and Distribution). It lists key master data tables for customers, sales documents, billing, delivery, and shipping. It also categorizes and lists commonly used transaction codes for business partners, items, conditions, sales processes, orders, billing, shipping, and more. The tables and transaction codes can be used to create, change, display and process sales documents and master records in SAP SD.
This article discusses how SAP can automatically determine which batch to use when creating a delivery based on the shelf life of the material. This is useful for industries like pharmaceuticals where batches closer to expiration should be delivered first. The document provides steps to configure SAP including importing standard characteristics, creating a class, setting up the material master, goods receipt, and multiple batches. It also demonstrates testing the configuration with a sales order, delivery, and billing document.
1) Availability check in SAP SD checks if sufficient material is available on the calculated availability date to deliver goods to customers on the requested delivery date. It is done at the plant level and considers factors like replenishment lead time and partial vs complete delivery.
2) Customization of availability check can be done by configuring transfer of requirements, planning strategies, MRP groups, checking groups, and schedule line categories to control the scope and level of checking.
3) Key determinants include requirements class, checking group, strategy group, and delivery item category, which control whether checking occurs and at what level or frequency.
This document provides steps for configuring and executing a make-to-order process in SAP ERP. It explains how to create materials, bills of materials, routings, sales orders, planned orders, purchase requisitions, purchase orders, goods movements, production orders, and deliveries to fulfill a customer order from sales to delivery. The major steps include sales order creation, planning, external procurement, subcontracting, production, and delivery.
This document discusses movement types in Materials Management and Inventory Management (MM-IM) in SAP. It defines movement types, explains how they influence goods movements and valuations, and describes the key tables that define movement types. Movement types determine stock and value updates, screen layouts, and more. The document provides examples of common movement type configurations.
This document outlines different types of plant to plant transfer orders including transfers without and with stock transport orders, with and without billing, and different document, delivery, billing, and pricing types as well as how stock is handled and costs are determined for each order type. It provides information on internal order processes for moving materials between plants.
This document provides training on running MRP processes in SAP. It explains how to prepare for an MRP run by closing open purchase orders, production orders, and schedule lines. It then outlines the steps to run MRP using transaction code MD02 for a single item, including parameters to set and how to view the results. The MRP run will create planned orders and purchase requisitions based on the production plan and dependent requirements.
How To Create Subcontracting Process In SAP MM _ Tech Azmaan.pdfkpkdhar36
This document outlines the steps to create a subcontracting process in SAP MM, including: 1) creating material and vendor masters; 2) generating a subcontracting purchase order; 3) releasing the purchase order; 4) transferring material and posting a goods receipt; 5) reconciling quantities using a subcontracting challan; and 6) verifying invoices.
Mts and mto and account based copa and costing based copa Intelligroup, Inc.
1) The document discusses two types of costing in SAP: make-to-order and make-to-stock production, as well as two types of COPA (cost of production analysis) costing: costing-based and account-based.
2) Make-to-order production is triggered by customer orders, while make-to-stock production is based on demand planning. Costing-based COPA uses value fields to store costs, allows viewing cost breakdowns, and activating sales orders.
3) Account-based COPA is for reconciliation, updates GL accounts directly, and does not allow viewing breakdowns or activating sales orders.
Reasons to use a constraint-based product configuration model.
-Respond to the specialized needs of the customer.
-Reduce high costs tied to stocking and moving inventory.
-Lower records maintenance by reducing the number of products and BOMs’ managed.
Developer license is not required to create and maintain product configuration models in Microsoft Dynamics AX 2012.
Customers can purchase items that meet their individual needs. Instead of having one or two choices when purchasing a home entertainment system, through Constraint Based Configuration and Dynamics AX you can configure the product specifically for a customer.
The document provides information on using the BEX Query Designer in SAP BW. It describes key components of the Query Designer including info providers, query elements, variables, reusable structures, formulas, and calculated key figures. The Query Designer allows users to define queries, filters, and calculations not available directly in the info providers to retrieve and analyze data from SAP BW.
The document discusses availability check configuration in SAP. Key points:
- Availability check verifies stock availability when creating sales orders.
- It can be configured using availability check groups, checking rules, and scope of check parameters.
- Configuration includes options like considering safety stock, stock in transit, blocked stock, and open purchase orders and sales requirements.
- Backorder processing allows assigning quantities from cancelled low priority orders to new high priority orders if stock is unavailable. It requires individual requirements to be set for the material.
This document outlines the configuration steps for automatically determining batches in delivery documents. Key steps include:
1. Configuring batch management strategies, access sequences, and search procedures.
2. Allocating the SD batch search procedure.
3. Activating automatic batch determination in sales orders and deliveries.
4. Creating a class for batch shelf life dates and maintaining it in material masters.
5. Creating batches for materials and maintaining shelf life expiration dates.
6. Maintaining condition records for batch search strategies to trigger automatic batch determination during delivery processing based on available stock batches.
In this presentation , I have covered WM-PP interface. The presentation gives an overview of the concept as well as the process flow with and without the interface.It also talks about the master data and the various parameters that play a key role in the WM-PP processes
Variant Configuration in SAP PP: Beginner's Guidesapdocs. info
1. The document provides guidelines for configuring and applying variant configuration in production planning. It demonstrates an MTO configuration scenario with characteristic parameter entry in the sales order, transfer of requirements from the sales order to MRP, conversion of planned orders to production orders, and selection of appropriate materials and operations from super BOMs and super routings to create deliveries of the finished product.
2. Key steps include creating characteristics, classes, a configurable material, super BOM, configuration profile, object dependencies, precondition/selection condition dependencies, super routing, testing the configuration, running MRP, creating production and purchase orders, confirming orders, and delivering the finished product.
3. The configuration allows parameters like car
SAP Data Migration With LSMW - Introduction and Key Conceptsanjalirao366
This document discusses SAP Data Migration With LSMW (Legacy System Migration Workbench). LSMW is a free SAP tool used to migrate non-SAP data into SAP. It can import large volumes of data from legacy systems into SAP efficiently with transformations. LSMW works with business objects rather than tables and requires little to no ABAP coding. The major tasks performed by LSMW are importing data from legacy systems, converting the data, and importing it into the SAP system. It can migrate different types of data like master data, transaction data, and configuration data.
This document provides instructions for configuring stock transport orders in SAP, which allow for the physical transfer of goods between two plants or company codes. It outlines the key configuration steps, which include defining a stock transport order document type, assigning shipping data and checking rules to plants, and associating delivery types and one-step procedures with document types and plant combinations. The configurations allow goods to be transferred between plants within a company code or across company codes with delivery and optional billing.
Condition technique is a configuration technique in SAP used to configure complex business rules, such as pricing. It consists of several key components, including a field catalog, condition tables, an access sequence, condition types, pricing procedures, and pricing procedure determination. Condition tables contain business rules and are accessed in the order specified by the access sequence. Condition types represent logical components like taxes or discounts. Pricing procedures combine condition types and are assigned to documents like sales orders. Overall, condition technique provides a rules engine for flexibly configuring diverse and changing business rules through its various components.
This document discusses how to configure a bill of materials (BOM) item as a variant material in SAP. It describes setting up a material called CYCLE as a configurable BOM item with characteristics like CYCLETYRES and CYCLEMODEL. It also covers creating a variant class, defining characteristic values and dependencies, building a configuration profile, and establishing variant conditions to control which sub-items are included based on the characteristic combinations selected. Finally, it shows how to create a sales order for the configured CYCLE material and have its BOM explode with the correct sub-items based on the variant condition rules.
The document discusses pricing concepts in SAP such as condition tables, condition types, access sequences, condition records, and pricing procedures. It provides definitions of these key terms and describes how to set them up in transactions like creating a condition table, defining condition types, and maintaining pricing procedures. Steps are outlined to go through the document and SAP documentation to understand these pricing concepts.
This document provides a summary of important tables and transaction codes for SAP SD (Sales and Distribution). It lists key master data tables for customers, sales documents, billing, delivery, and shipping. It also categorizes and lists commonly used transaction codes for business partners, items, conditions, sales processes, orders, billing, shipping, and more. The tables and transaction codes can be used to create, change, display and process sales documents and master records in SAP SD.
This article discusses how SAP can automatically determine which batch to use when creating a delivery based on the shelf life of the material. This is useful for industries like pharmaceuticals where batches closer to expiration should be delivered first. The document provides steps to configure SAP including importing standard characteristics, creating a class, setting up the material master, goods receipt, and multiple batches. It also demonstrates testing the configuration with a sales order, delivery, and billing document.
1) Availability check in SAP SD checks if sufficient material is available on the calculated availability date to deliver goods to customers on the requested delivery date. It is done at the plant level and considers factors like replenishment lead time and partial vs complete delivery.
2) Customization of availability check can be done by configuring transfer of requirements, planning strategies, MRP groups, checking groups, and schedule line categories to control the scope and level of checking.
3) Key determinants include requirements class, checking group, strategy group, and delivery item category, which control whether checking occurs and at what level or frequency.
This document provides steps for configuring and executing a make-to-order process in SAP ERP. It explains how to create materials, bills of materials, routings, sales orders, planned orders, purchase requisitions, purchase orders, goods movements, production orders, and deliveries to fulfill a customer order from sales to delivery. The major steps include sales order creation, planning, external procurement, subcontracting, production, and delivery.
This document discusses movement types in Materials Management and Inventory Management (MM-IM) in SAP. It defines movement types, explains how they influence goods movements and valuations, and describes the key tables that define movement types. Movement types determine stock and value updates, screen layouts, and more. The document provides examples of common movement type configurations.
This document outlines different types of plant to plant transfer orders including transfers without and with stock transport orders, with and without billing, and different document, delivery, billing, and pricing types as well as how stock is handled and costs are determined for each order type. It provides information on internal order processes for moving materials between plants.
This document provides training on running MRP processes in SAP. It explains how to prepare for an MRP run by closing open purchase orders, production orders, and schedule lines. It then outlines the steps to run MRP using transaction code MD02 for a single item, including parameters to set and how to view the results. The MRP run will create planned orders and purchase requisitions based on the production plan and dependent requirements.
How To Create Subcontracting Process In SAP MM _ Tech Azmaan.pdfkpkdhar36
This document outlines the steps to create a subcontracting process in SAP MM, including: 1) creating material and vendor masters; 2) generating a subcontracting purchase order; 3) releasing the purchase order; 4) transferring material and posting a goods receipt; 5) reconciling quantities using a subcontracting challan; and 6) verifying invoices.
Mts and mto and account based copa and costing based copa Intelligroup, Inc.
1) The document discusses two types of costing in SAP: make-to-order and make-to-stock production, as well as two types of COPA (cost of production analysis) costing: costing-based and account-based.
2) Make-to-order production is triggered by customer orders, while make-to-stock production is based on demand planning. Costing-based COPA uses value fields to store costs, allows viewing cost breakdowns, and activating sales orders.
3) Account-based COPA is for reconciliation, updates GL accounts directly, and does not allow viewing breakdowns or activating sales orders.
Reasons to use a constraint-based product configuration model.
-Respond to the specialized needs of the customer.
-Reduce high costs tied to stocking and moving inventory.
-Lower records maintenance by reducing the number of products and BOMs’ managed.
Developer license is not required to create and maintain product configuration models in Microsoft Dynamics AX 2012.
Customers can purchase items that meet their individual needs. Instead of having one or two choices when purchasing a home entertainment system, through Constraint Based Configuration and Dynamics AX you can configure the product specifically for a customer.
The document provides information on using the BEX Query Designer in SAP BW. It describes key components of the Query Designer including info providers, query elements, variables, reusable structures, formulas, and calculated key figures. The Query Designer allows users to define queries, filters, and calculations not available directly in the info providers to retrieve and analyze data from SAP BW.
The document describes the process of designing, developing, testing, and maintaining a configuration model in Oracle Configurator. It includes steps for creating the configuration model structure and rules, importing BOM and inventory data, developing the UI, testing, publishing the model, and refreshing imported data. Key aspects covered are the model structure, logical rules, importing BOM models and data, UI templates, publishing models, and refreshing imported BOM data.
This document provides instructions for configuring various settings in SAP's Project System module, including:
1. Defining special characters, coding masks, and validation rules for project numbers.
2. Creating and maintaining project profiles to store default values and control parameters for new projects.
3. Configuring network types, profiles, numbering, and other settings for managing project networks.
4. Setting parameters for timescales, evaluation periods, and other options used in project planning boards and graphics.
The steps describe technical customizing activities like specifying length limits, indicator settings, default profiles, and other configuration options required to set up the Project System according to an organization's needs and processes.
This document discusses variant configuration which allows manufacturers to offer customized product variants according to customer requirements. It covers characteristics, classification, configuration profiles, dependencies, and pricing. Characteristics define product attributes. Classification assigns characteristics to classes. Configuration profiles link materials to classes. Dependencies set conditions to activate or hide characteristics based on selections. Pricing is added using procedures linked to variants. The document provides an example of setting up variant configuration for USB products with brands, storage, and extra features.
The document discusses different types of queries that can be used with a database connector in Mule, including parameterized, dynamic, and from template queries. It explains that parameterized queries improve security and performance by replacing expressions with parameters, while dynamic queries have flexibility but risk SQL injection. The document also describes how to configure a query from a template, which allows reusing a predefined SQL statement that can include parameterized variables.
The document discusses different modes for running a changes-only extract in Oracle Fusion HCM. A changes-only extract compares the current data to a previous extract to identify incremental changes. Four modes are supported: Y returns changed attributes; ATTRIBUTE returns changed and marked attributes; ATTRIB_OLD returns changed/marked attributes and previous values; and BLOCK_OLD returns changed/marked data and previous data grouped by the threading data group. Configuration involves setting a parameter, defining multi-threading, and marking key and changed attributes.
Oracle PIM: Phantasmal Item Descriptions in your OrganizationAXIA Consulting Inc.
One of the top US-based manufacturers in the material handling space had item descriptions were inconsistent, vague, duplicate, incomplete and many times incomprehensible. This presentation accentuates AXIA’s journey on item description standardization by methodical creation of parts taxonomy & classification, schema structure and enrichment of user defined attributes to generate item descriptions by leveraging the attribute values and functions in Oracle Product Information Management. It also includes business considerations and best practices that were employed by AXIA to achieve success.
The BEx Query Designer is a desktop application for defining queries on Business Information Warehouse data. It allows users to select and combine characteristics and key figures from an InfoProvider to determine how data is navigated and evaluated. Key functions include restricting characteristics, defining selections and formulas, and creating reusable structures. Defined queries can then be used for OLAP reporting, tabular reporting, and as data providers for applications like the BEx Analyzer and Web Application Designer.
Describe what a stored procedure is
Explain the advantages of a stored procedure over a view
Cover the basic syntax for creating a stored procedure
Show how to set values within variables
Control the flow through a stored procedure
Look at the differences between a function and a stored procedure
Cover the basic syntax for creating a T-SQL user-defined function
Temporary Tables
Cursors
This document discusses using object-oriented programming with ABAP in Business Warehouse (BW) applications. It provides an overview of ABAP object-oriented classes and methods. It then presents several scenarios for using classes and methods in BW transformations, the class constructor, custom functions for the formula builder, and BADIs for BW loading. The motivation for using ABAP OO in BW is discussed, including increased reusability, organization, and a more modern programming approach. Details are given on how to call class methods in BW routines using the ABAP editor's patterns button.
CMGT/410 v19
Business Requirements Template
CMGT/410 v19
Page 2 of 14Business Requirements TemplateHow to Use This Document
This document is a template for creating a Business Requirements Document (BRD); it includes instructions and examples for guidance. As you complete your BRD using the template, only include sections pertinent to your project.Table of Contents
How to Use This Document1
Table of Contents1
1.Executive Summary2
1.1Project Overview2
1.2Purpose and Scope of this Specification2
2.Product/Service Description3
2.1Product Context3
2.2User Characteristics3
2.3Assumptions3
2.4Constraints3
2.5Dependencies3
3.Requirements4
3.1Functional Requirements4
3.2User Interface Requirements5
3.3Usability5
3.4Performance6
3.4.1Capacity6
3.4.2Availability6
3.4.3Latency6
3.5Manageability/Maintainability6
3.5.1Monitoring6
3.5.2Maintenance6
3.5.3Operations7
3.6System Interface/Integration7
3.6.1Network and Hardware Interfaces7
3.6.2Systems Interfaces7
3.7Security8
3.7.1Protection8
3.7.2Authorization and Authentication8
3.8Data Management8
3.9Standards Compliance9
3.10 Portability9
4.User Scenarios/Use Cases9
5.Deleted or Deferred Requirements9
6.Requirements Confirmation/Stakeholder Sign-Off10
Appendices11
Appendix A: Definitions, Acronyms, and Abbreviations11
Appendix B: References11
Appendix C: Requirements Traceability Matrix12
Appendix D: Organizing the Requirements131. Executive Summary
1.1 Project Overview
Describe this project or product and its intended audiences, or provide a link or reference to the project charter.
1.2 Purpose and Scope of this Specification
Describe the purpose of this specification and its intended audience. Include a description of what is within the scope what is outside of the scope of these specifications.
Example:
In Scope
This document addresses requirements related to Phase 2 of Project A:
· Modification of Classification Processing to meet legislative mandate ABC
· Modification of Labor Relations Processing to meet legislative mandate ABC
Out of Scope
The following items in Phase 3 of Project A are out of scope:
· Modification of Classification Processing to meet legislative mandate XYZ
· Modification of Labor Relations Processing to meet legislative mandate XYZ
(Phase 3 will be considered in the development of the requirements for Phase 2, but the Phase 3 requirements will be documented separately.)2. Product/Service Description
In this section, describe the general factors that affect the product and its requirements. This section should contain background information, not state specific requirements (provide the reasons why certain specific requirements are later specified).
2.1 Product Context
How does this product relate to other products? Is it independent and self-contained? Does it interface with a variety of related systems? Describe these relationships or use a diagram to show the major components of the larger system, interconnections, and external interfaces.
2.2 User Characteristics
Create gen.
The document discusses material variants in SAP, which are materials created from configurations of a configurable material. Material variants have their own material master record linked to the configurable material. Configuration values in a material variant determine which BOM items and operations are used from the configurable material's BOM and routing. Cross-plant variants can be used for procurement but not sales since plant-specific data is not defined.
Oracle Configurator is a tool for configuring products and services that enables end users to select components and view configurations. Oracle Configurator Developer (OCD) provides a drag-and-drop interface to rapidly develop configuration models. The development process involves building model structures and rules, testing models, managing models in a repository, and publishing models for system testing.
The document discusses designing architecture using Attribute-Driven Design (ADD). It describes ADD as a method for designing an architecture to satisfy both functional and quality requirements. The key steps of ADD include choosing architectural drivers from quality scenarios and requirements, selecting an architectural pattern to address the drivers, and instantiating modules and allocating functionality to implement the pattern. As an example, it applies ADD to design a product line architecture for a garage door opener system.
This document discusses setting up parameters and defaults in Enterprise Asset Management (EAM). It describes setting up:
1. EAM parameters such as maintained number defaults, cost defaults, and work request/order defaults.
2. Areas to logically group assets by location.
3. Departments and resources to represent crews and assign resources to work orders.
4. Category codes and sets to classify assets using classes and subclasses to simplify searching.
- Form modules contain objects and code routines, menu modules contain menus and menu commands, and library modules contain reusable procedures, functions, and packages.
- Default file extensions are .fmb for form modules, .fmx for executable form modules, and .mmb and .mmx for menu modules.
- Data blocks contain form items while control blocks are independent of database tables and views. Property classes set reusable properties and visual attributes set appearance properties.
- Record groups provide data to LOVs and list items and enable client-side validation. They can be static, query-based, or non-query.
- Libraries contain reusable subprograms that can be attached to forms, menus, or other libraries.
The document provides an overview and training on Test Director 7.6 for Intralinks QA team members. It describes the key components of Test Director including access, requirements tracking, test planning, test execution, and defect management. It explains how each component will be used as part of Intralinks' testing process and standard operating procedures.
This chapter discusses different ways that components and services can be supplied, including reusing existing functionality, renting functionality from external sources, buying functionality externally, or building new functionality. It covers making supply decisions based on identifying functional units and whether they will be components or services. The main part discusses the component delivery workflow, including defining specifications, designing components, constructing them, testing, and rolling them out. It also discusses maintaining components over time.
The document provides an overview of OSGi Compendium specifications, which establish common services for OSGi frameworks, including specifications for declarative services, event administration, and 41 other specifications covering areas like configuration, HTTP, and device access. It also gives a brief introduction to the declarative services specification, explaining concepts like immediate and delayed components, using services, and the component lifecycle.
Discover the benefits of outsourcing SEO to Indiadavidjhones387
"Discover the benefits of outsourcing SEO to India! From cost-effective services and expert professionals to round-the-clock work advantages, learn how your business can achieve digital success with Indian SEO solutions.
Understanding User Behavior with Google Analytics.pdfSEO Article Boost
Unlocking the full potential of Google Analytics is crucial for understanding and optimizing your website’s performance. This guide dives deep into the essential aspects of Google Analytics, from analyzing traffic sources to understanding user demographics and tracking user engagement.
Traffic Sources Analysis:
Discover where your website traffic originates. By examining the Acquisition section, you can identify whether visitors come from organic search, paid campaigns, direct visits, social media, or referral links. This knowledge helps in refining marketing strategies and optimizing resource allocation.
User Demographics Insights:
Gain a comprehensive view of your audience by exploring demographic data in the Audience section. Understand age, gender, and interests to tailor your marketing strategies effectively. Leverage this information to create personalized content and improve user engagement and conversion rates.
Tracking User Engagement:
Learn how to measure user interaction with your site through key metrics like bounce rate, average session duration, and pages per session. Enhance user experience by analyzing engagement metrics and implementing strategies to keep visitors engaged.
Conversion Rate Optimization:
Understand the importance of conversion rates and how to track them using Google Analytics. Set up Goals, analyze conversion funnels, segment your audience, and employ A/B testing to optimize your website for higher conversions. Utilize ecommerce tracking and multi-channel funnels for a detailed view of your sales performance and marketing channel contributions.
Custom Reports and Dashboards:
Create custom reports and dashboards to visualize and interpret data relevant to your business goals. Use advanced filters, segments, and visualization options to gain deeper insights. Incorporate custom dimensions and metrics for tailored data analysis. Integrate external data sources to enrich your analytics and make well-informed decisions.
This guide is designed to help you harness the power of Google Analytics for making data-driven decisions that enhance website performance and achieve your digital marketing objectives. Whether you are looking to improve SEO, refine your social media strategy, or boost conversion rates, understanding and utilizing Google Analytics is essential for your success.
Bridging the Digital Gap Brad Spiegel Macon, GA Initiative.pptxBrad Spiegel Macon GA
Brad Spiegel Macon GA’s journey exemplifies the profound impact that one individual can have on their community. Through his unwavering dedication to digital inclusion, he’s not only bridging the gap in Macon but also setting an example for others to follow.
1. Variant Configuration
1 Variant Configuration
Variant configuration is for manufacturing complex products in which customer determines the
features of the product. Objective of variant configuration is to react quickly to customers’
requirements.
Here it needs not to create separate material for each variant of a product. When companies
introduce variant configuration this often goes beyond a business process re-engineering project.
Variant configuration offers an opportunity to restructure product structures for which then
processes are defined. This has a direct impact to the core areas such as marketing and product
data management.
2 Advantages of VC
· No need to Create separate material master for each variant combination.
· Super BOM and Super Routing is enough for representing all possible Variants and Operations.
· Able to react more flexible to customer demands.
· Increase Information exchange between sales, engineering and production.
3 What is Configurable Material?
· A material with different features or characteristics and options is known as configurable
material. Example: PC, Car.
· Configurable materials are either created in a material type that allows the configuration (n the
standard system, the material type KMAT) or they are given the indicator Configurable in the
material master record.
4 Master Data used for VC
Following Objects are used as Master data for Variant configuration.
1. Super BOM
2. Super Routing
3. Characteristic
4. Class
5. Object Dependencies
6. Configuration Profile
7. SD Condition records
4.1 Super BOM
Super BOM Contains all the components for producing configurable product. It contains both
variant as well as non-variant parts required for producing configurable product.
4.1.1 Super BOM configuration
Super BOM can be created either one of the following methods.
· Create BOM with class Item of 200-class type that contains all characteristic of a configurable
material.
· Create BOM with all possible materials as its components. Then assign /define dependencies to
2. each component.
The different between this two method is
· BOM with class item, no need to assign or define object dependencies. Instead of that each
material is classified in material master itself using class 200.
· For both cases all characteristics are assigned to class 300 which is again assigned to KMAT
material in order to trigger configuration in configuration profile.
4.1.2 Super BOM with Class Item
Class items used to control the selection of variant parts in a BOM. Variant parts are classified in
a class, and the class is entered in the BOM as a class item. When you configure the material, the
class is replaced by a suitable variant part.
4.1.3 Advantages of using Class Item in BOM
· Only one item for the class is enough, instead of several items for the individual variant parts.
· No need to create and assign selection conditions.
· Able to classify additional objects in the class at any time, without having to change the BOM.
4.1.4 Steps involved in super BOM with Class
? Define all Characteristics and its Values assign it to Class with type 200.
? Assign characteristic Values to materials by Classification material
? Assign class 200 with material instead of assigning all BOM items.
? Create and Assign class 300 (with same characteristics) with configurable product using
configuration profile.
4.1.5 Super BOM with Material Components
This bill of material (BOM) of a configurable material contains all the components that are
required to manufacture the material. The BOM contains components that are only used in
specific variants (variant parts), as well as components that are used in all variants (non-variable
parts).
4.1.6 Steps involved in super BOM with Material Components
? Define all Characteristics and its values assign it to Class with type 300.
? Assign Class with configurable material in Configuration profile.
? BOM is created with all variant and non-variant items.
? Define interdependency between objects (Characteristic, BOM item, Routing Operation etc?)
by using Object Dependencies.
? Assign class 300 with configurable product using configuration profile.
4.2 Super Routing
A configurable routing describes the production process for all variants of a product. Instead of
creating a routing for each variant of a product, you can create operations for one routing, or a
"super" routing.
It is possible to maintain Object dependencies for following in super routing:
· Sequences
· Operations/sub-operations
3. · Production resource/tool assignments
The routing is configured by system, when order is created for KMAT material.
4.3 Characteristic
Characteristic is used to define the features of a configurable material. To enable to use
characteristics to configure a material, assign the material to a class of class type 300. The
customer can choose from among different options for each characteristic.
· Characteristics describe the properties of objects. The values of a characteristic specify these
properties.
· Value assignment to characteristic may be single value or multiple value with required entry or
restrict able entry.
· In characteristic it is also possible to use table name and its field name in order to change the
Object quantity or values. I.e. BOM item quantity or Operation time, which is known as ?
reference characteristic?.
· In Restriction screen allowed Class types are entered i.e. for what are the class this
characteristic may used. In general for Variant configuration class 200 and 300 are used.
· It is also possible to assign Dependency to characteristic values maintained in Characteristic.
4.4 Variant Class
· In Variant configuration, Class is used to hold the characteristics that describe about
configurable material. Class type to determine which object types can be classified.
· Class is used in variant configuration if the class has a class type that supports variant
configuration. In Customizing for Classification, the Variant class type indicator must be set for
the class type. In the standard system, this is class type 300.
4.5 Dependencies
· Dependencies restricts the combinations of options i.e. characteristic that are not allowed. It
also select exactly the right BOM components and operations to produce a variant.
· It also describe the interdependencies between characteristics and characteristic values
· It control which components are selected from a bill of material (BOM) and which operations
are selected from a task list
· It also changes the values of fields in BOM items and operations during configuration.
4.5.1 Global and Local Dependencies
Global dependencies have the following properties:
· They are independent of any object.
· They are identified by a name that you assign, and are maintained and managed centrally.
· If you change a global dependency, the change affects all the objects where the dependency is
used
Local dependencies have the following properties:
· They are only available to the object for which you create them
· You cannot use the central maintenance functions on these dependencies, and you cannot
allocate them to other objects
· They are identified by a number assigned by the system, not an external name
Local dependencies are only used where certain dependency will not be needed elsewhere
4. The differences between global and local dependencies are as follows:
· Global dependencies are created centrally and can be assigned to several objects.
· Local dependencies are created for one object and can only be used with this object
4.5.2 Declarative and Procedural Dependency
· In Declarative dependencies the result are explained logically
· Declarative dependencies are easier to trace than procedural dependencies, because the point in
time when the dependency is processed and the sequence in which the dependencies are
processed are not relevant.
· Example for Declarative dependency:
Constraint
Actions
Preconditions (provided that they contain no non-declarative expressions)
Selection conditions (provided that they contain no non-declarative expressions)
· In Procedural Dependency result depends on the processing sequence and the point in time
when the dependency is processed.
Procedures
Preconditions (only if they contain non-declarative expressions)
Selection conditions (only if they contain non-declarative expressions)
4.5.3 Dependencies Types
The SAP System supports the following types of dependencies:
· Preconditions
· Selection conditions
· Procedures
· Actions (obsolete)
· Constraints
4.5.4 Preconditions
Preconditions can be allocated to the following objects:
· A characteristic that you want to hide
· A characteristic value that you want to hide
Preconditions are used to hide characteristics and characteristic values that are not allowed and
thereby ensure that the configuration of an object is consistent. In the precondition, it is also
possible define the circumstances under which a characteristic or value is hidden.
A precondition is fulfilled if the condition you enter is either true or not violated.
4.5.5 Selection Conditions
Selection conditions used to ensure that all the objects relevant to a variant are selected:
· Selection conditions determine which variants require a specific component or operation
· Selection conditions determine when it is mandatory to assign a value to a characteristic
Selection conditions may allocate to the following objects:
· Characteristics
· BOM items
5. · Operations in task lists
· Sub-operations
· Sequences of operations
· Production resources/tools (PRTs)
A selection condition is fulfilled if the condition in it is unambiguously true.
4.5.6 Procedure
Procedures can be assigned to the following objects:
· The characteristic value that triggers the procedure
· The characteristic that triggers the procedure
· The configuration profile of the configurable object
Procedure is used for following purposes.
· A procedure is used to infer a value for a characteristic, you enter the variable $SELF before the
characteristic.
· Procedures can overwrite values that are set by other procedures.
· Procedures are always used for pricing (see Variant Conditions).
Processing Sequences of Procedure
If an object has more than one procedure, a processing sequence is used to define the point when
the procedure is processed.
4.5.7 Action
Actions are used to infer characteristic values. An action is processed as soon as the
characteristic to which it is assigned has a value. It is not possible to overwrite the characteristic
values that are set by an action.
The following Objects can assign to action:
· The characteristic value that triggers the action
· The characteristic that triggers the action
· The configuration profile of the configurable object
· Configuration profile
· BOM items ? to change the quantity
· Operations in task lists ? to change the standard values
Since Action is lead to serious system performance problems, it is replaced by Procedure and
Constraint.
4.5.8 Constraint
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 a constraint is to monitor the consistency
of a configuration.
Constraints have the following distinguishing features:
· Constraints are used to describe the dependencies between completely different objects and
their characteristics.
· Constraints are used to store information on which conditions must be fulfilled if the
configuration is to be consistent.
· Constraints are not directly allocated to individual objects. They are grouped together to form
dependency nets and allocated to a configurable material in the configuration profile.
6. · 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 allocated.
· Constraints are declarative dependencies. The processing sequence of constraints and the point
in time when constraints are processed is 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. If a value that is relevant to the
constraint is changed, the constraint is triggered again.
4.5.8.1 Structure of Constraints
There are four sections in a constraint. Each part is identified by a keyword. A colon follows the
keyword. Each section ends with a period.
OBJECTS:
In this section, you enter the objects that are relevant to the constraint. You must enter the
relevant objects in all constraints. You can also define variables for objects or characteristics.
CONDITION:
The condition entered here must be fulfilled in order for the constraint to be used. You do not
need to enter a condition in a constraint. You can leave out the keyword CONDITION: if
required. However, if you enter the keyword you must enter a condition.
RESTRICTIONS:
In this section, you enter the relation that must exist between the objects and characteristics if the
configuration is to be consistent. You must enter a restriction in a constraint.
INFERENCES:
In this section, you enter the characteristics for which characteristic values are to be inferred. The
main purpose of constraints is to check the consistency of a configuration. Usually, values are
only inferred if you make an entry in this section.
For reasons of performance, only use constraints to infer values if it is really necessary.
Constraints are grouped together to form dependency nets. The dependency net is allocated to a
configurable material in the configuration profile.
4.5.9 Dependency Net:
Constraints are grouped together in dependency nets. For this reason, the variant configuration
menu does not support a function for creating constraints directly. So that only constraints are
defined within a dependency net.
5 Configuration Profile
The configuration profile for a material controls the configuration process in sales order.
Configurable profile also used to define central settings for configuring the object. Using this
profile it is possible to hide some of the characteristic value defined during characteristic
creation. We can assign any number profile for a configurable material in which selection is
based on either priority or manual selection during configuration.
By defining a filter in the configuration profile, possible to determine the scope of the BOM
items to improve system performance when exploding the BOM. The filter is active in high-level
configuration, in result-oriented BOMs, and in SET processing.
5.1 Filters in Configurable Profile
7. Following objects can be used as filter:
· Object type
Class, material, document, text
In the standard system, all object types are selected and therefore exploded in the configuration.
Deselect the object types that you do not want to be displayed.
· Item category, for example, stock or non-stock item
All item categories in the configuration are exploded in the standard system. Remove the
selection for the item categories you do not want to be displayed.
· Item status
You maintain the status of a BOM item in maintain BOM dependent on its usage.
All items are displayed regardless of their item status in the standard system. However, only the
items with this status are displayed when you select specific item statuses. Items are not
displayed that do not have the selected status.
· Sort string
You can assign sort strings for BOM items in maintain BOM. You can restrict the display of the
BOM items by using these sort strings.
Only items that carry sort strings are checked and only those that match are displayed. Items that
have no sort string are always displayed.
5.2 Component availability in the configuration profile
The availability check is just a snapshot, telling that whether the materials required are in stock
at this moment. Several users can access the same material at once. This means that supply
problems can sometimes be overlooked.
Example: Only 2 pieces of a material are in stock, but the material is used in 3 BOMs. The
availability check does not detect a supply problem. The availability check for all 3 BOMs shows
2 pieces in stock.
5.3 Process Overview
There are different processes for configurable materials in sales documents. These processes can
be defined on the Configuration initial screen tab in the configuration profile, by choosing the
Configuration parameter tab.
The Process are described in the following scenarios:
Planned/Production orders
This processing type is used to describe variant products whose configurable materials are
assembled using planned and production orders. The bill of material (BOM) can have single-
level, multi-level, or no explosion.
Sales Order (SET)
This processing type is used to describe variant products that comprise salable configurable
materials. These products are supplied together, but are not assembled in a production order.
Only sales-relevant BOM items are exploded in the sales order.
Order BOM.
You use this processing type 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 header material, but the BOM is not exploded in the sales order.
8. 6 Material Variant and Planning Material
6.1 Material Variant
· Material Variant is an material that can arises from individual Configuration of a configurable
product and can be kept in stock
· For variants that are required frequently, we can create material variants, which can be
produced without a sales order and kept in stock. When a sales order is received, it is possible to
check whether the variant required is in stock, so that it can deliver immediately.
· For material variants, a separate material master record is created with a material type that is
kept in stock.
· Separate BOM and routing for a material variant, or you can link the material variant to the
BOM and routing of the configurable material. The correct BOM items and operations are
determined from the characteristic values assigned to the variant.
6.2 Planning Material
· Planning Material is a material, which contains all the non-variant parts.
· By using planning material all non-variants are procured / produced before sales order.
· It is also possible for Planing the Planning Materials without reference to any sales requirement.
· Planning material is planned separately using strategy 65 and produced before sales order
creation.
7 Planing in VC
The following strategies are used for planning configurable materials and its variant parts.
Make to Order production of Variants
? Make to Order for Material Variant. – 26
? Planning Variants without final Assembly- 55
? Planning Variants with planning Material – 65
? Make to order with configurable material.- 25
? Characteristic Planning with dependent requirement – 56 and
? Assembly Processing with Characteristic Planning – 89
8 Variant Configuration: (Object Diagram)
9. 9 Variant Pricing and Surcharges
9.1 Sales BOM
A bill of material (BOM) describes the different components that together create a product. A
BOM for a bicycle, for example, consists of all the parts that make up the bicycle: the frame, the
saddle, wheels, and so on.
When you enter the material number of a bill of materials that is relevant for sales order
processing, the system displays the material that describes the whole bill of materials as a main
item. The individual components are displayed as lower-level items.
There are two ways to process a bill of materials in Sales. Once you have entered a bill of
material in a sales order, the system runs pricing, inventory control, and delivery processing at:
Main item level if the material is assembled, or – Component level if the material is not
assembled.
9.2 Processing at Main Item Level (ERLA)
If you want the system to carry out pricing, inventory control, and delivery processing at main
item level, enter ERLA in the Item category group field of the Sales: sales org. 2 screen in the
material master record of the finished product. This means that the components only function as
text items and are not relevant for delivery.
9.3 Processing at Component Level (LUMF)
If you want the system to carry out pricing, inventory control, and delivery processing at the
component level, enter LUMF in the Item category group field of the Sales: sales org. 2 screen in
the material master record of the finished product. In this case, only the components are relevant
for delivery. During processing the system automatically creates a delivery group. The latest
delivery date among all the components becomes the delivery date for the entire delivery group.
10 Configuration of VC
10.1 Production Planning and Control
10.1.1 Creating Material
Use
The purpose of this activity is to create the material masters for the materials required in this
scenario.
Procedure
Access the activity using one of the following navigation options:
SAP Menu Logistics ® Materials Management ® Material Master ® Material ® Create
(General) ® Immediately
Transaction Code MM01
In Material Master of KMAT material following settings are maintained:
· Configurable material indicator in Basic Data must set.
· MRP type is PD.
· Lot size ? EX ( Lot for lot size)
· Availability check ? 02
10. · Planning Strategy 25 is entered in MRP 3 screen view.
· Item category group 0002 or 0004 is to be given in sales view.
10.1.2 Creating Bill of Material
Purpose:
· The purpose of this activity is to create bills of material (BOMs) for the configurable material
which is known as ?super BOM?
· Super BOM comprise all the variant as well as non-variant parts required for producing
configurable material.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics ® Production ® Master Data ® Bills of Material ® Bill of Material ®
Material BOM ® Create
Transaction Code CS01
· The Create Material BOM: initial screen appears. On this screen, data that identifies the bill of
material are maintained as well effectivity data.
· In the Material field, the configurable material for which super BOM need to create is entered.
· Plant and BOM usage is entered. In general BOM usage 1 for production and 3 is for Universal.
· In Component screen list of variant and non-variant parts are entered along with that quantity is
entered based on Base qty. of the configurable material.
· It is also possible to enter a class as a BOM component with item category ?class Item?. This
class must hold all characteristics and also classified with each material.
· Class type 200 and 300 can be used as a class item.
Following Procedure is followed for assigning class with BOM as a class Item.
· Enter the item category for class items in BOM.
· Make entries in the fields that identify the class
? Class types
? Class
· Enter the quantity.
Enter a unit of measure if appropriate.
The system determines the unit of measure from the additional data of the class.
If a unit of measure without a dimension is maintained in the additional data of the class, you
cannot change this unit.
10.1.3 Creating Characteristic
Purpose:
· Characteristic is created with possible values.
· It is also possible to use table name and its field name in order to change the Object quantity or
values. Ie BOM item quantity or Operation time. This is known as ?Reference characteristic?.
· For changing BOM quantity Characteristic is created with table name STOP-MENGE is used.
· For Variant pricing purpose SDCOM-VKOND is used.
11. · Characteristics allow describing and distinguishing between objects, such as length, color, or
weight within the classification system.
Procedure
SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
Transaction Code CT04
· From the classification menu, choose Characteristics.
· Enter data on the initial screen.
· In the Characteristic field, enter a name for new characteristic
· Enter a change number if you want to create the characteristic using engineering change
management.
· To do this, choose processing type Create characteristic.
· You can also copy the data of an existing characteristic. Use the pushbutton Create by copying.
Enter the name of a characteristic you want to copy.
· Confirm the entries.
· On the Basic data tab page enter the most important control data for the characteristic.
· You must maintain the basic data for all characteristics. All other screens are optional.
· In the formatting data for value assignment, whether a characteristic is single-value, multiple-
value, or retractable is defined. It is not possible change the value assignment indicator once it
has set. It applies wherever the characteristic is used.
· The data type of the characteristic determines which values can be entered for the characteristic.
I can any one of the following
Characters
Numeric
Time format/Date format
Currency format and
User defined data type.
· For numeric characteristic it need to maintain that whether interval values to a numeric
characteristic, or only individual values need to be maintain in Basic Data screen itself.
· Languages in which characteristic want to describe are entered.
· Choose the tab page Values.
· Enter values in the entry fields. Enter each value in a separate field.
· The values must match the format that you defined on the Basic Data screen. You can enter up
to the number of characters that you defined in the format.
· If your characteristic is an alphanumeric characteristic, enter a language-dependent value
description. You can enter up to 30 characters.
· It is not possible to enter a language-dependent description for numeric values
· It is also possible to define one value as a default value. This value then appears as a default in
characteristic value assignment functions
· Additional value indicator determines that whether values that are not defined as allowed values
can be assigned to a characteristic
· The following value check strategies are available in value maintenance screen.
12. Allowed Values:
Check Tables
Function module
Catalog character
· Allowed values permits only values defined in characteristics maintenance are used to check a
characteristic value
· Check table permits only values entered in characteristics maintenance is used to check a value
· Function module entered is used to check characteristic values.
· Value catalog entered is used to check characteristic values
· Documents, such as drawings or photographs, with characteristics can be linked in additional
data screen. Before link a document to a characteristic, it must create a document info record in
the document management system.
· In this screen it also possible to restrict or hidden or displaying only allowed values to
characteristic.
· It is possible to that characteristic can be only assigned to particular class type by assigning type
in restriction screen.
· To change a characteristic selects the pushbutton Change in characteristics after entering the
characteristic. To display the characteristic chooses the pushbutton Display.
10.1.4 Creating Class:
Purpose:
· A class is used to hold the characteristics that describe a configurable material. By linking the
class to the configurable material, you allow the material to be configured using the
characteristics of the class.
Procedure
SAP Menu Logistic->Central function->Environment->classification->Class
Transaction Code CL01
· Class holds all characteristics describe configurable material.
· Class with class type 300 is used in configuration profile.
· On basic Data screen class description, its status is entered. Status determines:
· whether a class can be maintained
· whether objects can be allocated to a class
· whether the class can be used for selecting objects
· Class group is used to group together related classes and also for finding classes quickly via a
matchcode.
· ?Same Classification ?indicator determines whether system check for identical characteristic
values. In this case, where several objects are assigned that have the same values for all
characteristics to the same class. Depends upon indicator system give warning or error message
or no message.
· Keyword string is used for finding a class via matchcode.The description entered on the basic
data screen serves as the first keyword
· On characteristic screen list characteristic which has to attach with configurable material is
entered.
13. · Using document tab screen it is possible to assign documents related to configurable object.
· On additional data screen whether or not this class can be used as a class component in bills of
material. If it is yes then Unit of measure in which stocks of the material are managed. The
system converts all the quantities you enter in other units of measure (alternative units of
measure) to the base unit of measure and resulting item category which will replace this class
item in BOM (i.e. Stock, Non-stock item etc?).
10.1.5 Creating Dependency
Purpose
Dependency describes the interdependencies between characteristics and characteristic values
and it controls which components to be selected from a bill of material (BOM) and which
operations to be selected from a task list. It also changes the field values in BOM items and
operations during configuration.
Procedure
SAP Menu Logistic->Central function->Variant Configuration->dependency->Single
Dependency->Create Dependency
Transaction Code CU01
· From the variant configuration menu, choose Dependency -> Single dependency-> Create
· In initial screen name of the dependency is entered. If dependency need to create for a specific
date, enter a change number. It is also possible to create dependency by copying from existing
dependency.
· On basic data screen the following data are required to enter
A language-dependent description for the dependency
Also possible to enter descriptions in different languages by choosing Descriptions.
Long texts for the dependency, choose Extras -> Documentation.
In the standard R/3 System, the status ?In preparation? when a dependency is created first time.
The status is set to ?Released? when the source code is syntactically correct.
Finally suitable dependency type is selected.
· In Dependency editor the source code for the dependency is entered. Once the source code is
syntactically correct, the source code is saved.
· Now the status of the dependency is turns to ?Released?. Save the Dependency and exit.
10.1.6 Changing Bill of Material (Assign Dependencies)
Purpose:
By assigning dependencies to BOM components, it is possible to restrict the selection of
irrelevant variant parts.i.e correct BOM components are get selected at result of configuration. It
is also possible to change the component quantity depends upon characteristic value changed.
Procedure
1. Access the activity using one of the following navigation options:
14. SAP Menu Logistics ® Production ® Master Data ® Bills of Material ® Bill of Material ®
Material BOM ® Change
Transaction Code CS02
· Dependencies are assigned with respect to characteristic for each variant part.
· Dependencies are created either locally within object or globally which can be assigned to any
objects.
· In BOM General Item overview screen choose the component in which dependency need to
assign and choose menu path Extras -> Dependency -> assignment of dependency for
assignment.
· It also possible to enter dependency directly in BOM itself by choosing Extras -> Dependency
-> dependency editor.
10.1.7 Creating Configuration Profile
Purpose
· Configuration profile used for assigning configurable material with variant class (300) and also
used to maintain some central settings.
· It is possible to assign more than one configurable profile for one KMAT material.
· The selection of profile depends upon either by priority or by manual selection.
· It is also possible to assign dependencies to configurable profile.
· Class with type 300, which hold the entire characteristics of KMAT material, are assigned to
each profile
Procedure:
Access the activity using one of the following navigation options:
SAP Menu Logistics ® Production ® Master Data ® Material Master ® Environment ®
Configuration Profile ® Create
Transaction Code CU41
· From the Variant Configuration menu, choose Configuration profile->Create.
· A dialog box will be displayed. The object name is entered. Confirm your entries.
· On profile overview screen the following data need to be entered.
· Profile name and the class type of classes used for configuration. In Customizing for the
Classification System, the class type must be defined as a variant class type.
· Choose Goto -> Class assignments or the ?Class assignment ? pushbutton to assign the object to
a class.
· In the classification screen, names of the classes are entered.
· It is possible to restrict allowed characteristic values for the configurable object if required.
· Release of profile is possible only if configurable object is assigned to a class. To go to the
detail screen, where you define further settings, choose the Profile detail pushbutton or double-
click on the profile.
10.1.7.1 Optional Settings on the Profile Overview
· Organizational Areas
You can specify organizational areas for configuration. If you restrict a profile to specific
organizational areas, you only see the characteristics that are relevant to your area when you
15. configure the object.
You can change how characteristics are displayed according to organizational area for your user
on the value assignment screen.
· Priority of Configuration Profiles
You can create several configuration profiles for a configurable material. The profile with the
lowest number has the highest priority.
If you define several profiles for an object, you see a dialog box for selecting a profile when you
start configuration. The profile with the highest priority is at the top of the list.
The priority is also relevant if you use Application Link Enabling (ALE) or intermediate
documents (IDocs) to run configuration, rather than dialog mode. In this case, the profile with
the highest priority is selected for the object. Profiles that have no priority are at the top of the
list, because they automatically have priority 0.
10.1.7.2 Profile Detail
· Configuration Profiles for Materials
The configuration profile has several screens. Depending on what you enter for the BOM
explosion and configuration process, fields are shown or hidden.
The parameters you maintain for a material apply to the material as a header material in a BOM
structure. You cannot define separate settings for use of a configurable material as an assembly
in a BOM.
By choosing the Assignments pushbutton, you can assign dependencies to the configuration
profile. You also see this pushbutton on the basic data tab, once at least one dependency is
assigned.
· Basic Data Tab
In the basic data, click on the profile overview data.
If configuration process need to starts with a Start logo, documents are assigned such, as a
graphic showing the product you want to configure, to the variant class.
Configuration Initial Screen Tab
· Configuration parameters
The parameters for BOM explosion and the configuration process in the sales order are specified
here.
BOM application must be entered, if BOM explosion ?None? is selected rather than single and
multi level explosion is selected.
By entering a level of detail for a multi-level configuration, system performance will be
improved.
It is also possible to define a filter and set the indicator for an availability check on assemblies.
10.1.8 Changing Configuration Profile: Add User Interface Settings
Purpose
Settings for the configuration editor in user interface.
16. An interface design is used to group characteristics together on the value assignment screen.
Here it also possible to define object-specific settings for functions in the configuration editor.
These settings are defaults for configuration, and can be overwritten for your user in the
configuration editor.
For all configuration parameters except BOM explosion ?None?, manually select the screens for
the configuration editor and define which screen configuration starts with. The start screen must
be one of the allowed screens.
The indicator for the configuration browser independently of the other start screens can be
selected, because the browser is an additional screen section.
Configuration Profiles for Objects Other than Materials
Object-specific settings for displaying characteristics and characteristic values in the
configuration editor can be defined. These settings are defaults for configuration, and can be
overwritten for your user in the configuration editor.
Procedure
Access the activity using one of the following navigation options:
SAP Menu Logistics ® Production ® Master Data ® Material Master ® Environment ®
Configuration Profile ® Change
Transaction Code CU42
10.1.9 Configuration Simulation
Purpose:
· Configuration simulation is used to check the configuration model. In the configuration
simulation, the whether or not Object structure is created correctly and dependencies are working
fine is checked.
· Simulation of Sales/Engineering
The configuration parameters in the configuration profile apply. Whether the configuration is
simulated from the sales point of view or the engineering point of view is defined.
If select Sales & distribution is selected the configuration in a sales document will be simulated
(sales order or quotation), so the BOM explosion depends on the settings in the configuration
profile.
If Engineering is selected, the configuration in order BOM processing will be simulated. The
configuration and BOM explosion depend on the configuration parameters in the same way as
when maintaining an order BOM. For example, we cannot configure the header material,
because the configuration is copied from the sales order.
· Simulation of a Planned Order
On the characteristic value assignment screen, we can choose Planned order to display the
components that are determined in material requirements planning (MRP) according to the
characteristic values assigned. This is especially relevant to assemblies whose BOMs are
17. exploded in MRP, not in Sales & distribution (for example, assemblies with the BOM explosion
setting None in their configuration profile).
Procedure:
SAP R/3 menu Logistics ® Production ® Master Data ® Bills of Material ® Environment ®
Variant Configuration ® Environment ® Configuration Simulation
Transaction Code CU50
· On the initial screen of the configuration simulation, select BOM to display the entire structure
on the result screen.
· If you have created more than one configuration profile for a material, you see a dialog box.
Select a profile and choose Continue. If you want to call detailed information on the profile,
choose Profile Detail or double-click on the profile.
· To display the task list of an assembly on the result screen, select the assembly and choose
View ® Objects ® Task list.
· You see the operations or activities in the task list that was selected for the assembly during
configuration.
· Operations that have been changed by dependencies have an information icon next to them.
You can display changes by choosing Information.
· To return to the BOM explosion, choose View ® Objects ® BOM
10.2 Sales and Distribution
10.2.1 Creating Condition Records – VA00
Purpose:
The purpose of this activity is to create condition records for VA00.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics ® Sales and Distribution ® Master Data ® Conditions ® Select Using
Condition Type ® Create
Transaction Code VK11
· Create price for each value of the characteristics by select using condition type VA00.
· Create the Price for the condition type that represents these types of the standard-delivered
condition type for this functionality is ?VA00.?
· Condition type VA00 requires as key fields the sales Organization, distribution channel, and
material number of the configurable.
· Condition type PR00 used to maintain base price of the configurable material.
· Using VA01it is also possible to maintain Surcharges and discounts.
10.2.2 Condition records for Variant Price and Surcharges
Purpose
Condition records allow you to store and retrieve pricing data in the system. All the pricing
elements of your daily business – the prices, discounts, and surcharges for freight and taxes –
that you want to use for automatic pricing must be stored in the system as condition records. You
18. can define as many condition records as you want for the different pricing elements for any
validity period.
You create condition records for all the pricing elements that the system takes into account
during automatic pricing. During document processing, the system transfers data from the
condition records and determines the amounts for individual pricing elements (prices, discounts
and surcharges) and the final amount for the sales document
Procedure
10.2.2.1 Create a characteristic for the Pricing
Create Pricing characteristic like CAR_Pricing and go to additional data tab give SDCOM table
name VKOND field name.
SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
Transaction Code CT04
10.2.2.2 Assign the characteristic to the class
Assign given characteristics to class, In variant configuration, a class is used to hold the
characteristics that describe a configurable material. By linking the class to the configurable
material, it allows the material to be configured using the characteristics of the class. In the
standard R/3 System, the class type for configurable material is 300.
SAP Menu Logistic->Central function->Environment->classification->Class
Transaction Code CL01
10.2.2.3 Create a dependency that triggers the price
A Dependency is a rule that defines how the different options and option values, represented by
characteristics and characteristic values, relate to one another. To create a dependency, follow
the menu path
SAP Menu Logistic->Central_function->VariantConfiguration->dependency->Single
Dependency->Create Dependency
Transaction Code CU01
10.2.2.4 Assign the dependency to the characteristic value that triggers the price
For example eCar2002, the value ?V8? refers to the engine selected by the customer. Therefore,
the dependency must be linked to the value ?V8? of the characteristic that represents the engine
type. To do this, go to the master data record of the characteristic CAR_ENGINE
SAP Menu Logistic->Centralfunction->Environment->classification->Chracteristics
Transaction Code CT04
Go to the ?Values? tab. From there, select the?V8? entry and use the menu path Extras Object
dependencies Assignments, which brings you to the screenshot to the right; if you have created a
global dependency, you can link it to the characteristic value.2 Once the dependency has been
19. assigned, the information on this screen, such as the description (?Engine price?), will default to
the information entered when you created the characteristic.
10.2.2.5 Create variant price
Create price for each value of the characteristics using condition type (or transaction VK11).
Create the Price for the condition type that represents these types of the standard-delivered
condition type for this functionality is ?VA00.? Condition type VA00 requires as key fields the
sales Organization, distribution channel, and material number of the configurable.
In the same way using condition type VA01 is also used to maintain prices for surcharges and
discounts.
10.2.2.6 Creating the output condition records for sales
Output types are used to represent various forms of output in the SAP system. Examples of
output types in Sales and Distribution processing are order confirmations, freight lists, and
invoices. You use the output type to control how the output should be transmitted, for example
whether an order confirmation should be sent via EDI, or be printed
10.2.3 Creating Output Condition Records: Sales
Purpose:
Output types are used to represent various forms of output in the SAP system. Examples of
output types in Sales and Distribution processing are order confirmations, freight lists, and
invoices. You use the output type to control how the output should be transmitted, for example
whether an order confirmation should be sent via EDI, or be printed
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics ® Sales and Distribution ® Master Data ® Output ® Sales Document ®
Create
Transaction Code VV11
· Choose Edit >Key combination
· Select the key combination for which condition records are to be created.
· Choose Enter.
· Enter the appropriate key for each condition record, according to the key combination you
selected.
· For transmission medium 1 (Print output) or 7, you can maintain the communication data. To
do this, choose Communication.
· Save the condition records.
10.2.3.1 Creating Output Condition Records: Billing
Purpose
The purpose of this activity is to create output condition records for billing. Output types are
20. used to represent various forms of output in the SAP system. Examples of output types in Sales
and Distribution processing are order confirmations, freight lists, and invoices. You use the
output type to control how the output should be transmitted, for example whether an order
confirmation should be sent via EDI, or be printed
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu Logistics ® Sales and Distribution ® Master Data ® Output ® Billing Document ®
Create
Transaction Code VV31
Enter an output type.
· Choose Edit >Key combination
· Select the key combination for which condition records are to be created.
· Choose Enter.
· Enter the appropriate key for each condition record, according to the key combination you
selected.
· For transmission medium 1 (Print output) or 7, you can maintain the communication data. To
do this, choose Communication.
· Save the condition records.
10.2.4 Order BOM
Purpose:
Products that are made to order in plant engineering and construction and mechanical
engineering are generally very complex and are specific to one customer. For this reason, you
cannot define a BOM entirely in advance. Once you have created your sales order, you need to
make manual changes to the BOM by creating an order BOM especially for the sales order,
without changing the original BOM.
The sales order, sales order item, and material number identify an order BOM. In variant
configuration, you can work with 2 types of order BOM. The difference is in the way they are
saved.
Knowledge based order BOM
The order BOM is saved as a copy of the super BOM with manual changes and dependencies.
Result Oriented BOM
The configuration result is saved as an order BOM, with manual changes but without
dependencies.
Procedure (For knowledge based BOM)
SAP Menu Logistics ® Production Planning ® Master Data ® Bills of Material -> Order BOM
Maintain (Multi-Level)
Transaction Code CU51
21. · The Create Order BOM: initial screen appears.
· Enter the sales order number, the order item, the material number and the BOM usage
· If you want to use material BOM, or an existing order BOM to copy from, go to step 4. If you
want to create an order BOM without a reference, click and go to step 7
· You cannot use a configurable BOM as a reference
· Click on copy order BOM or Click on copy material BOM
· The Copy material BOM or Copy order BOM dialog box appears
· Enter the data required and click. The item overview appears, for the bill of material you are
using as a reference.
· Enter new items and alter items if necessary. Entering items in order BOMs is similar to
entering items in material BOMs. However, you cannot enter class items in order BOMs.