Use of production versions

Dear Masters,
I have two BOM's for one material.I have created production versions for the same.
1.I want to create two production orders using two BOM's? How to create ?
Also how we can use the production versions at the time of creting production orders using MD02 & MD04?We have Make To Stock strategy.
Thanks & Regards,
Ram Kulkarni

Hi Ram,
if u create production order by manullay, u can select production version manuulay by doing following settings.
1. Goto OPL8 define production selection = Manual selection for your ordre type/plant combination
2. Define Bom selection  method =   2 or 3  by production version.
while creating production order(Co01) system will ask u to select production version
For MRP run,
system always select first  valid production version by default. Here u can define lotsize to select production version. And another way is u can define Quta arragement inthat u can define percentage quota for each production version.
while creating production order from planned order (MD04) system will copy the production version from the planned order.
regards
pradeep

Similar Messages

  • Costing variant and production version

    We have two costing variants "C" (used to create current cost estimates) and "F" (Used to create Future cost estimate). All of the production versions in the system have a validity date of 9999. Is there a way to tell the system to use one production version when costing using Variant C and another version when costing is done using variant F.
    Or if that is not possibel than how do we use one production version in 2011 while recosting current standards and another production version in 2012. (Remember the production version that we are using currently in 2011 has a validity date of 9999)
    Regards

    Hi
    In your Costing Variant - You have a tab callled "Qty Structure Control".... Here you can specify BOM Determination and Routing Selection id.... i.e. If the BOM / Routing attached to the prod version can be assigned a specific BOM Determination Class and Routing Selection id, it can work
    OR ELSE
    While doing CK11N, you can manually specify the Prod Version in the "Qty Struct" Tab..... Create an LSMW for CK11N and you can do a mass costing like CK40N.... CK40N does not have this option of specifying Prod Version
    I would prefer 2nd option
    Br, Ajay M

  • Which SAP Product version to assign to a Logical Component in SMSY (SOLMAN)

    Dear SAP Colleagues,
    In our SAP environment, we do have 2 versions of ERP systems :
    1. CON - SIF - CDP systems are 'SAP ERP Central Component 5.0' product version.
    2. CDD - CDT - CDP systems are 'SAP ECC 6.0' product version.
    Question :
    When I want to assign these systems to a Z_LOGICAL_COMPONENTS, which product version do I have to choose ?
    Example for CON - SIF - CDP systems :
    1. They are 'SAP ERP Central Component 5.0' product version.
    2. In SMSY in our SOLMAN system, logical component are created using
        'SAP ECC 5.0' product version.
    Example for CDD - CDT - CDP systems :
    1. They are 'SAP ECC 6.0' product version.
    2. In SMSY in our SOLMAN system, logical component are created using
       'SAP ECC 6.0' product version.
    Question :
    What about 'SAP ERP 2004' and 'SAP ERP 6.0' product version ?
    In which case must I use this product version to assign CON-SIF-CPS
    or CDD-CDT-CDP to new Logical components ?
    Are they OSS Note or any matrix which give me the right product version to choose ?
    I have heard that 'SAP ECC x.x' product version should not used any longer ?
    Thanks
    Best regards
    P.C

    Hi,
    Read the following document, the mapping for systems and component versions is described in here:
    https://websmp202.sap-ag.de/~sapdownload/011000358700000074392009E/SP18_SolMan_Setup_Guide_V2.pdf
    For ECC 6.0 you should select ERP 6.0
    regards,
    Jaap

  • Quality plan as per production version

    Hi SAP gurus,
    My client has multiple Production versions and they want to use different Quality plan as per version , how  I can map this process in SAP.
    I tired using in production version by putting Qualiity plan instaed of routing,  Inpection lot is created but when it come for the production order it was asking for the routing / or operation generation.
    As few specfication of Quality plan is different , that is the reason Plan has to be specific to PV.
    Thanks in advance.

    Hi
    Even if you create a Inspection plan you might have observed in the production version you have to specify the Routing.
    Reason is syem will check the routing for cost collector in production order.
    what you can do is may be you can carry out inprocess inspection with routing & specify the char in the task list
    or
    You may have to go for userexit while selection of the task list you will select the appropriate task list with appropraite prod version
    Also if you creat two inspection plan with two gr counters & do not tick on "Auto Assign" in the QM view,
    System will create a lot of 04 with CRTD status.
    In QA02 you can go & manually attach the relevent task list.
    What you can do is create a Group with name of "prod version" itself.This will ease the attaching of the tak list to the the lot.
    I hope this will add some value.
    Regards
    Sujit

  • Production Version in costing run.

    Dear all,
    We are using 3 production versions for a single material. We have made costing run for all the 3 versions. But we found the system considering the last production version in the costing run. we need all the three production versions to be used ,so kindly suggest how to go with .
    When we run CK24, there is no option to select the version. Even if we have the option, please tell us how the cost will get updated in the material master for all the 3 production versions.
    Thanks & Regards,
    A.Anandarajan.

    Hi,
    I think you want to have a costing, which considers a mix of different ways of producing a product. Here you want to have a mix of the 2 production versions. To do this, you need to use use what we call 'mixed costing'. Here you can define a 'mix' of
    different ways to build a product. In abstract X% of method A and Y% percent method B. What I called 'method A' or method 'B' is what you now call a prod.version. In SAP mixed costing it is called 'Procurement Alternative'. I think this is the right tool to solve your problems.
    For further documentation see:
    http://help.sap.com/saphelp_erp60_sp/helpdata/en//7e/cb938143a311d189ee0000e81ddfac/frameset.htm
    The method you are using now 'costing with prod.version A' and 'costing with prod.version B' lets the last costing be the winner, because the last one overwrites the results of the predecessor.
    regards
    Waman

  • Selecting New Production version while Splitting a Production Order

    Hi SAP Gurus,
    Is there any option of selecting a New Production Version for a split Production Order?
    I have a production Order with three operations 10.20 and 30. This production Order is curently using the Production Version 001. Now , i have split the production order at Operation 30 and want to select new production Version 002 for the same.
    Can you please let me know if this is possible?

    Hi Sandeep,
       If you don't mind can you please let me know for what purpose you want to assign a new production version to production order after splitting at operation 30?
       To quickly recap, Production version is used if you have alternative BOM or alternative routings for a material. Based on Production Version that you have assigned in Material Master - MRP screen, your Routing and BOM details are selected.
        So how is this Production Version 002 different from Production Version 001 - is it in terms of routing or bom?
      With Best Regards,
    Srinivas

  • ISSUE:regarding production version tab of MRP4 of  data transfer using BD10

    Hi all,
    This is regarding production version tab of MRP4 of  data transfer using ALE idoc (BD10).
    When i transfer the data using BD10 the production version is received at receiving end through segment
    but not created in MRP4 view tab.An error is coming as-
    "You wanted to maintain the master record of the material AB_06.04.09(2). However, it is already being processed by the user EBGABAP and is therefore locked."
    I logged in as-EBGABAP
    Please help me resolve the issue.
    Thanks
    Edited by: sanu debu on May 6, 2009 11:08 AM
    Edited by: sanu debu on May 6, 2009 11:09 AM
    Edited by: sanu debu on May 6, 2009 11:11 AM

    >
    sanu debu wrote:
    > Hi,
    > I have to upload production version tab data of  MRP4 view(MM01).Please suggest a function  moduleor bapi  for the same.
    >
    > Thanks.
    >
    > Edited by: sanu debu on May 6, 2009 3:24 PM
    BAPI_MATERIAL_SAVEDATA can be used, populate the respective fields in input parameter PLANTDATA

  • If I don't have a previous version of an adobe product, but the only ones available of older editions are updates, can I use the update version to install the software?

    Dear Adobe,
    I've got older systems, ones that can't handle CS6, and a budget too low to purchase a new system and your software even with a student discount. Is there any way to use an update version? I wish that all of the "Creative Suite[s] products [would] continue to be available for sale via ESD on Adobe.com"(Adobe)*, or at least most of them. I understand the need to update, and that the industry is difficult with competitors, but I wish that all of your software versions were aimed towards 32 bit systems too. There are plenty that can keep up with the operating System updates, and I only wish that you would have kept at least CS5 on support instead of shutting it down. So, if you won't accept support of older products, can you help me with this? Or is this beyond any of the software contracts that is in the company's power? I appreciate any assistance in this matter.
    *CS6 FAQ

    You can only buy CS6 and CC. Otherwise you will have to find someone willing to part with his license and run a license transfer. Though, quite frankly this doesn't really make sense. You can buy cheap laptops withe a suitable 64bit version of Windows 7/ 8 for 300 Euros. The money saved could easily be invested in a CC student plan rather than possibly trying to find an overpriced older version with the risk of getting scammed... Otherwise you can use the trials of course, but that's about it.
    Mylenium

  • Problem using production version of SQL Server 2005 JDBC drivers

    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    Sabrina
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

    SabrinaL wrote:
    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    SabrinaHi. Have you done all the XA-related install for the new MS driver? (put the XA
    dll in the DBMS environment etc)? Is your DBMS on a 32-bit machine or 64-bit machine?
    Does the driver present a dll for each of those? You can also get good JDBC help
    from MS via their microsoft.public.sqlserver.jdbcdriver newsgroup.
    Joe Weinstein at BEA
    >
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

  • Production version is not getting created using ALE-IDOC

    Hi all,
    Am using BD10 to transfer the material from sending to receving system.All the views are geting sent successfuly accept the production version tab data of MRP4 view.The segment is available in the standard IDOC.But prodction TAB  is not getting created at receving system .Please help to resolve this issue.
    Thank you.

    Hi Sanu,
    BD10 Send Material..
    the reason might be Production tab is not created is the segment is not a mandatory..
    and the data is not populating for that fields.
    if the segment is not madatorty and data is not available for the fields in the segment ..the prodction TAB  will not be created ..
    Regards,
    Prabhudas

  • Production version with status " locked for any use" being considered

    Dear All,
    while creating integration model for PDS , materials with production version locked for any use are being considered. Can any body put some light on it.
    My requirement is that in creation of integration model it should not take production version which are locked for use.
    Regards
    Arun Negi

    Check OSS Note 854561 - PDS does not recognize any locked production version in R/3
    "Symptom
    If a production version is locked in the R/3 System, this change is not transferred to the related production data structure (PDS) in APO. The PDS is therefore still used as a source in APO in the plan explosion. This causes errors during planning and results in terminations when an order is converted and subsequently transferred to the R/3 system."
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=854561
    Manish
    Edited by: Manish Kumar Rathi on Oct 10, 2008 11:46 AM

  • Can I use a student version adobe CS3 product to qualify for the $29.00 rate for the cloud?

    Can I use a student version adobe CS3 product to qualify for the $29.00 rate for the cloud?

    Hi Mariofsanders
    An educational version of the software does not qualify for the upgrade price of the Creative Cloud plans.
    Please see this link for the current plans.
    https://creative.adobe.com/plans
    Thanks
    Scott

  • Is it Necessary to create production version if  using master recipe

    our industry Process industry
    we are using Master recipe for Production
    is it necessary to create production version

    Hi Krishna,
    Production version is essential to mantain if you have a PP-PI industry scenario.
    However, if you have not mantained it, you can still create a process order. Process order first searches for the production version (automatically/ manually) depending on the configuration settings.
    If you have not mantained it, system would throw a SAP standard information message, "Material XXXXX: Production Version not mantained".
    If system is not able to select valid master recipe / version.  it would look for default values for operation in the master recipe settings and would try to create a operation.
    Please see the following link:
    http://help.sap.com/saphelp_470/helpdata/en/ee/641c181bed11d29bfe080009b31c68/content.htm
    Method for Selecting Alternative Bills of Material
    Indicator determining the selection of the alternative BOM when requirements are exploded in material requirements planning.
    Use
    With Selection by order quantity, the system chooses the alternative BOM into whose lot size range the order quantity falls. The lot size range and area of validity of the BOM apply.
    With Selection by explosion date, the system chooses the alternative BOM into whose area of validity the date falls according to the setting BOM via dates.
    With Selection by production version, the system chooses the alternative BOM defined in the valid production version. The lot size range and area of validity of the production version apply.
    With Selection only by production version, the system chooses the alternative BOM defined in the valid production version. The lot size range and area of validity of the production version apply.
    If no production version is found, no production orders or process orders can be created.
    BR
    Rahul

  • Use of different production versions for MRP and costing

    Dear PP Gurus ,
    We have a scenario in which there are multiple production versions for a particular product .The MRP run as welll as costing run considers only the production version 0001.
    We would like the system to consider different production versions for MRP and costing ..that is 0001 for MRP and 0005 for costing .
    Is this possible ... if yes ...Kindly suggest the config and master settings for this to happen .
    Ram ~

    Dear Ramakrishna,
    For doing the costing for a specific production version use CK11N,under quantity structure tab key you
    can assign the prod.version which is to be used for costing purpose.
    While taking MRP if you want to consider the particular Prod.version,assign the demand to the
    correct prod.version under schedule line tab in MD61.
    Otherwise the system always picksup the first prod.version for MRP.
    One more alternative is you have to lock the other prod.versions if you want the system to consider a
    particular prod.version.
    Check and revert back.
    Regards
    Mangalraj.S

  • Creation of inspection lot 04 depending on production version

    Hi Experts,
    could you tell me if it is possible to create a Good Receipt inspection (lot origin 04) depending on the production version used ?
    My material has 2 production versions:
    0001 - production with process order
    0002 - production with repetitve manufacturing
    When I do a GR on process order, I do not want to create an inspection lot 04.
    When I do a GR on product cost collector, I want to create an inspection lot 04.
    As I have entered inspection types in material master data, I do not know how to do the distinction ?
    Thanks in advance for your help
    Best regards
    Amaury

    Hi
    Check user exit
    QBCK0003 |Extended QM check for goods receipt
    Regards
    Sujit

Maybe you are looking for