In Transit Report

From UG

Revision as of 23:03, 7 July 2009 (edit) Alex (Talk | contribs) (→Output) ← Older edit		Revision as of 23:04, 7 July 2009 (edit) (undo) Alex (Talk | contribs) (→Output) Newer edit →
Line 95:		Line 95:
	** Shipper		** Shipper
	** Consignee		** Consignee
-	** Quantity, '''new:'''depends on the MOT: --[[User:Alex|Alex]] 23:03, 7 July 2009 (UTC)	+	** Quantity,
-	*** if FCL, then show number of containers (example: "5 containers")	+	*** '''new:'''depends on the MOT:
-	*** if LCL, then show Volume ("23 cbm")	+	**** if FCL, then show number of containers (example: "5 containers")
-	*** if AIR, then show Chargeable Weight ("200 kg")	+	**** if LCL, then show Volume ("23 cbm")
-	*** if TRUCK, then show Gross Weight ("200 kg")	+	**** if AIR, then show Chargeable Weight ("200 kg")
		+	**** if TRUCK, then show Gross Weight ("200 kg")
		+	*** --[[User:Alex|Alex]] 23:04, 7 July 2009 (UTC)
	** from country		** from country
	** to country		** to country

---

Revision as of 23:04, 7 July 2009

Contents 1 Business Needs and Requirements 2 Intro 3 Dates Conditions 3.1 MOT=Truck 3.2 MOT = Air 3.3 MOT = LCL 3.4 MOT = FCL 3.5 QA Plan 4 Filters 4.1 QA plan 5 Output 5.1 QA plan 6 RFC 7 Dev notes

Business Needs and Requirements

This report is used to identify those shipments that already "considered on the move" but "considered not yet delivered". Of course we can find out about that based on dates we store for shipment.

Because of the word "considered" we have more than one condition. For example for CT to be "in transit=on the move" it is enough to have estimated Pickup Date to be set, while actual can still be empty. And so on.

Intro

• The result of this report is a number of CTs in the system that satisfy Dates Conditions and Filters.
• "Dates conditions" and Filters are MOT-specific but user has a choice of running report for one, several or all MOT at once.
• CTs in output are grouped - each group corresponds to one MOT. This is similar to how CTs are grouped per MOT in Where Is Report

Dates Conditions

• These conditions are MOT specific
• Conditions below must be true for CT to be on this report
• They are hard coded

MOT=Truck

((GenTab Estimated Export Pickup Date is not empty 
  OR GenTab Actual Export Pickup Date is not empty 
 )AND
  GenTab Actual Delivery is empty ) = true

MOT = Air

((GenTab Estimated Export Pickup Date is not empty 
  OR GenTab Actual Export Pickup Date is not empty 
  OR ExpTab Arrival Into Warehouse Date is not empty
  OR ExpTab Airport of Departure ETD is not empty 
  OR ExpTab Airport of Departure ATD is not empty
  ) AND
  ImpTab Actual Delivery is empty ) = true

MOT = LCL

((GenTab Estimated Export Pickup Date is not empty 
  OR GenTab Actual Export Pickup Date is not empty 
  OR ExpTab Arrival Into Warehouse Date is not empty
  OR ExpTab Origin Terminal ETD is not empty 
  OR ExpTab Origin Terminal ATD is not empty
  OR ExpTab Port Of Loading ETD is not empty 
  OR ExpTab Port Of Loading ATD is not empty
  ) AND
  ImpTab Actual Delivery is empty ) = true

MOT = FCL

 (For every containerX on Container Table: 
      Estimated collection OR 
      Actual collection is not empty) 
  OR ExpTab Origin Terminal ETD is not empty 
  OR ExpTab Origin Terminal ATD is not empty
  OR ExpTab Port Of Loading ETD is not empty 
  OR ExpTab Port Of Loading ATD is not empty 
AND 
  For at least one containerX on Container Table:
      Actual Delivery is empty

QA Plan

• t1 for every MOT above design and run:
  • at least 2 sets of conditions for given CT that should make it APPEAR on report
  • at least 2 sets of conditions for given CT that should make it NOT APPEAR on report

Filters

• s1 Filters are selected by user
• s2 In front of each filter there is a checkbox. If checked then this filter must be applied.
• s3 All filters are multiselect
• s4 Air only filters:
  • Airport(s) of departure
  • Airport(s) of destination
• s5 Ocean only filters:
  • port(s) of departure
  • port(s) of destination
• s6 Other filters (any MOT):
  • 1 Client
  • 2 Origin Country
  • 3 Destination Country
  • 4 Origin Region
  • 5 Destination Region
• s7 Display PO Numbers on report results
• s8 [new] MOT filter - controls for what MOT to run this report --Alex 22:54, 30 June 2009 (UTC)

QA plan

• t1 verify s1-8. For every filter design and run 2-3 different tests

Output

• s1 Is in the form of Excel file
• s2 It consists of 4 sections (one per MOT). Each has same design
• s3 Each section is a table with the following columns
  • CT #
  • Shipper
  • Consignee
  • Quantity,
    • new:depends on the MOT:
      • if FCL, then show number of containers (example: "5 containers")
      • if LCL, then show Volume ("23 cbm")
      • if AIR, then show Chargeable Weight ("200 kg")
      • if TRUCK, then show Gross Weight ("200 kg")
    • --Alex 23:04, 7 July 2009 (UTC)
  • from country
  • to country
  • estimated/actual departure
  • estimated/actual arrival
  • PO (show only first PO, show PO++ if more than one PO exists)

• s4 sort by: estimated/actual arrival, to country, qty
• s5 For MOT=Air, Truck each line represents one CT

• s6 For MOT=FCL, LCL each line represents:
  • One CT only if that CT does not have Master
  • If CT has a Master then:
    • each line in the table above represent one master
    • ANY CT from that master is shown in a dropdown
    • all fields displayed are fields for THAT CT.
    • if user selects another CT then all fields are re-freshed (except Quantity that always shows value for entire Master)

• s7 [View] button opens CT record
• s8 For departure and arrival columns: Show estimated value if actual value is not set

QA plan

• t1 verify s1-s5
• t2 verify s6 for Ct without a Master
• t3 verify s6 for Ct with Master
• t4 verify s7, s8

RFC

Dev notes

mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=928