hi all experts pls giv me reply re: variant configuration

[Former Member]

hi all

i am a fresher in the sap sd ,Right now i am learning this module,In that i hav learn Variant Configuration . in that i hav a confusion that is

What z the exact functionality of

*precondition

*seletion condition

*action

*procedure etc,.

and

" i take a exemple that is for car manufacturing company produce three different cars with eng capcity x,y,and z.

and they produce in three different colours,in to three accesseries (varient pricing),

and i want to configure for x only one colour and w/o accessriers, y have first two colours and all accessries and similarly z also hav that functionality of y but it only any of two colours.."

pls suggest me how to write the code for that ,, mailnly the functionality of the procedure ,action,and etc..

Thank & Regards

T.N.Rao

91-9866673319

[Former Member]

hi

also refer to the links below.. along with the other member answers..

Special Settings for Variant Config

http://help.sap.com/erp2005_ehp_02/helpdata/en/41/191f2d45fd11d188ff0000e8322f96/frameset.htm

Special Features for Variant Config

http://help.sap.com/erp2005_ehp_02/helpdata/en/6c/a4e0b7003311d294cb00a0c92f024a/frameset.htm

Configuration

http://help.sap.com/erp2005_ehp_02/helpdata/en/10/8d984ef3d611d1aba70000e829fbfe/frameset.htm

Reward if USeful

Thanx & regards.

Naren..

[Manoj_Mahajan78]

Hi..

The procedure is as follows:

Create a Material - KMAT type with Item category (002)

Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc

Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)

Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.

Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.

Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save

Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)

Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save

Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)

Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.

Variant configuration is used where you have a configurable material like computer (made up of components like processor, monitor, keyboard, mouse etc). These components are called as characteristics in variant config. Again this will be having values like processor can be either P4 or P3, monitor can be 15" or 17" etc.

PLEASE REWARD POINTS IF U FINDS THIS AS USEFUL...

Regds

MM

[Former Member]

Dear narasimharao terala,

The procedure is as follows:

Create a Material - KMAT type with Item category (002)

Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc

Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)

Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.

Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.

Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save

Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)

Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save

Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)

Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.

A small search on SDN SD forum will help you to answer your query.

I will suggest you to visit http://sap-img.com/sap-sd.htm. It will give you the overview of SAP SD module.

Moreover there is a separate section of FAQs with answers which will help you in great deal.

Hope this helps you.

Do award points if you found them useful.

Regards,

Rakesh

P.S. you can send me a mail at my mail id rakeshsinghchauhan@gmail.com for any specific details

[Former Member]

hi

<b>Preconditions </b>

Use

You can use preconditions to hide characteristics and characteristic values that are not allowed and thereby ensure that the configuration of an object is consistent.

You can allocate preconditions to the following objects:

A characteristic that you want to hide

A characteristic value that you want to hide

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

You can also use restrictable characteristics to restrict the allowed values of characteristics when you configure and object.

Features

A precondition is fulfilled if the condition you enter is either true or not violated.

A precondition is fulfilled if:

The specified value is selected for the specified characteristic

No value is selected for the specified characteristic

The precondition is not fulfilled if a different value is selected for the specified characteristic.

<b>Selection Conditions </b>

Use

You can use selection conditions 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

You can allocate selection conditions to the following objects:

Characteristics

BOM items

Operations in task lists

Sub-operations

Sequences of operations

Production resources/tools (PRTs)

Features

A selection condition is fulfilled if the condition in it is unambiguously true.

A selection condition is fulfilled if the value in the condition is set for the characteristic.

A selection condition is not fulfilled if:

a) A different value is set for the characteristic

b) No value is set for the characteristic

<b>procedures</b>

You can use procedures to infer values for characteristics – they are like actions in this respect. However, there are some important differences:

Procedures

Actions

Actions are an old dependency type. You can almost always use procedures to do the same thing.

Procedures can overwrite default values that are set by other procedures.

Actions cannot overwrite values that are set by other actions.

Procedures can set default values for a characteristic, which can be overwritten by the user.

The user cannot overwrite values that are set by an action.

If several procedures are assigned to an object, you can define a processing sequence (see Processing Sequence of Procedures).

You cannot influence the sequence in which actions are processed.

You can assign procedures to the following objects:

The characteristic value that triggers the procedure

The characteristic that triggers the procedure

The configuration profile of the configurable object

It is easier to assign procedures to the configuration profile, so that they are all in one place.

BOM items – to change the component quantity, for example

Operations in task lists – to change the standard values, for example

Use

If you use a procedure 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).

Additional keywords for procedures:

Set default values:

$SET_DEFAULT ($SELF, <characteristic>, <term>)

Delete default values:

$DEL_DEFAULT ($SELF, <characteristic>, <term>)

Produce a sum of the values for a characteristic in a multi-level configuration:

$SUM_PARTS ($SELF, <characteristic>)

Add the components of a BOM together:

$COUNT_PARTS (<$SELF>)

Surcharge for variant conditions:

$SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>)

In procedures, you can use the following keywords, which are not allowed in actions:

NOT SPECIFIED

NOT TYPE_OF

<multiple-value characteristic>NE<value>

[Former Member]

hi

selection condition

Dependency type used to define that a value must be assigned to a characteristic, or a BOM component must be selected, if a specific value is assigned to a specific characteristic.

precondition

You can use preconditions to hide characteristics and characteristic values that are not

allowed and thereby ensure that the configuration of an object is consistent.

You can allocate preconditions to the following objects:

· A characteristic that you want to hide

· A characteristic value that you want to hide

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

[sailaja_vadlamudi]

Hi

[sailaja_vadlamudi]

hi

Special Features for Variant Configuration

Object dependencies

Engineering change management is only used to process global object dependencies that can be identified by the name of the dependency.
Local object dependencies are saved in the SAP object which is maintained locally (for example: BOM item).

Configuration profiles

If you want to use the change number for configuration profiles with object dependencies, you should define the settings for object types such that object dependencies can be processed with reference to this change number.

Variant Tables

You can process the contents of a variant table with reference to a change number. You cannot process the table structure with reference to a change number.

Displaying a Configuration Overview

You can display the variants of a configurable object. For example, a material could already be configured as a sales order, a production order, or a material variant.

From the variant configuration menu, choose Environment ® Configured objects, and select the object type for the configuration overview.
Enter the object key and choose Configured objects.
If different types of variant exist, select the type of variant you want to see.
If only one type of variant exists, such as configured sales orders, you see a list of objects immediately.

You can select a variant from the list and display its characteristic values.
You can also print the list and find a specific variant in the list.

You can use the modeling environment for Variant Configuration to edit an existing product configuration model.

http://help.sap.com/search/highlightContent.jsp

Sail