Error codes explain dolution: Difference between revisions

From HelpWiki Highnix
Jump to navigation Jump to search
No edit summary
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
__FORCETOC__
__FORCETOC__


'''Error Codes'''
== <span id="err message 1"><span style="color:black">This document cannot be processed because there is insufficient quantity for items marked.</span> ==
[[#err message 1|Tag:#err message 1]]
 
This error message occur when a delivery or direct invoice is processed.  If user does not set '''Negative Inventory Allowed?''' in System setup, System and General GL, then when there is insufficient inventory for the items at the time of delivery or direct invoice tranaction, this message will appear.    '''Note:''' The delivery or direct invoice date play an important part of the control.  For example, today is 1 Mar 2023.  If the stock of the item is received on 10 Feb 2023, and the delivery or direct inovice date is before the stock take in date (i.e. before 10 Feb), the same warning message will appear.  Therefore, user must determine the date of the document to be used to ensure that the stock is sufficient before processing the delivery or direct invoice.
 
[[#Top|<u>Go to Top</u>]]


In the Highnix ERP system, Error Codes serve as indicators of common issues or warnings that appear on the user interface when certain unauthorized or invalid actions are attempted. These error messages are crucial for maintaining data integrity and ensuring the smooth operation of the system.
----


Example Error Message:
== <span id="err message 1"><span style="color:black">The customer could not be added Tutorial, error code : 1062 error message : Duplicate entry for key ...</span> ==
{| class="wikitable"
[[#err message 2|Tag:#err message 2]]
|+
!''Error Message: This document cannot be processed due to insufficient quantities for marked items.''
''This error message may appear when a user attempts to process a delivery but there is an inadequate stock of one or more products required for the transaction. Unless the system configuration permits negative inventory, such transactions are prohibited to safeguard the accuracy of your system data.''
|}
Understanding Error Codes:


#Identification: Error codes are typically accompanied by a brief description or message that provides insights into the nature of the issue. Users can use this information to diagnose and address the problem effectively.
This error occur when user enter a short name of customer or supplier and when the short name already appeared in the customer or supplier records.
#Preventing Data Inconsistencies: Highnix ERP's error codes are designed to prevent actions that could lead to data inconsistencies or inaccuracies within the system. For instance, disallowing transactions with insufficient stock helps maintain precise inventory records.
#Customization: Depending on the system configuration, certain error codes and their associated actions may be customizable to align with your specific business rules and requirements.
#Resolution: Error codes often guide users toward the steps they need to take to resolve the issue. This may include adjusting quantities, seeking managerial approvals, or following other predefined processes.


By understanding and appropriately responding to these error codes, users can ensure the integrity of their data and enhance the efficiency and reliability of the Highnix ERP system.
'''Solutions:'''  Change the short name and user will be able to capture the customer or supplier records.
 
[[#Top|<u>Go to Top</u>]]


----
----


===<span id="err message 1"><span style="color:blue">Error Message: This document cannot be processed because there is insufficient quantity for items marked.</span>===
== <span id="Unable to find xref table"><span style="color:black">TCPDF error: Unable to find xref table.</span> ==
[[#err message 1|Tag:#err message 1]]
[[#Unable to find xref table|Tag:#Unable to find xref table]]
 
The TCPDF error "Unable to find xref table" means that the TCPDF library is unable to find the cross-reference table in the PDF file you are trying to process. The cross-reference table is a table that maps all of the objects in a PDF file to their respective locations in the file. Without the cross-reference table, TCPDF cannot properly process the PDF file.
 
The PDF file should be of Acrobat Reader format v5.0 (PDF format v1.4) or lower since Highnix ERP uses the open source FPDI v1.2.1 library. The PDF can be generated using most open source PDF creater such as CutePDF,  PDFCreator or doPDF.
 
There are a few possible reasons why you might be getting this error:


This error message occur when a delivery or direct invoice is processed. If user does not set '''Negative Inventory Allowed?''' in System setup, System and General GL, then when there is insufficient inventory for the items at the time of delivery or direct invoice tranaction, this message will appear.   '''Note:''' The delivery or direct invoice date play an important part of the control.  For example, today is 1 Mar 2023.  If the stock of the item is received on 10 Feb 2023, and the delivery or direct inovice date is before the stock take in date (i.e. before 10 Feb), the same warning message will appear.  Therefore, user must determine the date of the document to be used to ensure that the stock is sufficient before processing the delivery or direct invoice.
* The PDF file is corrupted.
* The PDF file is in a version that is not compatible with TCPDF.
* The PDF file is password-protected.
'''Solutions:''' Recreate the PDF using Libreoffice (export to PDF), or PDF printer such as CutePDF, PDFCreateor or doPDF.  


[[#Top|<u>Go to Top</u>]]
[[#Top|<u>Go to Top</u>]]
Line 31: Line 39:
----
----


===<span id="err message 1"><span style="color:blue">Error Message: The customer could not be added Tutorial, error code : 1062 error message : Duplicate entry for key ...</span>===
== The entered transaction does not exist or cannot be voided. ==
[[#err message 2|Tag:#err message 2]]
This message appears when the selected transaction cannot be voided.
 
The most common reasons are:
 
# '''The transaction has downstream transactions'''The transaction has already been used to create or process one or more subsequent transactions. In this case, the downstream transactions must be voided '''first''', before the original transaction can be voided.
# '''The transaction has already been fully voided'''The transaction may have been voided previously and therefore cannot be voided again.
 
=== What should I do? ===
 
# Please check the transaction and its related transactions to determine whether any downstream transactions exist or whether the transaction has already been voided.
# If downstream transactions exist, '''void them first and then try to void the original transaction again'''.


This error occur when user enter a short name of customer or supplier and when the short name already appeared in the customer or supplier records.  Change the short name and user will be able to capture the customer or supplier records.
[[#Top|<u>Go to Top</u>]]

Latest revision as of 14:00, 7 September 2026


This document cannot be processed because there is insufficient quantity for items marked.

Tag:#err message 1

This error message occur when a delivery or direct invoice is processed. If user does not set Negative Inventory Allowed? in System setup, System and General GL, then when there is insufficient inventory for the items at the time of delivery or direct invoice tranaction, this message will appear. Note: The delivery or direct invoice date play an important part of the control. For example, today is 1 Mar 2023. If the stock of the item is received on 10 Feb 2023, and the delivery or direct inovice date is before the stock take in date (i.e. before 10 Feb), the same warning message will appear. Therefore, user must determine the date of the document to be used to ensure that the stock is sufficient before processing the delivery or direct invoice.

Go to Top


The customer could not be added Tutorial, error code : 1062 error message : Duplicate entry for key ...

Tag:#err message 2

This error occur when user enter a short name of customer or supplier and when the short name already appeared in the customer or supplier records.

Solutions: Change the short name and user will be able to capture the customer or supplier records.

Go to Top


TCPDF error: Unable to find xref table.

Tag:#Unable to find xref table

The TCPDF error "Unable to find xref table" means that the TCPDF library is unable to find the cross-reference table in the PDF file you are trying to process. The cross-reference table is a table that maps all of the objects in a PDF file to their respective locations in the file. Without the cross-reference table, TCPDF cannot properly process the PDF file.

The PDF file should be of Acrobat Reader format v5.0 (PDF format v1.4) or lower since Highnix ERP uses the open source FPDI v1.2.1 library. The PDF can be generated using most open source PDF creater such as CutePDF, PDFCreator or doPDF.

There are a few possible reasons why you might be getting this error:

  • The PDF file is corrupted.
  • The PDF file is in a version that is not compatible with TCPDF.
  • The PDF file is password-protected.

Solutions: Recreate the PDF using Libreoffice (export to PDF), or PDF printer such as CutePDF, PDFCreateor or doPDF.

Go to Top


The entered transaction does not exist or cannot be voided.

This message appears when the selected transaction cannot be voided.

The most common reasons are:

  1. The transaction has downstream transactionsThe transaction has already been used to create or process one or more subsequent transactions. In this case, the downstream transactions must be voided first, before the original transaction can be voided.
  2. The transaction has already been fully voidedThe transaction may have been voided previously and therefore cannot be voided again.

What should I do?

  1. Please check the transaction and its related transactions to determine whether any downstream transactions exist or whether the transaction has already been voided.
  2. If downstream transactions exist, void them first and then try to void the original transaction again.

Go to Top