View source for EST 316159 Partnerlink Cancel and Redelivery method

{{Template:Estimate
|Supimix_Client_Code=PART
|Supimix_Project_Code=DEV
|Supimix_Site_Code=PART
|Supimix_Client_Reference=&nbsp;
|Supimix_Number=316159
|The_version_of_the_document=0.2
|Your_Name=A Walker
|Supimix_PO_Reference=Unknown
|Supimix_Priority=3
|Date_(DD/MM/YY)=27/03/2014
|Clients_Customer=N/A
|System_Version_being_changed=Latest
|Free_Of_Charge=Y
|Client_Request=ePOD functionality required for Cancellation and Redelivery. 
|OBS_Solution={{#vardefine:System|''CALIDUS'' ePOD}}


'''Description of problem'''

The Auto-Import functionality for the Partnerlink JobShare format currently checks whether the job already exists by checking the Site, Job Code and Type (Collection or Delivery) passed in the uploaded data file. 
If the job is found, this is seen to be an update of the existing job. As the job that is found has been cancelled already in the application, the system will not update the job to preserve the activity trail.

'''Solution'''

The upload 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 already has recorded 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 the existing 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.

{{Note}} This does not allow for jobs with the same reference to be planned onto multiple loads at the same time (for example, multi-legged trips, split deliveries). This is not expected to occur for Partnerlink.

In detail: 
* If the Job does not exist, a new job will be created.
* If the Job exists, at status Completed or Cancelled, and the Load ID on file is different to that in the incoming file, a new job will be created.
* If the Job exists, at status Completed or Cancelled, and the Load ID on file is the same as the incoming file, the job update will not occur - the file will not be rejected, the processing for other jobs will occur. 
* If the Job exists, at status In Progress or Pending, the job found will be updated with the details on the incoming file. 
<br />
<br />
<br />
<br />

|Requirements_Days=0
|Estimation_Days=0.25
|Functional_Specification_Days=0.25
|Technical_Specification_Days=0
|Development_Days=1.0
|Testing_and_Release_Days=0.5
|Implementation_Days=0.0
|Project_Management_Days=0
|Year=2014}}