Prerequisites:
Creating a Vendor Sales Location
Create a Purchase Order for Nest Run eggs in ERP
The vendor and items that are being used on the purchase order must exist in the Ovotrack database. Vendors and items have their own sets of requirements that must be met for the PO to be sent to Ovotrack.
Vendor Sync Requirements:
Ovotrack Vendor Data Synchronization
The Date field, Terms, Item Code, and House are all required fields:
Creating a Batch in CONNECT
Go to the Ordering module. Select New Batch in PO Sync.
The search looks at when the PO was created/modified. Make sure you enter a date/time in the Last Modified field BEFORE the day/time you created/modified the PO.
Ex: If you created the order on 10/29, you could to set the date to 10/28.
Once your date is set, click Import/Create Batch:
If there are any PO lines that match the criteria, they will now be staged in CONNECT.
Sending a Batch to Ovotrack
New Feature as of CONNECT 1.9.11+
Now the only requirement for a nest run purchase order to be sent to Ovotrack is the Shed ID/House
The PO can now be sent to Ovotrack. Click the Send Batch button. If the order passes validation, a send date will appear on the order line. If there are any errors, they can be reviewed in the Commit Messages tab.
Receiving a Batch From Ovotrack
The PO is now in the Ovotrack database. Before the PO is ready to be sent back to ERP, we need to click the Receive Updates button. If there are any changes to the quantity of items on the order, it will reflect in the Received Pallets and Received Quantity field. If there are no changes, the Received Pallets Received Quantity field will match the Pallets and Quantity field. Once the PO has been received, the Received date will be populated.
Committing Purchase Orders to ERP
At this point the PO is now ready to be sent back to ERP. Click the Commit button. Once the PO has completed the commit process, the Commit Date will be populated.
Once the PO has been sent back to ERP, it will create a receiver and receive the inventory.
