Production Version C223

What would be the easiest way to have the system show all Production Version's (C223) and their respective Route (CA01) relationship?
I want to make sure that all Production Version entries for ALL MATERIAL NUMBERS in the system coincide with the Routes that are turned on (status 4).
What method do you suggest I use to locate these?

Dear Lucas,
Goto C223,enter the plant and press enter the system displays all the production versions available.
Now select all the entries and click on consistency check (test) button to identify whether the
production version is ok or not and then click on system in the top menu->list->save--->local file and
you can check the details.
otherwise you have to download the datas from the table MKAL or check whether C252 can help you.
Regards
Mangalraj.S

Similar Messages

Master Recipe / Production Version

Hi,
I'm looking for FM/BAPI or IDOC's for creating/changing
master recipes (C201/C202) and production versions (C223). Can anyone help ?
TIA,
Rob Makelaar.

Hi Rob,
Message Type LOIROU ??
Regds,
Mano Sri

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

BAPI or FM or Standard BDC program for Production version creation (C223)

Hi All,
Is there BAPI or FM or Standard BDC program for Production version creation? Please help me.
Thanks & Regards
Santhosh

Hi,
Try this FM "CO_OCM_CREATE_PROD_VERSION"
Regards,
Smart

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.

Function Modules for creating production version.

Hi,
Is there any function module available in SAP to create Production version?
I'm aware of CM_FV_PROD_VERS_MAINTAIN function module but this one works on dialog mode.
Please let me know if there are any other function module/class available to create production version.
Many Thanks!
James....

Dear,
For C223 production version,
CM_FV_PROD_VERS_MAINTAIN
CM_FV_PROD_VERS_SAVE
Please refer this thread,
Re: Create "Production version".
Regards,
R.Brahmankar

Selection of Production version during MRP run

Hello experts
At present I am having 2 production versions for a material code as PV01 and MV01.
By putting validity date I am restricting correct version to be picked in MRP.
Is there any other way, for example in material master where if I maintain the production version, then MRP should pick that only.
Please suggest the best way.
Regards
Pradipta Sahoo

Dear Pradipata,
If you are having more than one production version for a material for the same Lot size and validity
dates,and if you have given BOM selection method as 2 in MRP4 view,then always the system picks up
the first production version defaultly.
If you want the system to pick up the second production version in that case means,you have to lock
the first production in MM02 or C223.
Check and revert back.
Regards
Mangalraj.S

Production version report

Hi Gurus,
is there a report that can give information about production versions. The fields at a minimum that i'm looking for are production version, material, text, alternate BOM, product line, Group, plant, valid from, lock, task list type, valid to, Bom usage
Thanks
Anusha

Anusha,
To my knowlede you cannot export it to Spread sheet from C223. If you need to download, then you can take it by table browser transaction SE16 from table MKAL.
1. Execute transaction SE16.
2. Input table as MKAL. Input the selection critera and also set the output fields and then execute.
3. You would be able to export this output to Spread sheet.
Regards,
Prasobh

Selection of BOM with Production version

Hello friends,
I have Finish product say A with two alt. BOM and Production Version 1 & 2
i have semi-finish product say B with two alt. BOM 1 and 2 in the BOM of the Product A
Now when i create PIR in MD61 for product A with production version 2 selection,how the system will select the component B
with alternative BOM 2
please suggest

Hi Mangesh,
The production version is selected based on the setting you are maitaining in MRP-4 view for Dependent Requirement Selection Method. The selection will be based on the Validity dates, Quantity i.e. based on the Lot sizes, and based on the production versions.
If both the versions are having same date,lot size etc, then the system will select the first version by default.
IF you do not want any version not to be selected then you can lock that version in MRP-4 view or in C223.
Thanks and regards
Muru

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

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

How to create production version & Explain with procedure

how to create production version & Explain with procedure
Madan

Hi Madan,
Production Versions are used to describe the production process to be used for planned / production order.
Why is it required?
Suppose you have 2/3 production lines and 2/3 alternative BOMs to produce one Finished Goods.
How system will come to know which BOM and Routing to be used. This is done thru Prod.Version.
In production version we maintain the combination of BOM and routing.
Also it can be designed with lot size or validity period.
Go to MM02--->MRP4 / Work scheduling view -
> Prod.Version.
Enter the validity period and lot size. and the production version should be unlocked.
After entering the reqd. routing no. and BOM alternative , carry a check.
After getting the Green signals ,Continue.
Thus you have saved the prod. version.
Mass processing TCode- C223.
Hope it would clarify you the basic of production version.

Create production version

Hi,
we use ECC 5.0 and APO 4.1. For APO we need production versions. My problem is to create or change the production versions of a material, every time the appropriate routing or BOM is created or changed in ECC.
There no suitable userexit in routing. Somebody told me to do with events and workflow. Can anybody tell me, how to do this on events routing-create/routing change and bom-create/bom-change.
regards Joerg

Function module CM_FV_PROD_VERS_MAINTAIN is used by transaction C223 to create/change production versions in dialog mode. Are you looking for a function module or BAPI that will allow you to create/change production versions without screen dialog? If so, I don't believe there is such a BAPI. I thought maybe BAPI_PO_CHANGE might be useful, but according to <a href="https://websmp202.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000252192005">Note 828538</a>, "For technical reasons, you cannot transfer the production version to the BAPI. However, as of SAP Release mySAP ERP 2005, you can influence the BOM components using the BAPI (complete recreation of the BOM or merging of the BOM components)."
- James G.

Urgent-material and production version

Is there a way i can pull the report or details for materials and production version used in a company code?

Hi,
USE Transaction C223
BR
Diwakar

Production Version C223

Similar Messages

Maybe you are looking for