Production version deletion

hi,
i have two production versions for material A, there is no open orders for this material. i am unable to delete production version 001 because its used in costing qty structure. but i amable to delete productioversion 002. we are using order based costing.. please help me delete production version which is used in costing qty structure....

HI,
Follow the below steps as Prerequisites before deleting the production version for a mterial :
1. You must settle the product cost collector you created for the production version.
2. No open planned orders exist in the system which are assigned to this production version.
3. Check that there is no wip exists on the production line if REM mfg strategy and No production order in WIP if DIscrete Mfg.
4. No open inspection lots are avl for the material with that PV.
5.For the period in which the last reporting point backflush was carried out and for all previous periods in which the run schedule header or the production version is valid.
the cutoff period is set for the WIP calculation
the cutoff period is set for the variance calculation (operation KVAR)
Hope this will help you.
regards
radhak mk

Similar Messages

NA KOSA012 and Product Version deletion

Good Day
I have an issue when trying to delete a production version from the material master.
The SAP message NA KOSA012 appears explaining that the version can not be deleted. I have checked the settings which the note suggests and everything appears to be correct. There are no open production orders in WIP either.
I have never had this issue before when trying to delete a version
Any idea's?

Hi,
Please check whether all the conditions as per the below link are satisfied.
http://help.sap.com/saphelp_47x200/helpdata/en/75/122e98f0bb11d2b6780000e82d81c3/frameset.htm
Regards
Kannan

Delete Production Version - Error

Hi
When I try to delete the production version, System wont allow to delete it and following message log is created -
Argument not contained in table T437s
Deleting Production Version 0001 for material XXXXXXXXXX is not possible
I checked table T437s and there is not entry for that matierla and plant combination. Also there is NO PCC created yet
REgards,
Lokesh

Dear Lokesh,
Check these links,
Re: Delete Production version
Re: production version
Regards
Mangalraj.S

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

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.

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_field

l_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.

SMSY: Product version SAP R/3 ENTERPRISE 47X200 keeps returning

Hi,
Last year we have upgraded our SAP R/3 ENTERPRISE 47X200 system to SAP ERP 6.0.
For downloading enhancement packages we need the product version to be SAP ERP 6.0. In SMSY however, SAP R/3 ENTERPRISE 47X200 is still mentioned in the product versions list. We can delete it manually (not used in any logical component anymore) and are able to download enhancement packages fine at that moment. However, when we refresh SMSY by reading data from the SLD the SAP R/3 ENTERPRISE 47X200 product version returns in the list of product versions and we have to delete it manually again.
Any ideas?
Thanks,
Regards,
Bart Groot.

check the Note and one of the same threads
Note 1296512 - SMSY: Product version transferred from deleted system
Configure ECC 6.0 EHP4 in SAP Solution Manager SP15

Change the Product version from ECC to ERP 6.0

Hello Experts
I am planning to apply EHP4 on my Development ECC system. In line with the the suggestion from guide "How to install SAP Enhancement Package 4 for SAP ERP 6.0" system I am supposed to define my ECC system with leading product version ERP 6.0.
My Ecc system is currently defined with Product version SAP ECC 6.0.
As per the above guide and also suggestion from "Note 1344564 - Maintenance Optimizer: Check system landscape" which says-
"In particular for a system of the product SAP ERP, assign the product version of SAP ERP, not SAP ECC."
I am supposed to change the leading product version to ERP 6.0.
Now with the current definition of system with product version SAP ECC 6.0, it is being used in a logical component. In order to change this I need to delete the associated logical component. The problem is -this logical component is being used in more than one Project definition that has huge documentation associated with them.
My question -
will the deletion of current logical component affect my documentation in any way?
How can I change the product version from SAP ECC 6.0 to SAP ERP 6.0 without affecting the current setup?
Regards
Dhiraj

Hello Warren,
Thanks for the suggestion.
I have already taken care of all the suggested notes in the master note that you suggested. I am able to generate the XML file for other solution defined in my system. In those I have my ECC system defined purely as ERP 6.0 system. I am not able to make out why its not generating the XML for this solution.
Regards
Dhiraj

Creating Production Order with wrong production version

Hello Expert,
please provide me answer and solution to resolve our problem regarding creation of production order (CO01 and CO41), because SAP provide and propose production version which have alternative BOM which is status 02 (inactive) already it is not picking the production version which has active alternative bom for our finished material. it is allowing the production to be created even the bom was inactive.
please help us to this it still bugging our system
tenx

Hi Ryan,
Production version will be selected based on the field Selection Method field in Material Matser MRP 4 view.
1 Selection by explosion date
2 Selection by production version
3 Selection only by production version
If the selected field value is 1 , then system selects the version based on the validity dates i.e whichever production version is active on that day that will be considered in MRP.
If the selected field value is 2 by production version. Then system will select the First Prodution version mentioned in the Material Master MRP 4 View (production version Tab).
If the selected field value is 3 always only by production version. Then system will select the First Prodution version mentioned in the Material Master MRP 4 View (production version Tab).
So to address you query I suggest you to delete the production version PV1 with BOM 01 and Make production version PV2 will be available and active in seen as the first production version in teh screen.
Then for your inof purpose you want have the PV1 then re-create it as second version in the Version tab screen.
Regards
radhak mk

Production version consistency check

Hi,
I am facing an issue in which i have created a BOM and a master recipe group. The production version is created and all the things are maintained properly so that consistency check shows green light i.e. everything is fine.
Then i delete the same material from recipe group and then do the consistency check then it turns to yellow since recipe group is missing.
But when i reassign the material to the recipe group and do the consistency check then also it remains in yellow and gives 2 line items in check result :-
one with message that task list exists.
and another with missing task list /material assisgnment .(in this the todate is the date on which i deleted the assignment)
My confusion is that after reassignment it should turn back to green but it is not.
Can you please help on this.
Thanks
Rohit

Hi Rohit,
Check Production Version Valid from date and also Date from when you have reassign that material in Master Recipe again.Both should be match.
Regards,
Dhaval

Production Version naming convention

Hi all,
We are using PDS and it is being transferred from R/3.
The problem is in R/3, in many cases different materials are having the same production version numbers.
If we have the same production version number will it cause any problem / confusion while transfer to APO and in further planning process in APO ?
Current situation in R/3 :
Product A : Production Versions 0011,0012,0013....
Product B : Production Versions 0012,0013,Z014..... Is this ok ?
Or is it better to delete and create with unique production version number in R/3 before transferring ?
Kindly guide.
Durai

Hi Durai,
The PDS will get the combo structure of product-location-version no only.
So, there is no harm in having different products having same production version numbers.
Regards
R. Senthil Mareeswaran.

Product version not found

Hi Experts,
I am create Integration scenario while assigning the Product version i was face Product version not found error.
I choose the different product version it is working. If you know solution please help me.
Thanks & Regards,
Veera.

Hi ,
Please check in the SLD once for the product version which you are trying to use.There might be the case that it had been deleted by someone.
access SLD from XI and check if someone has deleted your software component from SLD
Do a sld cache refresh. check for locks Integration Buileder -> administration->admin of locks and caches.
Last option restart the XI service and see if it starts working
Regards,
srinivas

New Jdevelopper Production version

Hi,
When last preview became a production version ?
Do you have resolve problem of physically delete java file, when a file is removed from a Project ?
Regards
Philippe

In 10.1.3 the way JDeveloper manages the project content has changed.
Details about the new (and improved) way are in this document:
http://www.oracle.com/technology/products/jdev/101/collateral/101/migratingjdeveloperprojectsto1013.pdf
The way to eliminate files from showing up in your project in the developer preview is with the working set feature.
In production we'll make it easier with a button that does this automtaically for you.

Reg:Production Version

Hi,
1Please tell me about the following question
1) Suppose i have created 5 productions versions
i want to use the 3rd PV first and 4th as second and other PV's afterwards
what are the settings we need to do
whare do we do the settings
Regards,
Raj

1Please tell me about the following question
1) Suppose i have created 5 productions versions
i want to use the 3rd PV first and 4th as second and other PV's afterwards
what are the settings we need to do
whare do we do the settings
IF the PV selction is based on Lot size maintain accordingly
OR
Delete the 1 and 2 PV and create after the 5 th PV

Production version deletion

Similar Messages

Maybe you are looking for