Procedure in Variant Class

Hi,
I have written a procedure to calculate some characteristic value. I am using batch specific UOM here. Material is configurable and is having both class (Variant and Batch class). Now when i am creating a PR and when i m trying to do the configuration then the value for the characteristic is not automatically calculated and not coming automatically. i have assigned the dependency to that characteristic and to the variant class both. But still the value is not calculated automatically.
Then i have tried the same dependency in the Batch class and when i m doing goods receipt then it is automatically calculating the required characteristic value.
Can u please tell me why the value is not calculating automatically. Below is the dependency..
$SELF.CD_CHAR_PL_WEIGHT_PER_PC = ( $SELF.CD_CHAR_PL_THICKNESS *
$SELF.CD_CHAR_PL_WIDTH * $SELF.CD_CHAR_PL_LENGTH *
$SELF.CD_CHAR_PL_DENSITY ) / 1000000000
Early reply will be appreciated.
Thanks in Advance
SISL
Edited by: SISL on Nov 19, 2009 12:07 PM

Hi,
Assign the procedure to that characteristic in class, after filling which you want CD_CHAR_PL_WEIGHT_PER_PC to be calculated (let's say CD_CHAR_PL_THICKNESS). When you fill it and press enter - CD_CHAR_PL_WEIGHT_PER_PC will be calculated.
regards,
Alexander

Similar Messages

Java stored procedures and referencing classes

We are referencing to some classes/libraries which are not present in the database. In normal java world, you specify the libraries/classes needed to run your piece of code in the CLASSPATH and that forms part of your complete code.
Can java stored procedures in the database refer to libraries or class files it requires on the file system rather than the database? Is it possible to make this happen?
Thanks

pshiva,
Posting the same question to multiple forums usually doesn't increase your chances of getting an answer, and it just frustrates those wishing to answer you with the result being that any future questions you post may have less chance of being answered -- because of your uncourteous, initial behaviour.
I have answered your other thread:
java stored procedures and referencing classes
In my opinion, that forum (the Database JVM forum) is the most appropriate for your question.
Good Luck,
Avi.

Assign variant class to service material for preconfigured service package

Hi,
Could somebody help with the steps on how to create a service material with variant. The requirement is to create a preconfigured service package.
I'm trying to create a service material and assign a variant class to it. Based on some examples in IDES, i see that in MRP 3 view there is a plant-specific configuration view which holds the variant check box and configurable material reference.
I'm unable to get that view while creating the material.
Regards
Rasheed

Hi Vishal,
From the PS perspective only one document type is allowed to be used for purchase requisitions. Therefore you can only maintain one in TA OPTT.
However, the SAP note no. 114213 gives an explanation of about how the document type is determined and shows where a modification to change this could be implemented.
Hope it helps.
Regards,
Rachel

Is possible to call procedure from vorowimpl class

Hi,
please tell me how to call procedure from vorowimpl class.
Thanks in advance,
SAN

Hi cruz,
Thanks for your reply.
I checked that link and they given for controller.
But i want to call that from the vorowimpl class. but i tried similar like calling in the controller.
here my code, please correct it if it is mistake.
public AssessmentsAMImpl xxam;
public String getXXCompName() {
//return (String) getAttributeInternal(XXCOMPNAME);
OADBTransaction txn=(OADBTransaction)xxam.getDBTransaction();
String compName=getCompName();
String xxName="";
CallableStatement cs=txn.createCallableStatement("DECLARE OUTPARAM VARCHAR2(100);begin apps.XX_COMP_ELEMENTSVO_PROC(:1,:2);end;",0);
try{
cs.setString(1,compName);
cs.registerOutParameter(2,OracleTypes.VARCHAR,0);
cs.execute();
xxName=cs.getString(1);
catch(Exception e){
try{
cs.close();
catch(Exception e){
return xxName;
}

Variants class 200 and 300

what are the differences between the variant classes 200 and 300.
where we have to select 200 class and where we have to select 300 class in variant configuration.
thanking you
srinivas pai

Thanks for marking thread useful.
Class 300 and 200 are both defined for the materials.class 300 is mainly used for a variant material used for variant configurartion.We can also classify materials under class 200 which do not have to be configurable materials.But allows to use the defined characteristics and restrict the usage for a specific purpose..
Please check below threads
http://scn.sap.com/thread/631073
https://scn.sap.com/thread/576848
Yes you can copy class and create your new class .
can you please share your business requirement, what kind of solution your are budiling with this?
Thanks
Ritesh

Step by step procedure to Define Class

Hi Experts!!
Anybody please tell me step by step procedure do develop the class.
Thanks
Anee

Hi
Classes are templates for objects. Conversely, you can say that the type of an object is the same as its class.
components of the class describe the state and behavior of objects.
Local and Global Classes: Classes in ABAP Objects can be declared either globally or locally. You define global classes and interfaces in the Class Builder (Transaction SE24) in the ABAP Workbench. They are stored centrally in class pools in the class library in the R/3 Repository.
Local classes are defined within an ABAP program. Local classes and interfaces can only be used in the program in which they are defined.
When you use a class in an ABAP program, the system first searches for a local class with the specified name. If it does not find one, it then looks for a global class.
Apart from the visibility question, there is no difference between using a global class and using a local class.
Certain restrictions apply when you define the interface of a global class, since the system must be able to guarantee that any program using an object of a global class can recognize the data type of each interface parameter.
Defining Local Classes:
A complete class definition consists of a declaration part and, if required, an implementation part.
 The declaration part of a class <class>
 CLASS <class> DEFINITION. ... ENDCLASS.
It contains the declaration for all components (attributes, methods, events) of the class.
The declaration part belongs to the global program data.
If you declare methods in the declaration part of a class, you must also write an implementation part for it. This consists of a further statement block:
 CLASS <class> IMPLEMENTATION. ... ENDCLASS
The implementation part of a local class is a processing block. Subsequent coding that is not itself part of a processing block is therefore not accessible.
REPORT YSUBOOPS17 .
CLASS c1 DEFINITION.
PUBLIC SECTION.
data : w_num type i value 5.
methods : m1.
ENDCLASS.
CLASS c1 IMPLEMENTATION.
METHOD M1.
WRITE:/5 'I am M1 in C1'.
ENDMETHOD.
ENDCLASS.
START-OF-SELECTION.
DATA : oref1 TYPE REF TO c1 .
CREATE OBJECT : oref1.
write:/5 oref1->w_num.
CALL METHOD : oref1->m1 .
Defined in the global area of a local program :-
CLASS <class name> DEFINITION.
ENDCLASS.
All the attributes , methods, events and interfaces are declared here.
Cannot be declared inside a subroutine/function module.
Class definition cannot be nested.
REPORT YSUBOOPS17 .
CLASS c1 DEFINITION.
PUBLIC SECTION.
data : w_num type i value 5.
methods : m1.
ENDCLASS.
CLASS c1 IMPLEMENTATION.
METHOD M1.
WRITE:/5 'I am M1 in C1'.
ENDMETHOD.
ENDCLASS.
START-OF-SELECTION.
DATA : oref1 TYPE REF TO c1 .
CREATE OBJECT : oref1.
write:/5 oref1->w_num.
CALL METHOD : oref1->m1 .
Local class in a program is implemented as follows:-
 CLASS <class name> IMPLEMENTATION.
 ENDCLASS.
Methods used by the class are described here.
A class can be implemented
At the end of the program( like subroutines).
After the class definition.
If the latter is adopted, one must then assign subsequent non-declarative statements explicitly to a processing block, such as START-OF-SELECTION, so that they can be accessed.

Variants Class (300) Extraction

Dear All,
I have enhanced this structure to capture material characteristics I am using the sap standard function VC_I_GET_CONFIGURATION for which I am passing the CUOBJ field (which is captured in VBAP at the time of sales order creation) as an requesting parameter, the whole enhancement works fine when I am running using RSA3 on the OLTP system hence capturing the characteristics.
When I am trying to extract the same at BW end it displays me an error message that a short dump has been generated on the OLTP system, when I cross check the same on the OLTP system using ST22 it lists an following
error
"SAPLCEI0" "INTERNAL_ERROR"                              or                                                       "SBIE0001 " "INTERNAL_ERROR"                             RAISE_EXCEPTION C SAPLCEI0
or                                                       LCEI0U30 VC_I_GET_CONFIGURATION
I checked up the corresponding notes related to this
1) 423431 Exception condition 'INTERNAL_ERROR' in SAPLCEI0
Ans) Has been implemented.
2) 524896 Deactivate BOM explosion with branching to configuration
Ans)    Not Using BOM.
Could you kindly look into this at your earliest possible convenience
and provide me the solution for same.
Thanks & Warm Regards,
Fayak.

Use the SAP NOTE: 1375815

Class & Characteristics in variant configuration

Hi PP guru's
Pl explain me in detail all the configuration path , spro , tcode for the above said .
thanx in advance
Regards,
Vimalbalaji

Dear Vimalbalaji,
<a href="http://www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm">Steps for SD Variant Configuration</a> :
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 href="http://help.sap.com/saphelp_ides/helpdata/en/0a/857463c87611d1a7760000e8a5f6c8/content.htm">SAP Help Link for Variant Configuration for an Order BOM</a>.
<a href="http://www.sap-basis-abap.com/sd/steps-for-variant-configuration-and-pricing.htm">Steps for Variant Configuration and Pricing</a>
$ROOT is the highest-level configurable material in a configuration.
$PARENT refers to the object immediately above $SELF in a multi-level configuration.
The variable $PARENT has no meaning for the header material, because the header material has no superior materials.
In dependencies that are allocated to BOM items, $PARENT refers to the configurable material for which the BOM was created, whereas $SELF refers to the material of the BOM item.
$SELF is the material to which the dependency is allocated.
Regards,
Naveen.

Class type has not been defined in Customizing as allowed for variant confi

Hi,
I want to use class type 200 in the varient configuration, but following error is showing so please reply me .
Class type 200 cannot be used for materials
Message no. CU731
Diagnosis
This class type has not been defined in Customizing as allowed for variant configuration.
Procedure
Choose a class type which is allowed for variant configuration.
Thanks

Thanks for ur reply.
please help me regarding my requirements
I will have to use the varient configuration. In this scenario multilevel BOM BOMis present & for every level varient is present.
so how to map this scenario, so that it should pop up at the time of sales order creation. i.e. it should ask that which varient should be used at all the levels in the BOM.
Thanks & Regards.
Abhi

Variant config - Two Varinat class to single material

Hi
I had defined two variant classes eg: Class1 & class2 and assigned it to material in clasiification view.
While sales order the systems take me to variant config screen which shows charateristics of both the class combined. I need to display separately .
How can do this ? please help
regards
Arun prasad

Some light on Variant Configuration in Detail.
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.
regards
Satish

Variant Configuration, Procedure for BOM Quantity Calculation

Hi, everybody,
I need to solve this problem and can't have any idea if this is possilbe.
Imagine a company that manufactures for customer specific requirement "plastic rectangles" (Length A, Width B).
Finished Product has a ZFG variant class with class 300.
Class ZFG has two characteristics, LENGTH and WIDTH
BOM for the finished product has one item class "Plastic" which can be replaced with any Plastic assigned to this class. Base unit of measure of Plastics is KG. If any plastic code has its own specific weight per area how can I calculate how much weight (Kg) I need for specific sales order?
The formula is Lenght x Width x Specifi Weight per area of chosen Plastic.
The two first values area characteristics values in configuration, the third one is a value dependent of material (could be a characteristic in plastic class too if this helps.....)
Do you know a way to achieve this? Is it possible to do it using a procedure?.
Thanks and best regards,
Sebastián Ligueros

1. Since youare using class item you will hvae one more characteristics called Plastic type in the Class
2. You can maintian one variant table, in which you can maintain Plastic Type and specific Gravity
3. Now using this you can try to infer the value and using a procedure you should be able to calculate the weight for the BOM item.
Kindly let me know for feedback
Reg,
Dsk

Variant price for one feature is missing -error in sales order

Hello Experts,
I am working on a SAP implementation project for a premier automobile company...
I have stuck on one point here in this project SAP is a back end system. So sales order will generated based on the interface feed from a legacy system.
We have Identified to have two different variant classes in SAP sales order. one will contained all vehicle specification, this will be used by PP for MRP and other variant class will have only optional features and all these features should have variant price in VA00 (maintained as pricing record) in pricing. if any of the feature don't have price then this sales sales order should through an error massage (we will customized this error message as per clients requirement)
Can any one suggest the relevant sales order user exit or any other method to do this check?
Thank & Regards,
Sulabh

Hi Sulabh,
In standard procedure any component value of VA00 not picked by the sale order system doe's not show any kind of message.
Use exit MV45AFZZ - USEREXIT_PRICING_PREPARE_TKOMK.take the help of ABAPer he will write the logic where the VA00
value missing in sale order system should through the error or warning and message which will illustrate the problem,according
to that user will check and maintain the price.
Ram

Variant .. Please Help

Hi guru's
I created varaints for selection screen (FBL5N) customer line items. My problem is tht i want these selection varaint to be come default depanding on specific user...Please tell me is it possible ??
Please help and if possible please let me know !!
Many thanks in advance..sure points
Regards
Inder

dear friend
please try out with the following
VARIANT CONFIGURATIONS:
Slide 1: VARIANT CONFIGURATION OVERVIEW Prepared by Arun prasad C R *Please place your comments
Slide 2: Variant Configuration Introduction: Variant Configuration is useful if you have a large number of combination of parts that go into a product. It means different permutations and combinations of the parts for same material. If you maintain a unique material code for each possible combination of parts, you require a large number of material numbers. Usually involves Make to Order Production Process Variant Configuration Examples: A customer ordering a computer can choose different combinations of monitor, CPU, keyboard. A customer ordering a car can choose different combinations of accessories and color. In a business involving steel manufacturing, the customer may order steel involving different physical properties like tensile strength, diameter. Source: SAP
Slide 3: Industries for Configurable Products Variant Configuration Source: SAP
Slide 4: Cross Module Integration Variant configuration is integrated with the following applications: CA Classification LO Material Master PP Bill of Material PP Routings PP Material Requirements Planning (MRP) PP Production Orders PPPI Master Recipes Variant Configuration CO Costing SD Sales SD Conditions MM Purchasing Source: SAP
Slide 5: Overview of Terms Variant Configuration Source: SAP
Slide 6: Overview of Terms A configurable material has a special bill of material called the Super BOM in which all possible combinations are stored. The product is configured in the sales order by choosing the required Characteristic Values. The requirements are passed on Production Planning. On Explosion of the Bill of Material, the system selects the components assigned to the characteristics values in the order. Variant Configuration After production, the material is assigned as sales order stock for delivery to customer. Source: SAP
Slide 7: Sales Order Processing
Slide 8: IDES Demo Process Steps to be used in the demo: Creating a Sales Order Checking Requirements Using MRP Requirements Planning Converting the Planned Order into a Production Order Confirming the Production Order Checking the Production Order Settlement Variant Configuration Creating a Delivery Creating a Billing Document Source: SAP
Slide 9: Enterprise Structure used for demo Company Code 1000 Sales Org 100 Distribution Channel 12 Variant Configuration Division 00 Plant 1000 Storage Location 0001 Shipping Point 1000 Source: SAP
Slide 10: MTO Process Overview Make-To-Order Production With a Configurable Product: In this process, you create a sales order in SD and transfer the requirements to PP. The requirements are checked using MRP, before a production order is generated. This production order is created in PP. Shipping and billing both occur in SD. Finally, you check the costs and revenues in CO. Variant Configuration Source: SDN
Slide 11: Creating a Sales Order (T Code :VA01) After entering the sales data, a configuration screen pops up. Configure the material by selecting the characteristics. Note that the value of Variant Conditions changes as per selection. Variant Configuration Source: SAP
Slide 12: Creating a Sales Order (VA01) The system allows analysis of Object Dependencies and Variant Conditions. Item Category determined in Sales Order is TAC. Note the Material Availability Date and save the sales order (for test11048 and 11059). Variant Configuration Source: SAP
Slide 13: Configuration for VC
Slide 14: Configuration Details: Material Type OMS2: In definition of KMAT Material Type, indicator Material is Configurable is set Other material types like FERT (Finished Product) can also be used if the indicator is set in material master Variant Configuration Source: SAP
Slide 15: Configuration Details: Item Category in sales order VOV4: Item Category determination is set to determine item category TAC Variant Configuration VOV8: Item Category TAC Source: SAP
Slide 16: Configuration Details: Condition type for Pricing Condition types VA00 and VA01 (%) are available in Standard SAP for Variant Pricing Variant Configuration Source: SAP
Slide 17: Configuration Details: Requirement type KEK The requirement class controls the MRP and the requirements consumption strategy as well as the relevancy for planning, settlement profile for costing. Requirements type KEK is determined for strategy group 25 and also for item category TAC. Variant Configuration Source: SAP
Slide 18: Classification System: Characteristics Mayback 57 S Engine Color Rear wheel Seat Exhaust Antitheft device Variant Configuration Other Options Source: SAP
Slide 19: Classification System: Characteristics Variant Configuration Source: SAP
Slide 20: Classification System: Characteristics Variant Configuration Source: SAP
Slide 21: Classification System: Characteristics CT04: Create characteristics Data type can be CHAR, NUM, DATE, TIME, CURR Variant Configuration List of values and default value for characteristics can be stored in Value tab. Source: SAP
Slide 22: Reference Characteristics Reference characteristics are characteristics that refer to table fields. Variant Configuration Tables / Structures whose filed values can be changed by dependencies: SDCOM - Communication between SD and Variant Configuration VCSD_UPDATE - Table for Updating Sales Documents from the Configuration MMCOM, STPO, PLPO, PLFH, PLFL Tables / Structures whose filed values can be read by dependencies: VBAK, VBAP, VBKD, VBPA_AG, VBPA_WE, VBPA_RE, VBPA_RG VEDA, MAEPV, MAAPV Source: SAP
Slide 23: Classification System: Characteristics CT04: Create characteristics Object dependencies like pre conditions, selection condition, action, procedures can be created for characteristics Object dependencies like pre conditions, action, procedure can be created for characteristic values Variant Configuration Source: SAP
Slide 24: Classification System: Class CL01 /CL02: Create class under class type 300 for Variants Variant Configuration Assign the characteristics to the class. During Material Master creation for Super BoM, this class will be used in the Classification view. Source: SAP
Slide 25: Material Master of Super BoM (MM02) Basic Data 2 Screen: Set Material is Configurable Indicator To determine item category TAC in sales order, maintain a suitable item category group such as 0002 MRP 2 View: Procurement type E: In house Production MRP 3 View: Strategy Grp. 25: Make-to-order for configurable used for demo MRP3 View: Availability Check 02: Individual Requirement Classification view: Attach the variant class Variant Configuration Source: SAP
Slide 26: Bill of Materials (CS01 / CS02 / CS03) Variant Configuration Source: SAP
Slide 27: Object Dependency in BoM (CS02) Components in Production Order can be selected using Object Dependency type Selection Condition Variant Configuration Source: SAP
Slide 28: Routings (CA02) Operations in Production Order can be selected using Object Dependency type Selection Condition Variant Configuration Source: SAP
Slide 29: Configuration Profile: Process Planned/production Order; explosion indicator None (others Single level or Multiple level) The material has a BOM that is not relevant to the sales order. Only the characteristics that describe the variant are required. The components are determined later during material requirements planning or production, so there is no need to explode the BOM in the sales order. Sales order (SET): See next slide also In the sales order, sales-relevant components are shown as sub-items of the header material. Requirements are transferred and pricing is calculated at component level, not at header material level. Order BOM You create a sales order. In order BoM, you can insert extra items or delete items manually. The Variant Configuration changed BOM is stored as a separate BOM for the sales order. Source: SAP CU42
Slide 30: Configuration Profile: SET This processing form means that in the sales order you can only process sales-relevant BOM items. You can use the item category group like 0004 at configurable material level to define that requirements transfer and pricing are at component level. For example, a PC is made up of the components monitor, CPU, keyboard, and printer. These components are all salable materials that are manufactured separately. In the sales order, you want to see the individual components that make up the computer as order items, as well as the whole computer. In the sales order, these products are grouped together in a SET. For this reason, this type of processing is also referred to as set processing. Variant Configuration Source: SAP
Slide 31: Configuration Profile: Dependencies Dependencies like Actions and Procedure can be assigned to Configuration Profile. Variant Configuration Source: SAP
Slide 32: Configuration Profile: Variant Table Tables are used to store combinations of values for different characteristics A table HD_1300_COLOR_PR is created in CU62 transaction. It has 2 fields: HD_COLOR (key field) and SURCHARGE. The selected characteristic will be transferred to HD_COLOR and surcharge to SURCHARGE2. The table contents are given below (see transaction CU60) Variant Configuration VK30: Has description entries for the surcharge column listed above VK12: Will pick up pricing value based on condition type VA00 Source: SAP
Slide 33: Pricing Check definition of characteristic SURCHARGE2 Additional data tab -> reference table and field Variant Configuration Simple method to achieve Variant Pricing is given below: Create multiple value characteristic SURCHARGE2 referring to SDCOM-VKOND. Put this characteristic in the class HD-000 which was used for the configurable material Now go to CT04 and change the Characteristic HD_COLOR Go to values tab and select Red. Go to Extras-> Object Dependencies->Editor and then select Procedure. In front of 000010 Enter $self.surcharge2='HD-003_03'. Similarly Select Black to enter $self.surcharge2='HD-003_02. Same way 'HD-003_01 for Silver VK30: Has description entries for the surcharge column listed above VK12: Will pick up pricing value based on condition type VA00 Source: SAP
Slide 34: Pricing VK30: Maintain descriptions for variant price conditions (optional step; done while creating dependencies for surcharges; maintains consistencies of configuration) Variant Configuration VK11 / VK12: Maintain actual condition record for variant price surcharges Source: SAP
Slide 35: Pricing Factors Pricing factors can only be maintained on characteristic level. The syntax of pricing factors is as follows: $SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>) This expression contains the following information: The characteristic that refers to structure SDCOM, in which variant conditions are defined. The variant key used to infer the condition for a characteristic value. Variant Configuration The factor by which the surcharge increases. Source: SAP
Slide 36: Material Variant For variants that are required frequently, create material variants, which can be produced without a sales order and kept in stock. When a sales order is received, check whether the variant is in stock and deliver immediately. The material master record of a material variant is linked to the configurable material and configured using the characteristics of the configurable material. Variant Configuration Source: SAP
Slide 37: Material Variant in Sales Order On the value assignment screen, you can check whether the values assigned match the configuration of a material variant. Variant Configuration Source: SAP
Slide 38: Material Variant Replacement of configurable material by a material variant Variant Configuration Source: SAP
Slide 39: Material Variant Item category gets changed to TAN; Pricing will also change as per new MTS product. Variant Configuration Source: SAP
Slide 40: Summary of day 1 By now, you should be comfortable with the following topics: Explain what Variant Configuration is and its use in make to order scenario Using Variant Configuration during sales order processing Configuration details like item category and condition types Classification System - Characteristics and Classes Super BoM, Configuration Profile, Object Dependencies Pricing Surcharges in sales order processing Variant Configuration Using Material Variants for make to stock scenario Source: SAP
Slide 41: Day 2: Understanding Object Dependencies in detail
Slide 42: Dependency Types Variant Configuration Source: SAP
Slide 43: Pre Condition Variant Configuration Only if the model specified is racing, the bicycle can have 21 gears. 1. Create a precondition with the following source code: MODEL eq 'Racing' and Specified MODEL 2. Allocate the precondition to value 21 of characteristic GEARS Source: SAP
Slide 44: Selection Condition A selection condition is allocated to each component and each operation. This selection condition determines which components and operations are selected for a variant. Variant Configuration Source: SAP
Slide 45: Changing Master Data with Dependencies In variant configuration, you can use reference characteristics with dependencies to change field values of tables for bills of material (BOMs), task lists, and master recipes. Table names and fields are given below for reference. Table STPO field MENGE can be used to change component quantities of BoM. Table PLPOD field VGW01 can be used to change setup time of Operation. Variant Configuration Source: SAP
Slide 46: Procedures Procedures can set default values for a characteristic (can be overwritten by the user) Variant Configuration Source: SAP
Slide 47: Procedures Set default values: $SET_DEFAULT ($SELF, <characteristic>, <term>) For example: ( $SET_DEFAULT ($SELF, COLOR_CHAR, 'BLUE'), $SET_DEFAULT ($SELF, GLOSS_CHAR, 'NONE') ) IF $root.PC_CASING_CHAR = 'TOWER' Delete default values: $DEL_DEFAULT ($SELF, <characteristic>, <term>) Variant Configuration Produce a sum of the values for a characteristic in a multi-level configuration: $SUM_PARTS ($SELF, <characteristic>) It can be used to calculate the weight of components and transfer the same to structure VCSD_UPDATE, gross weight field BRGEW Add the components of a BOM together: $COUNT_PARTS (<$SELF>) Surcharge for variant conditions in Pricing: $SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>) Source: SAP
Slide 48: Constraints and Dependency Net The main purpose of a constraint is to monitor the consistency of a configuration. There are four sections in a constraint. 1. OBJECTS: Declaration of all classes and objects used. 2. CONDITION: Pre requisite for processing the constraint. 3. RESTRICTIONS: For interdependencies and consistency check; check and set values. 4. INFERENCES: Enter the characteristics for which characteristic values are to be inferred. Variant Configuration Constraints are grouped together in dependency nets. The dependency net can be allocated to a configuration profile. Example: The hard disk can only have the value 1620 for a tower, or 850 for a mini tower. OBJECTS: PC IS_A (300) PC RESTRICTIONS: PC.HARD_DISK = 1620 if PC.CASING = Tower, PC.HARD_DISK = 850 if PC.CASING = Mini tower. Source: SAP
Slide 49: Actions Actions can be used to infer values for characteristics. Actions can also be used to change field values in BOM items or operations in routings. 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. For new developments, use Procedures rather than Actions (to become obsolete) Variant Configuration Source: SAP
Slide 50: Object Variables used in Multi level configurations Variant Configuration Source: SAP
Slide 51: Allowed Dependency Types Preconditions are allowed for characteristics and characteristic values. Selection conditions are allowed for characteristics, BOM items, operations, and production resources/tools. Procedures & Actions are allowed for characteristics, characteristic values, BOM items, operations, and configuration profiles. Constraints can only be linked to a configuration profile via dependency nets. Variant Configuration Source: SAP
Slide 52: Processing Sequence for Dependencies Each time you enter a value for a characteristic on the value assignment screen and confirm the value, the system processes all the dependencies. The dependencies are processed in the following sequence: 1. All actions several times, until no more values can be inferred. 2. All procedures exactly once in the following sequence: a) Procedures for the configuration profile in the order you defined b) Procedures for characteristics Variant Configuration c) Procedures for characteristic values The procedures for each characteristic or value are processed in the order you defined. 3. Actions Values set by procedures can also trigger actions. For this reason, all actions are processed again. 4. Preconditions 5. Selection conditions for characteristics Constraints are processed in parallel with points 13, if all the objects in the OBJECTS section are present, and if all the conditions in the CONDITIONS section are fulfilled Source: SAP
Slide 53: Transfer to Production Planning (Demo)
Slide 54: 2. Checking Requirements Using MRP (T Code :MD04) Step1 to create sales order has already been discussed earlier. 2. Stock Requirements List: The sales order is displayed as a separate planning segment (sales order stock required on material availability date and sales order). Variant Configuration Source: SAP
Slide 55: 3. Requirements Planning (T Code :MD50) The sales order will now be converted into a planned order. Planned Orders represent the first step toward an actual production schedule for the Shop Floor. Variant Configuration Source: SAP
Slide 56: 4. Convert the Planned Order into a Production Order (MD04) Planned Orders are a result of MRP run and serve to provide an initial Production Schedule. Production Orders contain comprehensive information to support a shop floor schedule and provide a method to confirm operations performed. Production orders can be created with reference to a Planned Order. Variant Configuration Source: SAP
Slide 57: 4. Convert the Planned Order into a Production Order (MD04) Object Dependency: BoM Selection Condition ensures only necessary material components are taken. Variant Configuration Source: SAP
Slide 58: 4. Convert the Planned Order into a Production Order (MD04) Object Dependency: Routing Selection Condition ensures only necessary operations are taken. Variant Configuration Source: SAP
Slide 59: 4. Convert the Planned Order into a Production Order (MD04) Prior to release of order, it is not possible for anyone to enter confirmations for the operations in the order. Release the Order and Save it. Gantt chart. Graphic Display the operation scheduling overview, choose Goto Variant Configuration Source: SAP
Slide 60: 4. Convert the Planned Order into a Production Analysis Variant Costs Order (MD04) Display the planned costs, choose Goto Configuration Source: SAP
Slide 61: 5. Confirming Production Order (CO11N) Production Time Ticket Variant For Operation  Enter  Confirmation Control Configuration Source: SAP
Slide 62: 5. Confirming Production Order (CO11N) Back flushing (posting of an issue of components or material withdrawals) Storage of the finished product in the warehouse to sales order stock Goods Movements are posted (errors if any can be corrected in COGI) Actual costs are calculated Just in case, to close the order without yielding a product, perform Restrict Processing -> Technical Completion for Production Order in CO02. Variant Configuration Source: SAP
Slide 63: 5. Confirming Production Order (CO11N) Sample Material Document and FI document entries are shown below Variant Configuration Source: SAP
Slide 64: 6. Checking the Settlement of the Production Order  Settlement From the Production Control node, choose Period-End Closing Individual Processing (KO88) Perform order settlement to transfer the costs of the production order to sales order. Analyze the current cost situation for the Production Order Variant Configuration Source: SAP
Slide 65: 7. Creating a Delivery (VL10G for delivery due list, VL01N for single delivery) Assign a serial number to the material. Pick and post the goods issue. Movement type will be 601 E indicating delivery from sales order stock. Accounting document will be generated to capture the change in inventory. Variant Configuration Source: SAP
Slide 66: 8. Creating Billing Document (VF04/VF06 for due list, VF01 for single invoice) VF01: Create the invoice sample accounting entries (without tax) are shown below F-28: Receive the payment from the customer Variant Configuration Source: SAP
Slide 67: Other Information CRM: It is possible to have configurable products among your Online Store offerings using the IPC (Internet Pricing and Configurator). It allows customers to interactively choose product options via an easy-to-use interface. Customers can mix- and-match these options to build the exact product they wish to purchase. ECC 5.0: Single transaction PMEVC Modeling Environment for VC Variant Configuration Source: SAP
Slide 68: Summary By now, you should be comfortable with the object dependencies and the following topics: Pre conditions Selection conditions Procedures Actions Constraints and Dependency Net Variant Configuration Transfer of sales order requirements to PP Delivery from sales order stock Invoicing the customer Source: SAP
Slide 69: Variant Configuration
regards,
amlan

Subcontractor Price in Variant Configuration

Hi All,
I have a requirement:
When the PO is getting generated for subcontractor, the price for the material has to be determined based on one of the variant value. Example: If the variant(x) <45, then price should $1.29 else $1.10.
There is already dependency written for pricing where I have to add some code for this requirement.
Please help me to do this.
Thanks in advance.
Regards,
Ipsit

hi,
just check if the characteristics are all assinged properly.
anyways.. pl go thru these steps again to chek and confirm.
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.
Hope it helps. Pl reward if useful.
Thanks,
Sadhu Kishore

Variant Configuration $Root $Parent $Self

Hi Gurus
Please help in providing information on Variant Configuration $Root $Parent $Self, and if possible with some test cases..to make it as a base for exploring.
Thanks in advance.
Points will be rewarded.
Regards
Suddu

Dear Suddu,
$ROOT is the highest-level configurable material in a configuration.
$PARENT refers to the object immediately above $SELF in a multi-level configuration.
The variable $PARENT has no meaning for the header material, because the header material has no superior materials.
In dependencies that are allocated to BOM items, $PARENT refers to the configurable material for which the BOM was created, whereas $SELF refers to the material of the BOM item.
$SELF is the material to which the dependency is allocated.
<a href="http://help.sap.com/saphelp_ides/helpdata/en/0a/857463c87611d1a7760000e8a5f6c8/content.htm">SAP Help Link for Variant Configuration for an Order BOM</a>.
<a href="http://www.sap-basis-abap.com/sd/steps-for-variant-configuration-and-pricing.htm">Steps for Variant Configuration and Pricing</a>
<a href="http://www.sap-img.com/sap-sd/steps-for-sd-variant-configuration.htm">Steps for SD Variant Configuration</a> :
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.
Regards,
Naveen.

Procedure in Variant Class

Similar Messages

Maybe you are looking for