FTZ Management: Preparation - Resolving Common Validation Messages in FIFO Processing

While researching the results of validation during Foreign Trade Zone daily processing this guide provides details on common FIFO transaction validations encountered, what they represent, and how to correct.

Validation Message	Standard Solution
FP010 - FIFOProcessing - Missing Parent To Child Relationship	There are incomplete FIFO transactions. note If both an individual FIFO and FIFO HTS file are transmitted review that your team has transmitted both files successfully and that the files have been loaded. Contact Support if this is not the case or if this error persists after corrective action.
FP020 - FIFOProcessing - Invalid Transaction Code	The TxnCode used is not a valid TxnCode FieldName in Global Codes maintenance. note Update the TxnCode on transactions in Preparation → FIFO Processing Correction.
FP030 - FIFOProcessing - Missing Transaction Date	The TxnDate is blank or the default missing date 1/1/1900. This date needs to be the date FTZ activity processed for and must be the same across all transactions processed at the time. note Update the TxnDate on transactions in Preparation → FIFO Processing Correction.
FP040- Missing Order NumReceipt.	The OrderNumReceipt is blank and must be populated. note Update the OrderNumReceipt on transactions in Preparation → FIFO Processing Correction.
FP050 - FIFOProcessing - Missing Order Number Work	The OrderNumWork is blank and must be populated. note Update the OrderNumWork on transactions in Preparation → FIFO Processing Correction.
FP051 - FIFOProcessing - Missing Order Number Work	The OrderNumWork is blank and must be populated. note Update the OrderNumWork on transactions in Preparation → FIFO Processing Correction.
FP060 - FIFOProcessing - Missing Order Number Ship	The OrderNumShip is blank and must be populated. note Update the OrderNumShip on transactions in Preparation → FIFO Processing Correction.
FP070 - FIFOProcessing - Invalid Product Number	The ProductNum used does not exist in the Item Master. note Verify the ProductNum on the transaction in Preparation → FIFO Processing Correction. Update if invalid or add the product to Global Classification or Item Master.
FP080 - FIFOProcessing - Product Type Does Not Match Item Master	The ProductTypeCode used is not PC, IM, or NM. note Verify the ProductTypeCode in Preparation → FIFO Processing Correction. Update ProductTypeCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP081 – FIFOProcessing – Product Type Code Should Be PC When Transaction Code is CNPC/CPPC	The ProductTypeCode used is not PC for product number change transactions. Only the PC product type is allowed. note Verify the ProductTypeCode in Preparation → FIFO Processing Correction. Update ProductTypeCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP081 – FIFOProcessing – Product Type Code Should Be PC When Transaction Code is DNPC/DPPC	The ProductTypeCode used is not PC for purchased component status change transactions. Only the PC product type is allowed. note Verify the ProductTypeCode in Preparation → FIFO Processing Correction. Update ProductTypeCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP081 – FIFOProcessing – Product Type Code Should Be PC When Transaction Code is DNIM/DPIM	The ProductTypeCode used is not IM for manufactured inventory status change transactions. Only the IM product type is allowed. note Verify the ProductTypeCode in Preparation → FIFO Processing Correction. Update ProductTypeCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP082 – FIFOProcessing – Invalid Product Number Change From PC to IM	The ProductTypeCode used on the positive product number change transaction is IM in the Item Master for the product. Only the PC product type is allowed. note Verify the ProductTypeCode in Preparation → FIFO Processing Correction. Update ProductTypeCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP100 - FIFOProcessing - Invalid NAFTA Certified Flag	The NaftaCertified used is not Y or N. note Verify the NaftaCertified in Preparation → FIFO Processing Correction. Update NaftaCertified in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP110 - FIFOProcessing - Transaction Quantity Should Be Positive	The TxnQty used is not greater than zero. note Verify the TxnQty in Preparation → FIFO Processing Correction. Update TxnQty on transactions in Preparation → FIFO Processing Correction.
FP111 - FIFOProcessing - Transaction Quantity Should Be Negative	The TxnQty used is not less than zero. note Verify the TxnQty in Preparation → FIFO Processing Correction. Update TxnQty on transactions in Preparation → FIFO Processing Correction.
FP115 - FIFOProcessing - Invalid Transaction Quantity UOM	The TxnQtyUOM used is not included in the list of Codes for the TxnQtyUOM FieldName in Global Codes maintenance. note Verify the TxnQtyUOM in Preparation → FIFO Processing Correction. Add new TxnQtyUOM in Global Codes maintenance or update Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP116 - FIFOProcessing - TxnQtyUOM Mismatch with Layers	The TxnQtyUOM used does not exist as a used TxnQtyUOM on existing inventory for the same product. note Verify the TxnQtyUOM in Preparation → FIFO Processing Correction. Update TxnQtyUOM in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP120 - FIFOProcessing - Quantity Per IM Should Be Positive	The QtyPerIM used is not greater than zero. note Verify the QtyPerIM in Preparation → FIFO Processing Correction. Update QtyPerIM on transactions in Preparation → FIFO Processing Correction.
FP121 - FIFOProcessing - Quantity Per IM Should Be One For Matching Issues	The QtyPerIM used on issued component and manufactured transactions (IPPC/IPIM) is not one when the same ProductNum/OrderNumWork combination is used on the production issued transaction (PPIM). If the same ProductNum is a component or sub assembly used to make the same finished good ProductNum, then it has to be a 1:1 ratio and QtyPerIM should be one. note Verify the QtyPerIM in Preparation → FIFO Processing Correction. Update QtyPerIM on transactions in Preparation → FIFO Processing Correction.
FP130 - FIFOProcessing - Weight Should Be Positive	The Weight used is not greater than zero. note Verify the Weight in Preparation → FIFO Processing Correction. Update Weight in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP135 - FIFOProcessing - Invalid Weight UOM	The WeightUOM should be KG. Any other UOM used will display an error. note Verify the WeightUOM in Preparation → FIFO Processing Correction. Update WeightUOM in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP140 - FIFOProcessing - Invalid Country Ship To	The CountryShipTo used does not exist in the Country maintenance. note Verify the CountryShipTo on the transaction in Preparation → FIFO Processing Correction. Update if wrong or add new country code to Country maintenance.
FP145 - FIFOProcessing - Neg Adj Country Ship To Should Be US	The CountryShipTo used is not US for the negative adjustment transaction. note Verify the CountryShipTo in Preparation → FIFO Processing Correction. Update the CountryShipTo on transactions in Preparation → FIFO Processing Correction.
FP150 - FIFOProcessing - Missing Transport ID	The TransportID is blank and must be populated. note Verify the TransportID in Preparation → FIFO Processing Correction. Update the TransportID on transactions in Preparation → FIFO Processing Correction.
FP160 - FIFOProcessing - Invalid Adjustment Product Number	The AdjProductNumber used on product number change transactions (CNPC and CPPC) does not exist in the Item Master. note Verify the AdjProductNumber in Preparation → FIFO Processing Correction. Add new product to Global Classification or Item Master or update AdjProductNumber to a valid product number in Preparation → FIFO Processing Correction.
FP170 - FIFOProcessing - Missing Negative Product Number Change Offset	The AdjProductNumber used on the positive product number change transaction does not have a matching negative product number change transaction for the same ProductNum. Both matching transactions TxnQty should also offset each other note Verify the AdjProductNumber and TxnQty in Preparation → FIFO Processing Correction. Update the AdjProductNumber and/or TxnQty on transactions in Preparation → FIFO Processing Correction.
FP171 - FIFOProcessing - Missing Positive Product Number Change Offset	The AdjProductNumber used on the negative product number change transaction does not have a matching positive product number change transaction for the same ProductNum. Both matching transactions TxnQty should also offset each other note Verify the AdjProductNumber and TxnQty in Preparation → FIFO Processing Correction. Update the AdjProductNumber and/or TxnQty on transactions in Preparation → FIFO Processing Correction.
FP172 - FIFOProcessing - Not Enough Receipts to cover Product Number Change	The TxnQty of the negative product change transaction (CNPC) is more than the available inventory to be converted. note Verify the TxnQty in Preparation → FIFO Processing Correction. Update TxnQty on transactions in Preparation → FIFO Processing Correction.
FP172 - FIFOProcessing - Not Enough Receipts to cover Status Change	The TxnQty of the negative status code change transaction (DNPC/DNIM) is more than the available inventory to be converted. note Verify the TxnQty in Preparation → FIFO Processing Correction. Update TxnQty on transactions in Preparation → FIFO Processing Correction.
FP173 - FIFOProcessing - Not Enough Scrap Hold to cover Scrap Transaction	The TxnQty of the recoverable scrap transaction (WPPC/ WPIM) is more than the available product’s scrap in Scrap Hold. note Verify the TxnQty in Preparation → FIFO Processing Correction. Update TxnQty on transactions in Preparation → FIFO Processing Correction.
FP180 - FIFOProcessing - Missing Shipment Record for SPNM Component	SPNM transactions of purchased components (SPNM TxnCode/ PC ProductTypeCode) are being processed without the transaction for the finished good (SPNM TxnCode/ NM ProductTypeCode). The link between the finished good and components is matching the OrderNumWork, OrderNumShip, CountryShipTo, and TxnCode. note Verify the SPNM transactions in Preparation → FIFO Processing Correction. Update necessary fields to ensure a match on transactions in Preparation → FIFO Processing Correction.
FP190 - FIFOProcessing - Transaction and Product Type Do Not Match	The ProductTypeCode used does not match last two characters of the TxnCode for non-SPNM transactions. or The ProductTypeCode used on SPNM transactions is not ‘NM’ or ‘PC’. The two options available for SPNM transactions are ‘NM’ and ‘PC’. note Verify the ProductTypeCode in Preparation → FIFO Processing Correction. Update ProductTypeCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP200 - FIFOProcessing – Country Visa Required	The client-designated field used to hold the Visa number is blank and the CountryOfOrigin on the transaction is included in the configured list of countries with a Visa quota. note Verify the designated Visa number field in Preparation → FIFO Processing Correction. Update designated Visa number field on transactions in Preparation → FIFO Processing Correction.
FP271 - FIFOProcessing - Please contact your administrator. Configuration For Clock/Watch Processing is Not Complete	The clock/watch processing setup is not complete. note Please contact Support if you get this error.
FP280 - FIFOProcessing - Transaction Quantity Should Be Less Than Maximum Value Limit	The TxnQty used exceeds the maximum value allowed by the Max_Txn_TxnQty FieldName in Global Codes maintenance. note Verify the TxnQty in Preparation → FIFO Processing Correction. Update TxnQty if wrong or update the Max_Txn_TxnQty FieldName in Global Codes maintenance.
FP281 - FIFOProcessing - Transaction Weight Should Be Less Than Maximum Value Limit	The Weight used exceeds the maximum value allowed by the Max_Txn_Weight FieldName in Global Codes maintenance. note Verify the Weight in Preparation → FIFO Processing Correction. Update Weight in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction if wrong. If correct, update the Max_Txn_Weight FieldName in Global Codes maintenance.
FP282 - FIFOProcessing - Transaction Value Should Be Less Than Maximum Value Limit	The Value used exceeds the maximum value allowed by the Max_Txn_Value FieldName in Global Codes maintenance. note Verify the Value in Preparation → FIFO Processing Correction. Update Value in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction if wrong. If correct, update the Max_Txn_Value FieldName in Global Codes maintenance.
FP283 - FIFOProcessing - Transaction Value2 Should Be Less Than Maximum Value Limit	The Value2 used exceeds the maximum value allowed by the Max_Txn_Value2 FieldName in Global Codes maintenance. note Verify the Value2 in Preparation → FIFO Processing Correction. Update Value2 in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction if wrong. If correct, update the Max_Txn_Value2 FieldName in Global Codes maintenance.
FP284 - FIFOProcessing - Transaction HTSUOMConvFactor Should Be Less Than Maximum Value Limit	The HTSUOMConvFactor used exceeds the maximum value allowed by the Max_Txn_HTSUOMConvF FieldName in Global Codes maintenance. note Verify the HTSUOMConvFactor in Preparation → FIFO Processing Correction. Update HTSUOMConvFactor in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction if wrong. If correct, update the Max_Txn_HTSUOMConvF FieldName in Global Codes maintenance.
FP285 - FIFOProcessing - Multiple Lots for Same OrderNumWork	The OrderNumWork used on the issued production transaction has been processed through FIFO before with a different lot or is trying to be processed with different lots. Each OrderNumWork/Lot combination should be unique. note Update the designated IMLot field, default is RCO22, on transactions in Preparation → FIFO Processing Correction.
FP286 - FIFOProcessing - Missing SetBreakdown	The HTSIndex used for a product set up as an active clock/watch does not have a ClockSequence or the HTSIndex used on the transaction does not match one of the HTSIndex setup on the active clock/watch. note Verify the HTSIndex in Preparation → FIFO Processing Correction. Update HTSIndex if wrong or add ClockSequence in Global Classification or the Item Master set breakdown.
FP287 - Missing Exchange Rate	The foreign CurrencyCode used does not have an exchange rate for the ExportDate on the transaction in Exchange Rate maintenance. note Verify the ExportDate in Preparation → FIFO Processing Correction. Update ExportDate if wrong or add new exchange rate in Exchange Rate maintenance.
FP288 - FIFOProcessing - Transaction Value Should Be More Than Minimum Value Limit	The Value used is less than the minimum value allowed by the Min_Txn_Value FieldName in Global Codes maintenance. note Update Value in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction if wrong. If correct, update the Min_Txn_Value FieldName in Global Codes maintenance.
FP289 - FIFOProcessing - Invalid Transaction Value	The Value used is equal to the Code on an Invalid_Txn_Value FieldName in Global Codes maintenance. note Verify the Value in Preparation → FIFO Processing Correction. Update Value in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction if wrong. If correct, update the Invalid_Txn_Value FieldName in Global Codes maintenance.
FP290 - Too Many Additional Fields Records	More than one record exists in the FIFO Processing Additional Fields repository for non-clock setup transactions. note Verify the Additional Fields records for the transaction from your Preparation → FIFO Processing Correction screen. Delete any invalid Additional Fields records. If this error persists, please contact Support.
FP300 - Unmatched Additional Fields Record	Clock setup transaction with a matching record existing in the FIFO Processing Additional Fields repository does not have the same HTSNum . note Verify the HTSNum and HTSIndex in Preparation → FIFO Processing Correction. Update HTSNum in HTS Codes maintenance for the HTSIndex on transaction for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP350 - FifoProcessing - Shipments assigned to a printed document (hist records)	Shipment transactions within the current FIFO run are assigned to a document that has been generated. note Unprint the document(s) by selecting “Unprint” within the Reports → CF7501 Entry screen or Reports → Outbound Bonded Movement Summary. Alternatively, unprint the entry by selecting the document number from the Tools → Reprint ExitDocID screen.
FP360 - FifoProcessing - Shipments assigned to a printed document (lastProcessedDate)	Shipment transactions within the current FIFO run are assigned to a document that has been generated. note Unprint the document(s) by selecting “Unprint” within the Reports → CF7501 Entry screen or Reports → Outbound Bonded Movement Summary. Alternatively, unprint the entry by selecting the document number from the Tools → Reprint ExitDocID screen.
FP370 - FifoProcessing - HS unit price outside restriction bounds	The unit price being calculated by dividing the Value of the transaction by the TxnQty is not within the MinPrice and MaxPrice bounds established for this Classification HS group. note Verify the Value and TxnQty in Preparation → FIFO Processing Correction. Update Value in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction or update TxnQty of transactions in Preparation → FIFO Processing Correction
FP510 - FIFOProcessing - Invalid HTS Number	The HTSNum used is not in the HTS Codes maintenance. note Verify the HTSNum in Preparation → FIFO Processing Correction. Add new HTSNum to HTS Codes maintenance for transaction sourcing and/or update HTSNum on the transaction in Preparation → FIFO Processing Correction.
FP520 - FIFOProcessing - Invalid Status Code	StatusCode must be a one-letter character. Below are what each character represents: D – Domestic N – Non-privileged Foreign P – Privileged Foreign I – Immediate Duty Paid Z – Zone Restricted note Verify the StatusCode in Preparation → FIFO Processing Correction. Update StatusCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP521 - FIFOProcessing - Invalid Status Code	StatusCode used on status code transactions (DPPC and DPIM) is not privileged or zone restricted. The status code must be one of the two. note Verify the StatusCode in Preparation → FIFO Processing Correction. Update StatusCode on transactions in Preparation → FIFO Processing Correction.
FP525 - FIFOProcessing - Invalid Status Code for Zone to Zone	The StatusCode being on positive receipts or adjustments of products that can be sent zone to zone are privileged. note Verify the StatusCode in Preparation → FIFO Processing Correction. Update StatusCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP530 - FIFOProcessing - Invalid SPI Code 1	The SPICode1 used does not exist in the SPI Codes maintenance. note Verify the SPICode1 in Preparation → FIFO Processing Correction. Update SPICode1 for matching HTSIndex in HTS Codes maintenance and/or transactions in Preparation → FIFO Processing Correction or add the SPICode to SPI Codes maintenance.
FP535 - FIFOProcessing - Invalid SPI Code 1 HTS Combo	The SPICode1 used does not exist in HTS Codes maintenance for the matching HTSNum. note Verify the SPICode1 in Preparation → FIFO Processing Correction. Update SPICode1 for matching HTSIndex in HTS Codes maintenance and/or transactions in Preparation → FIFO Processing Correction.
FP540 - FIFOProcessing - Invalid SPI Code 2	The SPICode2 used does not exist in the SPI Codes maintenance. note Verify the SPICode2 in Preparation → FIFO Processing Correction. Update SPICode2 for matching HTSIndex in HTS Codes maintenance and/or transactions in Preparation → FIFO Processing Correction or add the SPICode to SPI Codes maintenance.
FP545 - FIFOProcessing - Invalid SPI Code 2 HTS Combo	The SPICode2 used does not exist in HTS Codes maintenance for the matching HTSNum. note Verify the SPICode2 in Preparation → FIFO Processing Correction. Update SPICode2 for matching HTSIndex in HTS Codes maintenance and/or transactions in Preparation → FIFO Processing Correction.
FP546 - FIFOProcessing - SPI Code 1 and SPI Code 2 Cannot Contain Values	The SPICode1 and SPICode2 used must be blank. note Verify the SPICode1 and SPICode2 in Preparation → FIFO Processing Correction. Update SPICode1 and SPICode2 for matching HTSIndex in HTS Codes maintenance and/or transactions in Preparation → FIFO Processing Correction.
FP550 - FIFOProcessing - Invalid Country Of Origin	The CountryOfOrigin used does not exist in the Country maintenance. note Verify the CountryOfOrigin in Preparation → FIFO Processing Correction. Add new country to Country maintenance or update CountryOfOrigin in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP550 - FIFOProcessing - Country Of Origin cannot be US on a 214	The CountryOfOrigin used cannot be US for foreign status receipts. note Verify the CountryOfOrigin in Preparation → FIFO Processing Correction. Update CountryOfOrigin in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP555 - FIFOProcessing - Prohibited Country Of Origin	The CountryOfOrigin used is flagged as prohibited in the Country maintenance. note Verify the CountryOfOrigin in Preparation → FIFO Processing Correction. Update CountryOfOrigin in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP560 - FIFOProcessing - Invalid Manufacturer ID	The ManufacturerID used is not in the Manufacturer ID maintenance. note Verify the ManufacturerID in Preparation → FIFO Processing Correction. Add new ManufacturerID to Manufacturer ID maintenance or update ManufacturerID in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP570 - FIFOProcessing - Invalid Relationship Flag	The RelationShipFlag used is not ‘N’ or ‘Y’, which are the only values allowed. note Verify the RelationShipFlag in Preparation → FIFO Processing Correction. Update RelationShipFlag in Manufacturer ID maintenance for matching ManufacturerID for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP580 - FIFOProcessing - Invalid HTS Index	The HTSIndex used is not in the HTS Codes maintenance. note Verify the HTSIndex in Preparation → FIFO Processing Correction. Add new HTSIndex to HTS Codes maintenance or update HTSIndex in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP590 - FIFOProcessing - Invalid HTS Description	The HTSDesc used is blank. note Verify the HTSDesc in Preparation → FIFO Processing Correction. Update HTSDesc for matching HTSIndex in HTS Codes maintenance for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP600 - FIFOProcessing - Invalid HTS Number 2	The HTSNum2 used is not in the HTS Codes maintenance. note Verify the HTSNum2 in Preparation → FIFO Processing Correction. Add new HTSNum2 to HTS Codes maintenance or update HTSNum2 in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP610 - FIFOProcessing - Value Should Be Positive	The Value used cannot be a negative value or zero. note Verify the Value in Preparation → FIFO Processing Correction. Update Value in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP615 – FIFOProcessing – Alternate Value Should Be Zero or Positive	The AltValue used cannot be less than zero. note Verify the AltValue in Preparation → FIFO Processing Correction. Update AltValue in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP620 - FIFOProcessing - HTS Number 2 Should Contain Data When Value 2 Contains Data	The Value2 used is less than zero or the Value2 is not zero and the HTSNum2 is blank. If Value2 is populated, then HTSNum2 should be populated. note Verify the Value2 in Preparation → FIFO Processing Correction. Update Value2 in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP625 - FIFOProcessing - HTS Number 2 Should Contain Data When Alternate Value 2 Contains Data	The AltValue2 used is less than zero or the AltValue2 is not zero and the HTSNum2 is blank. If AltValue2 is populated, then HTSNum2 should be populated. note Verify the AltValue2 in Preparation → FIFO Processing Correction. Update AltValue2 in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP630 - FIFOProcessing - Invalid Currency Code	The CurrencyCode used is blank or is not a valid currency code in the Country maintenance. note Verify the CurrencyCode in Preparation → FIFO Processing Correction. Update CurrencyCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP635 - FIFOProcessing - Invalid Alternate Currency Code	The AltCurrencyCode used is blank or is not a valid currency code in the Country maintenance when the AltValue or AltValue2 is greater than zero. note Verify the AltCurrencyCode in Preparation → FIFO Processing Correction. Update AltCurrencyCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP640 - FIFOProcessing - Ad Valorem Rate Should Be Between Zero and Maximum Rate	The AdValoremRate used cannot be greater than configured maximum limit. Default is 21% note Verify the AdValoremRate in HTS Codes maintenance. Update if wrong for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction. If correct, contact Support to configure a new maximum limit.
FP650 - FIFOProcessing - Specific Rate Should Be Zero or Positive	The SpecificRate used cannot be less than zero. note Verify the SpecificRate in HTS Codes maintenance. Update if wrong for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP660 - FIFOProcessing - HTS UOM Conversion Factor Should Be Positive	The HTSUOMConvFactor used is not greater than zero. note Verify the HTSUOMConvFactor in Preparation → FIFO Processing Correction. Update HTSUOMConvFactor in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP665 - FIFOProcessing - HTS UOM Conversion Factor Should Match Weight When RptQtyUOM is KG	The Weight and HTSUOMConvFactor used do not match when the HTS has a RptyQtyUOM of KG. Both values must be the same. note Verify the HTSUOMConvFactor in Preparation → FIFO Processing Correction. Update HTSUOMConvFactor in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP670 - FIFOProcessing - Additional HTS UOM Conversion Factor Should Be Zero or Positive	The AddlHTSUOMConvFactor used cannot be less than zero. note Verify the AddlHTSUOMConvFactor in Preparation → FIFO Processing Correction. Update AddlHTSUOMConvFactor in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP672 - FIFOProcessing - HTS UOM Conversion Factor Should Match Item Master HTS UOM Conversion Factor on zone to zone receipts	The HTSUOMConvFactor used when FromZoneId is populated does not match the HTSUOMConvFactor in the Item Master for the matching product. Both values must be the same. note Verify the HTSUOMConvFactor in Preparation → FIFO Processing Correction. Update HTSUOMConvFactor in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP673 - Addl HTS UOM Conversion Factor Should Match Item Master Addl UOM Conversion Factor on zone to zone receipts AddlRptQtyUOM is KG	The AddlHTSUOMConvFactor used when FromZoneId is populated does not match the AddlHTSUOMConvFactor in the Item Master for the matching product. Both values must be the same. note Verify the AddlHTSUOMConvFactor in Preparation → FIFO Processing Correction. Update AddlHTSUOMConvFactor in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP675 - FIFOProcessing - Additional HTS UOM Conversion Factor Should Match Weight When AddlRptQtyUOM is KG	The Weight and AddlHTSUOMConvFactor used do not match when the HTS has an AddlRptyQtyUOM of KG. Both values must be the same. note Verify the AddlHTSUOMConvFactor in Preparation → FIFO Processing Correction. Update AddlHTSUOMConvFactor in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP680 - FIFOProcessing - Invalid Reporting Quantity UOM	The RptQtyUOM used is not included in the list of Codes for the RptQtyUOM FieldName in Global Codes maintenance. note Verify the RptQtyUOM in Preparation → FIFO Processing Correction. Update RptQtyUOM in HTS Codes maintenance for the HTSIndex on the transaction for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction if wrong. If correct, add the new RptQtyUOM FieldName in Global Codes maintenance.
FP681 - FIFOProcessing - Invalid Reporting Quantity UOM	The RptQtyUOM used is not included in the list of Codes for the RptQtyUOM FieldName in Global Codes maintenance. note Verify the RptQtyUOM in Preparation → FIFO Processing Correction. Update RptQtyUOM in HTS Codes maintenance for the HTSIndex on the transaction for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction if wrong. If correct, add the new RptQtyUOM FieldName in Global Codes maintenance.
FP690 - FIFOProcessing - Additional Report Qty Unit of Measure cannot be blank if AddlHTSUomConvFactor > 0	The AddlRptQtyUOM used is not included in the list of Codes for the RptQtyUOM FieldName in Global Codes maintenance and the AddlHTSUOMConvFactor is greater than zero. note Verify the AddlRptQtyUOM in Preparation → FIFO Processing Correction. Update AddlRptQtyUOM in HTS Codes maintenance for the HTSIndex on the transaction for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction if wrong. If correct, add the new RptQtyUOM FieldName in Global Codes maintenance.
FP691 - FIFOProcessing - Additional Report Qty Unit of Measure cannot be blank if AddlHTSUomConvFactor > 0	The AddlRptQtyUOM used is not included in the list of Codes for the RptQtyUOM FieldName in Global Codes maintenance and the AddlHTSUOMConvFactor is greater than zero. note Verify the AddlRptQtyUOM in Preparation → FIFO Processing Correction. Update AddlRptQtyUOM in HTS Codes maintenance for the HTSIndex on the transaction for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction if wrong. If correct, add the new RptQtyUOM FieldName in Global Codes maintenance.
FP700 - FIFOProcessing - Value Should Be Positive for Transaction Codes with Currency Conversion	The Value used cannot be a negative value or zero. note Verify the Value in Preparation → FIFO Processing Correction. Update Value in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP710 - FIFOProcessing - Currency Code Should Exist for Transaction Codes with Currency Conversion	The CurrencyCode used is blank or does not exist in the Country maintenance. note Verify the CurrencyCode in Preparation → FIFO Processing Correction. Update CurrencyCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP715 - FIFOProcessing - Currency Code Should Match Base Currency for Transaction Codes with Currency Conversion	The CurrencyCode used does not match the configured base currency code. Default is USD if not configured for different currency. note Verify the CurrencyCode in Preparation → FIFO Processing Correction. Update CurrencyCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP720 - FIFOProcessing - Antidumping Case Numbers Must Have Corresponding Antidumping Duty Rates	The ADDutyRate used is greater than zero and ADDCaseNumber is blank or the ADDutyRate is less than or equal to zero and ADDCaseNumber is not blank. note Verify the ADDutyRate in Preparation → FIFO Processing Correction. Update ADDutyRate in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP725 - FIFOProcessing - Status Code cannot be Nonprivileged Foreign when Antidumping exists	The StatusCode used is not privileged foreign and the ADDutyRate is not zero or the ADCaseNumber is not blank. note Verify the StatusCode in Preparation → FIFO Processing Correction. Update StatusCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP730 - FIFOProcessing - Countervaling Case Numbers Must Have Corresponding Countervaling Duty Rates	The CVDutyRate used is greater than zero and CVCaseNumber is blank or the CVDutyRate is less than or equal to zero and CVCaseNumber is not blank. note Verify the CVDutyRate in Preparation → FIFO Processing Correction. Update CVDutyRate in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP735 - FIFOProcessing - Countervailing Requires Status Code to be Privileged Foreign	The StatusCode used is not privileged foreign and the CVDutyRate is not zero or the CVCaseNumber is not blank. note Verify the StatusCode in Preparation → FIFO Processing Correction. Update StatusCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP740 - FIFOProcessing - Additional Specific Rate Requires An Additional Report Quantity UOM	The AddSpecificRate used is greater than zero and AddlRptQtyUOM is blank or the AddlSpecificRate is less than zero. note Verify the AddlSpecificRate in Preparation → FIFO Processing Correction. Update AddlSpecificRate in HTS Codes maintenance of HTSIndex on transaction for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
FP755 - FIFOProcessing - TxnNumGUID Already Processed Through FIFO	The transaction being processed has a TxnNumGUID previously processed through FIFO. The same TxnNumGUID cannot be used multiple times, as it is a FIFO transaction’s unique identifier. note Verify the TxnNumGUID in Preparation → FIFO Processing Correction. Delete the transaction if determined a duplicate transaction or contact Support for assistance if not a duplicate transaction.
FP760 - FIFOProcessing - There should be one and only one HTS Values record for each FIFOProcessing record	There is more than one HTS Values record for a transaction. note Verify the HTS Values records for the transaction from Preparation → FIFO Processing Correction screen. Delete any invalid HTS Values records. If this error persists, please contact Support.
HS100 - HTS - HS updates from tmdHTSUpdates need to be applied	Identified HTS updates have not been applied to HTS Codes maintenance. note The user can apply or remove the HTS Codes maintenance updates in Maintenance → HTS Updates. This validation will persist until all updates have either been applied or removed.
HS200 - TmdHTS - Blank HTS records exist	HTS Codes maintenance has records with a blank HTSIndex or HTSNum . note Update the HTSIndex or HTSNum in HTS Codes maintenance.
SM010 - Staging Move Check	The staging data transfer process did not complete successfully. note Please contact Support if you get this error.
SB010 SetBreakdown - Missing ClockSequence of 1	The product is set up as a clock/watch and does not have a HTS for ClockSequence of 1. note The user can edit the ClockSequence ordering in Global Classification or the Item Master.
SB020 - SetBreakdown - Duplicate ClockSequence	The product is set up as a clock/watch and has multiple HTS for the same ClockSequence . note The user can edit the ClockSequence ordering in Global Classification or the Item Master.
F010 - FIFO - Check 3461 Overflow	The 3461/7501 reconciliation report has actual values larger than the estimated values. The 3461 has not adequately estimated the outbound shipments and will need to be reviewed.
WG509 - FIFOProcessing - \|Global Trade Content\| shows HTS may have ADD/CVD applicability	The HTSNum/CountryOfOrigin used for receipt may be applicable to Additional Duty or Countervailing according to Content. note Verify the HTSNum in Content and determine appropriate action with compliance team. Additional Duty or Countervailing details can be updated for products in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
WG510 - FIFOProcessing - Global Trade Content shows Invalid HS Number	The HTSNum used is not valid according to Content. note Verify the HTSNum in Content. Add new HTSNum in HTS Codes maintenance and update products HTSNum in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
WG511 - FIFOProcessing - \|Global Trade Content\| shows HTS may have ADD/CVD applicability	The HTSNum2/CountryOfOrigin used for receipt may be applicable to Additional Duty or Countervailing according to Content. note Verify the HTSNum in Content and determine appropriate action with compliance team. Additional Duty or Countervailing details can be updated products in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
WG515 - FIFOProcessing - Scope of Authority	The HTSNum used is not included in allowed scope of authority. note Verify allowed HTSNum in Scope Of Authority maintenance. Update products HTSNum in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
WG680 - FIFOProcessing - Global Trade Content shows Invalid Reporting Quantity UOM	The RptQtyUOM used is not valid for the associated transaction’s HTSNum according to Content. note Verify the RptQtyUOM in Content. Update the RptQtyUOM in HTS Codes maintenance and transactions in Preparation → FIFO Processing Correction
WG690 - FIFOProcessing - Global Trade Content shows Invalid AddlRptQtyUOM	The AddlRptQtyUOM used is not valid for the associated transaction’s HTSNum according to Content. note Verify the AddlRptQtyUOM in Content. Update the AddlRptQtyUOM in HTS Codes maintenance and transactions in Preparation → FIFO Processing Correction.
WG700 - FIFOProcessing - Issued PC with no Issued IM	There are existing issued production, IPPC/IPIM, transactions with an OrderNumWork missing a positive production transaction, PPIM, that are older than the configured window. This window is a default of 60 days in the past. note The user will need to use available reports and search functionality to review older issued production transactions and determine internally the validity of these transactions. These will need to be cleaned up by backing out quantities with negative issued transactions, INPC/INIM, and negatively adjusted, ANPC/ANIM, to consume appropriate inventory. Duty inversion will not be realized during cleanup.
WG800 - FIFOProcessing - Negative issue of PC exceeds positive issue	There is a larger TxnQty of negative issued transactions, INPC/INIM, being processed than available issued production, IPPC/IPIM, TxnQty for each ProductNum/OrderNumWork combination. note The user will need to use available reports and search functionality to review any negative and positive issued transactions being processed along with available positive issued amounts for each ProductNum/OrderNumWork combination. The TxnQty can be updated for appropriate transactions in Preparation → FIFO Processing Correction.
WG-A33 - FifoReceipt–Parent ProductNum for a set is in on hand inventory layers and is not broken out. This ProductNum may have recently been added to the sets table	There is existing inventory for a ProductNum that exists in set breakdown as the parent product number of a set. Existing inventory may need to be broken out into a set. note Verify the ProductNum setup in Global Classification or Item Master. Update setup if ProductNum should not be a set. If ProductNum is correct, reach out to Support for assistance to turn existing inventory into a set. Existing inventory would need to be backed out using negative receipts and then a new receipt processed as a set to bring inventory back in correctly broken out as a set.
WG-01 - FIFOProcessing - Weight cannot be 9999 if Finished Good Will Consume Foreign Inventory	The Weight used cannot be 9999 for a finished good shipment. note Verify the Weight in Preparation → FIFO Processing Correction. Update Weight in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
WG-02 - FIFOProcessing - HTSIndex Cannot Be 1111111111, 0000000000, or 9999999999 if Finished Good Will Consume Foreign Inventory	The HTSIndex or HTSNum used cannot be 1111111111, 0000000000, or 9999999999 for a finished good shipment. note Verify the HTSIndex and HTSNum in Preparation → FIFO Processing Correction. Update HTSIndex or HTSNum in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
WG-03 - FIFOProcessing - HtsUomConvFactor cannot be 9999 if Finished Good Will Consume Foreign Inventory	The HTSUOMConvFactor used cannot be 9999 for a finished good shipment. note Verify the HTSUOMConvFactor in Preparation → FIFO Processing Correction. Update HTSUOMConvFactor in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
WG-04 - FIFOProcessing - AddlHtsUomConvFactor cannot be 9999 if Finished Good Will Consume Foreign Inventory	The AddlHTSUOMConvFactor used cannot be 9999 for a finished good shipment. note Verify the AddlHTSUOMConvFactor in Preparation → FIFO Processing Correction. Update AddlHTSUOMConvFactor in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
TX-02 - FIFOProcessing - AddlHtsUomConvFactor cannot be 9999 when receipt or adjustment is foreign	The AddlHTSUOMConvFactor used cannot be 9999 for a foreign status receipt or adjustment. note Verify the AddlHTSUOMConvFactor in Preparation → FIFO Processing Correction. Update AddlHTSUOMConvFactor in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
TX-03 - FIFOProcessing - COO Cannot be XX when Status Code is Foreign	The CountryOfOrigin used cannot be XX with a foreign status. note Verify the CountryOfOrigin in Preparation → FIFO Processing Correction. Update CountryOfOrigin in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
TX-04 - FIFOProcessing - MID Cannot Be NA, MULTIPLE, MISSINGMID, MIDGOESHERE, USDOMREC	The ManufacturerId used cannot be NA, MULTIPLE, MISSINGMID, MIDGOESHERE, USDOMREC, or MISSING. note Verify the ManufacturerId in Preparation → FIFO Processing Correction. Update ManufacturerId in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
TX-05 - FIFOProcessing - HTSIndex cannot be 1111111111, 0000000000, or 9999999999	The HTSIndex or HTSNum used cannot be 1111111111, 0000000000, or 9999999999 with a foreign status. note Verify the HTSIndex and HTSNum in Preparation → FIFO Processing Correction. Update HTSIndex or HTSNum in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
TX-06 - FIFOProcessing - Weight cannot be 9999 when receipt or adjustment is foreign	The Weight used cannot be 9999 with a foreign status receipt or adjustment. note Verify the Weight in Preparation → FIFO Processing Correction. Update Weight in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.
TX-07 - FIFOProcessing - TxnCode Does Not Match ProductTypeCode	The ProductTypeCode used does not match the last two characters of the TxnCode for positive and negative issued transactions. note Verify the ProductTypeCode and TxnCode in Preparation → FIFO Processing Correction. Update ProductTypeCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction. If ProductTypeCode is correct, update the TxnCode in Preparation → FIFO Processing Correction.
FP-22 - FIFOProcessing - Invalid ProductTypeCode Change	The ProductTypeCode does not match the ProductTypeCode on existing inventory and issued transactions in the system. The ProductTypeCode must be the same across the system. note Verify the ProductTypeCode in Preparation → FIFO Processing Correction. Update ProductTypeCode in Global Classification or Item Master for transaction sourcing and/or transactions in Preparation → FIFO Processing Correction.

This article applies to:

Product: ONESOURCE Global Trade
Sub-Product: US Regimes & Connectivity

Solutions

Law firms

Tax, audit & accounting firms

Corporations

Governments

Success stories

Products

Legal

Trade & supply

Tax, audit & accounting

Corporate tax

Risk & fraud

Books

Recommended products

Purchase

Buy solutions

Buy books

Contact sales

Questions? We are here to help.

Resources

Insights

Events

Product training

Product communities

Developers

Highlights

Help

Learn

FTZ Management: Preparation - Resolving Common Validation Messages in FIFO Processing

This article applies to:

Related Content