Error while calculating download files automatically

Hello All,
I have configured Maintenance Optimizer for Solution Manager 7.0 Ehp1. When i created a new Maintenance Transaction, it is displaying an error "System is not assigned to a host, There are no operating system/database-dependent files for your selection." after choosing the stack level.
Can anyone say what might be the problem?
Thanks,
Regards,
Hasan

Hi
as per the workarround this error got resolved after the proper maintaining Java technical system details for Java product instance and the port details.
hence please check and  enter the dispatcher, port number, & database schema on the Header tab, and the J2EE-Server on the Instances tab,
check the sap notes
Note 1176842 - Maintenance optimizer reports missing host assignment
Note 1121045 - Missing host assignment in Maintenance Optimizer
and the thread
[MOPZ - System is not assigned to a host|MOPZ - System is not assigned to a host]
Thanks,
Jansi

Similar Messages

  • Error while uploading text file....

    Halo Friends,
    I am uploading 4 text files which contain three columns separated by a tab, but when i am trying to upload those files using WS_UPLOAD Function Module i am getting a runtime error saying 'error while uploading/downloading'.
    Please solve this problem as soon as possible.
    Thanks in Advance,
    rama

    Halo again,
    Now that i am able to upload the files, i need to update the database table the update statement is executing correctly but when i debug i see that the sy-subrc value is 4 but not 0.
    and hence the it is not committed.
    Any suggestions. i am pasting my code here for your reference:
    Tables: qmfe.
    data: begin of gt1_qmfe occurs 0,
          qmnum       like qmfe-qmnum,
          fenum       like qmfe-fenum,
          /itml/usr20 like qmfe-/itml/usr20,
          end of gt1_qmfe.
    data: begin of gt2_qmfe occurs 0,
          qmnum       like qmfe-qmnum,
          fenum       like qmfe-fenum,
          /itml/usr21 like qmfe-/itml/usr21,
          end of gt2_qmfe.
    data: begin of gt3_qmfe occurs 0,
          qmnum       like qmfe-qmnum,
          fenum       like qmfe-fenum,
          /itml/usr19 like qmfe-/itml/usr19,
          end of gt3_qmfe.
    data: begin of gt4_qmfe occurs 0,
          qmnum       like qmfe-qmnum,
          fenum       like qmfe-fenum,
          /itml/usr07 like qmfe-/itml/usr07,
          end of gt4_qmfe.
    data: gs1_qmfe like line of gt1_qmfe,
          gs2_qmfe like line of gt2_qmfe,
          gs3_qmfe like line of gt3_qmfe,
          gs4_qmfe like line of gt4_qmfe.
    data: ls_lines1 type i,
          ls_lines2 type i,
          ls_lines3 type i,
          ls_lines4 type i.
    parameters: ip_file1 type RLGRAP-FILENAME default 'C:\Urgent\TextFiles\StoDt.txt'     obligatory,
                ip_file2 type RLGRAP-FILENAME default 'C:\Urgent\TextFiles\RcDtCust.txt'  obligatory,
                ip_file3 type RLGRAP-FILENAME default 'C:\Urgent\TextFiles\DockDate.txt'  obligatory,
                ip_file4 type RLGRAP-FILENAME default 'C:\Urgent\TextFiles\AWB.txt'       obligatory.
    field-symbols: <fs1> like gs1_qmfe,
                   <fs2> like gs2_qmfe,
                   <fs3> like gs3_qmfe,
                   <fs4> like gs4_qmfe.
    perform upload_gt1_qmfe.
    perform upload_gt2_qmfe.
    perform upload_gt3_qmfe.
    perform upload_gt4_qmfe.
    perform update_qmfe.
    *&      Form  upload_gt1_qmfe
          text
    -->  p1        text
    <--  p2        text
    FORM upload_gt1_qmfe .
    CALL FUNCTION 'WS_UPLOAD'
    EXPORTING
       FILENAME                      = ip_file1
       FILETYPE                      = 'DAT'
      TABLES
        DATA_TAB                      = gt1_qmfe.
    describe table gt1_qmfe lines ls_lines1.
    write: / ls_lines1.
    ENDFORM.                    " upload_gt1_qmfe
    *&      Form  upload_gt2_qmfe
          text
    -->  p1        text
    <--  p2        text
    FORM upload_gt2_qmfe .
    CALL FUNCTION 'WS_UPLOAD'
    EXPORTING
       FILENAME                      = ip_file2
       FILETYPE                      = 'DAT'
      TABLES
        DATA_TAB                      = gt2_qmfe.
    describe table gt2_qmfe lines ls_lines2.
    write: / ls_lines2.
    ENDFORM.                    " upload_gt2_qmfe
    *&      Form  upload_gt3_qmfe
          text
    -->  p1        text
    <--  p2        text
    FORM upload_gt3_qmfe .
    CALL FUNCTION 'WS_UPLOAD'
    EXPORTING
       FILENAME                      = ip_file3
       FILETYPE                      = 'DAT'
      TABLES
        DATA_TAB                      = gt3_qmfe.
    describe table gt3_qmfe lines ls_lines3.
    write: / ls_lines3.
    ENDFORM.                    " upload_gt3_qmfe
    *&      Form  upload_gt4_qmfe
          text
    -->  p1        text
    <--  p2        text
    FORM upload_gt4_qmfe .
    CALL FUNCTION 'WS_UPLOAD'
    EXPORTING
       FILENAME                      = ip_file4
       FILETYPE                      = 'DAT'
      TABLES
        DATA_TAB                      = gt4_qmfe.
    describe table gt4_qmfe lines ls_lines4.
    write: / ls_lines4.
    ENDFORM.                    " upload_gt4_qmfe
    *&      Form  update_qmfe
          text
    -->  p1        text
    <--  p2        text
    FORM update_qmfe .
    data ls_cnt type i.
    loop at gt1_qmfe assigning <fs1>.
    update qmfe set    /itml/usr20 = <fs1>-/itml/usr20
                where  qmnum       = <fs1>-qmnum
                and    fenum       = <fs1>-fenum.
    if sy-subrc = 0.
    commit work.
    add 1 to ls_cnt.
    endif.
    endloop.
    write: / ls_cnt.
    ENDFORM.                    " update_qmfe

  • Error while opening the file store file "WLS_DIAGNOSTICS000000.DAT".....

    I have a WL 9.2.1 running on Sun solaris o/s .....it is failing to start thowing the following exception
    <Mar 19, 2009 5:21:17 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.diagnostics.lifecycle.DiagnosticComponentLifecycleException: weblogic.store.PersistentStoreException: java.io.IOException: [Store:280021]There was a
    n error while opening the file store file "WLS_DIAGNOSTICS000000.DAT"
    at weblogic.diagnostics.lifecycle.ArchiveLifecycleImpl.initialize(ArchiveLifecycleImpl.java:44)
    at weblogic.diagnostics.lifecycle.DiagnosticFoundationService.start(DiagnosticFoundationService.java:107)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Caused by: weblogic.store.PersistentStoreException: java.io.IOException: [Store:280021]There was an error while opening the file store file "WLS_DIAGNOSTICS0
    00000.DAT"
    at weblogic.store.io.file.Heap.open(Heap.java:166)
    at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:85)
    at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:350)
    at weblogic.store.PersistentStoreManager.createFileStore(PersistentStoreManager.java:202)
    at weblogic.diagnostics.archive.DiagnosticStoreRepository.getStore(DiagnosticStoreRepository.java:61)
    at weblogic.diagnostics.lifecycle.ArchiveLifecycleImpl.initialize(ArchiveLifecycleImpl.java:42)
    ... 4 more
    Caused by: java.io.IOException: [Store:280021]There was an error while opening the file store file "WLS_DIAGNOSTICS000000.DAT"
    at weblogic.store.io.file.StoreDir.throwIOException(StoreDir.java:213)
    at weblogic.store.io.file.StoreDir.open(StoreDir.java:103)
    at weblogic.store.io.file.Heap.open(Heap.java:164)
    ... 9 more
    Caused by: java.io.IOException: Error from fcntl() for file locking, Resource temporarily unavailable, errno=11
    at weblogic.store.io.file.direct.DirectIONative.open(Native Method)
    at weblogic.store.io.file.direct.DirectFileChannel.<init>(DirectFileChannel.java:51)
    at weblogic.store.io.file.direct.DirectIOManager.open(DirectIOManager.java:138)
    at weblogic.store.io.file.StoreFile.openInternal(StoreFile.java:112)
    at weblogic.store.io.file.StoreFile.open(StoreFile.java:142)
    at weblogic.store.io.file.StoreDir.open(StoreDir.java:95)
    ... 10 more
    i went ahead and checkd the file and the privs on the file they look correct -rw-r--r-- ...but when i just restart it ..it starts with no errors the next time......What could be the issue.....please help
    Then only reason i could think of is the size of the file is 35MB now...is this the problem....if yes....is there a way to automaticaly rotate this file ....

    The root cause appears to be right in the stack trace:
    Caused by: java.io.IOException: Error from fcntl() for file locking, Resource temporarily unavailable, errno=11I think this indicates that either the file was either locked (because another instance of WebLogic had it opened), or that the file was unavailable for some reason. WebLogic locks files as a safety precaution to prevent misconfigured setups (multiple domains sharing the same directory and store name) from attempting to share the same file.
    I don't think that this message necessarily means there is a file corruption.
    As for rotation, the file store automatically adds new files as needed (I think its 1 file for every 2GB of data). The "diagnostics" file store is generated by the optional diagnostics feature, and I think that this feature has options for controlling the amount of stored data.
    Tom

  • Error while writing to file: C: \ Program Files (x86) \ iTunes \ iTunes.Resources \ el.Iproj \ iTunesExtrasDownload.png. Make sure you have access to this directory.

    When i try to install iTunes in my Windows 7, this error message apear "Error while writing to file: C: \ Program Files (x86) \ iTunes \ iTunes.Resources \ el.Iproj \ iTunesExtrasDownload.png. Make sure you have access to this directory." Someone help me!!

    That one's consistent with disk/file damage. The first thing I'd try with that is running a disk check (chkdsk) over your C drive.
    XP instructions in the following document: How to perform disk error checking in Windows XP
    Vista instructions in the following document: Check your hard disk for errors
    Windows 7 instructions in the following document: How to use CHKDSK (Check Disk)
    Select both Automatically fix file system errors and Scan for and attempt recovery of bad sectors, or use chkdsk /r (depending on which way you decide to go about doing this). You'll almost certainly have to schedule the chkdsk to run on startup. The scan should take quite a while ... if it quits after a few minutes or seconds, something's interfering with the scan.
    Does the chkdsk find/repair any damage? If so, can you get an install to go through properly afterwards?

  • Error while creating control file

    hi
    i am getting following error while creating controll file
    QL> shutdown
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area  629145600 bytes
    Fixed Size                  1250548 bytes
    Variable Size             171969292 bytes
    Database Buffers          452984832 bytes
    Redo Buffers                2940928 bytes
    SQL> @c:\study\rose\c.sql
    SP2-0042: unknown command "DATAFILE" - rest of line ignored.
    SP2-0734: unknown command beginning "'C:\ORACLE..." - rest of line ignored.
    SP2-0734: unknown command beginning "'C:\ORACLE..." - rest of line ignored.
    SP2-0734: unknown command beginning "CHARACTER ..." - rest of line ignored.
    SP2-0044: For a list of known commands enter HELP
    and to leave enter EXIT.
    1  CREATE CONTROLFILE SET DATABASE "ROSE" RESETLOGS  froce logging NOARCHIVELOG
    2      MAXLOGFILES 32
    3      MAXLOGMEMBERS 2
    4      MAXDATAFILES 32
    5      MAXINSTANCES 16
    6      MAXLOGHISTORY 1752
    7  LOGFILE
    8  GROUP 1 'C:\oracle\product\10.2.0\oradata\rose\LOG1ROSE.ORA'  SIZE 50M,
    9    GROUP 2 'C:\oracle\product\10.2.0\oradata\rose\LOG2ROSE.ORA'  SIZE 50M,
    10   GROUP 3 'C:\oracle\product\10.2.0\oradata\rose\LOG06.LOG'  SIZE 25M,
    11*   GROUP 4 'C:\oracle\product\10.2.0\oradata\rose\LOG07.LOG'  SIZE 25M
    SQL>

    CHETAN YADAV wrote:
    hi
    i am getting following error while creating controll file
    QL> shutdown
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area  629145600 bytes
    Fixed Size                  1250548 bytes
    Variable Size             171969292 bytes
    Database Buffers          452984832 bytes
    Redo Buffers                2940928 bytes
    SQL> @c:\study\rose\c.sqlWe can't debug what we can't see. And what we can't see is the contents of "c:\study\rose\c.sql".
    SP2-0042: unknown command "DATAFILE" - rest of line ignored.
    SP2-0734: unknown command beginning "'C:\ORACLE..." - rest of line ignored.
    SP2-0734: unknown command beginning "'C:\ORACLE..." - rest of line ignored.
    SP2-0734: unknown command beginning "CHARACTER ..." - rest of line ignored.
    SP2-0044: For a list of known commands enter HELP
    and to leave enter EXIT.
    1 CREATE CONTROLFILE SET DATABASE "ROSE" RESETLOGS froce logging NOARCHIVELOG
    2 MAXLOGFILES 32
    3 MAXLOGMEMBERS 2
    4 MAXDATAFILES 32
    5 MAXINSTANCES 16
    6 MAXLOGHISTORY 1752
    7 LOGFILE
    8 GROUP 1 'C:\oracle\product\10.2.0\oradata\rose\LOG1ROSE.ORA' SIZE 50M,
    9 GROUP 2 'C:\oracle\product\10.2.0\oradata\rose\LOG2ROSE.ORA' SIZE 50M,
    10 GROUP 3 'C:\oracle\product\10.2.0\oradata\rose\LOG06.LOG' SIZE 25M,
    11* GROUP 4 'C:\oracle\product\10.2.0\oradata\rose\LOG07.LOG' SIZE 25M
    SQL>

  • Error while converting class file to exp and jca file

    error while converting *.class file to *.exp and *.jca file
    =====================================================================================================================
    linux-y60u:/home/admin/java_card_kit-2_2_1/samples/src # converter -exportpath "/home/admin/java_card_kit-2_2_1/lib/" com/sun/javacard/samples/HelloWorld 0x00:0x01:0x02:0x03:0x04:0x05:0x06:0x07:0x0b 1.0 -v -applet 0x00:0x01:0x02:0x03:0x04:0x05:0x06:0x07:0x0b:0x01 Identity
    Java Card 2.2.1 Class File Converter, Version 1.3
    Copyright 2003 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.
    parsing /home/admin/java_card_kit-2_2_1/samples/src/com/sun/javacard/samples/HelloWorld/HelloWorld.class
    parsing /home/admin/java_card_kit-2_2_1/samples/src/com/sun/javacard/samples/HelloWorld/Identity.class
    error: com.sun.javacard.samples.HelloWorld.HelloWorld: unsupported class file format of version 50.0.
    error: com.sun.javacard.samples.HelloWorld.Identity: unsupported class file format of version 50.0.
    conversion completed with 2 errors and 0 warnings.
    =====================================================================================================================

    i compile a file javacard use this command:
    ===
    javac -source 1.3 -target 1.1 -g -classpath ./classes:../lib/api.jar:../lib/installer.jar src/com/sun/javacard/samples/Identity/Identity.java
    ===
    and try to convert this class use this command
    ===
    /home/xnuxerx/admin/java_card_kit-2_2_1/bin/converter -exportpath "/home/xnuxerx/admin/java_card_kit-2_2_1/lib/" com/sun/javacard/samples/Identity 0x00:0x01:0x02:0x03:0x04:0x05:0x06:0x07:0x0b 1.0 -v -applet 0x00:0x01:0x02:0x03:0x04:0x05:0x06:0x07:0x0b:0x01 Identity
    ===
    result convert:
    ===
    Java Card 2.2.1 Class File Converter, Version 1.3
    Copyright 2003 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.
    parsing /home/xnuxerx/admin/java_card_kit-2_2_1/samples/classes/com/sun/javacard/samples/Identity/Identity.class
    converting com.sun.javacard.samples.Identity.Identity
    error: export file framework.exp of package javacard.framework not found.
    conversion completed with 1 errors and 0 warnings.
    ===
    why ??
    please your comment for this problem.
    thank 4 all.

  • Error while deleting a file which is in a folder which inturn in workspace

    12:20:42.309  DELETE  (FAILED: Conflict [(pre||post)-condition failed: x:concurrency-lock-denied])  Hello.java   (C:\CFolder1\WSF1\WSF2\Dev\HelloWorld\Package\Hello.java)
    --- Problem summary: ---
    12:20:42.309  DELETE  (FAILED: Conflict [(pre||post)-condition failed: x:concurrency-lock-denied])  Hello.java   (C:\CFolder1\WSF1\WSF2\Dev\HelloWorld\Package\Hello.java)
    I am getting above error while deleting a file which is in a folder which inturn in workspace

    Here is the problem I have with deleting my folder. I had created a WD project TaxTool and and added the DC to my SC. There were obviously some checkedout activities. Being new to this, I deleted the project directly without checking in the activities. Now I have folder TaxTool/_comp with nothing underneath on the DTR server and on my client. I am unable to checkout TaxTool for delete but the checkout of _comp folder fails in NWDS with the following error:
    <b>EDIT  (FAILED: server response: Conflict [(pre||post)-condition failed: x:no-exclusivity-with-existing-checked-out-resources])  comp   (C:\JDI\JDIDEMO1\intelJDI_TEST\dev\inactive\DCs\intel.com\TaxTool\_comp\)</b>
    If I try the same from the DTR shell, I get this following error:
    <b>Unexpected problem occurred during executing command.Lockfile "C:\Documents and
    Settings\bvedamur\.dtr\.syncdbs\5b0d8b2110a7a29883734c0407462df8.syncdbM.lock" is already in use by another process.</b>
    I am the only user in the system (doing R&D) and I have tried Sync and Delete. Nothing works. Help appreciated.
    Thx
    Bhaskar

  • EXPORT XFA error while writing XFA files

    Hello Experts,
    We are facing an error while exporting to PDF from BEx report.
    We are on EP7 SP14. BI on SP16.
    After the report is displayed and Export to PDF button is clicked, a new window opens which shows following:
    1. Error:
    Message: No message was provided.
    Stack trace: java.lang.NullPointerException
    at com.sap.ip.bi.export.model.layout.impl.Margins.<init>(Margins.java:32)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.<init>(CellLayout.java:48)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.dub(CellLayout.java:57)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.createCell(TableContentIterator.java:170)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.next(TableContentIterator.java:104)
    at com.sap.ip.bi.export.xfa.xftextensions.TableSubFormSet.writeXFD(TableSubFormSet.java:1189)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_template.writeXFD(Xft_template.java:216)
    at com.sap.ip.bi.export.xfa.core.Xft.writeXFD(Xft.java:62)
    at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:294)
    at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
    at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:96)
    at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:626)
    at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:405)
    at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:325)
    at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:71)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:593)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:132)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:349)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.buildRenderingTree(Page.java:4494)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:4568)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:4204)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:4150)
    at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:2948)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2794)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:994)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller._processRequest(Controller.java:883)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:860)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:359)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:276)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java
    :33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Message: EXPORT XFA error while writing XFA files
    Stack trace: com.sap.ip.bi.base.exception.BIBaseRuntimeException: EXPORT XFA error while writing XFA files
    at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:311)
    at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
    at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:96)
    at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:626)
    at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:405)
    at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:325)
    at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:71)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:593)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:132)
    at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:349)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.buildRenderingTree(Page.java:4494)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:4568)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:4204)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:4150)
    at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:2948)
    at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2794)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:994)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller._processRequest(Controller.java:883)
    at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:860)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:359)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:276)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java
    :33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NullPointerException
    at com.sap.ip.bi.export.model.layout.impl.Margins.<init>(Margins.java:32)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.<init>(CellLayout.java:48)
    at com.sap.ip.bi.export.model.layout.impl.CellLayout.dub(CellLayout.java:57)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.createCell(TableContentIterator.java:170)
    at com.sap.ip.bi.export.xfa.xftextensions.TableContentIterator.next(TableContentIterator.java:104)
    at com.sap.ip.bi.export.xfa.xftextensions.TableSubFormSet.writeXFD(TableSubFormSet.java:1189)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_subform.writeXFD(Xft_subform.java:1604)
    at com.sap.ip.bi.export.xfa.core.Xft_template.writeXFD(Xft_template.java:216)
    at com.sap.ip.bi.export.xfa.core.Xft.writeXFD(Xft.java:62)
    at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:294)
    2. Message:
    No metadata is available for "DISABLE_NAVIGATION":
    <parameterList>
      <param name="BI_COMMAND_TYPE" value="OPEN_DIALOG_DISABLE_NAVIGATION"/>
      <param name="TARGET_DIALOG_REF" value="DISABLE_NAVIGATION"/>
    </parameterList>
    In this window, complete screen of report is displayed as an image instead of PDF.
    Please let me know if anybody faced similar issue earlier.
    It was working perfect earlier, but suddenly error started.
    regards
    Kedar Kulkarni

    No proper findings, but issue resolved.
    Problem i found that we got a domain change and service values were not refreshed until we apply new patch.
    So when we applied patch level 6 on BI WEBAPP& BI BASE S URL for ADS got refreshed and we faced the issue.
    After resetting the URL to new domain problem got resolved.
    Regards
    Kedar Kulkarni

  • Error while calculating the net present value

    Dear experts,
    Please help me in solving the following error.
    I am trying to do project vaibility analysis through pre investment analysis in appropriation request, interm I'm trying to calculate the IRR for the project.
    I have created the appropriation request and given all the data in that including the planed values for the project.
    In Variants tab of appropriation request, preinv. analysis sub tab, i have clicked the button Calculate preinvestment analysis figures , ( I hvae not mentioned any values in that screen, its picking the plan cost from the planed values of the appropriation request) there I'm getting an error saying
    Error while calculating the net present value
    If I open the message it is as follows:
    Error while calculating the net present value*
    *Message no. AO215*
    Diagnosis
    An error occurred during calculation of the net present value.
    The yield curve for determining the net present value is not completely maintained. Possible causes are:
    1. Evaluation type IM01 does not exist (table ATSYC).
    2. Yield curve types 9990 (bid) and 9991 (ask) have not been created (table JBD14) for the currency of the controlling area of the appropriation request.
    3. Reference interest rates have not been created for the yield curves (tables T056R and JBD15).
    4. Interest rates are not maintained for the complete planning time period for the reference interest rates.
    5. Under certain circumstances, the standard exchange rate types 'G' and 'B' may be inconsistent.
    Procedure
    Check your Customizing settings:
    1. SAP supplies the evaluation types.
    Remember, SAP supplies the evaluation types in client 000. You have to copy them into your working clients. If you do not have them in your system, you can create them in Customizing for the Treasury component (Treasury Management -> Market Risk Management -> Evaluations -> Define Default Settings). Create evaluation type IM01 with bid yield curve type 9990 and ask yield curve type 9991.
    2. In Customizing for appropriation requests (under Planning), create a bid yield curve type 9990 and an ask yield curve type for the currency of the controlling area of the appropriation request.
    3. Create at least one reference interest rate for each yield curve.
    4. Maintain the reference rates, starting at the minimum fron the point at which you you have planned costs or revenue.
    5. Check Customizing of the exchange rate types 'G' and 'B' in the IMG under Global Settings -> Currencies.
    I have checked all the procedures of the said customization and the values are similar to that of the error message, but still I'm unable to proceed further.
    I have goe through the note 160375, but did not succeed on this issue.
    Can any one help me out in solving the above error and also can any one explain me the process in SAP to calculate IRR?
    Is there any more customization missing or whats wrong going in that process?
    Please help me out...
    Thanks in advance..
    Regards,
    Praveen.

    Are you installing a Demo version of NetWeaver? If so please post your questions and search for answers here: SAP NetWeaver Application Server
    If this a real full blown system please contact the OSS, via the Marketplace (service.sap.com) or by OSS transaction in your SAP System.

  • Error while reading wsdl file

    I created and deployed a BPEL process with a JMS adapter and DB adapter.
    I have tested this and it works fine.
    After a few days, I try to open the project and the BPEL process, and click on the DB
    adapter and it throws an exception on the designer :
    "Error while reading wsdl file ... (wsdl file name) NULL Exception"
    This is hard to debug as the exception does not provide any info, NULL.
    This has happened several times for my project. The next time the JMS adapter hit the
    same exception while opening on designer. This one I notice happened after I imported
    a new schema file (xsd) into the BPEL process.
    Only way around that I have for this currently is to delete and recreate the adapters, which as time
    consuming as I have to re-create and re-assign a lot of the activities.
    Has anyone encountered this and is there a way to fix this without deleting/recreating the adapters ?
    Thanks.

    I experienced the same issue and found the cause and a workaround;
    "Error while reading wsdl file …. Exception: null"
    http://www.petervannes.nl/files/b7c08911ce3cde3677e2182bbc5f032a-47.php
    Edited by: 944333 on Jul 3, 2012 10:24 PM

  • Error while writing wsdl file

    Hi,
    i' m working on jdeveloper 10.1.3.1.0 and when i want to add a partner link to my BPEL project i get 'error while writing wsdl file' 'exception null' error then i couldn't create file.
    so how can i solve this problem?
    HELP:)

    Once the wrapper procedure is created by the adapter, the adapter does a second search to obtain the information about the wrapper (i.e. parameters, their data types, etc.). What's likely happening here is that the wrapper is getting created, but the adapter can't find it. The XSD is based on the wrapper, so if it can't be found, then no XSD can be generated. Try removing the existing wrapper package or choose that option in the wizard when it generates a new one.

  • Error while creating logical file using transaction FILE

    Hello there,
    I am facing an error while creating Logical File name definition using transaction FILE
    This is the input which I'm trying to give
    Logical file name: ZTEST
    Name : ZTEST
    Physical file : ZTEST_1<DATE><TIME>.csv
    Data format: ASC
    Application area: BW
    Logical path:ZTEST_1_DATAOUT
    when I tried to save it throws me an error like  ASSIGN_SUBSTRING_NOT_ALLOWED
    Please help.

    Hi,
    Please check the OSS Notes :
    Note 792061 - SP Case Locator: Dump: ASSIGN to a substring isn't allowed.
    SAP Note 1297989 - Short dump ASSIGN_SUBSTRING_NOT_ALLOWED
    Hope this solves the problem.
    -Vikram

  • Error while importing .xml file in Datatype

    Hi SDN,
    I am getting this error while importing .xml file in Datatype.
    Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8
    Actually I have created datatype in my development box..
    but my client doesn't want to develop in development box.
    so i have exported that datatype as xsd from datatype editor.
    and while importing into sandbox datatype editor i am getting this error..
    Any help please......

    Hi Rajeev,
    now i have an .xml file its not importing into datatype...
    error is
    Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8))
      <?xml version="1.0" encoding="UTF-8" ?>
      <xsd:schema targetNamespace="http://abc.com/xa" xmlns="http://abc.com/xa" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <xsd:complexType name="DT_PLANNINGSCHEDULE">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">3c6ae480f2f111dbc7ac0002556ad065</xsd:appinfo>
      </xsd:annotation>
      <xsd:sequence>
      <xsd:element name="PlanningSchedule_Output">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">c65d41c0f15b11dbb29f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PlanningScheduleHeader">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">c65d41c1f15b11dbb6ef00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ScheduleID" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">6c804600f15d11dbc02400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleIssueDate" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d0f15d11db8dd800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="SchedulePurpose">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d1f15d11dbac4100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Purpose">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd50f15e11db9eb600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PurposeCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd51f15e11dbc47a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ScheduleTypeCoded" type="xsd:string">
    <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d2f15d11dbbc3900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleTypeCodedOther" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d3f15d11dba00200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="QuantityQualifierCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d4f15d11dbc7e000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d5f15d11db969a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BuyerParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec100f16411dba2e900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec101f16411db997a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec102f16411dbb75900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec103f16411db8fa500123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec104f16411dba93f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">449ec105f16411dba20f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">0de2f450f16511dbaa4700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfIdentifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d0f16711dbbdd800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier" maxOccurs="unbounded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d1f16711dbcd2600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d2f16711db82f800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d3f16711dbcf6e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d4f16711dbcb6200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="SellerParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e0422b80f16711dba8c100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb80f16811db82e800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb81f16811dba6ab00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb82f16811db8b4e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb83f16811dbc0ff00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb84f16811dbb8f700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb85f16811dba46200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfIdentifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb86f16811db98c000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier" maxOccurs="unbounded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb87f16811dbb25200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb88f16811dbc7d100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e99ffa30f16811dba27100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d30f16a11dbb29f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ShipFromParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e0422b81f16711dbbfce00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d31f16a11db9adf00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d32f16a11dbbef100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d33f16a11db9e5600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d34f16a11dbba6d00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d35f16a11db855400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d36f16a11db877300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ShipToParty">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">e0422b82f16711db84ec00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Party">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac0f16b11dba49600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartyID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac1f16b11db80c700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac2f16b11db8ea300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac3f16b11dbb5bb00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac4f16b11dbb7bc00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">275ecac5f16b11db92a300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Language">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a370c1d6f15d11db9f9a00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LanguageCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd52f15e11dbc06300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfLocationGroupedPlanningDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">c65d41c2f15b11dba9fd00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocationGroupedPlanningDetail" maxOccurs="unbounded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">89515130f17f11db98e400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Location">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">de832980f17f11db8d4600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocationIdentifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d0f18011db8ce800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocID">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d1f18011db839900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Identifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d2f18011dba45300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Agency">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d3f18011db9ac700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="AgencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d4f18011dbc4ab00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="Ident" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f95b26d5f18011dbcd4400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfLocationPlanningItemDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">de832981f17f11db856100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LocationPlanningItemDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257410f18111db8b6f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BasePlanningDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257411f18111db839c00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="LineItemNum">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257412f18111db847f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BuyerLineItemNum" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257413f18111dbcf7200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ItemIdentifiers">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257414f18111dba6f100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartNumbers">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257415f18111db968700123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="BuyerPartNumber">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257416f18111db9f9100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartNum">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257417f18111dbc32500123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="PartID" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">d8257418f18111dbcfa900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="StandardPartNumber">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">50b67960f18211db839c00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ProductIdentifierCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">50b67961f18211dbc78900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ProductIdentifierQualifierCoded" type="xsd:integer">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">50b67962f18211dbae6e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ProductIdentifier" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">83815570f18411dbb4e800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ItemDescription" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">83815571f18411db876f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfItemReferences">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef0f18711dbbafe00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ListOfReferenceCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef1f18711db8a7600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ReferenceCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef2f18711db935200123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ReferenceTypeCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef3f18711dba69c00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ReferenceTypeCodedOther" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef4f18711db942b00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="PrimaryReference">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef5f18711db93a800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Reference">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef6f18711dbcebc00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="RefNum" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef7f18711dbce6300123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ForecastFrequencyCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef8f18711db937b00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ListOfScheduleDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aef9f18711dba61400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ScheduleDetail">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefaf18711db9d4800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="CommitmentLevelCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefbf18711dba59800123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="ScheduleDates">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefcf18711db947900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ListOfDateCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefdf18711dbc43e00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="DateCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefef18711dbaa5000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="Date">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59aefff18711dbcde600123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="DateQualifier">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af00f18711db87f100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="DateQualifierCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af01f18711dbc9cf00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="ScheduleQuantities">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af02f18711dbc24100123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="ListOfQuantityCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af03f18711db842900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="QuantityCoded">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af04f18711dbb59400123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="QuantityValue" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">2e59af05f18711dba6d900123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      <xsd:element name="UnitOfMeasurement">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a87e2580f18711dbc66f00123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      <xsd:complexType>
      <xsd:sequence>
      <xsd:element name="UOMCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a87e2581f18711db89a000123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      <xsd:element name="QuantityQualifierCoded" type="xsd:string">
      <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">a87e2582f18711db9a1500123fbbc71c</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:schema>

  • Getting error while uploading multiple files in sharepoint hosted app in 2013 with REST API

    Hi All,
    In one of my tasks, I was struck with one issue, that is "While uploading multiple files into custom list with REST API".
    Iam trying to upload multiple files in library with REST calls for an APP development, my issue is if i wants to upload 4 image at once its storing only
    3 image file and further giving "Conflict" error". Below is the attached screenshot of exact error.
    Error within screenshot are : status Code : 409
    status Text :conflict
    For this operation i am uploading different files as an attachment to an list item, below is the code used for uploading multiple files.
    my code is
    function PerformUpload(listName, fileName, listItem, fileData)
        var urlOfAttachment="";
       // var itemId = listItem.get_id();
        urlOfAttachment = appWebUrl + "/_api/web/lists/GetByTitle('" + listName + "')/items(" + listItem + ")/AttachmentFiles/add(FileName='" + fileName + "')"
        // use the request executor (cross domain library) to perform the upload
        var reqExecutor = new SP.RequestExecutor(appWebUrl);
        reqExecutor.executeAsync({
            url: urlOfAttachment,
            method: "POST",
            headers: {
                "Accept": "application/json; odata=verbose",
                "X-RequestDigest": digest              
            contentType: "application/json;odata=verbose",
            binaryStringRequestBody: true,
            body: fileData,
            success: function (x, y, z) {
                alert("Success!");
            error: function (x, y, z) {
                alert(z);

    Hi,
    THis is common issue if your file size exceeds 
     upload a document of size more than 1mb. worksss well for kb files.
    https://social.technet.microsoft.com/Forums/office/en-US/b888ac78-eb4e-4653-b69d-1917c84cc777/getting-error-while-uploading-multiple-files-in-sharepoint-hosted-app-in-2013-with-rest-api?forum=sharepointdevelopment
    or try the below method
    https://social.technet.microsoft.com/Forums/office/en-US/40b0cb04-1fbb-4639-96f3-a95fe3bdbd78/upload-files-using-rest-api-in-sharepoint-2013?forum=sharepointdevelopment
    Please remember to click 'Mark as Answer' on the answer if it helps you

  • Error while uploading .xml file for Customer/Vendor List for Italy

    Hi All,
    We are facing problem while uploading the .xml file in DMEE transaction for the new Customer/Vendor List for Italy.
    We have followed the entire process given in the OSS Note(1090857).
    We have SAP 4.6c and followed the below steps:
    1. Created ID-FI-IT Development class
    2. Added domains
    3. Added Data elements
    4. Tried to upload the given .xml file and got any error saying ".xml file could not be interpreted".
    Also there is a .SAR file mentioned to upload if we receive any errors while uploading .xml file.
    Tried uploading the .SAR file also. STill we are recieving the same Error.
    Can any one of you help us out.
    Thanks in Advance.
    Ramesh

    Ok, we upload .SAR file in this way:
    1. unpack .SAR file with SAPCAR.EXE program. Yuo obtain 2 files
    R492445.P9C and K492445.P9C
    2. put K492445.P9C in directory \SAPMNT\TRANS\COFILES and put R492445.P9C in directory \SAPMNT\TRANS\DATA of your system (DEV, TST or PRD)
    3. Use Tx STMS. If You want create DMEE tree in DEV system, go to DEV import queue. Choose menu Extras | Other requests | Add. Insert P9CK492445 in Transp. request field.
    4. Import the request. This creates the DMEE tree. You don't need ti upload XML file after. You can see the DMEE tree created with Tx DMEE and inserting
    Tree type        UMS1            
    Format tree     IT_CUST_VEN_LIST
    5. after continue follow the note
    I hope this help you
    Roberto

Maybe you are looking for

  • SD and HD preview (output only) interface choices?

    Hi there, I need HD & SD preview ability (to a couple external reference monitors), but no capturing is required. Most interfaces (much like audio) tend to include both A/D and D/A but I only need D/A for output. Do I need to buy a video interface wi

  • AlterProviderAttributes filter

    Hi Guys, I wrote a alterProviderAttributes filter to alter external user attributes. Filter is executed if user is hitting any UCM serveice for e.g http://server/ucm/idcplg?IdcService=GET_SERVER_OUTPUT. This filter never get executed to web URLs like

  • 857 Router Dot11Radio0 reset - problem

    Hi all I have just upgraded the IOS in a 857 Router to this: ROUTER#sh version Cisco IOS Software, C850 Software (C850-ADVSECURITYK9-M), Version 12.4(15)T7, RELEASE SOFTWARE (fc3) but now I can't get the dot11radio 0 interface to come up. I just get

  • Copy db 9i 32bit to other server and upgrade to 10g 64bit, how?

    Hi there, im trying to upgrade this 9i database 32bits that is in red hat enterprise 3, to other server that has red hat enterprise 5 64bits, but i couldnt make it work. searching i realice that 9i isnt certified by oracle to work in red hat enterpri

  • Welcome To Blog Talk TV

    On Friday, August 17, more than 650 middle school students nationwide competed head-to-head in the 2015 Zero Robotics Middle School Program. This year a total of 11 states participated in the annual competition, which took place aboard the Internatio