Home


EaglSys Guidelines


EaglSys has some significant limitations that you need to be aware of:
Producer ID, Farm ID: EaglSys has a 6-digit field called ACCT_NUM, which EaglSys uses as Producer ID and Farm ID combined. That's only six digits that have to be split up between your new Producer IDs and Farm IDs. Your Producer IDs need to be reduced to 2 digits and your Farm IDs need to be reduced to 4 digits in order to fit into the 6 digits total. Use the ID Editor to accomplish this.
Field ID: EaglSys has a 2-digit field called BLK_NUM, which EagleSys uses as Field ID. Your Field IDs need to be reduced down to 2 digits. Use the ID Editor to accomplish this.
The outbound layout _EAGLSYS has been created for you to use to send your producer/farm/field data to the EaglSys system.
The inbound file layout _EAGL-L1 has been created to bring in loads that have been called in (made, but not delivered). Each new load is assigned the next available Load Number, and the Module ID field is filled in with the EaglSys "Load number".

* Update * (07/25/2011) EaglSys has written a utility program to extract the data into a file without having to run the custom report. A replacement _EAGL-L1 inbound file layout has been created to read in this new format.
Exporting delivered loads from EaglSys to the eCotton Gin System: You will have to create a Custom Report in EaglSys (EaglSys personnel will set this up for you). The inbound file layout _EAGL-L2 has been created to bring in loads that have been delivered to the gin yard. Our Load Number field is filled in with the EaglSys Scale Ticket #, and our Module ID field is filled in with the EaglSys "Load number".

* Update * (07/25/2011) EaglSys has written a utility program to extract the data into a file without having to run the custom report. A replacement _EAGL-L2 inbound file layout has been created to read in this new format.
Pick, Shift, and Run Number: EaglSys does not have fields for these. If Pick is not important, you can fill it when inbounding the loads. If Shift is not important, you can fill it when importing the bales. Or you can import bales from only one shift at a time, and have the program prompt you for the shift number each time. Run numbers will have to be assigned in the Gin System (Ginning menu, Apply Bales to Loads, click the Assign Runs/Tickets button) when working with EaglSys.

When using the inbound file layout _EAGL-L2 (mentioned in the previous bullet) to bring in loads that have been delivered to the gin yard, the layout makes these assumptions:
- Pick will be filled with a "1".
- EaglSys Scale Ticket will be stored in the eCotton Load Number and Ticket # fields.
- EaglSys Load Number will be stored in the eCotton Module ID field.
Exporting ginned bales from EaglSys to the eCotton Gin System: You will have to create a Custom Reports in EaglSys (EaglSys personnel will set this up for you). The inbound file layout _EAGL-B has been created to bring in ginned bales.

Note that since EaglSys doesn't support the ginning "shift number", the bales' Shift field will be filled with a "1" (and therefore the Shift on the load will be set to "1" as well).

Because of the format of the EaglSys custom report, you will get 1 error while reading in bales. This is normal, and expected. Depending on your System Parameters settings, this error will either be an invalid seed weight error, or an invalid bale number error.

* Update * (07/25/2011) EaglSys has written a utility program to extract the data into a file without having to run the custom report. A replacement _EAGL-B inbound file layout has been created to read in this new format. You will no longer get the one error mentioned above.


2016 EWR, Inc. All rights reserved.   Privacy Policy