Message Mapping
User Data Dictionary
General Rules
- 1. The valid Message Function Codes for an AIROUT are:
- Original (9)
- Change (4)
- Withdraw (50)
- AIROUT messages must quote a unique Sender Reference. The ICS will use this number and the associated version number to ensure duplicate messages are not processed.
- The version number for an Original (9) message must be set at 1 or greater.
- Before the AIROUT message is processed at the application level:
- All non significant leading and trailing blanks will be stripped;
- Multiple spaces will be compressed;
- Illegal characters will be removed; and
- All nulls will be converted to blanks.
- Any errors in an AIROUT message will be reported in an AIROUT Response message (AIROUTR).
- Any advice messages resulting from the AIROUT message will be reported in an AIROUT Response message (AIROUTR).
- The maximum number of errors and advices that can be reported in a single AIROUT will be 50. No further errors or advices will be processed once the maximum number allowed for the AIROUTR has been reached.
- A Change to an AIROUT will be rejected if there is no difference between the Original and the Change AIROUT.
- Each Change AIROUT message will be considered to be a new version of the message. For each version of a message the Senders Reference Version Number must be unique and incremented from the previous version.
- Change or Withdraw AIROUT messages for which no original exist will be rejected by the ICS.
- The Withdrawal of an AIROUT is for the entire record.
- Once an Air Outturn Report has been created, amended or withdrawn online through the ICS, future processing via EDI will not be permitted.
- Where the Message Function Code is 9 (Original), the valid Line Action Code is I (Insert).
- Where the Message Function Code is 4 (Change) and the Line Action Code is populated, the valid codes are I (Insert), A (Amend) or D (Delete).
- To create a new line record, the MessageFunction Code is 4 (Change) and the Line Action Code is I (Insert).
- To amend a line record, the MessageFunction Code is 4 (Change) and the Line Action Code is A (Amend).
- To delete a line record, the MessageFunction Code is 4 (Change) and the Line Action Code is D (Delete).
AIROUT - Processing Rules
- An AIROUT is sent by a CTO or a Depot Operator to report to the Department the arrival at an Establishment of import cargo consignments. Consignments are reported when one of the following events occur.
- Unloaded from an aircraft at the first Australian Discharge Port.
- Received from another Establishment as the result of an Underbond Movement Request
- The operator of an Establishment must report the receipt of consignments within a specified time of the aircrafts arrival where the outturn is for the first Australian Discharge Port or within a specified time period where the outturn is the result of an underbond movement. See
Import Cargo Reporting Timeframes for more detail.
- The operator of an establishment will indicate the result of an outturn by using the following codes.
- SH - Short Landed
This code is used to indicate that that establishment has not received all the packages expected in the consignment. If zero packages are received, an outturn is still required with 'SH' as the Outturn Result Code and 0 as the Number of Packages. - Nil - Nil Discrepancy
The Establishment received the number of packages expected in the consignment. The actual Number of Packages received is included in the message. When outturning partshipments, "Nil Discrepancy" must relate to the entire consignment rather than individual part being outturned. - SU - Surplus packages
There were more packages received by the Establishment than reported in the consignment. The actual number of Packages received is included in the message. In all cases where SU is used, the Establishment supplying the Outturn shall be required to provide a Goods Description with the Outturn message. - SC - Surplus Consignment
A consignment is received that has not yet been reported to Customs. If the Bill information is known, this is provided in the Outturn. If the Bill information is not known, then an artificial Bill number has been allowed within the ICS which is MAWB "000-00000000" and if required HAWB "0". In all cases where SC is used, the Establishment supplying the Outturn shall be required to provide a Goods Description with the Outturn message.
- An AIROUT may include multiple Air Waybills. Each Air Waybill must be reported as a separate line.
- Customs will generate a Unique Cargo Message Identifier and Line Identifier for each AIROUT.
- An AIROUT is uniquely identified by:
- Airline Code;
- Flight Number;
- Estimated Date of Arrival;
- Outturn Establishment Code;
- Date and Time of Outturn;
- An AIROUT line is uniquely identified by:
- Master Air Waybill (MAWB); and
- House Air Waybill (HAWB) (if applicable).
- The unique document identifiers within an AIROUT cannot be amended. The existing AIROUT must be withdrawn and a new AIROUT submitted with the new identifiers supplied.
- At a minimum, the following attributes are required to withdraw an AIROUT:
- Document Name;
- Sender Reference;
- Sender Reference Version;
- Sender Site Id;
- Message Function Code;
- Airline Code;
- Flight Number;
- Estimated Date of Arrival;
- Outturn Establishment Code;
- Date of Outturn; and
- Time of Outturn.
- For all amendments to an AIROUT, the full report with all document header attributes is required.
- If the consignment being outturned is a Surplus Consignment (SC) and the Air Waybill number is not known, the MAWB supplied by the Outturn Establishment is "000-00000000".
- If the MAWB supplied is "000-00000000" then the HAWB can either be blank or "0".
- The Damaged and Pillaged Indicators are optional. If the indicators are supplied, a value of 'Y' or 'N' must be supplied.
- The Goods Description is mandatory if the Outturn Result Code is SC (Surplus Consignment) or SU (Surplus Packages).
- The ICS will provide the user with an advice confirming the successful withdrawal of an AIROUT.
- If the Estimated Date of Arrival cannot be greater than today.
- The Responsible Party Client ID is mandatory for an Original AIROUT. This is the ABN/CCID of the owner of the information, not the ABN/CCID of the document sender (note that the owner and sender may be the same client).
- The Responsible Party Client ID cannot be changed. The AIROUT must be withdrawn and a new AIROUT submitted.
Data Dependency Tables
Message Function Code | Action |
---|
ORIGINAL (9) | A new Air Waybill Outturn Report with a unique sender's reference. |
CHANGE (4) | A full Air Waybill Outturn Report containing changes to attributes excluding attributes contained within the unique business identifier. |
WITHDRAW (50) | A withdrawal of an existing Air Waybill Outturn Report. |
Data Dependency Table for Original and Change
The following table models the data dependencies of the Air Waybill Outturn Document where the document Message Function Code is "Original" or a "Change".
Data Element | ICS Business Requirement | ICS Business Rules and Comments |
---|
Document Name | Mandatory | Code is AIROUT |
Sender Reference | Mandatory | |
Sender Reference Version | Mandatory | |
Message Function Code | Mandatory | See Message Function Code table above. |
Date of Outturn | Mandatory | Universal Co-ordinated Time (UTC) in the format CCYYMMDD. Required if the 'Receipt or Unpack Indicator' is U (Unpack). |
Time of Outturn | Mandatory | Universal Co-ordinated Time (UTC) in the format HHMM. Required if the 'Receipt or Unpack Indicator' is U (Unpack). |
Responsible Party Client Id | Mandatory | The Australian Business Number (ABN) or Customs Client Identifier (CCID) belonging to the establishment responsible for communicating the outturn information to the Department. |
Flight Number | Mandatory | No stripping of characters undertaken. |
Airline Code | Mandatory | |
Outturn Establishment Id | Mandatory | Customs unique Establishment identifier. |
Estimated Date of Arrival | Mandatory | The local date in the format CCYYMMDD. Must match the Estimated Date of Arrival from the AIRIAR. |
Line Action Code | Mandatory | The valid Line Action code for an Original is: The valid Line Action codes for a Change are: I ( Insert) A (Amend) D ( Delete)
|
Outturn Result Type | Mandatory | Must have a value of one of the following: SH (Short Packages) SU (Surplus Packages) SC (Surplus Consignment) NIL (Nil Discrepancy)
|
House Air Waybill Number | Optional | |
Master Air Waybill Number | Mandatory | |
Damage Indicator | Optional | Valid Damage Indicator codes are:
Y (Damaged) N (Not Damaged)
|
Pillage Indicator | Optional | Valid Pillage Indicator codes are: Y (Pillaged) N (Not Pillaged)
|
Number of Packages | Mandatory | Must be a positive numeric value greater than or equal to zero. |
Goods Description | Optional | Required if Outturn Result Type is SU (Surplus Packages) or SC (Surplus Consignment). |
Data Dependency Table for Withdrawal
The following table models the data dependencies of the Air Waybill Outturn Document where the document Message Function Code is 'Withdraw'.
Business Term | ICS Business Requirement | ICS Business Rules and Comments |
---|
Document Name | Mandatory | Code is AIROUT |
Sender Reference | Mandatory | |
Sender Reference Version | Mandatory | |
Message Function Code | Mandatory | See Message Function Code table above. |
Date of Outturn | Mandatory | Universal Co-ordinated Time (UTC) in the format CCYYMMDD. Required if the 'Receipt or Unpack Indicator' is U (Unpack). |
Time of Outturn | Mandatory | Universal Co-ordinated Time (UTC) in the format HHMM. Required if the 'Receipt or Unpack Indicator' is U (Unpack). |
Responsible Party Client Id | Mandatory | The Australian Business Number (ABN) or Customs Client Identifier (CCID) belonging to the establishment responsible for communicating the outturn information to the Department. |
Flight Number | Mandatory | No stripping of characters undertaken. |
Airline Code | Mandatory | |
Outturn Establishment Id | Mandatory | Customs unique Establishment identifier. |
Estimated Date of Arrival | Mandatory | The local date in the format CCYYMMDD. Must match the Estimated Date of Arrival from the AIRIAR. |
V2.5 11 AUG 2005