Material variants via LSMW

Hello all,
Is it possible to create material variants via LSMW. Via the direct input (RMDATIND), I can't fill the necessary fields in the MRP 3 view and configure the variant. I tried to search for an other transaction to use and maybe create a batch input but for the moment no luck.
Thanks in advance
Best regards
Roel

Hi
Yes, u should use only one file with data of client-level and plant-level, so it means the data of client-livell will be the same for the same material code.
In this way u can create only one transaction for every materila/plant (i.e the BAPI will be called for every plant), if u use two files the system'll try to upload the data of two plants by the same transaction.
What u need to understand if u need to move the data client-level again as soon as you move the data of second plant.
Max

Similar Messages

Updating the Customer & Material Tax Classification via LSMW only

We need to update the Customer and Material Tax Classification via LSMW only, in such a way that on the updation of the Tax classifications the Customer Master and the Material Master should be updated automatically.
Please let me know if anyone has done the same also it would be really helpful if you can provide me the details.
Regards,
Arindam

Hi,
It's not clear your question to me.
Do you want to update the Tax classification in the customer master & Material master?
I did same, but with 2 different LSMW"s as there is not link between customer master & Material master.
To update customer tax classification -
In that you have to feed relevant customer numbers with sales areas & relevant tax classification for one LSMW.
To update Material tax classification -
In that you have to feed relevant material numbers with sales areas & relevant tax classification for different LSMW.
Best regards,
Anupa

Usage of material variants in automotive industry

Dear Experts,
I want to understand the usage of material variants in an automotive industry (car or two-wheeler). Please provide the config settings required and also the usage of super BOM & Routing (if required) with the complete flow. I would prefer if someone can share the scenarios in a two-wheeler industry.
Thanks in advance.
Sameer

Hi Suresh,
Thanks for your answer.
1)We have about 9 characteristics. If we need to create material variants, around 200 material variants will be required to be created. Is that the best option?
2)If we select the first characteristic value, we want only those remaining chararacteristics to be available for selection which are related to the first characteristic. Likewise, we want to have control over the selection of each characteristic, till all the characteristic value selections are made in the sales order. Is it possible that a pop-up comes with the available characteristic options for that combination/s.
3)Can we make a super BOM for items selection? How can I control the selections from the super BOM? Can it be done via Object Dependencies? Routings are same for all the options.
Thanks in advance.
Sameer

Routing - Direct upload via LSMW

Hello all,
Am using direct upload program RCPTRA02 to upload routings via LSMW.
I am uploading headers, operations and material assignments. I keep coming across the following error:
C\ 001
No header alternative for specified object exists
Anyone got any idea as to what this relates to/means?
Many thanks.

Hi Kruna,
I am having the same issue. I am working on SAP ECC 6.0.
Thanks in advance
Atul Bhardwaj

Plant specific material variant

Hi Forum,
Has anybody downloaded plant specific material variant from R/3 to CRM.
Please advise.
Regards,

Hi Anup,
First make sure you have replicated the customizing object DNL_PLANT (R3AS) and that the plants have been correctly created as business partners in your CRM client. After this you should be able to replicate the desired materials by applying the right filter settings for the object MATERIAL (R3AC1) and replicating the object via R3AS.
After replication the correct plant should be visible in COMMPR01.
Hope this helps,
Kind regards,
KZ

Creating Routings via LSMW

Hi all,
Can anyone give me some pointers when creating Routings via LSMW. I see there are two standard uploads in RCPTRA01 and RCPTRA02. However, the mapping structures seem to be different between the two.
I need to add PRT's material assignments and long texts to the routing.
Any help greatly appreciated.

Hi,
Use standard batch/Direct input : RCPTRA02
Source Fields
        MATERIAL_ROUTING          Material
            PLNAL                          C(002)    Group Counter
            MATNR                          C(018)    Article Number
            WERKS                          C(004)    Site
            OPERATION_ROUTING         Operations
                PLNAL                          C(002)    Group Counter
                VORNR                          C(004)    Operation/Activity Number
                STEUS                          C(004)    Control Key
                ARBPL                          C(008)    Work center
                WERKS                          C(004)    Site
                LTXA1                          C(040)    Operation short text
                MEINH                          C(003)    Quantity unit for operation (batch input)
                BMSCH                          C(017)    Base quantity (Batch input)
                LAR02                          C(006)    Activity Type
                VGE02                          C(003)    Unit for the standard value (batch input)
                VGW02                          C(011)    Standard Value (Batch Input)
                LAR03                          C(006)    Activity Type
                VGE03                          C(003)    Unit for the standard value (batch input)
                VGW03                          C(011)    Standard Value (Batch Input)
            COMPONENT_ROUTING         Components
                PLNAL                          C(002)    Group Counter
                VORNR                          C(004)    Operation/Activity Number
                POSNR                          C(004)    BOM Item Number
                MATNR                          C(018)    Article Number
                WERKS                          C(004)    Site
Field Mapping and Rule
       RC271_DS                       Work center structure for direct input (for datasets)
           Fields
               TCODE                        Transaction Code
                                   Rule :   Constant
                                   Code:    RC271_DS-TCODE = 'CA01'.
               STTAG                        Character Field Length = 10
                                   Rule :   Constant
                                   Code:    RC271_DS-STTAG = '18.03.2014'.
               AENNR                        Change Number
               REVLV                        Revision Level
               WERKS                        Site
                                   Rule :   Transfer (MOVE)
                                   Code:    RC271_DS-WERKS = MATERIAL_ROUTING-WERKS.
               PROFIDNETZ                   Profile
               PLNNR                        Key for Task List Group
               PLNAL                        Group Counter
                                   Rule :   Transfer (MOVE)
                                   Code:    RC271_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
               STATU                        Status
                                   Rule :   Constant
                                   Code:    RC271_DS-STATU = '4'.
               VAGRP                        Responsible Planner Group/Department
                                   Rule :   Constant
                                   Code:    RC271_DS-VAGRP = 'KD1'.
               VBELN                        Sales Document
               POSNR                        Character field of length 6
               PSPNR                        Work Breakdown Structure Element (WBS Element)
MAPL_DI_DS                     Assign routing to article for direct input (for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Code:    MAPL_DI_DS-ACTTYP = 'H'.
        MATNR                        Article Number
                            Rule :   Transfer (MOVE)
                            Code:    MAPL_DI_DS-MATNR = MATERIAL_ROUTING-MATNR.
        WERKS                        Site
                            Rule :   Transfer (MOVE)
                            Code:    MAPL_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    MAPL_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
        LIFNR                        Vendor Account Number
        KUNR                         Account Number of Customer
        SUCHFELD                     Search Field for Customer-Specific Task List Selection
        VBELN                        Sales Document
        POSNR                        Sales Document Line Item (Batch Input Field)
        PSPNR                        Work Breakdown Structure Element (WBS Element)
PLKO_DI_DS                     Header structure for direct input (for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Code:    PLKO_DI_DS-ACTTYP = 'H'.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    PLKO_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
        VERWE                        Use by user or system
                            Rule :   Constant
                            Code:    PLKO_DI_DS-VERWE = '1'.
        WERKS                        Site
                            Rule :   Transfer (MOVE)
                            Code:    PLKO_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
        STATU                        Status
                            Rule :   Constant
                            Code:    PLKO_DI_DS-STATU = '4'.
        PLNME                        Unit of measure for the task list (batch input)
                            Rule :   Constant
                            Code:    PLKO_DI_DS-PLNME = 'KG'.
        LOSVN                        From lot size (BTCI)
                            Rule :   Constant
                            Code:    PLKO_DI_DS-LOSVN = '0'.
        LOSBS                        To lot size (BTCI)
                            Rule :   Constant
                            Code:    PLKO_DI_DS-LOSBS = '999999999'.
        VAGRP                        Responsible planner group/department
                            Rule :   Constant
                            Code:    PLKO_DI_DS-VAGRP = 'KD1'.
        KTEXT                        Task list description
                            Rule :   Constant
                            Code:    PLKO_DI_DS-KTEXT = 'Article Routing'.
        TXTSP                        Single-Character Indicator
PLPO_DI_DS                     Routing/item structure for direct input (for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Code:    PLPO_DI_DS-ACTTYP = 'H'.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-PLNAL = OPERATION_ROUTING-PLNAL.
        PLNFL                        Sequence
                            Rule :   Constant
                            Code:    PLPO_DI_DS-PLNFL = '000000'.
        VORKN                        Node number (batch input)
        VORNR                        Operation/Activity Number
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-VORNR = OPERATION_ROUTING-VORNR.
        UVOKN                        Node number (batch input)
        UVORN                        Suboperation
        STEUS                        Control key
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-STEUS = OPERATION_ROUTING-STEUS.
        ARBID                        Object ID (batch input)
        OBJTY                        Object types of the CIM resource
        ARBPL                        Work center
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-ARBPL = OPERATION_ROUTING-ARBPL.
        WERKS                        Site
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-WERKS = OPERATION_ROUTING-WERKS.
        KTSCH                        Standard text key
        LTXA1                        Operation short text
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-LTXA1 = OPERATION_ROUTING-LTXA1.
MEINH                        Quantity unit for operation (batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-MEINH = OPERATION_ROUTING-MEINH.
UMREN                        Denominator for conversion from unit to base unit (BTCI)
                    Rule :   Constant
                    Code:    PLPO_DI_DS-UMREN = '1'.
UMREZ                        Numerator for converting from unit to base unit (BTCI)
                    Rule :   Constant
                    Code:    PLPO_DI_DS-UMREZ = '1'.
BMSCH                        Base quantity (Batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-BMSCH = OPERATION_ROUTING-BMSCH.
ZMERH                        Break time (batch input)
ZEIER                        Unit for break time (batch input)
LAR01                        Activity Type
VGE01                        Unit for the standard value (batch input)
VGW01                        Standard Value (Batch Input)
LAR02                        Activity Type
VGE02                        Unit for the standard value (batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGE02 = OPERATION_ROUTING-VGE02.
VGW02                        Standard Value (Batch Input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGW02 = OPERATION_ROUTING-VGW02.
LAR03                        Activity Type
VGE03                        Unit for the standard value (batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGE03 = OPERATION_ROUTING-VGE03.
VGW03                        Standard Value (Batch Input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGW03 = OPERATION_ROUTING-VGW03.
PLMZ_DI_DS                     Article component allocation for direct input(for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-ACTTYP = 'H'.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    PLMZ_DI_DS-PLNAL = COMPONENT_ROUTING-PLNAL.
        PLNFL                        Sequence
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-PLNFL = '000000'.
        PLNKN                        Node number (batch input)
        VORNR                        Operation/Activity Number
                            Rule :   Transfer (MOVE)
                            Code:    PLMZ_DI_DS-VORNR = COMPONENT_ROUTING-VORNR.
        STLTY                        BOM category
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-STLTY = 'M'.
        STLNR                        Bill of material
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-STLNR = '00000005'.
        STLAL                        Alternative BOM
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-STLAL = '01'.
        STLKN                        Node number (batch input)
        POSNR                        BOM Item Number
                            Rule :   Transfer (MOVE)
                            Code:    PLMZ_DI_DS-POSNR = COMPONENT_ROUTING-POSNR.
WERKS                        Site
                    Rule :   Transfer (MOVE)
                    Code:    PLMZ_DI_DS-WERKS = COMPONENT_ROUTING-WERKS.
BOMAT                        Article Number
                    Rule :   Transfer (MOVE)
                    Code:    PLMZ_DI_DS-BOMAT = COMPONENT_ROUTING-MATNR.
STLST                        Order level
STLWG                        Order path
STLTY_W                      BOM category
                    Rule :   Constant
                    Code:    PLMZ_DI_DS-STLTY_W = 'M'.
STLNR_W                      Bill of material
                    Rule :   Constant
                    Code:    PLMZ_DI_DS-STLNR_W = '00000005'.
STLAL_W                      Alternative BOM
                    Rule :   Constant
                    Code:    PLMZ_DI_DS-STLAL_W = '01'.
Map the extra fields according to your requirement. Hope you'll find the code helpful.

Is it Possible to delete the configuration from a Material Variant?

Hi,
Can you delete the configuration from a Material Variant and then reconfigure the part in MM02?

Hi
Once we created variant we can't delete it,
Regards,
srihari

How to find the list of material variant based on the characteristics value

Hi
We are creating materials variants for FERT Material Type in material master in MRP-3 view .There we configure the variant by attaching characteristics value
Now we want to have a report , which can give the list of material variants , if char value is given in selection
Can somebody guide me if there is standard report for this OR what is the linkage in Table , so that we can develop a report
rgds
Sandeep

I couldn't find a standard report to get the material variants based on characteristic values (the nearest I could find was CT12) but I wrote a report some time back here's the table join logic for the main select statement.
select a~matnr
        e~atwrt
        h~atwtb
into table i_tab
      from MARC as a
      inner join IBIN as b
      on b~instance eq a~cuobj
      inner join IBIB as c
      on c~ibase eq b~ibase
      inner join IBINVALUES as d
      on d~in_recno eq b~in_recno
      inner join IBSYMBOL as e
      on e~symbol_id eq d~symbol_id
      inner join CABN as f
      on f~atinn eq e~atinn
      inner join CAWN as g
      on g~atinn eq e~atinn
      and g~atwrt eq e~atwrt
      inner join CAWNT as h
      on h~atinn eq g~atinn
      and h~atzhl eq g~atzhl
     where     a~matnr in s_matnr
            and e~atinn in s_atinn
            and e~atwrt in s_atwrt
           and b~valto eq '99991231235959'. "This is important condition
I included bare minimum fields to suite your requirement needs you can add whatever other field you want . Though I tested the table join, I suggest you to test it again before writing your own ABAP program using SE16N.

Material variant replacement in sales order for Configurable Material

HI
I am using variant configuration. In this i have created material A as configurable material and have Preconfigured Material B as its variant by assigning configurable material in MRP 3 view.
Now when i am creating Order for material A i.e. Configurable material and the characteristics values are same as that of Preconfigured material system is not replacing Configurable material with Preconfigured material.
Please help me out.
Regards,
Anand.

Even after maintaining the item category MTAC(Mills Make to order config at mat level), the configurable material is not getting replaced in the sales order (va02). It is just showing material variant exists for the configurable material.
The setting in item category for configuration is.
Config. Strategy 01(Sales Order Strategy (TAC, TAM))
Mat. Variant Action 4 (Replace configurable material (Append and change))
ATP material variant 2 (Do not substitute if not completely available)
Structure scope D (Configuration, poss. with BOM explosion)
I have maintained the stock for material variant as well to take care of ATP material varinat setting shown above.
Please suggest if missing something.

Material Variant Matching in Sales Order Creation with ref.to Sales Order

Hi All,
We are working in Variant configuration.Our product is defined at PQD(Product, Quality & Dimension).
But, Sales Contracts are created at PQ (Product, Quality/Grade ) level only.
We have defined Variant Characteristics GRADE(ALLOY CODE),DIMENSION AND TWO MATERIALS.
MAT 1 , configurable material.
MAT 2, A Material Variant of MAT 1, Having values of GRADE = A & DIMENSION = 150 in MRP 3 view of the same.
When a Sales Order is created for MAT 1 and its characteristics values are GRADE = A, DIMENSION = 150, Material Variant type matching happens & it replaces the configurable material.
Similarly,Sales Contract is created for Configurable material MAT 1, with only GRADE = A ( As mentioned above, only quality is known at contract creation level).But, when we are trying to creart a Sales Order with reference to this Contract, we are trying to punch characteristic Value for DIMENSION = 150 also. At this stage, Materuial Variant MAT 2 is shown, but it is not replacing MAT 1.
Is this the standard behaviour or there is some solution/enhancement available.
regards,
Stuti

Dear Vijay,
in incompletion procedure we can arrange to check whether any field is empty, here data comparison is not possible.
As far as I know you can not achieve this through standard config.
To achieve your requirement, you will need to take help of an ABAPer, it can be achieved using Userexit.
ABAPer can use include MV45AFZZ
and Userexit ""USEREXIT_SAVE_DOCUMENT".
the code written in this userexit will check and compare the quantities before saving the dcument.
Logic if quantity enter is greater than the quantity mentioned in Contract show warning Message.
I hope this solves your Problem.
Regards,
Paresh

Transfer of characteristics values from material variant to its subordinate

Gurus
Need your Expert opinion on Variant configuration
We are using Multi level Material Variants and our bussiness process demands for configuration of These Material variants in Transaction MD81 and during creation of Sales order .These configuration will not affetc the BOM explosion but will only be passed to the The lower level components (Which are again theMulti level Configuriable Material variants ) as manufacturing instructions .To Enable these Flow of Characterisitcs we have Applied a Note which allows the Multi level Configuration of Material Variants and Pass this Values to lower Level and the characteristics value flow is visible as well for lower level from CU50 ,but when i create the requirement through CIR or sales order and Configure the Material Variants and Generate the Procurement Proposals to fullfill these requirements (MD02) in the form of Planned order we are unable to pass one the Characterisitcs values to planned orders of lower level Components of Material Variants .These characterisitc values are Used as Manufacturing Instructions and should be passed on to the Lower level of Material Variants through the use of dependencies in Configuration profile .but the problem is it works in CU50 and does not flow in planned orders , does any body have a solution for this ?
Thanks In Advance
awaiting reply
Milind

Hi Milind,
I check that you implement a Note which allows the Multi level Configuration of Material Variants? is it sap note? mind to share the number.
I ever faced this problems to before but fortunately the case in simpler so i just create another variant and maintain the component for the variant. For example : characteristic color. I create variant with color red black etc. For variant red, maintain component red. For variant black maintain component black, so on. Is it possible for your case?
Regards,
Arman

BAPI FOR CREATION OF MATERIAL VARIANT IN SAP

Dear All,
Can anoy one please provide me name of BAPI to create material variant.This is required when we create material variant for a configurable material, characteristics values are added in MRP 3 View .

i am not clear what youn are looking for.
Say material X is KMAT,
Material Y you have created as a variant of X by entering the conf material X in MRP3 view and setting the char values
Material Z you have created as a variant of X by entering the conf material X in MRP3 view and setting the char values different than Y
Now Y and Z are material variants of X, now tell me exactly what you are looking for?

Material variant not found when configuring an item on a sales order...

My client has been using Configurable Materials and Material Variants for several years. At times, when entering a sales order on a Configurable material, the Material Variant is NOT displayed, even though the values entered for characteristics exactly match that of a Variant.
I suspect that the "link" between the Configurable material and the Material Variant has been broken, perhaps due to changes made to one of the material masters. I've found that I can restore this "link" by changing the configuration of the Material Variant (MM02 transaction, the MRP3 tab, "Configure variant" button).
(1) Can you tell me under what circumstances the "link" between Configurable and Variant gets broken? In other words, are there certain fields on the Material master which, when changed, break this link? If so, which fields?
(2) Can you tell me how to identify those Material Variants which have a broken "link" (eg, those which do not link back to a Configurable material, for sales order entry purposes)? Is there an ABAP or such to restore all such broken links?

Hello and thanks for your response. I've searched OSS and had found several informative notes (900732, 774346), though none seem to deal with my problem. If you know of a note I'd much appreciate the lead... (:

Material Variant of a Config Material to take Charac. Values from Sales Ord

Hello Guys,
Is there any way to have a Material Variant for a Configurable Material to take the Characteristic values from a Sales Order instead of Material Master ?
I understand by default Material Variant has fixed characteristic values and is taken from material master......
however here is the situation am in.......
I have a completely MTO scenario where we will making the product from scratch only after we know the characteristic values.......however our Costing Guys want to do standard cost estimate for the Configurable Material somehow......they were able to do Cost Rollup by making the Configurable Material itself as the Material variant of itself (assigning the same Configurable Material # in MRP3 view)............however this broke my design of taking characteristics from the Sales Order...because the Configurable Material is now behaving as Material Variant and taking the default characteristic values from the Material Master....
Note: Our Costing guys donot want to cost settlement at Sales Order level.
Regards,
BRN.

I had exactly the same problem. (configuration "blocked" in SO because the use of material variants for PC purposes...)
SAP help says : To allow you to change the configuration of material variants in the sales order, the Configuration allowed or required indicator must be set in Customizing for Sales and Distribution. The requirements class is determined using the strategy group and requirements type defined in the material master.
The req. class parameter, mentioned not very clearly by the SAP help, that allows changing the characteristic values of a material variant during the SO configuration is V_T459K-KONFI and value must be either * or +
Hint: A quick check can be done In the SO entry: go to the procurement tab and replace your requirement type by KEL, you'll see that configuration is "open"
Hope this helps
Iñaki
Edited by: InakiGonzalez on May 11, 2009 8:08 PM
Edited by: InakiGonzalez on May 11, 2009 8:15 PM

Sales Contract with Material Variant at Sales Order

We are producing fabric and using make to order in SAP. Our customer give us a commitment with qty and a fixed price for certain fabric in advance, then later they release order to us with specific qty per color. We want to use Sales Contract for the customer commitment and sales order when the customer release the order with color qty to us. We are putting color in the sales order in the material variant. However we are facing the following problem:
1. Let say we have a contract 1 with 100,000 yds of material A.
2. then we have a sales order 2 of 20,000 yds of material A with color Blue refering to contract1.
3. Somehow our factory over produced Material A color blue total 25,000 yds.
4. Then we have another sales order 3 of 5,000 yds of material A with color RED referring to contract 1.
5. MRP does not create plan order for RED material A because it is showing customer stock 25,000 with contract 1 and 20,000 consume by sales order 2 and 5,000 extra. however these 5,000 extra is blue is not red and cannot fulfill sales order 3.
Any idea how to solve this problem?
Tks,
Calvin Ngan

Hi Calvin,
I think if you define your material as configurable, it can solve your problem.
A car, for example, has a large number of options that need to be described wheras the order is created only at a model and variant level. Then you define values for characteristics, to allow you to select specific options, such as 'black' for paint.
So in your case you need to define characteristics of colour(or texture or thickness) or whatever differentiates each output and add optins for each of them.
These are asked for and stored both in your reciepts(stocks, Prod. orders, POs etc) and in your requirements(SO etc). Also MRP will differentiate between each characteristics while planning.
Hope this helps.
Thanks & Regards
Santanu Dawn

Material variants via LSMW

Similar Messages

Maybe you are looking for