
While describing the definition of characteristic, I picked one characteristic as example to show all the sets of attributes involved in definition. In this demo lesson you will be taken through basic data and description related attributes of characteristics.
In this demo lesson attributes of characteristics under the sets additional data and restrictions, are explained.
After showcasing all important attributes of typical characteristic, using an example of RAM characteristic, you will walk through creation of all other characteristics relevant to business case.
Before creating a class to group the characteristics created, you are given a briefing on what is class and it's multiple types and capabilities.
You need create SuperBOM for the configurable Material. This special BOM includes all possible components along with standard components. In this lesson you will walk through creation of (Super)BOM for Configurable Material.
In this lesson, I will brief you on what is configuration profile and how the settings in the configuration profile can govern the behaviour of configurator (Value assignment screen).
After getting brief idea on purpose of configuration profile, you will be walking through SAP screens of Configuration profile for more understandig.
In this section, I will show you navigation to create configuration profile followed by a walk through of important attributes in Basic data tab of Configuration Profile page.
After going through the basic data tab, you will be able to see User Interface settings page. Here you can go through key settings to control the interface appearance in Value assignment screen (Configurator)
In this lesson, you will go through key UserInterf Parameters before you go to the main page of UI Settings for 8 sets of attributes.
In this lesson you will walk through important attributes of UI settings in the tabs Language and Display tabs.
You will go through key parameters to determine the scope of Configurator.
In the UI settings of Configuration Profile, you will go through Pricing and Default attributes. You can determine whether pricing is always performed for the selections or is exclusively requested. In the "default" you will make settings for determining how defaults are identified.
In the last and final set of UI Parameters, we will go through key attributes related to Variant Matching. You will understand that depending on the selection of attributes under this tab, you will determine whether variant matching happens without request and or with request and to whether the matching is fully or partially made.
Selection conditions are used to determine the selection of objects like BOM Components and Task List Operations. In this lesson a briefing is providing on what is object dependency of type selection condition. In addition, for what purpose these type of dependencies are written and what are the objects to which this type of dependency can be assigned etc are explained.
You will walk through all aspects of defining an Object Dependency. You will understand the navigation and key settings (Like Status of dependency , type of dependency etc) and parameters of Object dependency.
You will write selection conditions to determine the selection of components corresponding to features RAM and HDD.
Dependencies and restrictions for OS Components are a bit different. For enabling and disabling OS, the selection conditions are defined in this Demo lesson.
Selection conditions for Routing operations are made simple. As you might have noticed, the operations for most of the components like those for RAM, HDD and Screen size are same for any characteristic value. For OS there are 1-1 related conditions. You will go through definition of selection conditions for determining the selection of all these operations
In this demo lesson, you will get a feel of how your selection conditions work in Run time. The validation of these conditions is done through configuration simulation.
In Make to Order Manufacturing environment, the company makes the products after receiving the order. Make to order can be executed in two scenarios.
1. A design of product is in place but product is made only after receiving the order. This is because product is quite experience to make and stock before sales. example: Locomotives. Steam Turbines, Portable offices etc.
2. High level design of base product is in place but product may accommodate minor variations according to Customer choice. In such case the customer is presented with a few features and options for each feature to select. Accordingly the customer specific product is made and delivered.
With a product having large number of minor variations, you will find it difficult to plan and monitor each finished product with minor changes. Instead you can plan at sub-assembly and component levels. Finished products are determined only after customer chooses the features.
SAP has variant configuration as one cross- functional module which eases out the design, planning, costing, pricing and sales / purchase of such Products.
This course will go through the concepts as well as demos on how SAP enables Make to Order Manufacturing and sales.
In addition, you will get off-line reading material for your reference. You will also go through quiz items to check your knowledge