MAWB (M)
From UG
(→Addition info) |
((Link to Ops PDFs Old category)) |
||
| Line 1: | Line 1: | ||
| - | [[Category: | + | [[Category:Ops Pdfs Old]] |
== Mantis == | == Mantis == | ||
Revision as of 20:02, 5 June 2010
Contents |
Mantis
Business Needs and Requirements
Definitions
(wikipedia) International AWBs that contain consolidated cargo are called master air waybills (MAWB). MAWBs have additional papers called house air waybills (HAWB). Each HAWB contains information of each individual shipment (consignee, contents, etc.) within the consolidation. International AWBs that are not consolidated (only one shipment in one bill) are called simple AWBs. A house air waybill can also be created by a freight forwarder. When the shipment is booked, the airline issues a MAWB to the forwarder, who in turn issues their own house air waybill to the customer.
(export911) The freight forwarder may consolidate the consignments of several independent shippers that are intended for the same airport of destination and dispatch them together under one air waybill (AWB) issued by the carrier, known as master air waybill (MAWB), with a cargo manifest detailing such consignments attached to the MAWB. The freight forwarder in turn issues to each shipper its own AWB, known as a house air waybill (HAWB) or freight forwarder's waybill.
In the case of air freight using a house air waybill (HAWB), just like in ocean freight using a house bill of lading (the freight forwarder's bill of lading), it is the freight forwarder's handling agent at destination, not the carrier, who notifies the consignee of the cargo arrival at destination.
Technical Specification
Summary
Template
Template Top Section
Template Bottom Section
Header
Top Section
Bottom Section
Footer
Special case: Groups
Additional Figures
Figure X
History
Archive
http://mantis.jaguarfreight.com/wiki/Air_M_MAWBL
Several changes requested by Paris office
- Parent mantis for a group of tasks: http://mantis.jaguarfreight.com/mantis/view.php?id=1093
- Add admin to edit office specific airline fields
- http://mantis.jaguarfreight.com/mantis/view.php?id=1602
- see "Airlines Entity with Office fields.JPG" attached to mantis. This is one option. Alternatively we could add "per Office Admin" (Admin > Paris Admin, etc) where each office would maintain its local settings
- Add new fields: carrier’s headquarter address; carrier's IATA code; carrier’s account number
- http://mantis.jaguarfreight.com/mantis/view.php?id=1603
- add these to template and pdf
- mappings as defined in mantis#1602
- 1) Add JFS PARIS IATA code into the system 2) pull it into MAWB and HAWB automatically
- http://mantis.jaguarfreight.com/mantis/view.php?id=1604
- Add this into Admin > Office Profile OR Admin > Paris Admin
- pull this into "Agent's IATA code" field on template for HAWB / MAWB
- "Charges section": 1) Need 7 lines, not 4; 2) replace words Carrier and Agent with C and A
Addition info
- 1602: Spec is updated: Y
- 1603: Spec is updated: N
- 1604: Spec is updated: N
- 1605: Spec is updated: N
NOTE: Carrier's headquarter address, Agent IATA Code, and Account No are mapped from Admin>Carrier>Airlines. They are office specific. If an operator is a French user, when he/she generates MAWB, these 3 info from France office (from local office setting for airlines) for that particular airline will be pre-filled on the template and pdf doc, when is generated.
For example, if Airline is set to Air France (on ExpTab.Airline or Master Details Tab.Airline), carrier's headquarter address, Agent IATA Code, and Account No for local office will be pre-filled on the MAWB template and pdf doc.
Please see [Detail]
