HDTN-289962 - Partial Diversions

Issue No: MFT-1819
Created 3/1/2023 12:03:57 PM
Type Feature
Priority Critical
Status Closed
Resolution Fixed
Fixed Version 22.1
Description *This issue relates to i21 Help Desk ticket:* [ HDTN-291598 - Run UAP automation on latest 22.1 build and if passes, install in production 03/20 Night |https://helpdesk.irely.com/iRelyi21live/#/HD/Ticket/?ticket=HDTN-291598]   *This issue relates to i21 Help Desk ticket:* [ HDTN-289962 - Partial Diversions|https://helpdesk.irely.com/iRelyi21live/#/HD/Ticket/?ticket=HDTN-289962]   *Steps:*   1. Create TR Load   2. Go to MISC tab and enter necessary details   4. Post TR and Generate MFT - Diversion     *Issue/Feature:* Modify the basis of destination location when generating MFT report for TR with Diversion   *Problem Statement :* We need to be able to mark part of a load as a Diversion. Currently we can only indicate that the entire load was diverted, and this causes it to populate incorrectly on MFT forms.   [Abhilash Aravindan|abhilash.aravindan@iRely.com] [Mark Hisken|mark.hisken@irely.com] [Don Osmond|don.osmond@irely.com]   *Proposed Solution:*   Presently the Misc tab in Transports module determined the Diverted transaction:   !pastedImage_d210160_0.png|height=593,width=813!   But once a State is entered in this tab, the entire transport load delivery is considered a diversion from this state which would be wrong. Hence there is a need to have the below rules in place while pulling transactions for Diversions.   |State in Diversion (Misc Tab)|State for Destination in TR Load|Transaction Rules| |WV|TN|Transaction with delivery to TN only should be fetched| |WV|WV|Transaction with delivery to WV should not be fetched as its not diverted.|   *Acceptance:* Diversion transaction should look at Distribution Header - Location not in the Original Destination State in Misc tab