Error messages are messages that cancel the complete function
No. | Name in EDB | Description |
1 | EDB-IEF-E-SYMNFND | Environment variable is not defined or exported on operating system level |
2 | EDB-IEF-E-FOPN | Error when opening the file, e.g. wrong file name, directory does not exist, no access right to file |
3 | EDB-IEF-E-FRD | Read error when reading from file |
4 | EDB-IEF-E-FWRT | Write error when writing to file |
5 | EDB-IEF-E-FNOPN | File has not yet been opened it is therefor not possible to read and write (This message indicates problems with the reject file.) |
6 | EDB-IEF-E-CRD | Reading from EDB mask not possible, e.g. line number incorrect when exporting data. |
7 | EDB-IEF-E-PAR | Wrong transfer parameter when calling up an IEF function or userexit. |
8 | EDB-IEF-E-WDG | Opening an EDB mask not possible. |
9 | EDB-IEF-E-ACC | No access rights to data record in EDB. |
10 | EDB-IEF-E-NREL | Data record not released. This error might occur when relationships are to be exported which childs are not released or exported yet. |
11 | EDB-IEF-E-MNFND | No mask exists for the widget specified, the widget might not exist at all. |
12 | EDB-IEF-E-INSROW | Data record cannot be inserted into the mask. No rights, inserting not allowed, no free memory. |
13 | EDB-IEF-E-CWRT | Writing in mask field not possible. Wrong line position, no rights. |
14 | EDB-IEF-E-COPROW | Copying a line not possible. This error might occur if a new position is created in a relationship but the child format has no DataView relationship to the current relationship. |
15 | EDB-IEF-E-WDGNOPN | Widget has not been opened. |
16 | EDB-IEF-E-ARTNFND | Item not found. This error might occur in a relationship when the parent or child do not exist. |
17 | EDB-IEF-E-CFGRD | Configuration read error. This error might occur if the data base dump does not fit to the IEF version or if an IEF table is corrupt. |
18 | EDB-IEF-E-CNFND | EDB field not contained in the mask. For multi-lingual fields maybe no language ending or wrong language ending specified. For EDB-IEF-GET-DB-FLD=1 or EDB-IEF-PUT-FLD=1 the data base field is no string field. |
19 | EDB-IEF-E-FMTNF | Format not found. The IEF format specified does not exist or for relationships the parent or child format. |
20 | EDB-IEF-E-TRANFND | Transaction code not defined. When importing data records a transaction code occurs which is not defined. |
21 | EDB-IEF-E-NYIMPL | Function not yet implemented. |
22 | EDB-IEF-E-DEL | Error when deleting data records. Relationships do still exist for the data record specified, no access rights. |
23 | EDB-IEF-E-MSG | General message, exact error information is issued with message. |
24 | EDB-IEF-E-REL | Release or export of data records not possible, e.g. wrong progress indicator for the release, wrong group, no access rights. |
25 | EDB-IEF-E-REJ | Release or export of data records not possible, e.g. wrong progress indicator for the release, wrong group, no access rights. |
26 | EDB-IEF-E-INA | Release or export of data records not possible, e.g. wrong progress indicator for the release, wrong group, no access rights. |
27 | EDB-IEF-E-MODVER | Release or export of data records not possible, e.g. wrong progress indicator for the release, wrong group, no access rights, no preceding version existing. |
28 | EDB-IEF-E-MALLOC | No main memory space free. |
29 | EDB-IEF-E-NSEL | No data has been selected for export. |
30 | EDB-IEF-E-NO-LOG | This error code can be used in IEF pre-action userexits in order to prevent the report output for a certain data record. The data is not transferred. |
31 | EDB-IEF-E-FK | Release or export of data records not possible, e.g. wrong progress indicator for the transfer, wrong group, no access rights. |
32 | EDB-IEF-E-RUN | Operating system command or command procedure cannot be executed. |
33 | EDB-IEF-E-NODATA | It was tried to export and empty mask. |
36 | EDB-IEF-E-DTV | An error has occurred while calling up a DataView function. |
37 | EDB-IEF-E-WDGWRI | An error has occurred while saving the widget contents in the database. For a detailed description of the return code see function wdh_wri_lis in the manual DATAVIEW programming interface. |
38 | EDB-IEF-E-WDGUPD | An error has occurred while updating the widget contents from the database. For a detailed description of the return code see function wdh_upd_lis in the manual DATAVIEW programming interface. |
39 | EDB-IEF-E-LOCK | Data record is being edited. |
40 | EDB-BAS-NO-LICENSE | Licence error. |
41 | EDB-IEF-E-TOPNFND | Parent not found. |
Warnings are messages which cancel the function currently executed.
No. | Name in EDB | Description |
-1 | EDB-IEF-W-EOL | End of list reached when exporting data. |
-2 | EDB-IEF-W-FAOPN | File is already open. This might occur in connection with the reject file. |
-3 | EDB-IEF-W-REL | Data record has already been released (when importing) or data record has already been transferred (when exporting). |
-4 | EDB-IEF-W-ARTNUNQ | Data record is not unique. When exporting relationships this might occur when the parent and child are a type or an object parameter list and if the data record in the type master or object parameter list is not determined uniquely. When importing data records, the key fields in the format definition are not set or the key field do not determine the data record uniquely (e.g. version or revision not defined as a key field). This can be valid for the parent data record as well as for the child data record (also documents, projects.) |
-5 | EDB-IEF-W-MSG | General message. Problem is explained in more detail by the message text. |
-6 | EDB-IEF-W-NREL | Error when releasing data records, data record not released. |
-7 | EDB-IEF-W-FMTEXST | Format already contains a field definition, generation of format not possible. |
-8 | EDB-IEF-W-NREF | Relationship contains no position for transfer. |
-12 | EDB-IEF-W-NSELPAR | It has been found out that no key fields have been defined while importing data with an IEF format Please insert the marks for the key fields on the IEF field definition. |
-13 | EDB-IEF-W-NKEYW | While importing data of a relation, it has been found out that no key words (@PART_ID, @VERSION, @REVISION, @SHEET) have been defined in the relation format. Please define at least one of the key fields for the parent format as a key word (e.g. @PART_ID) in the relation format. |
-14 | EDB-IEF-W-NchildFMT | While importing data it has been found out that no child format has been assigned to the relation format. |
-15 | EDB-IEF-W-NTOPFMT | While importing or exporting data it has been found out that no farther format has been assigned to the relation format. |
-16 | EDB-IEF-W-TOPNUNQ | Parent not unique |
Information is a message which is only used as a user reference.
No. | Name in EDB | Description |
-101 | EDB-IEF-I-TON | Trace on |
-102 | EDB-IEF-I-TOFF | Trace off |
-103 | EDB-IEF-I-TINFO | Trance info |
-104 | EDB-IEF-I-LON | Log on |
-105 | EDB-IEF-I-LOFF | Log off |
-106 | EDB-IEF-I-LINFO | Log info |
-110 | EDB-IEF-I-EOF | End of file reached when importing data. |
-111 | EDB-IEF-I-VERSION | Version |
-112 | EDB-IEF-I-MSG | Universal information |
-113 | EDB-IEF-I-GFMTDEF | Generate format defaults start |
-114 | EDB-IEF-I-GFMTRDY | Generate format defaults end |
-115 | EDB-IEF-I-NO-LOG | This code can be used in IEF pre-action userexits in order to prevent the report output for a certain data record. The data is nevertheless transferred. |
-116 | EDB-IEF-I-EFK | Wrong state for modify |