| Description |
* Background/Objectives
** There is up to three pieces of data to capture on a transaction.
*** Card
*** Vehicle
*** Driver
** Some Networks only support two items, some handle all three.
** CFN and PacPride
*** Translate Vehicle Cards into Vehicle #s
*** Translate Driver Pins into Driver Cards
** Voyager, Wright Express, NBS, EEE
*** Sends Vehicle Card as a Card
*** Sends Driver Pins as a Vehicle
*** Voyager Can Provide all three pieces of information.
** If a customer has multiple networks that sends information in in different formats, we have a need to capture it consistently to allow for reporting between formats on the same invoice.
** For Example:
*** Wright Express has a Driver Pin 4130
*** PacPride has a Vehicle 4130
*** Both values go into i21 as the Vehicle # and is causing errors.
** Clean Up Verbiage to Portal Users
*** Currently they see Driver Pins in Vehicles.
* Requirements
** Standard Data Conversion
*** Add Driver Pin to existing Transaction table
*** Add Driver Pin to existing CF Invoice History Transaction table
** For Manual Data Conversion
*** Identify one-time SQL Script to Move Vehicles into Drivers Pins.
**** Insert All Vehicles into Driver Pins
**** Update Driver Pin on Transaction where Driver Pin = Vehicle on Transaction
**** Update Driver Pin on Invoice History Transaction wehre Driver Pin = Vehicle on Transaction
**** Remove all Vehicles from Transactions
**** Remove all Vehicles from Setup
*** This will be manual SQL script only and will not be on any screens.
*** Then as customers upgrade to 19.1 that are impacted, we will run this and change import mappings.
**** Lassus for NBS
**** Reed Oil for Wright Express and EEE
**** MCP for Voyager, others???
**** Rhoads Energy for Voyager
|