| Title: | Implementation of 10+2 (ISF and CUSRES) Programming |
|---|---|
| Date: | 2010-02-07 |
| To: | abi,ocean |
| Links: | previous, next |
On January 13, 2010, CSMS #10-000013 was issued to delay the implementation of the CUSRES response to the BAPLIE stow plan submissions. Since that date, CBP has received feedback from a number of trade participants who are affected by the CUSRES response transactions. This message will address those issues and others that are to be implemented on February 14, 2010.
1. Based on feedback from trade participants, CBP will allow the trade ten days to test their programming in the AMS Certification system. The CUSRES will be sent as a response to the BAPLIE in Certification beginning February 14, 2010. Additionally, CBP will send back Unmanifested Container messages (CAMIR RC or X-12 350) in Certification. Due to the lack of matching bills related to BAPLIEs in Certification, every Unmanifested Container message sent in Certification will read as 'ALL LOADS MANIFESTED'.
2. On February 24, 2010, the CUSRES will be sent as a BAPLIE response in the Production environment also. Please, be sure your programming is ready at this time.
3. On February 14, 2010, the Unmanifested Container messages will include the proper translation of the next port of call submitted in the input BAPLIE to the schedule D code. They will also include the proper mode of transportation.
4. New bond-related edits, which enforce business rules, will be added to the ISF programming and will be warnings for a no less than two weeks. After that time, these warnings will be changed to rejections without further notice. The bond-related data edits for which warnings have been sent regularly prior to February 14, 2010 will now be changed to rejections on that date.
5. Importer Security Filing (ISF) transactions filed by different filers, which have been rejected in the past for Duplicate ISF Transaction, will now be accepted by CBP. In the case where a second identical ISF transaction is submitted by the same filer as the original ISF, that filer will still receive a reject for Duplicate ISF Transaction along with the ISF transaction number associated with the original filing. If, after February 14, 2010, a filer receives a duplicate ISF transaction WITHOUT an ISF transaction number, please contact your assigned Client Representative for assistance.
6. Beginning February 14, 2010, ISF transactions will allow the Shipment Type code '10' to represent Outer Continental Shelf Shipments (OCS). Documentation will reflect these changes in the next few days. For further explanations related to OCS shipments, please read the FAQs at:
http://www.cbp.gov/linkhandler/cgov/trade/cargo_security/carriers/security_filing/10_2faq.ctt/10_2faq.doc#CODED
If you have any questions, please contact your assigned Client Representative or call 571-468-5500 for information.