Esci Inbox Errors

We had some more supplier errors today 

Order reference errors

I have been trying to determine which of teh 10 documents in the inbox is giving the error.

running 

inbox -l -u user -p pass -r https://vethub.provet.com.au/openvpms/registryservice.svc?wsdl

the aboves works fine and lists the docs (there are 10)

now I try 

 

C:\Development\Openvpms\ESCI\bin>inbox -i 2253910 -t invoice -g -d -u user -p pass -r https://vethub.provet.com.au/openvpms/registryservice.svc?wsdl

which is one of the invoices and I get the following

---[HTTP request - https://vethub.provet.com.au/openvpms/RegistryService.svc]---
Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Content-type: text/xml;charset="utf-8"
Soapaction: "http://openvpms.org/esci/RegistryService/getInboxServiceRequest"
<?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:getInboxService xmlns:ns2="http://openvpms.org/esci"/></S:Body></S:Envelope>--------------------
---[HTTP response - https://vethub.provet.com.au/openvpms/RegistryService.svc - 200]---
null: HTTP/1.1 200 OK
Server: Microsoft-IIS/7.0
X-frame-options: SAMEORIGIN
X-powered-by: ASP.NET
Date: Wed, 20 May 2015 01:00:54 GMT
Content-type: text/xml; charset=utf-8
Content-length: 309
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><getInboxServiceResponse xmlns="http://openvpms.org/esci" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><url xmlns="">https://vethub.provet.com.au/OpenVpms/inboxservice.svc?wsdl</url></getInboxServiceResponse></s:Body></s:Envelope>--------------------
---[HTTP request - https://vethub.provet.com.au/openvpms/InboxService.svc]---
Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Content-type: text/xml;charset="utf-8"
Soapaction: "http://openvpms.org/esci/InboxService/getDocumentRequest"
<?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns8:getDocument xmlns:ns2="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:ns3="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2" xmlns:ns4="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:ns5="urn:oasis:names:specification:ubl:schema:xsd:OrderResponseSimple-2" xmlns:ns6="urn:oasis:names:specification:ubl:schema:xsd:Order-2" xmlns:ns7="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2" xmlns:ns8="http://openvpms.org/esci"><ns4:DocumentReference><ns2:ID>2253910</ns2:ID><ns2:DocumentType>invoice</ns2:DocumentType></ns4:DocumentReference></ns8:getDocument></S:Body></S:Envelope>--------------------
---[HTTP response - https://vethub.provet.com.au/openvpms/InboxService.svc - 500]---
null: HTTP/1.1 500 Internal Server Error
Server: Microsoft-IIS/7.0
X-frame-options: SAMEORIGIN
X-powered-by: ASP.NET
Date: Wed, 20 May 2015 01:00:56 GMT
Content-type: text/xml; charset=utf-8
Content-length: 249
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring xml:lang="en-AU">An internal server error occured while processing the request</faultstring></s:Fault></s:Body></s:Envelope>--------------------

Any ideas or do I need to throw this back to provet.

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Esci Inbox Errors

ESCI will terminate on the first error it encounters in an Inbox, so it will be terminating on the first document in the list.

Note that document type names are case sensitive, so try with -t Invoice rather than -t invoice

 

Re: Esci Inbox Errors

Fixed thanks....bloody casing

 

Same old error...I reopened the issue with provet...but I doubt they will fix it.

A bigger issue for us / and all other ESCI users working with Provet is that if a 1 reorder code doent match in an order with multiple lines the order will still be accepted with that line removed without notice to any party. You will get the order accepted message ...but that lineitem will never arrive.  this has also been raised with provet.

 

 

 <ns3:InvoiceLine>
     <ID>1</ID>
     <InvoicedQuantity unitCode="PK">1</InvoicedQuantity>
     <LineExtensionAmount currencyID="AUD">98</LineExtensionAmount>
     <ns3:OrderLineReference>
         <LineID>-1</LineID>
         <ns3:OrderReference>
             <ID>13818</ID>
         </ns3:OrderReference>
     </ns3:OrderLineReference>
     <ns3:TaxTotal>
         <TaxAmount currencyID="AUD">9.8</TaxAmount>
         <ns3:TaxSubtotal>
             <TaxAmount currencyID="AUD">9.8</TaxAmount>
             <ns3:TaxCategory>
                 <ID>S</ID>
                 <Percent>10</Percent>
                 <ns3:TaxScheme>
                     <TaxTypeCode>GST</TaxTypeCode>
                 </ns3:TaxScheme>
             </ns3:TaxCategory>
         </ns3:TaxSubtotal>
     </ns3:TaxTotal>
     <ns3:Item>
         <Name>REPAIR - CLIPPER WAHL</Name>
         <ns3:SellersItemIdentification>
             <ID>INST R CL5</ID>
         </ns3:SellersItemIdentification>
     </ns3:Item>
     <ns3:Price>
         <PriceAmount currencyID="AUD">98</PriceAmount>
     </ns3:Price>
 </ns3:InvoiceLine>

Regards
 
Ben 
OpenVPMS Installer and Helper 
Ph: +61423044823 
Email: benjicharlton[at]gmail[dot]com

Re: Esci Inbox Errors

Take a look at the ESCI Inbox Administration project.

One of its aims is to allow you to selectively process messages with invalid order references.

Re: Esci Inbox Errors

Yeah I saw it but quite frankly this is as a result of poor implementation of the specification on Provets end.  I can handle a couple of poorly formed invoices but the missing line items is a major stumbling block

 

Regards
 
Ben 
OpenVPMS Installer and Helper 
Ph: +61423044823 
Email: benjicharlton[at]gmail[dot]com
Syndicate content