Minimum Version Required: 22.11
Steps
How to manage Import Conflicts
Using Universal Search, navigate to the Import Conflicts dashboard
Invoices with conflicts are displayed with details such as Date, Invoice Number, Customer, Route, and Error
NOTE: If there are many conflicted Invoices, you can use filters to narrow down the results then click Filter Results
Review the Error. The Error could be:
a. Problem 1: Payment can not be edited, Load Sheet (xxxx) is already Balanced. This means the handheld user is trying to add a payment to an invoice that is already balanced
To import this conflict select the load sheet link from Import Conflicts
Edit Load Sheet Status to Loaded
Confirm the invoice in question is not locked (unlock invoice)
Return to Import Conflicts
Select the check box next to Import conflict and execute ‘Import’
b. Problem 2:Locked with Signature. This means the handheld user is trying to make changes to an invoice that has already been locked with a signature. Once a signature is captured, you can no longer make changes to that Invoice. One explanation could be that two users have the invoice on their handheld and one user has already synced the signature on the invoice
To import this conflict select the Invoice link from Import Conflicts
Select Arrow next to the invoice
If the user has ‘Invoice Unlock’ permission select the ‘Unlock’ button
Return to Import Conflicts
Select the Check Box next to Import Conflict and execute ‘Import’
c. Problem 3:It's currently after the cut-off time. You can no longer send presell invoices for [date]. This means the handheld user (salesman) is trying to sync in a new sale on an invoice after the route's cut-off time
To Import this conflict confirm whether the error displays ‘Can Not Move’ or ‘Move Invoice to A Different Load Sheet’
To import to the original invoice and load sheet select the check box and execute ‘Import’
To import to a different load sheet select the checkbox next to the import conflict
Select ‘Import to Load Sheet…’
Select the delivery date and load sheet intended for delivery
d. Problem 4: Pallets for [Customer] Have Already Been Printed. Printed Pallet List = xxxx. This means the handheld user is trying to make an edit to an invoice that has been processed for picking. You can import this conflict with the proper permission, but you must re-process this invoice to picking
To Import conflict locate the route and pallet in the delivery optimizer
Select plus sign next to route
Select the checkbox next to the customer
Palletize
Select pallets
Select ‘Mark Not Printed’
Return to Import Conflicts
Select the check box next to Import conflict and execute ‘Import’
Imported invoice transactions will need to be palletized
e. Problem 5: Load Sheet (xxxx) is already Returned. This means the handheld user is trying to make changes to an invoice that is on a load sheet that is already returned. You may import this conflict, but it will require the load sheet to be un-returned and then returned by the warehouse again
To import this conflict select the Load Sheet link from Import Conflicts
Edit Load Sheet status
Confirm the invoice in question is not locked (unlock invoice)
Return to Import Conflicts
Select the check box next to Import Conflict and execute ‘Import’
f. Problem 6: Mismatch Between Customer Location and Load Sheet Location. Review System Setting 128) Allow Cross Location Invoices on other Locations' Routes. If True, 'Problem 6: Location Mismatch Between Customer Location and Load Sheet Location' import conflicts will not occur. If False, when importing to load sheet, users will now see Load Sheets from the Customers location.
System setting 128:Allow Cross Location Invoices on other Location's Routes. Remittance Invoices are omitted from this Setting and should be set to TRUE.
Go to Delivery Optimizer
Select the Load sheet where the invoice is located and the load sheet where you want it to be moved
Click Dynamic routing/Mapped routing
Drag/select the customer invoice to the other load sheet
Click Save
Select a view or action option to process the invoice
Import: Update the Invoice if it is already an existing member of a Load Sheet
Cancel Import: Remove the Invoice Audit from Import Conflicts
View Invoice Audit: View all Invoice Audit records
View Canceled: View all canceled Invoice Audits
Import To Load Sheet: Add the Invoice to a new Load Sheet (provided it is not already a member of a Load Sheet)
Best Practices
You may need to resolve the underlying problem first before importing (such as unreturning the load sheet if it was returned before the route was completed, etc.)
Not all conflicts should be imported or canceled. They must be managed according to the situation
You should define users that will be responsible for managing the import conflicts