Production Version of Co Product

Hi,
I have got one main product and one co product. Main product has got many Production Version based on lot size. When I do costing for the main product ,it picks the right PV based on the lot size. But in case of co product costing it picks the first PV of main product only irrespective of lot size. Why ?
Shahnawaz

>
Shahnawaz Farooqui wrote:
> Hi ,
> I am not maintaining separate BOM for co product . As mentioned in my question it is when I am doing the costing for Co product it is picking the wrong PV of main Product.
>
> Shahnawaz
Shahnawaz,
Why you are doing seperate costing for CO-Product, when you do costing for main product it should do cost roll-up for the co-product also. Please check
Regards,
Prasobh

Similar Messages

Change Production version during creation of Process Order COR1

Hi,
Scenario:
Based on the entered Material, Plant and Order type system need to trigger a popup asking the user to select the Production Version. This should happen before clicking on SAVE button, so that all the values will be populated correctly based on the changed VERID.
I did not find a user exit that enables to change the Production Version (VERID) value. So I thought of displaying the popup in the user exit EXIT_SAPLCOZF_003 which will be triggered before initial screen appears, export the selected value and pass it to a User Exit or BADI where VERID can be changed. But cannot find a user exit to do it.
Please help me find a User Exit or BADI to change the Production Version during creation of Process Order using COR1 transaction before clicking on SAVE button.
Thanks,
Manoj.

Hi Manoj,
So - almost four years later - I saw your post and I saw myself in the very same situation as you did...
I found a solution for those who wants to change the production version of the production order from the sales order creation: create an enhancement in the function module 'MD_VERSION_SELECTION' and you are good to go.

Is there option to assign Production Version in MD62

Hi,
Can any one please help.
I have a HALB Material with 3 Production Versions (with the same Lot Size and Validity Dates)
While creating Planned Indipenmdent requirement (PIR). how can i specify what Production version to be used here and as well for MRP run.
Can any one please guide me.
Thanks and Regards
Khadeer

Hi,
Goto MD62
Execute the report
Goto Schedule line tab page
Fallow the menu path
Setting Production version
Enter the Production version required
Save
Check the PV where it is in green colour it should be active with valide date.
Regards,
R.Brahmankar
Edited by: R Brahmankar on Aug 2, 2008 4:34 PM

Production version selection based on Process order type

Hi,
I have the following requirement.
A material is having two production version one is for R&D and one is for regular production. Now two process order types one for R&D and one for regular production. Now during creation of process order if we use order type of R&D then it has to select production version of R&D and if we use order type of regular productionthen it has to select production version of regular production. This selection has to be happened automatically. How this can be configured.
Thanks
Vinamrath.

Dear Kumar,
Assuming the production version selection is automatic in the order type dependent parameters,then during order creation this
can be automated only through validity date of the production version or else by locking the production version manually which
should not get picked or else only through different Lot Size.
Check and revert.
Regards
Mangalraj.S

How to get production version in your contract?

hi all,
I have already maintain multiple production versions for one product, but how can I let it appear in the contract item?
thanks

Hi,
I think I have already answered this one. You can get the curent version either from wwv_usr_menus$ or wwv_modules$
select version from wwv_modules$
where id = <module_id>
and status = 'PRODUCTION'
This gives the version of the current production version.
Thanks
Sharmila

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

How to maintain production version for material and how it will work

Dear Friends,
                      i have created alternative bom for a material , My FG is having two RM1 and RM2. like below,
                FG --->RM1
                FG---->RM2
i created alternative BOM. how it will fetch raw materils from BOM while doing production confimation. what is meant by production version and how to configure that. how it will work
regards
RK

Dear Raja karthik,
1.Production version is a combination of BOM & Routing in Discrete scenario & in REM scenario its a
combination of BOM & Rate routing/Routing.The same can also be created only containing the BOM incase if it is going to be
used for a sub-contracting purchase info record.
2.Production version is a method or technique which's is used to produce a material.
3.A Material may be having one or more than one production version.
4.Production version can be differentiated by using either the validity date or Lot size range.
5.Say For Eg: Prod.Version1 --> Alt BOM1 & Routing1
Prod.Version2---> Alt BOM2 & Routing 1.
6.It has the status Locked and unlock.We can lock it when it is to blocked for any usage purpose.
6.Generally its created using T code MM02,by selecting MRP4 view and clicking on Production version key.
7.It's a master data in REM scenario.
8.Production versions can also be created using T code C223 for more than one material.
9.Planned independent requirements can be created production version specific in MD61.
Regards
Mangalraj.S

Automactic Selection of production Version

Hi.
I have created a material "A"
I maintained in material master's MRP4 view selection method "2"
I have created two production version with same validity period & same lot size "0001" & "0002"
I maintained in order type dependent parameter's masterdata tab in production version column "Automatic production version selection"
Now when i am going to create a process order system is selection production version "0001".
But I want automatic selection of production version "0002".
What setting shall I do?
Regards
Vivek

Dear Vivek,
I maintained in order type dependent parameter's masterdata tab in production version column "Automatic production version selection"
In order type dependent parameters maintain as manual selection
Then system will raise an pop-up to select production version while creating prodiuction order
The above setting is only useful while creating manual production order
If you are converting plan order to production order then above setting will not play any role
System will default take 1st PV
All you can do is you can change manually in plan order
Or if you want system to take automatically in MRP then you need to lock 1st PV
Also refer my reply from this thread
[Alternative BOM selection|Using customer to determine what BOM to use in Production order (tx:CO41);
Regards
Madhu

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

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

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

There is already a transaction for the systems of this product version(MOPZ)

Hello All,
I am trying to configure maintenance optimizer in Solution Manager 7.0
on Windows 2003 server and SQL 2005 server.
I am configuring this for SAP CRM 2007 server.
Created the server, database and system in SMSY
Created Logical Component in TA code SMSY
SM59 connection for SAP-OSS is OK.
S-User is assigned to a User.
Created a solution using TA code solution_manager.
Defined the product version for the solution created in the TA code
solution_manager.
When creating a Maintenance Optimizer transaction, I select the
product version and its logical component in the Plan Maintenance
(Phase) and click on Continue to go to Select Files Phase, I get below
warning:
Information Procedure 8000000130 Saved
Warning: Status was reset by system
Warning: There is already a transaction for the systems of this
product version
I cannot get pass this phase.
I have deleted and recreated the solution, carried out the same
activity again but its giving the same Warning
Warning: Status was reset by system
Warning: There is already a transaction for the systems of this
product version
Any help will be appreciated???
Regards,
Satish.

Hello Ragu,
Thanks for your response.
As of now, we do not have ChaRM in place. Secondly, we use a single customer number.
I would like to let you know that in our landscape we have two CRM server, one ECC sever, one SOLMAN7.0 server.
I tried to configure MOPZ for CRM, ECC, SOLMAN server to download the respective STACKS.
I was successful in configuring CRM and SOLMAN.
But when I tried to configure in ECC, it failed due to RFC erros.
So I deleted the transaction for the ECC system and deleted the system itself in Solution Manager.
Reconfigured the Systems in "SMSY", RFC connections are correctly defined to configure MOPZ between SOLMAN7.0 and ECC6.0.
When I start configuring the MOPZ, I cannot get pass the first phase and this is when I get an error: There is already a transaction for the systems of this product version.
Please let me know if you need further information.
Regards,
Satish.

Error while running February 2014 CU for SharePoint 2010 Foundation: The expected version of the product was not found on the system

I ran SP2 and SP2 for Language Pack successfully before.
Here is how it looks:
Product
Version
Status
Language Pack for SharePoint Foundation 2010 - Portuguese/Português (Brasil)
Installed
Microsoft SharePoint Foundation 2010 1046 Lang Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft SharePoint Foundation 2010 1046 Lang Pack Core
14.0.7015.1000
Installed
Service Pack 2 for Microsoft 2010 Server Language Pack (KB2687462) 64-Bit Edition
14.0.7015.1000
Installed
Language Pack for SharePoint, Project Server and Office Web Apps 2010 - Portuguese/Português (Brasil)
Installed
Microsoft Access Services Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Document Lifecycle Components Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Hotfix for Microsoft Office Server (KB2512800)
14.0.5138.5000
Installed
Microsoft Excel Services Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Excel Web App Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft 2010 Server Language Pack (KB2687462) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft InfoPath Form Services Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Office Server Proof (Portuguese (Brazil)) 2010
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Office Web Apps Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft 2010 Server Language Pack (KB2687462) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Office Web Apps Proof (Portuguese (Brazil)) 2010
14.0.7015.1000
Installed
Service Pack 2 for Microsoft 2010 Server Language Pack (KB2687462) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Office Web Apps Shared Coms Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft 2010 Server Language Pack (KB2687462) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft OMUI Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft 2010 Server Language Pack (KB2687462) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Project Server Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft 2010 Server Language Pack (KB2687462) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Search Server 2010 Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Hotfix for Microsoft Office Server (KB2475878)
14.0.5135.5000
Installed
Microsoft Shared Coms Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft SharePoint Foundation 2010 1046 Lang Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft SharePoint Portal Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Slide Library Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Visio Services Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Web Analytics Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Word Server Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft XMUI Portuguese (Brazil) Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft 2010 Server Language Pack (KB2687462) 64-Bit Edition
14.0.7015.1000
Installed
PerformancePoint Services in SharePoint 1046 Language Pack
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft SharePoint Foundation 2010
Installed
Microsoft SharePoint Foundation 2010
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft SharePoint Foundation 2010 1033 Lang Pack
14.0.4763.1000
Installed
Hotfix for Microsoft SharePoint Foundation 2010 (KB2512804)
14.0.5138.5000
Installed
Microsoft SharePoint Foundation 2010 Core
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft® Search Server 2010 Express
Installed
Microsoft Office Server Proof (Arabic) 2010
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Office Server Proof (English) 2010
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Office Server Proof (French) 2010
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Office Server Proof (German) 2010
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Office Server Proof (Russian) 2010
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Office Server Proof (Spanish) 2010
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Search Server 2010 Core
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Search Server 2010 English Language Pack
14.0.4763.1000
Installed
Hotfix for Microsoft Office Server (KB2475878)
14.0.5135.5000
Installed
Microsoft Search Server 2010 Express
14.0.4763.1000
Installed
Microsoft Shared Components
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Shared Coms English Language Pack
14.0.4763.1000
Installed
Microsoft SharePoint Foundation 2010 1033 Lang Pack
14.0.4763.1000
Installed
Hotfix for Microsoft SharePoint Foundation 2010 (KB2512804)
14.0.5138.5000
Installed
Microsoft SharePoint Foundation 2010 Core
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
Microsoft Web Analytics English Language Pack
14.0.4763.1000
Installed
Microsoft Web Analytics Web Front End Components
14.0.7015.1000
Installed
Service Pack 2 for Microsoft SharePoint 2010 (KB2687453) 64-Bit Edition
14.0.7015.1000
Installed
However when I try to run February CU or December CU I get the error:
The expected version of the product was not found on the system
it's possible that I messed up because
I think I installed a SharePoint Server Service Pack 2 in a SharePoint Foundation Farm.
these are the files I ran:
1 - SP2 pt-br
oserversp2010-kb2687453-fullfile-x64-pt-br
2 - SP2 for Language Pack pt-br:
oslpksp2010-kb2687462-fullfile-x64-pt-br
3 - ran configuration wizard (had na error message the first time and success in the second try)
4 - December CU or February CU:
Download SharePoint Foundation 2010 February 2014 CU
The expected version of the product was not found on the system
In the first step I think I should have installed
wsssp2010-kb2687464-fullfile-x64-pt-br
Now I try to runthis and I get:
The update is already installed on the system.
Hopefully this is a QA Environment but it would be a pain to start over.
Any suggestion?
Thanks
J.Clua

Hi,
Here are all errors logged:
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:10:18 PM]: Found a missing feature Id = [81606c80-44b3-47c9-8c24-136bdeb07d64]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:10:18 PM]: The feature with Id 81606c80-44b3-47c9-8c24-136bdeb07d64 is referenced in the database [WSS_Content_Sites_01], but is not installed
on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:10:18 PM]: Found a missing feature Id = [4b6e8a49-765d-47a1-92f8-91f61d07bbed]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:10:18 PM]: The feature with Id 4b6e8a49-765d-47a1-92f8-91f61d07bbed is referenced in the database [WSS_Content_Sites_01], but is not installed
on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:10:18 PM]: Found a missing feature Id = [af6d9aec-7c38-4dda-997f-cc1ddbb87c92]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:10:18 PM]: The feature with Id af6d9aec-7c38-4dda-997f-cc1ddbb87c92 is referenced in the database [WSS_Content_Sites_01], but is not installed
on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:10:18 PM]: Found a missing feature Id = [00bfea71-dbd7-4f72-b8cb-da7ac0440130]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:10:18 PM]: The feature with Id 00bfea71-dbd7-4f72-b8cb-da7ac0440130 is referenced in the database [WSS_Content_Sites_01], but is not installed
on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:16:17 PM]: Found a missing feature Id = [5daabc0d-5714-4b95-9238-95d58704bc11], Name = [Blog Rating], Description = [This feature allows visitors
to rate blog posts], Install Location = [Blog Rating]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:16:17 PM]: The feature with Id 5daabc0d-5714-4b95-9238-95d58704bc11 is referenced in the database [WSS_Content_AcademiaTI], but is not installed
on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:23:56 PM]: Found a missing feature Id = [af6d9aec-7c38-4dda-997f-cc1ddbb87c92]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:23:56 PM]: The feature with Id af6d9aec-7c38-4dda-997f-cc1ddbb87c92 is referenced in the database [WSS_Content_GlobalIT], but is not installed
on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [DEBUG] [3/11/2014 5:25:49 PM]: Retrieving site definition for language 1046...
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:50 PM]: Found 21 web(s) using missing web template 75801 (lcid: 1046) in ContentDatabase WSS_Content_EXP.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:50 PM]: The site definitions with Id 75801 is referenced in the database [WSS_Content_EXP], but is not installed on the current farm. The
missing site definition may cause upgrade to fail. Please install any solution which contains the site definition and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:50 PM]: Found 1 web(s) using missing web template 75802 (lcid: 1033) in ContentDatabase WSS_Content_EXP.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:50 PM]: The site definitions with Id 75802 is referenced in the database [WSS_Content_EXP], but is not installed on the current farm. The
missing site definition may cause upgrade to fail. Please install any solution which contains the site definition and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:53 PM]: Found a missing feature Id = [75a0fea7-2d1e-451a-b445-16bc346d7d8e]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:53 PM]: The feature with Id 75a0fea7-2d1e-451a-b445-16bc346d7d8e is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:53 PM]: Found a missing feature Id = [75a0fea7-5f69-4282-83ae-22808c0fbfd9]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:53 PM]: The feature with Id 75a0fea7-5f69-4282-83ae-22808c0fbfd9 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:53 PM]: Found a missing feature Id = [75a0fea7-6e3f-4d4a-8f78-245bda567b60]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id 75a0fea7-6e3f-4d4a-8f78-245bda567b60 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id = [75a0fea7-040e-4abb-b94b-32f1e7572840]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id 75a0fea7-040e-4abb-b94b-32f1e7572840 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id = [75a0fea7-b5a0-47d5-90e6-4b3205b02278]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id 75a0fea7-b5a0-47d5-90e6-4b3205b02278 is referenced in the database [[OWSTIMER] [SPContentDatabaseSequence] [ERROR]
[3/11/2014 5:25:54 PM]: Found a missing feature Id = [75a0fea7-b5a0-47d5-90e6-4b3205b02278]], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature
and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id = [f7b9c169-1418-41f3-888f-8ac436e17a0a]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id f7b9c169-1418-41f3-888f-8ac436e17a0a is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id = [75a0fea7-f13a-4670-8b69-97e90d05f7c8]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id 75a0fea7-f13a-4670-8b69-97e90d05f7c8 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id = [75a0fea7-377d-4b4f-b864-984379ed0f42]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id 75a0fea7-377d-4b4f-b864-984379ed0f42 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id = [75a0fea7-9d96-4f02-a800-a3512154efcd]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: The feature with Id 75a0fea7-9d96-4f02-a800-a3512154efcd is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:54 PM]: Found a missing feature Id = [90cd055f-f21f-42c5-b3fe-bb67173583d4]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id 90cd055f-f21f-42c5-b3fe-bb67173583d4 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id = [75a0fea7-0017-4993-85fe-c37971507bbc]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id 75a0fea7-0017-4993-85fe-c37971507bbc is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id = [75a0fea7-fe65-41c3-a965-c5df83fb098b]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id 75a0fea7-fe65-41c3-a965-c5df83fb098b is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id = [75a0fea7-7c51-4a75-92c1-cbaccb371622]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id 75a0fea7-7c51-4a75-92c1-cbaccb371622 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id = [75a0fea7-b0ef-434e-90d6-ce997d970564]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id 75a0fea7-b0ef-434e-90d6-ce997d970564 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id = [75a0fea7-37d2-484b-b362-dcff1538e2a4]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: The feature with Id 75a0fea7-37d2-484b-b362-dcff1538e2a4 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:55 PM]: Found a missing feature Id = [49c44827-4747-4e89-999c-f199ad95cfa8]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:56 PM]: The feature with Id 49c44827-4747-4e89-999c-f199ad95cfa8 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:56 PM]: Found a missing feature Id = [75a0fea7-42e8-4527-8313-f63c4c49a7e6]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:56 PM]: The feature with Id 75a0fea7-42e8-4527-8313-f63c4c49a7e6 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:56 PM]: Found a missing feature Id = [75a0fea7-a4ce-4a83-867d-f6be0ffdd867]
[OWSTIMER] [SPContentDatabaseSequence] [ERROR] [3/11/2014 5:25:56 PM]: The feature with Id 75a0fea7-a4ce-4a83-867d-f6be0ffdd867 is referenced in the database [WSS_Content_EXP], but is not installed on
the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[OWSTIMER] [SPSiteWssSequence] [ERROR] [3/11/2014 5:32:40 PM]: Action 4.0.23.0 of Microsoft.SharePoint.Upgrade.SPSiteWssSequence failed.
[OWSTIMER] [SPSiteWssSequence] [ERROR] [3/11/2014 5:32:40 PM]: Inner Exception: Já existe um campo com este nome.
O nome especificado para este campo é igual ao de outro campo da lista. Escolha outro nome e tente novamente.<nativehr>0x81020013</nativehr><nativestack></nativestack>
[OWSTIMER] [SPSiteWssSequence] [ERROR] [3/11/2014 5:32:40 PM]:
at Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateField(String bstrUrl, String bstrListName, String bstrXML)
   at Microsoft.SharePoint.Library.SPRequest.UpdateField(String bstrUrl, String bstrListName, String bstrXML)
[OWSTIMER] [SPSiteWssSequence] [ERROR] [3/11/2014 5:32:40 PM]: Exception: Já existe um campo com este nome.
O nome especificado para este campo é igual ao de outro campo da lista. Escolha outro nome e tente novamente.
[OWSTIMER] [SPSiteWssSequence] [ERROR] [3/11/2014 5:32:40 PM]:
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
[OWSTIMER] [SPUpgradeSession] [ERROR] [3/11/2014 5:32:40 PM]: Upgrade [SPSite Url=http://sjkqa41:7779] failed. Microsoft.SharePoint.Upgrade.SPSiteWssSequence has the ContinueOnFailiure bit set. Moving
on to the next object in sequence.
[OWSTIMER] [SPUpgradeSession] [ERROR] [3/11/2014 5:32:40 PM]: Inner Exception: Já existe um campo com este nome.
O nome especificado para este campo é igual ao de outro campo da lista. Escolha outro nome e tente novamente.
[OWSTIMER] [SPUpgradeSession] [ERROR] [3/11/2014 5:32:40 PM]:
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
   at Microsoft.SharePoint.Library.SPRequest.UpdateField(String bstrUrl, String bstrListName, String bstrXML)
   at Microsoft.SharePoint.SPField.UpdateCore(Boolean bToggleSealed)
   at Microsoft.SharePoint.SPFieldIndexCollection.IndexOneField(Object field, Boolean bIndexed)
   at Microsoft.SharePoint.SPFieldIndexCollection.Add(SPField field)
   at Microsoft.SharePoint.Upgrade.RestoreWorkflowAndDatasourceLibraryPermissions.Upgrade()
   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
[OWSTIMER] [SPUpgradeSession] [ERROR] [3/11/2014 5:32:40 PM]: Exception: Action 4.0.23.0 of Microsoft.SharePoint.Upgrade.SPSiteWssSequence failed.
[OWSTIMER] [SPUpgradeSession] [ERROR] [3/11/2014 5:32:40 PM]:
at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)
[OWSTIMER] [SPUpgradeSession] [ERROR] [3/11/2014 5:37:44 PM]: Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.
Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20140311-164603-307.log.
The number of errors and warnings is listed at the end of the upgrade log file.
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
   at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId)
Despite all the erros, can I consider these farm updated in terms of SharePoint build?
Thanks
J.Clua

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

QC Activity based on Material Production Version

Hi,
Normally, we perform QC activity based on Material Code, i.e. in Material Master we maintain inspection type in QM View for material which needs QC activation during Good Receipt from Production
Is it possible to perform QC Activity based on Production Version of a material i.e.
For Example
Product A having 2 Production Versions
IF Product A with Production Version 1 then No QC required during goods receipt from production
IF Product A with Production Version 2 then QC required during goods receipt from production
So please tell me what feasible solution possible from your side
With Regards,
Kunal Sheth

Dear Sap User,
Production version is nothing just a combination of Master recipe/Routing and BOM used for particular production or process.
If you are having so many production version then you have to choose which you want to choose but if you are having a single production version then it will be chosen automatically.
Do it once and revert in case of any query.
Rgrds,
Dheeraj Rawal
Edited by: Dheeraj89 on Feb 9, 2012 6:13 AM

Production Version of Co Product

Similar Messages

Maybe you are looking for