Difference between revisions of "Communication Interfaces"

From Wiki - Heidler Strichcode GmbH
Jump to navigation Jump to search
Line 12: Line 12:
*[[HVS32 JDBC interface (automatic polling)|JDBC]]
*[[HVS32_SAP_RFC_Interface_(Polling)|SAP RFC]]
*[[HVS32_SAP_RFC_Interface_(Polling)|SAP RFC]]
*[[HVS32_SAP_IDOC_Interface_(Polling)|SAP IDOC]]
*[[HVS32_SAP_IDOC_Interface_(Polling)|SAP IDOC]]

Latest revision as of 10:48, 13 October 2021

HVS32 Processing-Interfaces

Please note: all descriptions are just examples. Field names, -length, format are open to customization. Due to a data evaluator, we are able to map your fields to our database structure. Except Automatic-Polling SOAP/REST - these interfaces are fixed and can not easily be customized!


In automatic polling mode, the HVS32 dispatch system works completely in the background and is addressed by the upstream system via interface. Functions such as dispatch label printing, package cancellation, daily closing, etc. can be triggered. No user input of data is required.

The data can be transferred from the upstream system to the HVS32 via the following interfaces:


In interactive processing, the dispatch data is entered in an entry mask of the HVS32. The dispatch data can be requested from or reported back to the previous system by various interactive Actions in the previous system.
This gives you the possibility, for example, to make a data request after scanning a delivery note, feedback after printing a label, feedback after daily closing, feedback after cancellation/release.

The following interfaces can be used to access the dispatch data of the previous system during interactive processing:

Other interfaces