Difference between revisions of "Interface Admin"
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
This screen is used to define which inbound and outbound interfaces are used by the application.<br><br> | This screen is used to define which inbound and outbound interfaces are used by the application.<br><br> | ||
| + | |||
| + | The Interface Administration screen is only required if you are wanting to exchange data with external applications. Typical scenarios might be receiving Material Master and Process Order data from an ERP system such as SAP. You might also want to link Commander4j to an Automatic Label Applicator system in which case Commander would receive label information from the external system. Another typical use would be for Commander4j to message back details regarding real time production. This latter message would send a Production Declaration message to an external ERP System as it occurs, as each pallet label is printed and optionally confirmed with a scanner. | ||
| + | |||
| + | |||
[[File:interface_admin.jpg]] | [[File:interface_admin.jpg]] | ||
<br> | <br> | ||
| − | Each message can generate an email exception message if the process fails. You can enter a comma separated list of email addresses. The SMTP email server settings to use for sending these messages are to be found in the [[System Keys|System | + | Each message can generate an email exception message if the process fails. You can enter a comma separated list of email addresses. The SMTP email server settings to use for sending these messages are to be found in the [[System Keys|System Keys]] |
Latest revision as of 15:06, 29 July 2017
This screen is used to define which inbound and outbound interfaces are used by the application.
The Interface Administration screen is only required if you are wanting to exchange data with external applications. Typical scenarios might be receiving Material Master and Process Order data from an ERP system such as SAP. You might also want to link Commander4j to an Automatic Label Applicator system in which case Commander would receive label information from the external system. Another typical use would be for Commander4j to message back details regarding real time production. This latter message would send a Production Declaration message to an external ERP System as it occurs, as each pallet label is printed and optionally confirmed with a scanner.
Each message can generate an email exception message if the process fails. You can enter a comma separated list of email addresses. The SMTP email server settings to use for sending these messages are to be found in the System Keys
