HVS32 SOAP Interface (Interactive): Unterschied zwischen den Versionen

Aus Wiki - Heidler Strichcode GmbH
Zur Navigation springen Zur Suche springen
Zeile 1: Zeile 1:
 
[[de:HVS32_SOAP_Schnittstelle_(Interaktiv)]]
 
[[de:HVS32_SOAP_Schnittstelle_(Interaktiv)]]
  
= prerequisites =
+
= Prerequisites =
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
Zeile 14: Zeile 14:
 
The DataGatewayServer (DGS) is the central communication unit through which all data is exchanged between the shipping system and the host system. It runs as a service on a Windows server.
 
The DataGatewayServer (DGS) is the central communication unit through which all data is exchanged between the shipping system and the host system. It runs as a service on a Windows server.
  
= Verfügbare HVS32 Funktionen =
+
= Available HVS32 functions =
Artikel-Daten und Gefahrgut-Informationen stehen in einer 1:n Beziehung zu den Packstückdaten.
+
Item data and dangerous goods information have a 1:n relationship with package data.
  
Bitte beachten Sie, dass die Feld-Beschreibungen sich nur auf einen Standard beziehen, welcher als Vorschlag für die Schnittstelle dienen soll. Funktionsnamen, Feldnamen /-längen /-formate können prinzipiell abweichen, müssen in diesem Fall jedoch individuell betrachtet/analysiert werden.
+
Please note that the field descriptions only refer to a standard, which should serve as a suggestion for the interface. Function names, field names /-lengths /-formats can deviate in principle, but must be considered/analyzed individually in this case.
 
<br><br>
 
<br><br>
 
'''[[HVS32_Funktionen_Interaktiv|Verfügbare HVS32 Funktionen]]'''
 
'''[[HVS32_Funktionen_Interaktiv|Verfügbare HVS32 Funktionen]]'''
  
= Beispiele =
+
= Examples =
 
<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">
 
<div class="toccolours mw-collapsible mw-collapsed" style="overflow:auto;">
 
<div style="font-weight:bold;line-height:1.6;">'''VersandDatenAnfrage'''</div>
 
<div style="font-weight:bold;line-height:1.6;">'''VersandDatenAnfrage'''</div>
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
;Anfrage vom DGS an den SOAP Server
+
;request from the DGS to the SOAP server.
 
<source>
 
<source>
 
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:std="http://my.path.to.endpoint.functions">
 
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:std="http://my.path.to.endpoint.functions">
Zeile 39: Zeile 39:
 
</source>
 
</source>
  
;Rückmeldung vom SOAP Server an den DGS zur obigen Anfrage
+
;Feedback from the SOAP server to the DGS about the above request.
 
<source>
 
<source>
 
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
 
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

Version vom 6. September 2021, 12:31 Uhr


Prerequisites

DGS-Version 3.6.0.588 oder höher
DGS-Plugins HVS32Server, SOAP Client

Function description

In interactive processing, requests are made from the dispatch system to your SOAP server. Thereby the DGS acts as SOAP Client.
This gives you the possibility, for example, to request shipping data for a reference number (e.g. delivery note number) from the HVS32. The functionalities available to you can be found under Verfügbare HVS32 Funktionen.

The DataGatewayServer (DGS) is the central communication unit through which all data is exchanged between the shipping system and the host system. It runs as a service on a Windows server.

Available HVS32 functions

Item data and dangerous goods information have a 1:n relationship with package data.

Please note that the field descriptions only refer to a standard, which should serve as a suggestion for the interface. Function names, field names /-lengths /-formats can deviate in principle, but must be considered/analyzed individually in this case.

Verfügbare HVS32 Funktionen

Examples

VersandDatenAnfrage
request from the DGS to the SOAP server.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:std="http://my.path.to.endpoint.functions">
	<soapenv:Header/>
	<soapenv:Body>
		<std:my_function>
			<arg0>
				<item>LS-123</item>
			</arg0>
		</std:my_function>
	</soapenv:Body>
</soapenv:Envelope>
Feedback from the SOAP server to the DGS about the above request.
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <S:Body>
      <ns2:my_function_Response xmlns:ns2="http://my.path.to.endpoint">
         <return>
            <AUFTRAGGEBERID>01</AUFTRAGGEBERID>
            <LIEFERSCHEINNR>LS-123</LIEFERSCHEINNR>
            <PACKSTUECKID>PID-53185</PACKSTUECKID>
            <VERSANDARTID>UPS</VERSANDARTID>
            <ZIELADRLKZ>D</ZIELADRLKZ>
            <ZIELADRNAME1>Heidler Strichcode GmbH</ZIELADRNAME1>
            <ZIELADRORT>Wolfschlugen</ZIELADRORT>
            <ZIELADRPLZ>72649</ZIELADRORT>
            <ZIELADRSTRASSE>Max-Eyth-Straße 25</ZIELADRORT>
         </return>
      </ns2:my_function_Response>
   </S:Body>
</S:Envelope>


PaketscheinDruckMeldung
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:std="http://my.path.to.endpoint.functions">
	<soapenv:Header/>
	<soapenv:Body>
		<std:my_function>
			<arg0>
				<AUSGANGDATETIME>28.04.2020</AUSGANGDATETIME>
				<DRUCKDATETIME>28.04.2020 15:23:45</DRUCKDATETIME>
				<FEHLERTEXT1/>
				<FEHLERTEXT2/>
				<GEBUEHR>5.30</GEBUEHR>
				<GEBUEHRWAEHRUNG>EUR</GEBUEHRWAEHRUNG>
				<PACKSTUECKID>PID-53185</PACKSTUECKID>
				<RETOURTRACKINGNR/>
				<TRACKINGNR>1Z0000DE6860000014</TRACKINGNR>
			</arg0>
		</std:my_function>
	</soapenv:Body>
</soapenv:Envelope>


AusgangsListenRueckmeldung
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:std="http://my.path.to.endpoint.functions">
	<soapenv:Header/>
	<soapenv:Body>
		<std:my_function>
			<arg0>
				<PACKSTUECK>
					<PACKSTUECKID>PID-102</PACKSTUECKID>
					<TRACKINGNR>889000232</TRACKINGNR>
				</PACKSTUECK>
				<PACKSTUECK>
					<PACKSTUECKID>PID-100</PACKSTUECKID>
					<TRACKINGNR>889000221</TRACKINGNR>
				</PACKSTUECK>
				<PACKSTUECK>
					<PACKSTUECKID>PID-101</PACKSTUECKID>
					<TRACKINGNR>889000221</TRACKINGNR>
				</PACKSTUECK>
				<PACKSTUECK>
					<PACKSTUECKID>PID-104</PACKSTUECKID>
					<TRACKINGNR>889000243</TRACKINGNR>
				</PACKSTUECK>
				<PACKSTUECK>
					<PACKSTUECKID>PID-105</PACKSTUECKID>
					<TRACKINGNR>889000243</TRACKINGNR>
				</PACKSTUECK>
				<PACKSTUECK>
					<PACKSTUECKID>PID-106</PACKSTUECKID>
					<TRACKINGNR>889000243</TRACKINGNR>
				</PACKSTUECK>
			</arg0>
		</std:my_function>
	</soapenv:Body>
</soapenv:Envelope>

FAQ / Troubleshooting