PRODUCTION VERSION
When i am creating process order for a material it is showing a message that
'Production version is not maintained'.What should be done to solve this problem.Please guide me on this.It is urgent.
Hi,
Go to MRP 4 view, select Production Version.
Give the name for the version, say 0001,
By default it is valid from today's day to 31.12.9999.
Again click on this version,
select the necessary BOM (in Bill of materials Tab) and routing (in planning data tab) .
Check it and if ok, you will get check start in Green.
Or else use T.Code C223, to create production version for the material.
Hope it is clear.
Srini
Similar Messages
-
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
AmauryHi
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. -
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)
RegardsHi
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 ShethDear 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
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 -
Different fix lot size depending on the production version
Hi all,
I have the next scenario:
2 production versions. 2 different fix lot size por each. So:
Prod Version 1 - Fix lot size 200
Prod Version 2 - Fix lot size 300
I created the Quota Arrangement just to make SAP to take my favourite version. And trought the quota, I can define the lot size for each version. BUT.
If I change the version in the order or in the planned order, the quantity don't change.
So: How can I manage 2 different fix lot size for 2 different product versions? If I change the version once the order is created, how can I do the system change de quantity to the right one?
Thanks in advante
<< Please do not offer points >>
Edited by: Rob Burbank on Oct 1, 2010 2:53 PMI have n't tried this scenario,
This is my Idea
Create a two production version
for ex: lot size 100 to 1000, set the rounding profile qty as 1000
for lot size 1001 to 99999, set the lot rounding profile value to 5000
BY this way u can get the two lot based on the rounding profie
Expert; please correct if i am wrong
Edited by: Sundaresan . E. V on Oct 1, 2010 4:12 PM -
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. -
Transfer of Production Version
Hi Gurus,
i am trying to transfer the Production Versions of a Material to an other System via IDoc. I am using BD10 for transfering.. The relevant Segment E1MKALM in MATMAS05 is filled with all data from the source. But in the Target Systen tge Production Version is not added (Material exists already in Target system, only addition is needed).
what am i am doing wrong? The Segment E1MKALM is directly for Production Version, but why this is not used in the target system? There are no errors in BD87 when i process the IDoc.
any Ideas?
Best Regards
Udono answered but i dont want this question to hang in ....
-
BAPI/Function module for production version tab data of MRP4 view(MM01).
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>
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 can i get production version value(verid) for luck through bdc.
HI..
i have one requirement..that in c223 tcode while i luck the production version through BDC in my report program as i given bellow...i upload mat.no , plant, production version and 1(for luck)...
req:: i want while i given production version for particlular plant and material no...that production version should be luck....
so in standard tcode c223 how can i get value to compair it with my input production version value then i will close that...
program:::
report ZC2232
no standard page heading line-size 255.
*include bdcrecx1.
Tables : mkal.
data : nodata value '/' .
data : CTUMODE type c value 'E'.
DATA : CUPDATE TYPE C VALUE 'L'.
DATA: BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
messages of call transaction
DATA: MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
data: begin of HEADER OCCURS 0,
data element: MATNR
MATNR_001(018),
data element: WERKS_D
WERKS_002(004),
data element: PLNNR
PLNNR_003(008),
data element: CP_STTAG
STTAG_003(010),
data element: ENTRY_ACT
ENTRY_ACT_005(011),
data element: PLNAL
PLNAL_004(001),
data element: FLG_SEL
FLG_SEL_01_006(001),
data element: PLANTEXT
STLAL_004(002),
DATUV_005(010),
data element: WERKS_D
WERKS_008(004),
data element: PLN_VERWE
ktext_005(001),
data element: PLNST
DELKZ_005(001),
data element: LOSGRVON
LOSVN_011(017),
data element: LOSGRBIS
LOSBS_012(017),
data element: PLNME
PLNME_013(003),
data element: PLNME
stlal_014(002),
end of HEADER.
data : begin of it_header occurs 0,
matnr like marc-matnr,
werks like marc-matnr,
verid like mkal-verid,
mksp like mkal-mksp,
end of it_header.
data : exnum(40) type c,
exnum1(40) type c,
cnt type I,
CN(2) TYPE C,
c1 type c value '(',
c2 type c value ')'.
start-of-selection.
parameters: p_file like rlgrap-filename.
at selection-screen on value-request for p_file.
call function 'F4_FILENAME'
EXPORTING
PROGRAM_NAME = SYST-CPROG
DYNPRO_NUMBER = SYST-DYNNR
FIELD_NAME = ' '
importing
file_name = p_file.
start-of-selection.
call function 'WS_UPLOAD'
exporting
CODEPAGE = ' '
filename = p_file
filetype = 'DAT'
HEADLEN = ' '
LINE_EXIT = ' '
TRUNCLEN = ' '
USER_FORM = ' '
USER_PROG = ' '
DAT_D_FORMAT = ' '
IMPORTING
FILELENGTH =
tables
data_tab = it_header
EXCEPTIONS
CONVERSION_ERROR = 1
FILE_OPEN_ERROR = 2
FILE_READ_ERROR = 3
INVALID_TYPE = 4
NO_BATCH = 5
UNKNOWN_ERROR = 6
INVALID_TABLE_WIDTH = 7
GUI_REFUSE_FILETRANSFER = 8
CUSTOMER_ERROR = 9
NO_AUTHORITY = 10
OTHERS = 11
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
DELETE it_header WHERE MATNR IS INITIAL.
LOOP AT it_header.
*start-of-selection.
*perform open_group.
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'
it_header-werks.
perform bdc_field using 'MKAL-MATNR'
it_header-matnr.
perform bdc_dynpro using 'SAPLCMFV' '1000'.
perform bdc_field using 'BDC_OKCODE'
'=PICK'.
perform bdc_field using 'MKAL-WERKS'
it_header-werks.
perform bdc_field using 'MKAL-MATNR'
it_header-matnr.
*>>>>>>>>>>>>>>>>>>>>here what logic can i write****
clear cnt.
do 15 times.
cnt = cnt + 1 .
CN = CNT.
exnum = 'MKAL_EXPAND-VERID'.
concatenate exnum c1 cn c2 into exnum1.
*perform bdc_field using 'BDC_CURSOR'
exnum1.
GET PARAMETER ID 'VER' FIELD EXNUM1.
CALL TRANSACTION 'C223' AND SKIP FIRST SCREEN.
if ( it_header-verid = EXNUM1 ).
exit.
endif.
enddo.
****************************************************end***>>>>>>>>
perform bdc_field using 'BDC_CURSOR'
exnum1.
perform bdc_dynpro using 'SAPLCMFV' '2000'.
perform bdc_field using 'BDC_CURSOR'
'MKAL_EXPAND-PLNTY'.
perform bdc_field using 'BDC_OKCODE'
'=PRFG'.
perform bdc_dynpro using 'SAPMSSY0' '0120'.
perform bdc_field using 'BDC_OKCODE'
'=RW'.
perform bdc_dynpro using 'SAPLCMFV' '2000'.
perform bdc_field using 'BDC_OKCODE'
'/ECANC'.
perform bdc_field using 'BDC_CURSOR'
'MKAL_EXPAND-VERID'.
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'
it_header-werks.
perform bdc_field using 'MKAL-MATNR'
it_header-matnr.
perform bdc_dynpro using 'SAPLCMFV' '1000'.
perform bdc_field using 'BDC_OKCODE'
'/EBACK'.
perform bdc_transaction using 'C223'.
endloop.
*perform close_group.
*& Form bdc_dynpro
text
-->P_0161 text
-->P_0162 text
form bdc_dynpro USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
endform. " bdc_dynpro
*& Form bdc_transaction
text
-->P_0351 text
form bdc_transaction USING TCODE.
call transaction 'C223' using bdcdata
mode CTUMODE
update CUPDATE
messages into messtab.
if sy-subrc <> 0.
message e000(zmm01) with
'Check your input data'.
endif.
endform. " bdc_transaction
*& Form bdc_field
text
-->P_0346 text
-->P_0347 text
form bdc_field USING FNAM FVAL.
if fval <> nodata.
CLEAR BDCDATA.
BDCDATA-FNAM = FNAM.
BDCDATA-FVAL = FVAL.
APPEND BDCDATA.
endif.
endform. " bdc_fieldl_nl := dbms_xslprocessor.selectNodes(l_n, '/TaxInvoice/TaxInvoiceDocument');try to change as follow
l_nl := dbms_xslprocessor.selectnodes(l_n,'/TaxInvoice/TaxInvoiceDocument','xmlns="urn:kr:or:kec:standard:Tax:ReusableAggregateBusinessInformation:1:0"');Edited by: AlexAnd on Aug 17, 2011 12:36 AM -
Production Version in Material Master
Hi,
I am having problems with this.
I need to either change date on a production version or
delete the product version.
I have tried using a batch input sequence from my program both for changing the date
and for deleting the production version and this all works well.
Now this isn't good enough since there can be multiple production versions on a material
and I don't know which line to change or delete in the batch run.
Is there a good FM or BAPI to handle this?
I don't want to change the MKAL table directly since there is a history table
connected to this also (MKAL_AEND).
What is the best approach?
Rgds,
/Fredrik.How can I use this to achieve what I want to do, either
change the production version date or delete the production version?
I have tried C223, but this is not good enough, nor is batch run in MM02.
I can have multiple production versions and can not pick the correct line
in batch run to change or delete. -
Production Version in R/3 & PDS in APO
Hi Team,
I have below master data settings in R/3:
1. Material Master
2. BOM
Note:
I do not have work center & routing in R/3. I have set the default operation for my order type in OPJG.
But as per system landscape, the planning will be performed in APO. Hence i need to CIF the production version to APO from R/3. But i do not have routing in R/3. Is it possible to create the production version without routing (in R/3)?
ThanksYes, It can be transferred. You need to create CIF integration model(CFM1) with "BOM" option selected.
SAP Help says following -
Material BOM in Integration Model
If you set this indicator, all bills of material that correspond to the
stated selection options are indcluded in your model.
Dependencies
The material BOM filter object can only be used in connection with the
production data structure (iPPE) and it is used to map phantom assemblies.
Only those bills of material are transferred for materials for which no
production production versions have been created.
Hope this will help.
Thank you
Satish Waghmare -
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.CHi,
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 -
Selecting production version in MRP run
Hi dudes,
our client is having reuirement is he will select the production version irrespective of lot size, but he select the production version at the time of manual creation of process order where it depends on resource(work center used in recipe of particular production version, BOM will be 1 alternative only.
now while running MRP how to make system to allow manual selection of production version at the time of converting planned order to processs order.
respond asap plz...
Daniel.Hi ,
During MRP, system will select the production version based on Validity date & Lot size.
If a material contains two production versions with same validity date & Lot size qty , system will select the First valid PV by default (unless it is locked) & will copy to planned order.
When u convert the planned order to production order,default PV will be copied automatically from planned order. Here u cannot select PV manually.
Settings:
Create valid production version with lot size and Valid routing , BOM at MRP view of Planning material.
Assign the selection method = 2 or 3 at MRP view of Planning Material
Regards,
Anand.
Maybe you are looking for
-
MultiColumn text in JEditorPane.
I'd like to represent solution for the multi column text. It may be used in JEditorPane and JTextPane. Opinions? regards, Stas import javax.swing.*; import javax.swing.text.*; import view.*; public class Application extends JFrame { JEditorPane e
-
Conversion from decimal to char
Hi experts, i am using some function module which has parameter of type char(132) . now i have to pass packed no p(7) decimals 3 to this how to do it . if i send directly function module raising run time error ( type conflict). how we can do this
-
Release strategy not applied for some contracts..
Dear All, At my client place,In some of the contracts release strategy is not applied. I have tried evrything...in classification plant,purchasing group,net value and order type (MK and WK)everything is added. but some of contracts release strategy i
-
Upgrade Content Services to Content DB
Looking for clarification on the following: 1. Can users of OCS Content Services upgrade to Content DB under their current OCS license? 2. Is Content DB the foundation for Universal Content Management? 3. Is Content DB related to the Content DB Suite
-
My IMAC has a 10.6 operating system and I am trying to learn how to use the cloud to store pictures and upload files etc from my iphone. Do I need to upgrade my operating system and how do I do that?