Interfaces for integration of the HVS32 shipping system
Options for communication with your host system, ERP, WMS
We offer a variety of interfaces for data exchange between shipping- and pre-systems
(such as ERP, WMS). Depending on the possibilities of the pre-system, different variations are available, such as CSV, SDF, XML, ODBC, REST, TCP/IP, HTTP, SOAP, SAP RFC, SAP IDoc.
In this way, merchandise management, warehouse management, or shop systems can be optimally connected with the appropriate interface technology. Depending on the interface technology used (such as SOAP, REST, etc.), both data, as well as features such as daily closing, list printing, label reprinting, and cancellation orders, can be controlled via the interface.
In most cases, bi-directional communication is chosen, via which not only tracking number and package status data but also the generated label Base64 can be reported back to the pre-system in encoded form.
The HVS offers defined standard interfaces to simplify the initial connection.
Individual interfaces can, of course, be implemented and adapted. With a central
interface to the HVS, you get full flexibility over carrier selection.
You have to send data from several different pre-systems to the shipping system? No problem, we’ll make it happen.
large selection of different technologies
integrated data evaluator /-parser
high performance HVS32 communication
many functions callable
stable connection to your host system
We have already implemented interfaces to the following systems
|Ehrhardt + Partner LFS
|Microsoft Dynamic 365
|Ehrhardt + Partner LFS
|Microsoft Dynamic 365
|Microsoft Dynamic AX
|Microsoft Dynamic Nav (Navision)
|SAP Business One
|SSI Schäfer WAMAS®
Available interface technologies
With this plugin we provide a SOAP Web service with a predefined WSDL, in which all functions are defined with the corresponding fields – both for the transmission to the HVS32 and for the feedback. This WSDL can be integrated by the source system then. For a request only the corresponding function has to be invoked by the respective transfer parameters. The feedback is done by the return parameters of the function.
With the SOAP client, GET or POST requests can be sent to a SOAP web service and response data can be interpreted in the form of an XML document from the body. This enables inquiries and feedback via various functions.
With this plugin, we provide a REST web service in which all functions are defined with the corresponding fields – both for the transmission to the HVS32 and for the feedback. For an inquiry, only the corresponding function with the respective transfer parameters has to be called. The feedback takes place via the return parameters of the function. The data are transferred in JSON format.
This plugin requires a RFC function module for each desired function which shall be invoked on the shipping system (e.g., printing request, cancellation, daily closing, etc.). For this communication the plugin is registered at first as a RFC server program with a program ID on a SAP gateway. Thus the RFC function modules can be invoked by SAP using SM59. The data exchange is carried out by the import parameters (data input) or export parameters (feedback) or the tables of the RFC function. The mapping can be adapted to the corresponding module, hence the structure of the RFC modules can be freely defined.
With the SAP RFC plugin it is possible to call RFC function modules that are registered at a SAP gateway. The data exchange takes place via the import parameters (feedback) or export parameters (data input) or the tables of the RFC function. The mapping can be adapted to the respective module, therefore the structure of the RFC modules can be freely defined. There are many different communication points in the HVS32 shipping system, at which data requests or feedback are possible. An RFC block can be stored for each desired communication point.
This plugin is used for the data exchange with a SAP system using IDoc format (Intermediate Document). Here the most common functions of the shipping system can be directly controlled from the SAP system.
For this communication the plugin is registered at first as a RFC server program with a program ID on a SAP gateway. Thus an IDoc can be sent by SAP via the SAP-RFC protocol (Remote Function Call) based on TCP/IP and it can be received and processed by the HVS32. The feedback is also done bz IDoc via RFC. Several RFC connections can optionally be established, what allows for a parallel processing of orders at the same time. We support all IDoc types thanks to a freelz configurable mapping, i.e., from base types as DESADV01 and DELVRY05, for example, up to IDoc formats structured completely individually.
This plugin offers the possibility to communicate with a database compatible with JDBC. Here a check for new data is carried out within a corresponding table with an interval of 500 mS. If a data set is filed in the table by the source system then, it can be called and processed by the shipping system. A distinction can be made between printing request, cancellation, daily closing, etc., using a function ID.
After the processing in the shipping system has been completed a corresponding feedback can be written in freely configurable tables (e.g., with tracking information).
The HVS32 clients are operated on the package places in the foreground. During scanning of a delivery note the data are selected from a JDBC-capable database. The data can be updated in the same table after successful processing or they can be written in another table. Also a feedback in another JDBC database is possible. Moreover, many different communication items exist in the shipping system HVS32, on which other feedbacks are possible.
Ehrhardt + Partner (LFS)
The interface plugin E + P is designed for direct communication with the warehouse management system “LFS” from Ehrhardt + Partner. Here, a TCP / IP socket server is started from our side, to which the LFS can register the processing jobs. The registered jobs can then call up the various functions of the HVS32 using the socket connection. The confirmation is sent back to the LFS via the same transaction. The XML format for communication with the LFS is standardized.
File (CSV, SDF, XML)
The different file formats CSV, SDF or XML can be processed during the file import from a configurable directory. The sequence of the data fields can be freely configured using a mapping and it therefore can be extended easily. A feedback, e.g., after printing a shipping label, can also be prepared in the above mentioned formats.
At first the files are imported completely in the internal shipping system database and are processed sequentially then. It is possible to transmit a station identification, thus the data set can be processed by a special packing station or a special HVS32 shipping station.
The scanning of a delivery note, which has still not been imported to the internal shipping system database, releases the import of the transfer files.
GET or POST requests can be sent to a Web server by the HTTP client, and answer data can be interpreted from the body in form of a XML document. Thus request and feedback are possible by different URLs.