Agvance Junge Blending Interface

Junge Dry and Liquid Automation can interface with Agvance using two blender types: Junge Liquid or Dry (TXT), and SSI Standard XML.

Product setup is done at Hub / File / Open / Products.

The Blender Factor, found on the Blend Setup tab of the product file in Agvance, must match the Import/Export ID in Junge.
Blending Units, also found on the Blend Setup tab in Agvance, must match the Import/Export Unit of Measure in Junge.

Product Sets are maintained at Blending / Setup / Product Sets.

On the Blender Interface / Print Preference tab, set the Blender Type to SSI Standard XML.
For the Data Storage Path, select a path that is a shared folder where the file is created for the blender interface.
The Shipped from Location Code is required for the SSI Standard XML Blender Type, but is not used by Junge. Enter a user-defined number. Some companies with multiple locations use this area for the location number. If the location number is entered, Junge uses it to set up batch information for multiple locations.

The Blend Ticket is created in Agvance using one of the Junge product sets with products setup with a Blender Factor. The Blend Ticket is created for application of a whole order. Agvance sends the product totals for each product. The Junge Dispatcher software allows the operator to resize batches to the truck.
Agvance sends the ticket to the shared folder when the Create Automated Blender File option is selected on the Print Blend Documents window.
Junge retrieves unimported tickets with a status of Ready from the shared folder.
The product identifiers (Blender Factor) are matched with the Import/Export ID in Junge.
Customer information is compared to the Junge records. If the customer is not found in Junge, a customer record is added.
Junge uses the Import/Export Units to calculate the proper amounts to import.
If any product identifier (Blender Factor) cannot be matched, Junge does not import any of the batch information in the file and moves on to the next ticket.
The XML can be modified in Agvance and exported with changes until any portion of the batch has been made. When the batch is sent to be made, the ticket status changes from Ready to In-Process.
When the last batch in Junge is completed, the ticket status is changed to Done and can be imported back into Agvance.

The Blender Factor on the product in Agvance must match the Import/Export ID in Junge. Fertilizer & Bulk Chemical ID must be between 1 and 40. Hand added, packaged products must be between 73 and 999.
Blending Units on the product in Agvance must match the Import/Export Unit of Measure in Junge.

On the Blender Interface / Print Preference tab, for the Blender Type select Junge Dry or Junge Liquid.
For the Data Storage Path, select a path that is a shared folder where the file is created for the blender interface.

A Blend Ticket is created in Agvance using the product set to send to Junge and with products set with a Blender Factor. The Blend Ticket is created for application of a whole order. Agvance sends the product totals for each product. The Junge Dispatcher software allows the operator to resize batches to the truck.
Agvance sends the ticket to the shared folder when the Create Automated Blender File option is used. The file has a a .txt extension.
Junge matches the product identifiers with the Import/Export ID in Junge, and uses the Import/Export Units to calculate the proper amounts to import.
The customer information from the file is compared to the customer record in Junge. If the customer is not found, it is added.
When the last load in Junge has been completed, a file is created with an .act extension. This file can be imported back into Agvance.
Once the Blender File has been imported into Agvance with the archive box selected, the file extension is changed to .dne.