Prithiviraj Potsangbam

XXXX Order Consignment Number Assignment Update v1.1 XXXX ORDER CONSIGNMENT NUMBER ASSIGNMENT UPDATE OBJECTIVES Orders for different customer going to same XXXX DEPOT will have different consignment number base on the customer number. This is to avoid closing of the consignment when the first customer picks up their order leaving the remaining orders with no documents to sign off for POD. MODIFICATION REVISION HISTORY Changed By Raj Potsangbam Raj Potsangbam Raj Potsangbam Raj Potsangbam Raj Potsangbam Date 04/06/2018 06/06/2018 12/06/2018 19/06/2018 22/06/2018 Version- Note Initial Draft Requirement Gathering and Analysis Configuration and Testing Approved Additional Configuration (consider on “XXXX DEPOT” orders) and Testing (Test 3) OVERVIEW Current XXXX DEPOT order consignment assignment process is consolidating multiple customers’ order in same consignment number (based on the consolidation logic). Potentially Depot can give away all the orders under the same consignment number to the first customer who comes to collect one of the consolidated order or there won’t be any POD for others customer order if the first customer picks-up and sign off the POD on the consolidated consignment number. Override Date will be modified to update “Ship_To_Address 3” value with “Ship_To” number which is same as the “Customer” number. This change will enhance XXXX Depot consignment consolidation and includes “Customer” number as another criteria of consolidation. 1. 2. 3. Override Data “00-XXXX - Ship to Adr3” which set “SHIP_TO_ADDRESS3” to “NULL” will be updated to set “SHIP_TO_ADDRESS3” to “SHIP_TO” record only when “SHIP_TO_ADDRESS2 LIKE ‘XXXX DEPOT%’” SHIP_TO_ADDRESS3” is also a part of consignment consolidation criteria logic and each unique record will be assigned a unique consignment number. Orders with “SHIP_TO_ADDRESS2” containing “XXXX DEPOT” will be considered during the update. This is to avoid COMPANY BRANCH transfer order consolidation process. ASSUMPTIONS 1. 2. 3. “Ship_To” field will always have the customer number. “Ship_To_Address2” contains “XXXX DEPOT” as a part of address line for DEPOT Orders. Order going to the same depot but with different consignment should not be MOP processed. FUNCTIONALITY Current Config: XXXX Issue orders from PROD Environment: Extract orders with issue for analysis. Page 1 of 3 XXXX Order Consignment Number Assignment Update v1.1 Modified Config: Configuration details. Unit Testing: In UAT Environment Test 1: To test order consignment consolidation before “Override Data” is updated. Expected Result: Orders with carrier TAN which fulfils all the other criteria of consolidation should consolidate to one consignment number irrespective of the customer when “SHIP_TO_ADDRESS3” field is NULL. Result: Orders consolidated to one consignment number : PASS Test 2: To test order consignment consolidation after “Override Data” is updated. Expected Result: Orders with carrier TAN which fulfils all the other criteria of consolidation should be consolidate to unique consignment number base on customer number when “SHIP_TO_ADDRESS3” field is populated with customer number (SHIP_TO number). Result: Order consolidated by considering customer number populated in “SHIP_TO_ADDRESS3” field provided other filed criteria of the consolidation are fulfilled. Order with the same customer number are consolidated and those which are different are assign a unique consignment number. PASS Test 3: To test consignment number assignment base on “Ship_To_Address2” content. Expected Result:   Different Customers orders going through XXXX DEPOT with “Ship_To_Address2” containing “%XXXX DEPOT%” as a part of the address text will be assigned a unique consignment number even when the orders has the same “Ship To” delivery address. Different Customers orders going through COMPANY BRANCH using carrier TAN will still have the same consignment number assignment base on the consolidation criteria. Before Wave: After Wave:      Orders going through same DEPOT and with same customers are assign with same consignment number. Orders going through same DEPOT but with different customers are assign with different consignment number. Order\s going to the same city as the Depot City (E.g. MLPOUYTH) with different “Ship_To_Address2” is assigned with a different consignment number even when the order is the same wave of the depot orders. Orders going through same COMPANY BRANCH for different customers are assign the same consignment number to allow consolidation (MOP). E.g. CVFRT and NHYTRF Branch. Orders going through XXXX DEPOT where “Ship_To_Address2” line has additional character as Prefix or Suffix to “XXXX DEPOT” e.g. “XXXX DEPOT MULDOON ST” - it will still be assigned a unique consignment number base on customer number. Status: PASS Label Output: Consolidated orders in Same wave # 39982 Individual consigmment number in the same wave # 39982 Result: No Changes in the Label output after the update: PASS Page 2 of 3 XXXX Order Consignment Number Assignment Update v1.1 Regression Testing: In UAT Environment Test 1: To test if an order -) with same “Ship To” address details with one of the order -) in previous wave (39982)- when process in a new wave is consolidated with the previous order consignment number (provided previous order still not yet ship confirmed and the load number is same). After wave: Order assigned to previous order consignment number. Test 2: To test an order -A) which have carrier TAN with similar city, state and post code as XXXX Depot order but with different “ship_to_address line 2”. Order should be assigned with a new consignment number even if it is put into the same load. After Wave: Order assigned with a new consignment number even if the order is in the same load with the previous waves orders. OPERATION APPROVAL Your signature is required as proof of acceptance of the modification described above. Name: Signature Date: Page 3 of 3