Founded in 1984, we've grown from two people and a telephone to a global agri-food business employing over 3,000 people in the UK and overseas, selling into 70 countries and we’re growing our community every day.
AB AGRI - Peterborough
User guide to using multi factor authentication
To get access to the QA AB AGRI Event environment, you will be invited to join by the Account Superuser.
​
​
Email Kamar with your email address and product requirement and he will invite you.
Then email your username (email address you signed up with) to antony.pratt@3t-europe.com to get ROUTE2 access.
​
Once we have activated your account, use the tile below in the Production or QA section to access your ROUTE2 environment.
​
Anytime you want access, click the tile below and follow the login process.
Carrier rate card template
Use to create carrier rate cards
AP 22-05-2020
A rate card has a pickup point. AB AGRI have multi pickup points. These will all need to be added to the distance rate card.
Mapping to the Oasis
Current mapping before testing
AP 25-05-2020
Current status for ROUTE2 filters for AB are:
-
Status = the Event ROUTE status types
-
Carrier name = all carriers associated to this Account
-
Type = TYPE in the integration file
-
Brand = the different Accounts available
-
Area = AREA in the integration file
-
Analysis = ANALYSIS in the integration file
-
Sales collection location = SALES LOCATION in the integration file
-
Item No. = PRODUCT ID in the integration file
-
Item Group = PRODUCT GROUP in the integration file
UAT environment
QA environment
To import files manually, put into below directory. There is no current import error process
File folder:
\\vlosftp02\TestFTP\test_logic_apps_sftp\QA\ABAGRIIN
Archive
?
Click image to open ROUTE2
ROUTE2 currently sits outside of the HOME screen. It will get incorporated but currently you will need to use the link above
Login to ROUTE2 using QA account credentials above.
Add orders through folder above. Format is included above to check against.
Currently no search function.
Please note, ROUTE2 is still in development.
Order file
Example order file
3 orders, change date and order No. to test
AP 25-05-2020
Rate cards
Alfred Hymas
Distance rate card
AP 13-06-2020
Frontier Agri Ltd
Distance rate card
AP 13-06-2020
DEV environment
To import files manually, put into below directory. There is no current import error process
File folder:
\\vlosftp02\TestFTP\test_logic_apps_sftp\DEV\ABAGRIIN
Archive
\\vlofile02\archive\TEST_ABAGRI_OMF
Click image to open ROUTE2
Rate cards:
Knowles Transport Ltd
AP 25-05-2020
Green WJ & J
AP 25-05-2020
Order Update Process
This is a description of how each order update is dealt with in Event for each Event status.
ON HOLD / UNALLOCATED / RECYCLE / REJECTED
The update of Order data is dependant on the data type and the Event status it is currently in at the point of updating.
Below documents each item that can be updated and how it will be updated in Event.
​
-
Update these fields directly on movement. There is no replanning, so update is directly on the status ON HOLD, REJECTED, RECYCLE, UNALLOCATED . Update order in database. Affects visibility in Event.
-
​Collection date- Update in database / UI and Manifest
-
COL_DATE
-
-
Collection time window- Update in database and Manifest
-
COLL_TIME, COL_TO_TIME​
-
-
Delivery time window- Update in database and Manifest
-
ELT_DEL_TIME, REQ_DEL_TIME​
-
-
Instructions - Update in database / UI and Manifest
-
Delivery notes - Update in database / UI and Manifest
-
Collection notes - Update database / Manifest
-
Capped route - Update in database / Manifest
-
Sales location - Update in database / search filters
-
Purchase location - Update in database
-
HU ID - Update in database
-
HU Quantity - Update in database
-
HU Qty Delivered
-
HU Weight - Update in database
-
HU Total Weight - Update in database
-
Product Quantity - Update in database
-
Product Del Quantity - Update in database
-
Fixing number ref - Update in database and Manifest
-
Cus Consignee Ord No - Update in database and Manifest
-
Purchase DO number - Update in database and Manifest
-
​​
-
Updates to these data types will result in the movement being 'replanned', so removed from current status in ROUTE2 if = ONHOLD / REJECTED/ UNALLOCATED . The movement will be replanned again going through Credit check process. and mileage calculation as if a NEW route.
-
Address source (all fields)- Update and replan on new route, new credit check
-
Address destination (all fields)- Update and replan on new route, new credit check
-
ROUTE No- Update and replan on new route, new credit check
-
Container type - Update and replan on new route, new credit check
-
Delivery date- Update and replan on new route, new credit check
-
-
-
If above movement = status RECYCLE. Then simply update, donot replan.
PUBLISH Status
The update of Order data is dependant on the data type and the Event status it is currently in at the point of updating.
Below documents each item that can be updated and how it will be updated in Event.
​
-
Follow current Event update process for Publish status. Unpublish back to ROUTE2, replan and leave new route in ACTIVE status
-
​Collection date to and from- Unpublish, replan in ROUTE2, leave in active status
-
Delivery date to and from - Unpublish, replan in ROUTE2, leave in Active status
-
ROUTE No - Unpublish, replan in ROUTE2, leave in Active status
-
Source / Dest address - Unpublish, replan in ROUTE2, leave in Active status
-
Container type - Update and replan on new route, new carrier. Leave in ACTIVE status. If no rate for the new container type, move to unallocated.​​​​
-
Product Quantity - Update and replan on new route, new carrier. Leave in ACTIVE status​​​​
-
​​
​
-
Update rate on the fly, recalculate rate. Leave in PUBLISH status
-
Collection time window - Update in database and Manifest
-
Delivery time window - Update in database and Manifest
-
Instructions- Update in database / UI and Manifest
-
Delivery notes- Update in database / UI and Manifest
-
Collection notes - Update in database and Manifest
-
Capped route - Update in database and Manifest
-
Sales location - Update in database
-
Purchase location - Update in database
-
HU ID - Update in database
-
HU Quantity - Update in database
-
HU Qty Delivered - Update in database
-
HU Weight - Update in database
-
HU Total Weight - Update in database
-
Product Del Quantity - Update in database
-
Fixing number ref - Update in database and Manifest
-
Cus Consignee Ord No - Update in database and Manifest
-
Purchase DO number - Update in database and Manifest​
-
​
​​​
-
​
ACCEPTED Status
The update of Order data is dependant on the data type and the Event status it is currently in at the point of updating.
Below documents each item that can be updated and how it will be updated in Event.
​
-
The below fields will follow the standard replan process, taking the route back to ROUTE2, but will replan in ROUTE2 using the same carrier as already allocated.
-
​Collection date to and from- Update in database, replan, CC and keep same carrier, auto publish
-
Delivery date to and from - Update in database, replan, CC and keep same carrier, auto publish
-
ROUTE No - Update in database, replan and keep same carrier, auto publish
-
Source / Dest address - Update in database, replan, CC and keep same carrier, auto publish
-
Container type - Update and replan on new route, new carrier, auto publish​​​​. If no rate for the new container type, move to unallocated..​​​​
-
Product Quantity - Update and replan on new route, new carrier, auto publish​​​​
-
​​​
​
-
The below are the same as PUBLISHED status in how they update = direct update in Accepted status. so Update rate on the fly, recalculate rate. Leave in ACCEPTED status
-
Collection time window - Update in database and Manifest
-
Delivery time window - Update in database and Manifest
-
Instructions- Update in database / UI and Manifest
-
Delivery notes- Update in database / UI and Manifest
-
Collection notes - Update in database and Manifest
-
Capped route - Update in database and Manifest
-
Sales location - Update in database
-
Purchase location - Update in database
-
HU ID - Update in database
-
HU Qty Delivered - Update in database
-
HU Weight - Update in database
-
HU Total Weight - Update in database
-
HU Quantity - Update in database
-
Product Del Quantity - Update in database
-
Fixing number ref - Update in database and Manifest
-
Cus Consignee Ord No - Update in database and Manifest
-
Purchase DO number - Update in database and Manifest​
-