Professional Documents
Culture Documents
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.
1. Super BOM
2. Super Routing
3. Characteristic
4. Class
5. Object Dependencies
6. Configuration Profile
7. SD Condition records
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.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.
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.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.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.
· 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.
· 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.
7 Planing in VC
The following strategies are used for planning configurable materials and its variant
parts.
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.
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
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.
Procedure
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.
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.
Procedure
SAP Menu Logistic->Central function->Environment->classification->Class
Transaction Code CL01
Procedure
· 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.
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 ® 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.
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
· 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.
Procedure
Access the activity using one of the following navigation options:
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
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 exploded in MRP, not in Sales & distribution (for example, assemblies with
the BOM explosion setting None in their configuration profile).
Procedure:
· 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.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
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 assigned, the information on this screen, such as the description (?
Engine price?), will default to the information entered when you created the
characteristic.
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
Purpose
The purpose of this activity is to create output condition records for billing. 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 ® Billing
Document ® Create
Transaction Code VV31
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.
SAP Menu Logistics ® Production Planning ® Master Data ® Bills of Material -> Order
BOM Maintain (Multi-Level)
Transaction Code CU51