UPI File Transfer interface. Schema for UPI related to file transfer request and response messages. Change history: 2010-01-04 Creation (TQN, Elca SA) Corresponds to a "postFile" operation's request Corresponds to a "postFile" operation's answer Corresponds to a "getFile" operation's request Corresponds to a "getFile" operation's answer File to post to UPI File Transfer web service. This corresponds to an UPI request compressed in ZIP format. Each ZIP file must contain only one UPI request. Is present, if the query has been processed successfully and the ticket is returned. Is present, if the query contained an error. The reason is for refusing is: 1 = Transmitted data contains formal error, or 3 = The file has been already sent before, or 10 = Server's internal error (I/O) and 11 = Server's internal error (Database) Combined with the "reason", this gives more detail on the error. Possible values: 2 = DB error while searching for the sequence, 3 = DB error while inserting the new ticket, 4 = DB error while reading the table TNNHPFILE, 5 = The user is not defined, 6 = The request is not XSD valid, 7 = The attachment is not a compressed (zip) file, 8 = The attachment could not be stored on the server, 9 = The attached compressed file does not contain one and only one file inside, 10 = The attached compressed file could not be decompressed, 11 = The decompressed file is not a XML file, 12 = The decompressed file is not an eCH-0085 or an eCH-0086 format, 13 = The XML file could not be scanned, 14 = The XML file could not be moved into the input folder. Incoming ticket. Is present, if the query has been processed successfully and the response is returned. The UPI response is compressed in ZIP format and is sent back to the requester as a SOAP attachment. Is present, if the query contained an error. The reason is for refusing is: 1 = Transmitted data contains formal error, 10 = Server's internal error (I/O), 11 = Server's internal error (Database), 100 = The ticket does not exist, 101 = The ticket is still in process, 102 = The user-ticket relation is not correct, 103 = The ticket is too old Combined with the "reason", this gives more detail on the error. Possible values: 100 = The ticket does not exist in DB, 102 = The ticket must be retrieved by the same user that posted the file, 103 = The non-compressed (xml) response could not be found, 104 = The compressed (zip) response could not be found, 105 = The user could not be defined, 106 = The request is not XSD valid, 107 = DB error while reading table TNNHPFILE, 108 = DB error while updating the ticket state to "Compression in process", 109 = Error while compressing the response, 110 = DB error while updating the ticket state to "Terminated", 1NNN = The response is not available yet (state = NNNN), 2NNN = The response is not compressed yet (state = NNN)