Skip to Content

To avoide duplicates in Material Master

Dear Gurus,

I am facing problem that we have plants some are under projects and others are running , now we have two material codes (with different material types)for same material for project and running plants , as their valuation class is different for O&M and for projects , this scenario is creating lot of duplicay in material master , can you please guide me to avoid this type of material duplicates in system

Thanks & regards

Akshay

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 03, 2013 at 08:42 AM

    It is still best to have just one material code across multiple plants for the same material. You can start an initiative to clean up all the redundant material codes and reconcile them under a single code. Of course, you have to assess the impact in your organization if you change codes since this would definitely affect your operations (e.g. BOM maintenance, Purchasing, Production, etc.)

    In your configuration, include all possible valuation classes in the assigned material type.If you need different valuation classes for different plants for the same material, you can still do so via Accounting view maintenance in the material master.

    Good luck! Hope this helps.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Akshay kukde

      if this is the case, i suggest you look into the option of using split valuation for your materials. this way, you can maintain a single material code for an item in the same plant but different valuation classes depending on the valuation type.

      you can have two valuation types 1) project and 2) operations. then from there, you can assign your valuation classes that you want.

      test this first, i think this would address your concern.

  • Posted on Jan 03, 2013 at 01:31 PM

    Hi,

    Better prevent creation of duplicate material master record and do ABAP works necessary in either one enhacement with structure STEXT - In short text(s) of newly created material should be found a validation!
    1.Check or try use Enhancement: MGA00001, user exit: EXIT_SAPLMGMU_001
    OR
    2.Can use BADI:BADI_MATERIAL_CHECK.

    Regarding material using in both plants and you need to re-design your process.
    How your material master numbering is design---is it internal or external?
    As your same material used in both plants,posting needed to separate G/L accounts and want single material code,so better use valuation grouping code concept.
    Use different valuation grouping codes where you can have different G/L posting with respect to each plant for same material.

    Refer detailed discussion on valuation grouping code concept where posting of different G/L accounts with respect to plant for same material code:

    http://scn.sap.com/thread/1899294

    Regards,

    Biju K

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi,

      Your concept of designing and creating two plants are wrong. As all activities happening in one place, you could have design or go for creation of ONE PLANT only.


      With regarding to your above explanation and if it true –such as same material code using in project phase and same material code using in production process as Operation & maintenance in same location of manufacturing process.

      Now go for following process:
      1.Go for creation of ONE PLANT only as P100
      2.Create ONE material type as ZPPM
      3.Create ONE valuation class 3015
      4.Create ONE account category reference Z015 and link material type ZPPM to valuation class 3015 through account category reference Z015
      5.Create purchase order document types ZPRO for project and ZNB for General Procurement
      6.Create a material Code MMM1 with material type ZPPM
      7.Create Purchase Order ZPRO with material Code MMM1 for project and enter WBS element and G/L account
      8.Do goods receipt for project purchase order(ZPRO)
      9.Create Purchase Order ZNB with material Code MMM1
      10.Do goods receipt(MIGO) for General Procurement purchase order (ZNB) and material MMM1 will post to Company Warehouse Stock
      11.Do goods issue(MB1A), the material MMM1 from Company Warehouse Stock to production process as Operation & maintenance with 201 movement type by entering cost center for Operation & maintenance

      Regards,

      Biju K

  • Posted on Jan 04, 2013 at 09:35 AM

    Normally one material can be

    - purchased as a standard material to the warehouse

    - or e.g. with account assignment K where no stock is added in warehouse and costs are posted to a cost center

    - or you purchase that material to a project, where the costs are going to the project

    Depending on the setup of the project you can have project stock inventory managed, or you only collect the costs for the materials and do not create stock

    As you material is a NLAG (non-inventoried item) after the project, I assume that it is not inventoried during the project too) so you are just collecting the costs at the project.

    In SAP standard delivery the NLAG material type is without accounting views. But it is possible to add accounting views to enable auto account determination even for account assigned purchases.

    Can you please explain what error you actually have if you use 1 material master during the project and after the project?

    And can you please clarify if you manage inventory for project stock

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi,

      I am not sure and your design of entire business system is wrong with having a plant 1000 having different valuation class for same material!

      As you said- initially your plant -1000 is under project but you should have that project under a plant! Repeating again,you can have only one material code which is assigned with only one valution class and creates purchase order for following process:
      1.For project
      Create purchase order for project with that material code by having account assignment catogory P by entering G/L account with WBS element

      2. Create purchase order for production process with that material code by having account assignment catogory K by entering G/L account with Cost center of "Operation & maintenance"

      OR

      If material with material code is already received in project and want the same material to sends for consumption to "Operation & maintenance".Better go for Stock integration or Stock Re-integration process where bring stock from project to company stock and then issue material stock to "Operation & maintenance".

      Refer detail for Stock integration or Stock Re-integration process

      http://scn.sap.com/thread/3233077

      Regards,

      Biju K

  • author's profile photo Former Member
    Former Member
    Posted on Jan 03, 2013 at 08:50 AM

    Currently one of my client also facing the same problems.

    How I suggest them is, create 1 table with only 1 field, set the field to unique.

    So before creating a new material codes, we ask clients to enter their code to the table, if they manage to do so, means there is no duplicates for that material code.

    This kinda ancient, but it works.

    PS: I also wanna know how to do this in more effective way if there is any way different than me.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.