Loading

Sea Actual Arrival Report (SEAAAR) Business Rules

​​​ Message Mapping

User Data Dictionary

SEAAAR - General Rules

  1. The valid Message Function Codes for an SEAAAR are:
    1. Original (9)
    2. Change (4)
    3. Withdraw (50)
  2. SEAAAR messages must quote a unique Sender Reference. The ICS will use this number and the associated Sender Reference Version to ensure duplicate messages are not processed.
  3. The version number for an Original (9) message must be set at 1 or greater.
  4. Before the SEAAAR message is processed at the application level:
    1. All leading and trailing blanks will be stripped;
    2. Multiple spaces will be compressed;
    3. Illegal characters will be removed; and
    4. All nulls will be converted to blanks.
  5. Any errors in an SEAAAR message will be reported in an SEAAAR Response message (SEAAARR).
  6. Any advice messages resulting from the SEAAAR message will be reported in an SEAAAR Response message (SEAAARR).
  7. The maximum number of errors or advices that can be reported is 50. No further errors will be processed once the maximum number allowed for the SEAAARR has been reached.
  8. A Change to an SEAAAR will be rejected if there is no difference between the Original and the Change SEAAAR.
  9. Each Change AIRAAR 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.
  10. Change or Withdraw SEAAAR messages for which no original exists will be rejected by the ICS.
  11. The Withdrawal of an SEAAAR is for the entire record.
  12. Once an Actual Arrival Report has been created, amended or withdrawn online through the ICS Interactive Facility, future processing via EDI will not be permitted.

SEAAAR - Processing Rules

  1. A SEAAAR allows Shipping Companies to report to the Department the Actual Arrival Details of a Vessel at an Australian Sea Port.
  2. The SEAAAR must be lodged within a specified time of the vessels arrival. See ​Import Cargo Reporting Timeframes for more detail.
  3. The Principal Agent or Operator who lodged the Impending Arrival Report will be deemed the responsible party for lodging the Actual Arrival Report.
  4. A SEAAAR is linked to a SEAIAR by the:
    1. Vessel Identifier;
    2. Voyage Number;
    3. Port of Arrival.
  5. If a SEAAAR cannot be linked to an SEAIAR an Advice is sent in an AIRAARR Response message.
  6. The Report Identifier for an SEAAAR is a concatenation of the:
    1. Vessel Identifier;
    2. Voyage Number;
    3. Port of Arrival;
    4. Stevedore ID.
  7. The unique identifiers within an AIRAAR cannot be amended. The existing AIRAAR must be withdrawn and a new AIRAAR submitted with the new identifiers supplied.
  8. At a minimum, the following attributes are required to withdraw a SEAAAR:
    1. Document Name;
    2. Sender Reference;
    3. Sender Reference Version;
    4. Owner Site Id;
    5. Message Function Code;
    6. Vessel Identifier;
    7. Voyage Number;
    8. CTO Establishment Id.
  9. For all amendments to a SEAAAR, the full report with all attributes is required.
  10. If the withdrawal of an SEAAAR is successful, an Advice is sent to the SEAAAR reporter in an SEAAARR message confirming the successful withdrawal.
  11. The Responsible Party Client ID is mandatory for an Original AIRAAR. 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).
  12. The Responsible Party Client ID cannot be Changed. The AIRIAR must be withdrawn and a new AIRIAR submitted.

Data Dependency Tables

A Sea Actual Arrival Report Message can be Created, Changed or Withdrawn. The mechanism for carrying out these transactions utilises Message Function Code. The Message Function Code is a document level transaction indicator that is applied to the document.

Message Function CodeAction
ORIGINAL (9)A new Sea Actual Arrival Report with a unique sender's reference.
CHANGE (4)A full Sea Actual Arrival Report containing changes to attributes excluding attributes contained within the unique business identifier.
WITHDRAW (50)A withdrawal of an existing Sea Actual Arrival Report.

Data Dependency Table for Original and Change

The following table models the data elements of the Sea Actual Arrival Report Document where the document is considered an "Original" or a "Change".

Data ElementICS Business RequirementICS Business Rule
Document NameMandatoryCode is SEAAAR
Sender Reference Mandatory
Sender Reference Version Mandatory
Message Function CodeMandatorySee Message Function Code table above.
Responsible Party Client IdMandatoryThe Australian Business Number (ABN) or Customs Client Identifier (CCID) belonging to the operator of the vessel.
Port of ArrivalMandatoryMust be a valid UNLOCODE. Must be an Australian port.
Berth CodeMandatoryThe related port must match that of the CTO Establishment Id.
Actual Date of ArrivalMandatoryUniversal Co-ordinated Time (UTC) in the format CCYYMMD.
Actual Time of ArrivalMandatoryUniversal Co-ordinated Time (UTC) in the format HHMM.
CTO Establishment IDMandatory

Must be a valid s.15 Wharf.

Must relate to the Stevedore Id.

The related port must match that of the Berth Code.

Stevedore IdMandatory

The Australian Business Number (ABN) or Customs Client Identifier (CCID) belonging to the Stevedore where the vessel has arrived.

Must relate to the CTO Establishment Id.

Voyage NumberMandatoryThe Voyage Number must be the Principal Agent's Voyage Number.
Vessel IdMandatory

Data Dependency Table for Withdrawal

The following table models the data elements of the Sea Actual Arrival Report Document where the document is considered a "Withdraw".

Data ElementICS Business RequirementICS Business Rule
Document NameMandatoryCode is SEAAAR
Sender Reference Mandatory
Sender Reference Version Mandatory
Message Function CodeMandatorySee Message Function Code table above.
CTO Establishment IDMandatory
Voyage NumberMandatoryThe Voyage Number must be the Principal Agent's Voyage Number.
Vessel Identifier Mandatory

NOTE: for further details in relation to a Business Term, refer to the User Data Dictionary.

V2.2 21 OCT 2004