Air CT HAWB

From UG

(Difference between revisions)
Jump to: navigation, search
(RFC and Next Version)
(Version 5.1)
Line 100: Line 100:
* [ss5(+)] Commod Table. Apply this spec: http://mantis.jaguarfreight.com/wiki/Commodity_Table_for_Pdfs#Version_5.0_Textarea_based  
* [ss5(+)] Commod Table. Apply this spec: http://mantis.jaguarfreight.com/wiki/Commodity_Table_for_Pdfs#Version_5.0_Textarea_based  
-
 
+
=== Special case: multipage ===
 +
* This document can not be more than 1 page. At the same time system would generate 2nd page if user enters too many lines into text areas in commod table. User can preview and reduce until all fits in one page. Is that good enough or we need validation / warnings or automatically cut off overflow???
=== Known bugs ===
=== Known bugs ===
-
* bug1] [fixed] see HAWBbugLongDescriptionDistribution.JPG in http://mantis.jaguarfreight.com/mantis/view.php?id=1077
+
* bug1] (FIXED) see HAWBbugLongDescriptionDistribution.JPG in http://mantis.jaguarfreight.com/mantis/view.php?id=1077
* b2] on pre-printed paper - doesn't print correctly
* b2] on pre-printed paper - doesn't print correctly

Revision as of 17:55, 28 August 2009

Figure 1. Hawb pdf with sections breakdown
Figure 1. Hawb pdf. Large size
File:HAWB-sectionC-1.JPG
File:HAWB-template.JPG
File:MAWBL-HAWBLsectionYYYlogic-1---YYYlogic-for-zeros.JPG

Contents

Dev

Version 5.0

This is Ver 5.0

Top Section

  • Filed: <logic>
  • SHIPPER'S NAME AND ADDRESS: GT.Shipper
  • AIRWAYBILL NUMBER: ET.Master Airway bill
  • AIRWAYBILL ISSUED BY: Login Office abbrev + Login User's Fist and Last Name
  • Logo: Login ofis logo
  • REFERENCE NUMBER: CT#
  • -
  • CONSIGNEE'S NAME AND ADDRESS: GT.Consignee
  • -
  • ISSUING CARRIER'S AGENT NAME AND CITY: <login office country>, <city>, <login user first name>, <login user last name>
  • AGENT ATA CODE: empty
  • ACCOUNT NO: empty
  • AIRPORRT OF DEPARTURE AND REQUESTED ROUTINE: ET.Airport of Departure
  • ACCOUNTING INFORMATION: empty
  • ... empty box...: empty

Mid Section

  • TO: Airport Of Destination:
  • BY FIRST CARRIER: ET.Airline
  • TO; BY; TO; BY all empty
  • CRNCY - dropdown with all currencies (see Admin), default to login office curr
  • CHGS: - read only 2-letter char string based on info in 2 fields: "WT/VA" and "OTHER"
  • WT/VA - radio group, pre-fill based on ET.Freight
  • OTHER - radio group, pre-fill based on ET.Freight
  • DECLARED VALUE OF CARRIAGE: empty??
  • DECLARED VALUE OF CUSTOMS: empty??
  • AIRPORT OF DESTINATION: Airport Of Destination:
  • FLIGHT: ET.Flight One #
  • DATE:ETD - Est Time of Dept
  • AMOUNT OF INSURANCE: empty??
  • empty box: empty

Commod Section

HAWB Commod Sec For Groups

Haz vs Non-Haz

  • This is a table with 6 lines: 3 lines for Haz and 3 lines for Non-Haz info
  • If CT is only Haz then show only Haz lines (utilize top 3 lines, bottom 3 would be empty)
  • If CT is only non-Haz then show only non-Haz lines (utilize top 3 lines, bottom 3 would be empty)
  • If CT is a mix of Haz/Non Haz then utilize top 3 lines fo Haz and bottom 3 for Non Haz)

Fields

  • NO. OF PIECES CT.TableA.Ttl HU
  • GROSS WEIGHT CT.TableA.Ttl G kg
  • kg/lbs dropdown re-calc on the fly
  • RATE pre-fill first line to "Q"
  • CHARGEABLE WEIGHT pre-fill first line to ET.Chargeable weight
  • RATE/CHARGE
  • TOTALS
  • NATURE AND QUANTITY OF GOODS

Totals line

Editing Features

  • Line Up/Down
  • Writing Across

Mapping from Template to pdf

...

Special case: CT Groups

Bottom Section

Version 5.1

File:Hawb_blank
HAWB.haz.example
HAWB.non-haz.example


Apply specs below over Ver 5.0 specs.

  • [ss1] This doc will be printed on pre-printed paper. Size: Letter. it means we need to re-allign all fields; remove lines and some static text See Fig. Hawb_blank
    • [ss1b] (+) Pls leave old version (not on pre-printed) as well in template's dropdown.
  • [ss2] IF Haz=true THEN Add to "handling info" textarea this text: "Dangerous goods as per attached shippers Dangerous Goods Declaration"
  • [ss3] (-)

Special case: multipage

  • This document can not be more than 1 page. At the same time system would generate 2nd page if user enters too many lines into text areas in commod table. User can preview and reduce until all fits in one page. Is that good enough or we need validation / warnings or automatically cut off overflow???

Known bugs

  • b2] on pre-printed paper - doesn't print correctly

RFC and On Hold

  • [ss1] Group generate case. Add to Accounting Info Box this: "ITN:" + ExpTab.Export Customs Information. Also add "++" if more than one CT is in the group.
  • [ss2] Group generate case. Add to Accounting Info Box this: list all CT numbers that were selected for a group.
Personal tools