General rules in ACI Message flow
- Bärbel Neitzel
Contents
Send message as ORIGINAL or UPDATE
The programme itself decides whether an update or an original must be sent when the 'Send' function is activated.
If the CA ACI OK is filled with Y or T, an update is sent, otherwise an original is sent.
Send eHBL update
B2B: If the HBL is changed for a B2B (update sent), the close does not need to be changed - cancellation and/or update of the close message is not required.
Consol Container: If a close message already exists for a consolidation container, certain values, such as the warehouse code of all HBLs, must be IDENTICAL.
If a HBL update is sent with a new warehouse code, this will result in an error, as this new code differs from the warehouse codes in the other HBLs.
The close message must be cancelled beforehand!
Afterwards, the updates can be sent.
Then a new close message must be sent.
If the customer changes a value in the HBL that does not have to be identical in all HBLs (e.g. Consignee), an update can be sent and the close message can be left untouched.
Send CLOSE update
In general, no updates may be sent for a CLOSE message.
This applies to ACCEPTED Close messages: They must be cancelled and then resent.
In the event of an error (reject), it is sent again (as ORIGINAL).
In case of a conformance error (PARTIAL ACCEPT), it is resent as CHANGE (i.e. update).
Data error/REJECTED status message
If CA ACI OK = N is set - send again as ORIGINAL.
A N (=error) is displayed with a red icon inTMS:
Conformance error/PARTIALLY ACCEPTED status message
If CA ACI OK = T is set - send again as CHANGE.
The interface checks the CBSA OK field (no longer whether the send date is filled or not) and sends CHANGE or ORIGINAL accordingly.
A T is displayed with an orange icon in TMS:
ACCEPTED status message
Wenn CA ACI OK = J darf für die Close-Nachricht kein UPDATE gesendet werden.
Es erscheint eine Meldung im TMS!
*the Change msg can only be submitted on RJ (Rejected) status not on ST or AC.
 Mögliche Fehlermeldung: FAIL ack Message with the info: "For CCN :8000BREEX21090235 and with PCCN :
020-00000136, Record is in ST status, Please wait for CBSA response."Â
Send amendment
Amendments are changes which are only sent after vessel arrival in Canada.
There is no arrival check in the TMS. Users themselves decide whether an amendment should be sent.
The following applies to the CLOSING Amendment message: No update may be sent. If a CLOSING Amendment is ACCEPTED, a change is no longer possible.
Cancel HBL
The CLOSE message must be cancelled first.
Send again after cancellation
HBLs and close messages can be cancelled.
If HBLs and close messages are to be sent again afterwards, this is possible.
The files must be sent with the ORIGINAL identifier (not as CHANGE).
The cancellation OK responses from ACI are read in such a way that the CA ACI OK tick in Send (left-hand column) is cleared in addition to the cancellation OK.
If the field is empty, the next transmission of the HAWB/HBL will be sent as ORIGINAL.
Error messages
461 (Close) | I believe the Change msg that you submitted prior to the last Origin submission, was rejected since the new HBL you added was not accepted in CBSA system in the time of close msg submission. |
|---|---|
463 (HBL) | The HBL was sent again by mistake, although there is still no response. Solution: The HBL must be cancelled. After cancellation OK, simply resend. |
W54 (HBL cancelled) | CANCEL HBL: The close message must be cancelled first. |
W72 (Close) | The forwarder code 8000 must be sent in the message. Not the airline code! |
W91 (Close) | The error W91 is indicating that the Previous CCN# is already exist in CBSA database and it cannot be transmitted as new/origin. That means the close msg needs to be sent as Change. Solution:Â Set eaaci_close_t.caaci_ok = T |
Y55 (Close) | Close contains a HAWB/HBL that was previously sent in/with another Close.v Solution: The Close message of the previous Consol/SaCo must be cancelled first. |
UMRN(20211019224477)SEGMENTBGMLINE1ELEM1225(3.0)INVALID CODEÂ (eHBL Amendment) | It may be technically incorrect to send an amendment here. Â |
Sent, but no entry on the EDI status tab?
It can (rarely) happen that the SFTP server fails and therefore the transfer of the file does not work.
The SFTP transmission OK or ERROR is written to the EDI log - this is executed with Provider SFTP.
On the ACI tab only the status of the provider ACi are visible.
Solution
Move the generated file from the error directory to the output directory so that it will be transferred.
Â