CT.Ocean.PickupOrder

From UG

Revision as of 16:54, 11 December 2009 (edit) Alex (Talk | contribs) (→Dev History) ← Older edit		Revision as of 21:33, 17 December 2009 (edit) (undo) Alex (Talk | contribs) (→V 2.1) Newer edit →
Line 69:		Line 69:
	UNDEFINED / AIR / OCEAN / Trucking Air/Ocean		UNDEFINED / AIR / OCEAN / Trucking Air/Ocean
-	Pick up location        Gen 5	+
-	Delivery location      Gen 6	+	PICK-UP/COLLECTION FROM: = Pick up location        Gen 5
-	Trucker                  Gen 8	+	DELIVERY TO: = Delivery location      Gen 6
		+	COMPANY:=Trucker                  Gen 8
	TRUCKING DOMESTIC;		TRUCKING DOMESTIC;
-	Shipper                   Gen 2	+	PICK-UP/COLLECTION FROM: = Shipper     Gen 2
-	Consignee              Gen 3	+	DELIVERY TO: = Consignee              Gen 3
-	Trucker                  Gen 8	+	COMPANY:=Trucker                  Gen 8
	== Dev History ==		== Dev History ==

---

Revision as of 21:33, 17 December 2009

Contents 1 Exec Summary 2 Intro 3 Section A (logo+addr) 4 Sec B (CT fields, etc) 5 Section C (PO/SKU table) 5.1 Questions: 6 V 2.1 7 Dev History

Exec Summary

TBD

Intro

• See Pdf example with sections

• Link to parent Mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=587
• Link to QA reports for this component

Section A (logo+addr)

a1] This is a standard Logo + Jag address pdf banner.

Sec B (CT fields, etc)

b1] This section have a number of fields pulled from CT/group. See this image

mapping for MOT = OCEAN

• pick up // impTab.cargo location
• deliv // impTab.deliv to

b2] Note:

• green dot means - this field is read only on template
• orange dot means - in case of group generate this field comes from CT from which this template is generated
• blue dot means - in case of group generate this fieldmust show accumulative info from all selected CT

b3] kg/lb dropdown must convert on the fly

Section C (PO/SKU table)

Questions:

a) How many PO/ItemCode textboxes should be on template?

   As many as there are in CT/group --Alex 21:54, 22 June 2009 (UTC)

b) Do we need ability to add additional PO/ItemCode textboxes on template?

No.

c) If there are more PO/ItemCode in CT than we can display on template, what to do with the rest?

see d) below

d) If there are more PO/ItemCode pairs than we can fit on the first page on pdf do we need second page? If yes then What is the 2nd page design?

 Note: PDF with today's fonts & fields can contain 10 rows х 3 cols = 30 --Andrei 19:50, 30 June 2009 (UTC)

If there are more PO/SKU pairs than can fit on one page then on template and pdf deisplay this: 
"Additional PO/Item #'s are included in this shipment, and could not be displayed on this document."

e) For Group generate case how to form list of PO/ItemCode from multiple CTs? What if it is very large?

Take PO/SKU from current CT first and then from any additional selected CT in no particular order.

V 2.1

• ss1 // this doc was released for ocean. It should be available for all modes, including “undefined”.
• ss2 // change mapping for ocean for some fields - see below.

Maping should be:

UNDEFINED / AIR / OCEAN / Trucking Air/Ocean

PICK-UP/COLLECTION FROM: = Pick up location        Gen 5
DELIVERY TO: = Delivery location       Gen 6
COMPANY:=Trucker                   Gen 8

TRUCKING DOMESTIC;
PICK-UP/COLLECTION FROM: = Shipper     Gen 2
DELIVERY TO: = Consignee               Gen 3
COMPANY:=Trucker                   Gen 8

Dev History

Specs folder with all versions/history: http://mantis.jaguarfreight.com/svn/ct2/SS/ops/pdfs/ocean_indiv_ct/Pickup_Order/

old: http://docs.google.com/View?id=dgwxtwcq_25c37qrkhf

--Alex 23:38, 17 June 2009 (UTC)