Product Variant?

Hello All,
I want to maintain Variants for a product in CRM using commpr01,
How do i maintain the variants to a product?
when i open the commpr01 and select a Product Category and flag material as Configurable,
the product Opens with new Tab pages 1.Configuration 2.Product Variants,
But i donot see any Maintainance available there..
How can i maintain the Variants ..
Plz help
FUll points gaurenteed...
Thanks in Advance
Arshad

Hi Arshad,
For Variants you need to have ERP system as an backend as CRM standalone or Products created in CRM dont allow a Variant assignment for the Same.
If you are having an Backend ERP system you assign a Variant to the Base article and Dowload the same in CRM which shall appear as variant of the Main article in Relationship Tab.
Hope it helps you,
Thanks and Regards,
RK.

Similar Messages

Product Variants in CRM from R/3

Hi Everybody,
As you know that Product variant in CRM is material variant in R/3. A material variant is created when the available item is in stock.
Scenario.
I created a configurable material 'KMAT' in the material master in R/3 system . In the basic data screen, I assigned a material variant for the material. Set the characteristics value for the material variant. Once pressed save. The Material record got automatically downloaded from R/3 to CRM.
Now I openend the transaction 'COMMPR01' and entered the material. I could not see in the tab 'Product variant' the material variant which was created in R/3.
1.Any Clue why the material variant did not get transfered to CRM from R/3.
2. Which CRM table and which CDB table has data regarding Product variants.
CRM experts could you please share your knowledge with me.
Any help will be highly appreciated.
thanks in advance
Middleware developer

Hi Jothi,
Just double check these steps :
1. You have created Knowledged base Object in R/3
(tcode CU31 - CU33)
2. You have created Knowledged base runtine in R/3
(tcode CU34 - CU35)
Make sure that VALID FROM information in Knowledge Base Object must be greater than VALID FROM in Material Class.
3. Re-download material ID (if necessary)
4. Re-download SCE Object in CRM
If all steps above successfully run without any
error/warning message, you should be able see Tab Configuration + Variant in CRM Master Data (COMMPR01).
You can see also the Configuration Model in Configuration
Tab (where you can simulate the characteristic
configuration).
Hope this could help.
Cheers,
Gun.

Product variants in CRM

Hi Everybody,
   As you know that Product variant in CRM is material variant in R/3. A material variant is created when the available item is in stock.
Scenario.
I created a configurable material 'KMAT' in the material master in R/3 system . In the basic data screen, I assigned a material variant for the material. Set the characteristics value for the material variant. Once pressed save. The Material record got automatically downloaded from R/3 to CRM.
Now I openend the transaction 'COMMPR01' and entered the material. I could not see in the tab 'Product variant' the material variant which was created in R/3.
1.Any Clue why the material variant did not get transfered to CRM from R/3.
2. Which CRM table and which CDB table has data regarding Product variants.
CRM experts could you please share your knowledge with me.
Any help will be highly appreciated.
thanks in advance
Middleware developer

Hi Jothi,
Just double check these steps :
1. You have created Knowledged base Object in R/3
   (tcode CU31 - CU33)
2. You have created Knowledged base runtine in R/3
   (tcode CU34 - CU35)
Make sure that VALID FROM information in Knowledge Base Object must be greater than VALID FROM in Material Class.
3. Re-download material ID (if necessary)
4. Re-download SCE Object in CRM
If all steps above successfully run without any
error/warning message, you should be able see Tab Configuration + Variant in CRM Master Data (COMMPR01).
You can see also the Configuration Model in Configuration
Tab (where you can simulate the characteristic
configuration).
Hope this could help.
Cheers,
Gun.

Product variant constraint in SNP optimizer run

Dear All,
I have a business scenario where I require a constraint on the number of FG variants produced per day. A number of FG SKUs come under a particular variant. On any day the factory is able to produce only a fixed number of variants (say 5). I am looking for a way to map this constraint in optimizer run.
Will appreciate your thoughts to solve this problem.
Regards,
biplab

Hi,
Does SNP Optimzer considers the Set up costs in the planning run ?
SNP Optimizer considers following factors for the optimizer Run:
Factors Considered During the Run
u2022        Valid transportation lanes
u2022        Lead times
u2022        Transportation capacity
u2022        Transportation costs
u2022        Handling capacity
u2022        Handling costs
u2022        Production capacity
u2022        Production costs
u2022        Storage capacity
u2022        Storage costs
u2022        Time stream (location master data)
u2022        Lot size (minimum, maximum, and rounding value)
u2022        Scrap
u2022        Alternative resources
u2022        Penalty costs for not fulfilling demand (supply shortage)
u2022        Safety stock violation penalty costs
u2022        Procurement costs
u2022        Shelf life
u2022        Cost multipliers
u2022        Location Products
u2022        Fixed PPM/PDS resource consumption
u2022        Fixed PPM/PDS material consumption
Regards
Datta

Product variant search

Hello,
I have created a configurable material 'test' and two variants 'variant1' and 'variant2' in the ECC system. I have transported all of them to ECC. But now I am not sure how to proceed with the variant search.What I mean is that in a transaction (e.g. service contract) exactly what needs to be done so that these two varianst 'pop' up on entering 'test' as a product and configuring the char values.
Kindly give me some leads.
Thanks,
Chili

Hello,
I have created a configurable material 'test' and two variants 'variant1' and 'variant2' in the ECC system. I have transported all of them to ECC. But now I am not sure how to proceed with the variant search.What I mean is that in a transaction (e.g. service contract) exactly what needs to be done so that these two varianst 'pop' up on entering 'test' as a product and configuring the char values.
Kindly give me some leads.
Thanks,
Chili

Product Variant Exclusion Table

Hi,
Using the T-code SE38 and with the Program RCU_EXCL_CHARACTERISTICS, if we select the characteristics which has to be excluded using selection of Configurable material charcteristics, after running this program, the characteristics those have been eliminated are also gets selected for Material Varaint .
Kindly solve this issue.
Regards,
B.Sivashankar.

Hi,
Using the T-code SE38 and with the Program RCU_EXCL_CHARACTERISTICS, if we select the characteristics which has to be excluded using selection of Configurable material charcteristics, after running this program, the characteristics those have been eliminated are also gets selected for Material Varaint .
Kindly solve this issue.
Regards,
B.Sivashankar.

CRM 7.0: set up IPC product configuration

Dear experts,
we set up a CRM 7.0 with ERP 6.0 backend integration. In the ERP we apply ERP variant configuration (Materials). Quite simple: some configurable materials (material type KMAT) with a few characteristics and product variants of them (material type FERT) which are maintained in order processing. Variant conditions are maintained and automatically determined for product items. Now we need this in CRM for opportunity processing.
Therefore we have created Knowledge Base and Runtime Version for the configurable products in ERP and downloaded test materials (one KMAT and one FERT (product variant) into CRM (download objects MATERIAL and SCE). In CRM product master data maintenance for the KMATconfigurable tab with the configuration profile is displayed. Afterwards we downloaded condition master data into CRM, among others variant condition VA00 with condition table A057. Everything looks fine.
In CRM we want to set up opportunity management. In the opprotunity transaction processing pricing is working already besides the determination of variant pricing. As we intend to maintain only FERT materials (product variants)we do not need interactive product configuration in CRM sales order or product simulation in CRM product master data. We only want the variant prices to be determined automatically for the product variants (FERT) in opportunity processing. That is why we are not sure if it necessary to set IPC configuration settings (XCM etc.). This is my first question. Nevertheless we started to maintain settings for product configuration in order to find out if this is solves our problem:
1.) XCM configuration (IPC): we set up a customer application for "crmproductsimulation" and defined customer components jco (RFC test worked) and productvariants and restarted J2EE Instance in TX: SMICM
2.) We set up product configuration customizing:
table: COMM_IPC_PROP: caller; crmproductsimulation; scenario.xcm; ZCRMproductssimulation
table: COMM_IPC_URL: UI_CFG; http://<host>:<port>100/ipc/ipc/command.do
When starting simulation of product model for configurable product in TX: COMMPR01 I get following error message: "HTTP500: ISA Framework: The [XCM application configuration]='ZCRMproductssimulation' does not exist. Check XCM configuration.
Details:   No details available". This application is maintained in XCM so I assume something else is missing.
To sum up my questions:
1.) Is it necessary to set up IPC product configuration as described above when we only want to maintain FERT products which are product variants and determine corresponding variant prices (VA00). No interactive product configuration is necessary.
2.) If it is necessary to set up IPC product configuration to active product configuration (to see product variants in product master data maintenance and opportunity processing and corresponding variant condition data), what did I do wrong?
Thank you very much for your help.
KInd regards,
Mark

Hi Arup,
thank you very much for your reply.
Concerning XCM / CRM customizing I have done the steps you recommended:
1. XCM: I created customer applications for crmordermaintain and crmproductsimulation and maintained customer component JCO for both of them (Assigned JCO User has SAPALL / SAPNEW, test run was successful) Active and default are ticked. Are there any further steps missing.May be in General Application Settings > Customer > ipcwebappconfig - I changed nothing there (SSLenabled: true)
2. In CRM customizing I maintained tables as follows:
COMM_IPC_PROP:
caller   crmordermaintain scenario.xcm   Zcrmordermaintain (name of customer xcm app -case sensitive)
caller   crmproductsimulation scenario.xcm Zcrmproductsimulation (name of customer xcm app -case sensitive)
COMM_IPC_URL:
Destination: UI_CFG ;Appl. <blank>; URL: http://<host>:<J2EEport/ipc/ipc/command.do
Calling the IPC product configuration e.g. from the CRM product master (simulate model), I get the already mentioned HTTP error:"ISA Framework: The [XCM application configuration]='Zcrmproductsimulation' does not exist. Check XCM configuration.".
That's why I am thinking that something is missing concerning the communication between CRM application and IPC,because XCM applications do definitely exist.
Is the URL correct .../ipc/ipc/commando.do which I maintained in table COMM_IPC_URL?
Is it possible to check if communication between CRM Online and Java does work respectively what do you exactly mean by "IPC URL must be available for UI_CFG"? UI_CFG ist a RFC-connection which has to be maintained additionaly and if so what has to be maintained exactly?
You mentioned a RFC_USER (This is the JCO-User I suppose?)and J2ee user. Is the J2ee user just the admin user of the J2EE engine or do you mean something different?
Thanks in advance for your further help.
Best regards,
Mark
Edited by: Mark Willhoeft on Jun 4, 2010 8:36 PM
Just one further thing: After changing XCM config I restarted J2EE by TX SMICM (Administration - J2EE Instance local - Send soft shutdown - with restart). Is this enough to restart J2EE and activate changed XCM settings or has the restart to be handled different?

How can we create Versions for Products in SAP CRM

Hi All,
We want use Product Versions in our CRM IC Webclient. We want to be able to select a product and then have a list of versions to pick from. Can anyone tell me if they have configured Versions for Products in their SAP CRM system. If yes, then how did you go about it.
Thanks,
Ramesh Nallabelli

Hi Arup and Shanthala,
Thanks for the prompt responses. Appreciate your help. We want to create Product versions like this: Product: Windows OS Version: 95, 98, XP, Vista, 7, etc.
When I try to create a configurable product, using the Configuration tab, to create or use a product model I see an error message: PME installation with errors The long text is: The environment variable PME_HOME that includes the PME application has to exist locally in order to start the PME from CRM.
This indicates the configuration of IPC in our CRM system. This is something that we have not undertaken so far.
When I use the Poduct Variants tab to create a product variant for a configurable product, I can't edit here. This view opens in a display only mode. After reading some more about this, It looks like variant configuration needs to be used in tandem with ERP variant configuration. There might also be a need to recreate this in the Java configuration engine. We are going to create these products in CRM only, so this might not work for us.
Regards,
Ramesh

Configurable product - ERP E-commerce 5.0

Hi Gurus,
E-commerce 5.0, ECC 6.0 .......... No TREX........VMC activated
I have the following error once I add the configurable product to the shopping basket and then go to shopping basket.
JCO Exception: COMMAND_EXCEPTION
Function: CFG_API_GET_CONFIG_INFO
Import Parameters:
| PARAMETERS 'INPUT'
CONFIG_ID
G
0
IC6133306
T
|----
|-|
I did the folowing steps
Knowledge bases and runtime versions are created
1) Event Handler is maintained in Table TBE31
2) IPC is maintained as consumer in table CRMCONSUM
3) Table CRMRFCPAR is not maintained as we are on ECC 6.0 (Do I need to maintain this)
4) The JCO user is maintained with the authorization objects S_RFC and S_MI_ADMCO
5) Initialized the DB using report CFG_AP_INITIALISE_DB
6) Request for the Knowledge base and version -- using report CFG_AP_REQUEST_DB
log shows every thing green ... but dont think the Knowledge base is uploaded.
7) ipc/admin/xcm/init.do ...XCM is configured for application type "erp" and the component "jco"
Is there any thing I am missing ... any suggestion why I am getting this error.
Thank you
Ram

Hi Chris,
I have moved to test environment and started working on a clean slate.
I understand what you are trying to tell regarding maintaining the XCM scenario in variant config (SPRO).
I have complete the following steps.
1) Activated VMC
2) IPC is set active in Shop Management.
3) Table TBE31 is maintained for the Event
4) table CRMCONSUM is maintained for IPC
5) Table CRMRFCPAR is maintained with two entries. Though RFC destination is not maintained.
RFC destinations in AP system are not maintained as we are running SAP E-Commerce 5.0 using ECC 6.0 as backend.
6) ran the report CFG_AP_INITIALISE_DB -- every thing is green and can see the knowledge bases in the log.
7) I have maintained the parameter "ipcjcodata" with the JCO component - and maintained the JCO connection user with authorization objects S_MI_ADMCO and S_RFC (with necessary functional groups).
Now If I login to b2b/init.do -- I can see the configuration icon next to the configurable product.
Once I click on the icon -
I can see the reset, accept, cancel options and status and product variant tabs.
But the charecteristics tabs and charecteristics are not being displayed. -- which shows blank.
the jsp's which are showing blank are
1) /ipc/components/characteristicGroup.jsp
2) /ipc/tiles/characteristicGroup.jsp/ipc/tiles/characteristics.jsp
Is there any thing I am missing - Please suggest.
Thank you
Ram

Configurable product in CRM 7.0

Hi all,
has anybody experience with configurable products and product model in CRM 7.0? or is there a detailed manual somewhere?
the way to manage them seems quite different from the previous release in which the PME component was external.
Thanks
Oreste

Hi,
ECC -> CRM Download of Configurable Products
First of all create the KB and Runtime version for ur configurable products(Variant configuration products ) in ECC. Then activate the IPC, download the KR and Runtime Version (SCE).
Create your own Application Customer confiruation in XCM component and the link look http://<host>:<port>/<web app name>/admin/xcm/init.do.
Then go to the table COMM_IPC_PROP and maintaint the table entry with the Application Customer Configuration in XCM for Product and also for sales order if you are using the Sales order for the configurable products...
and also u need to maintain the IPC server setting in the table COMM_IPC_URL
Using the below report RSVMCRT_HEALTH_CHECK you can check whether the IPC and java stack is active. One more thing to keep in mind is if you ever do changes to XCM component then you need to restart the Java Server everytime.
CRM (Standalone)
From CRM 2007 onward the PME has been replaced with WEBUI. in the WEBUI you create the Configurable products and then create the product model.
Create your own Application Customer confiruation in XCM component and the link look http://<host>:<port>/<web app name>/admin/xcm/init.do.
Then go to the table COMM_IPC_PROP and maintaint the table entry with the Application Customer Configuration in XCM for Product and also for sales order if you are using the Sales order for the configurable products...
and also u need to maintain the IPC server setting in the table COMM_IPC_URL
Using the below report RSVMCRT_HEALTH_CHECK you can check whether the IPC and java stack is active. One more thing to keep in mind is if you ever do changes to XCM component then you need to restart the Java Server everytime.
Pls let me know if you need any thing else
Regards
Vinod

Configuration management (LO-CM) used with Variant configuration (LO-VC)

Hi
I am new to SAP, working with Variant configuration (LO-VC).
I wish to enforce configuration management during development of a new Variant configurator.
Would Configuration management (LO-CM) work together with Variant configuration (LO-VC)?
My expectation is that SAP Configuration management (LO-CM) will work similar to solutions like e.g. MsVisualSourceSafe, SubVersion, CVS, IBM/Rational ClearCase etc. in the software development domain.
best regards Henrik

Hi Amber
Thanks a lot for answer, and please apologize my late response.
I am not confused by the term 'configuration', being used in two different meanings.
(1) Variant configuration (VC) is the dicipline of creating product variants by making a set of choises from the characteristics describing the product. A complete and consistent set of choises is a 'configuration'.
(2) Configuration Management in the 'traditional' software development meaning: Software Configuration Management (SCM). E.g. Microsoft VisualSourceSafe, IMB/Rational ClearCase, Subversion etc. are examples of tools used for the kind of SCM I wish to apply to VC models.
My confusion is whether the SAP CM that I can read about in the SAP online help, is similar to traditional SCM, and whether it can be applied to VC models.
I wish to apply SCM to a VC model. All the objects that together make up the VC model may then each exist in various versions (version control). A complete set of the objects (in a given version) make up a configuration of the VC model.
What is achieved is : you can control the development of VC model in just the same way that all serious software is under the control of SCM. This will allow an evolution of the VC model, like e.g. version 1.0 is released in January, then version 1.1 is released in June. A major upgrade of the model may become version 2.0 in December etc. The 'source code' (the objects) of each of the versions can be retrieved at any time from the SCM system. Also with SCM several developers may work on the same VC model at the same time, and merge their individual work into the same model.
This is very different from todays VC model development. In todays VC model development, only one version exists, that is 'todays version'. Any change to the model is released immediately, and you can undo model changes only if you remember what it was like a little while ago.
We do develop and test VC models in one SAP system, and then move them to the production system. This is however still very far from the benefits of SCM.
best regards
Henrik Saugbjerg

Product Structure Synchronzation-SAP PLM 7.02

Hello All
I need some clarification on PSS.
I have already created the M-BOM by synch' of Product variant in PSM.
The Synch Unit has the status aligned and also M-BOM is created.
Now there are some changes made in the items of the assembly used in the product variants.
1. Can I now re-run the existing synch unit so that the changes are reflected in the M-BOM
or is that I need to create new synch unit for the changes to be reflected with alternative number for the same M-BOM.
Prompt reply will be highly appreciated as I need to resolve this issue ASAP.
Cheers
Satish

Hi,
Has the assembly below the product variant been synchronized?
If yes, then of course leveraging the existing sync unit is the standard behavior.
Ulf.

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

Variants on Price Definitions - Please Help

Variants is a new topic that I am not familiar with.
Can anyone send me some documentation regarding variants on Price Definitions ?
My email is [email protected]
Marco

Hi
Variant Configuration is a tool which helps to simplify th complex manufacturingof final products with more variants and variationof the input material.
The Manufacturer always has to offer new variants of its Products
Example :
Take any Bike lets say in our example i am taking Honda CBZ
we know that Honda has come up with 150 CC bike and 180 CC bike and 300 CC bike. With Different Colors. Here we are Engine CC and Color as variants
As CC of engine grows so as Price of the Bike.
             Engine                                   Price
             150 CC                                 8000
             180 CC                               10000
             300 CC                               15000
              Color                                  Price
             Black                                   10000
             Green                                   20000
             Red                                      25000
Often by modifying the existing Product Variants. We create the New variants as we process the order. So that we can react quickly to the customer Requirements.
Step 1
Characterstics :
In our example we are taking Engine and Colour as Characterstics and 150cc,180cc,300cc, are variants of Engine
Red,Green,Black are variants of Color
when we create sales order for Configurable Material,That Sales Order must describe Precisely how the product being ordered has to look. This Desciption always comes from the characterstics and corresponding Values
We Use Characterstics to define the features of the configurable MAterial so that the customer can choose from the different options of the characterstics (i.e Characterstic Values nothing but Variants )
To creat Characterstics       CT04 - Create two charaters as Engine & Color
Action 1 : Specify the characterstic name and select the icon Create
               Select the tab Page Basic Data
Action 2 : Specify the Description
               The status must be released
              Data type : specify the data type as chracter - Format
              Number of Character give it as 10 :
In the "Value assignment" Section of Basic data specify as single if it is Single level or Multiple if it Multiple Values. But for our example it is Simple.
Action 3 :
Select the Tab Page Values and Enter the required Value.
In our example it is 150 CC,180 CCand 300CC for engine character.
Red,Green,Black for color Character
Step 2 : Creating Class CL02 Creat one class as BIKE two bind two characters.
iN VARIANT CONFIGURATION a class is used to hold to Charactestics together that describes Material.
BY linking class to the material we allow the material to be configured in the sales Order by using thecharactestics of the Class
In variant configuration we can only use a class if that class has to a class type that supports variant Configuration. In the standard SAP system The class type for Variant configuration is 300
CL01 create
Action : 1
Specify the required class "Bike"
Enter the class type 300
and select the icon create
Action 2
On the basic data view
specify the Description
and status must be released
Action 3
Select the view Chracterstics and Enter the Created characterstics I.e Engine and color
Step 3 :
Creating the material master : MM01
the material type is KMAT (configurable Material)
when you are creating material for Variant configuration select the view Basic Data, classification,slaes oranisation 1 and 2 and Sales Geral/plant and MRP .
Note : While creating material in Basic Data tab at the lower section in CM relevance field Give the Value 1 Relavent for configuration Management
We have to assign the "Class" to the material in the View classification
The Item category Group is Either 0002 or 0004
Enter the reqwuired data and save the material
Step : 4
Configuration Profile :
we maintain the configuration profile for theConfigurable Objects to define the central settings for configurating the objects.
Creating Configuration Profile
CU41- Create
Select the Object Material
Enter the required material(Honda)
Create the profile by specifing the Class Type 300
Select the created profile and the icon "Profile Detail"
We can maintain all the central settings on the view Configuration intial screen and save it
Step : 5 Dependencies
The dependencies descibe the inter dependencies between the chracterstics and the characterstic Values. It also controls which componens are selected from the bills of Material.
Dependency Types:
1. Pre condtion : which we should when our material BOM Material
for our eample we should use Procedures
Cu01 _ Create
Note Here we need to create the dependency and assign it to the required chracterstics value or we can create directly go to the chracterstic value and write the dependency there it self
Step : 6
Creating chractestic Price :
Create one Dummy chacraterstic at CT04
as Zprice
enter characterstic and create on Basic Data TAB
specify deascription and the status must be released
in the Tab of Addition Data specify the Table name SDCOM andthe VKOND
Format data given by ABAP dictionary

Dispaying the variant configurable produts in E-Commerce application

Hi Gurus
Need the Help
How to dispay the configurable products in E-commerce application.How can u differenciate the Normal products and Variant configured products,If any one having any idea please respond fast.
Currently we are using 2007 version of CRM.
Regards
Satish
Awaiting for ur response.
Regards
Satish

Dear Satish & Shalini Chauhan
I am also facing same problem.
We have Varaint configuration products in ECC. For this we created Knowledge base object and runtimer version in ECC.
This KB are downlaoded sucessfully in CRM using the 'SCE' object. Again we download the 'Material' object.
Product are replicated sucessfully (COMMPR01) but there is no entries in tab Configuration and Varints.
Please guide me any further settings are required to view the product variants entires in tab Configuration.
Regards
Mallik Kosuru

Product Variant?

Similar Messages

Maybe you are looking for