EST 316159 Partnerlink Cancel and Redelivery method
![]() |
CHANGE REQUEST ESTIMATE |
Client | PART | Project | DEV | Site | PART |
Client Reference | Aptean Reference | 316159 | Estimate Version | 0.2 | |
Prepared By | A Walker | Estimate Date | 17/03/2014 | ||
Invoice Reference | Unknown | Priority | 3 | ||
Customer | N/A | System Version | Latest |
Client Request |
ePOD functionality required for Cancellation and Redelivery. |
Aptean Solution |
Description of problem
The Auto-Import functionality for the Partnerlink JobShare format currently checks whether the job exists by checking the Site, Job Code and Type (Collection or Delivery) passed in. If found, this is seen to be an update of the existing job. As the job that is found has been cancelled already, the system will not update the job, to preserve the activity trail. Solution The process will be modified to recognise that confirmed jobs (at completed or cancelled status) should not be updated, but instead a new job created, if the Load specified on the incoming file is different to what the system has against the job. If the job is found in progress or pending, the job will be updated - this means that the job will be moved from one load to a different one and the details updated, if the incoming file specifies this. This change allows the TMS systems to re-plan jobs until they have been completed. Re-planning jobs after completion result in new jobs being created.
In detail:
|
Cost Details | |||
Activity | Hours | Rate per hour (£) | Cost (£ Exc. VAT) |
Requirements | 0.00 | 0 | £0.00 |
Change Request Evaluation | 0.25 | 0 | £0.00 |
Functional Specification | 0.25 | 0 | £0.00 |
Technical Specification | 0.00 | 0 | £0.00 |
Development | 1.00 | 0 | £0.00 |
Testing and Release | 0.50 | 0 | £0.00 |
Implementation | 0.00 | 0 | £0.00 |
Project Management | 0.00 | 0 | £0.00 |
TOTAL | 2.00 | £0.00 |
Estimate excludes training, release to live and go live support. |
Copyright © Aptean 2014. |