Error during MB11 bdc-upload

hi experts.
I am using a BDC-UPLOAD program for MB11 but there is one error during an upload.
Here is a procedure which i am following:
I have created an upload file, which is tab-delimited format. In which such information exists:
01.12.2008 12.12.2008 561 d920 m920 536319000 1 PC 100
Now when i am uploading this file using movement type P61 or 561 a same error occurs:
Formatting error in the field MSEG-EXBWR ; see next message
Make an entry in all required fields and this is a required field, its a currency type field but i have even checked it by replacing it into char & num.
Is there any standard upload program for STOCK UPLOAD using MB11? If there is any one who can send me a solution.
thanks in advance.
Regards,
Yahya Shoaib.

OK...I think you have declared the internal table field for that value same as the standard table right??
Now, create a variable with char and then move the value to that char variable and then pass it to the subroutines...
Ex:
loop at itab into wa.
var1 = wa-amount
perform bdc_field using mseg-exwbr var1.
endloop.
Now, I think it will pick up the value.
VIshwa.

Similar Messages

MB11 BDC upload issue

hi experts.
I am using a BDC-UPLOAD program for MB11 but there is one error during an upload.
Here is a procedure which i am following:
I have created an upload file, which is tab-delimited format. In which such information exists:
01.12.2008 12.12.2008 561 d920 m920 536319000 1 PC 100
Now when i am uploading this file using movement type P61 or 561 a same error occurs:
Formatting error in the field MSEG-EXBWR ; see next message
Make an entry in all required fields and this is a required field, its a currency type field but i have even checked it by replacing it into char & num.
Is there any standard upload program for STOCK UPLOAD using MB11? If there is any one who can send me a solution.
thanks in advance.
Regards,
Yahya Shoaib.

Hi,
For Stock upload I prefer creation of a program by calling Function Module BAPI_GOODSMVT_CREATE. When you use BAPI, as it is being function module you need not do the recording as well. You can test the BAPI also manually in SE37. This simulation helps in passing the data in the feed file. You may contact your ABAPer for creating a program using this BAPI. You can input the feed file in similar fashion that of BDC

NWDS 7.0 Error during Quick PAR Upload and while trying Exporting PAR-File

Hello,
I am trying to use the functions "Export as PAR-File" and "Quick PAR Upload" in NWDS 7.0.
Unfortunately I got an error every time when I am trying to use this functions. I am using the package explorer in the Java perspectiv in NWDS for starting this functions. The error tells me the following:
"Unable to connect to the Portal"
"Operation failed: Please make sure the server "XY" is running or check the log (sap-plugin.log) for more detail"
Thats all.
When I am looking in the log-file I can read the following messages:
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: GET_VIEW:ALL]"
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: IS_VIEW_EXISTS:ALL]"
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: SIZE_OF_VIEW:ALL]"
"ACCESS.ERROR: Authorization check for caller assignment to J2EE resource [keystore-view.TicketKeystore: view-actions: READ_ENTRY:ALL]"
LOGIN.ERROR|null|| Login Method=[default] UserID=[user_Admin] IP Address=[192.168.xxx] Reason=[Cannot authenticate the user]
I have tried this with several users and their passwords. All of the users have admin-rights at least in the portal. One of them even in the SDM.
I can sucessfully deploy webdynpros from NWDS into the same Portal with this users.
We are using SAP Logon Tickets and SSO is configured working fine between Portal and backend.
We have imported Key Store File in NWDS unter Window --> Preferences --> Java Development Infrastructure.
And we are not using the NWDI.
Who knows why I cannot even export par-files? Are their any configurations missing?
Best regards,
Iris

It is mentioning about authentication.
check whether you have access to deploy directly or not ? maybe direct deployment into portal disabled .
I think you have to follow the procedure of checkout and activate procedure.
Can you clarify few things
1) Are you using NWDI Based Transports in your landscape?
Login Method=default UserID=user_Admin IP Address=http://192.168.xxx Reason=Cannot authenticate the user
http://192.168.xxx is it your development portal?
Did you clarify with admin people whether direct deployment disabled?
Koti Redd

Error during BAPI while uploading Material data through MM01

Hi all,
i am facing one problem when uploading Material data thorough BAPI in MM01.i am attaching the code below and the error given.
but in the debugger all the value is being stored.
REPORT ZFINISHED_MAT.
Data: Begin of legacy_data occurs 0,
     MATNR LIKE MARA-MATNR,
     MBRSH LIKE MARA-MBRSH,            "Industry Sector
     MTART LIKE MARA-MTART,            "Matl Type
     WERKS LIKE MARD-WERKS,            "Plant
     LGORT LIKE MARD-LGORT,            "Storage location
     VKORG LIKE MVKE-VKORG,
     VTWEG LIKE MVKE-VTWEG,
     MAKTX LIKE MAKT-MAKTX,             "Matl Desc.
     MEINS LIKE MARA-MEINS,             "Base UOM
     MATKL LIKE MARA-MATKL,             "Matl.Grp
*     BISMT LIKE MARA-BISMT,
     SPART LIKE MARA-SPART,             "Division
*     BRGEW LIKE MARA-BRGEW,             "Gross weight
     GROES LIKE MARA-GROES,
     FERTH LIKE MARA-FERTH,
     ZEINR LIKE MARA-ZEINR,
     TAXKM1 LIKE MLAN-TAXM1,
     TAXKM2 LIKE MLAN-TAXM2,
     TAXKM3 LIKE MLAN-TAXM3,
     TAXKM4 LIKE MLAN-TAXM4,
     KTGRM LIKE MVKE-KTGRM,
*     GEWEI LIKE MARA-GEWEI,             "Weight unit
*     NTGEW LIKE MARA-NTGEW,             "Net weight
*     KLART LIKE RMCLF-KLART,
     MTVFP LIKE MARC-MTVFP,             "Availibility Check
*     XGCHP LIKE MARA-XGCHP,
     XCHPF LIKE MARA-XCHPF,             "Batch Management
     TRAGR LIKE MARA-TRAGR,
     LADGR TYPE MARC-LADGR,
     VPRSV LIKE MBEW-VPRSV,            "Price Control
     VERPR LIKE MBEW-VERPR,
*     SPRAS LIKE MAKT-SPRAS,
END OF LEGACY_DATA.
DATA: BEGIN OF IT_MAKT OCCURS 0.
INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF IT_MAKT.
*--- BAPI structures
DATA: BAPI_HEAD LIKE BAPIMATHEAD, " Header Segment with Control Information
BAPI_MAKT LIKE BAPI_MAKT, " Material Description
BAPI_MARA1 LIKE BAPI_MARA, " Client Data
BAPI_MARAX LIKE BAPI_MARAX, " Checkbox Structure for BAPI_MARA
BAPI_MARD1 LIKE BAPI_MARD,
BAPI_MARDX1 LIKE BAPI_MARDX, " Checkbox Structure for BAPI_MARD
BAPI_MARC1 LIKE BAPI_MARC, " Plant View
BAPI_MARCX LIKE BAPI_MARCX, " Checkbox Structure for BAPI_MARC
BAPI_MVKE1 LIKE BAPI_MVKE,
BAPI_MVKEX1 LIKE BAPI_MVKEX, " Checkbox Structure for BAPI_MVKE
BAPI_MLAN1 LIKE BAPI_MLAN,
BAPI_MLANX1 LIKE bapi_mlan1, " Checkbox Structure for BAPI_MLAN
BAPI_MBEW1 LIKE BAPI_MBEW, " Accounting View
BAPI_MBEWX LIKE BAPI_MBEWX, " Checkbox Structure for BAPI_MBEW
BAPI_RETURN LIKE BAPIRET2. " Return Parameter
*              $PARAMETERS DECLARATION$
SELECTION-SCREEN BEGIN OF BLOCK B11
                          WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE LIKE RLGRAP-FILENAME. " DEFAULT 'C:\TEST1.XLS'.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN ULINE.
SELECTION-SCREEN END OF BLOCK B11 .
*              $DATA DECLARATION$
*DATA : BDC_DATA LIKE STANDARD TABLE OF BDCDATA WITH HEADER LINE.
DATA : IT_EXCEL TYPE STANDARD TABLE OF ALSMEX_TABLINE INITIAL SIZE 0 WITH HEADER LINE,
        IT_EXCEL_DUMMY TYPE ALSMEX_TABLINE.
DATA : MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : L_MSTRING(480).
DATA :L_SUBRC LIKE SY-SUBRC.
DATA: V_FILE TYPE STRING.
*              $AT-SELECTON SCREEN DECLARATION$
AT SELECTION-SCREEN ON P_FILE.
IF P_FILE IS INITIAL.
    MESSAGE E398(00) WITH 'FILE NAME NEEDS TO BE SPECIFIED'.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
CALL FUNCTION 'F4_FILENAME'
   EXPORTING
     PROGRAM_NAME        = SYST-CPROG
*   DYNPRO_NUMBER       = SYST-DYNNR
     FIELD_NAME          = 'P_FILE'
   IMPORTING
     FILE_NAME           = P_FILE
start-of-selection.
perform data_fetch_to_xls.
perform insertion.
*&      Form data_fetch_to_xls
*       text
* --> p1        text
* <-- p2        text
FORM data_fetch_to_xls .
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
    EXPORTING
      FILENAME                = P_FILE
      I_BEGIN_COL             = 1
      I_BEGIN_ROW             = 2
      I_END_COL               = 25
      I_END_ROW               = 2
    TABLES
      INTERN                  = IT_EXCEL
    EXCEPTIONS
      INCONSISTENT_PARAMETERS = 1
      UPLOAD_OLE              = 2
      OTHERS                  = 3.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    WRITE: /'ERROR UPLOADING XLS FILE FROM PRESENTATION SERVER !' ,
           /'RETURN CODE : ', SY-SUBRC.
ELSE.
*************NOW FILL DATA FROM EXCEL INTO FINAL LEGACY DATA ITAB----LEGACY_DATA***************
    IF NOT IT_EXCEL[] IS INITIAL.
      CLEAR LEGACY_DATA.
      REFRESH LEGACY_DATA[].
      LOOP AT IT_EXCEL.
        IT_EXCEL_DUMMY = IT_EXCEL.
        AT NEW COL.
          CASE IT_EXCEL_DUMMY-COL.
            WHEN 1.
              LEGACY_DATA-MATNR = IT_EXCEL_DUMMY-VALUE(18).
            WHEN 2.
              LEGACY_DATA-MBRSH = IT_EXCEL_DUMMY-VALUE(1).
            WHEN 3.
              LEGACY_DATA-MTART = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 4.
              LEGACY_DATA-WERKS = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 5.
              LEGACY_DATA-LGORT = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 6.
              LEGACY_DATA-VKORG = IT_EXCEL_DUMMY-VALUE(4).
             WHEN 7.
              LEGACY_DATA-VTWEG = IT_EXCEL_DUMMY-VALUE(2).
            WHEN 8.
              LEGACY_DATA-MAKTX = IT_EXCEL_DUMMY-VALUE(40).
            WHEN 9.
              LEGACY_DATA-MEINS = IT_EXCEL_DUMMY-VALUE(3).
            WHEN 10.
              LEGACY_DATA-MATKL = IT_EXCEL_DUMMY-VALUE(9).
            WHEN 11.
              LEGACY_DATA-SPART = IT_EXCEL_DUMMY-VALUE(2).
            WHEN 12.
              LEGACY_DATA-GROES = IT_EXCEL_DUMMY-VALUE(32).
            WHEN 13.
              LEGACY_DATA-FERTH = IT_EXCEL_DUMMY-VALUE(18).
            WHEN 14.
              LEGACY_DATA-ZEINR = IT_EXCEL_DUMMY-VALUE(22).
             WHEN 15.
              LEGACY_DATA-TAXKM1 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 16.
              LEGACY_DATA-TAXKM2 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 17.
              LEGACY_DATA-TAXKM3 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 18.
              LEGACY_DATA-TAXKM4 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 19.
              LEGACY_DATA-KTGRM = IT_EXCEL_DUMMY-VALUE(2).
            WHEN 20.
              LEGACY_DATA-MTVFP = IT_EXCEL_DUMMY-VALUE(2).
             WHEN 21.
              LEGACY_DATA-XCHPF = IT_EXCEL_DUMMY-VALUE(1).
            WHEN 22.
              LEGACY_DATA-TRAGR = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 23.
              LEGACY_DATA-LADGR = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 24.
              LEGACY_DATA-VPRSV = IT_EXCEL_DUMMY-VALUE(1).
            WHEN 25.
              LEGACY_DATA-VERPR = IT_EXCEL_DUMMY-VALUE(14).
              APPEND LEGACY_DATA.
              CLEAR LEGACY_DATA.
          ENDCASE.
        ENDAT.
        AT END OF ROW.
        ENDAT.
      ENDLOOP.
    ENDIF.
ENDIF.
ENDFORM.                    " data_fetch_to_xls
*&      Form insertion
*       text
* --> p1        text
* <-- p2        text
FORM insertion .
LOOP AT legacy_data.
* Header
BAPI_HEAD-MATERIAL = legacy_data-MATNR.
BAPI_HEAD-IND_SECTOR = legacy_data-MBRSH.
BAPI_HEAD-MATL_TYPE = legacy_data-MTART.
BAPI_HEAD-BASIC_VIEW = 'X'.
BAPI_HEAD-SALES_VIEW = 'X'.
BAPI_HEAD-STORAGE_VIEW = 'X'.
*BAPI_HEAD-PURCHASE_VIEW = 'X'.
BAPI_HEAD-ACCOUNT_VIEW = 'X'.
* Material Description
REFRESH IT_MAKT.
*IT_MAKT-LANGU = legacy_data-SPRAS.
IT_MAKT-MATL_DESC = legacy_data-MAKTX.
APPEND IT_MAKT.
BAPI_MARD1-PLANT = legacy_data-WERKS.
BAPI_MARD1-STGE_LOC = legacy_data-LGORT.
BAPI_MARDX1-PLANT = legacy_data-WERKS.
BAPI_MARDX1-STGE_LOC = legacy_data-LGORT.
** Client Data - Basic
BAPI_MARA1-MATL_GROUP = legacy_data-MATKL.
*bapi_mara1-OLD_MAT_NO = legacy_data-bismt.
BAPI_MARA1-BASE_UOM = legacy_data-MEINS.
BAPI_MARA1-PROD_MEMO = LEGACY_DATA-FERTH.
BAPI_MARA1-SIZE_DIM = LEGACY_DATA-GROES.
BAPI_MARA1-DOCUMENT = LEGACY_DATA-ZEINR.
BAPI_MARA1-BATCH_MGMT = LEGACY_DATA-XCHPF.
*BAPI_MARA1-UNIT_OF_WT = legacy_data-GEWEI.
BAPI_MARA1-TRANS_GRP = legacy_data-TRAGR.
BAPI_MARA1-DIVISION = legacy_data-SPART.
BAPI_MARAX-MATL_GROUP = 'X'.
*BAPI_MARAX-OLD_MAT_NO = 'X'.
BAPI_MARAX-BASE_UOM = 'X'.
BAPI_MARAX-PROD_MEMO = 'X'.
BAPI_MARAX-SIZE_DIM = 'X'.
BAPI_MARAX-DOCUMENT = 'X'.
BAPI_MARAX-BATCH_MGMT = 'X'.
*BAPI_MARAX-UNIT_OF_WT = 'X'.
BAPI_MARAX-TRANS_GRP = 'X'.
BAPI_MARAX-DIVISION = 'X'.
*SALES
BAPI_MVKE1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKE1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKE1-DELYG_PLNT = legacy_data-DWERK.
BAPI_MVKE1-ACCT_ASSGT = legacy_data-KTGRM.
BAPI_MVKEX1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKEX1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKEX1-DELYG_PLNT = 'X'.
BAPI_MVKEX1-ACCT_ASSGT = 'X'.
** Plant - Purchasing
BAPI_MARC1-PLANT = legacy_data-WERKS.
BAPI_MARC1-LOADINGGRP = legacy_data-LADGR.
BAPI_MARC1-AVAILCHECK = legacy_data-MTVFP.
*BAPI_MARC1-MRP_GROUP = legacy_data-disgr.
BAPI_MARCX-PLANT = legacy_data-WERKS.
BAPI_MARCX-LOADINGGRP = 'X'.
BAPI_MARCX-AVAILCHECK = 'X'.
*BAPI_MARCX-MRP_GROUP = 'X'.
* Accounting
BAPI_MBEW1-VAL_AREA = legacy_data-WERKS.
BAPI_MBEW1-PRICE_CTRL = legacy_data-VPRSV.
BAPI_MBEW1-STD_PRICE = legacy_data-VERPR.
*BAPI_MBEW1-VAL_CLASS = legacy_data-BKLAS.
*BAPI_MBEW1-STD_PRICE = legacy_data-STPRS.
*BAPI_MBEW1-PRICE_UNIT = legacy_data-PEINH.
BAPI_MBEWX-VAL_AREA = legacy_data-WERKS.
BAPI_MBEWX-PRICE_CTRL = 'X'.
BAPI_MBEWX-STD_PRICE = 'X'.
*BAPI_MBEWX-VAL_CLASS = 'X'.
* TAX JURISDICTION CODE
BAPI_MLAN1-TAXCLASS_1 = LEGACY_DATA-TAXKM1.
BAPI_MLAN1-TAXCLASS_2 = LEGACY_DATA-TAXKM2.
BAPI_MLAN1-TAXCLASS_3 = LEGACY_DATA-TAXKM3.
BAPI_MLAN1-TAXCLASS_4 = LEGACY_DATA-TAXKM4.
BAPI_MLAN1-TAXCLASS_1 = 'X'.
BAPI_MLAN1-TAXCLASS_2 = 'X'.
BAPI_MLAN1-TAXCLASS_3 = 'X'.
BAPI_MLAN1-TAXCLASS_4 = 'X'.
*--- BAPI to create material
call function 'BAPI_MATERIAL_SAVEDATA'
exporting
HEADDATA = BAPI_HEAD
CLIENTDATA = BAPI_MARA1
CLIENTDATAX = BAPI_MARAX
*PLANTDATA = BAPI_MARC1
*PLANTDATAX = BAPI_MARCX
* FORECASTPARAMETERS =
* FORECASTPARAMETERSX =
* PLANNINGDATA =
* PLANNINGDATAX =
* STORAGELOCATIONDATA =
* STORAGELOCATIONDATAX =
VALUATIONDATA = BAPI_MBEW1
VALUATIONDATAX = BAPI_MBEWX
* WAREHOUSENUMBERDATA =
* WAREHOUSENUMBERDATAX =
* SALESDATA = BAPI_MVKE1
* SALESDATAX = BAPI_MVKEX
* STORAGETYPEDATA =
* STORAGETYPEDATAX =
IMPORTING
RETURN = BAPI_RETURN
TABLES
MATERIALDESCRIPTION = IT_MAKT
* UNITSOFMEASURE =
* UNITSOFMEASUREX =
* INTERNATIONALARTNOS =
* MATERIALLONGTEXT =
* TAXCLASSIFICATIONS =
* RETURNMESSAGES =
* PRTDATA =
* PRTDATAX =
* EXTENSIONIN =
* EXTENSIONINX =
IF BAPI_RETURN-TYPE = 'E'.
WRITE:/ 'Error:' ,BAPI_RETURN-MESSAGE ,'for material:' ,legacy_data-maTNR.
ELSEIF BAPI_RETURN-TYPE = 'S'.
WRITE: 'Successfully created material' ,legacy_data-maTNR.
ENDIF.
ENDLOOP.
ENDFORM.                    " insertion
The error: The field MARC-MTVFP/BAPI_MARC-AVAILCHECK is defined as a required field; it does not contain an entr
suggestion will be vry helpful,
Kind Regards,
Edited by: Prasenjit Sengupta on Nov 16, 2009 9:11 AM

Hi Prasenjit,
Did you get any solution for this as I am getting same error from BAPI to update MRP controller in MARC table.
Regards,
Suruchi

Error - "Exception during parsing of upload document"

Hi,
I am getting following error when trying to upload data with my custom integrator:
"The upload process has completed with errors. Press Close to return to the document and fix the errors.
Upload processing did not complete
Exception during parsing of upload document"
My custom integrator was created for UPDATE mode with view AP_HOLDS_V and Release_Holds API. I also added Standalone Query (to limit downloaded data to not released holds and user releaseable). Layout contains only API parameters fields (however I had some context fields, but error message was the same then).
I am quite new to Web ADI and I still don't have full understanding, maybe someone can also answer following questions:
- what is mapping needed for? is this to map view/table fields with the layout field?
- how does integrator know which layout field should be mapped with parameters of API?
- is there no web adi template to modify columns assigned to interface? is this only possible with UPDATE commands?
- where is bne log file stored?
I would appreciate if someone can help. I was even debugging VBA macro to see if that error is on client or server side, but it looks like it is on the server side.
Regards
Piotr

Any idea what this error message means?
6/20/12 5:45 AM CRITICAL ERROR BneUploader::Exception - going to tollback
6/20/12 5:45 AM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
6/20/12 5:45 AM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
6/20/12 5:46 AM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
6/20/12 5:46 AM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
6/20/12 5:46 AM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
6/20/12 5:46 AM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
6/20/12 5:46 AM CRITICAL ERROR BneUploader.processUpload(), fatal exception: java.lang.ArrayIndexOutOfBoundsException: 8
6/20/12 5:46 AM CRITICAL ERROR java.lang.ArrayIndexOutOfBoundsException: 8
     at oracle.apps.bne.integrator.upload.BneRefPLSQLUpload.setupColumnNameMapping(BneRefPLSQLUpload.java:531)
     at oracle.apps.bne.integrator.upload.BneRefPLSQLUpload.preparePLSQLStatement(BneRefPLSQLUpload.java:371)
     at oracle.apps.bne.integrator.upload.BneRefPLSQLUpload.doUpload(BneRefPLSQLUpload.java:249)
     at oracle.apps.bne.integrator.upload.BneSAXUploader.processDeepestLevel(BneSAXUploader.java:2320)
     at oracle.apps.bne.integrator.upload.BneSAXUploader.startElement(BneSAXUploader.java:1178)
     at oracle.xml.parser.v2.XMLContentHandler.startElement(XMLContentHandler.java:167)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1182)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:175)
     at oracle.apps.bne.integrator.upload.BneUploader.processUpload(BneUploader.java:309)
     at oracle.apps.bne.integrator.upload.BneAbstractUploader.processUpload(BneAbstractUploader.java:117)
     at oracle.apps.bne.integrator.upload.async.BneAsyncUploadThread.run(BneAsyncUploadThread.java:141)
Edited by: PiotrekJ on 22-Jun-2012 01:59

PO attachment - Read error during upload

Hi Gurus,
I am getting the error when I am trying to attach any file in ME22N, by clicking the services for object button, create attachment, and select the attachment.
The error message is "Read error during PC upload" and "The attachement has not been created".
The system is upgraded to ECC 6 last year and have not tried this function before. Now the client want to use this functionality.
Thanks in advance.
Durai

Hi Charlie,
There is no message number appeared. In the bottom message bar " The attachment has not been created" appeared. In the seperate message window, " Read error during PC upload" is on the title and "Include file in the PC application, Try again?, is in the body.
Hope I clarified your doubt.
Thanks and regards
Durai

PO attachment error - Read error during PC upload

Hi Gurus,
I am getting the error when I am trying to attach any file in ME22N, by clicking the services for object button, create attachment, and select the attachment.
The error message is "Read error during PC upload" and "The attachemnt has not been created".
The system is upgraded to ECC 6 last year and have not tried this function before.
Thanks in advance.
Durai

Hi,
They are not using any interfaces (EDI), no idocs. They are using either fax or email and post modes only.
After saving the PO, we can able to attach the documents by clicking the services for object button in ME22N. But I am not able to attach the document to PO.
Thanks for your response.
Regards
Durai.

Read Error During PC Upload

Hi Experts,
When I attempt to attach a document to a PO (ME21N/ME22N) I get an error message say:
Read Error During PC Upload : Include File in PC Application
The funny thing is, some users can make attachments, others cannot. Is this a profile or authorization issue?
Thanks in advance!
SW

Hi Steven,
You cannot attach a file in ME21N trxn using Services for Object. For this you have to come out of Trxn ME21N after saving Po and again go to ME22N trxn code and in Menu System - Select Services for Object and Attach your File.
Be sure the File is not in use and closed.
Reg,
Ashok

Sql exception occurred during pl/sql upload error in custom integrator

Hi,
I have modified custom integrator which was working fine. I have added one column in template and the lov is working fine.
Issue is that when i upload the file to oracle it showing error as ''sql exception occurred during pl/sql upload".
I have tried executing the same from back end but it was working fine from back end and inserting properly in interface table.
Kindly suggest for the issue.
Regards,
Gk

Hi,
You can get the error message in excel sheet itself by using the following piece of code.
FND_MESSAGE.CLEAR;
FND_MESSAGE.SET_NAME ('APPLICATION', 'APPLICATION_MESSAGE_NAME');
FND_MESSAGE.SET_TOKEN ('ERROR_TOKEN', ERROR MESSAGE);
FND_MESSAGE.RAISE_ERROR;
Create an excpetion block and include the above piece of code whilde catching the exception.
APPLICATION- The applicatio in which you create message
APPLICATION_MESSAGE_NAME- The message Name
ERROR_TOKEN- You must create a token in application message
ERROR MESSAGE- You can see the error using SQLERRM.
Thanks,
Vinoop

MFBF bdc upload ERROR

hie gurus , can anyone help me , i have created a bdc upload for transaction MFBF repetitive manufacturing backflush
, when i upload a material with multiple production version i get an error , production version for material could not be
determined. initially its supposed to give a pop up window that allows me to select the production version, in the bdc recording so the pop window is not being called in the program for some reason i have not modified the recording
in anyway this is straight from sm35 recording to my z program :
perform bdc_dynpro      using 'SAPLBARM' '0800'.
perform bdc_field       using 'BDC_OKCODE'
                              '=GOON'.
perform bdc_field       using 'RM61B-RB_BAUGR'
                              'X'.
perform bdc_field       using 'RM61B-BUDAT'
                              '06.06.2011'.
perform bdc_field       using 'RM61B-BLDAT'
                              '06.06.2011'.
perform bdc_field       using 'BDC_CURSOR'
                              'RM61B-MATNR'.
perform bdc_field       using 'RM61B-MATNR'
                              '900-03-000'.
perform bdc_field       using 'RM61B-WERKS'
                              '1200'.
perform bdc_field       using 'RM61B-ERFMG'
                              '1111'.
error screen not being called
perform bdc_dynpro      using 'SAPLBARM' '0160'.
perform bdc_field       using 'BDC_CURSOR'
                              'MKAL-VERID(02)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=GOON'.
perform bdc_field       using 'RM61B-SELEK(02)'
                              'X'.

Hi Daniel,
Please check the BAPIs available in Function group 2127 if you can use any. That way you do not have to manipulate the screens in BDC.
Regards,
Shyam

Error in BDC upload

Hi,
I am facing a problem in BDC upload for hr master data tcode pa40.
I want to stop bdc after 3 screens and i dont want to processforthe remaining screens.
Can anyone help me onthis?
Thanks in advance.

Hi Anil,
I am regret to you becz i could nt tell thanks because i am full busy of my work.
Thanks a lot.
I have checked with your valuable logic. Now I am processing BDC upto two screens.
Regards,
Sreekanth

BDC Uploading - Organisation structure position error

Hi Gurus,
When we are uploading Master data through BDC its uploading in pa30 but its not updating positions in organization structure (PPOM_OLD - TCODE) . we cant find the holder under the position though we have upload the data and clear see the data in pa30 for that position.
when we are doing Action manually its updating the position. ofcourse its common too.
My question is why its not updaing the holder to the position when we are doing BDC upload
Any thoughts and suggestions.
Regards,
Ravi
Edited by: ravi Kumar on Jun 17, 2010 12:02 PM

First try this.
1. Execute RHINTE00 for one person
Selection screen
tick CREATE RELATIONSHIPS and CREATE HOLDER RELATIONSHIPS ONLY.
Remove the TEST tick and run.
First try for one person only then you can run it for others.
cheers
Ajay

Error while importing BDC models to SharePoint from SAP

Hi Team,
I am facing error while importing the BDC models to SharePoint from SAP Duet environment. Please find the attached screen shot and text document for reference.
Below are the tasks performed before importing the BDC models.
1) SSL & STS certificated created in the SharePoint environment.
2) Certificates are uploaded to the SAP duet environment.
3) SSL certificate created in SAP duet environment is uploaded to Trust location in SharePoint central admin.
Error while importing the BDC models manually through Central Admin.
Application definition while import failed. The following error occurred: The BDC model file is not well-formed. Data at root level is invalid at. Line 1,position 1.
C:\Program Files\Duet Enterprise\1.0>duetconfig/importbdc C:\Users\adm-in.itsupp
ort\Desktop\Rahul\BDC\models.xml
Starting import of models from C:\Users\adm-in.itsupport\Desktop\Rahul\BDC ...
Attempting to import model: Account
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '48' and Position: '20'.
Failed to import model: Account
Attempting to import model: AccountDocumentStorageCategory
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '46' and Position: '20'.
Failed to import model: AccountDocumentStorageCategory
Attempting to import model: AccountDocumentTypeStatus
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '46' and Position: '20'.
Failed to import model: AccountDocumentTypeStatus
Attempting to import model: AccountDocuments
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '46' and Position: '20'.
Failed to import model: AccountDocuments
Attempting to import model: AccountTitle
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '47' and Position: '20'.
Failed to import model: AccountTitle
Attempting to import model: BOM
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '46' and Position: '20'.
Failed to import model: BOM
Attempting to import model: Contact
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '46' and Position: '20'.
Failed to import model: Contact
Attempting to import model: ContactTitle
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '47' and Position: '20'.
Failed to import model: ContactTitle
Attempting to import model: CountryCode
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '48' and Position: '20'.
Failed to import model: CountryCode
Attempting to import model: CustomerInquiry
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '47' and Position: '20'.
Failed to import model: CustomerInquiry
Attempting to import model: CustomerInquiryItem
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '44' and Position: '20'.
Failed to import model: CustomerInquiryItem
Attempting to import model: CustomerInquiryPartner
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '44' and Position: '20'.
Failed to import model: CustomerInquiryPartner
Attempting to import model: CustomerQuotation
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '49' and Position: '20'.
Failed to import model: CustomerQuotation
Attempting to import model: CustomerQuotationItem
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '47' and Position: '20'.
Failed to import model: CustomerQuotationItem
Attempting to import model: CustomerQuotationPartner
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '47' and Position: '20'.
Failed to import model: CustomerQuotationPartner
Attempting to import model: Employee
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '46' and Position: '20'.
Failed to import model: Employee
Attempting to import model: InquiryItemDocument
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '49' and Position: '20'.
Failed to import model: InquiryItemDocument
Attempting to import model: InquiryItemDocumentStorageCategory
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '45' and Position: '20'.
Failed to import model: InquiryItemDocumentStorageCategory
Attempting to import model: InquiryItemDocumentTypeStatus
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '45' and Position: '20'.
Failed to import model: InquiryItemDocumentTypeStatus
Attempting to import model: JobFunction
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '47' and Position: '20'.
Failed to import model: JobFunction
Attempting to import model: Product
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '46' and Position: '20'.
Failed to import model: Product
Attempting to import model: ProductDocument
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '42' and Position: '20'.
Failed to import model: ProductDocument
Attempting to import model: ProductDocumentStorageCategory
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '45' and Position: '20'.
Failed to import model: ProductDocumentStorageCategory
Attempting to import model: ProductDocumentTypeStatus
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '45' and Position: '20'.
Failed to import model: ProductDocumentTypeStatus
Attempting to import model: QuotationItemDocument
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '45' and Position: '20'.
Failed to import model: QuotationItemDocument
Attempting to import model: QuotationItemDocumentStorageCategory
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '46' and Position: '20'.
Failed to import model: QuotationItemDocumentStorageCategory
Attempting to import model: QuotationItemDocumentTypeStatus
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '46' and Position: '20'.
Failed to import model: QuotationItemDocumentTypeStatus
Attempting to import model: ReportTemplate
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '49' and Position: '20'.
Failed to import model: ReportTemplate
Attempting to import model: Role
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '65' and Position: '20'.
Failed to import model: Role
Attempting to import model: UserRoles
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '42' and Position: '20'.
Failed to import model: UserRoles
Attempting to import model: SAP.Office.DuetEnterprise.Workflow.UserSubscription
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '42' and Position: '20'.
Failed to import model: SAP.Office.DuetEnterprise.Workflow.UserSubscription
Attempting to import model: SAP.Office.DuetEnterprise.Workflow
[ERROR] The remote certificate is invalid according to the validation procedure.
Error was encountered at or just before Line: '45' and Position: '11'.
Failed to import model: SAP.Office.DuetEnterprise.Workflow
[WARNING] Duet Enterprise configuration utility has completed importing the BDC
models but some models could not be imported. Review the logs for detailed infor
mation on the errors which occurred during the import operation.
Failed to import the following models -
Account
AccountDocumentStorageCategory
AccountDocumentTypeStatus
AccountDocuments
AccountTitle
BOM
Contact
ContactTitle
CountryCode
CustomerInquiry
CustomerInquiryItem
CustomerInquiryPartner
CustomerQuotation
CustomerQuotationItem
CustomerQuotationPartner
Employee
InquiryItemDocument
InquiryItemDocumentStorageCategory
InquiryItemDocumentTypeStatus
JobFunction
Product
ProductDocument
ProductDocumentStorageCategory
ProductDocumentTypeStatus
QuotationItemDocument
QuotationItemDocumentStorageCategory
QuotationItemDocumentTypeStatus
ReportTemplate
Role
UserRoles
SAP.Office.DuetEnterprise.Workflow.UserSubscription
SAP.Office.DuetEnterprise.Workflow
C:\Program Files\Duet Enterprise\1.0>
C:\Program Files\Duet Enterprise\1.0>
Qucik response is much appreciated.
Regards,
Rahul Reddy.

Take a look at this blog post,
http://brainof-dave.blogspot.com/2008/08/remote-certificate-is-invalid-according.html
Dimitri Ayrapetov (MCSE: SharePoint)

Unable to delete request from write-optimized DSO (Error during rollback)

Hi Gurus,
I am trying to delete a delta request from a Write-Optimized DSO. This request was uploaded with a DTP from another Write-optimized DSO.
The actual overall status of the request is RED and the description of that status is now: 'Error during rollback of request DTPR_4JW6NLSVDUNYY3GTD6F4DQJWR; only rollback allowed'.
I checked the log of all Request Operations in DataStore (from the same line where the red request is now) and I see my several attemps to delete this request under a RED radiobutton with the title Rollback. The details for this error are the following:
Could not delete request data from active table
Message no. RSODSO_ROLLBACK114
Diagnosis
The system could not delete the request data from the active table of a write-optimized DataStore object.
System Response
Write-optimized DataStore object: DTFISO02
Active table: /BIC/ADTFISO0200
Request: DTPR_4JW6NLSVDUNYY3GTD6F4DQJWR
Procedure
Search for Notes containing the key words "Delete write-optimized DSO PSA"
I am relatively new to SAP BI 7.0 and I do not know how to delete this request. Any help will be highly appreciated !!
Leticia

Hi Leticia:
Take a look at the SAP Notes below.
Note 1111065 - "701: Delta consistency check for write-optimized DSOs"
Note 1263877 - "70SP20: Delta consistency check for write-optimized DSOs"
Note 1125025 - "P17:PSA:DSO:ODSR missing in PSA process for write-opt. DSO"
Additionally, some ideas from the alternative presented on the blog by KMR might help you.
"How to generate a selective deletion program for info provider"
Regards,
Francisco Mílán.

Error during phase XPRAS_TRANS in module MAIN_TRANSEXEC while updating to EHP7 on HANA

Dear Gurus,
I request your help to resolve the below mentioned error.
I got the below error while updating my system from EHP6 to EHP7 SPS03.
The details of the logs and the versions are mentioned below for your reference:
SAPup_troubleticket.log
SAPup broke during phase XPRAS_TRANS in module MAIN_TRANSEXEC / Downtime for transport mode
Error Message: Detected 99 errors summarized in 'XPRASUPG.ELG'
Calling 'E:\usr\sap\ERH\DVEBMGS00\exe/tp' failed with return code 8, check F:\SUM\SUM\abap\log\SAPup.ECO for details
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-617BRINSAPAPPL.ERH
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A3 ESNHI_DELIVERY_UNIT 007 Number of deleted objects: "0"
A3 ESNHI_DELIVERY_UNIT 010 A complete HANA delivery unit was imported.
A3 ESNHI_DELIVERY_UNIT 013 Content snapshot was uploaded in source system " " at " ".
A3 ESNHI_DELIVERY_UNIT 014 Details: Vendor " ", Version " ", Support Package " ", Patch " "
A3 ESNHI_DELIVERY_UNIT 081 HANA delivery unit name: " "
A2EESNHI_DELIVERY_UNIT 080 Aggregated import of HANA Delivery Units failed
A4EESNHI_DELIVERY_UNIT 025 "Repository: Encountered an int""ernal error in the repository""code, this is most likely a bu""g in the implementation;failed"
A4EESNHI_DELIVERY_UNIT 025 "to write attached content to""file"" "" "
A3 ESNHI_DELIVERY_UNIT 007 Number of deleted objects: "0"
A3 ESNHI_DELIVERY_UNIT 010 A complete HANA delivery unit was imported.
A3 ESNHI_DELIVERY_UNIT 013 Content snapshot was uploaded in source system " " at " ".
A3 ESNHI_DELIVERY_UNIT 014 Details: Vendor " ", Version " ", Support Package " ", Patch " "
A3 ESNHI_DELIVERY_UNIT 081 HANA delivery unit name: " "
A2EESNHI_DELIVERY_UNIT 080 Aggregated import of HANA Delivery Units failed
A4EESNHI_DELIVERY_UNIT 025 "Repository: Encountered an int""ernal error in the repository""code, this is most likely a bu""g in the implementation;failed"
A4EESNHI_DELIVERY_UNIT 025 "to write attached content to""file"" "" "
2EEPU133 Errors occurred during post-handling "SNHI_DELIVERY_UNIT_IMPORT" for "NHDU" "L"
3 EPU135 "SNHI_DELIVERY_UNIT_IMPORT" belongs to package "SNHI_DELIVERY_UNIT_PROXY"
2EEPU136 The errors affect the following components:
2EEPU137    "BC-DWB-AIE-AHI" ("Tools for ABAP and HANA Integration")
1 ETP111 exit code           : "8"
Details of the version:
Start Release:        731
Target Release:        740
OS Type:        Windows NT X86_64
OS Version:        6.1
Database Type:        hdb
Database Version:    1.00.70.00.386119
SUM Version:            Patch 0 for SOFTWARE UPDATE MANAGER 1.0 SP10
As per the release note 1737650 - EHP7 for SAP ERP 6.0 SP Stacks - Release & Information Note, I have to follow the below note :
1981346    SAP HANA activation error during XPRA phase
But I am not pretty sure if I can ignore this and go ahead , and then do the actions as mentioned in the note, as the symptom says "The error message in the log file tells you that the MultipleFiles repository import failed.", which is not my case.
I have searched for SAP Notes with the below keywords but did not find any relevant , either there is a version mismatch or does not apply to the above error :
SNHI_DELIVERY_UNIT_IMPORT
SNHI_DELIVERY_UNIT_PROXY
Aggregated import of HANA Delivery Units failed
Errors occurred during post-handling "SNHI_DELIVERY_UNIT_IMPORT"
Please help me to resolve the issue.
Kind Regards,
Anuj

Hi Anuj,
Can you check index server trace for more details into the error .
Based on the error message please check whether below SAP notes are valid
1996489 - Aggregated import of HANA Delivery Units failed with PackageStoreAccessor::createPackages
1996392 - Multiple delivery unit import fails with error code 301
Hope this helps.
Regards,
Deepak Kori

Error during MB11 bdc-upload

Similar Messages

Maybe you are looking for