Skip to main content

MoveEvents EDBL

Distributor reference for the MoveEvents EDBL import: move existing delivery events and their invoices to another route plan/load sheet, or update sequence and start time. Update Only; needs InvoiceEdit permission; v22.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 22.01

Pre-Conditions

  • User must have InvoiceEdit permission to run this import

  • This routine only supports the "Update Only" import action

  • Events must already exist in the system

  • Load sheets with status of "Loaded" or higher cannot be modified

Steps

The MoveEvents EDBL routine allows you to update and move delivery events and their associated invoices from one route plan to another. The routine works by:

  1. Identifying existing events by the EventID provided in your import file

  2. Moving the events to a different plan if a new PlanID is specified

  3. Moving associated invoices to the load sheet of the destination plan

  4. Updating event sequence and/or start time values if provided

  5. Re-sequencing invoices on affected load sheets automatically if sequence changes are made

This routine is particularly useful when you need to move pre-order invoices along with driver sell stops to maintain routing consistency.

Note that the routine can only update existing events and will not create new ones. It will ignore any records in your import file that don't match existing EventIDs in the system.

Fields And Definitions

  • EventID - Integer - The unique identifier of the event to update. This field is required and used to identify the existing event in the system.

  • Sequence - Integer - The new sequence number for the event. If provided, this will update the event's sequence in the route plan.

  • StartTime - DateTime - The new start time for the event. If provided, this will update when the event is scheduled to begin.

  • PlanID - Integer - The identifier of the destination plan where the event should be moved. If provided and different from the current plan, the event and its associated invoices will be moved to this plan.

Best Practices

  • Always verify your EventIDs are correct before importing to avoid unintended changes

  • Check that destination plans (PlanID) exist in the system before attempting to move events

  • Ensure load sheets are not already in "Loaded" status before attempting to move invoices

  • Run this import outside of peak delivery hours to minimize impact on operations

  • Consider sequencing all events in a plan when making sequence changes to ensure proper route order

  • After import completion, verify events and invoices have moved correctly in the system

  • Use this routine in conjunction with OrderRouting EDBL when reorganizing complete routes

Did this answer your question?