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

Similar Messages

Error: Enter a valid Production Version

Dear Gurus
I have a problem while production booking of a vehicle. It says Enter a valid production version. I have checked the version in Material master-->MRP4 view. The version is maintained there. What else whould i check ?
Pls Help
REGARDS

Dear Gaurav,
As this is Repetitive Manufacturing then , you should maintain the Product cost collector also. Please do maintain this & then try.
When u enter the group no of routing & also the alternat BOM & click on check at the top of the screen, When you click on check button then, the signals will turn to green if you have used the valid BOM & Routing group no.. If you get green in this screen then, there is no problem with Production Version.
Please do let me know for any clarifications.
Regards
Kalyan

Missing System under Product Version at Maintenance Optimizer

Hello Colleagues,
We currently using SAP Solution Manager 4.0 SP11 for our SAP landscape.
For upgrade our new PI 7.1 system with EHP1 we need to download respective files at SAP Solution Manager with the Maintenance Optimizer.
Under Product Version (pull down menu) at Maintenance Optimizer (TC DSWP) I am only able to select the Solution manager itself. Not the already configured PI system under System Landscape (TC SMSY).
Any idea why I am not able to select the PI system?
Many thanks in advance!
Regards,
Jochen

Hello Jochen
1. Are your Solution Manger system and P1 system in same Solution(system landscape) ?
2. Or each of the above two systems has different solution ?
If yes in the first case, then this might be filter problem in initial screen of MOPz. On the right corner you can see filter options. click on it and check if are able to select all of your systems under this Solution in which you are running MOPz tcode.
If 02nd option is true, then you should run MOpz tcode in the correct solution, in which the system P1 is maintained.

BDC Error in transaction CO02

Hi All,
I have to create a production order with one material and one component material with reference to WBS element (CO10). After creation of PP order, I have to add multiple items using CO02 transaction. But the transaction screen flow control is very complex and it is calling different screens dynamically for multiple items. If i create recording with no batch input checkbox and simulate background mode selected the screen flow sequence is different and if i uncheck any one of those the screen flow is different. Is there any solution in BDC to overcome this errors? Is there any BAPI, Function modules ormethods available to add items in PP order?
Thanks in advance.
Thanks and Regards,
Chandra Sekhar

Hi Chandrasekar,
Check No-Batch-input and simulate in background. I hope it will work. When you uncheck no-batch input, screen will get changed because system will take old screens. for example check recording XD01 with nobatchinput checked once and unchecked once. you will come to know the difference.
Hope this helps.
Regards,
Bhargav.

BDC Error in transaction code IHC1IP

HI Experts,
I have a requirment to Park/Post multiple Payment orders via transaction code IHC1IP .So proceeded with BDC but in the screen of IHC1IP there a long text called Payment Notes which i am unable capture by recording. Please suggest if anyone has faced the same problem. As per as my understanding because of container is used for payment notes .
So is it because of container its not captured by BDC or is there any problem. Please sugggest me the way to proceed further.
Regards,
Krishna Prasad.K

Hi Krishna,
If you have got the answer for the above query, please share with me. As I am stuck at the same place.
Thanks in advance!!!
Regards,
Roli

Error While Starting JDEV (production version 10.1.2)

I get the following error while starting jdev.
java.lang.NoClassDefFoundError: oracle/xml/parser/v2/DTD
at oracle.ide.marshal.xml.Object2Dom.<init>(Object2Dom.java:1625)
at oracle.ide.marshal.xml.Object2Dom.newInstance(Object2Dom.java:118)
at oracle.ide.config.IdeSettings.load(IdeSettings.java:250)
at oracle.ide.IdeCore.loadIdeSettings(IdeCore.java:1510)
at oracle.ide.IdeCore.startupImpl(IdeCore.java:1036)
at oracle.ide.Ide.startup(Ide.java:539)
at oracle.jdeveloper.JDeveloper.launch(JDeveloper.java:58)
at oracle.jdeveloper.JDeveloper.main(JDeveloper.java:37)
Any idea?
Raghu

Here is what I'm getting though:
java.lang.NullPointerException
at oracle.ide.addin.AddinConfig.isEmpty(AddinConfig.java:239)
at oracle.ide.AddinManager.exclusiveExtension(AddinManager.java:1317)
at oracle.ide.AddinManager.initProductAndUserAddins(AddinManager.java:43
1)
at oracle.ide.IdeCore.initProductAndUserAddins(IdeCore.java:1650)
at oracle.ide.IdeCore.startupImpl(IdeCore.java:1109)
at oracle.ide.Ide.startup(Ide.java:539)
at oracle.jdeveloper.JDeveloper.launch(JDeveloper.java:58)
at oracle.jdeveloper.JDeveloper.main(JDeveloper.java:37)
-Brian

How to customize production version error message

Hi Friends,
I copied the BAPI_REPMANCONF1_CREATE_MTS into Z FM and when I test the Z FM, I wantedly entered the wrong production version say ABCD instead of 1234. The message field of my return bapi BAPIRET2 is populated with an error message saying that "Production version not found". Till here it is working fine.
I need to modify my code in such a way that if I enter the wrong production version, my bapi should error me in such a way that "ABCD Production version not found" in the message field of BAPIRET2.
Please sugesst me ideas for solving this.
Thanks.

Nani,
Please follow approach suggested by Suman.
All you have to do is validate production version ( of that material/product?) against DB Tables before calling you ZFM or Std BAPI.
If you would like to go by my approach.. you will have to do something like this..
option1:
IF RETURN-TYPE = 'E' AND RETURN-ID EQ 'RM' AND RETURN-MESSAGE = '149'.
CONCATENAT 'XXXX' RETURN-MESSAGE INTO RETURN-MESSAGE.
ENDIF.
Option2: Create a Z class.
IF RETURN-TYPE = 'E' AND RETURN-ID EQ 'RM' AND RETURN-MESSAGE = '149'.
RETURN-ID = 'ZID'.
RETURN-NUMBER = 'XXX' -> Number in Z class.
RETURN-MESSAGE = 'your message'.
ENDIF.

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

How to add new product version in Mopz?

Hi,
Can anyone guide me how to add a new product version in maintenance optimizer?
I am going to get the stack file of Netweaver gateway 7.4, but without the product version, I could not proceed.
Thanks in advanced.

Dear Friend,
1. Maintain Solution Manager information in the system’s SLD data supplier. In case of ABAP system using tcode RZ70 and incase of Java system using the Visual Administrator/NWA(for NW 7.3 onwards)àSLD data Supplier.
2. Once the data supplier jobs gets executed you system will appear under SMSY under Server, Database and (Technical System in case of Java systems).
The ‘Data Source’ should be LMDB.Note: Please don’t changes to the system in SMSY
3)Execute transaction code ‘LMDB’ in your solution manager system.Select Technical system(Give Application server ABAP and SID of the Server)
4)Click on Edit and select Software
Click ‘Add’ and it will show Product Version screen and search for your installed product.
5)Select your relevant usage types and once done choose ‘Close’ and save the data.
6)Assignment of Product System :
Click ‘Assign to Product System’
Now Product system does not exist, hence we have to create one. Choose ‘Create’ and confirm
7)After that complete Landscape Verification check..it should be green.
8)Go to Solman_setup and complete Managed system configuration.
after that Create Maintainence transaction and generate stack file.
Before doing all activities make sure that ST-PI and ST-A/PI Patched should be applied in Managed server(NW 7.4) and run rtcctoll.
Regards
Maruthi V

Solution manager configuration for EHP4 install (Product Version Problem)

Hi guys!
I'm new on SAP and SDN is a help all days and this time i really need some help from you guys!
Im installing EHP 4 and need the XML Stack file, so i go to the solution manager to generating them. But after configuring the logical components, make the associations, etc. on create maintenence transaction, the product version dropdownlist is empty...
It is configured but it dont appears... Anyone had this problem before and could give me some help!
I will appreciate that!
My regards,

Hi,
In SMSY, the system should have product version as SAP ERP 6.0.
Next the logical component created for ECC Server should also reflect this version.
The solution you create in DWSP should include this logical component via the Solution Landscape definition. Here again the logical component should show the product version.
If all above are in place, the MOPZ for the respective solution should have the product version list populated.
Regards,
Srikishan

Production version problem

Hi friends
when i have created production version for one material i got the error. pleas efind the error below.
inconsistencies for production version.
when i checked the production version for that material systm shows the green light for bom and red light for routing. but system shows bom exists and task list exists. onle problem is inconsistencies for production version.
please help me any missing from my side
Thanks
venkat

Hi
1. Check the valid from date for Routing and the Valid from date that you entered in the production version ( MM02/ MRP4 VIEW ) is same
The vaild from date should be same for Routing and the PV valid from date (Mentioned in PV BASIC DATA)
Suppose the valid start date of the Routing is later than tha Date that you given in the production version basic date, then the inconsistence error will come . it give the red light to Routing
ie.
Routing valid from date : 06..06.2009
PV vaild from date : 01.06.2009
So for the date 01.06.2009 - 05.06.2009 , ysytem say that no Routing exist.inconsistence in pv.

Costing - Multiple Production Versions and Recursive BoMs

Hi All,
We have a production and product costing scenario as follows:
Production versions 10, 20 and 30. It takes all three versions to manufacture the finished material and there are no intermediate products in this scenario. 10 and 30 are to be costed and 30 is a recursive BoM with the input from version 10 also being the output. 10 is the main production step with components but 30 is a recursive BoM sometimes only with the output material as the input and sometimes with a more complete BoM but which includes the output material as an input component.
The quantity input appears to be the same as quantity output for the recursive element.
If anyone has come across this scenario and you can let me know what design principles you followed I would appreciate it.
We are getting iteration error messages when costing production version 30 and even reducing the input quantity below 95% of the input as per the SAP documentation does not fix the error message.
Any help you can give will be greatefully received.
Thanks.
Regards,
Tim

Murali - Its possible to use multiple PV in sub contracting.
Settings in ERP :
1. In CFC9 activate the - Transfer multiple selection of PDS indicator. When you select this indicator, the system allows you to select several productions versions in the integration model; it also creates a Production Process Model (PPM) or Production Data Structure (PDS) for each production version in SAP SCM
2. Assign the PV's to the subcontracting info record through - Logistics - Central Functions - Supply Chain Planning Interface - Core Interface - Advanced Planner and Optimizer - Environment - Data Transfer -Assign Multiple Production Versions
3. When you select the integration model parameters for PDS, you have selected PP/DS Subcontracting as the PDS Type value. Similarly, for PPM, you have selected Subcontracting PPM as the Type of PPM value.
Subcontracting with multiple production versions is supported. However, the integration with an SAP ERP system requires at least SAP ERP 2005 with Enhancement Pack 03.
Rgds
Valavan

Mass maintenance for Settlement rule

Hi,
I want to maintain settlement rule of Network (cn22) and Internal order (Ko02). How can I carry out mass maintenence for these business process?
PLease mention steps or any transaction.
Thanks
SIM

HI,
I don't know a standard transaction for settlement rules mass maintenance but you can use LSMW based on a batch-input recording for the changes you want to make.
Best regards, Christian

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

BDC Error in transaction C223 - production version mass maintenance

Similar Messages

Maybe you are looking for