Beruflich Dokumente
Kultur Dokumente
PR1 HTS NOT SUBJ TO MIN WGHT EXEMPT PER PGA N/A
PV6 MANDATORY GROUP RECORD MISSING PER PGA 10, 26, 50,
51
PX5 06
SOURCE TYP CD MISMATCH W/ PG19 ENTITY CD
PARTICIPANT Spec
PG06 PGA
PG13 PGA
PG14 PGA
PG19 PGA
PG21 PGA
PG22 PGA
PG30 PGA
PG10 PGA
PG25 PGA
PG26 PGA
PG29 PGA
DISCLAIMER SPEC
QUANTITY SPEC
PG07 PGA
MODEL PGA
PG35 PGA
PG34 PGA
PG05 PGA
PG20 PGA
DISCLAIMER SPEC
PG04 PGA
NAME OF THE CONSTITUENT ELEMENT PGA
QUANTITY PGA
PGA
PGA
PGA
PGA
PGA
PGA
PGA
PGA
PG17 PGA
PG32 PGA
PN DATA PGA
PN DATA PGA
GROUPING SPEC
A PG01 record must be preceded by an initial OI record for the beginning of the PGA
line data.
There is no desctiprion in the OI record
A PG01 record is mandatory for any PGA message set, including disclaims.
There is no PGA line number sent in the PG01 record.
PGA data requies the correct PGA code for the filing.
Program code in the PG01 must be valid for the PGA. Verify program code with the
PGA supplemental guide and Appendix PGA. If program code is correct, contact CBP
client rep or PGA contact.
The Item Type is = P (Product) for the initial use of Item Type on a PGA line.
Subsequent item types on the same PGA line must = C (Component)
If Intended Use Code 980.000 "For Other Use" code is used, an Intended Use
Description is required.
For APHIS Lacey Act filng, must - HRV (Harvest). For others, see Appendix PGA Source
Type Codes for values.
A PG 19 or PG22 record (Entity group) was submitted without an Entityt Role Code
Entity Role Code submitted must be in Appendix PGA. Aloso, JP5
A PG23 record was sent that didn't include an affirmation of compliance code.
A transaction is submitted with a Commodity Routing Type Code that is not on file
(see Apx PGA)
A transaction is submitted with a Travel Document Type Code that is not numbers 1,
2, 3 or 4
Filer is not active for the combination of filer code, entry port, PGA, and PGA program
code. Verify that all sent are valid. If so, email client rep to set up proflie for
participation for the PGA. On an SE, entry and unlading ports are mandatory for PGA.
If sent as blank, this error can result.
If a Remarks Type Code is reported, either a Remarks Code or Remarks Text is required
A transaction is submitted with more than one OI under one HTS code. In CERT, trade
submitted a file w/ multiple OI and it caused a d/b error such that the XML sent to
FSIS was all screwed up.
6/3/14 - Per Shailesh, for an AE, on one Entry line, if there is an OI with OGA data and
an OI with PGA data, this is acceptable. We would only pass through the OGA data to
ACE. For an SE, no OGA data is accepted at this time.
A transaction is submitted with no PG02 record and there is no disclaimer
A transaction is submitted with an eletronic image code that is not a Y. Y is the only
code accepted. Code can be Y or field can be left blank.
If it passes P59, then if it is EPA-ODS, separately we must check the intended use code
against the ref file that EPA has provided which lists acceptable EPA-ODS intended use
codes.
A If it does
transaction not find a match
is submitted with a in that list, code
disclaimer we notify EPA
that is not a Y. Y is the only code
accepted.
A transaction is submitted with a product code qualilfier that is not on file. The valid
codes are in Appendix PGA.
A transaction is submitted with an invalid date format (for Manufacture Month and
Year). Valid format is:
1) MMCCYY or
2) CCYY with zero fill
A transaction is submitted with a Processing Type Code that is not on file. Valid codes
are in Appendix PGA (Processing Type Codes).
A transaction is submitted with a Category Type Code that is not on file. Valid codes
are in Appendix PGA.
A transaction is submitted with a Category Code that is not on file. Valid codes are in
Appendix PGA.
A transaction is submitted with a Commodity Characteristic Qualifier that is not on
file. Valid codes are in Appendix PGA.
A transaction is submitted with an LPCO Issuer Code Qualifier that is not on file. Valid
codes are listed in the PGA Message Set Spec, in the description for this data element
in PG13. This is for positions 40-42.
A transaction is submitted with a Location of Issuer of LPCO code that is not on file.
Valid codes are in Appedix B of ACS ABI CATAIR. This is for positions 40-42
A transaction is submitted with an invalid LPCO Transaction Type. Valid codes are 1, 2,
3.
A transaction is submitted with an LPCO Type code that is not on file. Valid codes are
in Appendix PGA.
A transaction is submitted with an invalid LPCO Date Qualifier. Valid codes are 1, 2, 3,
4
A transaction is submitted with an invalid LPCO Quantity format or not greater than
zero. 9/2 code to be added that checks for greater than zero. Four decimal places are
implied.
A transaction is submitted with an LPCO Unit of Measure that is not on file. Valid
codes are in Appendix C in the ACS ABI CATAIR
A transaction is submitted with an Exemption Code that is not on file. Valid codes are
in Appendix PGA
A transaction is submitted with a Live Venomous Wildlife code. Valid Codes are Y or N
or the field can be left blank.
A transaction is submitted with an invalid data class format for UN Dangerous Goods
Code. Enforce the AN class format.
A transaction is submitted with an invalid data class format for EPA Hazardous Waste
Code. Enforce the AN class format.
A transaction is submitted with an invalid Packaging Group Code. Valid codes are 1, 2,
3
A transaction is submitted with an Entity Identification Code that is not on file. Valid
codes are in Appendix PGA
A transaction is submitted with an Entity State/Province that is not on file. Valid codes
are in Appendix B in the ACS ABI CATAIR. 1/26/2015 - updated the error message to
reflect 'missing'.
A transaction is submitted with an Individual Qualifier code that is not on file. Valid
codes are in Appendix PGA (Entity Role Codes)
A transaction is submitted with an invalid class format for Telephone Number of the
Individual. Enforce the Alpha Numeric class. on 10/15/2014 - Change the data
element format from N to AN.
A transaction is submitted with a Document Identifier Code that is not on file. Valid
codes are in Appendix PGA (Document Identifer).
A transaction is submitted with a Declaration Code that is not on file. Valid codes are
in Appendix PGA (Declaration Code).
A transaction is submitted with a Remarks Type Code that is not on file. Valid codes
are in Appendix PGA (Remarks Type Code).
A transaction is submitted with a Remarks Code that is not on file. Valid codes are in
Appendix PGA (Remarks Code).
A transaction is submitted with a Temperature Qualifier that is not on file. Valid codes
are listed in the PGA Message Set Spec, in the description for this data element in
PG25.
A transaction is submitted with a Degree Type code that is not on file. Valid codes are
F, C, K
A transaction is submitted with a Negative Number qualifier that is not an X. X is the
only code accepted if the actual temperature is in the negative numbers.
A transaction is submitted with a Lot Number Qualifier that is not on file. Valid codes
are 1, 2, 3, 4
A transaction is submitted with an invalid Production Start date of the Lot format.
Valid format is MMDDCCYY
A transaction is submitted with an invalid Production End Date of the Lot format. Valid
format is MMDDCCYY
A transaction is submitted with an invalid PGA Line Value format. One of the
characters entered is not a number.
A transaction is submitted with an invalid PGA Unit Value format. One of the
characters entered is not a number. Two decimals are implied.
A transaction is submitted with an invalid Quantity format or not greater than zero.
Two decimals are implied.
A transaction is submitted with Unit of Measure (Packaging Level) that is not on file.
A transaction is submitted with a Type of Container that is not on file. Valid codes are
1, 2
A transaction is submitted with an invalid Container Length format or not greater than
zero
A transaction is submitted with a Package Tracking Number Code that is not on file.
Valid codes are UPS, FEX, DHL, ITN and SCAC. As of 12/17 the CATAIR SPEC was
updated to increase the length of this data element from 3AN to 4AN.
A transaction is submitted with a Unit of Measure (PGA Line-net) that is not on file.
For APH (Govt Agency Code) + APL (Gov't Agency Program Code), the valid codes are
in Appendix PGA. Valid Unit of Measure Codes are listed in Appendix C in the ACS ABI
CATAIR. Updated description to include Lacey specific UOM codes in Appendix PGA
A transaction is submitted with an invalid Commodity Net Quantity (PGA Line - net)
format or value is not greater than zero
A transaction is submitted with a Unit of Measure (PGA Line-gross) that is not on file.
For APH (Govt Agency Code) + APL (Gov't Agency Program Code), the valid codes are
in Appendix PGA. Valid Unit of Measure Codes are listed in Appendix C in the ACS ABI
CATAIR. 2/23/15: updated description to include Lacey specific UOM codes in
Appendix PGA; code needs to be updated to only allow specific UOM codes for lacey
and retested.
A transaction is submitted with an invalid Commodity Net Quantity (PGA Line - gross)
format or value is not greater than zero
A transaction is submitted with a Unit of Measure (Individual Unit-net) that is not on
file. For APH (Govt Agency Code) + APL (Gov't Agency Program Code), the valid codes
are in Appendix PGA. Valid Unit of Measure Codes are listed in Appendix C in the ACS
ABI CATAIR. 2/23/15: updated description to include Lacey specific UOM codes in
Appendix PGA; code needs to be updated to only allow specific UOM codes for lacey
and retested.
A transaction is submitted with an invalid Commodity Net Quantity (Individual Unit -
net) format or value is not greater than zero
A transaction is submitted with a Unit of Measure (Individual Unit-gross) that is not on
file. For APH (Govt Agency Code) + APL (Gov't Agency Program Code), the valid codes
are in Appendix PGA. Valid Unit of Measure Codes are listed in Appendix C in the ACS
ABI CATAIR. 2/23/15: updated description to include Lacey specific UOM codes in
Appendix PGA; code needs to be updated to only allow specific UOM codes for lacey
and retested.
A transaction is submitted with an invalid Commodity Net Quantity (Individual Unit -
gross) format or value is not greater than zero
A transaction is submitted with a Commodity Routing Country Code that is not on file.
Valid ISO codes are listed in Appendix B in the ACS ABI CATAIR.
A transaction is submitted with a PGA record that is not in the current spec
If Commodity Net Quantity (PGA line – net) is provided, Unit of Measure (PGA line –
net) must be present.
If Commodity Gross Quantity (PGA line – gross) is provided, Unit of Measure (PGA line
– gross) must be present.
If Unit of Measure (PGA line – gross) is provided, Commodity Gross Quantity (PGA line
– gross), must be present.
BIO mandatory codes MF, DEQ, FD1 and DP. AAR also allowed
BIO mandatory codes MF, DEQ, FD1 and DP. AAR also allowed
DRU mandatory codes MF, DEQ, FD1 and DP. Conditional: GD, SPO. Reference FDA SG
DRUG chapter for extensive additional entity role codes
FDA Stand-alone PN codes: PNS, PNT, and 1 of:MF, FDC, or DFI, Conditional: LG,
Following reqd except for T&E: FD1, DFP; Additional allowed: PK
FDA Entry with full PN: PNS, PNT, DEQ, FD1, UC and 1 of: MF, FDC, or DFI;
Conditional: LG, Additional allowed: PK
FDA Entry with PN Confirmation number or Food Contac:t MF, DEQ, FD1, DP
FDA DEV Mandatory: MF, DEQ, FD1, DP, DII; FDA SG DEV chapter, PG19 record page
for list of additional Entity Role Codes that may apply
FDA TOB mandatory: MF, DEQ, FD1, TB, DP Cond: ITL, LAB; Also applicable RD
FDA RAD mandatory: MF, DEQ, FD1, DP; See FDA SG RAD chapter, PG19 record page
for list of also applicable Entity Role Codes
FDA VME mandatory: MF, DEQ, FD1, DP; See FDA SG VME chapter, PG19 record page
for list of also applicable Entity Role Codes
A transaction is submitted with a disclaimer code in PG01 set to 'y', but the HTS flag
says data "must be provided".
A transaction is submitted with a DOT Bond amount that is not numeric
A transaction is submitted with a PG50 record but no PG51 record.
When the system encounters a PG50 record, it will then check that the records that
follow are allowed in a group. If it encounters records not allowed in a group, the
system will send the message (P32) - for each errant record - that the record is not
allowed in a group.
At the same time, the system will look for the PG51 record. If, in the same PGA block
where the PG50 record was found, the system encounters a PG02, a PG01 or a 62
record (in that order) before encountering a PG51 record, it will stop processing and
send this PN1 error.
This is to keep the search from continuing too long/unnecessarily, and sending too
may P32 messages
Consult specific Supplemental Guide for the PGA and Appendix PGA for valid
Packaging Units of Measure.
Valid Unit of Measure for Packaging level. Consult FDA SG for the specific program
code PG26 record for UOM table, Appendix F of that documents for Packaging Units
and Lowest Level packaging units.
PG01 requires a valid processing code. Consult the supplemental guide for the PGA
for the correct Processing Code.
FDA Lot Number and Lot Number qualifier mandatory for Infant formula, Acidified
Foods, and LACF products. Qualifier = 3 (Grower) if processing code is NSF, else
Qualifier = 1 (Manufactuer).
Consult the FDA SG chapter for the particular valid Lot Number Qualifier values. Sent
if Lot Number in PG26 is sent. It identifies who assigned the Lot number.
9/3/2015 Because these are going out as warnings and not rejects, we are softening
this message from "PGA DATA MUST BE PROVIDED FOR THIS HTS" to "PGA DATA
MISSING FOR HTS - NO ACTION REQ". After Feb 28th, For APHIS Lacey, FDA & NHTSA,
Trade will get a P00 reject and all other agencies will get the P00 warning.
When an Entry Summary, NOT Certified for Release, is submitted with PGA data,
reject the Entry
A PG60 can appear immediately after a PG19, PG20 or PG21. Else, it should be
rejected. NOTE: Multiple PG60s are allowed. So a PG60 can be followed by one or
more PG60s.
If a PG60 is provided, and the Additional Reference qualifier code is provided, that
qualifier code must be a valid qualifier code, per the PGA Message Set, note 1.
Do not send PGA data on the X line of an X-V set. PGA data is submitted on the V line.
The PG06 record must come after the PG02 and cannot come after the PG04.
If the Entity Country provided in the PG20 at 66-67 is equal to 'US' or 'CA' then the
Entity Zip/Postal Code must be provided at 68-76.
If a PE10 record is provided, the Filing type must be provided at position 6 and it must
be equal to A.
If an entry XML has already been generated and sent to FDA (i.e. within 5 day window
prior to arrival in the PG30) AND the PN status (801m) does NOT equal 04-
REJECTED, then any subsequent entry filings must be rejected.
If the product code number on the PG02 at 10-28 requires PN data AND there is NOT
a PG14 record with LPCO Type at 6-8 equal to 'PNC' AND there is at least one PG19
with entity role code of 'MF' at positions 5-7, THEN a PG06 with source type code at
5-7 equal to '262' is NOT allowed.
FDA. Source type code 06 (manufacturer) for Prior Notice shipments (no PNC # sent)
does not allow Entity Role Code of DFI (Grower) or FDC. PG06 source type code 262
(place of growth) does not allow Entity role code MF (Manufacturer
If the product code number on the PG02 at 10-28 requires PN data and a PG14 record
is NOT provided, THEN only ONE of the following Entity Role Codes is allowed to be
present on the PG19 at 5-7 per PGA line (i.e. PG01001, PG01002, PG01003, etc): MF,
FDC, or DFI.
The sum of the FDA line values (i.e. positions 57-68) for all PG25 records, across ALL
PG01 blocks, under each HTS code should be less than or equal to the CBP value
associated to the HTS Number. The CBP value associated to an HTS number is
provided at one of the following locations depending on transaction type: If AE then
check value at positions 25-34 on the AE50 and if SE then check value at positions 15-
24 on the SE60.
If entry is not filed at a PGA authorized port (as defined in the entry header) then the
entry is rejected.
If trade provides an inbond number: Check that it is alpha numeric and 9, 11, or 12
characters in length, else reject. (We will not check whether it is a valid inbond
number. So, no rejects sent on the PE, if the number is not yet on file)
If PGA data (other than FSIS or EPA) is present on AE for ACS then REJECT.
Carrier code is not a valid carrier. Verify that the SCAC, IATA, or ICAO code is correct
and on file with CBP.
The same line number was repeated within a PGA block under a single tariff number.
or Dictionary for Trade
1
28, 2016
The PGA Error dictionary is a work in progress. It is unique in that the same error messages can be gene
and program codes.
This is why the same error code appears several times in different rows of the chart. For example, there
PER PGA. The different rows to describe the error are broken down by the PGA code (FDA right now) an
that row describes the reason for that error in the context of the PGA and the program. As more error d
more useful in sorting error conditions. Right now, it is minimal with only a few of the FDA errors broken
The ultimate source of the PGA information is the PGA chapater of the ACE CATAIR and the Supplementa
The emphasis is on the initial mandatory PGA's for February 28, 2016 :FDA, APHIS Lacey, and DOT NHTSA
Please provide coments, quesitons, and suggestions via email to michael.cooney@dhs.gov. In the subjec
code, include that in the subject line as well.
the chart. For example, there are several entries for PJ5 MSNG OR INVLD ENTITY ROLE CODE
PGA code (FDA right now) and the several program codes in that column. The Description for
the program. As more error descriptions are compiled, the data filter by PGA code should be
few of the FDA errors broken out.
E CATAIR and the Supplemental Guides issued by the PGAs.
ooney@dhs.gov. In the subject line put "PGA DICTIONARY" and, if it is about a specifc error