Variant configuration help needed.

[former_member232834]

Dear gurus

I am really stuck in Variant Configuration. I have read up on VC and seen lots of available material on the web but still I cannot get my pricing together. When I go to my Sales Order and enter the material. The screen automatically pops up that lets you select the characteristic values ex: color: red,blue,green .Car type: Honda,Toyota, Suzuki. Just to note I have another characteristic called Z_Carprice, which is just sitting there not able to choose or select. This is the one I have assigned the SDcom fields too. Once I select my needed characteristics, I click back and the item availability screen comes I just click the confirm or complete delivery button, then check my pricing and it has 0. The condition type va00 does not even show up and I have maintained the vk11 va00 record with the characteristics and prices.Ex: red 1000rs. Etc. If I enter manually va00 I have to also manually enter a price. It should come automatic. I have really checked my configuration steps many times. I have spent 2 days trying to figure out the mistake. I have also assigned and maintained 0010: dependencies.

$self.Z_Carprice=u2019redu2019

To note: I have a total of 3 characteristics: Z_Model,Z_Type,Z_Color.

In the case of Z_model I have used $self.Z_Carprice=u2019toyotau2019 for example.

I have maintained a new pricing procedure with only va00 inside. Nothing is ticked.

Material is called config material I have used 0002 for item cat and its group. Is there anything I need to maintain in the material master to get my material working properly if there is a mistake? Like MRP stuff.

Also, I have also maintained config profile assigned it to 300 variants etc.

Thanks,

Ali

[Former Member]

Hi Muzammil,

Gothrough below steps:

Slide 1: Sales and Distribution Enterprise Structure Overview

Slide 2: Organization Terms Finance Client u2022 A grouping of companies with a common purpose. Example: u201CClient 001u201D Company Code u2022 Legally independent entity, within a client, that has its own balance sheet and creates its own profit-and-loss statement. Example: Co. Code 0001

Slide 3: Organization Terms Sales and Distribution Sales Organization u2022 A selling unit Example: 0001 Distribution Channel RETAIL STORE u2022 Channel through which saleable materials or services reach customers. Example: Retail, Institution

Slide 4: Organization Terms Sales and Distribution Division u2022 A product group Example: Foods, Cosmetics Sales Area u2022 the combination of sales organization, distribution channel and division

Slide 5: Organization from Sales Perspective Client Sales Org Sales Org Distribution Distribution Distribution Distribution Channel Channel Channel Channel Sales Area Division Division Division Division Division Division

Slide 6: Organization Terms Sales and Distribution Sales Offices u2022 A subsidiary of a Sales Area (Sales Region) Example: South India Sales Group u2022 A subgroup of Sales Office (District) Example: Hyderabad

Slide 7: Organization Terms Sales and Distribution Sales Person u2022 Individual person assigned to a Sales Group Example: 0001

Slide 8: Organizational structure in MM Client Plant 1 Plant 3 Plant 2 Company Code 1 Company Code 2 = Storage Locations

Slide 9: Organizational Structure in Shipping Client 0001 Plant 0001 0002 Shipping point Truck Railway Air

Slide 10: Organizational Structure in Accounting Client 0001 0002 0003 Company Codes

Slide 11: MASTER DATA IN SALES AND DISTRIBUTION u2022every company is structured in a particular manner. In order to work with the SAP system the required company structure has to be mapped into the system. This is done with the help of different organizational structures. u2022 Data about the products, services and business partners is the basis for sales processing in sales and distribution. In the SAP R/3 system, the master data is required for sales processing. In addition to sales and Distribution, other departments of the company such as Accounting, MM, and PP access the master data. u2022 The different business transactions in sales and distribution are stored in the SAP system in the form of documents.

Slide 12: u2022 In SAP, customers and vendors have been termed as Business Partners. u2022 If a customer is also a vendor, both customer master record and a vendor master record should be maintained. To create a link between the master records you should enter the vendor number in the customer master record and customer number in the vendor master record. u2022 Both the accounting department and the sales and distribution department have access to the customer master record. In order to avoid data redundancy, the data for both department is stored in a common master record.

Slide 13: Customer Master Terms Business Partner u2022 All Customers with whom the company is in contact. Sold-to Party u2022 The company which places the order Ship-to Party u2022 The partner receiving the goods. Bill-to Party u2022 The location, the invoice is mailed to Payer u2022 Responsible for Payment Carrier u2022 The vendor responsible for transporting goods

Slide 14: Business Partners in SD Sold To Party Personnel Ship To Party Business Partner Functions Payer Bill To Party Vendor

Slide 15: u2022General data, Company Code data and Sales and Distribution data is stored separately in the customer master record. Company code data is defined individually for for each company code. Sales and distribution data is defined individually for each sales area. General data is independent from company code and sales area. It applies to one customer in all company codes and sales area.

Slide 16: Structure of the Customer Master Records General data Sales and Company Code Distribution Data Data

Slide 17: General Customer Master Data Address Marketing Export General data General Control Contact Person u2022Identified only by the Customer Number, not by Company Code or Sales Area u2022Gives the General Control Parameters Applicable for any business transaction with the customer

Slide 18: Company Code Customer Master Data Account Management Company Code Payment Data Correspondence Insurance Applies to only one Company Code

Slide 19: Sales and Distribution Customer Master Data Sales Shipping S&D Data Billing Partner Functions Applies to only one Sales Area - Dependent on Sales Structure

Slide 20: In most cases theLinking Business Partners sold-to party is at the same time ship-to party, payer and bill-to party. For this reason in the SAP system the function sold-to party includes all these other If a customer fulfils all the partner functions at the same timefunctions. Then only one master record is necessary but if the functions are divided, a corresponding number of master records is needed.

Slide 21: With the help of account groupsAccount Group: we can control the screens, fields and number ranges for the different partner each master record must be assigned to an accountfunctions of a customer group. When you create a customer record for different partner functions, different account groups are assigned automatically by the system. You can access the general data of a customer by just entering the customer number, but to access the S&D data, you have to enter the customer number and sales area.

Slide 22: One Time Customers: u2022 with some customers your company has a long-lasting relationship but with other customers you have only one contact. These customers are known as one time customers. u2022 For customers you create a customer master record for each customer but for one time customers you create a collective master record. u2022 When creating a sales order for a one time customer, the system automatically branches to an address screen, where you can enter the address, name and other relevant information.

Slide 23: u2022 Block/Unblock: You can block a customer master record for a sales order, a delivery, billing or sales support or all of them. u2022 Display changes: You can display all changes which have been made to a customer master record after its creation. u2022 Changing an Account group: If, for example a payer takes on the role of a sold-to party, you can assign the new function to the customer by changing the account group. Changes to the account group and the accompanying partner functions can only be made from a lower level to a higher level.

Slide 24: Comparing customer master record u2022Customer master records are created and maintained in financial accounting and in S&D.In some cases, a customer master record may have been created in S&D but not in FI or Vice-Versa. There is a program which determines which customer records have been maintained in one of these applications but not in the other.

Slide 26: Check Create 5 SP, 3 SH, 1BP, 1PY Assignment 1 Check the org. elements in which view theythe SD views associated with each Change the account group and check the data Check the comparison report fall related with each when changing the account group.

Slide 27: Product & Product and services areServices combined in SAP under the term material. All information necessary for the management of a material and its stocks, as well as its use, is maintained in the so-called material master record. This includes, for example, data on Material type: The material typepurchasing, on sales and on storage. Represents certain features of materials in the system, and has important control functions: the material type is used, among other things, to group field selection functions for a material, or to define the screen sequence, the type of number assignment and number ranges during material master record maintenance.

Slide 28: Material types in the SAP standard version are, for example, raw materials, trading goods, semi-finished products, finished Depending on the material type, company areas maintainproducts, or services. Different data screens. This screen selection applying specifically to an application is called a \"view\". Trading Goods Trading goods are movable goods intended for commercial exchange. Examples of trading goods are market goods, consumption goods and durable goods. Trading goods are always bought and re-sold by your company. The material master record for trading goods therefore always contains purchasing data and sales data. Trading goods are managed in the SAP R/3 System using the key HAWA.

Slide 29: Non-stock Material Non-stock material includes materials that are not managed on an inventory basis (for example, small parts such as nails) though physically in stock. Non-stock materials are managed in the SAP System using the key NLAG. Services Services are represented and managed in the SAP System as materials. Services are immaterial goods that differ from other goods, particularly in that their production and consumption coincide. Services are generally regarded as non-transportable and non-stackable. Typical services are commercial services, transport services, bank and insurance services, goods from cultural organizations and the mass media, as well as services provided by the public security forces or the education and health sectors. Since services cannot be stored, a material master record of this material type does not contain inventory data or inventory management data. No fields for gross weight, net weight or unit of weight are included in the basic data for a service, as are for other material types. Services are managed in the SAP R/3 System with the key DIEN.

Slide 30: Packaging Material This material type includes all materials needed for packaging. For example, boxes or crates. Packaging materials are managed in the SAP R/3 System with the key VERP. Other Material Materials which cannot be assigned to any of the standard material types, can be maintained, as \"Other material\". Thus, besides standard material types (trading goods, finished products, services etc.) you can also create additional material types. When creating such a material, note that a material type must be entered on the first data screen. For standard material types, this entry is not necessary because the material type is selected in the menu.

Slide 31: Type Material type description in SAP IBAU Maintenance assemblies INGG Prod. Resources/tools ASSM Semi finished products INTR Intra materials KMAT Configurable materials CONT Kanban containers DIEN Services LEER Empties DUTT Trading goods LGUT Empties (retail) MACH Rohstoffe MUSTER ERSA Spare parts MODE Apparel (seasonal) FERT Finished products NLAG Non-stock materials FGTR Beverages NOF1 Non-foods FHMI Prod. resources/tools PANI Trading goods PIPE Pipeline materials FOOD Foods (excl. perishables) PROC Process materials FRIP Perishables PROD Product groups GG GAUGES ROH Raw materials UNBW Nonvaluated materials HALB Semi finished products VERP Packaging HAWA Trading goods VKHM Additionals HERS Manufacturer parts VOLL Full products HIBE Operating supplies WERB Product catalogs WERT Value-only materials WETT Competitive products

Slide 32: S&D Screens in the Material Master Record Four screens in the material master record are relevant for Sales and Distribution: Sales 1, Sales 2, Sales/Plant Data ,Texts in Sales and Distribution . S&D Description and important data fields Sales 1 Basic data and units of measure (e.g. sales units, order quantities) Sales 2 Material groupings and tax classification e.g. product hierarchy, material pricing group Sales/Plant Data Sales and shipping data e.g. gross weight, loading group Texts in Sales and Distribution Single-line or multi-line texts for sales documents, in several languages.

Slide 33: In the standard version of the SAP R/3 System, the following industry sectors have been defined for the material master record: A -

---

Plant engineering and construction C -

---

Chemical M -

---

Mechanical engineering P -

---

Pharmaceutical Units of Measure and Quantity Specifications A material can be stored, transported and sold in various units of measure. In the SAP R/3 System, you can therefore define various units of measure which are maintained in the sales and distribution screens.

Slide 34: You can enter the following units of measure in the sales and distribution screens: u2022 Base Unit of Measure u2022 Alternative Unit of Measure u2022 Sales Unit u2022 Delivery Unit Quantity Specifications In Material Master Record two different quantity specifications are used: u2022 Minimum Order Quantity u2022 Minimum Delivery Quantity

Slide 35: Delivering Plants The delivering plant refers to the plant from which the goods are to be delivered to the customer, within a specific sales organization and distribution channel. The plant can be automatically proposed by the system when processing a sales order, if it has been maintained in one of the master records. It can be derived from: u2022 the customer/product info record u2022 the customer master record of the ship-to party u2022 the material master record.. The order of priority is as in the list above

Best Regards,

MH

[Former Member]

Hi

also assigned and maintained 0010: dependencies.
$self.Z_Carprice=u2019redu2019

To note: I have a total of 3 characteristics: Z_Model,Z_Type,Z_Color.
In the case of Z_model I have used $self.Z_Carprice=u2019toyotau2019 for example.

In CU01 create new dependency say ZDEP. with code

$self.Z_Carprice=u2019redu2019

if Z_Color = 'red'

goto CU43 and create configuration profile for your material.

In the confi. profile assign a dependency, created at t code CU01.

now maintain Vk11 with red.

try and revert

P.S. 'red' is case sensitive.

Edited by: Yadav on Dec 22, 2009 10:15 AM

[former_member232834]

Dear, thanks for the reply

but the dependencies already exist meaning I have already assigned all that in CT04 I will go more into detail now.

In ct04 for character Z_Color I have values Red,Blue,Black. I have assigned each one of those values to $SELF.Z_CARPRICE='Red' $SELF.Z_CARPRICE='Blue' $SELF.Z_CARPRICE='Red' in Extras assign object dependencies and also in the 0010 field i pasted the same code.

In ct04 for character Z_Model I have values Honda,Toyota,Suzuki. I have assigned each one of those values to $SELF.Z_CARPRICE='Honda' $SELF.Z_CARPRICE='Toyota' $SELF.Z_CARPRICE='Suzuki' in Extras assign object dependencies and also in the 0010 field i pasted the same code.

In ct04 for character Z_Type I have values XLI,GLI,2.0 D. I have assigned each one of those values to $SELF.Z_CARPRICE='XLI' $SELF.Z_CARPRICE='GLI' $SELF.Z_CARPRICE='2.0 D' in Extras assign object dependencies and also in the 0010 field i pasted the same code.

Z_CarPrice is the other character also that is in my variant class. In this character I have assigned the SDCOM and VKOND. and thats it.

Why is it though that in the sales order I am getting the popup va00 condition type is missing so I have to automatically input it in. I have created the condition record for va00 so it should come automatically. In condition type config for Va00 I have put automatic entry has preference. It is not assigned as mandatory or manual in the pricing procedure I only clicked on required so it can give me that popup. If I dont click on required I wont see anything in the condition in the sales order.

What exactly do u mean by case sensitive? No capital letters allowed or all capital and no lower case? or both.

[Former Member]

Hi

$SELF.Z_CARPRICE='Red' case sensitive means in VK11, "Red" should be maintained not 'red' or 'RED'.

second thing create new dependency (procedure type) for princing and assign it to CU43 configuration profile to material.

[former_member232834]

somehow I got it to work butttt. Since theres 3 different characteristics using the same va00. in my pricing conditions all 3 prices are shown but 2 are inactive and 1 is active. How can I make them all active using the same variant condition type VA00. It is possible to use a 2nd condition type like VA01 for variant surcharge/discount etc. But shouldn't there be a way to use va00 only?

[former_member232834]

Ok guys its now working. What I had to do was change the condition type VA00. From class B to class A.

Standard SAP will not have more then 1 price condition type at a time. It will disable all the previous ones except the last. In class B it becomes a surcharge/discount. So in pricing it will take all the VA00 as a Surcharge. (The config was done in the condition type in spro.)

Thanks for the previous replies and help.

Ali