| Title: | ACE CERTIFICATION deployment,Saturday Feb 27,2016 @1300ET,impact ACE CargoRel & EntrySumm |
|---|---|
| Date: | 2016-02-26 |
| To: | abi,newace,partner |
| Links: | previous, original, next |
Please be advised that there will be an ACE CERTIFICATION deployment on Saturday, February 27, 2016, starting at 1300 ET.
The deployment is expected to take approximately 30 minutes, and will impact ACE Cargo Release and ACE Entry Summary processing.
To be deployed:
• PGAD-9736 BUG- PO messaging incorrect format.
(1) PE sent out not a PO; PE and PO records mixed
(2) Envelope number was erroneously sent out in the SO71 (71 should only be used to send the PNC# as we do on the SO71)
(3) PO70 had PG line number as ‘2’ instead of 002 (not in the right format per the posted CATAIR)
• PGAD-9734 BUG – Fixes to PGA Message Set Validations for APHIS CORE Hold Intact rules and other APHIS CORE Bucket 2 Rules, not fully functional for various reasons across rules:
(1) Some validations resulted in May Proceeds instead of Hold Intact events.
(2) Detail IDs did not match ones on list.
(3) Some PGA Review events not displayed in PGA UI (PGA Review tab). The Hold Intact events are only shown in the PGA Data and in the SO.
(4) Detail Description & PGA Line Status_Reason and Sub_Reason codes did not match ones on list
• PGAD-9729 BUG - PG30 Date/time missing should have caused a reject for FDA FOO and did not
Without a date and time in the PG30, the data did not get sent to FDA and the 5-day window could not be determined. As a result, the entry remained in a PENDING state and FDA could not see the entry.
• PGAD-9393 BUG - NHTSA Business rule validation errors returning false or no results:
1. A PROD Entry had a valid Glazing Manufacturer Code (GMC) that should not have triggered a business rule hit for glazing. Error PF7 was incorrectly generated.
2. A PROD Entry should have rejected a Registered Importer # that had been incorrect & not in NHTSA's reference table.
3. A PROD Entry that was a HS-7 Box 3 Canadian certified filing, where both the registered importer# and VSA# were valid, should NOT have received NHT_1_011 BR hits.
4. A PROD Entry with no PG22 record should have been rejected with an error code P48.
5. A PROD Entry had a PG22 record with Doc ID 946, but no box checked, meaning, no conformance declaration. This should have received a PL0 [MISSING OR INVALID CONF DEC CODE PER PGA] reject.
6. A PROD Entry has Box 2A filled with program code OEI. Trade correctly got a Bucket 1 PG0 [INVALID GOV AGENCY PROGRAM CODE PER PGA] warning, but no BR rule hit was sent out for rule NHT_1_004a1.