PG SPEC / PGA / Program PGA Error Dictionary for Trade ...

1 Error CodeError TextPG Record(s) data ElementSPEC / PGA / PNPEPGA CodeProgram CodeDescriptionP00 PGA data MISSING PER PGA FLAGN/APGA data FLAGSPECThe tariff provided is flagged for a PGA, the entry is one that would require reorting of PGA data , and none is provided. This will be a reject for the PGA's that are mandatory February 28, 2016 when sent with ACE Cargo Release. Those PGAs are FDA, APHIS Lacey, and DOT NHTSA. P01 MISSING PARENT OI RECORDOIPARENT OI RECORDSpecA PG01 record must be preceded by an initial OI record for the beginning of the PGA line OI PGA LINE ITEM DESCRIPTIONOICOMMERCIAL DESCRIPTIONSpecThere is no desctiprion in the OI recordP03 MISSING PG01 RECORD01PG01 SpecA PG01 record is mandatory for any PGA message set, including PGA LINE NUMBER01 PGA LINE NUMBERSpecThere is no PGA line number sent in the PG01 record. P05 MISSING GOVERNMENT AGENCY CODE01 GOVERNMENT AGENCY CODESpecPGA data requies the correct PGA code for the filing.

2 P06 MISSING OR INVALID GOVT AGENCY PROG CODE01 GOVERNMENT AGENCY Program CODESpecProgram 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 ITEM TYPE02 ITEM TYPESpecThe 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)P08 MISSING INTENDED USE DESCRIPTION01 INTENDED USE DESCRIPTIONSpecIf Intended Use Code "For Other Use" code is used, an Intended Use Description is required. P09 MISSING ENTITY NAME PER PGA19 ENTITY NAME PGAP10 MISSING SOURCE TYPE CODE06 SOURCE TYPE CODESPECA transaction is submitted with a missing Source Type CodeP11 INVALID SOURCE TYPE CODE06 SOURCE TYPE CODESpecFor APHIS Lacey Act filng, must - HRV (Harvest). For others, see Appendix PGA Source Type Codes for values. P12 MISSING ENTITY ROLE CODE19, 22 ENTITY ROLE CODESpecA PG 19 or PG22 record (Entity group) was submitted without an Entityt Role CodeP13 INVALID ENTITY ROLE CODE19, 22 ENTITY ROLE CODESpecEntity Role Code submitted must be in Appendix PGA.

3 Aloso, JP5P14 MISSING AFFIRMATION OF COMPLIANCE CODE23 AFFIRMATION OF COMPLIANCE CODESpecA PG23 record was sent that didn't include an affirmation of compliance AFFIRMATION OF COMPLIANCE CODE23 AFFIRMATION OF COMPLIANCE CODESPECA transaction is submitted with an Affirmation of Compliance Code that is not on fileP16 MISSING PACKAGING QUALIFIER26 PACKAGING QUALIFIERSPECA PG26 record is submitted with a missing Packaging Qualifier data elementP17 INVALID PACKAGING QUALIFIER CODE26 PACKAGING QUALIFIERSPEC7/23/2015 A PG26 is submitted with a Packaging Qualifier value that is not 1, 2, 3, 4, 5, or 6. If only one PG26 record is provided, value of the Packaging Qualifier must be 1. If there are multiple PG26 records, then the first PG26 must have a 1, the second one must have 2 and so on. On 12/22/14 - the first part of this code was done and tested. P18 MISSING CONTAINER NUMBER27 CONTAINER NUMBER (EQUIPMENT ID)SPECA transaction is submitted with a missing Container Number (Equipment ID)P19 MISSING INSP/LAB TESTING STATUS CODE30 INSPECTION/LABORATORY TESTING STATUS SPECA transaction is submitted with a missing Inspection/Laboratory Testing Status codeP20 INVALID INSP/LAB TESTING STATUS CODE30 INSPECTION/LABORATORY TESTING STATUS SPECA transaction is submitted with an Inspection/Laboratory Testing Status code that is not on file (see description associated with PG30 record)

4 P21 MISSING CMDTY HARV VESSEL CHAR TYPE CODE31 COMMODITY HARVESTING VESSEL CHARACTERISTIC TYPE CODESPECA transaction is submitted with a missing Commodity Harvesting Vessel Characteristic Type CodeP22 INVALID CMDTY HARV VESSEL CHAR TYPE CODE31 COMMODITY HARVESTING VESSEL CHARACTERISTIC TYPE CODESPECA transaction is submitted with a Commodity Harvesting Vessel Characteristic Type Code that is not on file (see Apx PGA)P23 MISSING CMDTY ROUTING TYPE CODE32 COMMODITY ROUTING TYPE CODESPECA transaction is submitted with a missing Commodity Routing Type CodeP24 INVALID CMDTY ROUTING TYPE CODE32 COMMODITY ROUTING TYPE CODESPECA transaction is submitted with a Commodity Routing Type Code that is not on file (see Apx PGA)P25 MISSING TRAVEL DOCUMENT TYPE CODE34 TRAVEL DOCUMENT TYPE CODESPECA transaction is submitted with a missing Travel Document Type CodeP26 INVALID TRAVEL DOCUMENT TYPE CODE34 TRAVEL DOCUMENT TYPE CODESPECA transaction is submitted with a Travel Document Type Code that is not numbers 1, 2, 3 or 4 PGA Error Dictionaryfor TradeVersion 1 January 28, 2016P27 MISSING PROCESSING DESCRIP WITH 01706 PROCESSING DESCRIPTIONSPECA transaction is submitted with a missing Processing Description data element, if Processing Type Code 017 (Other) is usedP28 MISSING PARENT PG07 RECORD07, 08 PARENT PG07 RECORDSPECA transaction is submitted with a missing PG07 record, if a PG08 is submittedP29 EXPECTED ASSOCIATED RECORD MISSING13, 14 EXPECTED ASSOCIATED RECORD MISSINGSPECA transaction is submitted with a missing PG14 if a PG13 is used.

5 The PG13 may be followed by a PG50 (grouping) whose group includes several PG14s which will satisfy this rule. Otherwise, the PG13 should immediately precede the PG14. Coded not tested. Anything other than a PG01 or PG02 appearing after a PG01 will P30 MISSING CMDTY POL SUBUNIT ROUTING NUMBER32 COMMODITY POLITICAL SUBUNIT OF ROUTING NUMBERSPECA transaction is submitted with no Commodity Political Subunit of Routing Number, but with a Commodity Political Subunit of Routing Qualifier. As of 10/20/2014 - changed to check for the 'number' vs the 'name' and changed the Error message to 'number' vs 'name', per test review. This rule was incorrectly created OR INVALID OCEANGEO AREA33 GEOGRAPHIC AREA CODESPECA transaction is submitted with a PG33 record that contains no data (beyond the control identifier and record type). One of the two data elements must be provided (doesn't matter which one - Commodity Geographic Area Code or Commodity Geographic Area Name)P32 RECORDS NOT ALLOWED IN GROUPLISTRECORDS NOT ALLOWED IN GROUPSPECA transaction is submitted with records within a group that are not allowed.

6 The following records are currently allowed to appear in a group: 5, 6, 7, 10, 14, 19, 22, 25, 26, 29 and 31P33 MISSING PARENT PG19 RECORD19, 20 PARENT PG19 RECORDSPECA transaction is submitted with a missing PG19 if a PG20 is submitted. A PG20 can't exist on its own. If a PG20 exists it should have a parent of PG19. P34 MISSING PARENT RECORD FOR PG2121 PARENT RECORD FOR PG21 SPECA transaction is submitted with a missing PG19, PG22 or PG30 if a PG21 is submitted. A PG21 can't exist on its own. If a PG21 exists, it should have a parent of PG19, 20, 22 or OR INVLD ITEM ID NUM QUAL PER PGA07 ITEM IDENTITY NUMBER QUALIFIERPGAP36 MSNG OR INVLD DECLARATION CODE PER PGA22 DECLARATION CODEPGAP37 MISSING PG24 RECORD PER PGA24PG24 RECORD PGAP38 MSNG/INVLD RMK TYP CODE IN PG24 PER PGA24 REMARK TYPE CODEPGAP39 MISSING CMDTY HARV VESSEL CHARACTERISTIC31 COMMODITY HARVESTING VESSEL CHARACTERISTICSPECA transaction is submitted with a missing Commodity Harvesting Vessel Characteristic P40 INVALID PARTICIPANTN/APARTICIPANTSpecFiler is not active for the combination of filer code, entry port, PGA, and PGA Program code.

7 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. P41 MISSING REMARKS CODE OR TEXT24 REMARKS CODESPECIf a Remarks Type Code is reported, either a Remarks Code or Remarks Text is requiredP42 MORE THAN ONE OI UNDER SINGLE HTSOIMORE THAN ONE OI UNDER SINGLE HTSSPECA 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 - Per Shailesh, for an AE, on one Entry line, if there is an OI with OGA data and an P43 MISSING PG06 PER PGA06PG06 PGAP44 MISSING PG13 PER PGA13PG13 PGAP45 MISSING PG14 PER PGA14PG14 PGAP46 MISSING PG19 PER PGA19PG19 PGAP47 MISSING PG21 PER PGA21PG21 PGAP48 MISSING PG22 PER PGA22PG22 PGAP49 MISSING PG30 PER PGA30PG30 PGAP50 MISSING PG10 PER PGA10PG10 PGAP51 MISSING PG25 PER PGA25PG25 PGAP52 MISSING PG26 PER PGA26PG26 PGAP53 MISSING PG29 PER PGA29PG29 PGAP54 MISSING PG02 RECORD02PG02 RECORDSPECA transaction is submitted with no PG02 record and there is no disclaimerP55 INVALID PROCESSING CODE01 GOVERNMENT AGENCY PROCESSING CODESPECA transaction is submitted with a Government Agency Processing code that is not on file.

8 The valid codes are in Appendix PGA. As of 12/29/2014,there are now Government Agency Processing Codes. (May consider changing this to say 'missing or invalid govt agency processing ) P56 INVALID ELEC IMAGE CODE01 ELECTRONIC IMAGE SUBMITTEDSPECA 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 CONFIDENTIAL INDICATOR01 CONFIDENTIAL INFORMATION INDICATORSPECA transaction is submitted with a confidential information indicator code that is not a Y. Y is the only code accepted. Code can be Y or field can be left PIC QUALIFIER CODE01 GLOBALLY UNIQUE PRODUCT IDENTIFICATION CODE QUALIFIERSPECA transaction is submitted with a Globally Unique Product Identification Code Qualifier that is not on file. The valid codes are in Appendix INTENDED USE CODE01 INTENDED USE CODESPECA transaction is submitted with an intended use code that is not on file. Valid codes are in 'Appendix R Intended Use Codes for ACE'.

9 Applies for any submission for any agency, if an intended use code is provided. If the code is not found in Appendix R, it should be DISCLAIMER CODE01 DISCLAIMERSPECA transaction is submitted with a disclaimer code that is not a Y. Y is the only code PRODUCT CODE QUALIFIER02 PRODUCT CODE QUALIFIERSPECA transaction is submitted with a product code qualilfier that is not on file. The valid codes are in Appendix ACTIVE INGREDIENT QUALIFIER04 CONSTITUENT ACTIVE INGREDIENT QUALIFIERSPECA PG04 is submitted with a Constituent Active ingredient qualifier that is not a CONSTITUENT ELEMENT NAME04 NAME OF THE CONSTITUENT ELEMENTSPECA transaction is submitted with a Name of the Constituent Element that is not on APH (Govt Agency Code) + APV (Govt Agency Program Code), the valid codes are in Appendix PGA, Animal Group , for all other Govt Agency Codes, anything is accepted (within our syntax P64 INVALID QUANT CONST ELM FRMT OR NOT > 004 QUANTITY OF CONSTITUENT ELEMENTSPECA transaction is submitted with an invalid Quantity of Constituent Element format or value.)

10 (numeric and greater than zero)P65 INVALID UOM CONSTITUENT ELEMENT04 UNIT OF MEASURE CONSTITUENT ELEMENTSPECA transaction is submitted with a Unit of Measure (Constituent Element) that is not on APH (Govt Agency Code) + APL (Gov't Agency Program Code), the valid codes are in Appendix PGAP66 INVALID PERCENT FORMAT OR NOT > 004 PERCENT OF CONSTITUENT ELEMENTSPECA transaction is submitted with an invalid Percent of Constituent Element format or value. P67 INVALID SCIENTIFIC SPECIES CODE05 SCIENTIFIC SPECIES CODESPECA transaction is submitted with a Scientific Species Code that is not on FWS (Govt Agency Code) valid codes are in Appendix PGA (FWS Wildlife Category Codes). Otherwise, for all other Govt Agency Codes, enforce the AN DESCRIPTION CODE05 FWS DESCRIPTION CODESPECA transaction is submitted with a FWS Description Code that is not on FWS (Govt Agency Code) valid codes are in Appendix PGA (FWS Description Codes).Otherwise, for all other Govt Agency Codes, enforce the AN COUNTRY CODE06, 20, 32 COUNTRY CODESPECA transaction is submitted with a Country code that is not on file.