TABLE CHECK restrictions (CONSTRAINT)
The exact message is:
The AAAA statement violated the TABLE CHECK restriction'CCCC'.
The conflict occurred in the Eulanda_DDDDD-database, table'TTTT'
An exception error of the"EOleException" type has occurred
AAAA - the name of the statement. This stands for the SQL command that should be executed. This can be UPDATE, INSERT or DELETE. These commands represent the data changes, the creation of new data or the deletion of data.
CCCC - Name of the restriction. Each restriction has a unique name in the database. More about this in the next paragraph.
TTTT - Name of the table. The table in which the changes should be made
DDDD - Database name or name of the EULANDA® client
Several checks are stored in the SQL server to ensure that no inconsistent data can be saved. If an attempt is made to break such a restriction, the SQL server terminates the statement and generates an error message in the above format.
In many cases EULANDA® "translates" this error into understandable words. In some cases, however, the error may be passed on to the user without further processing. It is helpful to know exactly what the error says.
Each of these restrictions has its own name, which always begins with the capital letters CK followed by an underscore. This is followed by the abbreviation of the database table (see list of abbreviations) and the column name within the table or - if several columns are affected - a short term that describes the restriction.
TABLE CHECK Restriction 'CK_ARI_MengeMax'
The exact message is:
The UPDATE statement violated the TABLE CHECK restriction'CK_ARI_MengeMax'.
The conflict occurred in the Eulanda_xxx database, table 'ArtikelIdent'
An exception error of the "EOleException" type has occurred
The restriction CK_ARI_MengeMax
This restriction ensures that the same serial number of an item only appears once in the system. Example:
- The serial number 4711 of the article "boiler" is posted via the goods receipt.there is now exactly one piece of this serial number in the position system
- The boiler is sold
to customer "Meier", so there is still a piece in the storage system. Now no longer in the warehouse, but at the customer's site
- If you now try to post 4711 again via a goods receipt, the SQL server or the CK_ARI_MengeMax restriction recognizes this and the goods receipt cannot be posted.
However, Meiser would still have a piece available at the customer's premises. This would mean there would be two pieces of the same serial number in the system.
If the boiler 4711 is to flow back from the customer to the warehouse, then an order with the quantity minus one must be created. When posting the corresponding delivery note, you can then select serial number 4711.
A somewhat rarer case would be that the boiler manufacturer assigns the serial numbers several times over the course of time. This means that there are two different boilers with the same serial number. In EULANDA®, however, the serial numbers for an item must be unique. In this case, the new serial number must be given a different name. E.g. 4711-2. Or the existing serial number is changed under Warehousing\Serial Numbers. For example, 4711-ALT.