Recipients for messages
This post is also available on:
Difference for messages: milk and beef
If BU has the entry Milk, there are 2 options:
For shipping, the notification can only be intended for dairy cows.
- “YES” (active) or
- “NO” (inactive) = no message
If BU has the entry Beef, there are 3 ways:
For shipping, the notification can only be intended for beef cattle.
- YES = all
- HBKL = only animals with herd book class entry
- NO = no message
The settings for notifications vary from one country to another. Please contact your specialist dealer for configuration of the respective message.
Open the configuration window via 
Organization > 
Settings > Key > Receiver for messages.
In this window, the recipients for messages are created.
| Creates a new recipient
| Editing a recipient
| deletes a recipient from the list. This is only possible if no messages have yet been created for this recipient.
| Download existing receiver, overwrites the receiver with the same name if it exists
Parameter
Name | the name is freely selectable should describe the recipient and the type of message
Output messages for BU separately | when active, a separate message is triggered for each BU *
Shipping method | there are several to choose from *
Data format | there are several to choose from *
Insemination station(s) | one station can be stored in each of the 4 existing fields
- 00 for natural jump
- if a station is stored, the message is only created for the inseminator with the same station
- if you also store the identical station number in the sperm administration, it is only for this sperm and for the technician with the identical station number to record an Insemination , otherwise an error message appears. If the Insemination is successfully recorded, only the technician and sperm of the set station are created as a message.
Key type operation | this setting depends on receiver *
Holdings | If several establishments are managed in a database, the message can also be issued separately by operation.
Warning | standard is 1 day after creation. Can be deactivated if you set a “0”.
Example of the “HI-Tier message” configuration
Reorder ear tags was delivered in the update of 08.09.2020 and can be easily carried by any customer who sends the HIT messages directly to the HI-Tier.
For farmers who report the birth and movement (VVVO) via the LKV or where the transmission route is via e-mail, the HIT recipient must create the HIT recipient for the ear tags reorder as described here .
Mandatory entries for HIT are:
- Movement (VVVO)
- Birth
- Reorder ear tags *
* Optional
HIT ear tags (LKV)
For farmers who want to reorder ear tags with the update of 08.09.2020 and do not have an existing HIT-receiver, this will be used as in the following image.
Mandatory entries for HIT ear tags are:
- Reorder ear tags
Warning
As soon as notifications are received for shipment, HERDEplus checks whether they are sent within the specified deadline. If this is not done and the deadline is exceeded, a message will appear every minute to draw attention to it.
Example of the configuration laboratory
Name | the name is freely selectable should include the name of the recipient and the type of message
Shipping method | there are several to choose from *
Output Format Format | there are several to choose from *
File Name | may contain attachments, name format must be coordinated with the laboratory*
e-mail | Enter the e-mail address of the laboratory
In the case of “investigation order”, 
set
Key type operation | this setting depends on receiver *
Warning | i.e. 1 day after creation. Can be deactivated if you set a “0”.
* this setting should only be set or changed by qualified specialist dealers in consultation with the recipient of the message