6.1.3 Example of creating a batch E-mail
¡@
The E-mail must be structured in such a way that the receiving party can both re-route and parse the message in order to break out the individual component parts for on forwarding to the Airline.
It is essential that in a batch mode, the messages arrive with the Airline prior to receipt of the consignment and, in this mode, the recommendation is for transmissions to be made at least every 30 minutes. Some Agents are likely to agree flat file and batch processes directly with the CCS provider, with whom they may also have bilateral agreements.
¡@
Ref. | Data Item | Comment |
1.. | ¡§ILA:¡¨ | Start of inline addressing |
2. | (A/L) | Airline who should receive
these Messages. This line can be repeated if the messages are to be sent to more than one Airline. The address could be as simple as the carrier code or may Include a local PIMA address. |
3. | ¡§ILA:¡¨ | End of inline addressing |
4. | ¡§---Start of AWB---¡§ | Beginning of master air
waybill Message |
5. | (FWB or flat file) | Body of master air waybill |
6. | ¡§¡XEnd of MAWB---¡§ | End of master air waybill message |
7. | ¡§---Start of HAWB---¡§ | Beginning of first house air waybill |
8. | (FZB or flat file) | Body of house air waybill |
9. | ¡§---End of HAWB---¡§ | End of house air waybill message |
10. | ¡§---Start of HAWB---¡§ | Beginning of next or last
house air Waybill message |
11. | (FZB or flat file) | Body of next or last house air waybill |
12. | ¡§---End of HAWB---¡§ | End of house air waybill message |
13. | ¡§---Start of FHL---¡§ | Beginning of breakdown manifest |
14. | (FHL or flat file) | Body of breakdown manifest |
15. | ¡§---End of FHL---¡§ | End of breakdown manifest |
¡@
6.1.4 Internet FTP file
¡@
¡@