IMMEX Prevalidation/FIFO Errors
This manual was created to help IMMEX users have a better understanding of the validated information in the system.
The tables show the most common errors that users face when validating information in daily processing.
If you encounter one of these errors, these are the standard solutions we propose. If after taking these validations into account, the error is still displayed, please contact our support team at integrationpoint@thomsonreuters.com
Errors in the invoice header
FIELD BEING VALIDATED | ERROR | STANDARD SOLUTION |
|---|---|---|
TxnQty | MXIH010 - Invoice has no transactions | All invoices need transactions; otherwise, they cannot be validated.
important
Edit the invoice and add transactions on Product Data tab. |
ModeOfTransport | MXIH020 - Mode of Transport not valid | The ModeOfTransport code has to be a valid code included in the Global Codes catalog. This catalog is personalized with information provided by the client previously.
important
You can add a new record manually or can check with support for valid codes. |
Invoice Date | MXIH030 - Invoice Date not valid | The format for this field is YYYYMMDDTHHMMSS. For example: 10:35:03AM on September 12, 2003 would read as 20030912T103503. If only date is available, place zeros for HHMMSS.
important
The system will display an error if the date inserted is older than 01/01/1900 or the date does not match the format. |
Manifest Quantity | MXIH040 - Manifest Quantity must be positive | The value on this field must be ‘zero’ or positive. It cannot be ‘blank’ or have negative values.
important
Go to Invoice Header tab and correct the Manifest Quantity. |
Country ShipTo | MXIH050 - Country Ship To not valid | Verify that the Country Code has a correct abbreviation (e.g. “DN” for Denmark when it should be “DK”). These codes have to be registered on the Country Listing catalog.
Also, verify that the company’s record on the Company Partners catalog has a country selected in the Addresses tab.important
You can only add Country Codes provided by default. |
ToCompany RFC | MXIH060 - ToCompany RFC not valid | The RFC (FederalID) record has to be a valid one registered on the Company Partners catalog. This catalog has the information of all the partners provided by the client previously.
important
You can add a new record manually or contact support. |
FromCompanyRFC | MXIH070 - FromCompany RFC not valid | The RFC (FederalID) record has to be a valid one registered on the Company Partners catalog. This catalog the information of all the partners provided by the client previously.
important
You can add a new record manually or contact support. |
RemesaNum | MXIH080 - RemesaNum is duplicated in a current invoice | You are trying to process an invoice that has the same Pedimento Number and Remesa Number. Please verify other active invoices.
important
This error does not apply for consolidated pedimentos. |
RemesaNum | MXIH090 - RemesaNum is duplicated in an invoice in history | You are trying to work with an invoice that has been already processed with the same Pedimento Number and Remesa Number. Please verify other processed invoices.
important
This error does not apply for consolidated pedimentos. |
Invoice Type | MXIH100 - Invoice Type is not valid | Invoice type is not registered in the Global Codes catalog.
important
Please contact support if you get this error. |
Country ShipTo | MXIH110 - CountryShipTo does not match CompanyCountry in config | For import invoices, the country of the ShippedTo company country must match the CompanyCountry in the configuration (Mexico).
important
Please contact support if you get this error. |
ProductNum | MXFP088 - No static BOM found for product | For export invoices, all products categorized as an INVENTORY MANUFACTURED PRODUCT (Product Type Code) in the item master must have an associated Static BOM with aM-Manufacturing type registered for that product.
important
This validation will be verified if the tag on Config,xml <static_bom_processing><enabled>Y</enabled>) is “Yes”. important
You can add a child Product Number by creating a new Static BOM for this product. Navigate to the Maintain Static BOM screen, select Bill of Materials Type , and choose M - Manufacturing from the drop-down menu. |
MXEchangeRate | WFP104 - MX Exchange Rate not informed on Pedimento | During invoice pre-validation, ensure that the associated Pedimento contains a declared exchange rate.
important
If the value declared in the Pedimento is 0, this warning message also occurs. important
In the Search by Invoice screen, click on the left of the invoice to select Edit and then input the exchange rate in the MX Exchange Rate field under the Pedimento tab. |
Errors on the ItemMaster
VALIDATED FIELD | ERROR MESSAGE DISPLAYED | POSSIBLE SOLUTION |
|---|---|---|
ProductNum | FP020 - No Item Master record found for product | The product selected for this transaction is not registered on the ItemMaster catalog.
important
You can add this manually or contact support for help. |
ProductNum | FP030 - No MX Item Master record found for product. FP035 - No US Item Master record found for product | The product selected for this transaction is not registered on the MXItemMaster catalog.
important
You can add this manually or contact support for help. |
Product Desc | FP040 - Product Description cannot be blank | This product is missing the description on ItemMaster (this field is mandatory).
important
You must add the product description directly to the ItemMaster. |
TxnQtyUom vs Itemmaster | FP050 - TxnQtyUom must match Item Master | The TxnQtyUom for the product being processed does not match the one registered on the system for this product on ItemMaster catalog. |
TxnQtyUom vs Global Codes | FP060 - TxnQtyUom not found in Global Codes | The code TxnQtyUom must be a valid code included in the Global Codes catalog.
important
You can add a new record or can check with support for valid codes. |
TxnQtyUom | FP070 - TxnQtyUom does not match UOM in inventory (Layers) | The TxnQtyUom for the product being processed matches the TxnQtyUom registered on the ItemMaster catalog, but it is inconsistent with the TxnQtyUom used on other transactions previously processed for the same product.
important
Please verify the correct TxnQtyUom. |
ProductType | FP080 - ProductType not found in Global Codes | Verify that the code being used is one of the valid Product Codes on the Global Codes catalog.
important
You cannot add new Product Codes other than the ones by default. |
ProductType vs ItemMaster | FP100 - ProductType must match Item Master | The ProductTypeCode on the transaction does not match the ProductTypeCode on the ItemMaster. For instance: you are trying to process a product as ‘PC’ while ItemMaster record is ‘IM’. |
Weight | FP110 - Weight must be > 0 | Check for values that have a ‘0’ or a ‘blank’ value. Any number registered has to be greater than “0”.
important
This field is numeric, so any letter or symbol on the record will create an error. |
Weight | FP130 - Weight exceeds maximum weight limit on Global Codes | The weight reported on the transaction exceeds the maximum weight allowed estimated by the client previously on the Global Codes catalog. |
AltProductDesc | MXFP010 - AltProductDesc not valid | The product being processed is missing AltProductDesc (Spanish description) on the MX ItemMaster catalog.
important
Go to the Additional Table tab on the ItemMaster and enter a Spanish product description. |
AltValue | FPH040 - AltValue cannot be < 0 | This is a mandatory field. ‘Blank’ or negative values will not allow continuation with the process. Verify this field on both the ItemMaster ( ItemMasterHTSValues tab) catalog and Staging transactions.
important
You can edit this information on the Edit Staging Transactions screen or the ItemMaster. |
Added Value | FPH050 - AddedValue must be > 0 | This is a mandatory field. ‘Blank’ values will not allow you to continue with the process. Verify this field on both the ItemMaster (ItemMasterHTSValues tab) catalog and Staging transactions.
important
You can edit this information on the Edit staging transactions screen or ItemMaster. |
Value 2 | FPH060 - Value 2 cannot be > 0 when HTS Number 2 is blank | There is no value recorded on HTSNum2 for the product being processed, therefore Value2 is not applicable. Verify if HTSNum2 must have a value or if Value2 should be deleted. |
Value 2 | FPH070 - Value 2 must be > 0 when HTS Number 2 is not blank | If there is a value in the HTSNum2 field for the product being processed, then Value2 must be filled with the value that corresponds to the tariff. |
Value | FPH090 - Value must be > 0 | Check for values that have a ‘0’ or a ‘blank’ value. This field must be greater than “0”.
important
This field is numeric, so any letter or symbol on the record will create an error. |
HTS UOM Conversion Factor | FPH130 - HTS UOM Conversion Factor must be > 0 | Check for values that have a ‘0’ or a ‘blank’ value. This field must be greater than “0”.
important
This field is numeric, so any letter or symbol on the record will create an error. |
HTS UOM Conversion Factor vs Weight | FPH150 - HTS UOM Conversion Factor must match Weight when RptQtyUom is KG | When RptQtyUom is established in KG, the HTSUOM conversion factor from the ItemMasterHTSValues must be equal to the value entered on the Weight field. |
Additional HTS UOM | FPH160 - Additional HTS UOM Conversion Factor cannot be < 0 | The AddlHtsUomConvFactor from the ItemMasterHTSValues must be greater than “0” if there is an AddlRptQtyUom. Check the HTS Catalog and verify if there is a value in AddltRptQtyUom.
important
This field is numeric, so any letter or symbol on the record will create an error. |
Additional HTS UOM Conversion Factor vs AddlRptQtyUom | FPH170 - Additional HTS UOM Conversion Factor must match Weight when AddlRptQtyUom is KG | When AddRptQtyUom is established in KG, the HTSUOM conversion factor from the ItemMasterHTSValues must be equal to the value entered on the Weight field. |
Status Code | FPH180 - Status Code is not valid. | Verify that the code being used is one of the valid Status codes on the “Global Codes” catalog.
important
You cannot add new Product Codes other than the ones by default. |
Errors on FIFO
VALIDATED FIELD | ERROR MESSAGE DISPLAYED | POSSIBLE SOLUTION |
|---|---|---|
Product Number | FP010 - Product Number cannot be blank | Transactions in staging have a ‘blank’ value in the “Product Number” field (This field is a unique and mandatory identifier for transactions).
important
You can edit this information on the Edit staging transactions screen or on Invoice Detail on the Product Data tab. |
TxnCode vs ProductTypeCode | FP090 - TxnCode and ProductType do not match | The TxnCode on the transaction does not match the ProductType. For instance: the transaction being processed is an ‘SPPC’ and the product record on ItemMaster has a TypeCode of ‘IM’.
important
You can edit the ProductTypeCode on the ItemMaster record or edit the TxnCode on ‘Edit Staging Transactions,’ save the record, and validate again. |
Weight UOM | FP120 - Weight UOM must be KG | Weight UOM must be ‘KG’. |
ReceiptDocID | FP140 - Missing ReceiptDocID | Transactions in staging have a ‘blank’ value in the ReceiptDocID field. This field provides the Import Pedimento Number.
important
You can edit this information on the Edit Staging Transactions screen or on the invoice detail Product Data tab. |
ExitDocID | FP150 - Missing ExitDocID | Transactions in staging have a ‘blank’ value in the ExitDocID fiel. This field provides the Export Pedimento Number.
important
You can edit this information on the Edit Staging Transactions screen or on invoice detail Product Data tab. |
TxnCode | FP160 - TxnCode not valid | TxnCode is not registered in the Global Codes catalog.
important
You can add this manually or contact support for help. |
TxnDate | FP170 - TxnDate not valid | The format for this field is YYYYMMDDTHHMMSS, for example, 10:35:03AM on September 12, 2003 would read as 20030912T103503. If only date is available, place zeros for HHMMSS.
important
The system will display an error if the date inserted is older than 01/01/1900 or the date does not match the format. |
TxnGUID | FP180 - Transaction with this GUID already processed through FIFO | The GUID being processed has previously been assigned to another transaction that has already been processed.
important
This field is a unique and mandatory identifier for transactions. |
HTSValue | FP190 - No FIFO Processing Hts Values record found | Transactions in Staging do not have a record on the “FIFO HTS Values” table.
important
You can edit this information on the Edit Staging Transactions screen or contact support for assistance. |
HTSValue | FP200 - No MX FIFO Processing record found | Transactions in Staging do not have a record in the MX FIFO table.
important
You can edit this information on the Edit Staging Transactions screen or contact support for assistance. |
TxnQty | FP210 - TxnQty must be > 0 | Check for values that have a ‘0’ or a ‘blank’ value. Any number registered must be greater than “0”.
important
This field is numeric, so any letter or symbol on the record will create an error. |
TxnCode | FP220 - TxnCode not valid | TxnCode is not registered in the Global Codes catalog.
important
You can add this manually or contact support for help. |
TxnQty | FP230 - TxnQty > available balance | The TxnQty being processed is greater than the available balance for that specific product.
important
You must verify available balances or verify if TxnQty is correct. |
TxnQty | FP240 - TxnQty must = 1 for importation of EQ product type | For Fixed Assets transactions, the TxnQty must be = 1. |
TxnCode vs ProductTypeCode | FP250 - TxnCode and ProductType do not match | The TxnCode on the transaction does not match the ProductType. For instance: the transaction being processed is an ‘SPPC’ and the product record on ItemMaster has a TypeCode of ‘IM’.
important
You can edit the ProductTypeCode on the ItemMaster record or edit the TxnCode on Edit Staging Transactions , save the record, and validate again. |
TxnQty | FP260 - Quantity being returned exceeds quantity transferred | This error only applies for XPROC (External Process Returns) transactions, meaning that the TxnQty from the products being returned is greater than the one transferred. |
AltHTSIndex | MXFP020 - AltHTSIndex not valid | The AltHTSIndex being used for the transaction is not registered in the MXHTS catalog.
important
You can add this manually or contact support for help. |
AltHTSNum | MXFP030 - AltHTSNum vot valid | The product being processed is missing an AltHTSNum on the MX ItemMaster catalog.
important
You can add a valid AltHTSNum on the Edit Staging Transactions screen for that specific record or add a valid AltHTSNum on the MX ItemMaster. |
AltHTSDesc | MXFP040 - AltHTSDesc not valid | The product being processed is missing an AltHTSDesc (Spanish description) on the MXHTS catalog. |
RptQtyUom | MXFP050 - RptQtyUom not valid | The code RptQtyUom has to be a valid code included in the Global Codes catalog. This catalog is personalized with IP valid information.
important
If you cannot find the RptQtyUom on the catalog, contact support to check for valid codes. |
RptQtyUom | MXFP060 - RptQtyUom Code not found in Global Codes | The code RptQtyUom has to be a valid code included in the Global Codes catalog. This catalog is personalized with information provided by the client previously.
important
If you cannot find the RptQtyUom on the catalog, contact support to check for valid codes. |
MX HTS UOM | MXFP070 - MX HTS UOM Conversion Factor must be > 0 | Check for values that have a ‘0’ or a ‘blank’ value. Any number registered must be greater than “0”.
important
This field is numeric, so any letter or symbol on the record will create an error. |
BOM IM/ BOM PC | MXFP080 - No BOM found for product | The product being processed on the transaction does not exist in any of the active BOMS.
important
Please contact support if you get this error. |
BOM IM/ BOM PC | MXFP081 - BOM is recursive {0} | important
Please contact support if you get this error. |
BOM IM/ BOM PC | MXFP082 - BOM has non-existent/inactive child {0} | The product components in staging do not exist in any of the active BOMS.
important
Please contact support if you get this error. |
BOM IM/ BOM PC | MXFP083 - No BOM found for subassembly {0} | The Transactions in staging have a BOM that is not active on IP.
important
You can edit this information on the Edit staging transactions screen or on the BOMS. |
HTSIndex | FPH010 - HTSIndex Not Valid | Verify that that the record has a valid HTSIndex (this is a mandatory field). Verify that the HTSIndex is registered/validated by the HTS Codes catalog.
important
You can add a new record or can check with support for valid codes. |
HTSNumber | FPH020 - HTSNum not valid | Verify that that the record has a valid HTSNum (this is a mandatory field). Verify that the HTSNum is registered/validated by the “HTS Codes: catalog.
important
You can add a new record or can check with support for valid codes. |
HTS Desc | FPH030 - HTSDesc not valid | The product being processed has no HTSDesc (English description) on the HTS catalog. |
Value 2 | FPH080 - Value2 exceeds limit specified on Global Codes | The Value2 reported on the transaction exceeds the maximum value that was determined by the client previously in the Global Codes catalog. |
Value | FPH100 - Value exceeeds limit specified on Global Codes | The Value reported on the transaction exceeds the maximum value that was determined by the client previously in the Global Codes catalog. |
Country of Origin | FPH110 - Country Of Origin not valid | Verify that the Country Code has a correct abbreviation, for example: DN for Denmark when it should be DK. These codes have to be register on the Country Listing catalog.
important
You cannot add new Country Codes others than the ones by default. |
Manufacturer ID | Invalid Manufacturer ID | The commercial partner information has to be a valid one included on the ManufacturerID catalog. This catalog is personalized with information provided by the client previously.
important
You can add a new record manually or contact support. |
HTS UOM Conversion Factor | FPH140 - HTSUOM Conversion Factor exceeds limit specified on Global Codes | The HTSUOMConvFactor reported on the transaction exceeds the maximum conversion factor that was determined by the client previously in the “Global Codes” catalog. important
You can manually edit this value on ‘Edit Staging Transactions or contact support. |
SPI Code 1/ SPI Code 2 | FPH190 - SPI Code 1 and SPI Code 2 cannot both contain values | The fields SPI Code 1 and SPI Code2 from the HTS catalog cannot both contain values. important
Verify these values in the HTS Catalog and on the transaction record on the “Edit Staging Transactions” screen. |
CurrencyCode | FPH200 - Currency Code not active on Currency Frequency table | Transactions in staging have a CurrencyCode that is not registered on the “Exchange frequency” table. important
You can edit this information on the “Edit Staging Transactions” screen or on the “Exchange Frequency” table. |
Alt Currency Code | FPH210 - Alternate Currency Code not active on Currency Frequency table | Transactions received from staging have an AltCurrencyCode that is not registered on the “Exchange frequency” table. important
You can edit this information on the “Edit Staging Transactions” screen or in the “Exchange frequency” table in the “Catalogs” menu. |
Currency Code | FPH220 - Currency Code does not match base currency | Transactions in staging have a ‘blank value’ in the CurrencyCode field or the CurrencyCode is does not match the base currency. important
You can edit this information on the “Edit Staging Transactions” screen or contact support for assistance. |
AltCurrencyCode | FPH230 - Alternate Currency Code does not match base currency | Transactions in staging have a ‘blank’ value in AltCurrencyCode or the AltCurrencyCode does not match the base currency. important
You can edit this information on the “Edit Staging Transactions” screen or contact support for assistance. |
Related Content
-
IMMEX
Format:
Article