Production version issue.

Dear Guru's,
I have created two version in material master.
also I have changed in "opl8"{ production version = Manual selection of production version}
but still system is not asking me for production version at the time of creation of production order.
system is asking me routing only
now I am selecting version from function>read master data ( production version).
please sugest me wat i have to do for pop up of production version at the time of production order creation
and also system is not giving me any request no. at the time of save the changes in IMG.what will be issue
Nilesh

Dear,
please see that PV is applicable in terms of lot size, dates and status
if both
PV are valid wityh respect to the above then only upi will get the pop up for PV selection.
MRP4 setting is alosm required.

Similar Messages

MFPR - Processing Inspection Lots for Production versions issue

Hello,
User are not able to seeing line item to create inspection lot for a specific part number.
I checked inspection set up in material master, rate routing, and compared with similar part numbers.It all looks good to me.
Any help would be greatly appreciated!!
Regards,
Owais

In REM Inspection lot for Inprocess is generated for header material for which you actually define "production version".
Line items can not be seen in MFPR.

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

How to add production Version field in COOIS to selection options?

Dear Experts,
Need your suggestion for below issue raised by client.
1) As per client, he was running COOIS with the selection option of a production version. But currently he is not able to see this selection while executing a COOIS t-code.-----> Kindly guide me on its possibilities & necesary checks.
2) If I want to correct it & want to add Production Version field in COOIS report what steps I should take?
Need all your valuable guidence to resolve above issue.
Thanks & Regards,
Mehul

Hello Vivek,
Really thanks for your mail. Please see below comments-
1) I checked the transaction COOIS & also told user to select Production Version after executing the report by giving Plant code & dates. But user asking for this field before execution.
As per your suggestion I checked in Header level of first screen but its not showing me also.
2) I am using ECC6.0 version
3) One finding from my side- This is I am checking only selecting Production Orders. But when I am selecting only Planned order then Production version can be seen in first screen under Repetitive Mfg. section.
so kindly tell me why this not showing when Production order selected?
Thanks in Advance for your help.
Regards,
Mehul

REM Product cost collectors and Production version

Hi All,
Can some one pls let me know
What are the product cost collectors in REM and how to create the product cost collectors ?
What is the production version and the difference between production version and controlling version?
Thanks & Regards,
Bujji

Dear Bujji,
A product cost collector is a cost object in Product Cost by Period that collects the periodic actual costs incurred in the production of a material. It can be created in txn KKF6N.
[Product Cosr Collector|http://help.sap.com/saphelp_47x200/helpdata/EN/08/77ba810a1611d3a6b900104b55d538/frameset.htm]
[Product Cost Collectors: Collective Entry for Repetitive Manufacturing |http://help.sap.com/saphelp_47x200/helpdata/EN/08/77ba810a1611d3a6b900104b55d538/frameset.htm]
A production version determines the various production techniques that can be used to produce a material. It defines the following information:
Alternative BOM for a BOM explosion
Task list type, task list group, and group counter for assignment to task lists
Lot-size restrictions and period of validity
A material can have one or more production versions.
It can be defined in the Material Master (txn MM02) in one of the following views:
MRP 4
Work Scheduling
Costing 1
The costing version is a different issue. It is a costing parameter and is used to save several cost estimates for the same material, with the same costing variant and the same costing date (e.g. in oder to cost the material several times with minor changes without creating new costing variants).
BR,
Antje

BDC Error in transaction C223 - production version mass maintenance

Hi Experts,
         I have created a BDC recording for Tcode - C223. In my case for each plant and material there is a production version. if production version already exists, then we have to modify the record, if no record already exists, then we have to create and have to press save. When i was recording the transaction, i have changed the existing record and pressed saved, it has given the message record saved successfully.
          But in BDC when i was running the same recording, it says function code not possible. I was giving my code, please let me know how to solve the issue.
PERFORM bdc_dynpro      USING 'SAPLCMFV' '1000'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=ENTE'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'MKAL-WERKS'.
    PERFORM bdc_field       USING 'MKAL-WERKS'
                                  wa_record-werks.
    PERFORM bdc_field       USING 'MKAL-MATNR'
                                  wa_record-matnr.
    PERFORM bdc_dynpro      USING 'SAPLCMFV' '1000'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=ENTE'.
    PERFORM bdc_field       USING 'MKAL-WERKS'
                                  wa_record-werks.
    PERFORM bdc_field       USING 'MKAL-MATNR'
                                  wa_record-matnr.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'MKAL_EXPAND-PRVBE(01)'.
    PERFORM bdc_field       USING 'MKAL_EXPAND-MATNR(01)'
                                  wa_record-matnr.
    PERFORM bdc_field       USING 'MKAL_EXPAND-VERID(01)'
                                  c_verid.
    PERFORM bdc_field       USING 'MKAL_EXPAND-TEXT1(01)'
                                  wa_record-text1.
    DATA l_adatu2(10) TYPE c.
    CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
      EXPORTING
        date_internal = l_adatu
      IMPORTING
        date_external = l_adatu2.
    IF sy-subrc <> 0.
    ENDIF.
    IF l_adatu IS INITIAL.
      PERFORM bdc_field       USING 'MKAL_EXPAND-ADATU(01)'
                                    sy-datum.
    ELSE .
      PERFORM bdc_field USING 'MKAL_EXPAND-ADATU(01)'
                                  l_adatu2.
    ENDIF.
    PERFORM bdc_field       USING 'MKAL_EXPAND-BDATU(01)'
                                  c_date1.
    PERFORM bdc_field       USING 'MKAL_EXPAND-STLAL(01)'
                                  c_1.
    PERFORM bdc_field       USING 'MKAL_EXPAND-STLAN(01)'
                                  c_1.
    PERFORM bdc_field       USING 'MKAL_EXPAND-PLNNR(01)'
                                  wa_record-plnnr.
    PERFORM bdc_field       USING 'MKAL_EXPAND-ALNAL(01)'
                                  wa_record-alnal.
    PERFORM bdc_field       USING 'MKAL_EXPAND-PLNTY(01)'
                                  wa_record-plnty.
    PERFORM bdc_field       USING 'MKAL_EXPAND-SERKZ(01)'
                                  c_x.
    PERFORM bdc_field       USING 'MKAL_EXPAND-MDV01(01)'
                                  wa_record-mdv01.
    PERFORM bdc_field       USING 'MKAL_EXPAND-ALORT(01)'
                                  wa_record-alort.
    PERFORM bdc_field       USING 'MKAL_EXPAND-ELPRO(01)'
                                  wa_record-elpro.
    PERFORM bdc_field       USING 'MKAL_EXPAND-PRVBE(01)'
                                  wa_record-prvbe.
    PERFORM bdc_dynpro      USING 'SAPLCMFV' '1000'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=SAVE'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'MKAL-WERKS'.
    PERFORM bdc_field       USING 'MKAL-WERKS'
                                  wa_record-werks.
    PERFORM bdc_field       USING 'MKAL-MATNR'
                                  wa_record-matnr.
    CALL TRANSACTION 'C223' USING it_bdcdata
                                  MODE 'A'
                                  UPDATE 'A'
                       MESSAGES INTO tmess_mtab.
my record was like this
1038        37581     MG CY/CC WINTER HB ENTREE   1       50084122     2     N     M100     0200     0200     SA02
Thanks & Regards,
Poorna.
Edited by: poorna on May 10, 2009 4:52 PM

Thanks

An error has occurred in the script on this page ( Crystal Reports Product Version - 11.5.7.770)

Post Author: sampolo
CA Forum: Crystal Reports
I am running Crystal Reports Product Version - 11.5.7.770, On MS windows Server 2003 R2 standard Edition SP2
But every time I launch Crystal Reports I am getting the following error message..
An error has occurred in the script on this page
Line: 360
Char: 30
Error: Unspecified error.
Code: 0
URL: http://www.businessobjects.com/products/reporting/crystalreports/start/designer/default.asp
Do you want to continue running scripts on this page? YES or No..
========================
I have try this following fix with no success...can someone help?
http://support.microsoft.com/kb/895608
http://technicalsupport.businessobjects.com/cs/forums/permalink/606/5889/ShowThread.aspx

Post Author: sampolo
CA Forum: Crystal Reports
Well I found a temporary fix for this issue. I put the http://www.businessobjects.com/ as a trusted site in IE!!
First, get the URL of the site to trust. For example, " http://www.businessobjects.com/
.Next, Click on the "Tools" menu and select "Internet Options". Click on the "Security" tab.
Click on the green circle with a white check marked "Trusted Sites". In the space provided, enter the URL of the site (you'll probably want to uncheck the box requiring SSL, which is a high-security link, for all sites). Click the "Add" button. Continue entering sites until you have them all entered, then click OK as needed. If you find another trusted site later, simply go back to this menu item and enter the data.

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

SAP ECC 6.0 Software component Versions or Product versions in XI (SLD)

Hi All,
please, let me know the solution for this problem,
Curently we r using PI 7.0 SPS 14 kernal Version 179.
Unable to find out SAP ECC 6.0 Software component Version or (Product version) in SAP XI 7.0 SLD.
how to solve this issue....
Advace thanks.
Mahesh

Hi Volkar,
I am doing Plant driven procurement service enablement scenario by using XI 7.0, for this,
we are integrating MM & SRM SUS Through XI 7.0 (MM -- XI-- SRM SUS).
For doing this Scenario,
1. Downloaded XI Content for SRM
2. Imported XI Content into the IR
3.After importing, Plan_Driven_Procurement_SupplierEnablement Scenario was enabled.
Here, MM side SWCV is R/3 4.6 is available by default. but in my case i need to change to ECC 6.0(bcoz,currently we r using ECC 6.0 version )
In SLD, there is no ECC 6.0 version.
So, how to solve this issue.
Thanks in Advance.
Mahesh

MRP Run with production version.

Hi Experts;
I am working as a member of a SAP implementation supporting team. The client wants to run MRP with alternative BOM, not with the 1st BOM. As a solution for the requirement i created production versions and assigned to MD61 schedule line tab. It is working properly.
But the user maintain some quantity as a safety stock for finished materials also. To cover the safety stock requirement, system create planned orders with the 1st BOM, not the production version.Already i have maintained the selection method "3" in material master.
Is it possible to cover safety stock with alternative BOM.
Please help..
Thanks,
Malka

Hello Malka,
For your issue,,
As per other expert suggested you can block the first production version but if in future you want use first production then,,
In these case you maintain production version in many way
Ex.
1. Lot size .(if production version using for specific lot)
    Maintain the Lot for both production version, so Production version 1 lot completed system take       second production version.
2. Production version validity date (If production version using for specific period )
    In this case after completion of 1. Production version period system take second one
3. Manually selection of production version (If multiple production version and all have same condition)
    Whenever you convert the planned order to production order, one pop up come and ask for                manually selection for Production version, for this you go to OPL8 and select the Manually                production version
I hope this information cover your all requirement, No need to go with quota arrangement
Still you want know about the Quota arrangement, Please create new thread so other expert also provide their view
Regards
Umesh Mali

Product Version SAP ERP 6.0 Missing from solman 7.0

Hi All,
I have installed an ECC6 system and now i need to configure the solution manager and download the support packs
and xml file for EHP4 upgrade. I have done this before where in i configure the new system in SMSY as SAP ERP 6.0
and then configure maintenance optimizer and it gives me the option of Enhancement Package Installation.
However now in the current solution manager i dont see the product version SAP ERP 6.0 when im clicking
trying to creating a new system.
Our Solman version is 7.0 . I tried creating my new system under SAP ERP EHP as ehp version 1 and used maintenace
optimizer but it does not give me the option of EHP package installation. Can any one let me know how to address this
issue??
Regards,
Ershad Ahmed.

Hi,
Goto Tcode SMSY
1. Under Landscape Components --> Product Systems --> Select ERP --> Under that select your system ID and click on it,
Goto --> Header Data on your right side, change the Product Version to SAP ERP 6.0 and SAVE.
2. Goto System Groups and Logical Components --> Logical Components --> SAP ERP --> Create NEW Logical Component for your ECC system under this component and select Production version as SAP ERP 6.0 & assign ur system then SAVE.
3. Goto System Groups and Logical Components --> Solution Landscapes-Operations --> Select your system landscape and REMOVE your ECC systen form the Solution and SAVE.
4. Goto System Groups and Logical Components --> Solution Landscapes-Operations --> Select your system landscape and ADD your ECC system form the Solution and SAVE.
Regards
Kannan.K

Install of CE 7.1 productive version

Hi,
We are trying to install Composite Environment 7.1 Productive Version, and we followed the links that are in every master guides, but they don´t appear in the service marketplace. We have a S-user, so we don´t understand why is this happening. Is there another link to download the CE 7.1 ?
This is the link that we don´t find:
Downloads-> SAP Installations & Upgrades -> Entry by Application Group -> SAP NetWeaver -> SAP NETWEAVER -> SAP NETWEAVER CE 7.1 -> Installation ->
Thanks in advance,
Pablo.

I opened an OSS, because the problem was in the SAP Marketplace. The link wasn´t there.
This is the answer provided by SAP:
Hello, issue was solved. changes may take a few hours
to become effective. Please retry later and close the message.
Best regards
Problem Solved.
Thanks,
Pablo.

No Automatic Dispatching Of Planned Order to new Production Version

Dear Sir,
When rescheduling an operation from one line to another, the system
checks whether a production version exists for the material to be
produced that contains the new production line as the preferred work
center. If such a production version is found, this version is taken
over into the planned order. The planned order is scheduled again based
on the production version.
The second function allows you to automatically search for an
alternative work center in the case of a capacity overload of a work
center, and to dispatch the operations to it. The predefined
prioritization of the alternative work centers is considered in this
case.
The indicator Reschedule with production version must be set in the
strategy profile.
My issue is sytem does not making automatic Dispatch to the second
Production version for the material at the time of insufficient capacity
Best Regards
Rami Abd El Fattah Mohamed,PPQM Functional & Technical Application
Consultant

In the dispatching control u can remove operation date check indicator and regarding the termination indicator SAP help says"
"if you have not set this indicator then dispatching is not terminated but carried out without taking the production version into account. That means that the planned order is scheduled with the old standard values and the formulas from the new work center and dispatched to the new line."
Please check if it works now.
thanks

Error as Production Version = or repetitive mfg indicator cannot be deleted

Hi Guys,
Please let me know before I delete the Production version for a material what are all the steps I need to carryout.
Requesting to explain with detailed steps/Points.
Cheers,
Kumar.S

Dear Kumar,
1.First check whether is there any planned order assigned with this production version in MD04 or else in MD16.
2.Either confirm these planned orders using T COde MFBF or else delete these orders in MD16 or else in MD12.
3.Also clear the reprocessing list present in MF47.
4.Do the variance calculation and settlement (KO88)
4.Now here this issue can handled in 2 ways,one is set the valid to date as the system's date to the production version.
5.If you want to delete the production version,then the cut off period has to be set by the CO part and proceed.
Check these links,.
Re: Delete Production version
Re: production version
Regards
S Mangalraj

Production version issue.

Similar Messages

Maybe you are looking for