| Title: | ACE Entry Summary Certified for ACE Cargo Release Corrections |
|---|---|
| Date: | 2015-08-29 |
| To: | abi |
| Links: | previous, original, next |
Corrections made to an ACE Entry Summary Certified for ACE Cargo Release will NOW be processed and accepted as noted below. Prior to this change, a correction to an ACE Entry Summary Certified for ACE Cargo Release returned the two reject messages below.
ENTRY NUMBER ALREADY FILED IN ACE SE
SE DATA REJECTED
These reject messages generated due to ACE Cargo Release (App Id = SE) always processing an ADD transaction when entries were already on-file. The ACE Entry Summary (App Id = AE) processed the transaction correctly, in its entirety. The ACE Cargo Release (App Id = SE) process has been corrected and the transaction will NOW be fully processed as noted below.
Scenario 1 – ACE Cargo Release (SE Data) ON FILE
Upon receipt of an ACE Entry Summary Certified for ACE Cargo Release correction: if an ACE Cargo Release (SE data) is on-file, the SE data will process as a REPLACE transaction.
Scenario 2 – ACE Cargo Release NOT ON FILE
Upon receipt of the an ACE Entry Summary Certified for ACE Cargo Release correction: if an ACE Cargo Release (SE Data) is NOT on file, the SE data will process as an ADD transaction.
Please Note:
•Normal Cargo Release processing rules apply in either scenario. ACE Cargo Release (SE) rejections may still occur but not for “ENTRY NUMBER ALREADY FILED IN ACE SE”. Any rejection would arise from the same rules if it were a stand-alone Cargo Release Correction submitted as a “REPLACE” or “ADD” transaction.
•ACE Entry Summary (AE) processing will also follow normal processing rules for rejections.
•This correction impacts all ACE Entry Summary (AE) transactions Certified from Summary for ACE Cargo Release, whether or not the intent is to correct the ACE Cargo Release (SE data).
•CATAIR updates will made and communicated to Trade.